Regional Boards > Great Lakes and Ohio Valley
Ohio
PurdueBill:
--- Quote from: amroad17 on December 19, 2022, 03:03:09 AM ---The Ohio DOT district that is responsible for US 30 between Beaverdam and Upper Sandusky need to replace the mileage signs for Mansfield and Fort Wayne at each of the interchanges. It is approximately 150 miles between the two cities, as the correct mileages are shown at the OH 65 and OH 115 interchanges west of Beaverdam. The correct mileages should be at each interchange (Mansfield listed first then Ft. Wayne)...
-OH 696: 83-67 (shows 71-64)
-OH 235: 75-75 (shows 75-70)
-US 68 : 66-84 (shows 58-79 NB, 57-79 SB)
-OH 37 : 60-90 (shows 50-86)
-CR 330 : 51-99 (shows 43-99)
The mileage signs were correctly updated for Mansfield between Van Wert and just east of Delphos a few years ago. The Ft. Wayne mileage should be posted at 47 instead of 50 on the post interchange mileage sign on US 30 above Delphos.
Likewise, the post-interchange mileage signs on US 33 between Wapakoneta and St. Mary's should show Ft. Wayne five miles less than what is currently posted (62, 58, 54 heading WB on US 33). The Columbus-Ft. Wayne mileage sign at the Moulton interchange should have Ft. Wayne at 59 instead of 56.
There are others, not just in Ohio, but along I-86 in New York (Binghamton, Erie, and Jamestown--which I have mentioned on the I-86 and New York threads), some places in Virginia, in Kentucky, and in North Carolina.
I know I may be a bit OCD about mileage signs, however, I would just like to see more accuracy and consistency from the DOT's in our respective states.
--- End quote ---
It was interesting how the 1999-installed button copy sign on US 30 EB just after the Beaverdam exit said "Mansfield 70" and was patched to say "Mansfield 82" in the early 2010s, as does the new sign installed in fall 2017. 12 miles is a lot to be off by; is the difference on that particular one due to the reroutings as the dual carriageway was completed (OH 235 to US 23 in 2007; US 23 to Ontario in 2004)? The new road naturally runs a little longer with smoother curves and no hard corners, but 12 more miles seems high.
Mileages along the 2007-opened stretch may be off by using the older, shorter-distance routing of the 2-lane road--but those were outdated already as the 2007-opened stretch was the last "new" stretch on the way to Mansfield from Fort Wayne.
amroad17:
--- Quote from: PurdueBill on December 19, 2022, 07:47:13 PM ---
--- Quote from: amroad17 on December 19, 2022, 03:03:09 AM ---The Ohio DOT district that is responsible for US 30 between Beaverdam and Upper Sandusky need to replace the mileage signs for Mansfield and Fort Wayne at each of the interchanges. It is approximately 150 miles between the two cities, as the correct mileages are shown at the OH 65 and OH 115 interchanges west of Beaverdam. The correct mileages should be at each interchange (Mansfield listed first then Ft. Wayne)...
-OH 696: 83-67 (shows 71-64)
-OH 235: 75-75 (shows 75-70)
-US 68 : 66-84 (shows 58-79 NB, 57-79 SB)
-OH 37 : 60-90 (shows 50-86)
-CR 330 : 51-99 (shows 43-99)
The mileage signs were correctly updated for Mansfield between Van Wert and just east of Delphos a few years ago. The Ft. Wayne mileage should be posted at 47 instead of 50 on the post interchange mileage sign on US 30 above Delphos.
Likewise, the post-interchange mileage signs on US 33 between Wapakoneta and St. Mary's should show Ft. Wayne five miles less than what is currently posted (62, 58, 54 heading WB on US 33). The Columbus-Ft. Wayne mileage sign at the Moulton interchange should have Ft. Wayne at 59 instead of 56.
There are others, not just in Ohio, but along I-86 in New York (Binghamton, Erie, and Jamestown--which I have mentioned on the I-86 and New York threads), some places in Virginia, in Kentucky, and in North Carolina.
I know I may be a bit OCD about mileage signs, however, I would just like to see more accuracy and consistency from the DOT's in our respective states.
--- End quote ---
It was interesting how the 1999-installed button copy sign on US 30 EB just after the Beaverdam exit said "Mansfield 70" and was patched to say "Mansfield 82" in the early 2010s, as does the new sign installed in fall 2017. 12 miles is a lot to be off by; is the difference on that particular one due to the reroutings as the dual carriageway was completed (OH 235 to US 23 in 2007; US 23 to Ontario in 2004)? The new road naturally runs a little longer with smoother curves and no hard corners, but 12 more miles seems high.
Mileages along the 2007-opened stretch may be off by using the older, shorter-distance routing of the 2-lane road--but those were outdated already as the 2007-opened stretch was the last "new" stretch on the way to Mansfield from Fort Wayne.
--- End quote ---
The patch of Mansfield 82 is actually the correct mileage. Before the section of US 30 was opened between OH 235 and CR 330 west of Upper Sandusky, the mileage sign at the old stoplight at OH 235 and old US 30 had Mansfield at 66 miles, then just east of the old US 68/US 30 interchange in Williamstown (which is an at-grade intersection now), nine miles from OH 235, a mileage sign was posted with Upper Sandusky 19/Mansfield 61. That sign was probably more accurate with the way US 30 used to be routed instead of on the expressway between Upper Sandusky and Ontario. Now, based on the way US 30 is routed and using GoogleMaps Directions, Mansfield is right around 66 miles from the US 68/US 30 interchange.
It almost seems as if some of the DOT's "guess" at mileages between two points. Admittedly, Ohio DOT, when doing sign replacements, have corrected mileages--even if off by only one mile (examples: I-75 NB north of Exit 64, Toledo used to list 137-now listed at 138; I-75 SB south of Exit 110, the mileage sign used to be posted as Sidney 18/Cincinnati 109-now posted as Sidney 19/Dayton 56). Of course, the opposite instance has occurred with Xenia along US 35 WB. The mileage was correct on the mileage sign west of Palmer Road (26 miles). When the replacement Clearview sign was erected, Xenia had (has) a mileage of 22 because whomever designed the sign had based the mileage off the wrong posted number west of the OH 753 interchange, showing 27 miles for Xenia when it should be 31. However, the Dayton number did change from 47 to 49 on that last sign mentioned.
PurdueBill:
--- Quote from: amroad17 on December 20, 2022, 12:29:00 AM ---
--- Quote from: PurdueBill on December 19, 2022, 07:47:13 PM ---
--- Quote from: amroad17 on December 19, 2022, 03:03:09 AM ---The Ohio DOT district that is responsible for US 30 between Beaverdam and Upper Sandusky need to replace the mileage signs for Mansfield and Fort Wayne at each of the interchanges. It is approximately 150 miles between the two cities, as the correct mileages are shown at the OH 65 and OH 115 interchanges west of Beaverdam. The correct mileages should be at each interchange (Mansfield listed first then Ft. Wayne)...
-OH 696: 83-67 (shows 71-64)
-OH 235: 75-75 (shows 75-70)
-US 68 : 66-84 (shows 58-79 NB, 57-79 SB)
-OH 37 : 60-90 (shows 50-86)
-CR 330 : 51-99 (shows 43-99)
The mileage signs were correctly updated for Mansfield between Van Wert and just east of Delphos a few years ago. The Ft. Wayne mileage should be posted at 47 instead of 50 on the post interchange mileage sign on US 30 above Delphos.
Likewise, the post-interchange mileage signs on US 33 between Wapakoneta and St. Mary's should show Ft. Wayne five miles less than what is currently posted (62, 58, 54 heading WB on US 33). The Columbus-Ft. Wayne mileage sign at the Moulton interchange should have Ft. Wayne at 59 instead of 56.
There are others, not just in Ohio, but along I-86 in New York (Binghamton, Erie, and Jamestown--which I have mentioned on the I-86 and New York threads), some places in Virginia, in Kentucky, and in North Carolina.
I know I may be a bit OCD about mileage signs, however, I would just like to see more accuracy and consistency from the DOT's in our respective states.
--- End quote ---
It was interesting how the 1999-installed button copy sign on US 30 EB just after the Beaverdam exit said "Mansfield 70" and was patched to say "Mansfield 82" in the early 2010s, as does the new sign installed in fall 2017. 12 miles is a lot to be off by; is the difference on that particular one due to the reroutings as the dual carriageway was completed (OH 235 to US 23 in 2007; US 23 to Ontario in 2004)? The new road naturally runs a little longer with smoother curves and no hard corners, but 12 more miles seems high.
Mileages along the 2007-opened stretch may be off by using the older, shorter-distance routing of the 2-lane road--but those were outdated already as the 2007-opened stretch was the last "new" stretch on the way to Mansfield from Fort Wayne.
--- End quote ---
The patch of Mansfield 82 is actually the correct mileage. Before the section of US 30 was opened between OH 235 and CR 330 west of Upper Sandusky, the mileage sign at the old stoplight at OH 235 and old US 30 had Mansfield at 66 miles, then just east of the old US 68/US 30 interchange in Williamstown (which is an at-grade intersection now), nine miles from OH 235, a mileage sign was posted with Upper Sandusky 19/Mansfield 61. That sign was probably more accurate with the way US 30 used to be routed instead of on the expressway between Upper Sandusky and Ontario. Now, based on the way US 30 is routed and using GoogleMaps Directions, Mansfield is right around 66 miles from the US 68/US 30 interchange.
It almost seems as if some of the DOT's "guess" at mileages between two points. Admittedly, Ohio DOT, when doing sign replacements, have corrected mileages--even if off by only one mile (examples: I-75 NB north of Exit 64, Toledo used to list 137-now listed at 138; I-75 SB south of Exit 110, the mileage sign used to be posted as Sidney 18/Cincinnati 109-now posted as Sidney 19/Dayton 56). Of course, the opposite instance has occurred with Xenia along US 35 WB. The mileage was correct on the mileage sign west of Palmer Road (26 miles). When the replacement Clearview sign was erected, Xenia had (has) a mileage of 22 because whomever designed the sign had based the mileage off the wrong posted number west of the OH 753 interchange, showing 27 miles for Xenia when it should be 31. However, the Dayton number did change from 47 to 49 on that last sign mentioned.
--- End quote ---
Some others have changed over the years on US 30 from Delphos westward as they changed out button copy signs back around 2006 and then have since changed them out again. As they have rerouted in parts as the dual carriageways opened, it makes sense for them to adjust over time.
The "Mansfield 6" sign less than half a mile before the "Mansfield CORP LIMIT" is jarring if you don't consider that the mileage on signs is not to the town line.
amroad17:
^ Usually, Ohio signs their cities to their downtown areas. For example, on I-75 SB the first Cincinnati CORP LIMIT sign is just south of the Galbraith Rd. overpass at the 11 mile marker. However, the mileage for Cincinnati has always been posted to the downtown area. The last mileage sign for Cincinnati on I-75 SB is just north of the Monroe rest area at mm 28, posted at 28 miles.
This is different than New York State which usually posts the mileage to the city or village line. In this instance, the southern city line for Syracuse is around the 81 mm, just south of the I-81/I-481 interchange. Syracuse has been posted along I-81 NB as to that point, even though the downtown area is another three miles away (mm 84).
GCrites80s:
But then you have to change the signs when the city annexes.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version