trips-for-route includes trips for other routes

[hampelm]

The trips-for-route endpoint currently includes trips for routes other than the ID specified. For example, if you request trips for route A, you will get those trips and possibly also trips for routes B, C, etc. This is noted in a 2012 email on the mailing list. It's not clear why the additional routes are included. The expected behavior is for trips-for-route to only show trips for the specified route.

If the problem cannot be resolved completely, a flag to exclude extraneous routes would also solve the issue without breaking existing apps. In any case, the current behavior should be in the API documentation.

[kurtraschke]

Clarifying from the thread linked above, this is not a bug, but intended behavior for trips-for-route; the returned trips which are not on the requested route are linked by block ID to trips on the requested route.