-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Way to make ogr2ogr available in path? #29
Comments
Normally everything Which driver are you using and what is the transformation you are doing? |
Basically it is any variety of common geospatial formats (shp, kmz, gpkg, etc.) to geojson. I haven't tried kmz or gpkg but it looks like Also, I am happy to close this and move over to stack overflow or gis stack exchange if you'd rather deal with this sort of question there! |
GeoJSON has an excessive memory problem usage for sure - that is why GeoJSONSeq exists. Is there a concrete |
Hi, and thank you so much for this library!
I am dealing with datasets that I cannot bring into memory all at once, and to my understanding methods like
vectorTranslateAsync
need the data to be provided as a dataset in memory.I am wondering if there is a way to leverage this library to expose ogr2ogr in path. I would like to execute some function like
is that possible using this library? If not, is there a way to use this library to process data with ogr without bringing the full dataset into memory?
The text was updated successfully, but these errors were encountered: