You cannot post messages because only members can post, and you are not currently a member.
Description:
This group is the official venue for discussing upcoming changes to the Google Transit Feed Specification. Discussion is open to current users of the feed specification.
|
|
|
Exact change required?
|
| |
Most properties require exact change these days, but some will still give change. Is there any way to specify "exact change" in the spec? My agency requires exact change, but GO Transit, which also serves our area, does not.
|
|
|
review draft: December 30, 2009
|
| |
We've accumulated several minor issues since the last spec update this past March, so Naomi Bilodeau and I drafted an update to roll them all up before the end of the decade. I've attached the draft spec update for your consideration--please take a look and reply with any comments before the end of January 8, 2010 UTC.... more »
|
|
|
Layered Restructure Proposal
|
| |
I'd like to propose some changes to the GTFS specification to open up some flexibility and create a clearer organization of the data. Such changes would certainly prove valuable in my application of the data, but I'd like to see what the thoughts here are. Unfortunately these changes highly break backward compatibility, but... more »
|
|
|
Wheelchair accessibility
|
| |
I am pleased to announce that Open Trip Planner ([link]) now implements the wheelchair accessibility proposal from: [link] Brian Ferris and I added the feature last week, and have tested it with dummy data. We did not implement accessible-with-notes.... more »
|
|
|
Service Variations
|
| |
One of the issues that can be an issue for our clients is when the
client has a complex set of variations to standard service. These
variations include school variations (Exclusion - ie Open/Closed), day
of week variations, and special event variations. These change the
service levels on a day to day basis depending on what is running or... more »
|
|
|
accessibility: agencies, what data do you have on hand?
|
| |
This is a follow-on to our previous discussion on wheelchair
accessibility:
[link]
I wanted to ask some of the agency folks who were interested in
supporting accessibility extensions in GTFS: what accessibility-
related information do you already have in your databases above and... more »
|
|
|
Stop Amenities
|
| |
Hi all,
We are now using the stop amenities, stop_features.txt, file in our data.
We have found it necessary to change some of the naming tags.
I will give just a few quick examples and follow up with a more complete
list soon.
There are three: vending machine, ticket vending machine and food vending... more »
|
|
|
removing PublicFeeds wiki page in favor of gtfs-data-exchange.com
|
| |
Joe Hughes previously started a thread about the general topic of more
community ownership and participation in GTFS governance. One step of
that was removing the existing PublicFeeds index page which is no
longer 100% comprehensive of all public gtfs data available. (this is
also a desired step to help reduce confusion about what constitutes a... more »
|
|
|
add multi-agency support to transfers.txt
|
| |
I'm resurrecting this proposal because now that Google Transit is
becoming more regional, transfers between regional services operated
by different coordinated entities are becoming important in trip
planning. In some areas, local agencies could work together to submit
their routes in the same feed and satisfy current GTFS requirements... more »
|
|
|
|
