id-tagging-schema/data/fields/crossing
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
..
barrier.json fix spelling, run build 2021-12-15 10:16:24 +01:00
bell.json add fields for level crossing (#194) 2021-12-14 17:11:18 +01:00
island.json Initial commit 2020-11-05 11:30:34 -05:00
light.json add fields for level crossing (#194) 2021-12-14 17:11:18 +01:00
markings-BG.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings-DE-AT-CH.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings-PL.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings.json Specify crossing:markings in Poland (#1030) 2023-12-15 17:20:15 +01:00
markings_yes-BG.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings_yes-DE-AT-CH.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings_yes-PL.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00
markings_yes.json crossing: Use the same property order for fields/crossing/markings* 2024-04-26 12:00:45 +02:00