Author Topic: OR: HIDDEN_JUNCTION datachecks  (Read 7914 times)

0 Members and 1 Guest are viewing this topic.

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
OR: HIDDEN_JUNCTION datachecks
« on: June 06, 2017, 09:30:45 pm »
It looks like all these HIDDEN_JUNCTION datacheck errors in Oregon routes are the result of broken concurrencies.  I'm going to copy in the "nmp_merged" versions of the routes in Oregon that should fix these.  They'll all be part of a single commit so we should be able to back the changes out if the result is disastrous for some reason (seems unlikely).

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #1 on: June 06, 2017, 10:32:31 pm »
Oh well, that didn't fix most of the broken concurrencies.  The nmps weren't quite near-enough misses to be matched up. Maybe I'll tackle those manually now...

Offline Bickendan

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 553
  • Last Login:Yesterday at 09:47:18 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #2 on: June 07, 2017, 12:33:04 am »
I've been sidetracked with other things so I haven't gotten to it, and my net connection isn't stable enough to do any work at the moment,  but I have glanced at it. 
In a nutshell, US 30, OR 99, 99E and 138 (the three OR routes weren't part of that update) need to be synced to I-5.
I-84 needs to be synced to US 30.
I-405 needs to be synced to US 26 and 30 (I-405 wasn't part of the update and possibly to I-5 at the southern terminus. 
The US 20/26 overlap should be fine,  but OR 201 might need to be synced. 
US 395 might need syncing to I-82, US 30 then I-84, US 26 and 20 (OR 140 wasn't done yet).
OR 34 should be good along US 20, but OR 99W, 99E and 126 might not be. 
OR 200 along 36 may be slightly off.

Those are all the overlaps in Oregon I can think of off the top of my head.
« Last Edit: June 07, 2017, 10:39:05 pm by Bickendan »

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #3 on: June 07, 2017, 08:05:13 am »
Thanks.  I knocked off a few of them last night and will take care of the rest when I get a minute here and there.

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #4 on: June 07, 2017, 03:49:21 pm »
Looks like I fixed many but not all concurrencies, but introduced a bunch of duplicate (hidden) labels.  I'll make another pass tonight.

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #5 on: June 07, 2017, 05:28:44 pm »
Note to do later: reposition I-5(129) and corresponding points in OR 99 and OR 138.

Offline Bickendan

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 553
  • Last Login:Yesterday at 09:47:18 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #6 on: June 07, 2017, 10:41:57 pm »
Thanks. I'll be able to focus on cleaning up the >100 routes (can't remember if I did US 97) and start to prep up the ORH system.
I'll need to add in the Hist US 30 route along US 30 between Mosier and The Dalles (it's signed there as well as in the Falls section of the Gorge).

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2856
  • Last Login:Today at 03:19:38 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #7 on: June 07, 2017, 11:22:29 pm »
Most errors are taken care of.  I'll knock off the ones that slipped through.  I made other minor fixes and improvements as I noticed things in the files I had open anyway (like extraneous exit numbers in labels, nmps for intersections), but did not do any sort of thorough pass through all of the routes.

Offline Bickendan

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 553
  • Last Login:Yesterday at 09:47:18 pm
Re: OR: HIDDEN_JUNCTION datachecks
« Reply #8 on: August 03, 2017, 06:55:11 am »
Issue has finally been solved.
Any expected issues with I-5, OR 99, and 138 will be addressed when the two routes are cleaned up.