On Mon, Feb 16, 2015 at 11:58 AM, Éric Gillet gill3t.3ric+...@gmail.com
wrote:
2015-02-16 13:03 GMT+01:00 fly lowfligh...@googlemail.com:
There are still cases where forward/backward are useful with P2-routes.
E.g. a route with a loop and some members used twice but different
directions.
Can you send links to the route relations? (Ctrl-Shft-h of Ctrl-Shift-i in
JOSM, then copy/paste the url).
That rendering with all the red lines is not the best way to represent PT.
Jo
2015-03-04 12:55 GMT+01:00 Paul Johnson ba...@ursamundi.org:
On Mon, Feb 16, 2015 at 11:58 AM, Éric Gillet
2015-02-16 13:03 GMT+01:00 fly lowfligh...@googlemail.com:
There are still cases where forward/backward are useful with P2-routes.
E.g. a route with a loop and some members used twice but different
directions.
Shouldn't one just duplicate the stop_positions in the relation, and add
ways
Loops and spoons are still quite common, even when each variation gets its
own route relation to describe which ways are used from beginning to end.
What is better in v2 is that the way to describe each of the variations, is
completely unambiguous.
To me they are easier to fix when they get
Yes, I'm reconsidering my POV. It will probably make sorting the members
automatically a lot easier than it is atm.
/me is off to go and convert some route relations... :-) (Helped by a
script ofc, doing it manually is a chore. So I'll adapt the script and let
you know when it's ready to be
There are still cases where forward/backward are useful with P2-routes.
E.g. a route with a loop and some members used twice but different
directions.
Personally, I still use forward/backward on any member of a route which
is only used in one direction and for all P2-routes as it makes it much
On the one hand I'm not adding roles to the ways in PT routes relations
anymore, instead I add all the ways in the correct order. Some ways are
included twice.
But if you prefer to add them, you have to know forward/backward relates to
the direction of the way itself. If it follows the arrow:
