OpenStreetMap Forum

The Free Wiki World Map

You are not logged in.

#1 2018-02-08 10:48:03

Zisper
New Member
Registered: 2018-02-08
Posts: 1

Walkable Rivers

Hi;

     Just wondering how you go about marking a river as "walkable"?  There's some near me which are almost _always_ dry and I've tagged them as intermittent, but there's no option to set them as pedestrian accessible.  At least, none that I can find.  It occurs to me that there's often trails which will follow a riverbank edge for a while as well, would it make sense to me if those river sections could also be marked as walkable?

Offline

#2 2018-02-08 15:57:57

n76
Member
Registered: 2013-05-22
Posts: 215

Re: Walkable Rivers

There are desert areas near me where most of the "waterways" are nearly always dry. Some of them are used by motor vehicles most of the year. My solution to tagging them was:

waterway=stream
intermittent=yes
highway=track
ford=yes
surface=sand

Neither the default map rendering nor error checking in JOSM deal well with the combination of highway=* and waterway=* on the same way. But it does match what is "on the ground" so I ignore the JOSM warnings and realize that most maps won't have it rendered as I might like.

Offline

#3 2018-02-08 17:09:48

SomeoneElse
Member
Registered: 2010-10-13
Posts: 902

Re: Walkable Rivers

n76 wrote:

But it does match what is "on the ground" so I ignore the JOSM warnings and realize that most maps won't have it rendered as I might like.

At least one will (at least, for similar sorts of things mapped in the UK) - https://map.atownsend.org.uk/maps/map/m … =-2.494023 .  I used an extra-wide casing of the road to indicate ford, sidewalk or verge instead of bridge.  The style's available if you want to have a go at rendering a map of any of your desert tracks - see the links from the changelog at the top of that link.

Offline

#4 2018-02-17 12:53:53

Klumbumbus
Member
Registered: 2014-01-12
Posts: 527
Website

Re: Walkable Rivers

n76 wrote:
waterway=stream
intermittent=yes
highway=track
ford=yes
surface=sand

This solution doesn't work if one of highway or waterway or both has a name, which is true in most cases. In your example (https://www.openstreetmap.org/way/193001272) you ommited the waterways name "Bathford Brook" and gave the waterway the name "Tuckingmill Lane" too.

Offline

#5 2018-02-17 16:37:46

n76
Member
Registered: 2013-05-22
Posts: 215

Re: Walkable Rivers

Klumbumbus wrote:
n76 wrote:
waterway=stream
intermittent=yes
highway=track
ford=yes
surface=sand

This solution doesn't work if one of highway or waterway or both has a name, which is true in most cases. In your example (https://www.openstreetmap.org/way/193001272) you ommited the waterways name "Bathford Brook" and gave the waterway the name "Tuckingmill Lane" too.

Not my particular example, but you do point out an issue with the tagging I suggested. Fortunately, I've not come across this situation in the areas I've mapped. Generally the locals use the name of the waterway if it has one. So a local might say something like "go 6 miles on the Charouleau Gap road to where it crosses Dodge Wash, go up the wash about a half mile and the four wheel drive road leaves the wash on going up a ridge on the right side."

Unfortunately, as far as I can tell OSM hasn't yet come up with a way of having an array of values for a single tag. So as a first step, I'd suggest using the name tag for whatever the locals are more likely to call it and the alt_name tag for the other option. If there are more than two names, then this scheme would fail.

I suppose one could use route relations for both the stream and the track and have them reuse the same way. But I am not sure how common or supported that form of tagging is.

Offline

#6 2018-02-17 17:04:36

hadw
Member
Registered: 2014-09-02
Posts: 996

Re: Walkable Rivers

n76 wrote:

Unfortunately, as far as I can tell OSM hasn't yet come up with a way of having an array of values for a single tag.

Separate the values with semi-colons.  Note many data consumers use lazy parsing of values and will not split multiple values, and may try to match the composite value, rather than the first component.

Offline

#7 2018-02-17 17:45:01

Klumbumbus
Member
Registered: 2014-01-12
Posts: 527
Website

Re: Walkable Rivers

hadw wrote:

Separate the values with semi-colons.  Note many data consumers use lazy parsing of values and will not split multiple values, and may try to match the composite value, rather than the first component.

Thats not a good idea in this case as it is not clear which one the first or second value belongs to which tag highway or waterway.

Another solution is to use two ways drawn ontop of each other. One for highway and one for waterway.

Offline

#8 2018-02-18 14:50:23

SomeoneElse
Member
Registered: 2010-10-13
Posts: 902

Re: Walkable Rivers

What's more usual than a string of semicolon-separated names is to use specfic tags for specific names.  See e.g. https://www.openstreetmap.org/way/53247094 (though depending on contect ":" is often used instead of "_").  Maps that want to process that information can then do so.  See for example:

http://map.atownsend.org.uk/maps/map/ma … =-1.293013

which incorporates both lock_name and ref (or lock_ref if set), and the "name" is used elsewhere on the canal.

Offline

Board footer

Powered by FluxBB