AL: US98/US90 incorrectly formatted waypoint labels "I10*"

[rickmastfan67]

The I-10 point being hidden is due to the way the interchange is setup due to each highway leaving each other at the I-10 offramps, but needing the missing graph connection with I-10.

This will allow users browsing I-10 to click the link through to US90 and US98, but not vice versa. You're also creating a HIDDEN_JUNCTION error here.

The graph connection point needs to be either visible on both routes or simply not included. (I kinda favor the latter since other graph connections between I-10 and US 90/98 exist not that far away)

It was just a thought to keep it hidden on US-90/98 there.

[yakra]

Duke87, I believe you mean VISIBLE_HIDDEN_COLOC. These can be marked FP, and sometimes there's legitimate reason to create them.
The most familiar example for most of us may be the former end of I-22, before I-269 was completed, with a hidden point on US78 IIRC.
There are places in Europe where a Tier 1 route transitions to a lower-tier route, at like a subregion boundary or maybe a major river or whatever, all freeway or expressway, no entrance or exit. An E Road concurrent with both routes will have a hidden point at the transition.

his will allow users browsing I-10 to click the link through to US90 and US98, but not vice versa.

IMO, the fact that the link cannot be followed from both routes isn't necessarily a reason to not still allow it for one. I think it can be useful sometimes, and have done this a few places in Texas.
https://travelmapping.net/devel/datacheck.php?show=VISIBLE_HIDDEN_COLOC&showmarked=on&rg=TX

All that said, that "other graph connections between I-10 and US 90/98 exist not that far away" is a point worth considering too.

[Duke87]

Duke87, I believe you mean VISIBLE_HIDDEN_COLOC.

Yes, I do. Brain went to the first one I remembered, but that is a distinct one isn't it.

Anyway, okay, if there is precedent for this form of one-way graph connection and it can be FPed out of the datacheck error log then I withdraw my objection. It is less janky than an extra visible point on US90 and US98, certainly.

[froggie]

I finally got around to fixing the I-10 label errors, adding the hyphen.  That is the only change I intend to make here so I consider this concluded.

They will be uploaded when I do my next Alabama peer review update.

[rickmastfan67]

I finally got around to fixing the I-10 label errors, adding the hyphen.  That is the only change I intend to make here so I consider this concluded.

They will be uploaded when I do my next Alabama peer review update.

Hopefully they aren't "I-10/US98_*", as that is still a no-go label.  The 'US' part would still need to go.

[rickmastfan67]

Yep, 'I-10/US9*_*' is still a no go sadly, as I think that will still throw up an error due to the US part being in the label.

Either just remove the I-10 part (since the base US98_* / US90_* labels don't exist in either file), or go with I-10/9*_* labels.

[neroute2]

It's obviously a false positive though.

[froggie]

Doh!

I’ll refix that when I get to my next batch.

[rickmastfan67]

Doh!

I’ll refix that when I get to my next batch.

Alright.

I'll move this back into the 'main' area for now so it isn't accidentally forgotten about.

[rickmastfan67]

It's obviously a false positive though.

Not really.  Not having the second 'prefix' after a slash goes back to the early days of the project.

As for the OP, my memory's a bit hazy, but I'm pretty sure this was an early example (Alabama being one of the first sets of US routes drafted) of Tim wanting to keep point labels short, and the lack of the hyphen was deemed acceptable here.

That can't be right, unless as you said, early example. The '-' has always been there, and standardizing the usual United States route prefixes was an early priority. KS7 not K-7, MI28 not M-28 or M28, etc. In any case, why lose that one char when there's an extra "US" after the '/'? Dropping prefixes after the slash goes back to the earliest "routedata.html" days.

[si404]

Not really.  Not having the second 'prefix' after a slash goes back to the early days of the project.

The exception is single character prefixes, which there are none of in North America (because I-, etc are two characters).

[froggie]

Fixed (again).  Will be uploaded with my next peer review batch (again).