understanding the converter about gtfs2graphs

[daajoe]

Hi,
thanks!
Yes, you are absolutely right the repo misses a documentation.
I wrote one for a solver competition PACE 2016 transit feeds. It also contains a brief description about the converter parts.

• get_feeds.py : yes
• gtfs2graphs.py : yes. atm only dimacs/lp/gr/gml. note that gr and dimacs are integer based formats.
• gml_extract_types.py ... is deprecated (it was only used to split already available gml graphs with available agency/route type info)
• gmlgtf2slp.py : yes.
• run4allfeeds.sh : yes, but does it only for the gr format

Issue (non-identifiable IDs):

• this was a decision, because of a legal issue/unclarity. many transit feed providers don't use CC. making the data anonymous should avoid this for solver competitions.
• the option --print_symtab or --print_labels should allow you to output also the labels/symbol table for the integer based formats
• if you want to modify the output in the gml file graph_output.py:write_gml should have all the necessary data also for identifiable IDs

Configs:
The config file gtfs_into_conf.yml contains only info for the Berlin Metro region. It was only used to have a trivial mapping to cities.

The proper way to do a geo-location would probably be to take the lat/long data stored in the stops and run a geo-localization. The networkx graphs should already have the lat/long data (gtfs2graphs.py:L97). Google's geo-location is just a RESTful call, but the free plan is limited afaik to 1k calls each day (150k after registration).

[bonfirefan]

Thank you, the documentation is extremely helpful! I'll be continuing to work on this and will ask if I have further questions.