"Once that happens, perhaps the critical mass will be reached and
agencies at that time will have no choice but to join or be left
behind."
(from a post in late May)

It's nice to see so many people want Google to add their local transit
agency, but I'd like to provide a little reality check regarding what
that means for smaller agencies.

Google does not add transit agency data; transit agencies compile
their data and make it available to Google.  If an agency does not
have a scheduling database or other software with export capabilities
and keeps their schedules in spreadsheets or on pieces of paper, this
means literally writing the GTFS line-by-line!  And proofreading/
troubleshooting it line-by-line!  And maintaining it line-by-line!  If
that transit agency also has only one tech person on staff to handle
all of the office hardware and software and on-bus hardware and
software, I hope you can see why Google Transit is a lovely idea, but
unlikely to happen for that agency.

It's not that transit agencies are digging in their heels and refusing
to join, as suggested by that post in late May.  I think that a lot of
agencies would love to join.  The issue is that building and
maintaining the GTFS is a burden and we don't have the resources to
carry it.

So, this is my challenge to Google and to all of you transit buffs out
there:  build us a very cheap or free database or other software that
will maintain schedule data and export to GTFS.  There are products
out there on the market, but they cost an arm, a leg, and your
firstborn.  There is huge market potential for someone to build an
excellent product, sneak into the market, and grab up all of the
smaller customers that wouldn't touch one of the big companies (and
vice versa).

Thanks for reading.  Best wishes to everyone in the transit & Google
communities.

Nicole Tedesco
Service & Operations Analyst
TCAT
Tompkins County, NY