FEWS NET assigns FNIDs to new administrative units in order to have . Having a unique identifier for every administrative unit and to be able to query allows the query of specific administrative units. FEWS NET uses Microsoft Excel to organize the administration units and to create the FNIDs.
...
All polygons are assigned a unique alpha-numeric FNID. The structure of these codes is explained below:
Code Element | Places Needed | Description |
|---|---|---|
ISO_CODE | 2 Digits | Standard ISO 2 digit code |
Version (year) | 4 Digits | The effective year |
Type | 1 Digit (letter) | A=Admin unit, C= Food security classification, L= Livelihood Zone, R= Crop region |
Level/type code | 1 Digit | For Admin units, this is the location in the national admin hierarchy. See notes on the classification and the livelihood shapefiles. |
Level 1 | 2 Digits | |
Level 2 | 2 Digits | |
Level 3 | 2 Digits | |
Level 4 | 2 Digits |
FEWS NET ID Structure:
2-letter country code
Year of the geographic unit set version
Admin level number
For example Admin 1, Admin 2, Admin 3
Admin 1 Level ID in the 00, 01, 02 format
Admin 2 level ID in the 00, 01, 02 format
Each individual Admin unit must have a unique ID at every level
For example, in figure 1 below, Every Admin 1 has its own ID
then every Admin 2 that falls within each admin 1 has a unique ID
Admin 2 ID resets when the Admin 2 falls under a new Admin1
In figure 1, you see the Admin 2 ID go from 06 for West Tigray to 01 for Zone 1 because the Admin 1 unit changed from Tigray to Afar
Concatenate all the values together
This process can be applied to further Admin levels
For example, Admin 3, Admin 4
Keep adding admin ID levels as necessary