Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Improve <bounds> handling #1107

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Improve <bounds> handling #1107

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

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.

@openstreetmap-trac
Copy link
Author

Author: bob[at]cakebox.net
[Added to the original trac issue at 7.03pm, Wednesday, 11th February 2009]

Fixed in r13669

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant