# Appendix 4: Case Study - Global Polio Administrative Boundaries Goal: Responds to the need for consistent and complete global layers of administrative units which satisfy the mapping needs of the Global Polio Eradication Initiative (GPEI). Method: The project amasses available administrative units which connects best with GPEI data. Data composition: * Unique identifiers: all administrative units are given unique identifiers based on alpha numeric codes, which are dependent on codes of the higher levels. A code once used is never reused within the geodatabase. * Attribute table: the administrative codes (e.g ADM0\_CODE, ADM1\_CODE) are used to join the administrative units with non-spatial data. * Global ADM0 (Level 0): International country boundaries as approved by the WHO headquarters. This is the highest level of administrative unit. * Global ADM1 (Level 1): First level administrative boundaries (contained within level 0). These could represent a state, province or prefecture depending on each country). Irrespective of the name at country level, there are referred to as Admin 1 in the database. * Global ADM2 (Level 2): Second administrative boundaries (contained within level 1). This is the lowest level currently considered. Data sources: WHO Regions and country offices. Data Validation: Once administrative units from WHO Regions are shared with headquarters, the .shp files are checked for errors. The repair geometry tool checks the list for errors, fixes them, and then loads the data into a temporary database with a set of minimum required fields (ISO code and administrative unit name). The outer boundaries of administrative units need to be aligned to WHO legally approved country boundaries. Steps: * Sharing: Sharing of administrative unit shape files from WHO regions or country offices to headquarters * Validation: Establish validation periods for these geographic features (when possible) * Harmonization: Harmonizing and merging data to the global layer based on the international boundaries as stipulated by WHO headquarters legal unit * Code Generation: Generate unique codes in headquarters for each geographic unit. * Dissemination: Disseminate harmonized administrative units to regional/country offices and collaborating partners through geo-server or as geodatabases/shape files. Partnerships: ESRI, Centre for Disease Control (CDC)Data sharing: This database is used within the WHO for various purposes. Usage of these boundaries for publication and presentations needs clearance from the WHO legal team or from relevant ministries of partner countries. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://health-catchment-areas-working-g.gitbook.io/health-catchment-areas/appendix/appendix-4-case-study-global-polio-administrative-boundaries.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.