-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add CRS to geojson output #14
Comments
Is there a need for CRS? According to the last paragraph under "DESCRIPTION" in http://www.gdal.org/gdalwarp.html a Mercator GeoJSON with no CRS should be fine when the warp destination is Mercator. The GeoJSON authors are recommending against the old GeoJSON objects in the latest draft submitted to the IETF: http://tools.ietf.org/html/draft-butler-geojson-04. I'm uncomfortable with having mercantile write the old style CRS objects. |
@sgillies without CRS, gdalwarp assumes geojson cut line to be in WGS84, it appears from our testing yesterday. Sent from my iPhone
|
Dammit, gdalwarp. I'm looking into it now. Meanwhile, here's the workaround using ogr2ogr to make an EPSG:3857 shapefile.
I should update Fiona's fio script to allow the same kind of thing. |
See #16 (comment). Right now the workaround is to pipe CRS-less GeoJSON through ogr2ogr using /vsistdin/ and /vsistdout/.
|
Fixed in Mercator 0.4 (coming soon). See #16 (comment) |
Add the CRS info to the geojson output.
Currently the workaround is this:
cc @hrwgc
The text was updated successfully, but these errors were encountered: