OR and CA: Almost Intersecting Points

[mikeandkristie]

On our recent trip to the Redwoods, I noticed these points that look like they should have intersections or concurrencies, but don't.  The coordinates are slightly different from each other.  Apologies if I shouldn't have combined the two states.

US101 meeting OR38 in Reedsport, OR
- US101:  43.703374, -124.104953
- OR38:  43.703521, -124.105135

US101 meeting OR42 south of Coos Bay, OR
- US101:  43.292310, -124.219365
- OR42:  43.293388, -124.218614

US199 at CA/OR border
- US199 (CA side):  41.996881, -123.721440
- US199 (OR side):  41.996897, -123.721579

US199, OR99, and OR238 in Grants Pass, OR (US199 and OR238 intersect but OR99 does not)
- US199:  42.425294, -123.330202
- OR238:  42.425294, -123.330202
- OR99:  42.425342, -123.329966

Mike

[oscar]

On the one issue involving CA (the border point on US 199), the point in the OR US 199 route file needs to be synched to the corresponding point in the CA US 199 route file.

There are similar "near-miss points" elsewhere along Oregon's southern border (US 101, I-5, US 97, US 395, US 95 -- but not OR 39/CA 139), which should be synched along with a re-synch of OR/NV140. If it's OK with Bickendan (maintainer for OR), I can fix them on both sides of the border, as maintainer for both CA and NV. There are many other non-border NMPs in Oregon besides the ones you flagged, which Bickendan may already be working on.

[Bickendan]

@Oscar -- I think I-5 and OR 39 were the only ones that I've updated while I was increasing centerline fidelity. It's possible I managed to do US 97 and 101 as well, but I don't think those were ever uploaded.
I know for certain that 39/139 being good as is was because of CA 161 also being involved, and the research I did contacting CalTrans re: the westbound lane being in Oregon.

The non-border NMPs are all because I've been working on those routes. I just can't remember where I left off in terms of uploads :/

Go ahead and give me the coordinates for US 101, 199, I-5, US 97, 395, NV 140, and US 95 so I can make changes on my local side; no point in you fixing them only for me to rebreak them when I figure out GitHub again and upload more general fixes in my dataset.

[oscar]

I went ahead and synched on the GitHub master several points on Oregon's southern border with California and Nevada, so the Highway Browser shows the routes on both sides of the border as connecting, and those points are no longer on the near-miss points log. Route files on the California/Nevada side and/or the Oregon side were adjusted as needed.

For your local files, here's the border points on the Oregon side that were changed, and are now in the Highway Browser:

OR I-5:  CA/OR +0 http://www.openstreetmap.org/?lat=42.005468&lon=-122.615474

OR US95:  NV/OR http://www.openstreetmap.org/?lat=41.998520&lon=-117.718439

OR US97:  CA/OR http://www.openstreetmap.org/?lat=42.003350&lon=-121.889125

OR US199:  CA/OR http://www.openstreetmap.org/?lat=41.996881&lon=-123.721440

OR US395:  CA/OR http://www.openstreetmap.org/?lat=41.993019&lon=-120.298084

OR OR140:  OR/NV http://www.openstreetmap.org/?lat=41.994181&lon=-119.321243


OR US101 and OR OR39 were not changed: 

OR US101:  CA/OR http://www.openstreetmap.org/?lat=41.998483&lon=-124.208282

OR OR39:  CA/OR http://www.openstreetmap.org/?lat=41.998348&lon=-121.519604

[mikeandkristie]

Thank you.

[Bickendan]

Local files have been updated.