On 10/04/2011 03:32 PM, Arun Ganesh wrote:
I did not propose to tag the *way* as commuter rail, but the
*relations* regarding these train connections. Commuter rail often
uses the same rail tracks as long distance services. That is why
railway=rail is correct for the ways; but IMHO route=commuter for
the relations is interesting information.
Ah ofcoure, relation tagging makes sense.
+1
Currently, I see that in Germany some systems are tagged as light_rail
(those which use dedicated rail infrastructure), others are tagged as
train (or rail, not sure) if they use standard rail infrastructure, but
both are marketed in the same way (S-Bahn) and passengers likely will
perceive both systems as being similar.
And as the wiki page [1] states: it's generally best to go with whatever
the users of that service general understanding of it would be -- so
having two different tags for route relations which users perceive as
similar is not really nice. Yes, a dedicated route type for this would
be very much appreciated.
You might want to add some characteristics that generally distinguish
such services from ordinary rail connections:
- Metropolitan area (city and surroundings)
- Schedules with frequent runs at mostly constant intervals (such as
every 20 minutes)
- Relatively short distance between stops (shorter than ordinary rail
services)
- Often special rolling stock, optimized for acceleration and quick boarding
- Services are commonly identified by a single ref which is applied to
all runs of that service (similar to tram/subway networks)
- Often integrated into urban fare system (same ticket as for buses,
trams, subway etc.)
[1] http://wiki.openstreetmap.org/wiki/Public_Transport
Michael
_______________________________________________
Talk-transit mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk-transit
