Oklahoma concurrencies

[Jim]

https://github.com/TravelMapping/Web/issues/57

I'm guessing these are highway data problems, not data processing or web interface problems.

[mvak36]

Sorry my mistake I posted in the wrong folder in Github

[Jim]

Sorry my mistake I posted in the wrong folder in Github

Not a problem.  We'll take corrections however we can get them.

[yakra]

Fixes are in progress...

I-44: Exit 40A to Exit 46 <--Exits 41, 45, 46 coords mismatch
I-44: Exit 107 to Exit 115 <--All points' coords mismatch
I-240: Exit 1B to Exit 4A (I-35 Exit) <--All points' coords mismatch
I-35: Exit 121B to Exit 130 <--122B, 123A, 124A, 125A, 125B, 126, 127, 129, 130 mismatch
I-40: Exit 221 to Exit 240 <--All points' coords mismatch

Note: I have also found similar issues with US64, US70, US77, US277(possibly), US281(possibly), and US412 (possibly). I have only checked concurrencies of US highways with Interstates.

No comments on this right now; just including it for reference.

-----

Just by looking at the US62 examples mvak36 provided, it appears OK is plagued by the mysterious "point drift" that affected the Interstate &
US Routes in the early years of CHM. I took some time to correct the other states I maintained a few years back, but didn't touch OK, as mwasleski maintained it at the time.

OK can surely benefit from a larger-scale "Operation Multiplex".

The Oklahoma State Highways are likely okay for the most part, with the possible exceptions of:
• A state hwy leaving a multiplex with one I/US route and joining another
• Multiplexes along I/US route concurrencies that are themselves broken

[yakra]

Operation Multiplex, parts 1-3

Bookmark:
USAI USAIB USASF
US59 *
USAUSB USAOK

Concurrencies:
I-35 / US77 : 1
I-35 / US77 : 113 114 117 118 119A 120 122B 123A 124A 125A 125B 126
I-35 / US62 : 122B 123A 124A 125A 125B 126 127 129 130
I-35 / US77 : 141 142 143 146 151 153
I-35 / US64 : 186 193 194
I-40 / US62 : 151B to 153, Change US62 coords to I-35, and this gets fixed in the process.
I-40 / US62 : 221 to 240, All coords mismatch
I-40 / US75 : 231 237 240
I-44 / US277 : 1 5
I-44 / US281 : 1 5
I-44 / US277 : 30 33 36 37 39 41 45 46
I-44 / US281 : 30 33 36 37 39 41 45 46
I-44 / US62 : 41 45 46
I-44 / US62 : 107 to 115, All coords mismatch
I-44 / US412 : 237 238 241 242
I-235 / US77 : 1C 1D 1E 1G 2A 2B 4A 4B
I-240 / US62 : 1B 1C 2A 2B 3A 3B
I-244 / US75 : 2 4A 4B
I-244 / US64 : 4B 5A 5B
I-244 / US412 : 5B 6A 6B 7 8 9 10 11 12B 13A 13B 14 15 I-44
I-444 / US64 / US75 : US64/75 match; replace I-444 coords
I-40BLHen / US62 : fix both I-40BLHen points only
I-40BLSal / US59 : all points
I-40BLSal / US64 : all points; use coords from US64
US54 / US412, OK136, US64
US56 / US64, US412, US385
US59 / US270, US271, OK9, US64, OK100, OK51
US59 / US412AltLoc ..... US59 +X05921 gets coords from US412AltLoc +X4
US59 / OK10 (Kansas - Grove), OK20, US60, US69, OK10 (Miami - Welch), OK2Vin

Tripoints, etc.
I-35 121B / I-240 4A / US62 I-35(121B)
I-35 126 / I-40 151B / I-235 1A / US77 I-35(126)
I-35 194 / US64 I-35(194) / US412 I-35
I-40 240 / US62 I-40(240) / US75 I-40(240) / IndNatTpk 104
I-44 115 / I-240 1A / US62 I-44(115)
I-44 127 / I-235 4B / US77 I-235(4B) ..... all 3 mismatch
i-44 237 / I-244 I-44 / US412 I-44(237) ..... I-44 & US412 match; I-244 no
I-244 4B / I-444 I-244_W / US64 I-244(4B) / US75 I-244(4B) ..... US64/75 match; others no
I-244 5B / US64 I-244(5B) / US412 I-244(5B) ..... US64/412 match; I-244 no
I-244 6B / I-444 I-244_E / US75 I-244(6B) / US412 I-244(6B) ..... US75/412 match; others no
I-244 13B / US169 I-244 / US412 I-244(13B) ..... US169/412 match; I-244 no
I-40 308 / I-40BLSal I-40_W / US59 I-40 ..... Use I-40BL coords in other 2
I-40 311 / I-40BLSal I-40_E / US64 I-40(311) ..... Fix in all 3

I-40: Check plexes again (incl I-35)
I-40BLWea: Endpoint coords don't match I-40
US56: 12thStS -> 12thSt
US59: US69_S -> US60/69
US75: 7th8thSt +-> 7thSt

US270:
Mark I-40(147C) as closed
Add I-40(148B)
confirm that shaping point before 151B matches I-40

US412: Fix StiConn
StiCon: US412 coords

Pulls: region/mapview, before -> after
#580: 13060.9 / 15791.84 -> 12981.4 / 15791.87 mi
#592: 12981.4 / 15791.87 -> 12961.4 / 15791.92 mi
#596: 12961.4 / 15791.92 -> 12953.6 / 15791.45 mi

Submit:
USAI: 35 40 44 235 240 / USAUS: 62 64 75 77 270 277 281 412
USAI: 44 235 240 244 444 / USAUS: 62 75 77
USAI: 40 / USAIB: 40BLHen 40BLSal 40BLWea / USASF: StiCon / USAUS: 59 64 412

[yakra]

Operation Multiplex, part 4

Bookmark:
USAI USAIB USASF
US77 *
USAUSB USAOK

Concurrencies:
US60 / OK51, US283, OK34, US270/OK3, US281, OK58, US412, OK8, OK132, US81, US64, OK74, US77, US177, OK99, OK123, US75, US69, OK125, OK10

US62 / OK6, US277_Por, US281, OK19, OK9, OK8, US81, US277 (Chickasha), OK76, OK56
US62 / OK27 ..... replace OK27 I-40 coords
US62 / US75, OK72, US64, OK16, US69, OK10, OK82, OK51

US64 / US412 (Guymon), US385, OK95, OK136, US83, US270, OK23, US283, US183, OK34, US281, OK8, OK58, OK132, US81, US412 (Enid), US77, OK18, OK99, US412 (Tulsa), OK51, US169, OK72, OK16, US69, OK100, OK10

US69 / US75, OK3Ada, OK43, OK10

US70 / US183, OK36
US70 / US277:
   I-44: use coords from OK I-44 5
   OK70C: No route in HB. Point not on US277/281. On County/Control/City maps; label unused. Rename/add 6thSt?
US70 / OK76, US377, US271
US70 / US259 / OK3Ada
   extraneous shaping point on US259 / OK3Ada

US75 / OK3Ada, OK31, US270, OK11, OK10
US77 / OK32, OK7, OK29, OK19, OK74Pur, OK39, OK51, OK15, US177, OK11

Tripoints, etc.
I-44 5 / US70 I-44 / US277 I-44(5) / US281 I-44(5) ..... mismatch on US70

US60: OK58_N -> OK8/58
US77: ManRd +-> MtVicaRd; OK77C_W -> MainSt_Pur; OK77C_E -> CanAve
OK39: OK77C_W -> MainSt_Pur; OK77C_E -> CanAve
OK53: Routing at I-35 & US77: County map 2009/2010; City map 2010; Control section map 2012, agrees with GMSV & HB. Leave as-is.
OK74Pur: OK77C -> MainSt

Pulls:
#635: 12953.6 -> 12943.8 mi

Submit:
USAUS: 60 70 77 259 277 281
USAOK: 3Ada 27 39 74Pur

[snowedin]

I just noticed that my stats show a gap in OK66 between I-44(126) and I-44(128A), even though I have I-44 clinched entirely.

[yakra]

Operation Multiplex, part 5

Bookmark:
USAI USAIB USASF
USAUS *
USAUSB USAOK

Concurrencies:
US283 / OK34 ..... replace OK34 OK9_W coords
US64/412 / OK3 @ N0570 ..... N0570 added to OK3
US64/412 / OK3 @ N0720 ..... N0720 added to OK3
I-44/US412/OK66 ..... I-44(238) & I-44(241) recentered on OK66

US64: US183_S jct (newsworthy)
US177: Add OK18A
US183: US64_W jct (newsworthy)
US270: recenter IndNatTpk
62BusHen: resync US62_E coords to I-40BLHen US62_E
75BusHen: resync US75_N coords to I-40BLHen US62_E
OK1: recenter IndNatTpk
OK3: resync I-44(115) thru I-240(4C)
OK37: resync I-44(108) thru I-44(110)
OK59: move US270 point
OK152: recenter US283

CheckMe:
OK6 & OK34 routings in Elk City
OK15/74 N of Covington? ..... Completely stupid, bur for real.

Pulls:
#673: 12943.8 -> 12903 mi

Submit:
USAUS: 64 177 183 270
USAUSB: 62BusHen 75BusHen
USAOK: 1 3 34  37 59 66 152

YYYY-MM-DD;Country;Route;Root;Description

2017-07-09;(USA) Oklahoma;US 64;ok.us064;Removed from Stone City Park Dr between E0130 Rd and US 183, and relocated onto E0130 Rd and US183 between Stone City Park Dr and Broad St.
2017-07-09;(USA) Oklahoma;US 183;ok.us183;Waypoint US64_W moved from a point slightly north of Broad St to E0130 Rd.

[yakra]

Operation Multiplex, part 6

Bookmark:
USAI USAIB USASF USAUS
USAUSB *
USAOK

Concurrencies:
US62/69 / OK16 ..... resync US62_E coords on US69
I-40 / US69BusChe ..... resync Exit 265, both files
resync OK66@I-44(127)
I-44 / US75AltTul / OK66 ..... resync all 3 files
I-44 / OK66 (after I-244 split) ..... resync I-44 points in both files
I-244 / US75AltTul ..... resync all Exit 1 points, both files

US281BusLaw: resync termini
OK7: resync I-44
OK36: resync I-44(1)

Pulls:
#675: 12903 -> 12896.3 mi

Submit:
USAI: 40 44 244
USAUS: 69
USAUSB: 69BusChe 75AltTul 281BusLaw
USAOK: 7 36 66

[yakra]

I just noticed that my stats show a gap in OK66 between I-44(126) and I-44(128A), even though I have I-44 clinched entirely.

This is fixed now. Other parts of OK66 still need to be addressed.

-----

Operation Multiplex, parts 7-8

Bookmark: *

Concurrencies:
OK1/3Ada ..... resync OK1@OK3W/19&OK3E@OK3_E
I-35 / US70 ..... resync 29 & 31 in both files, and OK199

Tripoints, etc.:
I-40 264 / US69 I-40 / US69BusChe US69_S ..... I-40 resynced

US64: Add Lewis Ave interchange http://www.openstreetmap.org/?lat=36.142809&lon=-95.958232
OK4: MusRd_N -> YukPkwy_N
OK14: Useless multiplex at N end? No: END sign.
OK33: E terminus correct
OK45: W terminus label
OK51: Add Lewis Ave interchange http://www.openstreetmap.org/?lat=36.142809&lon=-95.958232
OK66: resync I-35(141)
OK78: N terminus correct

US64@OldOK97T&US412@129thAve: check labels for all routes

Datacheck: After each Pull Request

Pulls:
#861: 12896.3 -> 12894.4 mi
#862, #863: 12894.4 -> 12891.1 mi

Submit:
I-40 OK1 OK3E OK66
I-40 / I-35 US64 US70 OK4 OK45 OK51 OK199

[yakra]

All the multiplexes in OK should be fixed now.
I'm going to do another pass thru the OK data to look for any remaining NMPs before marking this thread as solved.

[yakra]

OK is now free of NMPs. Marking this topic as solved.
But why not leave it in the main Updates to Highway Data forum for a little while longer, in case anyone finds anything that still needs attention.