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

Shared riverbank ways flood adjacent relations in Osmarender. #2363

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

Comments

@openstreetmap-trac
Copy link

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.

@openstreetmap-trac
Copy link
Author

Author: osm[at]petschge.de
[Added to the original trac issue at 5.13pm, Monday, 19th October 2009]

I tried to reproduce the problem (see riverrelations.osm above) but couldn't.

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