Those all look fine, in that I wouldn’t change it if I saw it mapped that way.
I would expect any of these should be understood as a crosswalk by data
consumers:
highway=footway, footway = crossing
highway=cycleway, cycleway = crossing
highway=path, path = crossing
You could read this
Small detail, but if it's a bike trail, bicycle=designated is probably
better than bicycle=yes
http://wiki.openstreetmap.org/wiki/Bicycle#Bicycle_Restrictions
On Tue, Jun 23, 2015 at 3:35 PM, Jim McAndrew j...@loc8.us wrote:
Paul, Bryan,
Thanks for your help with this! My issue was with
I am looking into tagging some crosswalks, and I've just been putting a
node at the intersection. Some crosswalks are really long though, and I
think that information is important to the person crossing the road. Is
there an acceptable way that we can tag a way as a crosswalk without
interfering
Here's a relatively simplistic example
http://www.openstreetmap.org/node/3304635897 of crosswalk tagging
http://wiki.openstreetmap.org/wiki/Tag:highway%3Dcrossing.
On Tue, Jun 23, 2015 at 2:46 PM, Jim McAndrew j...@loc8.us wrote:
I am looking into tagging some crosswalks, and I've just been
Paul, Bryan,
Thanks for your help with this! My issue was with bicycle trails that cross
roads, as they usually put a crosswalk in for these cases, but the route
itself can support other non-motorized vehicles. I think this gives me some
good options that would be acceptable.
1) I could use
It’s ok to map them as either a single intersection node or a way. Here is my
understanding from the various wiki pages the document these things, and it
matches what I see people map in places with sidewalks and crosswalks. Keep in
mind, the wiki does seem to change kind of frequently, and
6 matches
Mail list logo