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: bob[at]cakebox.net [Submitted to the original trac issue database at 7.43pm, Monday, 11th August 2008]
Ref JOSM ticket [http://josm.openstreetmap.de/ticket/1112 #1112] there can now be several elements in a .osm file, osmarender should take the leftmost/rightmost/topmost/lowest coordinates from all bounds elements.
In addition I think the fallback code to look over all the data and calculate bounds should be moved so that it only runs if needed, that should save at least some resources.
The text was updated successfully, but these errors were encountered:
Reporter: bob[at]cakebox.net
[Submitted to the original trac issue database at 7.43pm, Monday, 11th August 2008]
Ref JOSM ticket [http://josm.openstreetmap.de/ticket/1112 #1112] there can now be several elements in a .osm file, osmarender should take the leftmost/rightmost/topmost/lowest coordinates from all bounds elements.
In addition I think the fallback code to look over all the data and calculate bounds should be moved so that it only runs if needed, that should save at least some resources.
The text was updated successfully, but these errors were encountered: