Codes and Frequencies
Can't find the category you are looking for? Try the Detailed codes
Explore how IPUMS created this variable
Most IPUMS data transformations are performed using variable harmonization tables that specify how each value in the source data is recoded. Some variables also require programming logic in addition to the harmonization table. The harmonization documents for this variable are:
- Harmonization table
- Supplemental programming
- Instructions for interpreting harmonization documents
class Mig2_p_cu : public Editor {
public:
Mig2_p_cu(VarPointer varInfo) : Editor(varInfo) {}
void edit() {
long a = getRecoded();
switch (dataSet) {
case dataset_id::cu2002a: {
if (CU2002A_0414() == 9999 && CU2002A_0412() <= 998)
a = 192997997;
if (CU2002A_0414() == 9999 && CU2002A_0412() == 999)
a = GEO2_CU(0);
} break;
case dataset_id::cu2012a: {
if (CU2012A_0416() == 9999)
a = GEO2_CU(0);
} break;
}
setData(a);
}
};
Description
MIG2_P_CU indicates the person's municipality of previous residence within Cuba. Migration municipality codes from MIG2_P_CU are compatible with codes from GEO2_CU.
Click on the Source Variables tab for information on place of residence for each sample year. Source variables may contain more geographic unit detail but are not suitable for cross-temporal comparison.
Comparability — General
Where boundaries changed over time, units were harmonized to create units with boundaries that remain stable over time. Boundary changes for MIG2_P_CU are too numerous to list here, but users should be aware that there were changes over time.
Universe
- Cuba 2002: All persons
- Cuba 2012: All persons
Availability
- Cuba: 2002, 2012
Loading...