Author Topic: HI 3000 endpoint label question  (Read 511 times)

0 Members and 1 Guest are viewing this topic.

Online oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 637
  • Last Login:Today at 01:34:06 pm
    • Hot Springs and Highways pages
HI 3000 endpoint label question
« on: October 17, 2018, 04:58:23 pm »
I drove out yesterday to the newly-extended Lahaina Bypass (HI 3000). An unexpected find was that HI 3000's south end isn't where the HB now has it, at an intersection with HI 30. Rather, it starts about 0.5 mile southeast, around where the new bypass pavement peels away from the old HI 30 alignment at a now-closed intersection. That short segment is clearly signed and milemarked as HI 3000, but is an implied concurrence with HI 30 which continues both west into Lahaina and beyond (via a short new Southern Connector road) and east to the Olowalu Tunnel and beyond.

My leaning is to extend HI 3000 to what is now HI 30's *OldHI30_E waypoint, name that endpoint HI30/*OldHI30 in the HI3000 route file, and rename it HI3000/*OldHI30 in the HI 30 route file (retaining the file's *OldHI30_W point, where HI 30 returns to its original alignment). It seems unusual to put an asterisk in the middle of a waypoint label, but it helps identify the endpoint location as a closed intersection. 

Another option would be to make HI 3000's new endpoint simply *OldHI30, and keep the existing waypoint labels in the HI 30 route file (except HI3000 would become HI3000_N).

Either way, in the HI 3000 file HI30 -> HI30_W, and in the HI 30 file HI3000 -> HI3000_N (since HI 3000 is a north-south route, while HI 30's overall direction as a three-quarter-circle route is east-west).

Any thoughts, in particular whether mid-label asterisks will confuse the system?
« Last Edit: October 17, 2018, 05:24:53 pm by oscar »

Offline dfilpus

  • Jr. Member
  • **
  • Posts: 81
  • Gender: Male
  • Last Login:Today at 10:38:48 am
    • Filpus Roadgeek
Re: HI 3000 endpoint label question
« Reply #1 on: October 17, 2018, 05:12:18 pm »
IMHO, the concurrency of HI30 and HI3000 should be labeled as any other concurrency.
Just HI3000_E and HI3000_W on HI 30 and HI30_E and HI30_W on HI 3000. The fact the _W points are at a closed intersection is irrelevant.

Online oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 637
  • Last Login:Today at 01:34:06 pm
    • Hot Springs and Highways pages
Re: HI 3000 endpoint label question
« Reply #2 on: October 17, 2018, 06:11:33 pm »
IMHO, the concurrency of HI30 and HI3000 should be labeled as any other concurrency.
Just HI3000_E and HI3000_W on HI 30 and HI30_E and HI30_W on HI 3000. The fact the _W points are at a closed intersection is irrelevant.

The closed intersection is definitely relevant for those who traveled HI 30 only before that route was realigned onto part of HI 3000, since they'd need to know which part of HI 30 they might want to not claim in their list files.

Offline dfilpus

  • Jr. Member
  • **
  • Posts: 81
  • Gender: Male
  • Last Login:Today at 10:38:48 am
    • Filpus Roadgeek
Re: HI 3000 endpoint label question
« Reply #3 on: October 17, 2018, 06:31:58 pm »
IMHO, the concurrency of HI30 and HI3000 should be labeled as any other concurrency.
Just HI3000_E and HI3000_W on HI 30 and HI30_E and HI30_W on HI 3000. The fact the _W points are at a closed intersection is irrelevant.

The closed intersection is definitely relevant for those who traveled HI 30 only before that route was realigned onto part of HI 3000, since they'd need to know which part of HI 30 they might want to not claim in their list files.
I am one of those people who traveled HI 30 years ago.  I can deal with whatever you name it.

To not break .list files (including mine), OldHI30_E should be kept as a hidden name for the the waypoint. The entry in the .wpt file could be
HI30_E +OldHI30_E
versus
HI30/*OldHI30 +OldHI30_E

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1718
  • Last Login:Today at 10:25:40 am
Re: HI 3000 endpoint label question
« Reply #4 on: October 17, 2018, 07:34:07 pm »
HI30:
*OldHI30_W
HI3000_N
*OldHI30_E

HI3000:
*OldHI30
HI30_W

Online oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 637
  • Last Login:Today at 01:34:06 pm
    • Hot Springs and Highways pages
Re: HI 3000 endpoint label question
« Reply #5 on: October 19, 2018, 03:19:37 am »
HI30:
*OldHI30_W
HI3000_N
*OldHI30_E

HI3000:
*OldHI30
HI30_W

I'll go with that.

I field checked earlier today my previous edits to HI 200 and HI 2000 on the Big Island. Some minor tweaks to at least HI 200. I'll pull those in along with the Maui changes above. EDIT: Pull request submitted.
« Last Edit: October 19, 2018, 05:19:17 pm by oscar »