AARoads Forum

Please login or register.

Login with username, password and session length

Author Topic: K-7 Olathe Turnback?  (Read 1815 times)

bugo

  • *
  • Offline Offline

  • Posts: 5307
  • Last Login: October 21, 2017, 11:37:15 PM
Re: K-7 Olathe Turnback?
« Reply #25 on: July 31, 2017, 06:16:00 AM »

I always thought that Metcalf (and Blue Valley Parkway) between US 69 near W 127th Street and I-35/I-635 should be Business 69. The section of US 69 that hops off of I-35 at exit 228 and hops back on at exit 231 is plain ridiculous and US 69 should just stay on I-35 through this stretch. I also think Shawnee-Mission Parkway should all be part of the state system. Perhaps US 56 could be rerouted to follow the SMP all the way to K-7, then follow K-7 south to I-35. Of course, if you wanted for the system to make sense US 69 would hop on I-35 at  (Kansas) exit 225 and hop off at (Missouri) exit 20. The orphaned parts of US 69 would become state highway or just city streets. The routing of US 69-169 in the KC metro are indeed fucked up.

silverback1065

  • *
  • Offline Offline

  • Posts: 2322
  • Age: 28
  • Location: Indianapolis
  • Last Login: October 21, 2017, 09:50:12 PM
Re: K-7 Olathe Turnback?
« Reply #26 on: July 31, 2017, 08:10:08 AM »

both 169 and 69 should follow 35 from where they cross on the northside of the city to the south side where they leave. 
Logged

SD Mapman

  • *
  • Online Online

  • Posts: 900
  • The best pace is a pace, and today is a good day.

  • Location: Running somewhere in Lawrence County
  • Last Login: Today at 02:11:51 AM
Re: K-7 Olathe Turnback?
« Reply #27 on: August 02, 2017, 09:59:00 AM »

both 169 and 69 should follow 35 from where they cross on the northside of the city to the south side where they leave.

What about the semi-freeway section of 69 between 35 and 70?
Logged
The traveler sees what he sees, the tourist sees what he has come to see. - G.K. Chesterton

silverback1065

  • *
  • Offline Offline

  • Posts: 2322
  • Age: 28
  • Location: Indianapolis
  • Last Login: October 21, 2017, 09:50:12 PM
Re: K-7 Olathe Turnback?
« Reply #28 on: August 02, 2017, 10:05:38 AM »

both 169 and 69 should follow 35 from where they cross on the northside of the city to the south side where they leave.

What about the semi-freeway section of 69 between 35 and 70?

make it K-X69 which ever number is available
Logged

stridentweasel

  • *
  • Offline Offline

  • Posts: 362
  • Age: 33
  • Location: Kansas
  • Last Login: October 08, 2017, 06:58:23 PM
Re: K-7 Olathe Turnback?
« Reply #29 on: August 10, 2017, 10:01:38 PM »

both 169 and 69 should follow 35 from where they cross on the northside of the city to the south side where they leave.

What about the semi-freeway section of 69 between 35 and 70?

make it K-X69 which ever number is available

A sensible routing such as this is impossible under current Kansas law, which prohibits a state route contained entirely within city limits.  The ridiculous routings of US 69 and 169 that we have are there because the powers that be still want some of those surface street/expressway/old-school freeway segments on the state highway system, rather than turning them over to the municipalities.  So, instead of using short state route designations such as K-X35 or K-X69, we have convoluted routings of US 69 and 169 that probably no drivers follow.  US 169 signage has also been sloppy, and I doubt many have noticed.

This is all old news.
Logged

route56

  • *
  • Offline Offline

  • Posts: 874
  • Age: 38
  • Location: Northeast Kansas
  • Last Login: October 21, 2017, 06:54:52 PM
    • route56.com
Re: K-7 Olathe Turnback?
« Reply #30 on: September 18, 2017, 12:29:14 PM »

The KDOT GIS system is now showing K-7 on the I-35/I-435/K-10 routing once again. The PDF maps of Johnson County on the KDOT website have also been changed. Again, I have not seen any evidence of signage changes in the field.
Logged
Peace to you, and... don't drive like my brother.

R.P.K.

 


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.