Notices by Eldan Goldenberg (eldang@mapstodon.space)

@dymaxion ...which keeps forgetting to clean its glasses?

I have a new favourite geospatial open data bug: US Federal Register 220519-0117 "Change to County-Equivalents in the State of Connecticut".

Sooo... a thing I'm working on for a client is to show various sorts of demographic data at the US Census Tract level, to serve as context layers for the main thing we're building. Most of them come from the 2020 Census, and are straightforward enough to handle: one set of geometries with consistent IDs that all the stats tables can be joined by. (1/?)

There are a couple that are drawn from the American Community Survey, which uses 5-year averages to make up for its comparatively smaller sample size in each year. Since the latest 5-year window started before the 2020 Census, they have to be mapped as 2010 Census Tracts. So far so good.

I noticed that the entire state of Connecticut was missing from one of those layers, so I had to investigate. Sure enough, it's in the data table, so what's going wrong here? (2/?)

I learned that there are two distinct sets of FIPS codes (if you don't know what a FIPS code is, all that matters here is that it should be unique and consistent). One of our data sources was consistent with the Tract geometries, and had Tract names like "Census Tract 1001, Fairfield County, Connecticut". The other had different codes, and names like "Census Tract 1001; Greater Bridgeport Planning Region; Connecticut"

Argh. (3/?)

Once I found that Federal Register announcement I could piece it together. From 1960 until 2022, the US Census Bureau was using outdated labels for subdivisions within Connecticut. Starting in 2022, they now use the up to date planning region names, which have been issued new FIPS codes because they don't have a perfect 1:1 correspondence with the old counties. The problem for me is that while the 2018-2022 ACS 5-year estimates have to use 2010 Tract geometries, they use the 2022 codes. (4/?)

@mastohost @jeremy That's reasonable! You have to keep your own workload manageable. And you're providing a great service here, thank you for it.

@jeremy would you be willing to install this patch? https://queer.party/@maffsie/109367901406518202

This may be partly because I'm used to Mastodon 3.x behaviour as @eldang@weirder.earth, but I keep being frustrated by copying the URL for someone's profile or toots and getting the captive replica of it within mapstodon instead of their actual page.