User talk:JPinAR
Thoughts on tagging NW 3rd Street in Bentonville, AR
Mapillary | Way | Tagging | Thoughts |
---|---|---|---|
NW 3rd & G St | 1116384887 1116384887 | cycleway=lane lanes=2 |
Starting off pretty simple just a couple of cycle lanes on either side of the road. |
NW 3rd & G St + 70m | 1116384888 1116384888 | cycleway:left=lane cycleway:right=shared_lane lanes=2 |
70m later the right bike lane disappears and becomes a shared lane |
NW 3rd & G St + 100m | 1116384889 1116384889 | cycleway:left=lane cycleway=shared_lane lanes=2 |
30m later the left bike lane disappears and becomes a shared lane |
Approaching NW 3rd & Walton from East | 1116384886 1116384886 | cycleway=shared_lane lanes=3 lanes:backward=1 lanes:forward=2 turn:lanes:forward=left;through|right |
Only the left/through and counter-flow lane are mark shared the right turn onto a 5 lane "Stroad" is not. Should this be cycleway:forward:lanes=shared_lane|no + cycleway:backward:lanes=shared_lane instead of cycleway=shared_lane? If I change it will is be rendered or routed correctly? *Probably Not* |
Approaching NW 3rd & Walton from West | 1065994300 1065994300 | cycleway=shared_lane lanes=3 lanes:backward=2 lanes:forward=1 turn:lanes:backward=left;through|right |
Only the left/through and counter-flow lane are mark shared the right turn onto a 5 lane "Stroad" is not. Should this be cycleway:forward:lanes=shared_lane + cycleway:backward:lanes=shared_lane|no instead of cycleway=shared_lane? If I change it will is be rendered or routed correctly? *Probably Not* |
Bi-direction Cycle Lane mid-block start | 1116384897 1116384897 | bicycle=designated cycleway:separation:left=bollard foot=no highway=cycleway |
Yes, this is a Cycle path and not a road but it's an important one because this is where the Cycle & Foot Path to the north ceases and become a bi-directional cycle lane. Technically the path continues but becomes a sidewalk for pedestrian use. This is blocked with anchored bollards, made of plastic, and join the road at 9789390905 9789390905 which explains the change occurring in the next section. |
NW 3rd now with protected bike lane | 1065994301 1065994301 | cycleway:right=lane cycleway:right:bicycle=yes cycleway:right:lane=exclusive cycleway:right:oneway=no cycleway:right:separation=bump cycleway:right:surface=asphalt lanes=2 lanes:backward=1 lanes:forward=1 |
We now have a bi-directional protected bike lane with bumps (except for smaller bumps at corners to allow vehicles to cut corners easier?) I also added that it is exclusive. Is cycle:lane=* and cycle:lanes=* almost a little too similar to be distinguishable? Lanes are only lanes if they can support vehicle traffic through right, cycleway:lanes=* appears and has more lanes than the lanes=* has a count for? I'm pretty sure this breaks things... but if you can only have cycleway:right=* or cycleway:left=* then a right turn lane can never cross a Template:Key:cycleway without causing a conflict with the current tagging schema for OSM that either requires a cycle lane to align to a roadside or prohibits cycle lanes from being considered lanes. This is a bit ranty and off topic but this gets even more complex when a cycleway:right=lane + cycleway:right:oneway=no makes a diagonal crossing at an intersection to become a cycleway=lane, spoiler warning it's coming and this is the setup. |
NW 3rd & NW O St | 1065994305 1065994305 |
cycleway=lane |
This is where it gets interesting because diagonal crossings are rare but in one intersection, a 116557722 116557722 in OSM, the road switches from cycleway:right=lane + cycleway:right:oneway=no to… cycleway=lane + cycleway:right:marking=solid_line + cycleway:left:separation=bump This doesn’t entirely capture the whole picture though because the diagonal crossing/lane could be a lane that crosses two lanes of traffic including oncoming, which makes this a left hand turn? Or this becomes a cycleway=crossing and becomes a crosswalk with the preferred right-of-way, at least in the state of Arkansas since the summer of 2021. But if this is the case then there is only a left or right, not a crossing right-to-left. (I’m not sure how an instant right to split lane cutover is routed.) |
NW 3rd Protected Bike Lane + Paint-only Bike Lane | 1065994306 1065994306 |
cycleway:right=lane |
This is where the eastbound Bike Sidepath transitions to become an on-street protected bike lane. Via 1065994304 1065994304 which is one-way for routing purposes and foot=no as the east side is a cycle lane only with no separated sidewalk, hence routing should take pedestrians via the sidewalk on the north side of the road. All this while the westbound bike lane continues as a paint-only bike lane. |
NW 3rd Paint-only Bike Lane Only | 1065994306 1065994306 |
cycleway:right=lane |
For only a few meters the paint-only bike lane continues with a solid line. |
NW 3rd Shared Road "Sharrow" | 12760096 12760096 |
cycleway=shared_lane |
And back to a shared road identified using "Sharrow" style pictograms. |