[Talk-us] New US Bicycle Routes (USBRs) are proposed

Volker Schmidt voschix at gmail.com
Sat Jul 3 14:41:03 UTC 2021


Hi,
as I worked in the past on an early version of the USBRS 66 in California,
and as I rode the entire ACA version of the bicycle route 66 in 2016) I
could offer to look into the new California part of it.
You also find Mapillary images for most of it (user: voschix)

BTW: I am used to using state=proposed for tagging proposed routes, not
"proposed=yes" . [1]

Regards

Volker
(Padova, Italy)

[1] https://wiki.openstreetmap.org/wiki/Key:state

On Sat, 3 Jul 2021 at 13:05, <talk-us-request at openstreetmap.org> wrote:

> Send Talk-us mailing list submissions to
>         talk-us at openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.openstreetmap.org/listinfo/talk-us
> or, via email, send a message with subject or body 'help' to
>         talk-us-request at openstreetmap.org
>
> You can reach the person managing the list at
>         talk-us-owner at openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Talk-us digest..."
>
>
> Today's Topics:
>
>    1. New US Bicycle Routes (USBRs) are proposed (stevea)
>    2. Re: Speed Limit Validity in US Questions (Minh Nguyen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 2 Jul 2021 16:52:44 -0700
> From: stevea <steveaOSM at softworkers.com>
> To: talk-us <talk-us at openstreetmap.org>
> Subject: [Talk-us] New US Bicycle Routes (USBRs) are proposed
> Message-ID: <0A07AC90-D982-4F9D-9967-FAAAB5DF0290 at softworkers.com>
> Content-Type: text/plain;       charset=us-ascii
>
> Fellow US mappers, especially bicycle enthusiasts / those who enjoy
> mapping bike routes:  AASHTO's Spring 2021 round of new additions to the
> USBRS includes many new proposed (national) United States Bicycle Routes
> yet to be added to OSM.  Some of these are realignments or extensions to
> existing routes, most are brand new alignments.
>
> It is expected these might be AASHTO-approved in July.  It now makes sense
> for OSM to do what we've been doing for many years, entering the routes
> (tagged proposed=yes) using applications provided to AASHTO by the
> respective state Departments of Transportation who publish / promote them
> as the states now ask AASHTO for official approval.  (AASHTO has kindly
> provided to OSM explicit permission for us to enter these; their entry
> while proposed follows established OSM precedent).  After approval, simply
> remove proposed=yes from each route (renderers "do the right thing" over
> days-to-weeks).  Instructions and links to route maps and turn-by-turn
> instructions are at:
>
>
> https://wiki.osm.org/wiki/United_States_Bicycle_Route_System#Proposed_USBRs_in_OSM
>
> Remaining Spring 2021 AASHTO ballots for new USBRs are:
>
> California (2 routes):
>         USBR 50 California (new alignment):  not difficult, quite minor,
> really, some small-scale realignment
>         USBR 66 California (new alignment):  about 25% entered, a great
> start!  (Let's get to the Colorado River/Needles)
>
> Indiana (1 route):
>         USBR 235 Indiana (new)
>
> Ohio (6 routes):
>         USBR 21 Ohio (new)
>         USBR 25 Ohio (new)
>         USBR 30 Ohio (new)
>         USBR 44 Ohio (new)
>         USBR 225 Ohio (new)
>         USBR 230 Ohio (new)
>
> Utah (2 routes remain to be realigned / extended, 4 have been entered):
>         USBR 70 Utah (realignment)
>         USBR 79 Utah (extension of existing USBR)
>
> Washington (4 routes):
>         USBR 20 Washington (new)
>         USBR 40 Washington (new)
>         USBR 81 Washington (new)
>         USBR 281 Washington (new)
>
> It would be great if OSM's terrific volunteers could enter these route
> data by the time AASHTO releases their results of their votes on the ballot
> (in weeks) and likely approves these.  Keeping our wiki updated (especially
> state route wikis in Ohio) is important if you can do that, too.  Please
> update route status in the Proposed section with red, yellow or green
> "status colors" as well as adding BrowseRelation entries as new relations
> are created for new routes.
>
> Thank you for any contributions you might make to improve the USBRS in
> OSM.  I am happy to offer guidance if the wiki still leaves you with
> questions.  Happy Mapping!
>
> SteveA
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 3 Jul 2021 03:55:02 -0700
> From: Minh Nguyen <minh at nguyen.cincinnati.oh.us>
> To: talk-us at openstreetmap.org
> Subject: Re: [Talk-us] Speed Limit Validity in US Questions
> Message-ID: <sbpfma$9s7$1 at ciao.gmane.io>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Vào lúc 07:42 2021-07-02, Horea Meleg đã viết:
> > 1. A speed limit sign is valid until next intersection, or until next
> speed limit sign encountered?
>
> The national MUTCD standard calls for a speed limit sign to be posted at
> each point where the speed limit changes and, optionally, a confirmation
> sign posted after major intersections and at an interval along the road.
> [1] (Most states have their own MUTCD editions or supplements instead of
> following the national standard verbatim. The California [2], Delaware
> [3], Indiana [4], Maryland [5], Michigan [6], Minnesota [7], Missouri
> [8], Ohio [9], Texas [10], and Utah [11] MUTCDs largely follow the
> national MUTCD with regard to speed limit signs.) The spacing of
> confirmation speed limit signs depends on the state, road
> classification, and speed limit. [12][13]
>
> Many states have guidelines to the effect of: if the speed limit changes
> at or just before an intersection, then the speed limit sign is the
> first sign posted just beyond the intersection. [5][14][15] Therefore,
> the sign's exact location is not necessarily the precise location where
> you'd split the roadway. In practice, if a north-south road has a
> different speed limit sign to the north of the intersection when going
> northbound and to the south of the intersection when going southbound,
> you'd typically split the roadway at the intersection instead of tagging
> a several-yard-long segment with maxspeed:forward/:backward tags.
>
> As long as you're following a single road and aren't turning off onto
> another road, you can pretty much count on seeing a sign of some sort
> around where the speed limit changes. If there's even such a thing as an
> "until the next intersection" speed limit, the sign would say so. The
> closest exception I can think of would be a school zone speed limit:
> some states explicitly post a sign where the school zone ends, while
> others do not. In the latter case, you could try locating the beginning
> of the school zone on the other side of the road.
>
> Rarely, a solid white line painted across the roadway can indicate a
> change in speed limit or the beginning of a school zone. [16] This would
> be the exact place to split the roadway.
>
> > 2. If it's until next intersection, which is considered as intersection?
> Any kind of highway type? Or there are some special rules?
> >
> > For example:
> >
> > A.       T intersection it’s considered?
> > B.       Cross intersection it’s considered?
> >
> >
> >
> >    - I'm asking this because for example in Europe there are both
> situations (next sign vs next intersection) depending on country rules.
>
> As noted above, a speed limit doesn't implicitly revert to another speed
> limit as you pass an intersection. However, it is common to post a
> confirmation speed limit sign at "major" intersections. Most standards
> are vague about what qualifies as a major intersection. Some states say
> it's based on the cross street's traffic volume but don't say how much
> traffic volume the street needs to carry to qualify. Georgia considers
> every intersection with a U.S. or state route to be major. [17]
> T-intersections and four-way intersections wouldi probably be treated
> the same for the purpose of speed limit sign placement.
>
> > 3.  Speed Limits marked on the road are considered as valid, or just
> those posted on a traffic sign? Meaning it could be added the information
> in OSM based on speed limit road markings?
>
> The national MUTCD allows for a pavement marking to supplement a speed
> limit sign. [18] These markings are the norm in urban and suburban areas
> in California. Elsewhere, they're much rarer, only used where there's a
> drastic speed reduction. They're just about always accompanied by speed
> limit signs, so if you see a speed limit pavement marking in aerial
> imagery, feel free to use it as a source, but don't count on there being
> another pavement marking at the end of the speed zone.
>
> As others have noted, in some jurisdictions, it's quite common for a
> speed limit to go unposted anywhere along a given street, so the default
> speed limit takes effect. The MUTCD allows a jurisdiction to post a
> default speed limit at the boundary, applying to any street that doesn't
> have an explicit sign. Default speed limit signs are common, for
> example, among cities and villages in Ohio and in various neighborhoods
> of New York City.
>
> A minor road may have no speed limit sign in a rural area that has no
> default speed limit sign. In the absence of any sign, determining the
> default speed limit is a maddening exercise [19][20], so I would advise
> your team to obtain an authoritative dataset from a state transportation
> department or county engineer's office as a reference or ask local
> mappers to research it for you, rather than making any assumptions
> yourselves.
>
> [1]
> https://mutcd.fhwa.dot.gov/htm/2009/part2/part2b.htm#section2B13_para03
> [2]
>
> https://dot.ca.gov/-/media/dot-media/programs/safety-programs/documents/ca-mutcd/rev6/camutcd2014-part2-rev6.pdf#page=36
> [3]
>
> https://regulations.delaware.gov/register/may2018/final/MUTCDPart2Signs.pdf#page=38
> [4]
>
> https://www.in.gov/dot/div/contracts/design/mutcd/2011rev1/part2b.pdf#page=12
> [5] https://www.roads.maryland.gov/mmutcd/2011_Chapters_02B.pdf#page=19
> [6]
>
> https://mdotjboss.state.mi.us/TSSD/getTSDocument.htm?docGuid=a933ceab-0a6c-4c81-a7fa-c3d973b002a5&fileName=mmutcdpart2b_2017.pdf#page=12
> [7]
>
> https://www.dot.state.mn.us/trafficeng/publ/mutcd/mnmutcd2020/mnmutcd-2b.pdf#page=18
> [8]
>
> https://epg.modot.org/index.php/903.5_Regulatory_Signs#903.5.10_Location_of_Speed_Limit_Signs
> [9]
>
> https://www.dot.state.oh.us/Divisions/Engineering/Roadway/DesignStandards/traffic/OhioMUTCD/Documents/2012%20OMUTCD%20-%20Pt.%202.pdf#page=36
> [10]
> https://ftp.txdot.gov/pub/txdot-info/trf/tmutcd/2011-rev-2/2b.pdf#page=13
> [11]
> https://drive.google.com/file/d/1JyNnvMXo5LgvhvSltSOh5miCxD84PSdJ/view
> page 56
> [12]
>
> https://ncutcd.org/wp-content/uploads/meetings/2011A/Attach-7-RW-No.6-Spacing-of-Speed-Limit-Signs-Appvd.pdf
> [13]
>
> https://safety.fhwa.dot.gov/speedmgt/ref_mats/fhwasa1304/resources2/22%20-%20Policy%20on%20Establishing%20and%20Posting%20Speed%20Limits%20on%20the%20State%20Highway%20System.pdf#page=6
> [14]
>
> https://www.wsdot.wa.gov/publications/manuals/fulltext/M51-02/Chapter2.pdf#page=14
> [15] https://cornell.app.box.com/v/clrp-pb-tsh page 88
> [16]
>
> https://www.bing.com/maps?osid=b9ea6558-8009-4b1b-9aea-595fc6769446&cp=32.829231~-97.188199&lvl=19&dir=0.337&pi=0&style=x&mo=z.0&v=2&sV=2&form=S00027
> [17]
>
> http://www.dot.ga.gov/PartnerSmart/DesignManuals/smguide/GDOT%20SIGNING%20AND%20MARKING%20DESIGN%20GUIDELINES.pdf#page=25
> [18] https://mutcd.fhwa.dot.gov/htm/2009/part3/part3b.htm#section3B20
> [19] https://wiki.openstreetmap.org/wiki/Default_speed_limits is heavily
> abridged, but it gives a sense of the complexity involved.
> [20] https://commons.wikimedia.org/wiki/File:Speed_limits_in_Ohio.svg is
> also abridged but is already quite complex.
>
> --
> minh at nguyen.cincinnati.oh.us
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
> ------------------------------
>
> End of Talk-us Digest, Vol 164, Issue 5
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20210703/565e420d/attachment-0001.htm>


More information about the Talk-us mailing list