...
Code Element | Places Needed | Description | |||||
|---|---|---|---|---|---|---|---|
ISO_CODE | 2 Digits | Standard ISO 2-digit country code | |||||
Version (year) | 4 Digits | The effective year year of the geographic unit set version | |||||
Type | 1 Digit (letter) | A=Admin unit, C= Food security classification, L= Livelihood Zone, R= Crop region | |||||
Level/type codeUnit level | 1 Digit | For Admin units, this This is the location in the national admin geographic unit hierarchy. See notes on the classification and the livelihood shapefiles. Level 1For example, A3 is the type and level of an Admin 3 unit. | |||||
Level codes | 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
...
per level | Each level is represented by two digits (e.g., 00, 01, 13). At each level, each unit must have a unique ID. Apply this process for as many levels as necessary. See Example 1 below. |
| Tip |
|---|
Example 1: Level codes To create the last part of an FNID, you will need to combine the codes for each relevant level. For example, if you are creating a code for an Admin 3 unit, you will need to combine codes for Admin levels 1, 2, and 3. Note the following in the image below:
|
...
|
...
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
FEWS NET ID (FNID) Structure:
2-letter country code
Year when the intersect shapefiles is being created
Admin unit code
LHZ code where the admin unit is located
Concatenate all the values together
...
 |
| Tip |
|---|
Example 2: Creating a C-type FNID in Afghanistan In Afghanistan, FEWS NET maps FIC data using the intersection of Admin 2 (districts) and livelihood zones. The |
...
FNIDs for these intersect units are structured as follows:
|
...
|
...
These are combined to create the following FNID: AF2018C3010108. |