Did I-515 in Las Vegas become I-11?

[404inthe404]

Driving this morning in the construction zone near downtown, heading south on I-515, I noticed just north of Charleston that the sign assembly had "I-11 / US 93 / US 95." To my knowledge, I did not know I-515 was intended to be designated as I-11 (although I always thought it was a foregone conclusions, just the studies had to be done first). Later on, even in the same construction zone, the freeway was only referenced as I-515.

Is I-515 becoming I-11?

[Alps]

I think they officially set it as such - check the threads in here: https://www.aaroads.com/forum/index.php?topic=7881.0

[ilpt4u]

Bumping this, because the part in bold...

It's time to open the bets. What is happening at this meet? A new US Route for the first time in 17 years? I-515 dropped in favor of I-11? I-590 designated to serve my planned pie-in-the-sky development near Belvidere, Illinois? Or what else?

... actually happened at this meeting. This turned out like Plutonium getting Pu as its symbol, I said that as a joke and kaboom, it gets through.

From the October 2022 AASHTO thread
https://www.aaroads.com/forum/index.php?topic=32315.msg2779592#msg2779592

[404inthe404]

Interesting, thank you. I even did a search for this but had no idea it happened so long ago. Even Google still lists it as I-515.

[vdeane]

Interesting, thank you. I even did a search for this but had no idea it happened so long ago. Even Google still lists it as I-515.

Just because it was determined and got AASHTO approval doesn't mean the signs were updated.  Some of those take a really long time between approval and actually getting signed in the field.  I think that I-11 sign you mentioned might be the only one so far.

[The Ghostbuster]

Hopefully there will be a lot more Interstate 11 signs in the future. It's time for the Interstate 515 designation to R.I.P.

[Rothman]

This is going to be another case where a route changes on a road and Travel Mapping is going to say I've clinched something I haven't...

[ilpt4u]

Interesting, thank you. I even did a search for this but had no idea it happened so long ago. Even Google still lists it as I-515.

Just because it was determined and got AASHTO approval doesn't mean the signs were updated.  Some of those take a really long time between approval and actually getting signed in the field.  I think that I-11 sign you mentioned might be the only one so far.

Perfect example is I-265 for the "gap" segment of the Louisville 3/4 beltway that was finished with the East End Bridge over the Ohio. AASHTO approved the I-265 designation for both the Indiana and Kentucky segments at the Spring 2019 meeting, and it is still unsigned to this day (apparently FHWA has some additional requirements to be met before giving its ok for the unified route number, mostly to do with mile markers/exit numbers starting at "0" at the KY 65/265 interchange and IN continuing KY's mile markers. At present, both segments count "up" to the state line on the new bridge, and the KY "0" point is the KY 841/US 31W/US 60 interchange)

[Rothman]

Well, sure.  FHWA holds authority over what is considered part of the IHS and is eligible for 90% NHPP funding, not AASHTO.

[rickmastfan67]

This is going to be another case where a route changes on a road and Travel Mapping is going to say I've clinched something I haven't...

Can't be helped, especially if you have inside of your list file the underlying US highways that are along it, due to the multiplex detection.

[Rothman]

This is going to be another case where a route changes on a road and Travel Mapping is going to say I've clinched something I haven't...

Can't be helped, especially if you have inside of your list file the underlying US highways that are along it, due to the multiplex detection.

I don't.  I just have I-515 in there.  But, there's a 50/50 chance that they'll just flip the code and automatically count I-11 as clinched...

[cl94]

As of right now, there have been zero substantial changes to 515, either internal or signage. I drove it today and that shield is a one-off. Similarly, nothing backend shows 515 being removed.

[Alps]

This is going to be another case where a route changes on a road and Travel Mapping is going to say I've clinched something I haven't...

Can't be helped, especially if you have inside of your list file the underlying US highways that are along it, due to the multiplex detection.

I don't.  I just have I-515 in there.  But, there's a 50/50 chance that they'll just flip the code and automatically count I-11 as clinched...

I count any road I've been on as clinched, even if the number changes. New alignment is where I need to revisit.

[oscar]

This is going to be another case where a route changes on a road and Travel Mapping is going to say I've clinched something I haven't...

Can't be helped, especially if you have inside of your list file the underlying US highways that are along it, due to the multiplex detection.

I don't.  I just have I-515 in there.  But, there's a 50/50 chance that they'll just flip the code and automatically count I-11 as clinched...

FWIW, I don't have I-515 in my list file, just the concurrent routes US 93 and US 95. I'm autocredited for I-515 anyway via TM's automatic multiplex detection, and will be autocredited for I-11 whenever ci94 extends that route in TM, without my having to lift a finger.

That comes in handy for all the Texas Interstate additions which follow existing US routes I've already clinched.

In your situation, TM will autocredit you for the part of I-11 you traveled when it was I-515, by treating I-515 as an alternate route name for I-11.

I count any road I've been on as clinched, even if the number changes. New alignment is where I need to revisit.

My practice, too, unless I traveled an Interstate segment before it was upgraded to freeway (as happened with parts of US 71 gradually upgraded to I-49), in which case I had to play with my list file to turn off TM's autocrediting for those segments.

[Rothman]

Can't have been on a route that wasn't there...

[cl94]

Alright, some I-11 updates from today's travels:

I-11 is now signed along I-15 SB in place of I-515. All approach assemblies are for I-11, but the gore sign and the signs on the ramps lack any I-shields. Given the lack of signs elsewhere and the fact that I-11 signs along 515/95 are still covered, I'm going to assume it's not official yet and these signs jump the gun.

I-11 shields are also covered along CC 215 at the Centennial Bowl. CC 215 is full freeway now, with the temporary expressway segment around the Centennial Bowl gone. VMSes along 515 and 95 refer to CC 215 as "I-215", so they're also jumping the gun with 215. My assumption is that I-11 will get extended north to NV 157 (last exit before an at-grade) when the Centennial Bowl work is complete, which is when we're also likely to see the transfer of CC 215 to NDOT.

I will note that I am actively monitoring NDOT's internal systems to see when the change becomes official. As long as everything on the NDOT end is 515, we can probably assume the change is not yet official unless there is a press release.

Can't have been on a route that wasn't there...

Well, are we clinching routes or roads? CC 215 and I-515 as they exist today will be I-215 and I-11, respectively. For this reason, I'm counting CC 215 and I-515 clinches for I-215 and I-11. Just like how I'm counting an I-73 clinch for a segment that was "future" when I was on it in 2008 as there were no substantial changes since I was on it. A freeway I was on getting a new designation doesn't mean I need to redrive it to reclaim it. But I acknowledge that people view this differently and those differences are what make the hobby interesting.

[Scott5114]

Can't have been on a route that wasn't there...

You can't be on a route as it's just a bureaucratic fiction; it is a pointer to a physical road. You're on the road, not the route. And the road is the same.

[Scott5114]

To truly establish whether traveling I-515 is the same as traveling I-11, we would need the ruling of a universally-accepted arbiter of truth and logic known throughout the world. Fortunately, I happen to have one handy; it's called gcc and it comes with Linux.

Code Select Expand


#include <stdio.h>

int main()
{
    int freeway = 93 + 95; /* This is the physical road */
    int *i11;  /* I-11 designation */
    int *i515; /* I-515 designation */
   
    i515 = &freeway; /* assign I-515 to freeway on July 12, 1976 */
    i11 = &freeway;  /* assign I-11 to freeway in 2022 */
   
    if(*i515 == *i11) /* See if I-515 and I-11 are the same */
    {
        printf("Traveling I-515 is the same as traveling I-11\n");
    }
    else
    {
        printf("Traveling I-515 is different than traveling I-11\n");
    }
   
    return 0;
}


Output:
Traveling I-515 is the same as traveling I-11

Quod erat demonstrandum.

[Rothman]

The complicated and perverted wrestling of logic roadgeeks will go through to not lose a clinch...

I clinch routes.

Makes it a lot easier for discussions when one is asked if they have been on a certain Interstate.

"Have you been on Interstate 11?"

"Yes, but when it was I-515."

"Wut."

[Scott5114]

If you think a single if/else pair is "complicated and perverted", that sounds like a skill issue to me.

[hotdogPi]

int freeway = 93 + 95; /* This is the physical road */

US 188 is a thing?

[Max Rockatansky]

The complicated and perverted wrestling of logic roadgeeks will go through to not lose a clinch...

I clinch routes.

Makes it a lot easier for discussions when one is asked if they have been on a certain Interstate.

"Have you been on Interstate 11?"

"Yes, but when it was I-515."

"Wut."

Going out to a city for the purposes of re-clinching a segment of freeway you've already completed because one of the three sign route designations changed is something only this hobby can come up with.

[Rothman]

The complicated and perverted wrestling of logic roadgeeks will go through to not lose a clinch...

I clinch routes.

Makes it a lot easier for discussions when one is asked if they have been on a certain Interstate.

"Have you been on Interstate 11?"

"Yes, but when it was I-515."

"Wut."

Going out to a city for the purposes of re-clinching a segment of freeway you've already completed because one of the three sign route designations changed is something only this hobby can come up with.

Well, that would be the definition of the hobby itself...

[Rothman]

If you think a single if/else pair is "complicated and perverted", that sounds like a skill issue to me.

Code means little when the premise upon which it is based is flawed.

[kphoger]

Can't have been on a route that wasn't there...

You can't be on a route as it's just a bureaucratic fiction; it is a pointer to a physical road. You're on the road, not the route. And the road is the same.

Or...  A road is a type of route.  A route is the way you get from A to B.  But are we clinching numerical designations?