so in the last week ive seen a number of errors sporadically popping up

GetDeparturesByStop
the output has changed because im getting data but something is different because my app is broken on certain stops
but on some stops it works fine
basically any stop that the 22 13 or 7 go past is broken
but the parts along green st where only the 5 goes are fine
did you change the routenames? because that could definitely cause the error im seeing
what is this field that was changed that was mentioned the other day???????

GetStopTimesByStop
is returning empty arrays on all the stops ive tried

these errors started showing up before the switch over to the summer schedule but are way more frequent now

please update us on any changes made

darkery: Do you know what field in GetDeparturesByStop is breaking your app? We did just go into summer service so some of the trips, etc. have changed but the structure of the response should definitely not have changed. It is totally possible that information in the route object (e.g. route_long_name, route_short_name, etc.) could change and your app should allow for that. That being said, I don't think any route information changed with the summer service update.

The field that was changed the other day that was breaking the API is not a field we share through the API directly, but something on the back-end. Regardless, that change has been reverted and things should be exactly the same as they have always been.

Maurice:
Can you post an example of a request and response that is giving you null values? Is it on GetDeparturesByStop or GetStopTimesByStop? I'm looking through some requests and things seem to be working fine.



Thanks both of you for helping us track down these issues.

Ryan

GetStopTimesByStop should be working as expected in both v2.0 and v2.1. I'm guessing that your issues with GetDeparturesByStop probably had to do with the summer service change and should be resolved now. If you see them again definitely let us know.

it is doing it (giving a bunch of nulls) again right now
here is an offender:
{"stop_id":"LSE:8","headsign":"10W GoldHOPPER","route":{"route_color":"c5972e","route_id":"GOLDHOPPER","route_long_name":"Goldhopper","route_short_name":"10","route_text_color":"000000"},"trip":{"trip_id":null,"trip_headsign":null,"route_id":null,"block_id":null,"direction":null,"service_id":null,"shape_id":null},"vehicle_id":"1168","origin":{"stop_id":"LSE:8"},"destination":{"stop_id":"E14:2"},"is_monitored":true,"is_scheduled":true,"scheduled":"2012-05-29T14:10:00-05:00","expected":"2012-05-29T14:15:46-05:00","expected_mins":10,"location":{"lat":40.112797,"lon":-88.222833}}

edit: it looks like every trip for bus 1168 is filled with nulls today but other golds are fine. this is what happened before, one bus(or trip)'s unexpected nulls bring my code to a stop. if i cant get the trip direction the data is useless.

Edited by user Tuesday, May 29, 2012 6:13:00 PM(UTC)  | Reason: Not specified