Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Jim on January 09, 2018, 09:55:03 pm
-
Heading north/east out of Woodsville, New Hampshire 10 is co-signed with US 302. TM has 10 ending at the 302 junction. I turned on NH 112, but the signs for traffic continuing from there still showed both NH 10 and US 302.
-
http://clinched.s2.bizhat.com/viewtopic.php?p=5931&mforum=clinched#5931
http://clinched.s2.bizhat.com/viewtopic.php?p=5922&mforum=clinched#5922 :)
-
Cosigned all the way to I-93 in Littleton. Now, whether one believes the relatively recent signage or the NH route log Eric referenced in that CHM thread, that is the question.
-
Cosigned all the way to I-93 in Littleton. Now, whether one believes the relatively recent signage
What I see in the latest GMSV is the same as I saw on my trip through in May 2008.
Cosigned all the way to I-93 in Littleton, yes; even as (https://www.google.com/maps/@44.3084121,-71.7811709,3a,15y,270.52h,87.58t/data=!3m9!1e1!3m7!1sHGtVHFAvyqw5yTZY8Qco9Q!2e0!7i13312!8i6656!9m2!1b1!2i41) far (https://www.google.com/maps/@44.3083705,-71.7819654,3a,54.5y,265.75h,79.68t/data=!3m9!1e1!3m7!1sftUY7MRptyjOx6yAg2rLgg!2e0!7i13312!8i6656!9m2!1b1!2i41) as NH US302 NH18_N.
...And then the trail goes cold. Over here (https://www.google.com/maps/@44.3060909,-71.7703168,3a,23y,11.23h,87.84t/data=!3m10!1e1!3m8!1s0soRbQzkauLsH6Mb2lBokA!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3D0soRbQzkauLsH6Mb2lBokA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D104.63277%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i41), no (https://www.google.com/maps/@44.3061282,-71.7699356,3a,15y,270.26h,92.16t/data=!3m9!1e1!3m7!1sgUtZ7bvgt5uM-EFj8gXnHw!2e0!7i13312!8i6656!9m2!1b1!2i41) mention (https://www.google.com/maps/@44.3047171,-71.7698016,3a,36.1y,175.81h,95.83t/data=!3m9!1e1!3m7!1sE8SIGWVIcL43Gg4JZIZzaA!2e0!7i13312!8i6656!9m2!1b1!2i41).
I'm not against extending NH10 per se; I'd just want to be sure that if we do, it's well-considered & well-founded, to a sensible point, and not something we'd end up walking back later on.
or the NH route log Eric referenced in that CHM thread, that is the question.
The roadgeek.org reference can be found on archive.org. (http://web.archive.org/web/20080827233259/http://www.roadgeek.org/nhroads/nh_1-25.html)
Wikipedia's cite, ISTR was never, even then, something I was able to access or view, and I just included it in the CHM thread to say "Hey, here's the source of that info."
What's Wikipedia's cite now? The GRANIT shapefiles. Thus I can't really call their figure of 122.476 mi definitive -- NH10 may have higher mileage than that, which just won't be shown in the file due to US302's mileage being shown instead.
What DO I see in the shapefiles? There's the STREET_ALI attribute, which stores route numbers carried by a particular segment of roadway.
• Main St is "NH 10,NH 18,US 302"
• US302 is "NH 10,NH 116,NH 18,US 302" (with a little "NH 10,NH 142,US 302" thrown in, right where you'd expect) right up to the NH18/116 split.
• "NH 10,US 302" right up to US3, ending there. Plain as day.
So it's pretty clear that at least in some capacity, NH10 officially goes to US3 in Twin Mountain / Carroll.
Damn that gaping lack of signage, though. >:( Annoyingly puts this somewhat into "unsigned routes" territory.
May the discussion continue...
-
OK, looked a bit, and found signage for NH 10 at the eastern I-93 interchange in 2008 (https://www.google.com/maps/@44.2840074,-71.7428114,3a,31.5y,338.98h,88.39t/data=!3m6!1e1!3m4!1sumWrrtmlcpG9rldeAMeiTQ!2e0!7i3328!8i1664) but not in 2014 (https://www.google.com/maps/@44.2833669,-71.7421929,3a,15y,317.27h,88.93t/data=!3m6!1e1!3m4!1sVv47BYCrJCy551-jKF2RzQ!2e0!7i13312!8i6656) (you have to look kinda through the grass).
I'm not sure if this will help or not.
-
Oh wow. Wasn't aware of anything this far east.
This (https://www.google.com/maps/@44.2850079,-71.7450866,3a,52y,166h,93.72t/data=!3m9!1e1!3m7!1svpSZYB2GedU5beNxjIcB2g!2e0!7i3328!8i1664!9m2!1b1!2i41) sign (https://www.google.com/maps/@44.2850959,-71.7451119,3a,31.9y,155h,91.81t/data=!3m9!1e1!3m7!1s_n8SdNTkM-7xjkhk-yd9cA!2e0!7i13312!8i6656!9m2!1b1!2i41) also changed between Oct 2008 & Sep 2013.
Seems that NHDOT is getting even more consistent about the northeastern leg being unsigned.
I could possibly be talked into extending NH10 up to NH18 in Littleton...
-
Given your own comments from Sunday, I think it's safe to extend it at least to the western I-93 interchange.
-
You talked me into it. :D
https://github.com/TravelMapping/HighwayData/pull/1826
Heh - US302 already used NH10_S as a label, unnoticed all these years...
Along for the ride: NH US302BusBar gets deleted.
-
The extension to NH18 is live in the HB.
This sign (https://www.google.com/maps/@44.3082839,-71.7966914,3a,46y,77.28h,88.78t/data=!3m10!1e1!3m8!1shsUWeIxhyKoHw8X4Ghwq0w!2e0!6s%2F%2Fgeo3.ggpht.com%2Fcbk%3Fpanoid%3DhsUWeIxhyKoHw8X4Ghwq0w%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D271.6357%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i41) also makes me confident in extending it past the western I-93 interchange.
I've made a new pull request (https://github.com/TravelMapping/HighwayData/pull/1831) to relabel I-93(42) -> I-93.
-
Topic marked as solved.