On Sun, Nov 8, 2015 at 5:24 PM, Dave Swarthout <daveswarth...@gmail.com> wrote:
> > On Mon, Nov 9, 2015 at 5:39 AM, moltonel 3x Combo <molto...@gmail.com> > wrote: > >> While I agree that relations can break and can be tricky to edit, I >> find it tiring to see this argument repeatedly used against the use of >> relations for this or that usecase. >> > > Your point is well taken. You've heard the last on this topic from me. I > suppose in some way my arguments are an attempt to raise awareness of the > limitations of the tools we use to work with relations not with the use of > relations, which are certainly necessary to deal with complex mapping > situations. > Though it's one of those chicken/egg problems. Something's got to make the first move. I really believe bringing road routes onto the same scheme as every other route used in OSM is about the only real way to break the deadlock with the toolchain on this and get some creative juices flowing on how to make relations less of the red-headed stepchild people are making it out to be. We ran into the same issue and overcame it with turn restrictions already...now it's almost exceedingly difficult to break one of these relations in JOSM. Granted, I've seen folks also bring up the difficulties with administrative boundaries, however, that type of relation has it's own unique set of issues editing that are largely not in play with routes. Additionally, road routes tend to be the simplest flavor of route, since it's just an ordered list where each member way only appears one time: Very editor and validator friendly already. I have run into the conflict situation a few times when working with very long routes crossing more frequently edited areas, however, this conflict is usually pretty obvious and easy to resolve with a sort and check for continuity. Where I have run into issues that make it difficult to tell if the relation is correct is when a route ends on a dual carriageway on one or both ends with at least one central segment being a two-way single carriageway. In this case, the simplest fix seems to be to create a super-relation, and then add a child relation for each direction with a role of a cardinal direction, and have all the ways in the child directions have a role of forward or backward as appropriate, and tag the relation direction=west, for example (this is already how Interstates, which are, AFAICT, always fully divided). But, you do get a lot of advantages from relations for this, such as being able to quickly and easily pull from API an entire network of highways, a single highway, or even just a section where it shares with another route, in a relatively sane and easy way.
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
