Difference between revisions of "GTFS Explore Tool"

From TransitWiki
Jump to navigation Jump to search
(Created page with "{{infobox |title=GTFS Explore Tool |image= |vendor= James Wong [http://jameswong.org/ http://jameswong.org/] |license= Open Source |website=[https://github.com/jcwong86/GTFS_E...")
 
 
Line 18: Line 18:
 
*use of the gtfs_sql_importer (https://github.com/cbick/gtfs_SQL_importer)
 
*use of the gtfs_sql_importer (https://github.com/cbick/gtfs_SQL_importer)
 
*PostgreSQL 9.1 w/ PostGIS support enabled
 
*PostgreSQL 9.1 w/ PostGIS support enabled
*The batch importer also uses the excellent OneBusAway GTFS Transformer tool, which is licensed under the Apache 2 license and is checked in in the lib/ directory.
+
*The batch importer also uses the excellent OneBusAway GTFS Transformer tool, which is licensed under the [[Apache 2]] license and is checked in in the lib/ directory.
  
 
Limitations of the scripts:
 
Limitations of the scripts:

Latest revision as of 02:26, 30 January 2017

GTFS Explore Tool
Vendor James Wong http://jameswong.org/
License Open Source
Website https://github.com/ jcwong86/GTFS_Explore_Tool



"A postgres based analysis of transit service from a GTFS feed using TCQSM based methodologies and batch analysis tools.

This is a series of .sql scripts and R code designed to provide the user with information about the transit service described in a GTFS feed using methodologies from the Transit Capacity and Quality of Service Manual 2nd Ed (The project visiting the third editions is at http://tcqsm.org).

There is also a batch analysis element which will loop through the analysis of many agencies and return aggregate results which can be analyzed by the R code.

The postgres scripts rely on:

  • a properly formed GTFS feed
  • use of the gtfs_sql_importer (https://github.com/cbick/gtfs_SQL_importer)
  • PostgreSQL 9.1 w/ PostGIS support enabled
  • The batch importer also uses the excellent OneBusAway GTFS Transformer tool, which is licensed under the Apache 2 license and is checked in in the lib/ directory.

Limitations of the scripts:

  • Works when stops are coded individually, not with time-point only feeds
  • Requires use of shapes.txt file for any distance related functions
  • Does not currently work on files using frequency-based schedules."[1]

References