Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Bickendan on February 23, 2022, 10:33:59 pm
-
The DC segment of I-95 and 495 might need to be recentered, and their corresponding points in Virginia and Maryland to match.
https://travelmapping.net/hb/showroute.php?u=null&r=dc.i095
-
Yeah and the point with I-295 is kinda off too. Looks like a map drift issue. Fixing...
This will also affect mapmikey since I moved the VA points to match the DC ones.
-
Yeah and the point with I-295 is kinda off too. Looks like a map drift issue. Fixing...
I think it was still aligned with the 'original' bridge before they replaced it. That was our issue here.
-
I think it was still aligned with the 'original' bridge before they replaced it. That was our issue here.
Was that part of the Springfield Interchange project, which received so many posts on MTR all those years ago?
-
I think it was still aligned with the 'original' bridge before they replaced it. That was our issue here.
Was that part of the Springfield Interchange project, which received so many posts on MTR all those years ago?
No, that was a separate project. However, the height of both were going on at the same time (2000-2007).
-
Yeah and the point with I-295 is kinda off too. Looks like a map drift issue. Fixing...
I think it was still aligned with the 'original' bridge before they replaced it. That was our issue here.
I don't think that was the case. First off, the original bridge was north of the centerline on the new bridge. And IIRC, CHM began in late 2006. By that time, both directions of the Beltway were routed onto what is now the Outer Loop (i.e. "eastbound"). When Tim created the Maryland Interstate lists, he probably went by what traffic was using at the time.