Commit graph

10 commits

Author SHA1 Message Date
Tobias
75d756f2bc crossing: New approach with @templates/crossing/bicycle_relevance and @templates/crossing/defaults
The field "crossing" is removed from the `/defaults` fields.
- it is only relevant for the geometry line because it is hidden on geometry vertex.
- but on geometry line, we want it to be on the first position of fields
- the `/defaults` fields however should be positioned below the `markings` which are more relevant for specifying the kind of crossing
- the `/defaults` fields now includes `crossing_raised` which was removed from the previous and discontinued `/geomery_line` fields template.

The new `@templates/crossing/bicycle_relevance`
- is used on all highways that have bicycle relevance which are `highway=path|cycleway` and not on `highway=footway`

For all traffic_signal presets, the order of fields is different to give the `/traffic_signal` more prominence.
2024-04-26 13:18:25 +02:00
Tobias
c624700656 crossing: Introduce @templates/crossing/traffic_signal_more
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.
2024-04-26 12:00:45 +02:00
Tobias
50aeb69b4e crossing: Introduce @templates/crossing/traffic_signal
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.
2024-04-25 04:57:26 +02:00
Tobias
e47e4d6325 crossing: Introduce @templates/crossing/geometry_line
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.
2024-04-25 04:57:08 +02:00
Tobias
ca2b2e5f7a crossing: Introduce @templates/crossing/defaults
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.
2024-04-25 04:57:08 +02:00
Kamil Monicz
3f8c56bdd0
Specify crossing:markings in Poland (#1030) 2023-12-15 17:20:15 +01:00
Martin Raifer
05b48d6ca7
remove opening_hours:covid19 field, closes #963
follows #401
2023-08-04 16:37:27 +02:00
Martin Raifer
af21810172
add field for Mobile Phone number (mobile/contact:mobile) 2023-05-23 14:55:08 +02: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
Martin Raifer
bdae3f06ff
consolidate optional fields of "POI" presets into template "presets" 2023-04-13 21:18:08 +02:00