Hello, I noticed that MIGRATE1 is currently not available for years 2022 and 2023. However, MIGRATE1 was previously available for 2022, and I believe it should still be possible to construct this for 2023. Is there a reason for this, or will it become available at some point? Thank you.
We temporarily removed MIGRATE1 from the 2022 ACS/PRCS due to inaccuracies (see our revision history entry for November 20, 2024). We are implementing a correction and will re-release MIGRATE1 for the 2022 data and add it to 2023 as soon as it is ready. We will email affected users once the updated variable is available; in the interim users should refrain from using MIGRATE1 in 2022 ACS/PRCS for any previously created customized datasets.
Ok, thank you very much for your reply.
1 Like
Hi @KariWilliams
Do you have a predicted date for the re-release of MIGRATE1 for 2022 and 2023?
Also: was the 2022 data inaccurate back in January 2024 - that is, for data downloaded from iPUMS back then? Thanks.
We are working on a fix to the bug now and are hopeful that we can release the updated version before the 5-year ACS/PRCS PUMS data are released by Census Bureau in late-January (though we may need to release the fix along with the IPUMS release of the 5-year PUMS).
The error with MIGRATE1 affected the detailed codes for persons who moved within state only. Codes 23 and 24, which report moving within migration or between migration PUMAs, were not correctly assigned. However, any previously downloaded extracts can be used for general codes as well as detailed codes for moving between contiguous and non-contiguous states.
Are you still working on the fix for this? It looks like the data is not available.
On January 31, 2025 we re-released MIGRATE1 for the 2006-2022 data to address this error and extended the variable to include the 2023 1-year data. Details about the changes are described in the revision history. The most substantial changes were in the 2022 sample. For a breakdown of how many records (and their associated population estimates) were affected, by sample, please refer to the Revisions to MIGRATE1 (by SAMPLE) note. A list of all PUMA-MIGPUMA pairs that were miscoded is available on the Revisions to MIGRATE1 MISCODINGS note.