Author Topic: Tennessee State Highways (usatn)  (Read 20346 times)

0 Members and 1 Guest are viewing this topic.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2847
  • Last Login:Today at 11:30:30 am
Re: Tennessee State Highways (usatn)
« Reply #60 on: June 16, 2017, 12:30:52 am »
I've never liked that part of Tim's waypoint labeling.  Always preferred a more a descriptive waypoint for multiple route crossings,
I tend to mix-n-match the two conventions, based on what works best in a given context. In Texas, there's a lot of FM42_A, FM42_B, FM42_C... In New England, I use town suffixes more, ME9_Sca, ME9_SPo, ME9_Cal, ME9_Bai. Then there's the hybrid AbcN type as Si mentioned: US1 has ME161_CarA, ME161_CarB, ME161_CarC, ME161_FtKS, and ME161_FtKN. :D
I think later on, Tim was moving toward deprecating city suffixes (?) (or at the very least, the 4-letter city+direction kind) in favor of just the _A _B _C type. Now THAT is what gave me heartburn. It got as far as making (Jeff, was it?) relabel a bunch of county roads in (WI, was it?) to a much less intuitive system. Yecch.

like TN56Coa (for Coalmont) or TN56Alt (for Altamont).
Though I've gotta be anal here and point out that  TN56Coa would be correct in the case of multiple segments of TN56 in the browser, one of which is the "TN56Coa" ("list file name") Coalmont segment. If there are multiple segments intersecting a route being plotted, we can use the highway name, in this case TN56Coa. Otherwise, if there's just one TN56, intersecting our route in multiple places, one of which is Coalmont, then the citty suffix tacked on to the TN56 label would use an underscore, I.E. TN56_Coa, TN56_Alt. (I can definitely see room for confusion here, and have seen a lot of such confusion in labeling in the HB over the years. Including in my own early work. US1AltWHAT? *Walks away whistling casually*)
Clear as mud?  ::)

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1023
  • Last Login:Today at 10:09:38 am
Re: Tennessee State Highways (usatn)
« Reply #61 on: June 16, 2017, 08:54:55 pm »
For TN108 I decided to go with _S, _AltS, _AltN, and _N.
Clinched:

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #62 on: June 29, 2017, 10:20:51 am »
TN110 - fine
TN113 - fine
TN114 - fine
TN116 - fine
TN117 - fine
TN118 - TN54 -> TN54/89?
TN119 - fine
TN120 - fine
TN121 - fine
TN122 - fine
TN123 - fine
TN124 - fine
TN125 - fine
TN126 - shaping point before TN93_N move to Orebank Rd and make visible
TN127 - fine
TN128 - fine
TN128Trk - fine
TN129 - fine

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #63 on: June 29, 2017, 11:49:12 am »
TN131 to TN149 - fine

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #64 on: July 25, 2017, 06:33:49 am »
TN151 to TN168 - fine
TN169 - move shaping point to VanRd
TN170 to TN173 - fine
TN174 - add points for Conference Drive and Harris Drive (link to interchange)
TN175 - add points for Riverdale Road and the Forest Hill - Irene Road (link to interchange)
TN176 to TN199 - fine

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1023
  • Last Login:Today at 10:09:38 am
Re: Tennessee State Highways (usatn)
« Reply #65 on: July 25, 2017, 11:14:08 am »
For TN174, since Conference Dr is only 250m away from the I-65 interchange, I added one at Caldwell Dr instead, which should serve visitors to the built-up area better. And I also added a point on TN175 for Kirby Pkwy since it also leads to an interchange. All other changes made and submitted.
Clinched:

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #66 on: July 26, 2017, 02:51:34 pm »
Conference Drive, while close, seems to be the route between the two freeways. However, Cadwell Drive is reasonable enough.

TN200 to TN205 - fine
TN206 - replace shaping points with points at Meade Lake Rd, Rosemark Rd (both yellow in OSM, so relatively major) and maybe Old Memphis Road
TN207 - fine
TN208 - add point for Lake Dr?
TN209 - TN88 -> TN88/180
TN210 to TN212 - fine
TN213 - are Lk and Aprt valid abbreviations?
TN214 to TN249 - fine

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #67 on: July 27, 2017, 06:24:34 pm »
TN250 to TN253 - fine
TN254 - are Pk and Mt valid abbrevs? I rather like them, but just to say that they aren't standard, AFAICS
TN255 to TN265 - fine
TN266 - US70S -> US41/70S
TN267 - fine
TN268 - US41 -> US41/70S; replace 1st shaping point with point at Sulphur Springs Road
TN269 - fine
TN269Eag - fine
TN270 - fine
TN271 - TN431 -> US431
TN272 to TN276 - fine
TN277 - I know it's close to the point for South Avenue, but South Boulevard looks to be worth adding a point for
TN279 to TN283 - fine
TN284 - Arpt
TN285 to TN291 - fine
TN292 - TN56 -> TN53;
TN293 - fine
TN294 - TN52 -> TN52/85
TN295 - fine
TN296 - fine
TN297 - IndRockTr -> IndRockTrl
TN298 - fine
TN299 - Lwr

General point - a couple of routes seem over zealously split when it comes to implied concurrencies.

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #68 on: July 29, 2017, 08:57:57 am »
TN400 to TN425 - fine
TN431 - ToTN22_Uni -> TN22_Uni; ToTN22_Mar -> TN22_Mar
TN434 to TN448 - fine
TN449 - point at McCarter Hollow Road, which seems to be the main entrance to Dollywood, rather than Dollywood Lane (which is the service entrance)
TN452 to TN477 - fine

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1023
  • Last Login:Today at 10:09:38 am
Re: Tennessee State Highways (usatn)
« Reply #69 on: July 29, 2017, 10:45:10 am »
TN254 - are Pk and Mt valid abbrevs? I rather like them, but just to say that they aren't standard, AFAICS
The abbreviations appear on the signs in GMSV. "Pike" is spelled out sometimes, but "Pk" is frequent enough. It doesn't need to be abbreviated, I suppose, but then neither does Road.  "Mount" instead of "Mt" seems rather frequent as well.
Quote
TN277 - I know it's close to the point for South Avenue, but South Boulevard looks to be worth adding a point for
I added it, as it's a major connector, but wonder really how many users would care about using a waypoint that's one block off from the actual end of the segment they travelled. This one certainly will cause a NMP error.

Quote
General point - a couple of routes seem over zealously split when it comes to implied concurrencies.
I explained my criteria for splitting them upthread, so if you noticed a case where I deviated from them, please let me know and I'll look into it.

All others have been submitted.
Clinched:

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2847
  • Last Login:Today at 11:30:30 am
Re: Tennessee State Highways (usatn)
« Reply #70 on: July 30, 2017, 01:18:01 am »
Pk is used for Pike throughout Pennsylvania, so there's precedent there.
Mt is a USPS standard abbreviation, so that one should be fine.

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1336
  • Last Login:Today at 09:12:07 am
Re: Tennessee State Highways (usatn)
« Reply #71 on: August 17, 2017, 10:17:10 am »
Lets get these 300s done.

TN301 - TN346: fine

TN347: RockSprDr_N -> RockSprDr_W; RockSprDr_W -> RockSprDr_E

TN348 - TN380: fine

TN381: US19W -> US11E/19W

TN382 - TN390: fine

TN392: TNs101_N -> TN101_N; TNs101_S -> TN101_S (check concurrent US127Alt)

TN394 - TN399: fine

review done

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1023
  • Last Login:Today at 10:09:38 am
Re: Tennessee State Highways (usatn)
« Reply #72 on: August 17, 2017, 02:18:43 pm »
TN347: RockSprDr_N -> RockSprDr_W; RockSprDr_W -> RockSprDr_E

Note that there is a Rock Spring Dr and a Rock Spring Rd, and TN 347 follows segments of both, so I believe that the existing labels (RockSprDr_N and RockSprRd_W) are correct.

Quote
TN392: TNs101_N -> TN101_N; TNs101_S -> TN101_S (check concurrent US127Alt)

Fixed TN381 & 392. Jim & I may eventually find a way to automate the TNs -> TN adjustment in the active systems.

Quote
review done

Thank you! I'll submit these changes this afternoon and if there are no further comments, I'll activate the system next week.
Clinched:

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2847
  • Last Login:Today at 11:30:30 am
Re: Tennessee State Highways (usatn)
« Reply #73 on: August 17, 2017, 02:57:21 pm »
Quote
Jim & I may eventually find a way to automate the TNs -> TN adjustment in the active systems.
Writing a script or program to do this may be fairly simple. You could even have it check pointsinuse.log to avoid putting extraneous AltLabels in the output files.
Only thing to watch out for would be label collisions, E.G. TNs101_N -> TN101_N if there's already a TN101_N elsewhere in the file. I see these being flagged, to be manually inspected and dealt with.

Heck, I could borrow a lot of classes and functions from GISplunge, and be a good ways toward seeing some progress...
I won't commit myself to that though; I have my hands in a lot of other sub-projects right now; gotta manage my time & attenton span... :)
« Last Edit: August 17, 2017, 02:59:32 pm by yakra »

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2816
  • Last Login:Yesterday at 12:58:14 pm
Re: Tennessee State Highways (usatn)
« Reply #74 on: August 17, 2017, 03:41:03 pm »
A script to replace TNs by TN in all wpt files of TN region?
There are 599 left in TN region. Replacing is a maximum 30s job with Notepad++, plus commit+sync+pull request... Should I do it (tomorrow)?

(I already invested more time to write this post...)