More route attributes
Anyone fancy attributes for service frequency, or service type for the routes?
I would add for example be interested in adding: sleeping_car=yes couchette=yes resturant=yes
and also approximate service frequency (at peak): frequency=5/week ... 10/hour seasonal=no
to be able to, for example, make a map of night train services.
Train timetables don't belong i OSM, but I think this more static information could be of use. What do you think?
- I welcome that. After seeing this post on the forum I think we need to document more attributes of train routes. I'll make a start with some examples I've seen in the wild. --Mdeen (talk) 07:29, 24 September 2018 (UTC)
Is this used for light rail, light metro, subways, etc?
Is route=train used for subways, els, metros, light metros and light rail in your area? Or do mappers use specific tags like route=subway and route=light_rail? --Jeisenbe (talk) 05:03, 11 January 2020 (UTC)
- In the Netherlands we use route=subway and route=tram where appropriate. --Mdeen (talk) 06:25, 11 January 2020 (UTC)
- In the USA, we use all of route=train ("heavy rail"), often tagged passenger=(inter)national, regional and suburban, route=subway (also considered heavy rail) is usually passenger=suburban, route=light_rail is often tagged passenger=urban, route=tram is often tagged passenger=local. So, what you are asking is a sort of big question, but route=train is "only" used where a full-sized train is used. If it is a "metro" that is substantially underground, route=subway. If it is a light_rail or tram, we tag accordingly with route=light_rail or route=tram. Stevea (talk) 12:49, 11 January 2020 (UTC)
route=bus has opening hours as a possible tag to add to the relation. What about route=train?