Introduction 

1. The boundaries of an existing area change, but its name is retained -- Replace the area by declaring a new geo code, and substitute into the "after" vintage.
2. A new area is created, usually in conjunction with the redefinition of an existing area -- Declare a new geo code, and add to the "after" vintage.
3. An existing area is terminated, usually because it has fissioned -- Retire the geo code from the "after" vintage.

Note that a geo code may remain in statistical use even after the area has been terminated as an administrative entity. We do not double-guess our historical sources.

Summary of mutations

Table 1. Counts of areas (not geo codes) at each geo level, and mutations between the vintages.

Specific mutations

Table 2. Regions retired.

Table 3. Regions added.

Table 4. Provinces retired.

Table 5. Provinces added.

Table 6. Communes retired. - None.

Table 7. Communes added. - None. 

Reference files

The reference file is an Excel workbook with a separate worksheet for each geo type, tabulating (as applicable) the area name, type, Data Buffet geo code, and parent geo.

The "after" geo vintage:

• Go to: DataBuffet.com » menu:Tools » Reference Files » Geographies »  Chile - Geographic Lists - 2017
• Direct link: ICHL_GeographyLists_2017.xlsx

The "before" geo vintage:

• Go to: ... » Chile - Geographic Lists - 2007
• Direct link: ICHL_GeographyLists_2007.xlsx

References

• INE: Census
• BCN: Territorial Update Reports
  • Hierarchy
• Chile Political-Administrative Division Update

See also

• Using Data Buffet: Geography changes
• Using Data Buffet: Geo wild cards
• Using Data Buffet: Geo lists
• Using Data Buffet: FIPS codes for geographies
• FAQ: Why doesn't Data Buffet use provider geo codes?