Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on November 01, 2019, 08:34:14 pm
-
I would like for a point to be added at State St (StaSt) (https://www.google.com/maps/@42.8072163,-70.8717614,3a,75y,331.78h,69.62t/data=!3m6!1e1!3m4!1s1i3JhJGvvbEshtlS8oNtEg!2e0!7i13312!8i6656) in Newburyport. It connects to the US 1 rotary and the meet itinerary for the Newburyport meet had us turn from State St here onto MA 1A NB.
EDIT: I also think the US 1 points should be edited to better reflect the signed concurrency between Newburyport and Salisbury. Using just the town names IMO does not show a concurrency here. The requirement of using US1_S at the southern end does not help either.
EDIT 2: Nearby CaryAve on US 1 should be for CarAve (Carey Ave (https://www.google.com/maps/@42.8099673,-70.8775838,3a,75y,219.79h,95.94t/data=!3m7!1e1!3m5!1sMgffuMqJS99DW3i3E5AFhQ!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DMgffuMqJS99DW3i3E5AFhQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D359.94208%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656)).
-
Guess I should have gone ahead and clinched the section of MA 1A between MA 113 and the start of the overlap with US 1 rather than relying on the lack of point on State Street making that part of the tour not result in anything clinched for Travel Mapping!
-
I would like for a point to be added at State St (StaSt) (https://www.google.com/maps/@42.8072163,-70.8717614,3a,75y,331.78h,69.62t/data=!3m6!1e1!3m4!1s1i3JhJGvvbEshtlS8oNtEg!2e0!7i13312!8i6656) in Newburyport. It connects to the US 1 rotary and the meet itinerary for the Newburyport meet had us turn from State St here onto MA 1A NB.
Added.
EDIT: I also think the US 1 points should be edited to better reflect the signed concurrency between Newburyport and Salisbury. Using just the town names IMO does not show a concurrency here. The requirement of using US1_S at the southern end does not help either.
If we were starting usama fresh, US1, US1_S, and US1_N would be a possibility. But US1_S is in use, so this is not the case. Having three US1 intersections, our 2 options are:
1. Use alphabetical suffixes _A, _B, _C, etc.
2. Choose 3-letter suffixes for a nearby towns if they are fairly close. The 3-letter suffix should be the first 3 letters of the town name. Add a suffix with an underscore and those 3 letters.
The alphabetical suffixes aren't any more clear (town suffixes not "confusing") IMO; the town suffixes are sufficient. Leaving as-is.
EDIT 2: Nearby CaryAve on US 1 should be for CarAve (Carey Ave (https://www.google.com/maps/@42.8099673,-70.8775838,3a,75y,219.79h,95.94t/data=!3m7!1e1!3m5!1sMgffuMqJS99DW3i3E5AFhQ!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DMgffuMqJS99DW3i3E5AFhQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D359.94208%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656)).
Changed to RaiSt, as at least that's a RIRO as opposed to a RI-only.
Edit: https://github.com/TravelMapping/HighwayData/pull/3283