Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on April 03, 2022, 08:23:22 pm
-
Myself (and probably a few others) would like to have a point at Aurora St (just north of CT 8 ) as we turned here as part of touring the I-84/CT 8 Construction during the Waterbury/Meriden, CT, Meet yesterday. A point on US 5 at Britannia St would be useful as well.
I could also personally use a point on CT 157 at Jackson Hill Rd (north of CT 147). (This was due to me following CT 157 NB north of CT 147 by accident.)
-
I was wondering whether you were going to request that point on CT 73. I've been learning not to assume that I can plan travels to smooth out the map based on whether a meet tour doesn't go on a complete segment of a route (which would therefore make it a non-factor for TM purposes).
Similarly, CT 68 could use a point where the access for CT 8 is. It didn't end up as one that would have been used by meet attendees, but it was supposed to be - it just so happens that the signs for CT 69 from CT 42 are gone, so we missed the turn and ended up using CT 63 instead. It's just as well; my map looks nicer with the graph connection.
-
I was wondering whether you were going to request that point on CT 73. I've been learning not to assume that I can plan travels to smooth out the map based on whether a meet tour doesn't go on a complete segment of a route (which would therefore make it a non-factor for TM purposes).
I even told Duke87 that I wondered whether I would be the first to do that one.
I was wondering whether you were going to request that point on CT 73. I've been learning not to assume that I can plan travels to smooth out the map based on whether a meet tour doesn't go on a complete segment of a route (which would therefore make it a non-factor for TM purposes).
Similarly, CT 68 could use a point where the access for CT 8 is. It didn't end up as one that would have been used by meet attendees, but it was supposed to be - it just so happens that the signs for CT 69 from CT 42 are gone, so we missed the turn and ended up using CT 63 instead. It's just as well; my map looks nicer with the graph connection.
I did not realize that pretty much everyone missed that turn. Duke87 and I ended up with a clinch (or in Duke87's case a reclinch) of CT 42. (giving me 5 truly clinched 42s (DE, MD, PA, NJ, CT) and the middle section of VA 42) (I also clinched the southern section of NY 42 on the trip home.)
-
a point at Aurora St (just north of CT 8 )
Looks reasonable. Added.
A point on US 5 at Britannia St would be useful as well.
I'm more Meh about this one. Was it also used by a number of people at the meet?
I could also personally use a point on CT 157 at Jackson Hill Rd (north of CT 147). (This was due to me following CT 157 NB north of CT 147 by accident.)
A little meh, but I'll add it under the CHM "collaborator perks" doctrine. What the hey, it's a major enough road for CT157 to have a stop sign.
Oh bother. That brings it out of tolerance here (http://www.openstreetmap.org/?lat=41.531045&lon=-72.688567&zoom=19). WadSt (http://www.openstreetmap.org/?lat=41.537848&lon=-72.683862) added.
CT 68 could use a point where the access for CT 8 is.
Added.
-
A point on US 5 at Britannia St would be useful as well.
It was a turn on the early part of the meet after visiting the Meriden Traffic Control Tower.
-
Fair enough; added for the sake of the meet attendees.
Added to https://github.com/TravelMapping/HighwayData/pull/5698