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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: arun.planemad[at]gmail.com [Submitted to the original trac issue database at 2.49pm, Tuesday, 12th October 2010]
The export panel on the osm homepage gives the bounding coords of the selected area in 4 different boxes. It would be extremely if it also generated the entire "bbox=lon_min,lat_max,lon_max,lat_min" code that is needed for so many other osm tools like gpsmid, maperitive etc.
The text was updated successfully, but these errors were encountered:
Reporter: arun.planemad[at]gmail.com
[Submitted to the original trac issue database at 2.49pm, Tuesday, 12th October 2010]
The export panel on the osm homepage gives the bounding coords of the selected area in 4 different boxes. It would be extremely if it also generated the entire "bbox=lon_min,lat_max,lon_max,lat_min" code that is needed for so many other osm tools like gpsmid, maperitive etc.
The text was updated successfully, but these errors were encountered: