Larry, I think it's important to keep shoulders and bike lanes separate because they are governed by different rules. I'm assuming those rules are different state by state, but for example I would think that in many places it is illegal for motor vehicles to pass in a dedicated bike lane, whereas passing on the shoulder is permissible (under certain conditions only, of course). Similar differences probably exist for the rules regarding stopping and parking. My rule of thumb is: If there aren't any signs or pavement markings involving bikes, it's a shoulder, not a bike lane. Then it becomes important to tag attributes of the shoulder such as surface and width.
Harald. On Wed, Jun 3, 2015 at 6:12 PM Larry-CalRoadRunner <calroadrun...@gmail.com> wrote: > Hello Everyone, > > I would like to thank everyone for the quick response. I agree that the > tag <cycleway=shoulder> is the correct tag to use, but for it to be > effective, it must be used consistently. Otherwise anyone trying to create > a cycle map for cyclists, will have a very confusing data. The type of > Shoulders that cyclists need to know is > > Code (2 or 3) > [image: xFigure 4.49 shows an example of a bituminous shoulder, which > would be identified as Code "2" for this Data Item.] > > and > > Code 4 > [image: Figure 4.50 shows an example of a stabilized shoulder, which would > be identified as Code "4" for this Data Item.] > > Special Thank you to Thomas Roff for this link > > http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/chapter4c.cfm > > I mentioned before that I added the tag <cycleway=lane> to the Silverado > Trail, since the shoulder is marked with bike lane signs and painted bike > lane signs and logos on the shoulder. I have ridden this road for years and > I can remember when this was nothing but a highway with paved shoulders and > nothing to indicate that it is a bike lane. I am going to include a link to > my personal YouTube Channel, so that everyone can see what I am talking > about. It starts on Trancas Rd. in Napa, Ca. No shoulder at first, then > paved shoulder and finally the Silverado Trail with the bike lane signs and > logo on the paved shoulder > > https://www.youtube.com/watch?v=ek0M8wtGhSY > <https://www.youtube.com/watch?v=ek0M8wtGhSY&index=21&list=PL5do4uwsHN3XRUuCuNPGfs6OX9_CF-j5F> > > 4 minutes and 35 seconds > > For those of you that would like to see the entire bike ride, then click > on this link > to see all of the various road conditions encountered > > https://www.youtube.com/watch?v=_lmxxZEb_jk > > This is a fast motion video of most of the total ride including Hwy 29 > with paved shoulders. If you are not a bicycle rider this video will give > you an idea of what it is to ride a bicycle in the US. This is typical of > many of the conditions encountered, if you are a long distance cyclist. > > According to current practice this is tagged as <cycleway=lane> for the > Silverado Trail. > For part of Trancas Rd. The appropriate tag should be <cycleway=shoulder> > just before arriving at the Silverado Trail. My question is does the > Silverado Trail qualify as a true dedicated cycleway or is it just a > highway with paved shoulders. Currently, I see on the current cycle maps > that roads with paved shoulders are currently tag as <cycleway=lane> if > they have the bike signs and logo. I also see roads that do not have any > bike signs and logo also tagged with <cycleway=lane> According to the wiki > tag most of the roads tagged as <cycleway=lane>, do not fall into the > strict definition of a dedicated cycle lane. This is why I am asking for a > published wiki tag describing roads with paved shoulders, so that everyone > in the world will used the appropriate tag when mapping roads. > > Thank You, > > Larry-California RoadRunner > > > > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us >
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
