#10770 closed enhancement (fixed)
[Patch] save coordinates in current map projection
Reported by: | TobWen | Owned by: | simon04 |
---|---|---|---|
Priority: | normal | Milestone: | 15.10 |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Since JOSM supports multiple map projections with the plugin "proj4j" and since it supports output in GeoJSON and GPX, it would be nice to export coordinates in the current map projection.
When working in EPSG:31466, coordinates get transformed back to EPSG:4326 on export. Since the transformation isn't perfect, errors are growing. Sure, that's not important for OSM, but JOSM can also be used outside of OSM.
GeoJSON, GPX and other formats support different map projects, so it would be nice to see an expert settings to switch from geographic coordinates to map coordinates.
Attachments (2)
Change History (9)
follow-up: 2 comment:1 by , 10 years ago
comment:2 by , 10 years ago
Replying to stoecker:
Regarding the errors it does not help, as JOSM always uses geographics coordinates. Different projections are only used for display. But the idea in itself may have other benefits.
Like the problems with tool functions (e.g. create circle,align etc.) ?
by , 10 years ago
Attachment: | 10770.patch added |
---|
comment:3 by , 10 years ago
Milestone: | → 15.10 |
---|---|
Owner: | changed from | to
Summary: | save coordinates in current map projection → [Patch] save coordinates in current map projection |
attachment:10770.patch adds a *.proj.geojson
exporter which writes the GeoJSON file with the currently set map projection. See http://geojson.org/geojson-spec.html#named-crs for the CRS specification in GeoJSON.
follow-up: 6 comment:5 by , 9 years ago
Hi,
There is a problem with the CRS field, it does not comply with the geojson spec.
Spec says: A non-null CRS object has two mandatory members: "type" and "properties".
This CRS object should look like: {"type":"name", "properties":{"name":"EPSG:4326"}}
See http://geojson.org/geojson-spec.html#coordinate-reference-system-objects for examples.
comment:6 by , 9 years ago
comment:7 by , 9 years ago
See also #13358: GeoJSON as in RFC 7946 no longer permits projections other than WGS84.
Regarding the errors it does not help, as JOSM always uses geographics coordinates. Different projections are only used for display. But the idea in itself may have other benefits.