Recent Posts

Pages: 1 ... 8 9 [10]
91
Solved Highway data updates / Re: SD: truncate SD377?
« Last post by oscar on April 29, 2024, 08:36:17 am »
FWIW, the next day in Fort Pierre, I saw an End sign for SD 1806 at the US 14/SD 34 junction. Then a few blocks east, the sign assembly has SD 1806 continuing south onto US 83. Maybe SDDOT doesn't take END signs as seriously as we do in other jurisdictions?

So leaving SD 377 alone would be defensible, in the absence of other data like official route definitions, and considering that SD 240 is signed within Badlands National Park.
92
Updates to Highway Data / Re: FL: FL 686A/FL 690 (Gateway Expressway) Opening April 26th
« Last post by AARoads on April 27, 2024, 03:40:58 pm »
Quote from: rickmastfan67 on April 24, 2024, 10:04:27 pm
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!

SR 686A signage was first posted in 2020: https://www.aaroads.com/guides/fl-686a/
Drove SR 686A and SR 690 in both directions yesterday. There are no reassurance markers, but the mile markers reference each route.

There was also an erroneous SR 686 Toll shield posted on SR 688/Ulmerton Road east at least three years ago. Not sure if it is still there, as I didn't check yesterday.
93
Solved Highway data updates / Re: SD: truncate SD377?
« Last post by rickmastfan67 on April 27, 2024, 08:06:17 am »
Quote from: oscar on April 27, 2024, 02:12:32 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.
94
Updates to Highway Data / Re: FL: FL 686A/FL 690 (Gateway Expressway) Opening April 26th
« Last post by rickmastfan67 on April 27, 2024, 08:02:10 am »
Now submitted.

https://github.com/TravelMapping/HighwayData/pull/7362
95
Solved Highway data updates / SD: truncate SD377?
« Last post by oscar on April 27, 2024, 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.
96
In-progress Highway Systems & Work / Re: usatr: United States select tourist routes
« Last post by Duke87 on April 25, 2024, 09:02:32 pm »
Quote from: 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

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.
97
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
98
Updates to Highway Data / SC: Various Route Concerns in Charlotte, NC, Metropolitan Area
« Last post by Markkos1992 on April 25, 2024, 01:23:38 pm »
US 21: S-27-98>-GoldHillRd

US 21 BUS (Fort Mill): 
1.  WhiSt>-WhiSt_S
2.  Is there a better point location than RicSt?

SC 5:  SC75Trk_E technically should be SC75Trk_N IMO.

SC 49:  Replace the shaping point near SC/NC with a visible point at Blucher Circle (BluCir).

SC 121:  I am tempted to recommend SC322 instead of US21/322.

SC 274:  PolBraRd>-PoleBraRd

SC 460: 
1. I do not think that WolTrl is correct.
2.  Should the route be flipped?

99
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
100
Updates to Highway Data / NC: Various Point Concerns Around Charlotte and along NC 16 and US 21
« Last post by Markkos1992 on April 25, 2024, 08:44:02 am »
I-277:  StoSt should be relabeled (also affects US 74 and NC 27)

US 21: 
1.  CatAve>-CatAve_E
2.  Consider replacing BraPlDr with Oates Rd (OatRd) to the south.
3.  MurSt>-MurRd
4.  A point should be added at Amity Hill Rd.  (signed access to I-77)
5.  US64>-US64_E
6.  CouClubRd>-CouClubDr
7.  NC1910>-CenChuRd_S. CenChuRd>-CenChuRd_N.
8.  DoeRun should probably be replaced.  DavDr probably is best left as-is.

US 21 BUS (Elkin):  ValRd>-ValDr

US 29:  NC49_E>-NC49_N

US 64: 
1.  NC90>-NC90_Tay??
2.  US21>-US21_N

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 3:
1.  Consider replacing shaping points with visible points.
2.  WakeDr should be replaced by WinRd (Windy Rd) nearby.
3.  Consider adding a point at Roxie St (direct connection from I-85 Exit 60 SB offramp) (CouClubDr covers Copperfield Blvd IMO).

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 (Lucia): 
1.  Consider replacing shaping points with visible points.
2.  FaiForRd>-WebRd

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 49:
1.  Consider replacing the shaping point north of SC/NC with a visible point.
2.  NC160>-NC160_S
3.  MooSt_E>-MorSt_E
4.  GraSt>-GraSt_N (also affects US 29)
5.  TrySt>-TrySt_S (also affects US 29)

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:
1.  Should a point be added at Verhoeff Dr?  (maybe add to US 21 as well)
2.  Maybe add a point at Mount Holly-Huntersville Rd (MHHunRd). (direct access to interchange at US 21)
3.  I would change US421Bus_N to NC18/268.  Technically fine as-is though.

NC 163: Consider replacing shaping points with visible points.

NC 268: StiMeaRd>-StiMeaLn

NC 268 BUS (Elkin):  The US21Bus_S and US21Bus_N labels should be switched.

NC 273: 
1.  KeeBlvd>-KeeBlvd_W
2.  Consider replacing shaping points with visible points.
3.  I think that MainSt should be replaced with TucRd to the south.
4.  Should CarAve be removed or replaced?
Pages: 1 ... 8 9 [10]