Recent Posts

Pages: [1] 2 3 ... 10
1
Updates to Highway Data / Re: SD: truncate SD377?
« Last post by rickmastfan67 on Today at 08:06:17 am »
However, GMSV shows, and I saw, an End SD 377 sign at the southern park boundary.

All the historical GSV shows said 'END' shield there as far back as Oct '08.
3
Updates to Highway Data / SD: truncate SD377?
« Last post by oscar on Today at 02:12:32 am »
I traveled part of SD 44 yesterday, south of the Badlands National Park boundary. I turned north on SD 377, to get back to I-90 via SD 240.

TM has SD 377's south end at SD 44 (fine), and its north end at SD 240. However, GMSV shows, and I saw, an End SD 377 sign at the southern park boundary. Some much older 2013 GMSV imagery has SD 377 signage within the park, at the junction with SD 240. I didn't look back at that junction for whether there is still SD 377 signage there.
4
In-progress Highway Systems & Work / Re: usatr: United States select tourist routes
« Last post by Duke87 on April 25, 2024, 09:02:32 pm »
Not exactly trying to drop a new bomb in here, but what about adding the 49-mile drive in SF? https://en.wikipedia.org/wiki/49-Mile_Scenic_Drive

This is exactly the type of thing I absolutely do not want this system to scope creep into including. Random insignificant local nonsense that happens to have some signs, as opposed to the major multi-state spanning stuff like Great River Road that was the impetus for the system's creation.
5
Solved Highway data updates / Re: GRC: Extension of A3
« Last post by michih on April 25, 2024, 03:27:39 pm »
https://github.com/TravelMapping/HighwayData/pull/7359

It seems that no E route is on currency yet albeit the project is also called "E65". I spot a sign on the video with an "E " but w/o number :D
6
SC 5:  SC75Trk_E technically should be SC75Trk_N IMO.
7
In-progress Highway Systems & Work / Re: usatr: United States select tourist routes
« Last post by IMGoph on April 25, 2024, 01:14:07 pm »
Not exactly trying to drop a new bomb in here, but what about adding the 49-mile drive in SF? https://en.wikipedia.org/wiki/49-Mile_Scenic_Drive
8
I-277:  StoSt should be relabeled (also affects US 74 and NC 27)

US 64:  NC90>-NC90_Tay??

US 421:  NC16>-NC16_N

US 421 BUS (Wilkesboro):  At minimum, I recommend the following:

1.  Add a point at Speedway Rd for access to North Wilkesboro Speedway.  (also affects NC 115)
2.  Make the shaping point north of NC18/268_S visible and label it DSt_E or 6thSt_N.
3.  Add a point at CBD Loop for where NC 18 SB/NC 268 WB leaves US 421 BUS NB.

NC 10: The NC16Bus points should be S and N instead of W and E.

NC 16:
1. Consider replacing shaping points with visible points.
2.  IntWay>-IntDr
3. I think a point should be added at Charlottetowne Ave.
4. IdaDrv>-IdaDr
5.  A point should be added at the south end of the NC 16 freeway. (access to NC 273)
6. A point should be added at Rock Barn Rd.  (direct connection to I-40)
7.  WayChuRd should be slightly relocated.
8. AspDamRd>-AlsDamRd
9. Consider replacing WalLn with a nearby point. 
10. US421_E>-US421(286A)
11. NC268>-US421(286B)
12. US421BusWil>-US421Bus (optional IMO)
13. US421_W>-US421_N

NC 16 BUS (Conover):  7thSt>-7thStPl (I think)

NC 18:  I recommend moving the CBDLoop to the CBDLoop/Wilkesboro Blvd intersection where the directions split.  (also affects NC 268 obviously)

NC 75:  The shaping point east of NC 75 is unnecessary.  The one east of OldProRd should probably be made visible somewhere.

NC 84: 
1.  WedBroDr and the shaping point east of there probably have viable replacement places for a point.
2.  GSV indicates that KeeRd has been destroyed by subdivision development.

NC 115: I would change US421Bus_N to NC18/268.  Technically fine as-is though.

NC 163: Consider replacing shaping points with visible points.
10
Will craft the files tonight.  However, will hold off on submitting till I have some proof that 686A is actually signed.  I assume it will be, but want to play it safe.

EDIT: Well, FL-686A is CONFIRMED to be signed when the route opens.  TY GSV!
Pages: [1] 2 3 ... 10