Author Topic: NC NMPs  (Read 340 times)

0 Members and 1 Guest are viewing this topic.

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 855
  • Last Login:Today at 12:45:44 pm
NC NMPs
« on: April 26, 2020, 07:31:16 pm »
Quote
nc.nc481busenf@+x3 36.180926 -77.665862
nc.nc481busenf@SERaiSt 36.180714 -77.666184

Either remove +X3 or mark it FP.
Quote
nc.nc125@US64Alt 35.839595 -77.088232
nc.us064altbet@NC125_S 35.839642 -77.088613

Both points need to be synced and moved to the correct intersection (with NC125_S on US 64 ALT becoming just NC 125).  I made a new thread regarding other changes needed around Williamston and Windsor. (http://forum.travelmapping.net/index.php?topic=3580.0)
Quote
nc.nc012ocr@+y1 35.115898 -75.986901
nc.nc012ocr@OcrFry 35.115613 -75.986815

FP presumably, but check to make sure there is not a relocation needed.
Quote
nc.nc024busros@NC242 34.956636 -78.510633
nc.nc242@NC24Bus 34.956496 -78.510591

NC 242 should be synced with NC 24 BUS (Roseboro) here.

Quote
nc.nc242@NC242Trk_N 34.953084 -78.509196
nc.nc242trkros@NC242_N 34.953084 -78.509368

NC 242 TRUCK (Roseboro) should be synced with NC 242 here.

Quote
nc.nc041@+x20 34.643836 -78.644342
nc.nc087buseli@+x1 34.64382 -78.644219

These points just need to be synced with each other as this is a result of a broken concurrency.
Quote
nc.nc008@NC704_N 36.539913 -80.224284
nc.nc008@NC704_S 36.539648 -80.224292
nc.nc008@NC704_N 36.539913 -80.224284
nc.nc704@NC8_S 36.539648 -80.224292
nc.nc008@NC704_S 36.539648 -80.224292
nc.nc704@NC8_N 36.539913 -80.224284
nc.nc704@NC8_N 36.539913 -80.224284
nc.nc704@NC8_S 36.539648 -80.224292

FPs, except that the NC 704 points should be W and E instead of S and N.
Quote
nc.nc008@US52(108B) 36.084474 -80.22911
nc.us052@108B 36.084006 -80.22927
nc.us052@108B 36.084006 -80.22927
nc.us311@US52(108B) 36.084474 -80.22911

NC 8 and US 311 need to be synced with US 52 here.  Of course, US 311 may be truncated in the HB by the time this is done.
Quote
nc.i073@68 35.620291 -79.82563
nc.us220busash@US220_S 35.620293 -79.82563
nc.i074hig@68(73) 35.620291 -79.82563
nc.us220busash@US220_S 35.620293 -79.82563
nc.us220@I-73(68) 35.620291 -79.82563
nc.us220busash@US220_S 35.620293 -79.82563
nc.us220altcan@US220_N 35.620291 -79.82563
nc.us220busash@US220_S 35.620293 -79.82563

I am covering this one in a separate thread.
(http://forum.travelmapping.net/index.php?topic=3581.0)
Quote
nc.nc087bypsan@US421(143) 35.446976 -79.119297
nc.us421@143 35.446792 -79.119077
nc.nc087bypsan@US421(143) 35.446976 -79.119297
nc.us421bussan@US421_S 35.446792 -79.119077
US 421 and US 421 BUS (Sanford) should be synced with NC 87 BYP (Sanford).  Also the NC 87/US 421 BUS (Sanford) intersection nearby needs its points recentered.

Quote
nc.us001bussan@McNRd 35.507706 -79.17885
nc.us001bussan@SR1405 35.507688 -79.17881
The SR 1405 point on US 1 BUS (Sanford) should be deleted.  It is practically a duplicate point.
Quote
nc.i040@*153 35.812593 -80.842896
nc.us064@*I-40(153) 35.812228 -80.842724
FP
Quote
nc.nc027@NC275 35.359359 -81.09534
nc.nc275@+x14 35.359227 -81.095747
nc.nc275@+x14 35.359227 -81.095747
nc.nc275@NC27 35.359359 -81.09534

+X14 should be changed to Chestnut St (CheSt_W).  Otherwise this is a FP.
Quote
nc.nc007@US29/74_E 35.24671 -81.013951
nc.nc007trkbel@NC7_E 35.246697 -81.014053
nc.nc007@US29/74_E 35.24671 -81.013951
nc.us029@NC7_W 35.246697 -81.014053
nc.nc007@US29/74_E 35.24671 -81.013951
nc.us074@NC7_W 35.246697 -81.014053

NC 7 needs to be synced with US 29, US 74, and NC 7 TRUCK (Belmont) here.
Secondly, the NC 7 points on US 29 and US 74 should be NC7_W and NC7_E.  If the NC7_W point (at what should be NC7_E) is in-use on either route, you may have to create updates entries.
Quote
nc.blueridpkwy@NC226 35.852796 -82.050783
nc.nc226@NC226AltLSw_N 35.852492 -82.050871
nc.blueridpkwy@NC226 35.852796 -82.050783
nc.nc226altlsw@NC226_N 35.852492 -82.050871
nc.nc226@BlueRidPky 35.852796 -82.050783
nc.nc226@NC226AltLSw_N 35.852492 -82.050871
nc.nc226@BlueRidPky 35.852796 -82.050783
nc.nc226altlsw@NC226_N 35.852492 -82.050871

FPs

Quote
nc.nc226altlsw@+x20 35.829422 -82.106152
nc.nc226altlsw@WilAcrRd 35.828996 -82.105725

+X20 should be replaced with a point at Bear Wallow Rd (BearWalRd).  Otherwise this can be a FP.
Quote
nc.nc009@US74 35.281615 -82.114284
nc.us074@167 35.281615 -82.114434

NC 9 should be synced with US 74 here.
Quote
nc.us023@US441Bus 35.194073 -83.361704
nc.us441busfra@US441_N 35.193924 -83.361586
nc.us064trkhen@US441Bus 35.194073 -83.361704
nc.us441busfra@US441_N 35.193924 -83.361586
nc.us441@US441BusFra 35.194073 -83.361704
nc.us441busfra@US441_N 35.193924 -83.361586

US 441 BUS (Franklin) should be synced with US 23, US 441, and US 64 TRUCK (Henderson).
Quote
nc.i095blfay@DobHolRd 35.076616 -78.814201
nc.us301@DobHolRd 35.076774 -78.814663

US 301 should be synced with I-95 BL (Fayetteville) here.
Quote
nc.i095@40 34.930873 -78.938699
nc.i095blfay@I-95_S 34.930556 -78.938613

I-95 BL (Fayetteville) should be synced with I-95 here.  The same needs to be done at the northern end of I-95 BL (Fayetteville) at I-95 (Exit 56) as well.
Quote
nc.i074pem@209 34.59312 -79.111133
nc.i095@13 34.593195 -79.111294
nc.i074pem@209 34.59312 -79.111133
nc.us301@I-95(13) 34.593195 -79.111294
nc.i095@13 34.593195 -79.111294
nc.us074@I-74(209) 34.59312 -79.111133
nc.us074@I-74(209) 34.59312 -79.111133
nc.us301@I-95(13) 34.593195 -79.111294

I-74 (Pembroke) and US 74 should be synced with I-95 and US 301 here.
Secondly, the graph connection at the closed Exit 14 with US 74 ALT (Pembroke) should be broken.

Quote
ga.ga246sky@GA/NC 34.995676 -83.337084
nc.nc106@GA/NC 34.995674 -83.336931

NC 106 should be synced with GA 246 (Sky Valley) here. Just noting this post regarding NC 106 being three files (or NC GA 246) in the meantime (http://forum.travelmapping.net/index.php?topic=215.msg12852#msg12852).

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 836
  • Gender: Male
  • Last Login:Today at 01:53:20 am
Re: NC NMPs
« Reply #1 on: April 26, 2020, 11:16:56 pm »
Secondly, the graph connection at the closed Exit 14 with US 74 ALT (Pembroke) should be broken.

I think that one can be debatable, but that's just my opinion.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 547
  • Last Login:Today at 09:29:47 am
    • Co-curator Virginia Highways Project
Re: NC NMPs
« Reply #2 on: April 27, 2020, 06:26:03 am »
Secondly, the graph connection at the closed Exit 14 with US 74 ALT (Pembroke) should be broken.

I think that one can be debatable, but that's just my opinion.

I'm also curious about why to break it.  If someone left I-95 at the former US 74 exit, shouldn't their graph be continuous?

Regardless, I may add a point on US 74 ALT for the former US 301 split (SR 1207).

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 855
  • Last Login:Today at 12:45:44 pm
Re: NC NMPs
« Reply #3 on: April 27, 2020, 07:34:58 am »
Secondly, the graph connection at the closed Exit 14 with US 74 ALT (Pembroke) should be broken.

I think that one can be debatable, but that's just my opinion.

I'm also curious about why to break it.  If someone left I-95 at the former US 74 exit, shouldn't their graph be continuous?

Regardless, I may add a point on US 74 ALT for the former US 301 split (SR 1207).

I broke one for US 6 BUS (Carbondale) at PA 347 due to the ramps being closed and the new connection being made via a connector road to the east.

http://forum.travelmapping.net/index.php?topic=2999.msg13717#msg13717

I guess I just assumed that a lack of connection would mean automatically removing the graph connection, but that is just me.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 547
  • Last Login:Today at 09:29:47 am
    • Co-curator Virginia Highways Project
Re: NC NMPs
« Reply #4 on: May 23, 2020, 02:55:05 pm »
changes made, including adding the small NC 106 segments at the GA line...

In the queue

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 855
  • Last Login:Today at 12:45:44 pm
Re: NC NMPs
« Reply #5 on: May 24, 2020, 01:36:06 pm »
Updated NMP FPs (including GA 246) are here: https://github.com/TravelMapping/HighwayData/pull/3911

The below NMPs were not done.

Quote
Quote
nc.nc041@+x20 34.643836 -78.644342
nc.nc087buseli@+x1 34.64382 -78.644219

These points just need to be synced with each other as this is a result of a broken concurrency.

Quote
Quote
nc.i095@40 34.930873 -78.938699
nc.i095blfay@I-95_S 34.930556 -78.938613
I-95 BL (Fayetteville) should be synced with I-95 here.  The same needs to be done at the northern end of I-95 BL (Fayetteville) at I-95 (Exit 56) as well.

Quote
Quote
nc.i074pem@209 34.59312 -79.111133
nc.i095@13 34.593195 -79.111294
nc.i074pem@209 34.59312 -79.111133
nc.us301@I-95(13) 34.593195 -79.111294
nc.i095@13 34.593195 -79.111294
nc.us074@I-74(209) 34.59312 -79.111133
nc.us074@I-74(209) 34.59312 -79.111133
nc.us301@I-95(13) 34.593195 -79.111294

I-74 (Pembroke) and US 74 should be synced with I-95 and US 301 here.
Secondly, the graph connection at the closed Exit 14 with US 74 ALT (Pembroke) should be broken.

Also NC 106 was written instead as NC 109 in the Updates Entries. (Fixed here: https://github.com/TravelMapping/HighwayData/pull/3911)

Quote
nc.nc226altlsw@+x20 35.829422 -82.106152
nc.nc226altlsw@WilAcrRd 35.828996 -82.105725

I should have just advocated for the removal of +x20.

Quote
nc.i074pem@210 34.592807 -79.089077
nc.us074altpem@US74_E 34.592807 -79.08907
nc.us074@I-74(210) 34.592807 -79.089077
nc.us074altpem@US74_E 34.592807 -79.08907

US 74 ALT (Pembroke) needs to be synced with I-74 (Pembroke) and US 74 here.  I could have missed this one on the first go-around.

Also BlueRidPky should be BlueRidPkwy on NC 226.  (I asked yakra via PM to grep all of these.)


« Last Edit: May 24, 2020, 04:24:11 pm by Markkos1992 »

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2654
  • Last Login:Today at 04:20:17 am
Re: NC NMPs
« Reply #6 on: May 24, 2020, 09:21:10 pm »
Also BlueRidPky should be BlueRidPkwy on NC 226.  (I asked yakra via PM to grep all of these.)
http://forum.travelmapping.net/index.php?topic=3637.msg18803#msg18803