Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: vdeane on October 21, 2023, 09:37:08 am
-
Poking around in street view, I noticed that signage is inconsistent around the east end of MD US40ScePin. Westbound is signed as we have it in TM, yet eastbound doesn't appear to show the turn to end at I-68, and has the end shield a block to the east (https://www.google.com/maps/@39.6974507,-78.2451884,3a,75y,84.09h,83.41t/data=!3m6!1e1!3m4!1s2kmLIS_WjUe52jpXarVXAQ!2e0!7i16384!8i8192?entry=ttu). Is there a way of verifying which is correct?
-
MDOT SHA GIS (https://maryland.maps.arcgis.com/apps/webappviewer/index.html?id=14f27a6cab51422dabdfb168ca603482) shows that MD144 as mapped is correct In GSV, I only see the one US-40 Scenic End sign disputing what is mapped, so I guess SHA/Washington County just put it in the wrong place.
Thus, I would vote "no-build."
-
It's worth noting here that US 40 Scenic is not actually a state highway. And thus, SHA has no official definition of it. The HLR log (https://roads.maryland.gov/OPPEN/2022%20Washington.pdf) doesn't even mention it at the MD 144 intersection, it's just "CO 1036 NATIONAL PIKE".
So, signs are all we really have to go by, and, well, in the face of some slight inconsistency I'm inclined to stick with the logical option of having the route actually return to US 40 itself rather than randomly end a tenth of a mile or so past the turnoff to it.
Either way it has a short MD144 concurrency so no clinchable mileage is gained or lost.