The only way that I successfully programmed the statewide Kansas system was to methodically go through all of the sites in close proximity to the highway or interstate of interest. For instance, I programmed the route from IH35 northeastward toward KC. Yes, it is tedious work, but it is well worth it. You will likely need to zoom in on the area you are wanting to program for the various toll roads in Kansas. Basically, I ended up programming the toll road from the Oklahoma-Kansas border to KC going on IH70.Shocker81
Putting in the control channels isn't the problem. Which towers along the turnpike are carrying the traffic? Unless I missed something there is no reference to the particular sites along the road that carry the radio traffic. And putting every site into my 396T would be tedious, to say the least.
I don't know if they are still using it or not KAA, but my ComL book from four years ago had the following in templates. They could have changed, but I know for sure that I had some very unfun conversations with KTA during the Reading tornado response taking so much tower space on three towers in that area.The point that Shocker was trying to make is that even though there may be more than 77 towers in the system, there are only so many different frequencies used throughout it. Therefore, you will find that multiple towers across the state use the same control channels. As a result, simply by programming the control channels for the system most scanners will allow you to monitor the system as you move through it. Just an alternative to adding all the sites along the Pike.
In case you still want to do that though, here are the primary sites (from north to south):
Leavenworth County subsystem
Douglas County tower (soon to be the Douglas County subsystem)
Cottonwood Falls Tower
Butler County subsystem