CT: Waypoint Fixes

[cockroachking]

US6:
CT67_W > CT67_N

US7:
AshFalRd is located one intersection too far south
Route is out of tolerance between CT33_N and CT57/107
SulRd is near the wrong intersection

US202:
Intersection at CT67_E was realigned between 2009-2013 and needs to be recentered

CT2:
Missing graph connection at CT214

CT25:
HomLn is not located at an intersection and needs to be recentered

CT37:
ChiHillRd is not located at an intersection and needs to be recentered

CT45:
CT341_W needs to be centered on the actual intersection

CT67:
Intersection at US202_E was realigned between 2009-2013 and needs to be recentered

CT72:
CanSt is a significant distance east of the actual intersection

CT184:
CT12 > 1

CT188:
CT67_E > CT67_S
CT67_W > CT67_N

CT214:
Missing graph connection at CT2

CT341:
CT45_N needs to be centered on the actual intersection

CT349:
US1 > 3A
I-95 > 3B

[yakra]

US6:
CT67_W > CT67_N

Meh. it's signed as an E-W route overall. I'm just not fussed about changing it.

US7:
AshFalRd is located one intersection too far south

Aah, memories! This looks like a holdover from the early CHM days, c. 2006, when our routes were drafted from Google imagery, which may have been based on old TIGER data, itself quite out of date.
https://historicaerials.com/location/42.043841/-73.325399/1991/18
Moved.

Route is out of tolerance between CT33_N and CT57/107

SeeRd added.
This tells me you're loading route files into wptedit...

SulRd is near the wrong intersection

US202:
Intersection at CT67_E was realigned between 2009-2013 and needs to be recentered

...In which case, be sure to load the latest version from the TravelMapping/master repo.
SulRd was deleted and  the US202_E/CT67_E junction was recentered on Sep 20, 2023.

CT2:
Missing graph connection at CT214

This is intentional.

CT25:
HomLn is not located at an intersection and needs to be recentered

Deleted.

CT37:
ChiHillRd is not located at an intersection and needs to be recentered

Repositioned.

CT45:
CT341_W needs to be centered on the actual intersection

Hm. looks like this may have been 2-way in the distant past. Way before TIGER. Gotta wonder if Google -- and consequently Jason -- thought it was 2-way back in 2009-2010.
Repositioned in both files.

CT72:
CanSt is a significant distance east of the actual intersection

Looks like another case where Google was out-of-date; realigned c. 2007. Repositioned.

CT184:
CT12 > 1

Relabeled.

CT188:
CT67_E > CT67_S
CT67_W > CT67_N

Grumble. Another N-S segment of an otherwise E-W route, signed as such at both ends.
I'll hold off on changes for now, and get some other opinions -- what have people done, or would people do, in similar cases?

CT349:
US1 > 3A
I-95 > 3B

Relabeled Oct 15, 2023.

https://github.com/TravelMapping/HighwayData/pull/7151

[Duke87]

Grumble. Another N-S segment of an otherwise E-W route, signed as such at both ends.
I'll hold off on changes for now, and get some other opinions -- what have people done, or would people do, in similar cases?

I would stick with the overall route direction even if signage in one specific spot defies it. No guarantee local signage will remain as such/isn't in error.