Opened 18 months ago
Closed 9 months ago
#23251 closed defect (fixed)
Crossing preset: Change label for crossing_ref
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | 24.08 |
| Component: | Internal preset | Version: | |
| Keywords: | template_report | Cc: |
Description ¶
In preset "Highways/Waypoints/Pedestrian crossing", the form field that corresponds to crossing_ref is labelled "Crossing type name (UK)". This is misleading. According to Taginfo, only 4% of uses of this key are in the UK (source: compare 1 and 2). The tag is widely used in France and Germany, among others.
A good label might be "Local name for crossing type".
Relevant forum discussion: https://community.openstreetmap.org/t/whats-up-with-the-crossing-ref-tag/105293
Revision:18822 Build-Date:2023-08-30 11:52:18 Identification: JOSM/1.5 (18822 en_GB) Mac OS X 12.6.3
Change History (11)
comment:1 by , 18 months ago
| Milestone: | → 24.05 |
|---|
comment:2 by , 18 months ago
Thank you for looking at this.
The approved proposal from 2008 says crossing_ref is "the traditional, region-specific reference, such as zebra or pelican". There is no mention of the UK in the key definition, only for some of the tags (e.g. pelican, toucan).
To be honest I think the UK bit in the JOSM label was only ever a misunderstanding from an English speaker, maybe an American or a Brit, who was under the false impression that referring to crossings as zebra crossings is somehow a uniquely British thing, when they have been known as Zebrastreifen in Germany for as long as they have existed (since the 1950s), and probably in other countries too.
But I understand your argument about letting the discussion settle before making changes to a 15 year old label. I'll report back here if there is anything else to add :-)
comment:3 by , 15 months ago
See also this recent discussion in German and #23290 which introduced a warning.
comment:4 by , 13 months ago
And another thread. Changing it to crossing=zebra should not be the goal.
Usually the wiki reflects the current usage without considering the approved or intended meaning (which I find problematic but that is life). Why do we make an exception here?
comment:7 by , 10 months ago
| Component: | Core → Internal preset |
|---|
comment:10 by , 9 months ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Looking at the wiki page history, I am strongly disinclined to make changes right now. Part of the problem is that we've had the same definition in JOSM for close to a 15 years (see #2135/r1374).
TBH, I'd rather see it deprecated. With that said, I'll give the wiki page some time to stabilize before I make a decision. I like to see the wiki not have changing tag definitions. I usually give changes to the wiki ~6 months with no changes to the meaning of the tag before I consider it to be stable.