I have read an article about the CA 180 Braided Freeway ramp project in Fresno, CA. in the Fresno Bee on Monday of this past week, does anyone have any insight to this? It would be much better to have that project completed late in the year to prevent weaving. ---SCP
EDIT: Changed icon. --roadfro
This project will eliminate the weaving caused by the closely spaced junctions of CA-180 with CA-168 and CA-180 with CA-41. I believe that, upon completion, motorists on WB CA-168 will be able to connect directly with CA-41 without having to get onto CA-180, and motorists coming from CA-41 will be able to connect directly with CA-168 without having to get onto CA-180.
When the CA-180 freeway was built, there was space provided for these connections but they were not built, probably due to a lack of funds.
This project is being done using design-build. Specs and other materials can be found at: http://www.dot.ca.gov/hq/oppd/designbuild/fresno-rfp.htm
This article indicates the braided ramp project is now complete:
http://www.constructionequipmentguide.com/Caltrans-Completes-Segment-of-SR-180/24349/
QuoteEarlier in 2014, Caltrans completed another significant transportation improvement for Fresno motorists who regularly travel the busy traffic maze between State Routes 180, 41 and 168 a less stressful, safer commute.
The SR-180 Braided Ramps Project added two braided connectors that allow motorists to use new designated lanes between interchanges to safely merge into freeway traffic. These connectors are identified as "braided ramps" since one connector goes over the other, similar to a braid. This section along SR-180, with an average annual daily traffic count that often surpasses 150,000 vehicles, is a principal artery for the Fresno area.
Additional information is found at http://www.dot.ca.gov/dist6/environmental/projects/sr180braidedramps/.
Looks like Google Street View is already on the job. At least some of the signage (but not all?) is of the new 'up arrow' style:
https://goo.gl/maps/5NUFt
Quote from: flowmotion on February 15, 2015, 11:01:37 PM
Looks like Google Street View is already on the job. At least some of the signage (but not all?) is of the new 'up arrow' style:
https://goo.gl/maps/5NUFt
I'm starting to think Caltrans is on to something here with their unique arrow-per-lane signing style...This is at least the second application of "Caltrans APL" pointed out on this forum, and it doesn't look half bad.
Caltrans APL uses different (shorter) up arrows, so that all the necessary APL elements can fit on the panel while still conforming to Caltrans' 120" maximum sign height. Where this will break down is if there is a longer destination name, or if becomes necessary to sign multiple destinations/shields on one panel. Otherwise, it's a great way to make APL signing more reasonable (read: less sign panel area) than vanilla MUTCD.
Quote from: roadfro on February 17, 2015, 04:12:38 AM
Quote from: flowmotion on February 15, 2015, 11:01:37 PM
Looks like Google Street View is already on the job. At least some of the signage (but not all?) is of the new 'up arrow' style:
https://goo.gl/maps/5NUFt
I'm starting to think Caltrans is on to something here with their unique arrow-per-lane signing style...This is at least the second application of "Caltrans APL" pointed out on this forum, and it doesn't look half bad.
Caltrans APL uses different (shorter) up arrows, so that all the necessary APL elements can fit on the panel while still conforming to Caltrans' 120" maximum sign height. Where this will break down is if there is a longer destination name, or if becomes necessary to sign multiple destinations/shields on one panel. Otherwise, it's a great way to make APL signing more reasonable (read: less sign panel area) than vanilla MUTCD.
And I think that that's exactly the point. APL signs are great, because it should be easy to tell when you're driving where your lane will let you go, as opposed to doing something along the lines of counting lanes while your driving. And of course, with so many existing signs in CA being shorter, it's much more cost-effective if the new signage meets those specs.
In Georgia, they also sign APL signs, even when there is no option lane. While technically not allowed by the national MUTCD, I don't have a problem with it because the signs are very legible.
Quote from: roadfro on February 17, 2015, 04:12:38 AM
Quote from: flowmotion on February 15, 2015, 11:01:37 PM
Looks like Google Street View is already on the job. At least some of the signage (but not all?) is of the new 'up arrow' style:
https://goo.gl/maps/5NUFt
I'm starting to think Caltrans is on to something here with their unique arrow-per-lane signing style...This is at least the second application of "Caltrans APL" pointed out on this forum, and it doesn't look half bad.
Caltrans APL uses different (shorter) up arrows, so that all the necessary APL elements can fit on the panel while still conforming to Caltrans' 120" maximum sign height. Where this will break down is if there is a longer destination name, or if becomes necessary to sign multiple destinations/shields on one panel. Otherwise, it's a great way to make APL signing more reasonable (read: less sign panel area) than vanilla MUTCD.
I don't think multiple shields and longer destination names are going to be an issue as you can simply make the signs wider. I figure that Caltrans' approach to arrow-per-lane signage can accommodate 2 lines of legend given the examples we have in the Fresno area. However, including a distance message with two lines of legend does result in some cramming. Here's an advanced APL guide sign from a signing plan for a project near the CA-99/CA-152 junction near Chowchilla that shows the above problem...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99n-152_apl-plan1.png&hash=6fcb73440165a23fb8b613198d02cac0c97dbc53)
If you take the distance message out of the equation, the sign lays out quite nicely...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99n-152_apl-plan2.png&hash=4b96995cfae9ee5943e012340bb48606907cb555)
While I've guestimated that the up-arrows used in the 41-180-168 braided ramps project to be 45 inches tall, the arrows in the above signing plan are only 42 inches tall. I've developed both for my sign making library but would really like to know if an official spec for these arrows exist.
Note: Just for the heck of it, I tried drawing the 1 mile advance arrow-per-lane sign following the signing plan I posted above...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99-152_advAPL.png&hash=3be6f419f7fa69ee979a8c56e180ddca4ca118df)
Quote from: myosh_tino on February 19, 2015, 02:34:18 AM
I don't think multiple shields and longer destination names are going to be an issue as you can simply make the signs wider. I figure that Caltrans' approach to arrow-per-lane signage can accommodate 2 lines of legend given the examples we have in the Fresno area. However, including a distance message with two lines of legend does result in some cramming. Here's an advanced APL guide sign from a signing plan for a project near the CA-99/CA-152 junction near Chowchilla that shows the above problem...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99n-152_apl-plan1.png&hash=6fcb73440165a23fb8b613198d02cac0c97dbc53)
If you take the distance message out of the equation, the sign lays out quite nicely...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99n-152_apl-plan2.png&hash=4b96995cfae9ee5943e012340bb48606907cb555)
While I've guestimated that the up-arrows used in the 41-180-168 braided ramps project to be 45 inches tall, the arrows in the above signing plan are only 42 inches tall. I've developed both for my sign making library but would really like to know if an official spec for these arrows exist.
Note: Just for the heck of it, I tried drawing the 1 mile advance arrow-per-lane sign following the signing plan I posted above...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99-152_advAPL.png&hash=3be6f419f7fa69ee979a8c56e180ddca4ca118df)
Here's the current sign (https://www.google.com/maps/@37.078537,-120.201809,3a,75y,330.63h,82.5t/data=!3m4!1e1!3m2!1sZrHDbvxoknMg8cH8fu9sXw!2e0)
it's fairly new, so it's kind of strange they are replacing it already.
Quote from: Occidental Tourist on February 19, 2015, 06:33:25 PM
Here's the current sign (https://www.google.com/maps/@37.078537,-120.201809,3a,75y,330.63h,82.5t/data=!3m4!1e1!3m2!1sZrHDbvxoknMg8cH8fu9sXw!2e0)
it's fairly new, so it's kind of strange they are replacing it already.
If you advance the GMSV camera a couple of shots, you can see the foundations for the new truss... http://goo.gl/maps/5Gucb
Quote from: myosh_tino on February 19, 2015, 02:34:18 AM
Note: Just for the heck of it, I tried drawing the 1 mile advance arrow-per-lane sign following the signing plan I posted above...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99-152_advAPL.png&hash=3be6f419f7fa69ee979a8c56e180ddca4ca118df)
I wonder how it would look if the distance message was placed between the arrows. This would avoid the vertical spacing issue, but might not look all that great.
The only thing I don't like is that the exiting portion of the shared lane arrow looks incredibly weird (compared to the curved arrow). It looks like this is done to avoid having the arrowheads touch. Are these Caltrans arrows using a thicker shaft, or is it just because the arrows are shorter? Would a diagonally stemmed arrow look better?...that would be more in line with a typical exit direction sign.
Quote from: roadfro on February 19, 2015, 09:19:44 PM
The only thing I don't like is that the exiting portion of the shared lane arrow looks incredibly weird (compared to the curved arrow). It looks like this is done to avoid having the arrowheads touch. Are these Caltrans arrows using a thicker shaft, or is it just because the arrows are shorter? Would a diagonally stemmed arrow look better?...that would be more in line with a typical exit direction sign.
I think this might be the most sexually suggestive comment ever written on a roadgeek forum.
^ I think you're reading way too much into that...
Quote from: roadfro on February 19, 2015, 09:19:44 PM
Quote from: myosh_tino on February 19, 2015, 02:34:18 AM
Note: Just for the heck of it, I tried drawing the 1 mile advance arrow-per-lane sign following the signing plan I posted above...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99-152_advAPL.png&hash=3be6f419f7fa69ee979a8c56e180ddca4ca118df)
I wonder how it would look if the distance message was placed between the arrows. This would avoid the vertical spacing issue, but might not look all that great.
The only thing I don't like is that the exiting portion of the shared lane arrow looks incredibly weird (compared to the curved arrow). It looks like this is done to avoid having the arrowheads touch. Are these Caltrans arrows using a thicker shaft, or is it just because the arrows are shorter? Would a diagonally stemmed arrow look better?...that would be more in line with a typical exit direction sign.
I am not sure if the Caltrans' arrows have thicker shafts because the sign plan only shows that the up-arrow is 21" wide by 42" tall and I do not have the sign plans for the 180-41-168 braided ramp project. I did notice the oddly shaped arrowheads used on both curved arrows. As for what I did when developing my version of the Caltrans APL arrows, I used an 8" shaft which is slightly wider than the FHWA spec (7.75") along with a standard arrowhead.
I took a stab at the suggested modifications (moving the distance message down and the diagonal arrow) and here's what I came up with...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.markyville.com%2Faaroads%2F99-152_advAPL_v2.png&hash=0cfc2ae5aed14203f04d245a276a4f9bf8cea61e)
Here are some aerial photos I took on April 26, 2015.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5036.JPG&hash=c36422eaee476ad02e0e7a31f68d67a443f26c9c) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5036.JPG)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5037.JPG&hash=e7fc8ab35bbc7b027d313df80e78c55de7cf2ad2) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5037.JPG)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5038.JPG&hash=31774cb6afdfa7039a95289753ef3d7a71a91b8e) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5038.JPG)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5039.JPG&hash=270947f2e88545c1c3b8eaae9d7d446304a73a80) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5039.JPG)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5040.JPG&hash=cfce6a97a539845ad02be7c22b31de79e413a4ce) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5040.JPG)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fnaru.yamatonetwork.net%2FMapProjects%2FUS-CA%2FFresno%2FSAM_5041.JPG&hash=44b2babce87cce2ee02109653eb6b10a975d1855) (http://naru.yamatonetwork.net/MapProjects/US-CA/Fresno/SAM_5041.JPG)