Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on April 10, 2022, 10:02:20 pm

Title: MD: Easton and MD 213 Corridor Point Concerns
Post by: Markkos1992 on April 10, 2022, 10:02:20 pm
MD 33: Consider replacing the shaping points west of CalRd and east of MD 579 with visible points.

MD 288:  This route should be flipped. (https://www.google.com/maps/@39.1405672,-76.2237688,3a,75y,76.28h,93.08t/data=!3m6!1e1!3m4!1sKc4P41pD4v6nroqKUZGz9Q!2e0!7i13312!8i6656)

MD 292: 
1.  StiPondRd should be BesCorRd (Bessicks Corner Rd) (https://www.roads.maryland.gov/OPPEN/2020%20Kent.pdf) according to the latest HLR.
2.  End should be moved south to the Ericsson Ave (EriAve) intersection (based on HLR and 2008 GSV).

MD 298:  StJamNRd needs to be shortened.

MD 328/MD 331:  The BlaDogAly labels should match.

MD 333: 
1.  TredAvonAve should maybe be MorSt_S.  (based on HLR (https://www.roads.maryland.gov/OPPEN/2020%20Talbot.pdf))
2.  Is there a better point than CatPoiRd in the area?
3.  WasAve should be WasSt.

MD 579:  Consider making the shaping point south of MD 33 a visible point.

MD 662:  Should 3BriBraRd be shortened?