PR #282: Update stop_name Best Practices

14 views
Skip to first unread message

scott

unread,
Aug 26, 2021, 12:44:37 PMAug 26
to GTFS Changes
Hi all,

PR #282 has just been opened following conversations in #273 and #281 to disambiguate the current `stop_name` description.

The current description reads:
> Name of the location. Use a name that people will understand in the local and tourist vernacular.

"local and tourist vernacular" is confusing.

The proposed update is:
> Name of the location. The `stop_name` should match the agency's rider-facing name for the location as printed on a timetable, published online, or represented on signage. For translations into other languages, use `translations.txt`.

Looking forward to feedback. Thanks!
Scott

scott

unread,
Sep 3, 2021, 9:00:33 AMSep 3
to GTFS Changes
Hi everyone, 

The above contents have been put to a vote at #282.

Voting ends on 2021-09-10 at 23:59:59 UTC.

Thanks!
Reply all
Reply to author
Forward
0 new messages