[Talk-transit] maintenance is very time consuming on public transport routes

[Jo]

First we need to decide that this is the way to go. The name for the
relation could be type=route_segment. What is used in the walking routes?

Then we need to get the renderers to follow suit.

Writing a MAPCSS to make sure it's rendered correctly in JOSM wouldn't be
too hard.

JOSM already has all that is needed to add relations to other relations.
What would be nice is a 'mode' where the route is visualised expanded to
check whether the result is continuous.

Polyglot


2013/12/2 Teuxe <teuxe at free.fr>

> Mike N <niceman at att.net> a écrit :
>
> >On 12/1/2013 5:32 PM, Jo wrote:
> >> Hmm, I was thinking of staying more or less within the lines of what
> >we
> >> have now, but take away the burden of 10, 20, 70 relations on the
> >same
> >> piece of road.
> >
> >  I'm just curious - what type of data consumer could use information
> >from OSM which contains 70 routes in a road segment?  It would seem to
> >be too many to fit on a map display, but I suppose a device would be
> >able to highlight a single route variation on demand.
>
> You're right, we would have to think of ways to integrate the following
> operations in edit tools:
> - Adding items to a relation (OK itns available)
> - Removing items from a relation (one by one, feasible)
> - Copying a relation
> - Splitting a relation into two relations (the main issue with our
> "variants" issue): how to visually handle this?
> - Sorting items in a relation?
>
> Regarding "groups of segments" to be represented on a tool, this is
> already possible since we do that with routes.
> Now how to call this relationship?
>
> Teuxe
> _______________________________________________
> Talk-transit mailing list
> Talk-transit at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-transit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-transit/attachments/20131202/7c88621c/attachment.html>