Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on February 17, 2016, 08:56:08 pm
-
http://clinched.s2.bizhat.com/viewtopic.php?t=1846&mforum=clinched
Froggie, do you know if everything is ok with the current 'future' files for I-22 to promote them to a normal Interstate on the site?
-
Would like to see something a little more official from MDOT first.
-
How about the AL part, froggie? Would that be safe to at least convert to a normal Interstate here?
-
The endpoint label Fut269 doesn't meet labeling conventions and should probably be changed to I-269Fut -- even if said I-269Fut isn't open to traffic yet.
Yeah, this is a weird one. I'm leaving aside the issue of ending at an unopened non-interchange; it makes sense that this is where I-22 will end once I-269 opens; I'm OK with calling it legit.
Or, alternately, what do you think of using the future exit number (12, I'm guessing?), if it's known?
On US78, as there's no interchange in service here, I recommend hiding the point (to maintain the multiplex with I-22Fut) until the interchange opens.
-
Can this be converted to a normal interstate now that it's open? Or is there something else we are waiting for? No hurry, just curious.
Thank You
-
The news articles linked from Wikipedia seem to indicate it's I-22 in both Alabama and Mississippi now, but I don't know how official any of that is. When we drove it last summer, the signs were for Future I-22 in Mississippi and I-22 in Alabama.
-
I still say we can at least convert the Alabama part to a full Interstate on the site safely. Especially since the connection to I-65 has finally opened this week.
http://abc3340.com/news/local/corridor-x-opens-today
-
I'm guessing this is good enough to move the whole thing to I-22.
http://www.fhwa.dot.gov/planning/national_highway_system/interstate_highway_system/routefinder/table01.cfm
-
While we're on AL and Future Interstates becoming Interstates, the FHWA list of Auxillary Interstates (http://www.fhwa.dot.gov/planning/national_highway_system/interstate_highway_system/routefinder/table02.cfm) has this entry.
I-685 Alabama 14 0 - - - 14 Mi on I-85
So I-685 is an unsigned interstate?
-
I'd be hesitant to consider it such, considering that "I-685" is supposed to follow existing I-85 once I-85 is moved to the Montgomery Outer Loop, which at the rate they're going won't be in any of our lifetimes...
-
So I-685 is an unsigned interstate?
I'd say no in this case, as it's suppose to depend on when I-85 is moved.
-
I drove the final part of I-22 in Birmingham tonight. It's definitely open as a full interstate (no future banners, no AL 4). The odd thing were the Corridor X US 78 signs that were in the process of being removed between I-65 & US 78. Looks like they were accidentally left in the I-22 signage plans.
The I-22 EB exit to I-65 is unnumbered. On I-65 NB, I-22 is exit 265A; US 31 is now exit 265B.
I still say we can at least convert the Alabama part to a full Interstate on the site safely. Especially since the connection to I-65 has finally opened this week.
http://abc3340.com/news/local/corridor-x-opens-today
-
The Corridor X US 78 photos on new I-22 are attached. Looks like they were being removed.
I drove the final part of I-22 in Birmingham tonight. It's definitely open as a full interstate (no future banners, no AL 4). The odd thing were the Corridor X US 78 signs that were in the process of being removed between I-65 & US 78. Looks like they were accidentally left in the I-22 signage plans.
The I-22 EB exit to I-65 is unnumbered. On I-65 NB, I-22 is exit 265A; US 31 is now exit 265B.
-
So, what do we want to do here froggie? I'd still say we should at least get the AL part online, especially since it fully posted as an Interstate all the way to I-65.
-
If you can verify that it's signed as vanilla I-22 in more than just Jefferson County, then go for it.
-
At the very least, we can immediately extend AL I-22FutJas east to I-65 (unnumbered exit), add to I-65 its new exit 265A (I-22), and rename 266 (for US 31) to 265B. I drove the new segment west to exit 81 earlier today, and can confirm what rlee said above.
-
I can confirm the above and was just about to post regarding this. Definitely open to I-65 and a few of us have been on it. Fully signed as I-22 as well, but an extension of the future would be a good temporary measure.
-
AASHTO just approved this:
Alabama Interstate 22-Establish (segment)
Between I-65 in Birmingham, AL and Coalburg Road in Birmingham, AL
Route begins at mile marker 96.480 and the junction of I-65 in Birmingham, AL from the junction of I-65 in Birmingham, AL., westerly to Coalburg Road (Exit 93) in Birmingham, AL Traveling over existing Future Interstate 22 and continuing west to Birmingham, AL. and Jasper, AL for 2.879 miles. Route ends at mile marker 93.601 and the junction of Coalburg Road in Birmingham, AL.
-
I drove that segment on Oct. 26 so I can confirm, yes, it is open and signed and I now have a bit of I-22 on my list. ;D
-
I thought Interstate 22 is signed now? Is it not official yet?
-
The newest section north of Birmingham is open, signed, and officially approved by AASHTO as regular (not "future") Interstate 22. Is there anything more needed to make it "official", and add it to the HB (along with some related change to the I-65 route file)?
It's less clear that the rest of I-22 in Alabama, which is in the HB as a future Interstate, has or can be graduated to regular I-22. AASHTO's approval for the newest segment seems to assume that west of there it's still Future I-22. The Mississippi portion is even less clear, with some Future I-22 signs reportedly still posted.
There's already a discussion of this in the Updates part of this forum (http://tm.teresco.org/forum/index.php?topic=100.0).
-
There are at least I-22 (not future) reassurance shields all the way to MS exit 14 according to the more recent street view images in both states.
-
Looking there's a total dearth of any BGSs telling you what the mainline is and where it goes - it's all those reassurance signs to know the number. All the intersecting roads (save I-65) have GMSV that's at least a couple of years old.
"I'm guessing straight on to Birmingham here at this major junction with US45?" (https://www.google.co.uk/maps/@34.2970979,-88.7103317,3a,48.4y,109.73h,89.25t/data=!3m6!1e1!3m4!1sStme3J_51ICkEoQXzCRXJw!2e0!7i13312!8i6656).
Here's a photo of I-22 shields on a side road: https://c1.staticflickr.com/8/7510/15306956713_9ceb3d5c06_m.jpg
From the thread Oscar mentions (which comes with this warning "Warning: this topic has not been posted in for at least 120 days. Unless you're sure you want to reply, please consider starting a new topic.")
If you can verify that it's signed as vanilla I-22 in more than just Jefferson County, then go for it.
I drove that segment on Oct. 26 so I can confirm, yes, it is open and signed and I now have a bit of I-22 on my list. ;D
So signage shows that it is de facto I-22. The de jure is also solid, with confusing coming from AL's recent AASHTO request (http://route.transportation.org/Documents/2016%20AM%20Boston%2c%20MA/USRN_I22%20Segment%20%28Updated%29.pdf) to convert Future Interstate 22 between Birmingham and exit 93 in Birmingham to I-22 proper. It strikes me that this is 2.879 miles of renumbering that only increased interstate mileage in the state by 0.26 miles (matching the route log on page 8's total of 96.48) is about correcting the length figure more than formalising the missing link's status as interstate.
It also clearly has a map showing I-22 save the bit it is adding as part of the existing interstate system, per the 2012 request for establishment of I-22 along 96.22 miles of Future I-22 (http://route.transportation.org/Documents/SCOH%20Report%2011-16-2012.pdf) (which included the bit from 93 to I-65) that was conditionally approved pending MS submitting an application, and FHWA approval (as FHWA list 96.22 miles of I-22 in AL, and have it as part of the interstate system on the map (https://www.fhwa.dot.gov/planning/national_highway_system/nhs_maps/alabama/al_alabama.pdf) then clearly FHWA approved it).
As for MS, then the FHWA (http://route.transportation.org/Documents/05%2014%202015%20Cheyenne%2c%20WY%20Report/FHWA%20to%20AASHTO%20Interstate%20Numbering%20May%2014%202015.pdf) approved it as I-22, with a boiler plate "they can sign it as future until it is added to the interstate network" given to all the requests. The request (http://route.transportation.org/Documents/05%2014%202015%20Cheyenne%2c%20WY%20Report/Mississippi%20I-22%20AASHTO%20Application.pdf) said the whole route met interstate standards. I-22 in MS was an interstate on paper from May 14th 2015: 710 days ago! GMSV shows that it clearly didn't take 101 weeks to sign it.
I cannot see how I-22 can be consider anything other than an official interstate all the way from Future I-269 (not yet open exit 12) to I-65.
These are Froggie's states, but his last log-in to these forums were in Feb. I've made a pull request making the changes (https://github.com/TravelMapping/HighwayData/pull/1214)*, but it's up to Froggie (or us deciding Froggie is inactive) whether it should be pulled or chucked.
*almost entirely cosmetic - the new I-65/I-22 interchange added on both routes, and a shaping point on I-22 between 93 and I-65. I renamed and moved the files, tweaked the .csvs and relabeled (keeping alt label) 'Fut269' as '12' to fit in with the rest of the route better than I-269Fut would.
-
I'll give this a few days for @froggie to weigh in and/or for a consensus to form about how much of this route is ready to be promoted to full usai status in TM.
-
A pair of tweaks to the I-65 route file:
265 => 265A
266 => 265B +266 (265B is the new exit number for US 31, but 266 is a label in use)
These are based on my observations, and rlee's, noted in the previous thread.
-
These are Froggie's states, but his last log-in to these forums were in Feb
Thesis and other busy college classes have a tendency to put a crimp in one's time. I've had to cut back on a few things (this forum being one of them).
FHWA updated their Interstate Route Log in February, and it shows 106 miles of I-22 in Mississippi and 96 miles-and-change in Alabama. So as long as Si's pull request fits with that, let it run.
-
That appears to be exactly what Si's pull request brings in. I'll pull it down and run a site update. A new 2di in today and likely another very soon when the I-14 files are submitted.
-
Check that, I see yakra submitted I-14 last night. So two new 2dis in a single site update.
-
both 2dis in all their glory
(https://s22.postimg.org/dppdut89d/14-22.png)
-
530 > 14
-
Looking at that map, is there really no official I-269 in Tennessee yet? James?
-
Looking at that map, is there really no official I-269 in Tennessee yet? James?
The HB has regular I-269 in TN only from the MS border to the junction with TN385 in Collierville. North of there, the HB has it as just Future I-269/TN 385.
-
Looking at that map, is there really no official I-269 in Tennessee yet? James?
I haven't heard anything about it being posted along TN-385 yet.
-
530 > 14
Huh?
-
That the new I-14 is shorter than a 3di, which isn't even the longest one?
Of course, I-14 might be extended, not sure about the growth prospects of I-530.
-
I-530 has 46.82 mi, whereas I-14 has only 25.46 mi. Heh.