Page History

...

1. First row containing the label for the level.
2. Second row containing labels for each alias column, labels for the point and polygon columns should not be included.
3. Remaining rows containing:
   1. Columns containing aliases (there can be as many aliases for a particular level as you require. Some levels may have one or two different aliases, but others may have several).
   2. If the CSV is not the top level of the hierarchy it must now have a column containing the alias value of the level directly above it that the row belongs to in order to link it.
      Note: as each level can have more than one alias, the linking aliases are defined in the metadata file described later.
   3. One Column containing a centroid Point.
   4. One Column containing Polygons (this can be left completely empty if polygons are not required or available for the level, but if it's populated, all rows must contain a polygon, no blanks will be accepted).

...

"State"
"State Name","State Code"
"New South Wales","NSW","<WKT Point>","<WKT Polygon>"
"Victoria","VIC","<WKT Point>","<WKT Polygon>"
...
etc ...

Note: the <WKT Point> and <WKT Polygon> text displayed in the examples above will have to actually contain Point and Polygon data, we've just displayed these as place-holders. Coordinates should be listed in the WKT as latitude longitude, not the other way around.

...

1. First rows contain links between the hierarchy CSVs. There will be one row for each child level. The way this is done is a pair of comma separated numbers:
   1. The first number tells you which column of the parent level file the linking field is.
   2. The second number tells you which column of the child level file the linking field is displayed in.
2. Second last row containing links between the bottom level of the hierarchy and the demographic CSV.
3. Last row containing how each of the demographic metrics should be aggregated. The values available are "AVG", "SUM", "MAX", and "MIN". These should be listed in the same order the fields are listed in the demographic CSV.

Note: if your file only contains one hierarchy level, or it doesn't contain demographic information, simply do not include metadata rows to link up this data.

...