Author Topic: MD: I-695 issues  (Read 2351 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1841
  • Gender: Male
  • Last Login:Today at 04:13:11 am
MD: I-695 issues
« on: November 21, 2019, 04:21:42 am »
Just happened to notice we have some issues along I-695.  Will go in the order of the exit numbers.

=====
BroHwy
(maybe a shaping point here would be warranted between these two exits?)
1
.....
12A -> needs a recenter to have a graph connection to US-1.  Also see [1] below.
12 -> 12B (StreetView ('Inner') as it's posted as 12B/C there. (Note: not in use, so no issue in renaming it)
.....
21 -> Split into two separate interchanges as missing graph connection to MD-129?  Also 0.51 miles between each set of split ramps.
.....
29 -> Missing graph connection with MD-542?
.....
41
(Need a shaping point here between 41 & 42, as the line is almost on top of MD-151 here, and could use a little bit of separation.)
42
43 -> Maybe somehow a graph connection with MD-157 here?

=====

[1] - US-1 issue: I-695(10) -> I-695(12A)  (Note: current incorrect label is in-use and needs to be hidden, & recentered to match fixed 12A point in I-695's file.)

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 957
  • Last Login:Yesterday at 10:34:40 pm
Re: MD: I-695 issues
« Reply #1 on: November 21, 2019, 07:18:53 pm »
BroHwy
(maybe a shaping point here would be warranted between these two exits?)
1

Sure, why not. I like shaping points.

Quote
12A -> needs a recenter to have a graph connection to US-1.  Also see [1] below.

Fixed

Quote
12 -> 12B (StreetView ('Inner') as it's posted as 12B/C there. (Note: not in use, so no issue in renaming it)

Fixed

Quote
21 -> Split into two separate interchanges as missing graph connection to MD-129?  Also 0.51 miles between each set of split ramps.

Agreed, and implemented.

Quote
29 -> Missing graph connection with MD-542?

Annoying geometry, but Imma go ahead and make a graph connection here by making separate points for 29A and 29B. I'd say this should be 1PPI otherwise, but there's no unstupid way to have both that and a graph connection so...

Quote
(Need a shaping point here between 41 & 42, as the line is almost on top of MD-151 here, and could use a little bit of separation.)

Agreed, and implemented.

Quote
43 -> Maybe somehow a graph connection with MD-157 here?

Hmmm. More annoying geometry.

So... the point on I-695 is exactly where it should be. And putting MD 157's point there would have it be fairly far from where the inner loop ramps actually meet it.

I'm going to just leave this and accept it as a case where it's not possible to make a graph connection without putting a point in a weird place.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1841
  • Gender: Male
  • Last Login:Today at 04:13:11 am
Re: MD: I-695 issues
« Reply #2 on: November 22, 2019, 06:19:16 am »
12 -> 12B (StreetView ('Inner') as it's posted as 12B/C there. (Note: not in use, so no issue in renaming it)

Fixed

This one didn't make it in.

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 957
  • Last Login:Yesterday at 10:34:40 pm
Re: MD: I-695 issues
« Reply #3 on: November 24, 2019, 02:18:28 pm »
Should be good now.