Author Topic: usasc: South Carolina State highways  (Read 41879 times)

0 Members and 1 Guest are viewing this topic.

Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: usasc: South Carolina State highways
« Reply #75 on: October 29, 2019, 08:38:46 am »
Quote
US29ConGree is 2 points over from US29ConGreen.  I don't know if there was a US29ConGre previously that precipitated these two designations (I had no involvement with the US route set in SC).
ISTR back in the CHM days a bunch of US route connectors were found to be unsigned, and thus removed from the HB.
With no actual routes intersecting here, we'd just use street names, I.E. WadeHamBlvd_S & PineKnoDr.
I also see a US29Spr point label with no corresponding route in the HB.
There may well be other cases lurking around the state (It could be possible with some effort to search for these programmatically, with the caveat that SC's 26 NMP pairs (a relatively small amount, not insurmountable) could throw some wrenches in the works. Or maybe not -- the only bannered US route label in these NMPs is a legitimate extant business route...)

Looking at GMSV, PineKnoDr is signed from US 276 as US 29 South.  Wade Hampton Blvd was signed from US 276 as US 29 North up until at least 2016.  Greenville has over the years removed more and more route signage.  The US 29 ConGreen is signed as SC 291 South from US 29.


Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: usasc: South Carolina State highways
« Reply #76 on: October 29, 2019, 12:48:38 pm »
Hoo boy...
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #77 on: October 29, 2019, 05:11:31 pm »
I am trying to update my list file and work on the review tonight.  We will see how this works.

SC 602: (actually ends at US 21 CON)
1.  RamRd should be slightly relocated.
2.  JohHarExp should be JohnHarExp.

SC 641: (actually posted east-west)
1.  MilSwaChuRd needs to be shortened.
2.  I would change S-5-8 to State Park Rd (StaParkRd) based on the SCDOT Street Finder because I did not see a blade for S-5-8.

SC 642:
1.  The US17Alt point needs to be relocated to the new intersection.  (also affects US 17 ALT TRUCK (Summerville))
2.  Old Trolley Rd (OldTroRd) is correct based on the SCDOT Street Finder, but GSV shows it as just Trolley Rd (TroRd).
3.  I would consider a point at Cross County Rd (CroCouRd) for better shaping.
4.  WHilBlv should be HillBlvd.
5.  +X001 should be replaced with a point at Montague Ave (MonAve_W).  MonAve then becomes MonAve_E.

SC 692:
1.  CatBlv should be CatBlvd.

SC 700:
1.  +X001 could easily be replaced by a visible point at Boy Scout Rd (BoyScoRd).
2. MaiRd should be MainRd.

SC 702:
1.  LakGreStPk should be LakeGreSP or State Park Rd (StaParkRd). (roadname based on SCDOT Street Finder)
2.  AulMilRd should be AullMillRd.

SC 703: (should be flipped)
1.  JasBlv should be JasBlvd_W.
2.  PatPoiBlv should be PatPoiRd.

SC 707:
1.  I would add a point at Holmestown Rd (HolRd) due to the connection to US 17 and US 17 BUS.
2.  A point will be needed at SC 31 when its extension opens.
3.  DicPonRd should be DickPondRd.

SC 742: (should maybe be flipped...)
1.  SC145 should be recentered.

SC 760:
1.  Wildcat Rd should be added as it seems to be a US 76 CON as shown on the SCDOT Street Finder.

SC 763:
1.  I would add a point at Deschamps Rd (DesRd) as the route is dangerously close to going out of tolerance just to the west.
2.  The SC 120 points should be W and E instead of S and N.

SC 764:  (should probably be flipped)

SC 768:
1.  ShoRd should be ShoRd_W.
2.  PinDr should be PinRd_S. (though the SC 48 PinDr point was left the same earlier, the blade there supports PinRd as well, the Street Finder supports PinDr.  I would support at minimum relocating the PinDr point on SC 48.)

SC 769:
1.  +X001 should be replaced with a visible point at Elm Savannah Rd (ElmSavRd).  (based on SCDOT Street Finder)
2.  AirBasRd should be AirBaseRd.
3.  +X002 should be replaced with a visible point at Crossing Creek Rd (CroCreRd).

SC 781:
1.  The US78 point needs to be relocated due to an intersection realignment.

SC 802:
1.  AlsRd should be slightly relocated.

SC 823:
1.  CirARanRd should be shortened.
2.  I would change S-33-38 to Old Charleston Rd (OldChaRd) as I did not see a black blade.  I would also slightly relocate it.
3.  I would add a point at White Creek Rd (WhiCreRd) as the route is dangerously close to going out of tolerance here.

SC 901:
1.  GolCouRd should be DeWRd (DeWitt Rd) based on the SCDOT Street Finder.
2.  I would add a point at William Martin Rd (WilMarRd) based on the SCDOT Street Finder as the route is dangerously close to going out of tolerance here.
3.  BeaRd should be BeaDamRd.
4.  I would add a point at Hunter Rd (HunRd) based on the SCDOT Street Finder as the route is dangerously close to going out of tolerance here.
5.  OldMilRd should be OldMillRd.
6.  ReiRd should be ReidRd.

SC 903:
1.  I would consider points at Mining Rd (MinRd) and Fork Hill Rd for better shaping.
2.  TaxRd should be PotRd (Potter Rd).

SC 905:
1.  ECouCluDr should be CouClubDr.
2.  BucCreDr should be BuckCreDr.

SC 908: (should probably be flipped)
1.  +X001 could easily be replaced with a visible point at Reason Rd (ReaRd).

SC 909: (needs to be flipped)
1.  Based on the SCDOT Street Finder and the lack of a black blade, I would change S-12-1 to OldYorkRd_S.
2.  DarRd should be recentered.
3.  The SCDOT Street Finder indicates that SteVilRd should be MilRd (Millen Rd).
4.   BlaRd should be slightly relocated.

SC 912: (should maybe be flipped)
1.  I would add points at McCalls Mill Pond Rd, Old River Rd (OldRivRd), and Brickyard Rd (BriRd) for better shaping.

SC 917:
1.  S-26-19 should considered being renamed as Hwy19.  I think S-26-19 is correct based on SC 905.
2.  LakSwaRd should be LakeSwaRd.
3.  PeeDeeHwy should be PeeDeeRd.
4.  BarRd should be BarnRd.
5.  Apparently HenSt should be HenExt.
6.  +X001 should be replaced by a visible point at Cattle Farm Rd (CatFarmRd).
« Last Edit: October 31, 2019, 06:51:36 pm by Markkos1992 »

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #78 on: October 31, 2019, 06:53:11 pm »
I have finished going through all the SC State Highways through SC 917.  Once all the edits are caught up, I will check NMPs and let yakra do his grepping labels project.


Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: usasc: South Carolina State highways
« Reply #79 on: November 02, 2019, 03:44:20 pm »
I have submitted all changes through SC 917 this afternoon to Jim.  Hopefully I got everything...

Thank you again for the hard detailed look at the SC state route set...

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #80 on: November 02, 2019, 09:35:49 pm »
NMP Notes:
1.  sc.us521@US521BusKer_N 34.561925 -80.587545
sc.us521busker@US521_N 34.561925 -80.58754

(Seems to be simple enough to fix, but I am unsure of the validity of the nearby US521ConKer points on both routes.  I cannot find an official road name or designation on the SCDOT Street Finder.)

2.  sc.sc009@SC72/121_N 34.706361 -81.190803
sc.sc072@SC9_S 34.706414 -81.190803
sc.sc009@SC72/121_N 34.706361 -81.190803
sc.sc097@SC9_S 34.706414 -81.190803
sc.sc009@SC72/121_N 34.706361 -81.190803
sc.sc121@SC9_S 34.706414 -81.190803
sc.sc009busche@SC9_S 34.706361 -81.190803
sc.sc072@SC9_S 34.706414 -81.190803
sc.sc009busche@SC9_S 34.706361 -81.190803
sc.sc097@SC9_S 34.706414 -81.190803
sc.sc009busche@SC9_S 34.706361 -81.190803
sc.sc121@SC9_S 34.706414 -81.190803

(SC 72, SC 97, and SC 121 still need to be synced with SC 9 and SC 9 BUS (Chester).  The coordinates for SC 9 and SC 9 BUS (Chester) should be used here.)

3. sc.i020@131 34.206186 -80.026292
sc.us401@I-20(131) 34.206159 -80.026217

(US 401 should be synced with I-20 here.)

4.  sc.sc022@US501 33.92046 -79.153683
sc.us501@SC22 33.920625 -79.15379

(Either point works fine here as long as they are synced.)

5.  sc.i026@15 35.027132 -82.035202
sc.us176@I-26(15) 35.027044 -82.03517

(The US 176 point should be synced with the I-26 point.)

6. sc.sc183@US178_E 34.88374 -82.707377
sc.sc183@US178_W 34.883645 -82.707732
sc.sc183@US178_E 34.88374 -82.707377
sc.us178@SC183_W 34.883645 -82.707732
sc.sc183@US178_W 34.883645 -82.707732
sc.us178@SC183_E 34.88374 -82.707377
sc.us178@SC183_E 34.88374 -82.707377
sc.us178@SC183_W 34.883645 -82.707732

(FPs, though on US 178, SC183_W should be SC183_S, and SC183_E should be SC183_N.)

7.  sc.sc003busspr@SC4_W 33.496662 -81.279323
sc.sc004@SC39_N 33.496539 -81.279639
sc.sc003busspr@SC4_W 33.496662 -81.279323
sc.sc039@SC4_E 33.496539 -81.279639
sc.sc004@SC39_N 33.496539 -81.279639
sc.sc004@SC3Bus_S 33.496662 -81.279323
sc.sc004@SC3Bus_S 33.496662 -81.279323
sc.sc039@SC4_E 33.496539 -81.279639

(FPs)

8.  sc.sc217@US21_N 33.089382 -80.813539
sc.sc217@US21_S 33.089157 -80.813446
sc.sc217@US21_N 33.089382 -80.813539
sc.us021@SC217_N 33.089157 -80.813446
sc.sc217@US21_S 33.089157 -80.813446
sc.us021@SC217_S 33.089382 -80.813539
sc.us021@SC217_N 33.089157 -80.813446
sc.us021@SC217_S 33.089382 -80.813539

(FPs, though I did see a SC5_W on US 21 while quickly looking that should be SC5_N.)

9.  sc.sc304@US78Bus 33.355025 -81.26943
sc.us078busbla@SC304 33.355025 -81.269432

(These should be synced with each other.)

10.  sc.us017@US78 32.796089 -79.943836
sc.us078@US17 32.796296 -79.944061

(These should be synced with each other since US 78 is King St.  I do not think I-26 should get a point here though.)

11.  sc.sc171@ArtAve 32.654985 -79.940525
sc.sc171@AshAve 32.65545 -79.940761

(FPs)

12.  ga.ga150@GA/SC 33.6612 -82.199836 LI
sc.us221@GA/SC 33.661201 -82.199836 LI
ga.us221@GA/SC 33.6612 -82.199836 LI
sc.us221@GA/SC 33.661201 -82.199836 LI

(These should have been synced previously.)



Last Submission Comments:  (I did this just using the commit for the most part if you are wondering why this was done before the 11/2/2019 update.)
SC 642:
1.   FortDorSP seems to be signed as the Colonial Dorchester State Historic Site (ColDorSHS).  (label would be based on CTLanSHS from SC 171)
2.  HillBlv should be HillBlvd.
SC 703:  JasBlvd should be JasBlvd_W. (Clarified with the SCDOT Street Finder)
SC 707: I have not seen an official opening date for the SC 31 extension.  While I doubt there is an issue with making the point visible now, I would have waited until it opened.
SC 763: Technically StPChuRd should be SPChuRd.
SC 905: CouCluDr should be CouClubDr.

Unused Alternate Labels:  (may as well be cleaned up while we are at it though these are mostly unrelated to usasc)
sc.i077(1): 82
sc.i074futmyr(1): WATTOWRD
sc.us001(3): 2NDST N9THST US521/601TRK_S
sc.us017(2): US21/17ALT_N US701/17ALT_N
sc.us021(4): SC217_E SC217_W US17CON US21BUSROC_S
sc.us025(4): I-520CON S-19-29 SC125CON US25/276CON
sc.us052(1): 2NDST
sc.us076(8 ): I-126(GREYBLVD) SC14_S SC187_S SC20_N SC20_S SC28BUSPEN_N SC28BUSPEN_S SC28BUS_S
sc.us176(2): SC49 SC496
sc.us178(1): US178/378CON
sc.us221(4): S-33-26 S-33-70 SC10_S US221/176CONSPA
sc.us321(1): SC9BUSCHE_W
sc.us378(1): N9THST
sc.us521(9): MAINST MCILWRD OLDCHURD SC522_N SC522_S SGUIPKWY US1/521TRK US15/521CON US521/601TRK_N
sc.us601(1): US521/601TRK_S
sc.us001trkaik(1): ARBCT
sc.us001trkcam(1): YORKST
sc.us017altsum(2): SC63_E SC642
sc.us078busbla(1): MAINST
sc.us078trkaik(1): ARBCT
sc.us178busora(1): US21/178CON
sc.us221trklau(1): SHARSTEXT
sc.us321busche(3): SC97/97BUS SC9BUS_E SC9BUS_W
sc.us378buslak(1): SC341_E
sc.us521busker(1): SC157
sc.us521buslan(3): BARST MAINST SC9BUS_W
sc.us521trkcam(2): CHEFERRD US1_S
sc.us601busker(1): SC157
sc.sc028(2): I-85(19) SC88
sc.sc763(1): US15/521

« Last Edit: November 03, 2019, 05:36:29 pm by Markkos1992 »

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #81 on: November 07, 2019, 07:03:07 am »
The extension of SC 31 is expected to open this weekend.  You may as well leave the new point on SC 707 as-is at this point. 

I guess an updates entry will still be needed for SC 31 whether we activate usasc or not since it is in usansf.

EDIT:  It is now open.
« Last Edit: November 08, 2019, 08:37:31 pm by Markkos1992 »

Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: usasc: South Carolina State highways
« Reply #82 on: November 16, 2019, 09:44:43 pm »
Everything addressed from two posts above except the GA syncing...

The US 521 Con is shown explicitly on the SCDOT map of Kershaw - http://info2.scdot.org//GISMapping/GISMapdl/KERSHAW_2017.pdf

SC 31 extension also added and in the queue

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #83 on: November 17, 2019, 01:38:07 pm »
The only thing I see missed is the US 501/SC 22 NMP.  Otherwise I directed ntallyn here from the GA State Highways thread for the US 221/GA 150

I will probably upload the other NMPs into the nmpfps.log file later this week.  Also I plan to look further into the VA and NC NMPs at a later date.

Overall, I am fine with activating the system at this point.  (I believe it is up to whether yakra wants to do his grepping label program before or after activation.)


Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: usasc: South Carolina State highways
« Reply #84 on: November 17, 2019, 06:10:39 pm »
SC 22 fix made and submitted...

Offline ntallyn

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 328
  • Last Login:March 24, 2024, 03:22:47 pm
Re: usasc: South Carolina State highways
« Reply #85 on: November 17, 2019, 06:20:06 pm »
The only thing I see missed is the US 501/SC 22 NMP.  Otherwise I directed ntallyn here from the GA State Highways thread for the US 221/GA 150

Updated GA 150 and US 221 (GA) locally. Will be included with my next push.

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #86 on: November 22, 2019, 08:43:40 am »
Added the relevant SC NMPs to FP file:  https://github.com/TravelMapping/HighwayData/pull/3342 

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: usasc: South Carolina State highways
« Reply #87 on: November 28, 2019, 11:28:12 am »
I forgot to do this before, but this pull request removes the Relevant FPs from the Datacheck FP file:  https://github.com/TravelMapping/HighwayData/pull/3364

This should end the SC clean-up minus yakra's label corrections.


Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: usasc: South Carolina State highways
« Reply #88 on: November 28, 2019, 03:57:22 pm »
`Bout that time then is it?
I've come up with several new searches, to be copied to the grep thread for staying organized. I'll do that, then go to town.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: usasc: South Carolina State highways
« Reply #89 on: November 28, 2019, 11:51:16 pm »
prefix after slash

SC/usaus/sc.us521.wpt:US521Trk/US601Trk_N
We don't want the US after the slash:
Drop the prefix of the second highway if it is more than one character long.
...
If one of the two highways is already long as a label (e.g., a bannered route like US42BusKin), consider skipping the city abbrev. or even skipping the whole second route.

Avoid extra distinguishing suffixes on labels with 2 numbered designations unless necessary.
Only in the case of two identical two-designation waypoints should the suffixes be added for distinction.



lower -> upper case

SC/usaus/sc.us076.wpt: I-20Bs -> I-20Bs



should be suffix, not abbrev

SC/usaus/sc.us001.wpt:US378Col_W
SC/usaus/sc.us076.wpt:US1Col_N
SC/usaus/sc.us378.wpt:US1Col_S
SC/usaus/sc.us378.wpt:US1Col_N

US##Col_W -> US##_ColW
Because this is part of a disambiguating city suffix, not an abbrev which is tied to this route segment as part of its .list file name.



long word

SC/usaus/sc.us029.wpt:US29ConGreen



too many words

SC/usaif/sc.i074futmyr.wpt:RobMGriPkwy
SC/usasc/sc.sc009.wpt:OldCamMonHwy
SC/usasc/sc.sc024.wpt:ONeFerRd
SC/usasc/sc.sc120.wpt:StPauChuRd
SC/usasc/sc.sc154.wpt:ManStCRd
SC/usasc/sc.sc213.wpt:StBChuRd
SC/usasc/sc.sc219.wpt:StPChuRd
SC/usasc/sc.sc395.wpt:StLChuRd
SC/usausb/sc.us017altsum.wpt:RemCDenBlvd
SC/usaus/sc.us017.wpt:BarRBrgRd
SC/usaus/sc.us052.wpt:RemCDenBlvd
SC/usaus/sc.us052.wpt:OldMtHRd
SC/usaus/sc.us076.wpt:StPauChuRd
SC/usaus/sc.us176.wpt:OldMtHRd
SC/usaus/sc.us378.wpt:StPauChuRd
http://205.209.84.174/devel/manual/wayptlabels.php#truncate

Some borderline cases here. Weaseley ones though; one 2-letter abbreviation + another 1-letter abbreviation does not equal one three-letter abbreviATION. :) Excuse me, I sneezed. And it made me bump into the caps lock key.



potential leading directional specifiers

SC/usasc/sc.sc005.wpt:NMouSt
SC/usasc/sc.sc146.wpt:SJWorHwy
SC/usasc/sc.sc186.wpt:SCChuRd
SC/usasc/sc.sc215.wpt:SHChuRd
SC/usasc/sc.sc763.wpt:SPChuRd
SC/usausb/sc.us017altsum.wpt:ECarAve
SC/usausb/sc.us017busmyr.wpt:SOceBlvd
SC/usaus/sc.us029.wpt:EMainSt
SC/usaus/sc.us052.wpt:NADRd
SC/usaus/sc.us052.wpt:EMonAve
SC/usaus/sc.us076.wpt:EWPkwy
SC/usaus/sc.us076.wpt:EBreRd
SC/usaus/sc.us078.wpt:NADSt
SC/usaus/sc.us078.wpt:EMonAve
SC/usaus/sc.us123.wpt:NMainSt
SC/usaus/sc.us178.wpt:EWPkwy
SC/usaus/sc.us276.wpt:NMainSt
SC/usaus/sc.us378.wpt:SJenSt
SC/usaus/sc.us401.wpt:EMainSt
SC/usaus/sc.us401.wpt:WMainSt
These could very well all be false positives for all I know.



SC/usasc/sc.sc045.wpt: FraMarHBS -> FraMarAve
SC/usasc/sc.sc171.wpt: CTLanSHS -> OTPlaRd or similar
SC/usasc/sc.sc642.wpt: ColDorSHS -> OldDSPRd, ODorSPRd, etc
SC248: NinSixNHS could maybe be at Louden Rd instead, but it's not something I feel especially strongly about.
« Last Edit: November 29, 2019, 12:46:56 am by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca