I wanted to check in on the state of implementations of this proposal,
to see whether it's ready for inclusion in the spec. On the data
publisher side, the Caltrain public feed includes this field:
http://www.caltrain.com/google_transit_feed/
Now I'd like to get confirmation from one or more application authors
that they're using this field in their app and that it's working as
expected. I've CC'd the authors of a few third-party Caltrain
applications on this thread to see who's using this info.
Here's an updated version of the proposal to clarify some ambiguities
in the last draft:
Proposal:
A new trip_short_name field would be added to trips.txt, with a
description as follows:
--------------------------------
trip_short_name (optional):
For individual trips that have a short rider-facing name in schedules
and station signage (for instance, commuter rail train numbers), this
field provides that name. If riders do not commonly identify trips by
name, please leave this field blank. A trip_short_name value, if
provided, should uniquely identify a trip within a service day; it
should not be used for destination names or limited/express
designations.
---------------------------------
Thanks,
Joe
sorry for a slow follow up.
I think this is a good proposal and that it's ready for inclusion in
the spec. I have started including this field in the feeds I publish
(LIRR and VRE so far),
some of which are being used by Yuri Yakimenko on trainlogic.net
(including the trip_short_name)
--
Jehiah