Author Topic: KS K-30 K-206  (Read 2292 times)

0 Members and 1 Guest are viewing this topic.

Offline ntallyn

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 328
  • Last Login:March 24, 2024, 03:22:47 pm
KS K-30 K-206
« on: August 01, 2018, 09:48:18 pm »
K-206 is not signed on the BGSes on I-70. I did not get a chance to exit there and check the route signage.

KDOT is ridiculously consistent at marking the ends of all these little routes that run to the edge of town.

In the HB, K-30 has the waypoint "End" while the other similar routes indicate the name of the city (for example, "PaxLim" on K-138). I suggest changing "End" to "MapLim" (Maple Hill).
« Last Edit: August 26, 2018, 05:08:47 am by michih »

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: Kansas K-30 K-206
« Reply #1 on: August 03, 2018, 02:54:12 pm »
K-206 is not signed on the BGSes on I-70. I did not get a chance to exit there and check the route signage.
KDOT has been decommissioning a lot of these short city spurs over the past few years.
Gonzo per both http://wfs.ksdot.org/arcgis_web_adaptor/rest/directories/arcgisoutput/County/halfInch/DickinsonCounty.pdf and http://wfs.ksdot.org/arcgis_web_adaptor/rest/directories/arcgisoutput/City/CHAPMAN.pdf

KDOT is ridiculously consistent at marking the ends of all these little routes that run to the edge of town.

In the HB, K-30 has the waypoint "End" while the other similar routes indicate the name of the city (for example, "PaxLim" on K-138). I suggest changing "End" to "MapLim" (Maple Hill).
Interesting. http://wfs.ksdot.org/arcgis_web_adaptor/rest/directories/arcgisoutput/City/MAPLE%20HILL.pdf shows it going all the way to Main St.
OTOH: https://www.google.com/maps/@39.0791732,-96.0300191,3a,38.2y,61.45h,82.03t/data=!3m9!1e1!3m7!1saBJYX1k1FHyitYHTbb8YrQ!2e0!7i13312!8i6656!9m2!1b1!2i41
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline ntallyn

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 328
  • Last Login:March 24, 2024, 03:22:47 pm

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: Kansas K-30 K-206
« Reply #3 on: August 08, 2018, 02:55:07 pm »
KS206 has been deleted from the HB.

KDOT is ridiculously consistent at marking the ends of all these little routes that run to the edge of town.

In the HB, K-30 has the waypoint "End" while the other similar routes indicate the name of the city (for example, "PaxLim" on K-138). I suggest changing "End" to "MapLim" (Maple Hill).
While OSM shows the city line roughly following the centerline, the city map shows the roadway slightly within city limits here. Thus "End" could have been chosen for either of these reasons. Or because the END sign was there at an unnamed grade crossing...

WRT positioning...
Current & historic Wabaunsee county maps are maddeningly inconsistent:
2000 shows an end just inside the SW city limits, corresponding to the old RR crossing, as shown in the HB.
2011 seems to indicate the SW city limit itself.
2018 matches the city map, at Main St and the new RR crossing.

An endpoint at the old crossing makes sense from a historical perspective:
https://historicaerials.com/location/39.07976968182654/-96.0288280248642/2002/17
The county road along the SE side of the tracks was built by 2006, after which the old crossing was discontinued, while the endpoint stayed in place. The county map took a while to get updated.
Eventually, the endpoint may have moved (after 2013?) to the new crossing. Makes sense in that that's where the county road access is now.
The 2000 county map still doesn't make sense in this context, though.

Has the endpoint really been bouncing around this much over the past 18 years?
Or, could it be there's some oddity in the way KS30 is defined, and thus mapped?
Could KS30 have been extended quietly on paper in the last few years, with the END sign just staying put?
Or, could it be that the END sign is now farther northeast, at Main St and the new RxR?
Where does KS30 end?

Notice the pavement change, too.
Yup. The contrast is so striking that that caught my attention before the actual END sign!
« Last Edit: August 08, 2018, 03:05:00 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: Kansas K-30 K-206
« Reply #4 on: August 18, 2018, 02:35:02 pm »
In the HB, K-30 has the waypoint "End" while the other similar routes indicate the name of the city (for example, "PaxLim" on K-138). I suggest changing "End" to "MapLim" (Maple Hill).
After some discussion on AARoads, I'm satisfied that this right thing to do, without changing the point's coords.

https://github.com/TravelMapping/HighwayData/pull/2128
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca