Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on January 22, 2023, 03:58:22 pm

Title: MD: MD Point Concerns from 1/21/2023 Trip
Post by: Markkos1992 on January 22, 2023, 03:58:22 pm
US 40/MD 2:  If MD 2 SB follows St. Paul St, I am not convinced that it should have a graph connection with US 40.

MD 144 (Frederick):  A point should be added at Monocacy Blvd (direct access to I-70/US 40 WB, the previous WB entrance at Exit 56 has been removed).

MD 144 (New Market):  2018 HLR (https://www.roads.maryland.gov/OPPEN/2018%20Frederick_HLR_web.pdf) shows it truncated to the curve at the east New Market town line. 

MD 144 (Cooksville):  Consider adding a point at Marriottsville Rd. (direct access to US 40 and I-70)

MD 147:  This route goes out of tolerance south of Fork Rd.
Title: Re: MD: MD Point Concerns from 1/21/2023 Trip
Post by: cockroachking on January 24, 2023, 06:14:18 pm
Rather than starting a separate thread, I'll add this here:

Requesting a point on MD175 at Reece Road (ReeRd). MD174 begins a little over 1/2 mile up Reece Rd from MD175, so a point here would effectively serve as the "MD174" point on MD175, as if MD174 were to continue all the way there.

(Contextual note: If the point is added, I will be putting it to use, since I would need this point to accurately map my travels from Sunday.)
Title: Re: MD: MD Point Concerns from 1/21/2023 Trip
Post by: Duke87 on January 25, 2023, 07:30:44 pm
US 40/MD 2:  If MD 2 SB follows St. Paul St, I am not convinced that it should have a graph connection with US 40.

Eh, leaving this. The other fork of St. Paul St functions as ramps to US 40.

All others addressed.
Title: Re: MD: MD Point Concerns from 1/21/2023 Trip
Post by: Markkos1992 on January 25, 2023, 07:42:32 pm
One other note:

MD 550:  MD806_N>-MD806