I say go ahead and add it, though `highway=track` (with appropriate access tag)
might make more sense if vehicles drive along the beach.
Here in NJ, people have also been mapping the paths that lead down to the beach
from the boardwalks, but they generally aren’t connected. I’m a runner, so I
A few years ago, I mapped beach access paths, too: http://ow.ly/yZT3G
But I did not map along the beach as there was no clearly defined path or
boardwalk, nor could I see a compelling case for doing so. I can see a
reason if driving, horses, bikes compete for access, or there are areas
that
I think this would be a great addition for routing.
I would make sure that you add tags like bicycle=no, even though bicycles
are probably not forbidden, bicycles and sand generally do not mix. (
http://www.njbikemap.com/ omits dirt roads in southern jersey for this
reason)
Another consideration
On 7/10/2014 2:58 PM, Jim McAndrew wrote:
I would make sure that you add tags like bicycle=no, even though
bicycles are probably not forbidden, bicycles and sand generally do not mix.
The key word being generally
I think I'd probably only do bike=no if there was a No Bikes on Beach
type sign. (same with horses) It is possible to ride along the surf where
the sand is hard with a standard MTB. What about:
highway=path (can't be track for the viz tags)
access=public
surface=sand
trail_visibility=no
?
On
5 matches
Mail list logo
