Crossing and Cycleway Refactoring Notes

[tordans]

While working on #1201 – which is now merged (but not released at this time) – I wrote down a few follow ups that I want to look into as soon as I find the time.

I did not work on them in #1201 to keep the scope on a refactoring and cleanup of what we have.

They are not all thinks that we should to … but thinks I wanted to look into. To give them a bit more visibility I move them from the PR description here so we can reference when things are being worked on …

---

segregated for cycleways

• 🟢 resolved for crossings https://github.com/openstreetmap/id-tagging-schema/pull/1201/files#diff-c4d82f94ab6f12c4a01ad5b61483785731cd878f7034c3f6b8233247f6942c47R5
• 🏗️ for cycleway+foot in Add presets for highway=path-based cycle-footway tagging #1384
• Related issues Preset for a way designated for both cyclists and pedestrians, without separate spaces (segregated=no) #317 (comment), Preset for a way designated for both cyclists and pedestrians, with separate spaces (segregated=yes) #871

---

bicycle_foot versions

• 🏗️ in Add presets for highway=path-based cycle-footway tagging #1384
• 🟠 the idea from Treat presets with locationSet.exclude as unsearchable presets with low score instead of hiding them #1205 to make highway=cycleway+foot=designated visible in those country that don't promote it but the tagging still might be used

---

crossing:signal field

• 🏗️ in Add crossing:signals field to crossing/*traffic_signals presets #1203
• Related, closed PR Refactor crossing presets #1044

---

kerb:left/kerb:right field

• ⚫ discarded solution fields/kerb: Make directionalCombo to allow optional left/right tagging #1206 (comment)
• 👁️ maybe something we can look into with Proposal to add field groups in presets (How to start iterating on more detailed OSM data) #1202

---

traffic_island preset

• 🏗️ 🟠 add presets for cycleway=traffic_island #1068 need to be restarted after Crossing refactoring #1201

---

crossing=informal preset

We have presets for some of the ways, but not for the crossings. However, SC does use the tag.

• https://github.com/search?q=repo%3Aopenstreetmap%2Fid-tagging-schema+informal+path%3A%2F%5Edata%5C%2F%2F&type=code
• https://github.com/search?q=repo%3Astreetcomplete%2FStreetComplete+informal&type=code

Notes

• Make it unsearchable (at first)
• Don't add it to the translated field-list in order to keep this focussed on the tree main types

---

crossing=no preset

• Related Issue crossing=no support #548

Notes

• Make it unsearchable (at first)
• Don't add it to the translated field-list in order to keep this focussed on the tree main types

---

Research how common values are

Research if traffic_calming=table is common with crossing=traffic_signals?
And is crossing:island=yes common with crossing=traffic_signals?
If not, we could remove those from the presets for node hw=crossing + crossing=traffic_signals.
Testcase https://ideditor.netlify.app/#background=Bing&disable_features=boundaries&id=n7242739087&locale=en&map=20.00/52.33904/13.65936

---

infrastructure on crossing presets?

Do we want the infrastructure preset on crossings as moreFields? There are cases like https://ideditor.netlify.app/#background=Bing&disable_features=boundaries&id=w1009387182&locale=en&map=20.00/52.47153/13.46059 where the crossing is on the bridge. => We can add it to the new @templates/geometry_way_more. "bridge" is used 3k times for "crossing=*" https://taginfo.openstreetmap.org/keys/crossing#combinations

---

name on crossing presets?

Do we want to give name more visibility on hw=path+path=crossing because path sometimes have names? Testcase https://ideditor.netlify.app/#background=Bing&disable_features=boundaries&id=w947039863&locale=en&map=20.00/52.43023/13.44348
The name is a general field which always shows when present, it does show below the explicit fields, though, see https://pr-1201--ideditor-presets-preview.netlify.app/id/dist/#background=Bing&disable_features=boundaries&id=w947039863&locale=en&map=20.00/52.43023/13.44348 at the end of the list

---

width on crossing presets?

• Do we want to add width and width:source as moreTags?
• For the hw=path we might also add bicycle:width and footway:width as moreTags

---

bicycle:oneway

Is there a way to add bicycle:oneway=* as kind of synonym for oneway=* on hw=path|cycleway? Both are used but only one is visible as field.

---

zebra

Add "addTags" for crossing=zebra to add marking zebra. Maybe also crossing_ref=zebra? Testcase https://ideditor.netlify.app/#background=Bing&disable_features=boundaries&id=n9446412638&locale=en&map=20.00/52.32519/13.62391