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: 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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: