Author Topic: OR: NMPs to fix or mark as FPs  (Read 167 times)

0 Members and 1 Guest are viewing this topic.

Online Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2348
  • Last Login:Today at 04:53:04 pm
OR: NMPs to fix or mark as FPs
« on: May 26, 2022, 11:26:10 am »
In preparation for my summer work on the METAL algorithm visualization project, I'm going through things on TM and METAL and our graph data looking to remind myself of things to be done and prioritize projects.  Along the way, I noticed that we have a lot of NMPs not marked as false positives in Oregon.  It looks like many are just points that need to be aligned at intersections.  @Bickendan do you have a little time to fix those up or mark them, or can I or someone else take care of them?  It would really improve the graph data a lot for those loading the Oregon graphs in METAL.

Offline Bickendan

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 469
  • Last Login:Today at 10:11:17 am
Re: OR: NMPs to fix or mark as FPs
« Reply #1 on: June 01, 2022, 11:06:42 pm »
Slowly looking this over, and honestly, I'm not sure I can get to making the changes themselves if you want to do it... Right off the bat, all of OR 46's are FPs.
OR 66's are FPs being used to avoid a sharp angle.
US 30H Columbia River Highway: FP
I-84/US 30 and US 30H Cascade Locks: Technical FP
US 30 (and US 30H Rowena Crest): FP, also FP for US 30 in The Dalles.
I-5/US 26/OR 43/I-405: Shape points near exit points through the Ross Island Maze are FPs.
OR 74: FP
OR 201/ID 19: ID 19 is better... but the OR/ID point is not on the border per OSM.
Generally speaking, for all others, the higher numbered route should be synced to the lower numbered route.
Exception: OR 78 needs to be synced with US 95.
OR 34/99E: Defer to OR 99E
I-5/OR 99E/120: Defer to I-5
I-84/US 30/US 30 Byp: Defer to I-84
US 20/OR 78/US 395: Defer to US 20
OR 51/99W/194: Defer to OR 99W
US 20/97/Bus 97: Defer to US 97
US 97/[Bus 97]/OR 126: Defer to US 97 in both ends of the 97/126 overlap. Might as well include @Yakra's notes in the other thread:
Quote
US97BusRed:
OR126 -> OR126_W
The S end is synced up with OR126, but US97 is an NMP. US97's coords are a tiny bit closer to the center, but if you only want to resync one point, moving US97's here is easier.

US97:
US97Bus/OR126 -> US97Bus/126. Also the aforementioned NMP.
OR126 -> OR126_E

OR126:
US97/97Bus: With US97Bus ending here, wouldn't US97_S be better?
US97 -> US97_N. This point's also an NMP with US97; recommend moving here to sync up.
US 26/97/OR 361: Hard to tell with only two points present/labeled in the NMP tool, but defer to US 26.

Online Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2348
  • Last Login:Today at 04:53:04 pm
Re: OR: NMPs to fix or mark as FPs
« Reply #2 on: June 04, 2022, 11:34:43 am »
Thanks.  I marked the FPs you mentioned and fixed the ones specifically listed here.  I will go through others as time permits.

Online Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2348
  • Last Login:Today at 04:53:04 pm
Re: OR: NMPs to fix or mark as FPs
« Reply #3 on: June 04, 2022, 05:59:12 pm »
A complete pass through the OR NMPs is done, I found a few more FPs but mostly matched up points.  When I noticed other things, like unused alt labels or waypoint labels that no longer comply with standards, I took care of those but did not make any kind of comprehensive effort for those.  I'm running an extra site update now so if I messed anything up I can fix it for tonight's regular update.

The main thing the typical user will notice is that many routes will have lengths changed by small amounts, and since several concurrencies will now be detected properly, some might see new mileage on some routes where only one of a concurrent set were listed, but will also reduce the total amount of mileage now that those with both routes in a concurrency listed will be credited (overall) just once.

Online Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2348
  • Last Login:Today at 04:53:04 pm
Re: OR: NMPs to fix or mark as FPs
« Reply #4 on: June 04, 2022, 06:17:09 pm »
Forgot about this one, which I'm not sure about.  SE of Astoria, US 101, US 101 Business, and OR 104 Spur all sort of meet and I'm not sure if there are intentionally 2 points there since it looks like you can only enter/exit US 101 from the other routes, not continue across US 101.  Is it good as it?

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1362
  • Last Login:Today at 04:00:41 pm
Re: OR: NMPs to fix or mark as FPs
« Reply #5 on: June 04, 2022, 06:43:14 pm »
Something went wrong with OR 126. A point is out of order or something.

https://travelmapping.net/hb/showroute.php?units=miles&u=mapcat&r=or.or126
Clinched:

Online Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2348
  • Last Login:Today at 04:53:04 pm
Re: OR: NMPs to fix or mark as FPs
« Reply #6 on: June 04, 2022, 08:57:48 pm »
Something went wrong with OR 126. A point is out of order or something.

https://travelmapping.net/hb/showroute.php?units=miles&u=mapcat&r=or.or126

Sure did!  Looks like I copied the wrong x9 shaping point from US 20.  It will be better a little later this evening, thanks for the heads up.

Offline Bickendan

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 469
  • Last Login:Today at 10:11:17 am
Re: OR: NMPs to fix or mark as FPs
« Reply #7 on: June 05, 2022, 04:21:09 am »
Forgot about this one, which I'm not sure about.  SE of Astoria, US 101, US 101 Business, and OR 104 Spur all sort of meet and I'm not sure if there are intentionally 2 points there since it looks like you can only enter/exit US 101 from the other routes, not continue across US 101.  Is it good as it?
104S is strange, since you physically can't drive across 101 to clinch it. I'd suspect ODOT wants to get rid of it between 104 and 101B.
I'll look at the GIS to reverify 101B's routing and whether it ends at 101/104S or swing north on unsigned 105.