Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding hazard warnings to paths #7

Open
SK53 opened this issue May 21, 2020 · 3 comments
Open

Adding hazard warnings to paths #7

SK53 opened this issue May 21, 2020 · 3 comments

Comments

@SK53
Copy link

SK53 commented May 21, 2020

Recent discussion on tagging reminded me that I'd made some very basic experimentation with ideas of how to add hazard warnings to a Carto-Csst style.

I was mainly interested in two types of paths:

  • Ones crossing tidal areas, such as the path to Hilbre. Often these have an elaborate warning in the name
  • SAC Scale 3 and above in mountainous areas. We know that Gordale Scar is the classic one to catch people out.

I thought there were potentially two types of annotation which could be used to make these clearer:

  • An international danger warning sign (see ISO 7010 on Wikipedia), repeated along the path at intervals. W001 would be the obvious first one to use, but W008 has potential for SAC Scale. I haven't found one for flood danger.
  • An explicit annotation along the path ("Beware of tides", "Nur fur schwindelfrei" or English equivalent, "Slippy when wet")

My very crude approach has been to create a separate hazard layer. This potentially allows ways to be merged so that a single symbol could be shown at smaller scales, as well as creating generic warning text (although this probably should be handled by LUA in the end).

I used "marker-placement: line" with a representative SVG triangle, and "text-placement:line" for the warning text. Both were given a transform to offset them from the line (preferably one on the other side of the line from any name or ref text). This is presumably similar to how you do walking routes, albeit cruder.

I actually cannabilised files I was using to try & add direction arrows on waterways, hence use of [waterway] in second part which contained "stream" or "river".

#hazard {
line-width:0;
line-color:white;

marker-placement: line;
marker-spacing: 150;
marker-height: 12;
marker-transform: translate(0,15), scale(2,2);
marker-file: url("symbols/triangle-stroked-15.svg");
marker-fill: #ff0000;
marker-max-error: 0.5;

text-name: "[waterway]";
text-face-name: 'Open Sans Bold';
text-size: 10;
text-placement: line;
text-spacing: 300;
text-dy: -10;
text-fill: #ff8800;

marker-fill: #aa0000;
}

I failed to find a way to get the triangle to always be upwards with the marker-placement which was where I left it.

Anyway thought I'd actually document these ideas in case you can see a way of taking them further.

@SomeoneElseOSM
Copy link
Owner

SomeoneElseOSM commented Sep 28, 2022

Just a quick note about what's currently implemented at https://map.atownsend.org.uk/maps/map/map.html :

  • There's a "no vis paths" overlay now, which you can see at https://map.atownsend.org.uk/maps/map/map.html#zoom=17&lat=54.445418&lon=-3.22455 . Things that are ((not public footpaths etc.) and ((have a high sac_scale) or (have a low trail_visibility))) will appear there. "no vis paths" are shown with longer gaps between the dots, as are "intermediate trail viisbility" paths on the main layer.

  • Things aren't completely consistent yet. Gordale Scar isn't shown as a "no vis path" because it has a designation on it.

  • The bundling of "paths that are dangerous" with "paths that aren't very visible" isn't ideal, but better than nothing.

  • I've not used a "warning" marker because I suspect that it'd make the map too "busy"

@SomeoneElseOSM
Copy link
Owner

Just to link to a few other things:

This is a diary entry that discusses some of this. There's a comment on that that links to https://wiki.openstreetmap.org/wiki/United_States/Trail_Access_Project#Suggested_Tagging and discusses how this maps align with those suggestions.

There is a related discussion about "obstacle" here

@SomeoneElseOSM
Copy link
Owner

(not directly hazard but) this is definitely worth a read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants