Author Topic: usanp (U.S. National Park Highways)  (Read 24128 times)

0 Members and 1 Guest are viewing this topic.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1000
  • Last Login:July 28, 2020, 10:20:49 am
Re: usanp (U.S. National Park Highways)
« Reply #120 on: December 22, 2018, 02:46:09 pm »
I agree with keeping the labels short & simple per the manual whenever possible. These examples don't seem likely to cause confusion for users.
Clinched:

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 562
  • Last Login:Today at 06:38:38 am
    • Co-curator Virginia Highways Project
Re: usanp (U.S. National Park Highways)
« Reply #121 on: December 22, 2018, 03:30:40 pm »
ping oscar (NM, NV), yakra (OK), Bickendan (OR), mapcat (TN), Duke87 (UT), mapmikey (VA) and compdude787 (WA) as I've changed usanp files in your states per this review.



Acknowledged...thanks

Offline Duke87

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 376
  • Last Login:Today at 12:43:53 am
Re: usanp (U.S. National Park Highways)
« Reply #122 on: December 22, 2018, 05:21:04 pm »
ping oscar (NM, NV), yakra (OK), Bickendan (OR), mapcat (TN), Duke87 (UT), mapmikey (VA) and compdude787 (WA) as I've changed usanp files in your states per this review.

I haven't been touching anything in usanp so no conflict here.

I went ahead and changed the endpoint of UT149 from DinNM -> CubCreRd to match (well, "DinNM" remains as hidden alt since it's in use). Will be reflected in my next update.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2701
  • Last Login:Today at 02:29:35 pm
Re: usanp (U.S. National Park Highways)
« Reply #123 on: December 23, 2018, 02:27:04 am »
I agree with keeping the labels short & simple per the manual whenever possible.

Seconded. I don't like long labels with more than 3 words. Keep it simple!

Offline Bickendan

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 325
  • Last Login:July 28, 2020, 04:01:35 am
Re: usanp (U.S. National Park Highways)
« Reply #124 on: December 23, 2018, 02:27:14 am »
ping oscar (NM, NV), yakra (OK), Bickendan (OR), mapcat (TN), Duke87 (UT), mapmikey (VA) and compdude787 (WA) as I've changed usanp files in your states per this review.



Acknowledged...thanks
likewise!

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 548
  • Last Login:Today at 11:22:43 am
Re: usanp (U.S. National Park Highways)
« Reply #125 on: December 23, 2018, 07:48:34 am »
Some of us still don't understand this HDX thing.  Seems far above and beyond the original intentions of the project.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1000
  • Last Login:July 28, 2020, 10:20:49 am
Re: usanp (U.S. National Park Highways)
« Reply #126 on: December 23, 2018, 08:21:08 am »
Some of us still don't understand this HDX thing.  Seems far above and beyond the original intentions of the project.
Besides being useful for detecting NMP errors, it also makes TM data more useful for Jim's classes. That may not be the original intention of the project, but it's one of the main reasons the project still exists.
Clinched:

Offline Duke87

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 376
  • Last Login:Today at 12:43:53 am
Re: usanp (U.S. National Park Highways)
« Reply #127 on: December 23, 2018, 10:33:09 pm »
I've been relying on nearmisspoints.log to find NMPs. It's straightforward and easy to use.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2701
  • Last Login:Today at 02:29:35 pm
Re: usanp (U.S. National Park Highways)
« Reply #128 on: December 24, 2018, 03:06:17 am »
Some of us still don't understand this HDX thing.

HDX is a great tool to identify broken concurrencies and check for near-miss points. That's it. All other features is not relevant for us but for Jim's students.
Without HDX, we would find these issues falsifying stats only at random.

I've been relying on nearmisspoints.log to find NMPs. It's straightforward and easy to use.

It's just software and software does always have room for improvement. If anyone has a problem with using it, one can report it here or on GitHub and there is always a chance that it might be improved.
« Last Edit: December 24, 2018, 03:08:28 am by michih »

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1035
  • Last Login:Today at 02:49:16 pm
    • Hot Springs and Highways pages
Re: usanp (U.S. National Park Highways)
« Reply #129 on: December 28, 2018, 11:26:13 pm »
CA BigOakRd:
CA GenHwy: Add a waypoint at Crescent Meadow Road.
CA KinCanRd: Add a waypoint at Grant Tree Road.
CA LasPeakHwy: Are both Summit Lake Camp waypoints necessary?
The southern point seems more dispensable, and isn't in use.
Quote
CA MinSumRd: DevPosAccRd => DevPosRd
Done. I also changed the north endpoint (Mad/Mon) to CA203.
Quote
CA TioPassRd: Western hidden waypoint => TuoGro
I suggest reposition and rename to OldBOFRd_W, and rename existing OldBOFRd to OldBOFRd_E
Quote
CA WawRd: Add waypoint at Tunnel View
I agree with this change, and all the others above on which I haven't otherwise commented.

My pull request to implement the CA changes submitted (#2466).
« Last Edit: December 31, 2018, 08:20:39 pm by oscar »

Offline compdude787

  • TM Collaborator
  • Full Member
  • *****
  • Posts: 206
  • Last Login:Today at 02:38:50 am
Re: usanp (U.S. National Park Highways)
« Reply #130 on: December 29, 2018, 12:21:13 pm »
I agree with keeping the labels short & simple per the manual whenever possible. These examples don't seem likely to cause confusion for users.

I'd agree as well with keeping labels as short as possible. I'd rather not have to be copy-pasting long labels from the HB to my list file.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2798
  • Last Login:Today at 12:32:35 pm
Re: usanp (U.S. National Park Highways)
« Reply #131 on: December 30, 2018, 01:27:20 am »
ME ParkLpRd: remove Sieur de Monts Rd
https://github.com/TravelMapping/HighwayData/pull/2460

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 897
  • Last Login:Today at 12:36:15 pm
Re: usanp (U.S. National Park Highways)
« Reply #132 on: December 30, 2018, 02:35:34 pm »
PA RivRd: Relocated Broad St (BroSt) due to new roundabout (drawn on Google Maps but not in GSV). Changed HilDr to Gap View Dr.

https://github.com/TravelMapping/HighwayData/pull/2462
« Last Edit: December 30, 2018, 02:49:06 pm by Markkos1992 »

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1313
  • Last Login:Today at 02:12:43 pm
Re: usanp (U.S. National Park Highways)
« Reply #133 on: January 01, 2019, 05:49:09 am »
Datacheck issues, most of which are Visible Distances (that we don't need to mark as FP as they are removed as errors when system activated). I'm sure most are false positives

ak.parkrd   IglCrkCamp,TokRivSta   VISIBLE_DISTANCE   18.36   ak.parkrd;IglCrkCamp;TokRivSta;;VISIBLE_DISTANCE;18.36
al.nattrapkwy   MS/AL,US72   VISIBLE_DISTANCE   11.64   al.nattrapkwy;MS/AL;US72;;VISIBLE_DISTANCE;11.64
ca.badrd   CA178,HarWadeRd   VISIBLE_DISTANCE   10.32   ca.badrd;CA178;HarWadeRd;;VISIBLE_DISTANCE;10.32
ca.badrd   WestSideRd_S,Bad   VISIBLE_DISTANCE   23.40   ca.badrd;WestSideRd_S;Bad;;VISIBLE_DISTANCE;23.40
ca.bigoakrd   BigOakRd   LABEL_SELFREF      ca.bigoakrd;BigOakRd;;;LABEL_SELFREF;
ca.elporrd   SenDr_S,NorDr,SenDr_N   SHARP_ANGLE   163.07   ca.elporrd;SenDr_S;NorDr;SenDr_N;SHARP_ANGLE;163.07
ca.elporrd   SouDr_W,SouDr_E   DUPLICATE_COORDS   (37.716941,-119.666224)   ca.elporrd;SouDr_W;SouDr_E;;DUPLICATE_COORDS;(37.716941,-119.666224)
ca.laspeakhwy   +x188,+x191,+x192   SHARP_ANGLE   139.36   ca.laspeakhwy;+x188;+x191;+x192;SHARP_ANGLE;139.36
ca.minsumrd   RedsMeaRes,+X799297,RedsMeaCamp   SHARP_ANGLE   136.22   ca.minsumrd;RedsMeaRes;+X799297;RedsMeaCamp;SHARP_ANGLE;136.22
ca.minsumrd   SodaSprCamp,AgnMeaRd,CA203   SHARP_ANGLE   156.13   ca.minsumrd;SodaSprCamp;AgnMeaRd;CA203;SHARP_ANGLE;156.13

ca.pinbasrd   MecDaleRd,ParkBlvd   VISIBLE_DISTANCE   22.22   ca.pinbasrd;MecDaleRd;ParkBlvd;;VISIBLE_DISTANCE;22.22
ca.scocasrd   DayPassRd,TitCynRd   VISIBLE_DISTANCE   14.21   ca.scocasrd;DayPassRd;TitCynRd;;VISIBLE_DISTANCE;14.21
ca.scocasrd   TitCynRd,MesRd   VISIBLE_DISTANCE   17.71   ca.scocasrd;TitCynRd;MesRd;;VISIBLE_DISTANCE;17.71
co.bearlakerd   +X188630,+X817209,+X283029   SHARP_ANGLE   142.39   co.bearlakerd;+X188630;+X817209;+X283029;SHARP_ANGLE;142.39
co.bearlakerd   +X672063,OldBearLakeRd_N,HolParkRd   SHARP_ANGLE   146.64   co.bearlakerd;+X672063;OldBearLakeRd_N;HolParkRd;SHARP_ANGLE;146.64
co.bearlakerd   BearLake,+X188630,+X817209   SHARP_ANGLE   135.30   co.bearlakerd;BearLake;+X188630;+X817209;SHARP_ANGLE;135.30
co.bearlakerd   MorParkCamp,+X122853,+X640280   SHARP_ANGLE   156.68   co.bearlakerd;MorParkCamp;+X122853;+X640280;SHARP_ANGLE;156.68
co.bearlakerd   OldBearLakeRd_N,HolParkRd,+X623312   SHARP_ANGLE   147.93   co.bearlakerd;OldBearLakeRd_N;HolParkRd;+X623312;SHARP_ANGLE;147.93
co.mesaverrd   +X329794,+X260741,+X579668   SHARP_ANGLE   136.85   co.mesaverrd;+X329794;+X260741;+X579668;SHARP_ANGLE;136.85
co.rimrockdr   +X148951,+X157499,+X889271   SHARP_ANGLE   159.01   co.rimrockdr;+X148951;+X157499;+X889271;SHARP_ANGLE;159.01

fl.mainparkrd   MahHam,FlaRd   VISIBLE_DISTANCE   17.46   fl.mainparkrd;MahHam;FlaRd;;VISIBLE_DISTANCE;17.46
fl.mainparkrd   RoyPalm,PaHayOkee   VISIBLE_DISTANCE   10.45   fl.mainparkrd;RoyPalm;PaHayOkee;;VISIBLE_DISTANCE;10.45
me.cadsumrd   +X133948,+X138493,CadMtn   SHARP_ANGLE   136.02   me.cadsumrd;+X133948;+X138493;CadMtn;SHARP_ANGLE;136.02
me.cadsumrd   +X185788,+X133948,+X138493   SHARP_ANGLE   148.79   me.cadsumrd;+X185788;+X133948;+X138493;SHARP_ANGLE;148.79
me.cadsumrd   +X858922,+X185788,+X133948   SHARP_ANGLE   156.59   me.cadsumrd;+X858922;+X185788;+X133948;SHARP_ANGLE;156.59
me.parklprd   +X270370,+X563093,+X482183   SHARP_ANGLE   142.10   me.parklprd;+X270370;+X563093;+X482183;SHARP_ANGLE;142.10
me.parklprd   OttCliRd,+X270370,+X563093   SHARP_ANGLE   149.61   me.parklprd;OttCliRd;+X270370;+X563093;SHARP_ANGLE;149.61
me.parklprd   SieMonRd_S,SieMonRd_N   DUPLICATE_COORDS   (44.36242,-68.203801)   me.parklprd;SieMonRd_S;SieMonRd_N;;DUPLICATE_COORDS;(44.36242,-68.203801)

ms.nattrapkwy   CanRd,MS43   VISIBLE_DISTANCE   10.87   ms.nattrapkwy;CanRd;MS43;;VISIBLE_DISTANCE;10.87
ms.nattrapkwy   MS12,MS413   VISIBLE_DISTANCE   15.28   ms.nattrapkwy;MS12;MS413;;VISIBLE_DISTANCE;15.28
ms.nattrapkwy   MS16,MS429   VISIBLE_DISTANCE   11.52   ms.nattrapkwy;MS16;MS429;;VISIBLE_DISTANCE;11.52
ms.nattrapkwy   MS18,FisFryRd   VISIBLE_DISTANCE   18.03   ms.nattrapkwy;MS18;FisFryRd;;VISIBLE_DISTANCE;18.03
ms.nattrapkwy   MS27,MS467   VISIBLE_DISTANCE   12.58   ms.nattrapkwy;MS27;MS467;;VISIBLE_DISTANCE;12.58
ms.nattrapkwy   MS413,MS415   VISIBLE_DISTANCE   10.15   ms.nattrapkwy;MS413;MS415;;VISIBLE_DISTANCE;10.15
ms.nattrapkwy   MS429,MS19/35   VISIBLE_DISTANCE   13.83   ms.nattrapkwy;MS429;MS19/35;;VISIBLE_DISTANCE;13.83
ms.nattrapkwy   MS43,MS16   VISIBLE_DISTANCE   20.40   ms.nattrapkwy;MS43;MS16;;VISIBLE_DISTANCE;20.40
ms.nattrapkwy   MS533,MS552   VISIBLE_DISTANCE   10.06   ms.nattrapkwy;MS533;MS552;;VISIBLE_DISTANCE;10.06
ms.nattrapkwy   US61_N,MS533   VISIBLE_DISTANCE   11.92   ms.nattrapkwy;US61_N;MS533;;VISIBLE_DISTANCE;11.92
ms.nattrapkwy   US82,MS15   VISIBLE_DISTANCE   10.27   ms.nattrapkwy;US82;MS15;;VISIBLE_DISTANCE;10.27
mt.goisunrd   +X568313,+X377714,+X833031   SHARP_ANGLE   166.73   mt.goisunrd;+X568313;+X377714;+X833031;SHARP_ANGLE;166.73
mt.goisunrd   AvaCamp,LogPass   VISIBLE_DISTANCE   14.72   mt.goisunrd;AvaCamp;LogPass;;VISIBLE_DISTANCE;14.72
nc.blueridpkwy   +X726553,+X231819,+X779126   SHARP_ANGLE   136.64   nc.blueridpkwy;+X726553;+X231819;+X779126;SHARP_ANGLE;136.64
nc.blueridpkwy   ElkMtnSceHwy,NC128   VISIBLE_DISTANCE   17.84   nc.blueridpkwy;ElkMtnSceHwy;NC128;;VISIBLE_DISTANCE;17.84
nc.blueridpkwy   NC151,NC191   VISIBLE_DISTANCE   10.74   nc.blueridpkwy;NC151;NC191;;VISIBLE_DISTANCE;10.74
nc.blueridpkwy   NC18_S,US21   VISIBLE_DISTANCE   17.11   nc.blueridpkwy;NC18_S;US21;;VISIBLE_DISTANCE;17.11
nc.blueridpkwy   NC226,US221_Lin   VISIBLE_DISTANCE   11.64   nc.blueridpkwy;NC226;US221_Lin;;VISIBLE_DISTANCE;11.64
nc.blueridpkwy   US21,NC18_N   VISIBLE_DISTANCE   11.08   nc.blueridpkwy;US21;NC18_N;;VISIBLE_DISTANCE;11.08
nc.blueridpkwy   US23/74,NC215   VISIBLE_DISTANCE   17.93   nc.blueridpkwy;US23/74;NC215;;VISIBLE_DISTANCE;17.93
nm.chalooprd   +X731081,PueArr,PueBon   SHARP_ANGLE   140.66   nm.chalooprd;+X731081;PueArr;PueBon;SHARP_ANGLE;140.66
nv.whepeaksd   +X428182,+X721767,+X712721   SHARP_ANGLE   142.16   nv.whepeaksd;+X428182;+X721767;+X712721;SHARP_ANGLE;142.16
nv.whepeaksd   +X721767,+X712721,+X408584   SHARP_ANGLE   149.92   nv.whepeaksd;+X721767;+X712721;+X408584;SHARP_ANGLE;149.92
nv.whepeaksd   LowLCCamp,UppLCCamp,+X875034   SHARP_ANGLE   152.91   nv.whepeaksd;LowLCCamp;UppLCCamp;+X875034;SHARP_ANGLE;152.91
or.cralakerimdr   CraLakeHwy_W,CraLakeHwy_E   DUPLICATE_COORDS   (42.966033,-122.151575)   or.cralakerimdr;CraLakeHwy_W;CraLakeHwy_E;;DUPLICATE_COORDS;(42.966033,-122.151575)
tn.cadcovelprd   LauCreRd_A,LauCreRd_B   DUPLICATE_COORDS   (35.606475,-83.774164)   tn.cadcovelprd;LauCreRd_A;LauCreRd_B;;DUPLICATE_COORDS;(35.606475,-83.774164)

tn.foopkwyw   US321_Wal,US321_Wea   VISIBLE_DISTANCE   13.02   tn.foopkwyw;US321_Wal;US321_Wea;;VISIBLE_DISTANCE;13.02
tn.nattrapkwy   RaiBedRd,US64   VISIBLE_DISTANCE   15.02   tn.nattrapkwy;RaiBedRd;US64;;VISIBLE_DISTANCE;15.02
tn.nattrapkwy   TN7,TN46   VISIBLE_DISTANCE   12.83   tn.nattrapkwy;TN7;TN46;;VISIBLE_DISTANCE;12.83
tn.nattrapkwy   US412,TN50   VISIBLE_DISTANCE   15.48   tn.nattrapkwy;US412;TN50;;VISIBLE_DISTANCE;15.48
tx.mainparkrd   DagFlatRd,ChaDraRan   VISIBLE_DISTANCE   13.17   tx.mainparkrd;DagFlatRd;ChaDraRan;;VISIBLE_DISTANCE;13.17
tx.mainparkrd   RGVlgRd,DagFlatRd   VISIBLE_DISTANCE   12.65   tx.mainparkrd;RGVlgRd;DagFlatRd;;VISIBLE_DISTANCE;12.65
tx.rgvlgrd   PanDr,BoqCanRd   VISIBLE_DISTANCE   18.67   tx.rgvlgrd;PanDr;BoqCanRd;;VISIBLE_DISTANCE;18.67
ut.briviewdr   +X412413,OwaBriOve,BriViewDr_N   SHARP_ANGLE   139.52   ut.briviewdr;+X412413;OwaBriOve;BriViewDr_N;SHARP_ANGLE;139.52
ut.briviewdr   +X966440,KacBriOve,+X412413   SHARP_ANGLE   150.49   ut.briviewdr;+X966440;KacBriOve;+X412413;SHARP_ANGLE;150.49
ut.briviewdr   BriViewDr_N   LABEL_SELFREF      ut.briviewdr;BriViewDr_N;;;LABEL_SELFREF;
ut.briviewdr   BriViewDr_S,BriViewDr_N   DUPLICATE_COORDS   (37.608682,-109.986556)   ut.briviewdr;BriViewDr_S;BriViewDr_N;;DUPLICATE_COORDS;(37.608682,-109.986556)
ut.briviewdr   BriViewDr_S   LABEL_SELFREF      ut.briviewdr;BriViewDr_S;;;LABEL_SELFREF;
ut.kolterrd   +X296003,+X241424,+X686912   SHARP_ANGLE   148.34   ut.kolterrd;+X296003;+X241424;+X686912;SHARP_ANGLE;148.34

ut.kolterrd   SmiMesRd,SprSprDr   VISIBLE_DISTANCE   12.46   ut.kolterrd;SmiMesRd;SprSprDr;;VISIBLE_DISTANCE;12.46
va.blueridpkwy   PeaRd,SR781   VISIBLE_DISTANCE   13.03   va.blueridpkwy;PeaRd;SR781;;VISIBLE_DISTANCE;13.03
va.blueridpkwy   SR608_E,SR607_S   VISIBLE_DISTANCE   16.70   va.blueridpkwy;SR608_E;SR607_S;;VISIBLE_DISTANCE;16.70
va.blueridpkwy   SR664_N,US250   VISIBLE_DISTANCE   12.48   va.blueridpkwy;SR664_N;US250;;VISIBLE_DISTANCE;12.48
va.blueridpkwy   US221,US220   VISIBLE_DISTANCE   13.28   va.blueridpkwy;US221;US220;;VISIBLE_DISTANCE;13.28
va.blueridpkwy   US221/460,VA43   VISIBLE_DISTANCE   14.36   va.blueridpkwy;US221/460;VA43;;VISIBLE_DISTANCE;14.36
va.blueridpkwy   VA130,SR607_N   VISIBLE_DISTANCE   10.58   va.blueridpkwy;VA130;SR607_N;;VISIBLE_DISTANCE;10.58
wa.hurridrd   HeaOTheHil,HRVisCen   VISIBLE_DISTANCE   10.54   wa.hurridrd;HeaOTheHil;HRVisCen;;VISIBLE_DISTANCE;10.54
wa.stecynrd   ParVlyRd_S,WA123   VISIBLE_DISTANCE   16.37   wa.stecynrd;ParVlyRd_S;WA123;;VISIBLE_DISTANCE;16.37
wa.stecynrd   WA706,ParVlyRd_N   VISIBLE_DISTANCE   12.77   wa.stecynrd;WA706;ParVlyRd_N;;VISIBLE_DISTANCE;12.77
wa.sunparkrd   +X165287,+X526700,+X776898   SHARP_ANGLE   144.07   wa.sunparkrd;+X165287;+X526700;+X776898;SHARP_ANGLE;144.07
wa.sunparkrd   Sun,SunPt,+X387041   SHARP_ANGLE   165.83   wa.sunparkrd;Sun;SunPt;+X387041;SHARP_ANGLE;165.83
wa.sunparkrd   SunPt,+X387041,+X165287   SHARP_ANGLE   163.99   wa.sunparkrd;SunPt;+X387041;+X165287;SHARP_ANGLE;163.99
wy.gralprd   +X16,SEntRd,+X17   SHARP_ANGLE   145.64   wy.gralprd;+X16;SEntRd;+X17;SHARP_ANGLE;145.64

wy.gralprd   +X26   HIDDEN_JUNCTION   3   wy.gralprd;+X26;;;HIDDEN_JUNCTION;3
wy.gralprd   EEntRd,SouRimDr   VISIBLE_DISTANCE   12.71   wy.gralprd;EEntRd;SouRimDr;;VISIBLE_DISTANCE;12.71
wy.gralprd   NEEntRd,NEntRd_E   VISIBLE_DISTANCE   17.02   wy.gralprd;NEEntRd;NEntRd_E;;VISIBLE_DISTANCE;17.02
wy.gralprd   NEntRd_W,NEntRd_E   DUPLICATE_COORDS   (44.976343,-110.700999)   wy.gralprd;NEntRd_W;NEntRd_E;;DUPLICATE_COORDS;(44.976343,-110.700999)
wy.gralprd   NEntRd_W,YakCampRd,+X01   SHARP_ANGLE   157.12   wy.gralprd;NEntRd_W;YakCampRd;+X01;SHARP_ANGLE;157.12

wy.gralprd   NorCynRd_E,NEEntRd   VISIBLE_DISTANCE   16.12   wy.gralprd;NorCynRd_E;NEEntRd;;VISIBLE_DISTANCE;16.12
wy.gralprd   OldFaiRd,SEntRd   VISIBLE_DISTANCE   16.20   wy.gralprd;OldFaiRd;SEntRd;;VISIBLE_DISTANCE;16.20
wy.gralprd   YakCampRd,+X01,BunPeakRd   SHARP_ANGLE   138.99   wy.gralprd;YakCampRd;+X01;BunPeakRd;SHARP_ANGLE;138.99
wy.sentrd   US89/191,LewLake   VISIBLE_DISTANCE   11.06   wy.sentrd;US89/191;LewLake;;VISIBLE_DISTANCE;11.06
« Last Edit: January 01, 2019, 12:27:30 pm by si404 »

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1035
  • Last Login:Today at 02:49:16 pm
    • Hot Springs and Highways pages
Re: usanp (U.S. National Park Highways)
« Reply #134 on: January 01, 2019, 08:40:41 am »
Datacheck issues, most of which are Visible Distances (that we don't need to mark as FP as they are removed as errors when system activated). I'm sure most are false positives

ca.bigoakrd   BigOakRd   LABEL_SELFREF      ca.bigoakrd;BigOakRd;;;LABEL_SELFREF;
ca.elporrd   SenDr_S,NorDr,SenDr_N   SHARP_ANGLE   163.07   ca.elporrd;SenDr_S;NorDr;SenDr_N;SHARP_ANGLE;163.07
ca.elporrd   SouDr_W,SouDr_E   DUPLICATE_COORDS   (37.716941,-119.666224)   ca.elporrd;SouDr_W;SouDr_E;;DUPLICATE_COORDS;(37.716941,-119.666224)
ca.laspeakhwy   +x188,+x191,+x192   SHARP_ANGLE   139.36   ca.laspeakhwy;+x188;+x191;+x192;SHARP_ANGLE;139.36
ca.minsumrd   RedsMeaRes,+X799297,RedsMeaCamp   SHARP_ANGLE   136.22   ca.minsumrd;RedsMeaRes;+X799297;RedsMeaCamp;SHARP_ANGLE;136.22
ca.minsumrd   SodaSprCamp,AgnMeaRd,CA203   SHARP_ANGLE   156.13   ca.minsumrd;SodaSprCamp;AgnMeaRd;CA203;SHARP_ANGLE;156.13

The BigOakRd label self-ref can be fixed by renaming that point to TioPassRd. BigOakRd is a point in use, so list files would be broken.

The two ElPorRd duplicate coordinates are FPs, due to the route being a lollipop-shaped loop route that intersects itself.

The sharp angle errors are also FPs, except one in MinSumRd can be easily eliminated by removing shaping point +X799297. The ones on LasPeakRd can be eliminated by removing two shaping points and tweaking a third, but I'd rather leave them alone and just mark them as FPs. Also, ElPorRd needs some recenterings, which will also eliminate its sharp angle error.

While we're at it, I'll tweak CA ScoCasRd, CA and NV DayPassRd, and their connecting usanv routes, to better match up with the state line and park boundary.
« Last Edit: January 01, 2019, 11:50:43 am by oscar »