Administrative Boundaries Shapefiles
This page describes the steps FEWS NET uses to create, update, and published standardized subnational administrative boundaries shapefiles.
FEWS NET uses standard subnational administrative boundary shapefiles as the foundational unit of analysis and for mapping products across FEWS NET mechanisms.
Administrative boundaries should be reviewed and updated before any FEWS NET work begins in a country of interest or when FEWS NET staff are alerted to boundary changes or new boundary data.
In general, responsibilities by team are as follows:
Knowledge Base staff will complete this process for countries as new livelihoods or market fundamentals projects begin.
Decision Support staff will complete the process for countries that are onboarded as food security monitored countries or for ad-hoc requests.
Hub staff will complete the process for other countries requested by the client for ad-hoc projects.
Process overview
The standardization process aims to deliver shapefiles that meet the following standards:
Administrative units have standard attributes and metadata.
Administrative units are edge-matched to FEWS NET’s world shapefile.
Where applicable, administrative unit names are approved by FEWS NET’s local staff in the country of interest.
The standardized data are published and stored in the FEWS NET Data Warehouse (FDW).
The process involves four sequential sub-processes, outlined below and in the supporting documentation.
Perform desk research on possible new boundary data or boundary updates.
Document potential changes in boundaries and administrative unit names.
Make updates to the shapefile:
Edge-match geometries.
Create new unique FEWS NET IDs (FNIDs).
Standardize the attributes.
Produce a readme with sourcing information.
Upload the standardized shapefile to the FEWS NET Data Warehouse (FDW) and inform key stakeholders that the file has been updated.
Perform administrative boundary source review for country of interest
The administrative boundary source review verifies that we are using the best available administrative boundary shapefiles for the country. Use the following steps to perform your review:
Research possible sources for administrative boundary data in that country. For example:
Government websites (local census, statistics ministry)
HDX search for “___Country___ - Subnational Administrative Boundaries”
Wikipedia often has a good first look at the types of administrative boundaries and their history. Search “Administrative divisions of ___country__”
Review how any of those boundary datasets differ from FEWS NET’s existing boundaries (if applicable) or from each other.
Check the number of units, level of units, authority of source, and how recently produced. Check if reported changes are incorporated into the dataset.
Come to a consensus with any relevant stakeholders on the preferred source of new boundaries based on precision, high-quality sourcing, and recency.
Create boundary and name change review document
The boundary and name change document captures the changes made between FEWS NET’s existing administrative boundary file and the new boundary file in a single location. Use the following steps to document the changes:
Compare the FEWS NET shapefile with the shapefile from the external source, especially on the following aspects:
Admin levels, e.g., if the country has created a new level of admin boundaries or a lower level is now available.
Admin names, e.g., spellings, aliases, names in their original language, and English names.
Admin boundaries, e.g., boundary shapes and name updates.
Consolidate findings in a Google Doc to document changes over time, and if applicable, share them with the Decision Support field team to confirm any major changes.
Update and validate country shapefiles and readme text file
Use the guidance below to clean, document, and zip the shapefiles to standardize the source data to align with FEWS NET standards.
The steps for cleaning the boundaries are generally explained below. This companion document provides step by step instructions using two possible methods - one manual and one using an ArcGIS model tool to edge match boundaries using step by step instructions.
Before you begin, confirm that you have the latest version of the world shapefile by accessing the FDE Spatial topic page and searching ‘world.’ Ensure you have downloaded the latest version of the “GAUL Global Admin0 boundaries.”
Edge-match boundaries to the world shapefile:
Start by editing/geoprocessing the lowest level of administrative boundary in the new dataset.
Make sure the projection is WGS 1984.
Note any unique IDs (i.e., objectid or PCODEs if from a UN-derived source for each level of admin), make sure to maintain those throughout editing and geoprocessing.
Identify any places where the new subnational boundary falls outside of the FEWS NET country boundary, and remove those areas.
Identify any gaps where the subnational boundary does not extend to the FEWS NET country boundary. Extend those areas to match the FEWS NET country boundary.
Use the Dissolve tool to aggregate up to Admin 1 level, preserving relevant attributes and unique IDs.
The file naming convention for the output files (and associated files) should be <two-letter country code>_Admin<level>_<YYYY>. For example MZ_Admin1_2021.shp and MZ_Admin2_2021.shp.
Create the following standard attribute fields in the cleaned file(s):
FNID: 18 character text
EFF_YEAR: Short integer
COUNTRY: 2 character text
ADMIN0: 50 character text
ADMIN1: 50 character text
ADMIN2: 50 character text
ADMIN3: 50 character text (if applicable)
ADMIN4: 50 character text (if applicable)
ALIASES: 250 character text
ADMIN#XX: 50 character text (use for the local language if applicable)
If including the local language, add a field for each admin level to include the name in the local language. For example, in a country with 3 admin levels that speaks French, add ADMIN0FR, ADMIN1FR, ADMIN2FR, ADMIN3FR. The number represents the admin level, and the last two characters are the 2-digit ISO code for the language.
Populate the standard attribute fields as follows:
FNID: See FEWS NET IDs for details on structuring FNIDs.
EFF_YEAR: The year the source organization last updated the shapefiles.
COUNTRY: ISO 2 Character Country Code
ADMIN0: English name of the country
ADMIN1: English Admin 1 name of the unit
ADMIN2: English Admin 2 name of the unit
ADMIN3: English Admin 3 name of the unit (If applicable)
ADMIN4: English Admin 4 name of the unit (If applicable)
ALIASES: List of alternate spellings of the English name of the unit, separated by tildes. For example ~Mane~Mayne~Main~West New Brunswick~. This list should come from the previous shapefile, any alternate spellings identified in the shapefile review, and a quick review of the GNS.
ADMIN#XX: If a country has French, Spanish, Portuguese, or Arabic as a national language, include names of subnational units in those languages in their respective fields. The data should be in previous versions of the shapefiles or in the source shapefiles. Work to find sources as needed. If other local languages are present in the source data, it is best practice to maintain those spellings.
Create a readme.txt file with the source and FEWS Net documentation:
In the folder, right click → New → Text Document.
Add the text from this template cc_admin_yyyy_readme (Admin Shapefile Documentation Readme) - Google Docs. Update all items in bold brackets and delete sections that are not relevant.
Review the geometries
Use the following steps to review the outputs:
Use the Union tool to combine the output subnational boundaries with the country boundary from FEWS NET’s modified GUAL global boundaries.
Review the attribute table to find any instances where the output boundaries did not union with the GAUL boundary. These areas need to be removed as they fall outside the GAUL boundary.
Next, find any areas where the GAUL boundary did not intersect the subnational boundaries. This may only be one feature. For a multipart feature, use the ‘Explode’ tool on the editor toolbar to split the feature into different features. These areas all need to be added to the subnational boundary to match the GAUL boundary.
Review the tables
The GIS or Data Specialist’s leadership should review the tables as follows:
Copy tables to a Google Sheet.
Ensure no repeated FNIDs:
Format -> Conditional formatting, selecting "Custom formula is," and entering =COUNTIF(A:A, A1)>1 (update the column reference).
Review the attribute field names.
Ensure no extra attributes are maintained.
Review the attributes for any obvious errors (missing data, misspellings).
Review the readme
The GIS or Data Specialist’s leadership should copyedit the readme.
Create a ZIP file
Zip all shapefiles and the readme in a file named CountryCode_Admin_EFF_YEAR.zip (for example, MZ_Admin_2021.zip).
Upload new shapefiles to the FEWS NET Data Warehouse
Following the review process, the new administrative boundary data should be uploaded to the FEWS NET Data Warehouse.
Pre-upload steps
The pre-upload steps depend on whether you are updating an existing Geographic Unit Set. Follow the guidance for the scenario that applies to your upload:
Add a new Geographic Unit Set Version
The pre-upload steps described above must be completed before adding a Geographic Unit Set Version to avoid upload errors.
From the main FDW toolbar, go to Metadata Management > Spatial > Geographic Unit Set Versions.
Click Add Geographic Unit Set Version and complete the following fields:
Geographic Unit Set: Search for the Geographic Unit Set in the dropdown.
Start: Set the Start as Jan 1 of the effective year of the shapefile.
Description: Populate with the country-specific content added to the readme .txt that was produced for this set of shapefiles.
File: Use Choose File to browse to the zip file with the new boundaries.
Metadata: Enter ISO 19139 Geographic Information Metadata XML (optional).
Click Save and continue editing. The backend will run the checks that are described below in the FDW troubleshooting section.
If it runs successfully, click Save.
Troubleshoot administrative boundaries uploads
Use the following information to troubleshoot administrative boundaries uploads in FDW:
If the same FNID and full_name are in different rows, this will not cause an error. The row will match the existing unit by code and update it. Repeated rows with the same FNID will overwrite the same record.
If an FNID is paired with a different full_name, this will not cause an error unless
full_nameis duplicated. The importer will match to the unit using the FNID and update thefull_name,name,aliases, attributes, geometry, etc. The last row takes precedence.If a new
full_namecollides with another unit’s full_name in the same layer, an error will be raised.
If a
full_nameis paired with a different FNID, an error will be raised.
Review the uploaded boundaries
You can review the uploaded boundaries using the FEWS NET Data Explorer (FDE).
Go to the Spatial topic page in FDE.
Filter by the country and the admin unit type. Look for a new row with the correct Start date.
Select the row and scroll down.
Review the Table and Map tabs to ensure the data is correct.
You can adjust the positioning of a Geographic Unit’s label or icon on maps by manually setting the point location. To set a different display location from the centroid:
Go Spatial > Geographic Units in the FDW.
Select the Geographic Unit from the table.
From the change screen, select the Allow Override Display Location option.
Edit the Display Longitude and Display Latitude.
Select Save.
Once you have confirmed the boundaries are uploaded as expected, inform any stakeholders via email.
See also
Geographic Unit Boundaries and Definitions
Geographic Unit Set Versions: Administrative and Crop Production