Re: [Tagging] better mapping for embankments / slopes

2016-11-30 11:03 GMT+01:00 Volker Schmidt : > I would tag the structures in the illustration as "retaining_wall" in OSM. +1, but there's also an embankment. And there are similar cases without the retaining wall, so it's of course completely possible to have an embankment

Re: [Tagging] better mapping for embankments / slopes

> > 'Embankment' is frequently used for a built-up structure on a steep > hillside that keeps a road, railroad, or similar feature from sliding into > a gorge or river. See https://en.wikipedia.org/wiki/ > Embankment_%28transportation%29#/media/File:Embankment_1_%28PSF%29.png > for an illustration

Re: [Tagging] better mapping for embankments / slopes

Although it can be interesting how to map embankment properties on other objects like roads or railroads (where the discussion led in the meantime), this discussion started as a question how to map embankments on their own, as features. I am interested in providing the data needed to create a map

Re: [Tagging] better mapping for embankments / slopes

Javbw > On 30 Nov 2016, at 7:28 AM, Kevin Kenny wrote: > > 'Embankment' is frequently used for a built-up structure on a steep hillside > that keeps a road, railroad, or similar feature from sliding into a gorge or > river. So a retaining wall (or reinforced

Re: [Tagging] better mapping for embankments / slopes

I render the things that OSM shows as cliffs, because sometimes surprises lurk between the contour lines. Otherwise, when I care, on my own maps I render elevation contours (and hence have no use for the cliff height in the data base). In a spot like

Re: [Tagging] better mapping for embankments / slopes

I would hope that a scheme can be had that is one sided - and the same for cliff, embankment, cutting etc. As such it should be one sided. After all another side could have a different slope/area. A single sided scheme could be used for 2 sided or multi sided structures by many separate one

Re: [Tagging] better mapping for embankments / slopes

It makes sense that a road embankment have only one slope. Perhaps for a levee[1] we need a specific tagging system because a levee has always two slopes. I'm native of the Po Valley where levees are along every river (Volker can confirm it ;) ). A levee for flood prevention could be simple[2]

Re: [Tagging] better mapping for embankments / slopes

'Embankment' is frequently used for a built-up structure on a steep hillside that keeps a road, railroad, or similar feature from sliding into a gorge or river. See https://en.wikipedia.org/wiki/Embankment_%28transportation%29#/media/File:Embankment_1_%28PSF%29.png for an illustration from

Re: [Tagging] better mapping for embankments / slopes

On 29 November 2016 at 22:03, Warin <61sundow...@gmail.com> wrote: > Not all embankment have 2 slopes > To my understanding of the English term, an "embankment" is the equivalent of dyke or levee and is a long, narrow man-made elevation. Therefore they always have two slopes of opposite

Re: [Tagging] better mapping for embankments / slopes

Not all embankment have 2 slopes .. nor does a 'slope' describe all of the properties of an embankment. The same problem exists for a 'cliff' and a 'cutting' ... and stairs that cover a large area. So use what has been done for them as a guide. What are the key properties of these features

Re: [Tagging] better mapping for embankments / slopes

If you want to micromap slopes you should create a new key "slope" or something similar. An embankment has two slopes. It is equivalent to dyke or levee. The one-side embankments that are defined in the OSM wiki, are in reality slopes and should be retagged accordingly. Independently of the name

[Tagging] better mapping for embankments / slopes

Currently we are mapping only one side of the embankment (I think it's the upper side, but am not sure if the wiki says this explicitly), with the direction. What we would IMHO need is a way to map the lower side as well and to combine both. A closed polygon will not work I believe. The obvious