On Thu, 28 Nov 2019 at 12:45, Andy Townsend <ajt1...@gmail.com> wrote:
Tagging 2 things to represent 1 physical feature just makes it extra-hard > for anyone consuming the data. > Yet we have a very similar problem with "two things, two objects." We make a tennis court surrounded by a fence two objects for good reasons. But it is very difficult to subsequently edit those objects in some editors. Not only may you not realize there are two objects, but there is no way (in some editors) of cycling through objects having all ways in common. The only way I've found is to split a node so I can move the node of one object away in order to be able to select between them, then put that node back when I've finished. It's a problem that shouldn't exist. Fixable in the tool chain. They'd have to say "OK, I've got a man_made=embankment here; now, before > I decide what to do with it, I have to see if there is another parallel one > facing the other way that tells me that what I've really got is a raised > flood bank or similar" > The editor I use shows such things with triangles on one side. So fixed in at least one alternative. > We represent other linear features (e.g. roads) as lines; it makes sense > to do the same here. > But we also have roads with areas, when that makes sense. Representing a wide embankment not a good option without a width tag and a double-sided tag and renderer support. Two parallel embankments, as currently handled, makes it clear. And also copes nicely with an irregular width without having to split the embankment in (possibly many) places. -- Paul
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
