Item talk:Q23228
key name with ":" or "_"
@HaPe-CZ: Is the key with ":" or "_", railway:signal:distant:repeated:form or railway:signal:distant_repeated:form?
Like railway:signal:main_repeated:form (taginfo) and railway:signal:distant_repeated:deactivated (Item:Q23221)? --Chris2map (talk) 06:12, 15 November 2025 (UTC)
- @Chris2map:: Item
railway:signal:distant:repeated:formcreated on September 19, 2018, at 7:27 p.m. by Yurikbot. Following this example, I continued to create additional items for this object. But you're right, Yurikbot created the item incorrectly, and that's where the error comes from.
- ":" separates the properties of an item, e.g.,
cube:green - "_" replaces a space, e.g.,
cube_steel:green/railway:signal:distant_repeated:form
- This problem then concerns: Item:Q2619, Item:Q23221, Item:Q23228
- I don't know if it's possible to correct the item. Simply rewriting the item is not the correct procedure. In the definition of the item "permanent key identifier" - "the value should not be changed." A big problem is (will be) with integration into the editor itself. --HaPe-CZ (talk) 11:06, 15 November 2025 (UTC)
It was also obvious to me to seperate everything (every property) with ":". I think, the following was done with the scheme here:
4 key parts seperated by ":" → railway : signal : type of signal : property.
And they take "main_repeated" as a signal type, if it is followed by a (sub)property like ":form". So "...:main:repeated" is written as a property, but "...:main_repeated:..." is written as a signal type with further properties.
- taginfo statistics
| ":repeated" | ||
|---|---|---|
| uses | key | fix |
| 16 302 | railway:signal:distant:repeated | railway:signal:distant_repeated:something |
| 3 364 | railway:signal:crossing:repeated | railway:signal:crossing_repeated:something |
| 442 | railway:signal:crossing_info:repeated | incorrect entry, not used, it doesn't make sense |
| 325 | railway:signal:crossing_hint:repeated | incorrect entry, not used, it doesn't make sense |
| 139 | railway:signal:crossing_distant:repeated | railway:signal:crossing_distant_repeated:something (not expected but possible) |
| 88 | railway:signal:combined:repeated | railway:signal:combined_repeated:something |
| 23 | railway:signal:speed_limit_distant:repeated | incorrect entry, not used, it doesn't make sense |
| 22 | railway:signal:humping:repeated | railway:signal:humping_repeated:something (realy exist) |
| 21 | railway:signal:shunting:repeated | railway:signal:shunting_repeated:something (not expected but possible) |
| 13 | railway:signal:main:repeated | railway:signal:main_repeated:something |
| 12 | railway:signal:speed_limit:repeated | railway:signal:speed_limit_repeated:something (but in practice it is unclear, strange, vague usage) |
| 5 | railway:signal:repeated | signal type specification missing railway:signal:???_repeated:something |
| 4 | railway:signal:departure:repeated | railway:signal:departure_repeated:something (not expected but possible) |
| 3 | railway:signal:distant:repeated:form | railway:signal:distant_repeated:form |
| 3 | railway:signal:distant:repeated:height | railway:signal:distant_repeated:height |
| 2 | railway:signal:shunting_repeated:repeated | railway:signal:shunting_repeated:something |
| 1 | railway:signal:route_distant:repeated | railway:signal:route_distant_repeated (not expected but possible) |
| "_repeated" | ||
|---|---|---|
| uses | key | fix |
| 7 043 | railway:signal:main_repeated:form | Ok |
| 6 973 | railway:signal:main_repeated | Ok |
| 4 866 | railway:signal:main_repeated:states | Ok |
| 1 557 | railway:signal:main_repeated:substitute_signal | Ok |
| 315 | railway:signal:main_repeated:height | Ok |
| 105 | railway:signal:main_repeated:function | Ok |
| 92 | railway:signal:main_repeated:deactivated | Ok |
| 31 | railway:signal:main_repeated:caption | Ok |
| 6 | railway:signal:main_repeated:shape | Ok |
| 4 | railway:signal:shunting_repeated | not expected but possible |
| 4 | railway:signal:shunting_repeated:form | not expected but possible |
| 2 | railway:signal:shunting_repeated:height | not expected but possible |
| 2 | railway:signal:main:main_repeated | railway:signal:main_repeated:something |
| 2 | railway:signal:shunting_repeated:repeated | railway:signal:shunting_repeated:something |
| 1 | railway:signal:main_repeated:position | Ok |
So the keys with 4 ":" would have to be updated to "...:...:signal_type:..." to strictly follow the scheme above, if I got it right. --Chris2map (talk) 13:06, 15 November 2025 (UTC)
- The signals
railway:signal:main:somethingandrailway:signal:main_repeated:somethingare two signals, just asrailway:signal:distant:somethingandrailway:signal:distant_repeated:somethingare two signals. I have added my proposed corrections to the table. --HaPe-CZ (talk) 15:34, 15 November 2025 (UTC) - @Chris2map:: Do you have any thoughts on my comments? --HaPe-CZ (talk) 12:45, 16 November 2025 (UTC)
- Because I do not map railways I'm not common with the mapping and tagging of it and don't want to decide what is better or worse, or if a retagging is applicable. I was just wondering about the different key notations. – To your proposed keys: I struggle with e.g. "railway:signal:distant:repeated" -> "railway:signal:distant_repeated:something". In my understanding "railway:signal:distant:repeated" is the present key for a repeated distant signal; so it is synonymous to "railway:signal:distant_repeated". The additional properties are then tagged "railway:signal:distant_repeated:something" (what is a synonym for "railway:signal:distant:repeated:something"). – Following that, I would say ("form" can be replaced by any of the properties):
| variant | current | suggested | |
|---|---|---|---|
| A | railway:signal:main_repeated | = | railway:signal:main_repeated |
| railway:signal:main_repeated:form | = | railway:signal:main_repeated:form | |
| railway:signal:distant:repeated | → | railway:signal:distant_repeated 💥 | |
| railway:signal:distant:repeated:form | → | railway:signal:distant_repeated:form | |
| B | railway:signal:main_repeated | → | railway:signal:main:repeated 💥 |
| railway:signal:main_repeated:form | = | railway:signal:main_repeated:form | |
| railway:signal:distant:repeated | = | railway:signal:distant:repeated | |
| railway:signal:distant:repeated:form | → | railway:signal:distant_repeated:form |
- As said, I cannot overlook the consequences. I would use "railway:signal:distant_repeated:form" and so on. With the basic keys in wide use "railway:signal:main_repeated" and "railway:signal:distant:repeated" it would be important to involve the railway mapping community before do anything basic, IMHO. --Chris2map (talk) 15:14, 16 November 2025 (UTC)
- There are no synonyms here; the only correct option is "A." The only problem is the one you pointed out, which is:
- incorrectly:
railway:signal:distant:repeated:form - correctly:
railway:signal:distant_repeated:form
- incorrectly:
- This is how all signal descriptions should look.. Other cases (see tables above) are mostly errors made by editors.