Transit Index API

[abyrd]

This API is half-finished and needs to be expanded.

[abyrd]

The lack of certain index API endpoints is holding back OTP client development and confusing a lot of people. It would be best to get at least minimal implementations in place and adapt the main client to use them.

[barbeau]

+1 - We've started stubbing out a few items ourselves since its blocking some of our client when using the OTP master branch backend (though unfortunately I don't think we have anything significant to contribute yet), but it would be great to see this officially fleshed out.

[aguiraf]

Tried a first implementation, just for avoiding errors and also useful for testing the new API features. some notes:

• I started working on a new file, IndexApi.js, then progressively changed all references from TransitIndex to IndexApi; don't know if it's ok or is better to refactor the old code.
• some calls were trivial to adapt ( agencies, routes, ...);
• other required some hack to accommodate ( stop times, stops in pattern);
• some other will need enhancements to the API ( e.g. findStopByName);

Old api was tighten up to the web widgets, providing buckets of info needed each time. Indeed I prefer the new RESTFull approach, general purpose, more standard; We should work on both sides (web client and server API) to fulfill all features needed, but pheraps modifications to the API will wait for the major GTFS rework. @abyrd, what do you think?

[steveathon]

Is anyone actively working on the index API at the moment?

[abyrd]

This API is now widely used and definitely "expanded". If anything it has too many unmaintained or experimental endpoints. Closing this issue.