Page History

Overview

...

CSV Geometry & Aliases File(s)

Naming Conventions

The CSVs containing geometry and aliases must all share a common name, suffixed with an underscore and the order of the CSV in the pack hierarchy.

...

1. auspack_1.csv - this will contain the State information from the hierarhcy.
2. auspack_2.csv - this will contain the Postcode information from the hierarhcy.
3. auspack_3.csv - this will contain the Suburb information from the hierarhcy.

File Format

The CSVs will need to contain data in the following structure:

...

For this example, when creating the top State CSV, we've decided to use two aliases; State Name, and State Code. This will mean that the file will look something like this:

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

...

The second level of the hierachy, the Postcode CSV, might contain a single alias, and we've chosen to link it to the State level on the State Code field. This will mean that the file will look something like this:

"Postcode"
"Postcode"
"2000","NSW","<WKT Point>","<WKT Polygon>"
"2009","NSW","<WKT Point>","<WKT Polygon>"
...
"3000","VIC","<WKT Point>","<WKT Polygon>"
"3008","VIC","<WKT Point>","<WKT Polygon>"
...
etc ...

...

The third level of the hierarchy, the Suburb CSV, might again contain a single alias, and we link to the Postcode level on the only alias available, Postcode. This will mean that the file will look something like this:

"Suburb"
"Suburb Name"
"Sydney CBD","2000","<WKT Point>","<WKT Polygon>"
"Darling Harbour","2000","<WKT Point>","<WKT Polygon>"
"Haymarket","2000","<WKT Point>","<WKT Polygon>"
"Darling Island","2009","<WKT Point>","<WKT Polygon>"
...
"Melbourne CBD","3000","<WKT Point>","<WKT Polygon>"
"Docklands","3008","<WKT Point>","<WKT Polygon>"
...
etc ...

CSV Demographic File

Naming Convention

This CSV file, containing demographic values for the bottom level of the hierarchy, must use the same common name used by the Hierarchy CSVs, suffixed with an underscore and the word "demo".

...

1. auspack_demo.csv - this will contain the Suburb demographic values.

File Format

The demographic data included in packs explore various values associated with census demographics available in the geographic area. The CSV will need to contain data in the following structure:

...

In this example, we will need to link our demographic information to the bottom of our hierarchy, the Suburb level. As our bottom level only has one alias, we'll use that to identify each row, if there were multiple available we would have to select one to use throughout. Either way we will need to specify this link in the metadata file, described later.

"Population","Median Income"
14308,75000,"Sydney CBD"
28371,60000,"Melbourne CBD"
...
etc ...

Metadata File

Naming Convention

This file, containing linking information about the CSVs, must use the same common name used by the CSV files, with no suffix or file extension.

...

1. auspack - this will contain the information on how each of the CSV files are linked together.

File Format

The metadata included in this file must define how each of the hierarchy and demographic CSVs are linked so that the pack is correctly generated.

...

1. The first row will need to pair the State and Postcode levels.
   The Postcode file uses the State Code field as the pairing field. The State Code is the 2nd column in the State file and the linking field is the 2nd column of the Postcode file. So the row will be 2,2.
2. The second row will need to pair the Postcode and Suburb levels.
   The Suburb file uses the Postcode field as the pairing field. The Postcode is the 1st column in the Postcode file and the linking field is the 2nd column of the Suburb file. So the row will be 1,2.
3. The third row will need to pair the Suburb level with the Demographic data.
   The Demographic file uses the Suburb Name field as the pairing field. The Suburb Name is in the 1st column in the Suburb file and the linking field is in the 3rd column of the Demographic file. So the row will be 1,3.
4. The fourth row will need to nominate how each metric in the Demographic file should be aggregated.
   The Population value should be summed up, and the Median Income should be averaged, so the row will be SUM,AVG.

2,2
1,2
1,3
SUM,AVG