-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently can't provide custom args when specifying a custom command #79
Comments
Good point, maybe we add a
Thoughts? |
I will have a look sometime this week and make a pull request |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Sorry, I never got round to this |
One possible workaround is to create a small shell script that receives all parameters.
Then use the script, using It works, but it would be nice to support this on ogr2ogr module. |
Hi,
I previously submitted a pull request for allowing for switching the command to use ogr2ogr via Docker (#60). However I've just checked now and it's not working. Looking at the code I'm actually not sure that it ever worked... I apologise!
I would like to use this feature now though, so I would like to fix it.
Looking at the
run
function: https://github.com/wavded/ogr2ogr/blob/master/index.ts#L147-L170, it doesn't seem like it's possible to specify an alternative command that requires args.for example, If I try to run via docker (this is currently in the readme):
Then I get an error:
In the code
It looks like the command should actually just be
docker
, and the args should be['run', '-v', etc. etc., ... then the ogr2ogr args]
.But currently there is no way of specifying this
The text was updated successfully, but these errors were encountered: