Metro-North trip_headsign suggestion

[Sunny]

I think Metro-North should remove the train's destination from the
"trip_headsign" and just leave the destination, which the user would
see on the departure board/hear on the announcements. To the majority
of riders, the origination of a train isn't important, just that it
serves both their origin and destination stations.

What do you think?

[John L]

Think you meant origin.

The origin was kept to conform to a traditional headsign, however we only use destination on any of our signs.

The thought was a different display medium so if you planned a trip with multiple connections, the origin may give added value.

It is really there for riders not familiar with the system, international and national.

It would reduce the size of the file so it is something to consider.

[Sunny]

I previously proposed this idea to the LIRR, and as you can see, it was implemented. I personally find it confusing in Google Maps clicking on a station (say Westport) and seeing "New Haven Grand Central Terminal - New Haven" and "New Haven New Haven - Grand Central Terminal". For someone completely unfamiliar with Metro-North it would only add confusion, in my opinion.

[John L]

Is a fair compromise "to New Haven State St" removing the origin and adding "to" as this is a headsign and not a destination indicator?

 

Anyone else have a comment?

 

I would have to pass this by our Customer Service Department

[Sunny]

That's fine with me.

[Brian Ferris]

I would leave the "to" out of the headsign value.  Most GTFS feeds that I've seen do not include words like "to" or "towards" in their headsign values, but instead stick to the plain destination name.

That said, I'm definitely all for removing the origin name from the trip headsign as well.

Thanks,

Brian

[Sunny]

Is there an ETA on this, seeing that it is not in the new schedule change?

[Sunny]

Any updates? Another schedule change has come and gone.