91
General Web Design Discussion / Re: Clinched Routes Highway Shields
« Last post by CoreySamson on August 31, 2025, 03:36:18 pm »Looks fine on my end (Safari).
News:
Travel Mapping's main site is at https://travelmapping.net/ . Old tm.teresco.org URLs and http:// URLs are redirected there, and will continue to work indefinitely.
Recent Posts
92
General Web Design Discussion / Re: Clinched Routes Highway Shields
« Last post by Jim on August 31, 2025, 08:17:09 am »Looks like chng needs work to make 4 digit routes fit:What seems to be the issue? It looks just fine on my end.
https://travelmapping.net/hb/showroute.php?r=chnzj.g9211
I see it as attached.
93
General Web Design Discussion / Re: Clinched Routes Highway Shields
« Last post by cockroachking on August 30, 2025, 10:55:09 pm »Looks like chng needs work to make 4 digit routes fit:What seems to be the issue? It looks just fine on my end.
https://travelmapping.net/hb/showroute.php?r=chnzj.g9211
94
Updates to Highway Data / Re: OK: I-44 and OK 20
« Last post by CoreySamson on August 30, 2025, 08:23:59 pm »Bumping... I can personally confirm that this section is open, but I have a little morsel of information that I would like to share about the project. I found an "END OK 20" shield at the interchange heading EB, which I suppose could only mean two things:
1. OTA made a sign goof
2. There is a poorly signed spur route of OK 20 running from exit 252 to OK 20 at Frederick Road
I'm more inclined to believe the former, that OTA mistakenly thought that OK 20 ended at the new interchange (which would explain why the exit is signed for OK 20), rather than there being a whole new spur route. As radison said below, I'll leave that to how you see fit.
I documented the sign in this post on the AARoads forum:
https://www.aaroads.com/forum/index.php?topic=87.msg2999681;topicseen#msg2999681
1. OTA made a sign goof
2. There is a poorly signed spur route of OK 20 running from exit 252 to OK 20 at Frederick Road
I'm more inclined to believe the former, that OTA mistakenly thought that OK 20 ended at the new interchange (which would explain why the exit is signed for OK 20), rather than there being a whole new spur route. As radison said below, I'll leave that to how you see fit.
I documented the sign in this post on the AARoads forum:
https://www.aaroads.com/forum/index.php?topic=87.msg2999681;topicseen#msg2999681
95
Updates to Highway Data / OH: OH 93 in Ironton
« Last post by aterrypenak on August 29, 2025, 07:42:36 pm »The route we have as OH 93 between the Kentucky state line and US 52 is consistently signed as "To OH 93" (see https://maps.app.goo.gl/gsCnjp9kTcPF8cZJ9 https://maps.app.goo.gl/yACNeJu1PrzZvXPw8; the imagery is a little old, but I saw the same thing driving through yesterday.) I was driving northbound, so I didn't look for southbound signage, but I don't see any in Street View south of the roundabouts at US 52. (I also don't see an END sign anywhere.) Is that part of the route still OH 93, or was it truncated at some point?
96
Updates to Highway Data / Re: MS: US 82/278 Greenville Bypass
« Last post by rlee on August 29, 2025, 03:20:47 pm »Greenville bypass now open to the public. The former route segment of US 82 to be redesignated as MS 182. https://mdot.ms.gov/portal/news_release_view/2439
Video and story from WABG
97
Other Discussion / Re: New Travels and Stats Discussion
« Last post by Markkos1992 on August 29, 2025, 07:51:31 am »I am finally done with my trip report for the Springfield, IL, Meet back in June.
So finally onto my Nashville, TN, trip that I skipped the Brattleboro Meet for.
I finished the Nashville trip last night.
98
Updates to Highway Data / MI: US-10 issues
« Last post by rickmastfan67 on August 29, 2025, 05:14:51 am »MainStCus -> MainSt_Cus
DepSt -> on wrong road, move west to the actual road
MainStEva -> MainSt_Eva
US127_S -> 158(127)
DepSt -> on wrong road, move west to the actual road
MainStEva -> MainSt_Eva
US127_S -> 158(127)
99
Updates to Highway Data / MI: M-59 issues
« Last post by rickmastfan67 on August 29, 2025, 05:01:22 am »LatRd -> recenter. Well east of the actual intersection
LivRd -> remove (no road by that name there), replace with 'FenRd' or 'PleValRd' to the east
WimRd -> WatRd
OrmlRd -> OrmRd and recenter to intersection
WilLakeRd -> recenter. Way, way, way too far east of the actual intersection.
NoyDr -> recenter, on the wrong road
? -> maybe add a point between MI53 & MI97 to cut down that 7 mile gap between points? Maybe @ RomPlaRd?
LivRd -> remove (no road by that name there), replace with 'FenRd' or 'PleValRd' to the east
WimRd -> WatRd
OrmlRd -> OrmRd and recenter to intersection
WilLakeRd -> recenter. Way, way, way too far east of the actual intersection.
NoyDr -> recenter, on the wrong road
? -> maybe add a point between MI53 & MI97 to cut down that 7 mile gap between points? Maybe @ RomPlaRd?
100
Updates to Highway Data / MI: I-96 issues
« Last post by rickmastfan67 on August 29, 2025, 04:42:38 am »122 -> needs a recenter badly. Would need fixed in M-43 & M-52.
141 -> needs centered in the middle of I-96 instead of on the WB lanes. Would need fixed in "MI I-96BLHow" too.
===
MI I-96BLHow:
MichAve -> MicAve (& slightly recenter)
GolCluRd -> GolfClubRd (& slightly recenter)
missing -> LatRd (connects to I-96 Exit 140)
missing -> GraRivAve_E (where the ramps from I-96 Exit 141 connects)
141 -> needs centered in the middle of I-96 instead of on the WB lanes. Would need fixed in "MI I-96BLHow" too.
===
MI I-96BLHow:
MichAve -> MicAve (& slightly recenter)
GolCluRd -> GolfClubRd (& slightly recenter)
missing -> LatRd (connects to I-96 Exit 140)
missing -> GraRivAve_E (where the ramps from I-96 Exit 141 connects)