All fields are unsearchable (for now) so we can learn how to name properly.
The names are adapted from `presets/highway/cycleway/crossing/bicycle_foot.json`.
The terms are removed because the presets are unsearchable.
Using the preset I find the markings field to be the most important to change. The `@templates/crossing/defaults` is less important for all situation except for `data/presets/highway/crossing.json`. The main reasons for this is, that only on the base `highway/crossing` the field `crossing` is actually visible. For the more precise presets this field is hidden by some automatic part of the system.
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.
The convention is, to tag this on the node _and_/_or_ on the separate `barrier=kerb+kerb=*` node when the path is mapped separately.
It should be part of all crossing vertex presets.
This extract the three moreFields to be reused in all traffic_signals presets.
- "traffic_signals/arrow"
- "traffic_signals/countdown"
- "traffic_signals/minimap"
For unclear reasons the cycleway/crossing/traffic_signals did not have those more fields which are now added to streamline the presets.
This extract the three fields to be reused in all traffic_signals presets.
- "button_operated"
- "traffic_signals/sound"
- "traffic_signals/vibration"
Nothing else is changed, this is just an extraction into a template.
This streamlines the fields on all line geometry crossings.
- "oneway"
- "surface"
- "smoothness"
- "crossing_raised"
- "access"
Those fields are always the last in the list. For traffic signal those specific fields are put above. Which is also the only change for one vertex preset in this commit, to have the "crossing_raised" come after the traffic signal specific fields and so the order is the same across presets.
This will roll out the smoothness field for all crossings; it was previously only present in some. But given the importance of smoothness for accessibility I think that is OK. This commit also moves the surface (and smoothness where present) fields further down the list which reduces the priority a bit.
The biggest change in priority is the oneway-field which had the first position before and now is below the defaults- and markings-field.
This way we have the same fields in all crossing presets:
- "crossing"
- "tactile_paving"
- "crossing/island"
This change the order of things slightly for some footway, cycleway crossing where `surface` is now a bit lower, but that should not be a problem.
this includes most of the top ~100 most used values of the `cuisine` tag, omitting discouraged values like `international`
also sorts the list by the current number of uses according to taginfo (see https://gist.github.com/tyrasd/aaa5d32cb05f8ed1acafdd2e40737254)
