Skip to end of banner
Go to start of banner

Relationship Tables: Preparing and Uploading

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Relationship tables work as a path for the system to follow when looking at 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:

  1. Find the relevant relationship table spreadsheet.

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

      • Parts of, or the whole of two or more administrative units joined together to create a new administrative unit

    • Split

      • An administrative unit is divided in two (almost perfectly) to form new administrative units

  • There must only five rows of information

    • If there are multiple relationship sets, the oldest start-years are listed first, and when all relationships for that year are done, begin again for the next set

  • Uploading to FDW

    • Log in to FDW

    • Under Metadata Management

      • Spatial-Geographic Unit Relationships

    • Click Import Geographic Unit Relationships

    • Choose file

    • Format: .XLS (x)

    • Click Submit

    • Confirm Import

  • No labels