You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When defining a dash array pattern as default on map or layer level, it is not obvious how to overwrite it with a solid line property on layer or element level where needed. As a result editors design maps where the majority of lines are dashed not with any dash array pattern as default, just because also one or or few solid lines need to be given. This is because people naturally guess that an empty string value would be the pattern for a solid line, because this is what they see in the dash array field before they give a line a dashed pattern.
Describe the solution you'd like
In the map editing session, when the editor enters a dash array default on layer or overall map level, hint to the editor that he/she can overwrite the default with "," for a solid string on element respectively layer level.
Describe alternatives you've considered
Provide the same information in a complete, compact, and fully searchable uMap editor documentation in English.
Additional context
uMap instance: https://umap.openstreetmap.fr/ as of 16 Sep 2024.
Take https://umap.openstreetmap.fr/en/map/milke-danda-trek_1112959 as an example. It defines "4, 12" as dash array pattern on overall map level and "," as dash array default for the layer "Drive to/from the trailhead". Done. As our maps share the same layer concept and therefore we just clone an existing map to start a new map, we almost never enter any dash array pattern. For any new path we just Import it, Chose the layer, and boom, work done.
But possibly "," was never planned to be the dash array for solid lines and already from the next umap.openstreetmap.fr update on, "," will not work anymore while we only accidentally find out about this issue weeks if not months later.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When defining a dash array pattern as default on map or layer level, it is not obvious how to overwrite it with a solid line property on layer or element level where needed. As a result editors design maps where the majority of lines are dashed not with any dash array pattern as default, just because also one or or few solid lines need to be given. This is because people naturally guess that an empty string value would be the pattern for a solid line, because this is what they see in the dash array field before they give a line a dashed pattern.
Describe the solution you'd like
In the map editing session, when the editor enters a dash array default on layer or overall map level, hint to the editor that he/she can overwrite the default with "," for a solid string on element respectively layer level.
Describe alternatives you've considered
Provide the same information in a complete, compact, and fully searchable uMap editor documentation in English.
Additional context
uMap instance: https://umap.openstreetmap.fr/ as of 16 Sep 2024.
Take https://umap.openstreetmap.fr/en/map/milke-danda-trek_1112959 as an example. It defines "4, 12" as dash array pattern on overall map level and "," as dash array default for the layer "Drive to/from the trailhead". Done. As our maps share the same layer concept and therefore we just clone an existing map to start a new map, we almost never enter any dash array pattern. For any new path we just Import it, Chose the layer, and boom, work done.
But possibly "," was never planned to be the dash array for solid lines and already from the next umap.openstreetmap.fr update on, "," will not work anymore while we only accidentally find out about this issue weeks if not months later.
The text was updated successfully, but these errors were encountered: