Relationship tables work as Geographic unit relationships provide a path for the system to follow when looking at comparing data across different administrative versions, e.g., comparing ML_1983 to ML_2016.
Preparing tables
Relationship tables should be completed before they are uploaded.
To prepare a relationship table for upload:
Find the relevant relationship table spreadsheet.
Go to flow chart tab and copy paste the appropriate data set by set (FNID, Admin name, relationship type, etc) starting from left to right
Copy all the relationship for changes from 1993-1996 from top to bottom
Once you finish that, copy all the relationships for changes from 1996-1997, etc.
This makes sure the data are ordered chronologically
For cases where there is only one start row that splits into multiple rows in the flow chart (Splits, redistributes, etc), make sure you copy the starting information for each individual split
...
Copied information
...
Copy start information for second row
...
Upload Requirements
Relationship table sheet must be first in the workbook (farthest left)
Relationship table has to follow exact format below from_name, from_fnid,relationship type, to_name, to_fnid
Older FNID goes on the left hand side, newer FNID goes on the right
Relationship Types must be one of predefined options
...
Successor
This means that there was no change or barely any change in this administrative unit between geographic unit set versions
...
Aggregate
An administrative unit becomes a higher level administrative unit
Admin2 becomes Admin1
...
Redistribute
Parts of a administrative unit were divided to become a part of new administrative units
...
Demotion
An administrative unit becomes a lower level administrative unit
IE Admin1 become Admin2
Merge
Geographic unit relationships can be updated in three ways.
If you need to update a few relationships, this can be done individually within the FDW.
If you need to update many relationships, this is best done by uploading a relationship table.
When adding new Markets and IDP camps, their relationships to admin units can be specified by adding a
parentcolumn that contains the FNIDs to the file. FDW will automatically create the relationships upon upload.
Relationship types
Relationship Types include:
Boundaries stay the same and data can be aggregated both forward and backward in time
Successor: This administrative unit did not change between geographic unit set versions.
Equivalent: Two units are equivalent between different geographic unit sets and do not need to be the same unit type, e.g., population and crop production units that are equivalent.
Seceded: Two units are equivalent between different geographic unit sets, are the same unit type, and can be part of separate countries, e.g., the admin 1 states of South Sudan seceded the admin 1 states of Sudan.
Name change: Only the name has changed between geographic unit set versions.
Promotion: An administrative unit becomes a higher-level administrative unit, e.g., Admin2 becomes Admin1.
Demotion: An administrative unit becomes a lower-level administrative unit, e.g., Admin1 becomes Admin2.
Boundaries change
Data can be aggregated forward in time
Merge: Parts of, or the whole of, two or more administrative units were joined together to create a new administrative unit version in the same geographic unit set.
Aggregate: Parts of, or the whole of, two or more administrative units were joined together to create a new administrative unit. However, unlike merge, this relationship doesn’t indicate anything about the relationship between the geographic unit sets.
Data can be aggregated backward in time
Split
An administrative unit is divided in two (almost perfectly) to form new administrative units
There must only five rows of information
: One administrative unit was divided to form two or more new administrative units.
Split_demotion: One administrative unit was divided to form two or more new administrative units and the new units are demoted to a lower admin level.
Data can not be aggregated
Redistribute: Parts of more than one administrative unit were divided and redistributed into more than one new administrative unit.
Definition of one unit within another, e.g., admin1_0 indicates the unit is an admin1 within a specific admin 0.
Updating geographic unit relationships
To add individual unit relationships:
Go to Metadata Management > Spatial > Geographic Unit Relationships.
Click Add Geographic Unit Relationship.
Choose a From Unit and a To Unit. You can search for units by typing a unit's name into the drop-down menu.
Choose a Relationship Type.
Click one of the Save options.
Preparing and uploading relationship tables
Preparing tables
To prepare a relationship table for upload, you will need to copy the relationship data from one tab to another in the relevant spreadsheet.
| Note |
|---|
The relationship table tab must be the first tab in the spreadsheet. Relationship tables should be completed before they are uploaded. |
The relationship tab should be set up as follows:
from_unit_name | from_unit | relationship_type | to_unit_name | to_unit |
|---|---|---|---|---|
The FDW will also accept "from_fnid", "from fnid", "fromfnid", or "fnid_from_unit" as the column header. | The FDW will also accept “relationship type” or “relationship” as the column header. | The FDW will also accept "to_fnid", "to fnid", "tofnid", or "fnid_to_unit" as the column header. | ||
This column should contain the name of the old geographic unit. | This column should contain the FNID of the old geographic unit. | This column should include the type of relationship between the old and new units. Use a type from the list at the beginning of this page. | This column should contain the name of the new geographic unit. | This column should contain the FNID of the new geographic unit. |
To copy the information:
You will need to copy the appropriate information from the FlowChart tab to the Relationship Table tab.
Copy information by dataset.
If there are multiple relationship sets, copy the data for the oldest start
-years are listed first, and whenyear first so they are at the top of the sheet. When all relationships for that year are done, begin again for the next set
Uploading to FDW
Log in to FDW
For cases where one start row splits into multiple rows in the FlowChart tab (e.g., when a unit splits or redistributes), copy over the starting information for each individual split.
Under Metadata Management
Spatial-Geographic Unit Relationships. This ensures the data are ordered chronologically.
...
Uploading relationship tables
Go to Metadata Management > Spatial > Geographic Unit Relationships.
Click Import Geographic Unit Relationships.
Click Choose
...
File.
Choose a format from the dropdown menu. This will likely be xls(x).
Click Submit
...
.
Confirm the import.
Troubleshooting relationship table uploads
Possible errors when uploading relationship tables include:
Extra columns: If the file contains extra columns that are not recognized by FDW, the upload will fail with an error message that notes the unidentified metadata. Remove the extra columns before re-uploading the file.
New geographic units: If the file contains units do not already exist in FDW, the upload will fail noting the unidentified units. Upload the new units to FWD before re-uploading the file.