Modify

Opened 9 months ago

Closed 2 months ago

Last modified 2 months ago

#17495 closed enhancement (fixed)

GeoJSON import seems to ignore EPSG code

Reported by: stoecker Owned by: Don-vip
Priority: normal Milestone: 19.10
Component: Core geojson Version:
Keywords: Cc:

Description

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.

Attachments (1)

R21H23UTM.json (798 bytes) - added by stoecker 9 months ago.
GeoJSON file in EPSG:25832

Download all attachments as: .zip

Change History (11)

Changed 9 months ago by stoecker

Attachment: R21H23UTM.json added

GeoJSON file in EPSG:25832

comment:1 Changed 9 months ago by Don-vip

Resolution: wontfix
Status: newclosed

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

comment:2 Changed 9 months ago by stoecker

Resolution: wontfix
Status: closedreopened

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.

comment:3 Changed 9 months ago by Don-vip

Type: defectenhancement

comment:4 Changed 2 months ago by Don-vip

Milestone: 19.10
Owner: changed from Larry0ua to team
Status: reopenednew

comment:5 Changed 2 months ago by Don-vip

Owner: changed from team to Don-vip
Status: newassigned

comment:6 Changed 2 months ago by 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.

comment:7 Changed 2 months ago by 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.

comment:8 Changed 2 months ago by Don-vip

Resolution: fixed
Status: assignedclosed

In 15442/josm:

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

comment:9 Changed 2 months ago by stoecker

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

comment:10 Changed 2 months ago by Don-vip

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

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Don-vip.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.