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 used fo the tag I see the prblem of defining where the slope starts, normally these are rounded features. On 29 November 2016 at 13:48, Martin Koppenhoefer <[email protected]> wrote: > 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 solution that comes to mind is a new relation type: in case > the upper end is mapped, draw a new way for the lower end and combine both > with a relation (possibly assigning roles like upper and lower, maybe also > draw lateral ways (ways that connect the ends of the upper and lower ways > and defines their shape) in cases they are not straight). (The type=area > relation does this) > > Maybe it could also be done without the relation, simply by tagging the > upper and lower ways accordingly, and connect them at least at one of their > ends with an explicit lateral way (and respective tags). This would require > from the data user to topologically search for the embankment area in order > to be able to render it (or make other use). > > What do you think, which representation is better? Are there alternatives? > > Cheers, > Martin > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
