Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: mapcat on May 31, 2016, 01:01:39 pm
-
MA16's MysValPlwy waypoint should be MysValPkwy.
I'd personally appreciate a waypoint at GorSt for MA3AMan, since I got on after clinching the Lowell Connector which ends a block north of there, but would understand if that seems excessive.
Just curious: what is the rationale for naming MA3AMan after a city in another state, rather than Lowell or any other Massachusetts city it traverses?
-
Just curious: what is the rationale for naming MA3AMan after a city in another state, rather than Lowell or any other Massachusetts city it traverses?
I can't speak for this instance. I don't know if it was Jim's decision or Tim's decision or what. I know that in Maine, US1Byp is named after Portsmouth NH rather than Kittery. I did that on Tim's advice early on. There's also a MO business route with a segment in OK named after the MO city. (Though to be fair, there's nothing much to speak of on the OK side.)
It could be there was an early unofficial practice of having a single City/Abbrev for multi-state child routes, for consistency or something… maybe Jim just followed my precedent of naming the segment after Manchester, with usanh (IIRC) being active earlier. I don't know man I didn't do it.
I will add this thread to my ToDo list shortly.
-
I don't remember, but I'm sure I'd have named it after Lowell or something else in MA if it was left up to me.
-
MA16's MysValPlwy waypoint should be MysValPkwy.
https://github.com/TravelMapping/HighwayData/pull/599
I'd personally appreciate a waypoint at GorSt for MA3AMan, since I got on after clinching the Lowell Connector which ends a block north of there, but would understand if that seems excessive.
I see a partially at-grade trumpet here, and am inclined to just One-Point-Per-Interchange it.
Is the LowConn point OK? (Though when I find these lately, I've been changing them to LowCon, mumble mumble,,,)
-
I'd personally appreciate a waypoint at GorSt for MA3AMan, since I got on after clinching the Lowell Connector which ends a block north of there, but would understand if that seems excessive.
I see a partially at-grade trumpet here, and am inclined to just One-Point-Per-Interchange it.
Is the LowConn point OK? (Though when I find these lately, I've been changing them to LowCon, mumble mumble,,,)
The end seems like it has separate functions to me (exits 5A and 5B to MA3A, and a continuation marked "Exit 5C" that ends at Gorham St), but I admit that the one-point-per-interchange rule hasn't always been clear to me.
-
I admit that the one-point-per-interchange rule hasn't always been clear to me.
I don't think it ever can BE clear. What exactly one interchange or more than one interchange is, is wibbly-wobbly, a judgment call for whoever's looking at the map. There are bound to be differing opinions.
Edit: Oh what the hey. Gorham St leads north to Bridge St and MA38. Why not!
-
Edit: Oh what the hey. Gorham St leads north to Bridge St and MA38. Why not!
Finally added GorSt. It's along for the ride with the US44/NY55 tweak in Poughkeepsie.
https://github.com/TravelMapping/HighwayData/pull/781
-
Cool. Thanks!