Hello,I was looking to use MIGPUMA with PUMA and realized the geographies are different. Additionally, I wanted to incorporate county data and realized it doesn't share borders with PUMA. Yet, MIGPUMA/POWPUMA fully enclose one or more PUMAs. They also fully enclose one or more counties. So, County and PUMA-level data can be aggregated to share the MIGPUMA/POWPUMA level. This also allows place of living to be utilized with MIGPUMA or differentiated from POWPUMA. So, I created crosswalks that can be used to determine which MIGPUMA/POWPUMA a PUMA falls into and also what MIGPUMA/POWPUMA a county falls into. Most of these already exist here: https://usa.ipums.org/usa/volii/20migpuma.shtml https://usa.ipums.org/usa/volii/10migpuma.shtml Yet, that was missing 2010 County to MIGPUMA/POWPUMA. So that's really all I've added. I also simplified variable names to essentially create GEOID. I also left out Puerto Rico. I could make versions that include it if that's demanded. Ideally, ACS data could play nicely with CPS data, but the change in Connecticut's census equivalent regions occurred in ACS in 2022 and only in 2024 for CPS. So, that will likely cause issues that could only be remedied by something like Geocorr. These files can also help you create your own type of Geocorr calculation, but with these MIGPUMA/POWPUMA regions, which I believe Geocorr lacks. You would need shapefiles to calculate area (or some other sources), but these would then help relate variables. I assume population can just be done by summing 'PWGTP' by whatever region is your interest. Here's the link: https://github.com/rfeir/ACS-Crosswalks/tree/main