Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: froggie on June 24, 2018, 09:05:39 am
-
Specifically referring to the shaping point east of MA 85: why have a shaping point at a usable intersection? (Cook Ln/Concord Rd) Why not have it as a full point? Unless the guidelines have changed, I recall the waypoint guidelines recommending full waypoints instead of hidden/shaping points if an intersection could be used. (For the time being, and in full disclosure, I could also use this point as I just attended a funeral at the adjacent cemetery this weekend.)
On the same token, the intersection on the east side of downtown Marlborough where US 20 turns (at Lincoln St/Stevens St) should probably have a waypoint...that's a major turn from a traffic standpoint.
-
Specifically referring to the shaping point east of MA 85: why have a shaping point at a usable intersection? (Cook Ln/Concord Rd) Why not have it as a full point? Unless the guidelines have changed, I recall the waypoint guidelines recommending full waypoints instead of hidden/shaping points if an intersection could be used.
Correct. Changed to ConRd, with slightly tweaked coords.
On the same token, the intersection on the east side of downtown Marlborough where US 20 turns (at Lincoln St/Stevens St) should probably have a waypoint...that's a major turn from a traffic standpoint.
Added, although points are getting a bit dense here. I considered deleting the MainSt_MarW & MainSt_MarE points to compensate, but ultimately opted not to.
https://github.com/TravelMapping/HighwayData/pull/2034