Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: theFXexpert on March 02, 2016, 11:20:19 am
-
http://nflroads.com/_layouts/FDOT%20D2%20Northeast%20Florida%20Road%20Construction/ProjectDetails.aspx?pid=60&sid=I-10
The Marietta interchange (Exit 355) is being relocated 0.8 miles west and construction is expected to be completed this Spring.
-
Thanks for the heads up, let me know if you hear when it opens and I'll add it into I-10's file. ;)
-
To note: The exit number will remain at 355 per new signage.
A waypoint for US90 at Devoe St. might be in order upon opening.
-
FDOT says via Twitter that the overpass will open the week of May 30th. Don't know if they mean the exit ramps as well.
https://twitter.com/MyFDOT_NEFL/status/733756359800442880
-
FDOT says via Twitter that the overpass will open the week of May 30th. Don't know if they mean the exit ramps as well.
https://twitter.com/MyFDOT_NEFL/status/733756359800442880
Hear anything new on the exit ramps?
-
FDOT says via Twitter that the overpass will open the week of May 30th. Don't know if they mean the exit ramps as well.
https://twitter.com/MyFDOT_NEFL/status/733756359800442880
Hear anything new on the exit ramps?
The Times-Union reported (http://jacksonville.com/news/metro/2016-06-08/story/new-i-10-marietta-overpass-and-interchange-scheduled-open-wednesday) that it was scheduled to open Wednesday. I planned on checking it out tonight.
-
Yep. Opening is confirmed.
-
I'm probably going to name the new interchange as '355A' as the current '355' point is in use and mark it as closed (it did close when the new ramps opened, right?). Just wish somebody didn't have it in their list file, otherwise, I would have done the reverse and given the new interchange the 355 point and mark the old one as *355A. Oh well, can't win them all.
-
I'm probably going to name the new interchange as '355A' as the current '355' point is in use and mark it as closed (it did close when the new ramps opened, right?). Just wish somebody didn't have it in their list file, otherwise, I would have done the reverse and given the new interchange the 355 point and mark the old one as *355A. Oh well, can't win them all.
It's just one TM user with the point in use and I don't think that person every actually sent in a .list. I think the file is one of the handful I grabbed from CHM for early testing and it just stayed. At least I can find no record of that file ever being emailed to me for TM. So go ahead and call the new one 355 and put in an updates entry in case that user or another CHM user who might have it ever joins us and cares to be that precise.
-
I'm probably going to name the new interchange as '355A' as the current '355' point is in use and mark it as closed (it did close when the new ramps opened, right?). Just wish somebody didn't have it in their list file, otherwise, I would have done the reverse and given the new interchange the 355 point and mark the old one as *355A. Oh well, can't win them all.
It's just one TM user with the point in use and I don't think that person every actually sent in a .list. I think the file is one of the handful I grabbed from CHM for early testing and it just stayed. At least I can find no record of that file ever being emailed to me for TM. So go ahead and call the new one 355 and put in an updates entry in case that user or another CHM user who might have it ever joins us and cares to be that precise.
Alright. I'll whip up an update later once I know for sure (via theFXexpert) that the old interchange has closed so I don't have to do a second edit to the file just to mark it as such. I like saving time. lol.
-
The ramps for the old interchange were blocked with barrels when I went by. The Right lane of I-10 was closed too. If I remember correctly, the closing of the old interchange was supposed to occur simultaneously. I can check again if needed.
-
If you saw barrels blocking off the old interchange, that's good enough for me.
I'll work up an update for this and 9B within the next 24h.
-
Exit 355 has now been relocated, and the old one marked at *355A.
https://github.com/TravelMapping/HighwayData/pull/618
Update entry has been also been added to that pull request since 355 had been in use.