google/transitfeed

A Python library for reading, validating, and writing transit schedule information in the GTFS format.

⚠️ NOTE: This project is no longer actively maintained. For up-to-date GTFS validation tools, see the https://github.com/MobilityData/gtfs-validator project. ⚠️

transitfeed

Provides a library to help you parse, validate, and generate General Transit Feed Spec (GTFS) feed files. See INSTALL for installation instructions.

For the latest documentation, see:

https://github.com/google/transitfeed/wiki

For the latest release and downloads, see:

https://github.com/google/transitfeed/releases/latest

For general questions, send a message to the mailing list:

https://groups.google.com/forum/#!forum/transitfeed

transitfeed's Issues

Add additional metadata to the feed validator output

From [email protected] on September 10, 2007 14:09:35

It would be nice to have the feed validator add the following things to its output:

• Agency Name
• Stop/Route/Trip count
• Effective date range

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=34

Add validation for no service period defined

From [email protected] on April 22, 2007 19:37:26

Currently, if no service periods are defined, the feedvalidator doesn't
complain about that.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=8

Google Code skipped issue 18

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=18

calendar.txt with empty start_date and end_date

From [email protected] on February 06, 2008 18:23:27

An agency sent us a file with 8 <sp> characters for start_date and a tab
for end_date. validator from trunk didn't complain.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=41

Create hosted version of feedvalidator

From [email protected] on April 21, 2007 18:16:01

It would be great to have a web-based version of feedvalidator that would
make it ridiculously easy to check the integrity of a feed.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=5

feed validator should check line endings

From [email protected] on June 19, 2007 21:59:57

feedvalidator should complain if a feed has anything other than consistent
CR LF line endings or consistent LF line endings.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=27

Create standalone Windows executable for schedule_viewer

From [email protected] on April 21, 2007 18:09:27

schedule_viewer is really cool, so we should make it easier for people to
run by creating a Windows executable version.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=3

validator warn when short route names are too long

From [email protected] on May 04, 2007 09:48:42

Since Googles UI depends on the short route names being pretty short, maybe
flag a warning if the name is longer than, say, 6 chars?

If possible, flag a louder warning for 10+ chars?

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=21

Add service_id validation between trips.txt and calendar.txt

From [email protected] on April 25, 2007 13:13:34

Trips marked with a service_id that is non-existent in calendar.txt aren't
flagged as errors.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=13

schedule_viewer service period display and selection

From [email protected] on April 28, 2007 08:21:13

schedule_viewer should provide a way to browse service periods, display
them on a calendar and allow the user to select periods.

Currently the list of departure times is a little confusing because it
displays times in any service period instead of the service on a particular
day.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=17

Add a warning for stop codes embedded in stop_names

From [email protected] on March 27, 2008 10:07:20

Now that the spec offers a proper stop_code field, the validator should
warn if it seems like most stop names contain a stop code number.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=49

Google Code skipped issue 38

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=38

missing weekday column in calendar.txt can crash parsing/validation

From [email protected] on May 16, 2007 21:41:27

This is what the trace looks like:

Traceback (most recent call last):
  File "./feedvalidator.py", line 64, in ?
    loader.Load()
  File "/home/jhughes/gtdf/trunk/python/transitfeed.py", line 2271, in Load
    self._LoadCalendar()
  File "/home/jhughes/gtdf/trunk/python/transitfeed.py", line 2049, in
_LoadCalendar
    period = ServicePeriod(field_list=row)
  File "/home/jhughes/gtdf/trunk/python/transitfeed.py", line 1203, in init
    self.original_day_values += [value.strip()]
AttributeError: 'NoneType' object has no attribute 'strip'

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=23

When validating, ensure that each row has the same number of cells as the header

From [email protected] on December 27, 2007 10:35:17

Currently, the FeedValidator is lenient about the number of cells (that is, unquoted commas) in
each file.  This issue seems to occur frequently in new feeds, so it should be marked as an error
in the FeedValidator .

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=39

feedvalidator doesn't check some values

From [email protected] on May 02, 2007 13:10:34

It doesn't warn when day columns contain value not in ('0', '1')

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=20

Add validation comparing shape distance values in stop_times vs. shapes (if present)

From [email protected] on April 25, 2007 11:23:11

A point in a shape that has the same distance value as a stop time in a
trip should be at roughly the same point in space.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=11

Feed parsing doesn't deal with quoted values correctly when surrounded by spaces

From [email protected] on September 12, 2007 10:29:18

When a quoted value is preceded by an extra space, it isn't treated as quoted:

value1, "value2, more", value3

is parsed into 4 values.

However, without the space, the value is parsed correctly:

value1,"value2, more", value3

This is coming from the python csv libary; we need to see if there's a workaround or whether we
need to write our own CSV parsing to get around this.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=36

&quot;No module named marey_graph&quot; when running schedule_viewer from /usr/bin

From [email protected] on May 22, 2007 04:02:22

When trying to execute schedule_viewer.py under Fedora, no matter if I
execute after running setup.py, it always report an import error:

Traceback (most recent call last):
  File "/usr/bin/schedule_viewer.py", line 26, in ?
    import marey_graph
ImportError: No module named marey_graph What version of the product are you using? On what operating system? I am using transitfeed-1.0.7. My operating system is version 2.6.20-1.2944.fc6

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=24

Google Code skipped issue 14

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=14

feedvalidator should use arrival_secs and departure_secs when checking stop_times order

From [email protected] on April 02, 2008 11:45:15

Today AddStopTimeObject uses stoptime.GetTimeSecs(). Instead it should
check that previous.departure_secs <= current.arrival_secs

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=50

invalid utf8 crashes feedvalidator

From [email protected] on June 27, 2007 16:01:15

The sample feed Marcy sent Joe and I (off the list) included invalid UTF-8
which crashed the validator.

ERROR: 7 issues found
Traceback (most recent call last):
  File "/home/thecap/src/transitdatafeed-trunk/python/feedvalidator.py",
line 198, in ?
    output_file.write(problems.GetOutput(os.path.abspath(feed)))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u02c7' in
position 2541: ordinal not in range(128)

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=29

Group unused stop messages together in validator output.

From [email protected] on April 24, 2007 10:29:07

It would be nice to group (and limit) unused stop messages, since feeds
that have unused stops often have many unused stops, to the point where
they drown out other high-level issues.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=10

create standard python distribution

From [email protected] on April 21, 2007 21:05:25

http://docs.python.org/dist/dist.html After that is done we can add our code to the python index, cheeseshop.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=6

schedule viewer bottom panel not showing correctly in IE6 and FF3

From [email protected] on February 19, 2008 16:58:12

In IE6 the bottom panel doesn't display at all. In FF3 it appears to not
resize after drawing the marey graph, leaving the graph below the window
bottom until the browser window is resized.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=45

schedule_viewer: &quot;No such file or directory: &quot;

From [email protected] on May 01, 2007 16:31:38

If you run schedule_viewer from a different directory you get an error such as
IOError: [Errno 2] No such file or directory:
'schedule_viewer_files\index.html'

Work around is to change into install directory and run it there.

I should fix it to make an absolute path relative to file

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=19

improve memory performance of transitfeed.py

From [email protected] on June 28, 2007 03:23:39

processing feeds takes tons of memory and it seems to get worse with each
release. Internally we have some large GTFS files that won't load on a 2GB
machine.

We need to do some profiling to work out if we are doing something that
prevents python doing the right thing.

It might be worth trying to reload a medium sized feed several times. If we
delete the Schedule object each time then the python process should stop
growing.

Here's someone with debugging a possibly similar problem http://mail.python.org/pipermail/python-list/2007-June/445838.html but he didn't get a reply.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=30

Trip objects created without parameters don't have direction_id or block_id set

From [email protected] on April 22, 2007 19:35:55

What steps will reproduce the problem? 1. create a Trip using Trip()   # no parameters
2. add the Trip object to a Schedule
3. call schedule.WriteGoogleTransitFeed
4. you'll get exceptions that trip.direction_id and trip.block_id aren't
defined.

Once this is fixed, we can remove the gratuitous definitions of those
attributes from the TransitFeed sample code.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=7

Add more validation for StopTimes (arrival after departure, arrival/departure only)

From [email protected] on September 06, 2007 10:08:26

In GTFS stop times, the arrival and departure times should either both be specified or both be
empty. FeedValidator should check for this.  Also, there currently isn't a check for an arrival time
that occurs after the departure time, and there should be.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=33

FeedValidator should warn if the expiration date for the data is soon

From [email protected] on September 10, 2007 14:11:05

If the expiration date of the schedule in the feed is in the near future (say, 30 days), FeedValidator should give a warning

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=35

FeedValidator should provide informative message when given a UTF-16-encoded feed

From [email protected] on September 06, 2007 10:04:35

Currently FeedValidator throws an exception when given a feed whose files are encoded in UTF-
16.  It would be useful to display more informative output.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=32

Add check for too many CSV columns in input

From [email protected] on May 16, 2007 14:25:12

From the group:

"Greetings.  I wish I were able to suggest a fix however I can find a
possible bug.  My file validated (I ran it twice) and I pushed through
to FF.  He reported that there were too many columns and indeed there
were some ,,,, that were not returned as an error.  I can try to
recreate the datafile, if helpful, but I think you can get my drift."

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=22

Relax stop times sequence policy to strictly increasing integers.

From [email protected] on June 14, 2007 17:00:21

(On behalf of TomH)

In Trapeze, each actual stop pattern comes from (is a subset of) the master
pattern (the entirely of the master pattern may never be used in any actual
stop pattern). The sequence numbers come from the master pattern.

We should only detect a bad sequencing if a stop is missing for all trips
of a route.

An example,
A master pattern and sequencing.
stop_id     sequence
a              1
b              2
c              3
d              4

Applying the master pattern to a trip which only services b-c-d,
stop_id     sequence
b              2
c              3
d              4
will generate a sequence error.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=26

Trip with no stop times message prints trip ID as u'id', which could be confusing

From [email protected] on April 24, 2007 10:13:46

We should avoid using repr() in validation output, since the unicode
designator will be confusing to users unaccustomed to Python's string
representation.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=9

possible to output route without agency_id

From [email protected] on March 19, 2008 18:06:24

According to the spec, if routes.txt includes an agency_id column all rows
must have a value. Ideally Route.GetFieldValuesTuple would use the
schedule's default route if self.route_id is None and there would be a way
to totally omit the column if only one agency is in the schedule.
The easiest fix is to make agency_id required when creating a Route object
and populate it with the default agency in the loader when loading
routes.txt. I don't like adding things so that transitfeed loading and
writing a feed modifies its content.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=47

Invalid route_color string causes stack dump

From [email protected] on December 28, 2007 13:27:21

We need to add validation to ColorLuminance or things that call it.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=40

Add a warning for unknown columns in the validator

From [email protected] on February 12, 2008 13:28:00

Unknown columns in feed files are ignored by parsers (to allow for future
extension), but we've seen occasional problems due to mislabeled optional
columns.  Providing an informative warning in those cases would make them
easier to discover.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=42

Add shape display to Schedule Viewer

From [email protected] on April 25, 2007 11:24:26

Currently, Schedule Viewer doesn't display shapes for trips if they're
present, making it more difficult to evaluate/debug shape data

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=12

check for html in text fields

From [email protected] on June 20, 2007 09:44:28

feeds should never contain html or html escape entities (&amp; for example).

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=28

Google Code skipped issue 1

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=1

Google Code skipped issue 44

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=44

Google Code skipped issue 15

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=15

Check stop <--> shape point distance in validator

From [email protected] on February 12, 2008 13:29:34

Some GTFS users (such as Google Maps) will ignore shapes attached to a trip
if the stops aren't close enough to points on the shape.  It would be nice
to catch that condition in the validator and generate a warning.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=43

Create HTML output for feedvalidator

From [email protected] on April 21, 2007 18:11:22

feedvalidator can generate a lot of useful information, but its plain text
output is an eyesore.  It should be able to generate an easier-to-read HTML
file as output.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=4

Google Code skipped issue 2

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=2

Transitfeed should understand &amp; validate full stop_times information

From [email protected] on April 26, 2007 10:56:29

Currently, the transitfeed module uses a simplified representation of
stop_times information--currently, a single time and a stop.  The pickup &
dropoff info, shape distance, etc. aren't handled yet.  This is the last
major hole in transitfeed's coverage.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=16

Clarify warning text for no rows in calendar.txt that don't define service days

From [email protected] on May 31, 2007 10:25:17

Currently, the warning text isn't clear when a row in calendar.txt doesn't
have service days (because all service is defined in calendar_dates.txt).
The gist of it is that the row isn't needed.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=25

Support stop_code in transitfeed

From [email protected] on March 27, 2008 10:06:17

We need to change the library to support the stop_code field that was
recently added to the official spec, and possibly add relevant validation.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=48

Color contrast issue in FeedValidator should be a warning, not an error.

From [email protected] on March 19, 2008 16:51:41

Also, the text of the issue description should be properly spaced so that
it doesn't run together when displayed in HTML.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=46

transitfeed installed as an egg can interfere with tests

From [email protected] on September 15, 2007 19:57:31

Even though test/testexamples.py sets PYTHONPATH='.' the examples may be
run with a different older version of transitfeed.py if it is installed on
the system in an egg. You can see the problem by editing an example script
to print sys.path. As a work-around I tried running the examples as
python -c'import
sys;sys.path.insert(0,".");exec("example/feedvalidator.py")' other args but
couldn't get the quoting to work in windows. cmd.exe is not my friend.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=37

validate stop_headsign and trip_headsign are consistent

From [email protected] on August 19, 2007 12:08:04

The spec is not very clear and the validator doesn't check. I don't think
it is intentional. We need to fix both.

Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=31