Travel Mapping

Highway Data Discussion => Updates to Highway Data => Topic started by: rickmastfan67 on March 05, 2025, 01:26:51 am

Title: VA: I-395/VA-27 mess
Post by: rickmastfan67 on March 05, 2025, 01:26:51 am
We honestly should have a graph connection here between the two routes.  Would recommend using the location that I-395 use for that interchange mess.

Also, the following exit number should be adjusted in both I-395/US-1's files:
10 -> 10A  (It's signed as 10A both ways, NB (https://maps.app.goo.gl/v8Fjsy3Wku9JPqqf7) & SB (https://maps.app.goo.gl/uaMCxMj9zpfufaLfA))

Also would recommend adding a new point to I-395 for the Express interchange @ Eads St, as that's a complete interchange.  Especially since that's the northern end of the 'reversible' system too where it splits into separate lanes for each direction so that it can be open 24/7 into/out of DC.
Title: Re: VA: I-395/VA-27 mess
Post by: froggie on March 07, 2025, 09:08:29 am
^ Minor caveat:  US 1 is not along that stretch of I-395.

That said, I agree that a graph connection should be done.  I'd also make the argument that a point should be added at South Hayes St for the half-interchange that IMO is *NOT* 1PPI with the US 1/VA 110 interchange.
Title: Re: VA: I-395/VA-27 mess
Post by: rickmastfan67 on March 07, 2025, 10:18:19 am
^ Minor caveat:  US 1 is not along that stretch of I-395.

Fixed my post.

That said, I agree that a graph connection should be done.  I'd also make the argument that a point should be added at South Hayes St for the half-interchange that IMO is *NOT* 1PPI with the US 1/VA 110 interchange.

I was thinking about that too, but didn't wanna mention it, as I thought the Eads one would be a higher priority, as you could be forced off onto it depending the time of day.