Route (legacy) is not really "legacy"

[akks]

People complain that relation "type=route" is called "legacy" relation.

There is of course route in public transport section, which is more suitable, but this is Public transport route, not hiking/automotive/etc.

As far as I know, type=route is the only type of universal relation.
(type=network is a group of routes, super-relation)

So the names of the presets should be changed somehow. I do not attach the patch because do not knoq the best words.

Maybe "Transport route" for public transport and "Route" for universal one.
Maybe "Route" for public transport and "General route" for universal one...

[Don-vip]

​The wiki distinguishes different kind of routes with ​Public transport routes and ​other routes.

[Don-vip]

I'm hunting anonymous tickets, did you also create #8564 and #8565 ? :)

[akks]

I'll ask him to register :)

[akks]

So let us change Route->"Public transport route" and "Route(legacy)->Route" ?

The translation will be broken with such change... What is the best way and time to do this?

[skyper]

Replying to akks:

So let us change Route->"Public transport route" and "Route(legacy)->Route" ?

The translation will be broken with such change... What is the best way and time to do this?

Think Route->"Public transport route" and Route(legacy)->"General route" will make it more obvious.

[Don-vip]

Ticket #8564 has been marked as a duplicate of this ticket.

[andygol]

Replying to skyper:

Replying to akks:

So let us change Route->"Public transport route" and "Route(legacy)->Route" ?

The translation will be broken with such change... What is the best way and time to do this?

Think Route->"Public transport route" and Route(legacy)->"General route" will make it more obvious.

We can leave "Route" as it is. This item situated in the sub-menu Public transport. Route(legacy)->"General route" agreed.

[akks]

I agree that Route(legacy)->General route is the best choice for now.
(Route in public transport will remain translated)

@stoecker: I would commit it, but what about stabilization and translations?

[Weide]

When choosing the wording...
Just to make things more complicated...

Inside of the public transport realm there are "legacy Routes" and "Public Transport Routes". They are of course both for Public Transport, but the latter refers to routes made according to the Public Transport Proposal while the first one refers to the "old style".

Weide

[akks]

Replying to Weide:

When choosing the wording...
Just to make things more complicated...

Inside of the public transport realm there are "legacy Routes" and "Public Transport Routes". They are of course both for Public Transport, but the latter refers to routes made according to the Public Transport Proposal while the first one refers to the "old style".

Weide

The problem is that the same relation type=route is not for public transport only. Is is only extended by new scheme to fit Public transport better.

I propose to rename Route (PT/Route) to Public transport route and Route (legacy) to General route (or Generic route, or Route?)

[Weide]

Sorry, ich hatte nicht gründlich genug mitgelesen.

"General route" wäre nicht schlecht.

[akks]

In 5838/josm:

see #8563: (presets) Route(legacy) renamed to General route, Route - to Public transport route
please discuss and then update translations

[akks]

Let it be, then.

@team: If the wording is incorrect, rename it again, please.
Then we need to update transaltions.

I think we should also modify General route preset content, removing "deprecated" public transport roles or placing the at "legacy/deprecated transport roles" section. They are not "general", they are legacy :)

Maybe the new preset "Transport route (legacy)" should be added (is it is still used).

Why deprecated "forward" and "backward" roles are still used 1 464 859 and 284 079 times? Are they used for non-PT routes?

[anonymous]

Are they used for non-PT routes?
Yes, they used by route=road for distinquish the role of oneway roads in road routes ( "Route(legacy)" ). It is useful, e.g., in route length computing and so on.

[akks]

This is fixed and translated, I guess.