Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Jim on February 12, 2016, 07:52:27 am
-
Thoughts on adding Milford Parkway in CT to usasf? I think it's a useful to include as a freeway connection between CT 15 and I-95, with a short extension (that I assume we'd include) connecting up to US 1.
-
Does anyone recall why it wasn't included before?
-
Because it's really short?
http://clinched.s2.bizhat.com/viewtopic.php?t=1422&highlight=milford&mforum=clinched
-
I see no problem in adding it.
The north end is a bit wibbly-wobbly; I'd probably invoke "one point per interchange" and have a single point at CT CT15 54.
-
Because it's really short?
http://clinched.s2.bizhat.com/viewtopic.php?t=1422&highlight=milford&mforum=clinched
I'm sure that's why CHM never had it. I (and I think most of the rest of the TM crowd) don't see that as a problem.
-
I see no problem in adding it.
The north end is a bit wibbly-wobbly; I'd probably invoke "one point per interchange" and have a single point at CT CT15 54.
I'd definitely be in favor of a single point there, lining up with CT 15's point.
-
Pull request submitted. (https://github.com/TravelMapping/HighwayData/pull/417)
-
Pull request submitted. (https://github.com/TravelMapping/HighwayData/pull/417)
You're quick, thanks.
-
The Milford Parkway has an Exit 4 at Wellington Rd (after 3A to northbound CT 15, but "before" 3B to southbound CT 15). This makes the one-point-per-interchange kind of screwy. It's definitely an oddball.
-
Topics merged.
3A & 3B & 4 were all given a single point, as noted upthread.
-
The one thread I fail to search for history...