Add new US counties in CT, AK, and VA and rework related CT localadmin

[nvkelso]

Fixes whosonfirst-data/whosonfirst-data#2197 (CT) and whosonfirst-data/whosonfirst-data#2136 (AK and VA).

• 9 new CT counties don't cleanly map to 8 old CT counties (end them, no superseding), with populations
• 169 existing CT localadmin need updated geoid concordances (because their parent chanaged), with pops
• 2 new AK counties do cleanly map to 1 old AK county (supersede them), with pops
• 1 revised VA county does cleanly map to 2 old VA county (supersede just the one, mod the remaining, alt geom it, too), with pops

Needs full PIP

[nvkelso]

@stepps00 The commits in this PR should be fairly atomic and reviewable in sequence and in total.

For the counties I manually set the wof:hierarchy & etc, but really it needs a fuller PIP to account for all the child places in these counties (not just localadmin but also locality and neighbourhoods, etc).

[nvkelso]

I'll followup with a separate PR for the localadmin work outside of Connecticut as that affects many thousand places, but doesn't require PIP.

[nvkelso]

Connecticut

Old county records in black outlines (missing populations because expired geoid concordances), new counties in red with red text labels (with updated geoid concordances):

Existing localadmin get new geoid concordances and parent county_id hierarchies:

Alaska

New county records:

Virginia

Modified and retired county records for Bedford Co and Bedford City:

[nvkelso]

Followup outside of these new features in CT and AK for statistical gores is in #208.

[stepps00]

This and a few others should get an update to the wof:lastmodified date field.

[nvkelso]

Fixed by re-exportifying everything!

[stepps00]

Looks good - a few comments, mostly around missing or unexpected properties. Once these features get Exportified and PIPd, I can take a second look before merge.

[nvkelso]

@stepps00 I've addressed your PR review comments and re-exportified everything. One more 👀 ?

Then I'll pick this up later for final PIP round.

[stepps00]

Hmm.. looks like this feature hasn't been updated, aside from this property?

[stepps00]

Same issue, this feature only has the lastmodified date edited.

[stepps00]

A few records only have lastmodified date updates.. aside from that, LGTM. I can take another look once the PIP work is added.

[ashah-lightbox]

@stepps00 Any updates?

[nvkelso]

The next step here is to PIP update the hierarchy and parent attributes. I haven't had time to do that yet...

[ashah-lightbox]

@nvkelso just curious what do you mean by PIP update?

[tfeathers]

@nvkelso @stepps00

Is there an established process to do the PIP work? Is there anything we can do to help complete the hierarchies and get this PR over the finish line?

[nvkelso]

PIP means "point in polygon" and is PIPing is the process of taking the revgeo centroid, or the label centroid, or the math centroid and doing a spatial join with all the possible parent polygons to then update the wof:hierarchy properties.

We used to have a semi-automated workflow for PIPing, but we're more low fi now.

@thisisaaronland described how this can be accomplished using modern workflow in blog post, but I haven't found time to get that up and running on my new dev machine.

There's some WOF specific business logic for the hierarchy calculations... else you could manually run the PIP in QGIS with a and with a little bit of scripting construct the new message and update each record.