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.
Originally I used an adjacent segment of the Spokane River riverbank that was already a member of http://www.openstreetmap.org/browse/relation/74223 but I discovered that Osmarender actually filled my Gonzaga relation with blue water and labelled it part of the Spokane River as well. Mapnik did not have this problem and rendered the two adjacent relations like I expected. After I ran into this issue in Osmarender I also tried removing the water=riverbank tag from the shared segment and moving it into the Spokane River relation, but the it didn't make a difference in the rendering.
The text was updated successfully, but these errors were encountered:
Reporter: axodys
[Submitted to the original trac issue database at 12.14pm, Thursday, 8th October 2009]
In an effort to clean up and reduce redundant ways I recently created the following relation for Gonzaga University:
http://www.openstreetmap.org/browse/relation/283657
Originally I used an adjacent segment of the Spokane River riverbank that was already a member of http://www.openstreetmap.org/browse/relation/74223 but I discovered that Osmarender actually filled my Gonzaga relation with blue water and labelled it part of the Spokane River as well. Mapnik did not have this problem and rendered the two adjacent relations like I expected. After I ran into this issue in Osmarender I also tried removing the water=riverbank tag from the shared segment and moving it into the Spokane River relation, but the it didn't make a difference in the rendering.
The text was updated successfully, but these errors were encountered: