Trip ID is included in the RESTful service

[David Zhong (MARTA)]

We have updated our BRD RESTful service and GTFS. The updated RESTful service has the TRIP_ID included, and the TRIP_ID in the real time feed matches with the TRIP_ID in the GTFS.

Please make sure to download the new version of GTFS from MARTA’s web site http://www.itsmarta.com/marta-developer-resources.aspx, before using the TRIP_ID in the RESTful service. 

[Landon Reed]

This is great news!  Thanks, David.

One sidenote: in the updated GTFS file the latlngs in the shape entities have only two decimal places of precision whereas older copies have up to six decimal places.  It seems like the new shapes must have been truncated.  Could you re-export the GTFS with the more accurate 'shapes.txt'?

Also, I (and some others I've been talking to) are getting some strange results when running the GTFS feed through a validator (http://code.google.com/p/googletransitdatafeed/wiki/FeedValidator).

[Landon Reed]

Oops, my post got cut short.  But what I meant to say is that a general re-export from MARTA might be necessary to fix these strange errors that we're getting.

Thanks,
Landon

[David Zhong (MARTA)]

Hi Landon,

We re-exported the shape.txt with correct decimals. 

Thank you for catching this issue.

David

[Landon Reed]

Hi David,

Digging into the GTFS a little farther we're finding some other errors as well.  We'll start documenting here so that you can try to find the source upstream:

routes.txt

• service_id - 54 instances of unknown value of '11' and 26 instances of value '12'

trips.txt

• direction_id - 'Northbound' and other strings are not valid values for direction_id; here you need either 0 or 1
• We think there may be some trips missing here that are referenced in 'stop_times.txt', one example being trip 3679748 among others that we expect.

Field headings - should be all lowercase.  Currently, stop_times.txt and trips.txt have uppercase headings

stop_times.txt

• stop_id - this field is currently referencing stop_code from 'stops.txt' incorrectly.  It should (per the GTFS reference) refer to the stop_id field in the 'stops.txt' file.  Past MARTA GTFS feeds have done this as well.

This is all we have for now.  We'll let you know if we find anything else that seems off.  Just as a reference, the website I mentioned earlier (http://code.google.com/p/googletransitdatafeed/wiki/FeedValidator) has a pretty solid tool for validating GTFS feeds.

Thanks,

Landon

[David Zhong (MARTA)]

Thanks Landon. I will look into it and get it updated as quick as possible.

[Quentin Zervaas]

I was just about to post this as well. In some instances the stop_id field has correctly been used in stop_times.txt (you can see this by the 3 digit "old" stop IDs), but in other instances it's using stop code

[Kenny Chapman]

I believe all trips for the Gold Line, route_id = 7731, are missing from the trips table.

[David Zhong (MARTA)]

Hi Landon,

The GTFS has been updated and validated by the feed FeedValidator. Please go to MARTA web site to download it.

Thank you

David

[Candace Brakewood]

Hi David-

Thank you very much for your help with the TripIDs - this is very exciting!  

Some of us are wondering if there has been any discussion within MARTA about releasing a real-time train feed.  We would really like to begin working with train data, if that is possible.

Thanks again for all of your help!

-Candace

--
You received this message because you are subscribed to the Google Groups "atl-transit-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atl-transit-devel...@googlegroups.com.
To post to this group, send email to atl-transit...@googlegroups.com.
Visit this group at http://groups.google.com/group/atl-transit-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Candace Brakewood 

803.727.3317 | cbrak...@gmail.com

PhD Student  | Georgia Institute of Technology