You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both of the classes mentioned in the issue title have overrides to the default asGeoJson method implemented in OGCGeometry. On calling op.execute for the GeoJSON writer, both pass in a null in place of the spatial reference of the geometry. The GeoJson output then contains a {"crs": null} object.
Is this by design? It differs from the behaviour of e.g. ST_AsGeoJSON in PostGIS where we would see:
SELECT ST_AsGeoJSON(geom) FROM mytable;
st_asgeojson
------------------------------------------------------------------------------------------------------------------------------
{"type":"MultiPolygon","crs":{"type":"name","properties":{"name":"EPSG:26910"}},"coordinates":[[[[0,0],[0,1],[2,2],[0,0]]]]}
Happy to open a PR if there's no good reason why the esriSR shouldn't be passed to the GeoJSON writer.
The text was updated successfully, but these errors were encountered:
Hello Esri team and wider contributing group.
Both of the classes mentioned in the issue title have overrides to the default asGeoJson method implemented in OGCGeometry. On calling
op.execute
for the GeoJSON writer, both pass in a null in place of the spatial reference of the geometry. The GeoJson output then contains a{"crs": null}
object.Is this by design? It differs from the behaviour of e.g. ST_AsGeoJSON in PostGIS where we would see:
Happy to open a PR if there's no good reason why the
esriSR
shouldn't be passed to the GeoJSON writer.The text was updated successfully, but these errors were encountered: