21
Solved Highway data updates / Re: VA: US23 and US58AltAbi broken concurrency
« Last post by mikeandkristie on July 05, 2025, 05:20:29 pm »Thank you.
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
22
Updates to Highway Data / Re: ME: US 202 Truncated?
« Last post by yakra on July 05, 2025, 02:38:33 pm »US202 has ended at I-395 on paper for decades; Cameron Kaiser puts the truncation somewhere between 1986 and 1989.
When I was a new roadgeek, there was still signage at US2 if not elsewhere on Main St, but that's slowly been disappearing.
While the old overhead signage on 395 was arguably enough IMO to justify continuing US202 to its parent, the new signage you linked from the 395/9 connector topic, along with the END sign especially, clinches it (pardon the pun).
I'll submit this along with the 9 relocation in a couple days, saving some time to get up there & drive it for myself, even if this is all perfectly straightforward.
Routes ending in at an unnumbered road while on a useless multiplex aren't unheard of.
ME111 ending at Main St in Biddeford while concurrent with ME9 immediately comes to mind.
There's also the E end of ME154.
May be worth checking out ME100 in the field just for due diligence's sake.
When I was a new roadgeek, there was still signage at US2 if not elsewhere on Main St, but that's slowly been disappearing.
While the old overhead signage on 395 was arguably enough IMO to justify continuing US202 to its parent, the new signage you linked from the 395/9 connector topic, along with the END sign especially, clinches it (pardon the pun).
I'll submit this along with the 9 relocation in a couple days, saving some time to get up there & drive it for myself, even if this is all perfectly straightforward.
Quote
I wonder what this means for ME 100, since it ended at US 202 and now it just ends in an overlap for no reason.I bet it will stay the same. Old habits die hahd up heah.
Routes ending in at an unnumbered road while on a useless multiplex aren't unheard of.
ME111 ending at Main St in Biddeford while concurrent with ME9 immediately comes to mind.
There's also the E end of ME154.
May be worth checking out ME100 in the field just for due diligence's sake.
23
Solved Highway data updates / Re: TX: US-181 Harbor Bridge now OPEN
« Last post by yakra on July 05, 2025, 01:16:32 pm »https://github.com/TravelMapping/HighwayData/pull/8470
All pretty straightforward, except the I-37 terminus got a bit tricky.
The Statewide planning Map and grid map have the 37-181 transition at a point N of Carrizo St.
Shapefiles meanwhile show I-37 all the way to the 37S->181N ramp at the old bridge, just about exactly the existing terminus in the HB.
On AARoads, Chris posted a schematic (PDF here). If we take the non-Interstate-grade looking RIRO at Tancahua St to be the end, that's the most de minimis change from what's in the HB now; within the footprint of the existing interchange & not even newsworthy.
Other points and labels near the S end could probably use a cleanup, but I'll hold off on that until the dust settles and the real exit numbers become known.
All pretty straightforward, except the I-37 terminus got a bit tricky.
The Statewide planning Map and grid map have the 37-181 transition at a point N of Carrizo St.
Shapefiles meanwhile show I-37 all the way to the 37S->181N ramp at the old bridge, just about exactly the existing terminus in the HB.
On AARoads, Chris posted a schematic (PDF here). If we take the non-Interstate-grade looking RIRO at Tancahua St to be the end, that's the most de minimis change from what's in the HB now; within the footprint of the existing interchange & not even newsworthy.
Other points and labels near the S end could probably use a cleanup, but I'll hold off on that until the dust settles and the real exit numbers become known.
24
Solved Highway data updates / Re: VA: US 311 rerouted to US 58 Bypass
« Last post by Jim on July 05, 2025, 09:42:50 am »I didn't notice it was a new file, so it didn't get into the repository. I'm about to launch a site update that will include it (and other things that came in overnight).
25
Solved Highway data updates / Re: VA/WV: VA/WV-83 transition in wrong place???
« Last post by rickmastfan67 on July 05, 2025, 04:00:41 am »WV side submitted.
https://github.com/TravelMapping/HighwayData/pull/8469
https://github.com/TravelMapping/HighwayData/pull/8469
26
Solved Highway data updates / Re: VA: US 311 rerouted to US 58 Bypass
« Last post by rickmastfan67 on July 05, 2025, 03:36:34 am »Seems like this file didn't get submitted, while it's changes in 'usausb' were, causing a site update breakage?
https://github.com/TravelMapping/HighwayData/commit/8f2fcf885b203f0edcd5fec8d38e61dea174344f
https://github.com/TravelMapping/HighwayData/commit/8f2fcf885b203f0edcd5fec8d38e61dea174344f
27
Solved Highway data updates / Re: VA/WV: VA/WV-83 transition in wrong place???
« Last post by rickmastfan67 on July 05, 2025, 03:30:53 am »^ Looks like what he sent is live, so should be able to just grab them from Github...
Isn't live on the site. Just only in Github. Guess something else broke the update. (EDIT: Yeah, I see what broke it, the new VA US-311 Alt file was missing.)
Still, will submit my end in a little bit.
28
Solved Highway data updates / Re: VA/WV: VA/WV-83 transition in wrong place???
« Last post by froggie on July 05, 2025, 12:45:49 am »^ Looks like what he sent is live, so should be able to just grab them from Github...
29
Solved Highway data updates / Re: VA/WV: VA/WV-83 transition in wrong place???
« Last post by rickmastfan67 on July 04, 2025, 11:04:44 pm »I moved the state line point to the pavement change location, renamed the former state line location as DivRidRd, and added DavMouRd to the file...
Can you post the coordinates you used for the new border point so I can make sure WV is synced?
30
Solved Highway data updates / Re: NC US221 missing interchange
« Last post by mapmikey on July 04, 2025, 03:34:29 pm »fixed