Preliminary notes

• COD-AB topology errors are one of the spatial criteria evaluated described here in the Dashboard and Evaluations for Core CODs tutorial.  Administrative boundary layers can only be assessed as 'fully useful' if all spatial criteria including the topology evaluation are satisfied.  As the set of all administrative boundary layers for a country is given the evaluation of the worst administrative boundary layer (from administrative levels 1 to 4 inclusive), any topology errors will disqualify the 'fully useful' rating for the country.

• COD-ABs should be evaluated for two topological rules:
  • "Must Not Have Gaps"
  • "Must Not Overlap"

Legitimate islands will cause "Must Not Have Gaps" false positives.  If there are many islands they can add time, complexity, and risk of mistakes to the topology fixing process described here Insert link.  These can be avoided by preparing and evaluating a union of the COD-AB and a surrounding 'world' polygon shapefile, which is then removed after any topological errrors are fixed.  This optional process should be done at the beginning of the COD-AB topology evaluation and is described below.

• It is generally only necessary to evaluate the topology of the lowest available administrative boundary level, as higher levels are normally dissolved from lower levels which should contain all higher level attributes, and dissolving does not introduce new topological errors.  However, the evaluation may be made to any level at any time.

Topology evaluation process

This process description uses ArcGIS.  The standard license is sufficient.

Optional 'world polygon' union process

• Use the ArcToolbox > Analysis Tools > Overlay > Union tool to combine the shapefile or feature class with a 'world' polygon.  For the most universal applications a 'world' polygon is a shapefile or feature class with one polygon that extends from 90°N to 90°S and 180°E to 180°W, although any polygon completely surrounding the COD boundary polygons will be sufficient.  A sample 'world' polygon shapefile is available here.  The resulting union will become the 'input shapefile or feature class' described below.

Topology evaluation preparations

• Using ArcCatalog create a new file database by right-clicking in a suitable folder

• Rename the file geodatabase appropriately

• Right-click the new file geodatbase and create a new Feature Dataset

• Right-click the geodatabase and import the administrative boundary shapefile or feature class into a new feature class

• Again-click the new feature class