On the "change route to" issue..

GTFS headsign

On the "change route to" issue..

Based on how Google Transit handles this data (per the GTFS), it would be very confusing to the reader to see that, especially when the Google presentation is actually launched. Let's use this as an example:

First, review the example maps at:
http://code.google.com/transit/spec/transit_feed_specification.html#transitTripHeadsignScreenshot

I am boarding at Adams & Crenshaw, I want to go to Adams & Faifax. This is a trip that would be on the 37. However, in MTA scheduling, that is Line 14 (Route 37). The way the data is configured right now, it appears that the short route number that would appear on the map would be '14', even though I am clearly on the '37'. The trip plan will say "Bus 14 - Metro Local - Destination: Change to Route 37 ADAMS-LA BREA". I just think it will be less confusing to the user of Google Transit to see the routes displayed that way. Plus, for those who are writing apps, especially those who are writing apps that can be adapted to multiple cities, it would mean having to write a lot less exceptions for Los Angeles.

Just my ¥100 on why I think that we need to split the interlines for the purpose of Google Transit. (*^u^*)

=m