Ticket #6 (closed defect: fixed)
Export to GPX maxlon attribute wrong for data in the western hemisphere
| Reported by: | Ed Davies <osm@…> | Owned by: | imi |
|---|---|---|---|
| Priority: | minor | Component: | unspecified |
| Version: | latest | Keywords: | |
| Cc: |
Description
With data which is all in the western hemisphere (around longitude -0.793, latitude 51.62) using the Files -> Export to GPX command produces a GPX file with the metadata element containing the following element:
<bounds minlat='51.62387073' minlon='-0.793708973429861' maxlat='51.628462672' maxlon='4.9E-324' />
The minlat, minlon and maxlat attributes appear reasonable but the maxlon value is wrong.
Adding a node to the east of the prime meridian corrects the problem. My guess is that JOSM initalizes the minlon value to java.lang.MIN_VALUE then updates it when any subsequent values are found to be larger. All points in the western hemisphere are, of course, smaller. Presumably the same thing would happen for latitudes in the southern hemisphere.
I'm not sure of the priority of this report - it depends on whether any relevant software actually uses the bounds. I don't know of any but don't know much about GPX.
