Changeset: 142719567
Add TfGM route codes
Closed by tadintune
Tags
changesets_count | 4 |
---|---|
created_by | iD 2.27.1 |
host | https://www.openstreetmap.org/edit |
imagery_used | OpenStreetMap (Standard) |
locale | en-GB |
Discussion
-
Comment from user_5359
Welcome to OSM! Please look at https://www.openstreetmap.org/way/1216279313 again (one of eight hundert two ways). Your change comment suggests that you have confused the meaning of a reference abbreviation and the name. If tfgm is not a language code but the operator, then the reference code CCL should be noted as ref:tfgm.
Please also look at the different spellings of the second key https://taginfo.osm.org/search?q=tfgm#keys. Regardless of which spelling you choose: What does a direction have to do with a name? -
Comment from tadintune
TfGM is the operator but these are route codes that are specific to TfGM and separate from the route name. For instance the route "Airport Line" as known by the public is made of the TfGM route codes "CCL", "EYL", "APL", et al.. These codes have specific meanings to TfGM. The full name of a route code is, for example, "APL_IN" or "APL_OUT" but the route code "APL" covers all lines, crossovers and sidings attached to that route. Having the direction part of the name as a different tag makes it easier to split out the three datasets. The different spellings of TfGM:direction are a mistake and will be fixed. If it really offends you that much let me know and I'll move the data to an offline server and remove this information from the public osm maps.
-
Comment from user_5359
For the operator it may be a name, but according to the actual definition it is a reference designation. So I recommend the key ref:<operator> or better ref:<country code>: <operator> (ref:GB:tfgm). Since there seems to be also the possibility of in and out classification I rather recommend a name:tfgm_direction=both instead of name:tfgm_direction2. If this causes problems when searching, a key ref:GB:tfgm:in and ref:GB:tfgm:out (with yes / no value) would be worth considering as an alternative.
I have nothing against the entry of such operator-specific information, only such keys can also be easily mapped by other OSM users. Also a corresponding wiki entry for this would be recommendable.
I guess also the key tfgmcitycentre belongs to the project? Wouldn't it then also make sense to adapt the notation accordingly?
Since you work with the (beginner) editor iD, I could help you with the agreed changes, if it's okay with you. -
Comment from tadintune
Hi user_5359,
1. The direction 2 field is redundant - it was for bidirectional track and should have been removed (it's handled differently in our database).
2. I have no objections to how tags are named, as references or names or any other naming schema. If you think that the data would be tagged better then please feel free to fix my edits. I was after the line data for a TfGM project - adding safety systems to trams.
3. The key "tfgmcitycentre" is nothing to do with me - I have no idea what it refers to.
Thanks for your input. I am supposed to be writing software for safety systems on trams and I have only had time to scratch the surface of OSM. I introduced new tags to avoid breaking any existing data. If there is a better/standardised means of tagging this data I am happy to comply. We've extracted the route information and that will be checked/amended following further surveys.
- 1216279313, v1
- 1216279314, v1
- 1216279315, v1
- 3663332, v48
- 4947735, v43
- 22961311, v37
- 22961313, v30
- 22961316, v25
- Metrolink (22961321), v33
- 22961327, v42
- 22961342, v20
- 22961347, v22
- Metrolink (40609959), v14
- 75636670, v6
- 135930401, v16
- 135976460, v14
- 135976461, v19
- 204921062, v14
- Metrolink (205196843), v8
- 296954734, v8
Relations (10)
- Metrolink: Ashton-under-Lyne => Eccles (64307), v135
- Metrolink: Bury => Altrincham via Shudehill (65667), v92
- Metrolink: Shaw & Crompton => East Didsbury via Exchange Square (5861742), v42
- Metrolink: MediaCityUK => Ashton-under-Lyne (5861755), v35
- Metrolink: Rochdale => East Didsbury via Exchange Square (9332228), v29
- Metrolink: Ashton-under-Lyne => MediaCityUK (9427381), v16
- Metrolink: Bury => Piccadilly (9446632), v20
- Metrolink: Eccles => Ashton-under-Lyne (10326845), v23
- Metrolink: Ashton-under-Lyne => Eccles via MediaCityUK (10326849), v18
- Metrolink: Eccles => Ashton-under-Lyne via MediaCityUK (10326850), v20
Nodes (3)
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |