GeoJSON import seems to ignore EPSG code

[stoecker]

I have created a GeoJSON file with coordinates differing to WGS84. Other tools like KDE marble can load it. conversion with ogr2ogr works as well:

ogr2ogr -t_srs EPSG:4326 -f GeoJSON R21H23.json R21H23UTM.json

Only JOSM loads it wrong.

[stoecker]

GeoJSON file in EPSG:25832

[Don-vip]

GeoJson coordinates must be in WGS84, the plugin respects the specification. See ​https://github.com/JOSM/geojson/issues/5

[stoecker]

Section 4 states "However, where all involved parties have a prior arrangement, alternative coordinate reference systems can be used without risk of data being misinterpreted."

GeoJSON with different coordinate systems is part of software like geoserver or as said marble.

If we reject different system, then this should be said instead of importing invalid data like ATM.

JOSM is able to do coordinate transformation internally, so it's not clear to me why it should not be supported.

[Don-vip]

The 2008 GeoJSON spec states:

OGC CRS URNs such as "urn:ogc:def:crs:OGC:1.3:CRS84" shall be preferred over legacy identifiers such as "EPSG:4326"

I won't add complete support of this. I will only consider urn:ogc:def:crs:OGC:1.3:CRS84 exact string and strings starting by urn:ogc:def:crs:EPSG: as in your example. I guess there are other values possible.

[Don-vip]

I won't also support linked CRS. That's a security risk as it requires fetching a remote WKT on the internet and it is not used in your example.

[Don-vip]

In 15442/josm:

fix #17495 - limited support of named CRS in GeoJSON import

[stoecker]

Thanks. I need that from time to time at work. Makes life easier when I don't have to convert the stuff first.

[Don-vip]

You're welcome. Can I ask in return a status about #10033?