Multipolygon sharing boundary with shore renders incorrectly #3183
Comments
Author: simone.saviolo[at]gmail.com Another example of the bug happening: http://tools.geofabrik.de/mc/?mt0=mapnik&mt1=tah&lon=8.42239&lat=45.32467&zoom=17 The pedestrian area is drawn as a multipolygon, and there is no coastline involved. |
Author: tms13 A couple more examples, in case that helps:
(the last is waiting for a Mapnik redraw, but it definitely looks wrong with osmarender). |
Author: tms13 The common feature appears to be that ways that are tagged natural=coastline or part of another (correctly rendered) multipolygon get dropped, and replaced with a straight line to close the area. Does the multipolygon code somehow eat its arguments? |
Author: simone.saviolo[at]gmail.com Replying to [comment:4 tms13]:
That is not the only problem. If you look at my example http://tools.geofabrik.de/mc/?mt0=mapnik&mt1=tah&lon=8.42239&lat=45.32467&zoom=17 in the west-most part of the multipolygon you'll notice huge interpretation errors, even though the ways are not shared with any other multipolygon, or any other relation at that. In my specific case, this may be due to the fact that certain members (the ways that run across the road, perpendicular to the blocks) have not been given any role, while all the others are tagged as "outer". Mapnik, though, handles this correctly, and the multipolygon has no inner member anyway. I suggest the priority of this bug be elevated. Multipolygons are a long-accepted official feature of OSM, and the fact that Osmarender itself doesn't handle them correctly seems to me more than a "major" bug. |
Author: tms13 Replying to [comment:5 simone.saviolo@]:
It's probably worth fixing those, and checking the result is fully closed, using [http://ra.osmsurround.org/analyze.jsp?relationId=1231156 Relation Analyzer]. As you say, there may well be two different but related issues, and it's probably worth having separate examples of both. Labelling all the roles shouldn't be necessary, but it can't hurt! |
Author: monxton is this another example: http://www.openstreetmap.org/browse/relation/1400796 ? |
Author: monxton Replying to [comment:7 monxton]:
This eventually healed itself - perhaps one tile was updated several days before its neighbour? |
Author: iandees Cleaning aging tickets. |
Reporter: Wim L
[Submitted to the original trac issue database at 7.29pm, Sunday, 22nd August 2010]
Actually I'm not sure that the shore is the problem. But anyway, there is a park here which is bounded on one side by the lake shore:
http://www.openstreetmap.org/browse/relation/907023
http://www.openstreetmap.org/?lat=47.62702&lon=-122.33772&zoom=17&layers=O&relation=907023
Notice how Osmarender draws a straight line for the north boundary of the park rather than following the lakeshore.
The text was updated successfully, but these errors were encountered: