Tobias
3ab88d0fcd
crossing: Use the same property order for fields/crossing/markings*
...
All those fields used a different order of properties, which made it hard to compare them.
This commit does not change anything on the fields, it just streamlines the same order of properties across files.
2024-04-26 12:00:45 +02:00
Kamil Monicz
3f8c56bdd0
Specify crossing:markings in Poland ( #1030 )
2023-12-15 17:20:15 +01:00
Martin Raifer
8d45c78e65
create template for crossing:markings fields, and add regional field for DE-AT-CH
2023-05-11 16:45:01 +02:00
Dimitar
bc25be16f1
[regional:BG] Only show relevant values for crossing markings in Bulgaria ( #891 )
2023-05-11 15:17:43 +02:00
Martin Raifer
09b0fd9ae7
specify icons for crossing markings
2023-01-24 15:08:29 +01:00
Martin Raifer
b583fd1e83
add crossing:markings=yes by default to Marked Crossings
2023-01-13 13:50:14 +01:00
Martin Raifer
a7037f96cd
add translatable strings for crossing:markings values
2022-11-08 19:30:55 +01:00
Martin Raifer
ef116afa71
add documented options for the crossing:markings tag
...
from https://wiki.openstreetmap.org/w/index.php?title=Key:crossing:markings&oldid=2420133
2022-11-08 17:25:43 +01:00
Martin Raifer
80c5df168a
refactor crossing presets to use (new) crossing:markings tag
...
The tag proposal `crossing:markings` was recently accepted: https://wiki.openstreetmap.org/wiki/Key:crossing:markings
Closes #589
Closes #507
Closes #568
See also #408
2022-09-23 15:22:38 +02:00
Martin Raifer
4e60539d32
fix spelling, run build
2021-12-15 10:16:24 +01:00
Kyℓe Hensel
754d07395f
add fields for level crossing ( #194 )
2021-12-14 17:11:18 +01:00
Quincy Morgan
bf95421f65
Initial commit
2020-11-05 11:30:34 -05:00
