GTFS namespace key formatting

General talk Tagging general discussion
,
1

What format should keys within the GTFS namespace follow?

gtfs:$field:$feed=* (example: gtfs:stop_id:US-WA-KCM=29640)
or,
gtfs:$feed:$field=* (example: gtfs:US-WA-KCM:stop_id=29640)

Context notes:

  1. Existing ref-tagging generally follows a ref:$identifier:$field=*, as in ref:US-WA:SDOT:UNITID=*.
  2. Public transport stops are often served by multiple operators - meaning just gtfs:feed=$feed + gtfs:$field=* (example: gtfs:feed=US-WA-KCM + gtfs:stop_id=29640) is not always sufficient, and semicolon-delimited values are more difficult to edit and parse.
  3. The OSM Wiki: GTFS page says the feed should be a suffix, and that gtfs:feed=* is deprecated.

(Original discussion: Changeset: 174218415 with @Itserpol)

2

I think we should stick with option one, as described in the wiki. As can be seen in taginfo, this option is already widely used. I don’t see any reason to change it. Personally, I also find option one a bit more intuitive.

3

i.e. gtfs:$field:$feed=* (example: gtfs:stop_id:US-WA-KCM=29640) as described in the OSM Wiki: GTFS for GTFS ?

4

Yes, exactly. I probably should have been more specific.

1 Like