-
Notifications
You must be signed in to change notification settings - Fork 8
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
Can we simplify large GeoJSONs? #12
Comments
Worth noting that all 3 of those are the same feature (a lake with very precise mapping of edges, and tributaries, creeks, etc around it) |
Also realized that the JSON write includes indents which we can drop to reduce file size |
JSON write updated in 9dc4f1a |
Confirming this is still an issue and these are pushing us close to GitHub max file size for combined geojson zip |
Moving this off of launch milestone |
Note that these trigger errors based on GDAL's OGR_GEOJSON_MAX_OBJ_SIZE env var, which defaults to 200MB https://gdal.org/drivers/vector/geojson.html |
One more note: considering that this project is for a hydro power plant, we can likely get a better feature than the entire lake. |
Currently there are 3 GeoJSONs that are about 7x larger than the next largest GeoJSONs.
These 3 make up about 30% of the combined GeoJSON's total size.
Possible solution is to simplify these features, but when do we decide to simplify and how much do we simplify?
The text was updated successfully, but these errors were encountered: