Add more station information

iRail / stations

A list of all the Belgian stations and their properties used within the iRail project

http://irail.be/stations/NMBS

29 stars 20 forks source link

Add more station information #115

Closed Bertware closed 6 years ago

Bertware commented 7 years ago

Include more detailed information about stations. Data source (example): http://www.belgianrail.be/nl/stations-en-trein/zoek-een-station/1/brussel-zuid.aspx

To be scraped:

[x] Address
[x] Accessibility (high platforms, elevator, escalators)
[x] Connections to other transportation (bus/tram/metro)
[x] Bicycle parking space
[x] ~~Key card stations (preferably stored by id)~~
[x] Optional: luggage storage

To-do:

[x] Write scraper
[x] Scrape all data mentioned above
[x] Store data in stations.csv

Bertware commented 7 years ago

How should stations reachable by key-card be included? I'd prefer by some id, but there's a choice between URI, hafas id (e.g. 8895000) and the iRail id (008895000). For most stations, more than 10 other stations can be reached. Therefore, it seems like the URI might be too long? (It'd add quite some overhead, while it could just be calculated for those who need it?) Another option would be to use id:name pairs, so developers who just need the name don't have to look up the id's. Which one would be best?

@pietercolpaert

pietercolpaert commented 7 years ago

In GTFS, that’s the fare zones you would define. See the documentation over here: https://developers.google.com/transit/gtfs/reference/fare_rules-file

As most of our traffic is gzipped anyway, I would not worry too much about the overhead of a prefix in an identifier. I’d rather be consistent that save a couple of bytes.