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

osmarender.xsl doesn't correctly fetch minlon from a bounds element inside a rules element #3322

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

osmarender.xsl doesn't correctly fetch minlon from a bounds element inside a rules element #3322

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: osmarender Priority: minor Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: royhodgman
[Submitted to the original trac issue database at 7.28pm, Wednesday, 3rd November 2010]

Of the four subelements in a bounds element in a rules file (minlat, minlon, maxlat, maxlon), all but minlon are correctly used by osmarender.xsl. Currently instead of looking into the rules file for the value of minlon, osmarender instead looks into the osm file.

This patch fixes that behavior.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: bob[at]cakebox.net
[Added to the original trac issue at 9.16pm, Wednesday, 3rd November 2010]

Thanks for the patch, applied in r24053

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: osmarender Priority: minor Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac