Date: Thu, 28 Mar 2024 09:06:39 -0600 (MDT) Message-ID: <194082328.2479.1711638399399@confluence-external-wiki> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2478_873047683.1711638399398" ------=_Part_2478_873047683.1711638399398 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
=
Source & Disclaimer information is required for all GeoPacks. It's i= mportant to ensure any source data used has been acquired in an appropriate= manner and is allowed to be redistributed in this form.
For the purposes of the examples throughout the page, we will explore a = scenario around creating a GeoPack for Australia, which has three levels of= geographical hierarchy:
This pack will require five files:
The CSVs containing geometry and aliases must all share a common name, s= uffixed with an underscore and the order of the CSV in the pack hierarchy.<= /p>
In the case of the Australian GeoPack we're creating, the CSV Geometry &= amp; Aliases files will be called:
The CSVs will need to contain data in the following structure:
For this example, when creating the top State CSV, we'v= e decided to use two aliases; State Name, and Stat= e 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 ...
Note: the <= strong><WKT Point> and <WKT Polygon> = text displayed in the examples above will have to actually contain Point an= d Polygon data, we've just displayed these as place-holders. Coordinates sh= ould be listed in the WKT as latitude longitude, not the other way around.<= /p>
The second level of the hierachy, the Postcode CSV, mig= ht contain a single alias, and we've chosen to link it to the State= level on the State Code field. This will mean th= at the file will look something like this:
"Postco= de" "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 me= an 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 ...
This CSV file, containing demographic values for the bottom level of the= hierarchy, must use the same common name used by the Hierarchy CSVs, suffi= xed with an underscore and the word "demo".
In the case of the Australian GeoPack we're creating, the CSV Demographi= c file will be called:
The demographic data included in packs explore various values associated= with census demographics available in the geographic area. The CSV will ne= ed 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 wer= e 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= .
"Popula= tion","Median Income" 14308,75000,"Sydney CBD" 28371,60000,"Melbourne CBD" ... etc ...
This file, containing linking information about the CSVs, must use the s= ame common name used by the CSV files, with no suffix or f= ile extension.
In the case of the Australian GeoPack we're creating, the CSV Metadata f= ile will be called:
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.= p>
Note: if yo= ur file only contains one hierarchy level, or it doesn't contain demographi= c information, simply do not include metadata rows to link up this data.
In this example, we have a three level hierarchy, as well as demographic= information. This will mean that we need the following in the metadata fil= e:
2,2
.1,2
.1,3
.SUM,AV=
G
.2,2 1,2 1,3 SUM,AVG
This GeoPack provides geometry for every coun=
try on Earth. It includes a metric for country population estimates as of 2=
005. <= strong>Source:
Disclaimer: Although the data in this GeoPack has = been produced and processed from sources believed to be reliable, no warran= ty, expressed or implied, is made regarding accuracy, adequacy, completenes= s, legality, reliability or usefulness of any information. This disclaimer = applies to both isolated and aggregate uses of the information. The informa= tion is provided on an "as is" basis. All warranties of any kind, express o= r implied, including but not limited to the implied warranties of merchanta= bility, fitness for a particular purpose, freedom from contamination by com= puter viruses and non-infringement of proprietary rights are disclaimed. Ch= anges may be periodically made to the information herein; these changes may= or may not be incorporated in any new version of the publication. Da= ta can also quickly become out-of-date. It is recommended that careful atte= ntion be paid to the contents of any data associated with a file, and that = the originator of the data or information be contacted with any questions r= egarding appropriate use. If you find any errors or omissions, please repor= t them to the provider. |
As you can see, this pack has provided: