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
One constant issue I have with GeoJSON is, that people export whatever Projection they are currently using in QGIS and the resulting file does not conform to the specification which is explicit in requiring urn:ogc:def:crs:OGC::CRS84
Hm yeah, difficult topic. As you said, GeoJSON should be always latlon coordinates, but as other coordinate systems were allowed in an earlier specification, using GeoJSON like that is still not explicitely invalid.
Unfortunately afaik there is no consistent system how the coordinate system string is defined, I have seen other definitions involving any form of 1984, 4326 etc. that can be read by custom tools.
So yeah we could add an optional function to reproject it, but:
It would probably fail to recognize some custom definition strings
It probably needs to stay optional and can't be applied automatically (to avoid errors with the above case and unintended applications by the user.
But yeah I can imagine an additional function and in the webapp a button popup "Hey your GeoJSON seems to use a different crs, do you want to transform it 4326?"
One constant issue I have with GeoJSON is, that people export whatever Projection they are currently using in QGIS and the resulting file does not conform to the specification which is explicit in requiring
urn:ogc:def:crs:OGC::CRS84
https://stevage.github.io/geojson-spec/#section-4
It would be awesome, if the validator could fix this automatically.
The text was updated successfully, but these errors were encountered: