Agency endpoint down
The agency endpoint for, say, King County Metro seems broken.
http://api.pugetsound.onebusaway.org/api/where/agency/1.xml?key=TEST
There is no Action mapped for namespace /api/where/agency and action name 1.
Confirmed. Some work we introduced with agency metadata is conflicting with the agency namespace.
On Sat, Dec 5, 2015 at 11:08 PM, Joel Verhagen [email protected] wrote:
The agency http://developer.onebusaway.org/modules/onebusaway-application-modules/current/api/where/methods/agency.html endpoint for, say, King County Metro seems broken.
http://api.pugetsound.onebusaway.org/api/where/agency/1.xml?key=TEST
There is no Action mapped for namespace /api/where/agency and action name 1.
— Reply to this email directly or view it on GitHub https://github.com/OneBusAway/onebusaway-application-modules/issues/157.
Everything else seems ok -- this issue is specific to a single API.
On Sun, Dec 6, 2015 at 6:47 AM, Sheldon A. Brown [email protected] wrote:
Confirmed. Some work we introduced with agency metadata is conflicting with the agency namespace.
On Sat, Dec 5, 2015 at 11:08 PM, Joel Verhagen [email protected] wrote:
The agency http://developer.onebusaway.org/modules/onebusaway-application-modules/current/api/where/methods/agency.html endpoint for, say, King County Metro seems broken.
http://api.pugetsound.onebusaway.org/api/where/agency/1.xml?key=TEST
There is no Action mapped for namespace /api/where/agency and action name 1.
— Reply to this email directly or view it on GitHub https://github.com/OneBusAway/onebusaway-application-modules/issues/157 .
The URL in my original post works now. I've long since moved on to other projects but the URL seems fine now.