CalvinBackup/id-tagging-schema
1
0
Fork 0
mirror of https://github.com/FoggedLens/id-tagging-schema.git synced 2026-05-22 08:16:55 +02:00
Code Issues Packages Projects Releases Wiki Activity

crossing: Add readme for crossing presets and fields

Browse Source
This commit is contained in:
Tobias
2024-04-25 04:36:01 +02:00
parent 118ae02ebe
commit 2cec1313d7
1 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
data/presets/highway/crossing/README.md
+25
View File
@@ -0,0 +1,25 @@
# About the crossing presets
## General
These presets use fields `@templates` to make sure all have a similar structure.
Some presets like `traffic_signals` have additinal fields and use a different field order.
Try to keep the file structure very similar so they can be easily compared.
## nodes `highway=crossing + crossing=*`
Crossing nodes are handel by `highway/crossing.json` + `highway/crossing/*.json` (as geometry type `vertex`).
Crossing nodes and crossing ways have a big overlap.
However, there are a few tags that should _only_ be expected on the crossing node. When crossing ways are present, this also means there are separate ways attached with additional nodes that hald the
There are places in OSM that follow a different tagging style where only crossing ways are used (without the vertex nodes). Those regions might have other conventions on where to place
## ways `highway=footway|cycleway|path + *=crossing + crossing=*`
Crossing way presets are duplicated per highway class:
- `/highway/footway/crossing.json` + `/highway/footway/crossing/*.json`
- `/highway/cycleway/crossing.json` + `/highway/cycleway/crossing/*.json`
- `/highway/path/crossing.json` + `/highway/path/crossing/*.json`
The crossing presets for `/cycleway*` and `/path*` are considered to be relevant for bike traffic and have additional fields that target bike vs. foot traffic.