|
Barrier:hedge does not explicitly cover this type of barrier! A line of trees is a common natural boundary. So how should it be mapped? |
|
A line of trees is mapped as a way with the natural=tree_row tag. How is natural=tree_row modelled on OSM various layers?
(05 Feb '12, 16:57)
Meersbrook
This still leaves the barrier issue open. A hedge is a barrier that is usual pruned but a line of trees that act as a barrier is not. Such trees could of course also be wild bushes.
(05 Feb '12, 17:20)
dcp
|
|
Just make sure you draw your line from left to right as with natural=cliff else your trees in the polyline may be upside down 2
I'm not aware of any left-to-right convention for tree rows. With cliffs, the convention is necessary because they have "upper" and "lower" sides in the real world. No comparable asymmetry exists with trees.
(06 Feb '12, 06:47)
Tordanik
1
Yes, L to R convention applies and as with natural=cliff, the Oregon displays exactly the opposite of what OSM shows! So if you want your GPS to show things correctly, OSM should be the opposite.
(07 Feb '12, 20:10)
wilda69
3
That'd be a bug in the software / method that was used to convert the data to Garmin format, wouldn't it? Do you have a specific example?
(20 Aug '12, 17:51)
SomeoneElse ♦
|
Is the row of trees impassable? If no, then it is not a barrier, but something else.
This I don't know! Bing imagery! This leads to two questions: How do we map a line of trees that is not a barrier? - natural:tree is meant to used for special trees How do we map a barrier comprising a line of trees?
Go and have a look. Surveying is important. If you just create a map based on Bing imagery, why not just use Bing imagery?
If it really is a barrier of plants (like trees) I'd call it a hedge.