MTD Developer Forum
»
API
»
General Discussion
»
Issues Parsing getStops XML response
Rank: Newbie
Groups: Registered
Joined: 12/16/2011(UTC) Posts: 2
|
I'm developing an application for the app challenge and encountered some odd behavior with the getStops method XML response. It appears the following entry doesn't contain any valid point(s) or a stop code:
<stop stop_id="SMRSGSWTCHGRS" stop_name="Summersage and Switchgrass"><points/></stop>
I can work around this issue my making the field optional, but I don't think it should be returned since it doesn't have a valid point element. Is this normal? If so, would it be possible to include a DTD document for each XML response on the website? Trying to build objects to parse and store the XML doesn't work very well if elements are missing. Thanks in advance for any help you can provide.
|
|
|
|
Rank: Administration
Groups: Administrators, Registered Joined: 6/1/2011(UTC) Posts: 88 Location: Urbana Thanks: 1 times Was thanked: 6 time(s) in 6 post(s)
|
Sorry for the late response; usually we get an email when there is a new forum post, but for some reason we did not on this post.
Anyway, thank's for bringing this issue to our attention. You are absolutely right that there shouldn't be any stops that are returned without any stop points. It appears that there was a small typo in the GTFS feed (which is where this data comes from) which caused this parent stop to not match up to the child stop. We'll need to talk to our planner to get it resolved, but I would expect a fix early Monday.
Thank's again for bringing this to our attention and thank's for participating in the App Challenge!
|
|
|
|
Rank: Administration
Groups: Administrators, Registered Joined: 6/1/2011(UTC) Posts: 88 Location: Urbana Thanks: 1 times Was thanked: 6 time(s) in 6 post(s)
|
The issue should now be resolved. Please feel free to let us know if you have any other problems.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/10/2011(UTC) Posts: 34
Thanks: 1 times
|
I’m still seeing this issue, with the same stop but with the JSON output.
|
|
|
|
Rank: Administration
Groups: Administrators, Registered Joined: 6/1/2011(UTC) Posts: 88 Location: Urbana Thanks: 1 times Was thanked: 6 time(s) in 6 post(s)
|
This is a little embarrassing... We definitely had this fixed, but we just imported new data for spring service and it seems to have managed to crop up again. It should be fixed again (hopefully for the last time). Thank's for alerting us to the issue. Edited by user Thursday, December 22, 2011 9:03:08 AM(UTC)
| Reason: Not specified
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/10/2011(UTC) Posts: 34
Thanks: 1 times
|
|
|
|
|
MTD Developer Forum
»
API
»
General Discussion
»
Issues Parsing getStops XML response
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.