[landcover] rendering barrier=hedge as closed area #3395
Comments
Author: steve8[at]mdx.ac.uk Added in version just committed (r25076), will show when deployed - if using area=yes |
Author: craigloftus This fix does not allow one to mark the boundary of an area as having the barrier hedge (but still lets you do it for every other kind of barrier). I think it has changed the behaviour from that described in the documentation and from what I think many users will expect. I'm not clear this is a regression, or just an inconsistency in treatment of hedge vs other linear barriers; I can certainly understand the use-case described by thiesp. === Examples ===
The following tags have the area filled 'garden' green with a black line around the boundary ([http://www.openstreetmap.org/browse/way/79975283 #79975283]):
|
Author: Ldp Replying to [comment:3 craigloftus]:
barrier=hedge has an explicit area variant, so it's drawn as an area in this case, overpainting the landuse=farmland.
barrier=wall has no area variant. Hence only the linear version is drawn. I'm not sure what can be done about this. How is the renderer to discern between a closed way where the hedge is only around the perimeter vs. a closed way where the entire interior is hedge? They both look exactly the same to it. |
Author: craigloftus Replying to [comment:4 Ldp]:
Would you explain why barrier=hedge has "an explicit area variant" but barrier=wall doesn't? The tagging documentation ([http://wiki.openstreetmap.org/wiki/Tag:barrier%3Dhedge Tag:barrier=hedge]) doesn't say that? In fact the documentation seems to state the opposite when it says that barrier=hedge can be used to "mark the boundary of an area. Useful in conjunction with Tag:landuse=farm to mark field boundaries."?
Perhaps an explicit area=yes tag on the hedge way would be appropriate? |
Author: Ldp Replying to [comment:5 craigloftus]:
... in the mapnik stylesheet. Could've made that clearer.
How would you get onto the field when there's a hedge all around it? :)
Area handling being the default in this case, that would accomplish exactly nothing. As I said, it's a tricky one, with no clear answer just yet. |
Author: rohieb I have just discovered this behaviour. I have allotments which are surrounded by a hedge with gates in it. So I used a closed way tagged with However, the area of the way is completely green, not filled with the allotments pattern (see http://www.openstreetmap.org/browse/way/23713197). While I acknowledge the usefulness of the "area variant" of |
Author: rohieb I just tried |
Author: Ldp Replying to [comment:8 rohieb]:
Well, yes, of course. You're attaching two conflicting meanings onto a single way. That single way is processed based on its tags. If it has a landuse=, it will be processed as a polygon, not as a line. No matter what other tags are present. In fact, if there are other tags, like barrier=, that the renderer also understands, it can also only process them as a polygon as well. This is what's happening with barrier=hedge. There is a polygon variant in the stylesheet, so it can draw it as such. There is no polygon variant for barrier=wall, so it will not render a barrier, neither as a polygon nor as a line.
Sure you can model this: Don't cram two conflicting meanings onto a single way. Use two ways. You're going to have a hard time with this situation anyway (using a single way) once OSM progresses to an area datatype. |
Author: Mateusz Konieczny Nowadays it is fixed. |
Reporter: thiesp
[Submitted to the original trac issue database at 12.00am, Wednesday, 15th December 2010]
Look here:
http://www.openstreetmap.org/?lat=55.372914&lon=10.404336&zoom=18&layers=M
This is the corresponding changeset:
http://www.openstreetmap.org/browse/changeset/6664276
The hedges mapped as areas aren't rendered as expected. I expected they would be filled green, instead of the color from the polygon below.
I even added area=yes to try to enforce it, but no luck.
The text was updated successfully, but these errors were encountered: