On Mon, Nov 3, 2008 at 4:34 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote:
> Hi, > > Shaun McDonald wrote: > > Relations are unordered. You could load the relation and all the ways > > referenced by it, then check to see if each way has another way that has > > the same start and end nodes, through a process of stitching. > > 1. Shaun is right BUT > > 2. I want relations to become ordered and will try to sneak this into > API 0.6; there will be no noticeable change for any API client, just > that it so happens that things are returned in the order you put them > in, rather than in any order. The rationale behind that is that people > start (ab)using the role attribute for that (e.g. a bus route with nodes > that have the roles "stop1", "stop2", "stop3" etc.), which of course is > a pain to modify. > If you're sneaking relation changes into the API, could you also allow a member to be repeated? This would be useful in describing a prohibited U-turn on a single carriageway. The same way would need to be in both the "from" and "to" roles, which I believe is currently prohibited. Karl
_______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
