Page Comparison

...

1. 2-letter country code

2. Year of the geographic unit set version

3. Admin level number 

   1. For example Admin 1, Admin 2, Admin 3

4.  Admin 1 Level ID in the 00, 01, 02 format 

5.  Admin 2 level ID in the 00, 01, 02 format 

   1. Each individual Admin unit must have a unique ID at every level

   2. For example, in figure 1 below, Every Admin 1 has its own ID 

   3. then every Admin 2 that falls within each admin 1 has a unique ID

6. Admin 2 ID resets when the Admin 2 falls under a new Admin1 

   1. 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

7. Concatenate all the values together 

8. This process can be applied to further Admin levels 

   1. For example, Admin 3, Admin 4

   2. Keep adding admin ID levels as necessary

 FEWS NET ID (FNID) Structure: 

1. 2-letter country code

2. Year when the intersect shapefiles is being created 

3. Admin unit code

4. LHZ code where the admin unit is located 

5. Concatenate all the values together 

An example from Afghanistan, FEWS NET maps FIC data using the intersection of Admin 2 (districts) and livelihood zones. The FIC data mapping units FNIDs have the following structure: 

AF2018C3010108

Country: AF

Year:2018 

Class: C3 

Kabul admin 2 code: AF2017A20101

LHZ code: AF08