Data Product Description

Transcription

Product:
Prepared:
Geoscape
Evaluation Dataset
May 2016
Data Product
Description
Standard
This document is based on the AS/NZS ISO 19131:2008 Geographic information – Data product
specifications standard. For more information, refer to www.saiglobal.com/online/.
Disclaimer
PSMA Australia believes this publication to be correct at the time of printing and does not accept
responsibility for any consequences arising from the use of information herein. Readers should rely on
their own skill and judgement to apply information to particular issues.
This work is copyright. Apart from any use as permitted under the Copyright Act 1968, no part may be
reproduced by any process without prior written permission of PSMA Australia Limited.
GEOSCAPE EVALUATION DATASET
PAGE i
Contents
1.
2.
3.
4.
5.
6.
Overview ......................................................................................................................................... 1
1.1
Data product specification title .................................................................................................. 1
1.2
Reference date.......................................................................................................................... 1
1.3
Responsible party ..................................................................................................................... 1
1.4
Language .................................................................................................................................. 1
1.5
Topic category........................................................................................................................... 1
1.6
Informal description of the data product.................................................................................... 1
1.7
Distribution format ..................................................................................................................... 2
1.8
Terms and definitions ................................................................................................................ 2
1.9
Abbreviations and acronyms ..................................................................................................... 3
Specification Scope ........................................................................................................................ 4
2.1
Scope identification – dataset ................................................................................................... 4
2.2
Scope identification – themes ................................................................................................... 4
Data Product Identification .............................................................................................................. 7
3.1
Title............................................................................................................................................ 7
3.2
Alternate titles ........................................................................................................................... 7
3.3
Abstract ..................................................................................................................................... 7
3.4
Purpose ..................................................................................................................................... 7
3.5
Topic category........................................................................................................................... 7
3.6
Geographic description ............................................................................................................. 8
Data Content and Structure .......................................................................................................... 10
4.1
Feature-based data ................................................................................................................. 10
4.2
Feature-based application schema (data model) ................................................................... 10
4.3
Data dictionary ........................................................................................................................ 11
4.4
Feature-based content scope ................................................................................................. 11
Reference System ........................................................................................................................ 12
5.1
Spatial reference system ........................................................................................................ 12
5.2
Temporal reference system .................................................................................................... 12
5.3
Reference system scope ........................................................................................................ 12
Data Quality .................................................................................................................................. 13
6.1
Positional accuracy ................................................................................................................. 13
6.2
Thematic Quality ..................................................................................................................... 14
6.3
Logical consistency ................................................................................................................. 15
6.4
Topological consistency .......................................................................................................... 15
6.5
Temporal Accuracy ................................................................................................................. 15
6.6
Completeness ......................................................................................................................... 15
PAGE ii
6.7
7.
Data Quality scope .................................................................................................................. 16
Data Capture................................................................................................................................. 17
7.1
Buildings Theme ..................................................................................................................... 17
7.2
Trees Theme ........................................................................................................................... 28
7.3
Swimming Pools Theme ......................................................................................................... 29
7.4
Swimming Pools Theme ......................................................................................................... 29
7.5
Elevation Theme ..................................................................................................................... 30
7.6
Data capture scope ................................................................................................................. 30
8.
Data Maintenance ......................................................................................................................... 31
8.1
Update frequency .................................................................................................................... 31
8.2
Maintenance scope ................................................................................................................. 31
9.
Data Product Delivery ................................................................................................................... 32
9.1
PSMA Partner Network Delivery Format Information ............................................................. 32
9.2
Organisation responsible for delivery...................................................................................... 33
10.
PSMA Data ................................................................................................................................... 34
Appendix A – Geoscape Evaluation Dataset Data Model Diagram ...................................................... 35
Appendix B – Data Dictionary................................................................................................................ 36
BUILDING .......................................................................................................................................... 36
SWIMMING POOL ............................................................................................................................ 46
SURFACE_COVER ........................................................................................................................... 46
TREES ............................................................................................................................................... 47
Tables
Table 1: BUILDING ................................................................................................................................ 36
Table 2: BUILDING POLYGON ............................................................................................................. 37
Table 3: BUILDING_ADDRESS ............................................................................................................ 38
Table 4: BUILDING_CAD ...................................................................................................................... 38
Table 5: BUILDING_PROPERTY .......................................................................................................... 39
Table 6: BUILDING _ZONE................................................................................................................... 39
Table 7: BUILDING_QUALITY_INDICATOR_AUT ............................................................................... 40
Table 8: BUILDING_QUALITY_INDICATOR_AUT Codes ................................................................... 40
Table 9: BUILDING_ADDRESS_PROCESS_AUT ............................................................................... 41
Table 10: BUILDING_ADDRESS_PROCESS_AUT Codes .................................................................. 41
Table 11: BUILDING_CAD_PROCESS_AUT ....................................................................................... 41
Table 12: BUILDING_CAD_PROCESS_AUT Codes ........................................................................... 41
Table 13: BUILDING_PROPERTY_PROCESS_AUT ........................................................................... 42
PAGE iii
Table 14: BUILDING_PROPERTY_PROCESS_AUT Codes ............................................................... 42
Table 15: GROUND_ELEVATION_SOURCE_AUT ............................................................................. 43
Table 16: GROUND_ELEVATION_SOURCE_AUT Codes .................................................................. 43
Table 17: ZONE_AUT ........................................................................................................................... 43
Table 18: ZONE_AUT Codes ................................................................................................................ 43
Table 19: SOLAR_PANEL_AUT ........................................................................................................... 44
Table 20: SOLAR_PANEL_AUT Codes ................................................................................................ 44
Table 21: ROOF_SHAPE_TYPE_AUT ................................................................................................. 44
Table 22: ROOF_SHAPE_TYPE_AUT Codes ...................................................................................... 45
Table 23: ROOF_TYPE_AUT................................................................................................................ 45
Table 24: ROOF_TYPE_AUT Codes .................................................................................................... 45
Table 25: SWIMMING_POOL_ADDRESS ............................................................................................ 46
Table 26: SURFACE_COVER_TYPE_AUT .......................................................................................... 46
Table 27: SURFACE_COVER_TYPE_AUT Codes .............................................................................. 46
Table 28: TREE_METADATA_AUT ...................................................................................................... 47
Table 29: TREE_METADATA_AUT Codes........................................................................................... 47
PAGE iv
1. Overview
1.1
Data product specification title
Geoscape Evaluation Dataset Product Description
1.2
Reference date
May 2016
1.3
Responsible party
PSMA Australia Limited | ABN: 23 089 912 710
Level 2, 113 Canberra Avenue, GRIFFITH ACT 2603 Australia
T: +61 2 6260 9000 | E: enquiries@psma.com.au | URL: http://www.psma.com.au
1.4
Language
English
1.5
Topic category
Boundaries for buildings and related characteristics within Australia.
1.6
Informal description of the data product
Geoscape will be a suite of digital datasets which represent buildings,
surface cover, swimming pools, trees, elevation and relationships to
representations of other land related data. The Geoscape Evaluation
Dataset is a subset of the anticipated national dataset and has been
designed to include expected product features. The dataset covers
approximately 25 square kilometres within Adelaide, South Australia.
In general terms, source data is derived from remotely sensed and volunteered information sources
and is coupled with data across all Australian jurisdictions to produce the final dataset.
The Geoscape Evaluation Dataset is comprised of 4 themes:
•
•
•
•
Buildings
o
1 building polygon spatial table
o
1 building aspatial table
o
4 tables linking buildings with related information
o
9 authority tables.
Trees
o
1 tree height raster dataset
o
1 tree metadata raster dataset
o
1 authority table.
Surface Cover
o
1 2m surface cover raster dataset
o
1 30m surface cover raster dataset
o
1 authority table.
Swimming Pools
PAGE 1
o
Swimming pool address aspatial table.
PSMA welcomes your feedback on the Geoscape Evaluation Dataset. We also publish regular
updates on Geoscape’s development on our website.
1.7
Distribution format
PDF
1.8
Terms and definitions
Term
Definition
Feature attribute
Characteristic of a feature (e.g. name of an area).
Class
Description of a set of objects that share the same attributes, operations, methods,
relationships, and semantics [UML].
NOTE: A class does not always have an associated geometry (e.g. the metadata
class).
Contours
A line connecting points of equal elevation/height, used to display a 3D surface on a
2D map or image.
Digital Elevation Model (Bare earth
model on regular grid)
The representation of continuous elevation values over a topographic surface by a
regular array of sampled z-values, referenced to a common datum and expressed
on a regular grid spacing or raster data set. The DEM is a ground only
representation and excludes vegetation such as trees and shrubs and human
constructed features such as sheds, houses and bridges.
Note: Some organisations refer to a bare earth model as a regular grid as a DTM. In
this context, refer the alternate DTM definition in this document.
Digital Surface Model - Irregular
Grid (Surface model irregular grid)
A topographic model of the earth’s surface in digital format represented by mass
points of variable density and may include break lines. The DSM represents
surfaces including ground, vegetation, buildings and other constructed features.
Digital Surface Model - Regular
Grid (Surface model on regular
grid)
The representation of continuous elevation or height values over a topographic
surface by a regular array of sampled z-values, referenced to a known datum and
expressed on a regular grid spacing or raster data set. The DSM represents
surfaces including ground, vegetation, buildings and other constructed features.
Digital Terrain Model (Bare earth
model on irregular grid)
A topographic model of the earth’s ground surface in digital format represented by
mass points of variable density and may include break lines. The DTM
representation of ground includes works such as levees, banks and roads, but
excludes vegetation such as trees and shrubs and human constructed features
such as sheds, houses and bridges.
Note: Some organisations refer to a bare earth model a regular grid as a DTM. In
this context, refer to the specific DEM definition in this document.
Elevation
This is a measure of height relative to a known vertical datum.
Event
Characteristic of a feature measured within an object without modifying the
associated geometry.
Feature
Abstraction of real world phenomena.
Feature attribute
Characteristic of a feature (e.g. name of an area).
Height
This is a measure of relative vertical difference between two known points on the
same vertical datum.
Object
Entity with a well-defined boundary and identity that encapsulates state and
behaviour [UML Semantics]
Note: An object is an instance of a class.
Package
Grouping of a set of classes, relationships, and even other packages with a view to
organizing the model into more abstract structures.
PSMA Systems Online Data
Delivery
A suite of applications to store, quality assure and distribute PSMA Australia’s
datasets.
Raster Resolution
This is a measure of an images pixel/cell dimensions, providing information on the
level of detail of features it represents. The smaller the value the higher level of
detail represented.
PAGE 2
Term
Definition
Resolution
This is a measure of the geometric fidelity of each building represented. It is a
combination of the minimum area of a polygon and minimum vertex separation.
Sensor
A device / machine that measures/records 1 or more physical properties.
Visible
Observable by someone with reasonable skill and expertise.
1.9
Abbreviations and acronyms
Term
Definition
ABS
Australian Bureau of Statistics
ASGC
Australian Standard Geographical Classification.
ASGS
Australian Statistical Geography Standard
AS4590:2006
Data interchange standard
AS/NZS 4819:2011
Rural and urban addressing standard
CD
Collection Districts (for Census collection)
DEM
Digital Elevation Model
DEM
Digital Elevation Model (See Terms and Definitions)
DPS
Data Product Specification
DSM
Digital Surface Model (See Terms and Definitions)
DTM
Digital Terrain Model (See Terms and Definitions)
FOI
Features of Interest
GDA94
Geocentric Datum of Australia 1994
GIDB
A copy of the IDB for use in Data Maintenance in Radius Studio™
G-NAF
Geocoded National Address File
GCCSA
Greater Capital City Statistical Areas
ICSM
Intergovernmental Committee on Surveying & Mapping
IDB
Integrated Data Base
LiDAR
Light Detection and Ranging
MB
Mesh Blocks
NAMF
National Address Management Framework
PID
Persistent Identifier
SLA
Statistical Local Area
TIN
Triangulated Irregular Network
UCL
Urban Centre Localities
UML
Unified Modelling Language
WGS84
World Geodetic System 1984
WV2
World View 2
WV3
World View 3
PAGE 3
2. Specification Scope
The Feature Based Content, Reference Systems, Data Quality, Data Capture and Data Maintenance
also have defined scopes regarding the data accuracy, geometry, metadata and temporal
considerations of the data release cycle.
2.1 Scope identification – dataset
Geoscape Evaluation Dataset
Level
Dataset
Level name
Geoscape Evaluation
Extent
The Evaluation Dataset product extent covers an area of approximately 25 square kilometres.
2.2 Scope identification – themes
Geoscape Evaluation Dataset themes
Level
Theme
Level name
•
Buildings
•
Trees
•
Surface Cover
•
Swimming Pool
•
Elevation
PAGE 4
Extent
The Geoscape Evaluation Dataset product has been defined as ‘Urban’. The classification of ‘Urban’
has been developed based on a number of factors including the probability of the occurrence of a
natural events (e.g. flooding), population distribution and industrial/commercial activities.
The following extent will be used for the Geoscape Evaluation Dataset Product:
o
Area: Approximately 25 square kilometres
Figure 1: Geoscape Evaluation Dataset extent.
Spatial coverage of Australia’s buildings using remotely sensed information.
A building is a digital representation of the roof outline of buildings which have been classified from
remotely sensed information.
The buildings dataset represents building footprints that have been created using a combination of
automated and manual processes to extract and orthogonalise building roof outlines from remotely
sensed sources. These processes use electromagnetic radiation reflectance in the red, green and
blue bands (visible bands) to classify pixels based on known patterns of signal combinations from
various building roof types.
The Trees dataset is a digital representation of areas which are classified using remotely sensed
information as ‘trees’ generally using additional spectral bands. Where information is classified as
trees, various digital surface model and digital elevation model sources have been used to derive each
cell values height.
Surface Cover is a digital representation of the location of different types of surface cover which have
been classified from satellite imagery. This theme contains 2 variations; one a high resolution dataset
representing surface cover within urban areas, the other a national 30m resolution dataset
representing surface coverage nationally.
Swimming pools is a digital relationship between swimming pools and addresses for Australia.
PAGE 5
Elevation is a digital representation of the terrain, national coverage of terrain elevation is currently
available from Geoscience Australia. Geoscape will utilise the National 1 sec hydrologically enforced
SRTM to assign building features Z vertices and centroid elevations where data of higher
resolution/accuracy cannot be sourced. The SRTM provides a terrain surface that supports relative
heights provided for buildings.
The national SRTM is available to use with the Geoscape Evaluation Dataset Product at the following
location:
http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_a05f7893-0050-7506-e04400144fdd4fa6
PAGE 6
3. Data Product Identification
3.1 Title
Geoscape Evaluation Dataset
3.2 Alternate titles
Geoscape Evaluation Dataset for Australia
3.3 Abstract
Geoscape will be a suite of digital datasets which represent buildings, surface cover, swimming pools,
trees, elevation and relationships to representations of other land related data. This particular product
is a subset of the anticipated national dataset and has been designed to include expected product
features. The coverage is an area of urban Adelaide, outside of the central business district. In general
terms, source data is derived from remotely sensed and volunteered information sources and is
coupled with data across all Australian jurisdictions to produce the final dataset.
3.4 Purpose
The purpose of this Evaluation Dataset version of the Geoscape dataset is to represent building and
related features in a small geographic area to elicit feedback from potential users.
The purpose of a national dataset will be to spatially represent building and related features for the
use by industry and government in digital applications / systems.
3.5
Topic category
Vector and raster spatial data defined by coordinates (latitude and longitude) with associated textual
metadata.
PAGE 7
3.6 Geographic description
Urban area in Adelaide, South Australia.
o
o
o
Area: Approximately 25 square kilometres
North East Corner: 138.609 E -34.951 S
South West Corner: 138.553 E -34.995 S
Figure 2: Geoscape Evaluation Dataset extent.
The anticipated national product would have the following geographic description:
The Geoscape datasets cover the landmasses of Australia boundaries within the national geography
of Australia (AUS). The bounding box for this data is as follows;
North bounding latitude: -10˚
South bounding latitude: -45˚
East bounding longitude: 154˚
West bounding longitude: 112˚
This area covers the landmasses of Australia (Geographic Australia), but excludes External
Territories (e.g. Christmas Island, Norfolk Island) and some offshore islands (e.g. Lord Howe Island).
The spatial domain is described by the polygon:
PAGE 8
Figure 3: Geographic Australia
Geographic extent name
AUSTRALIA EXCLUDING EXTERNAL TERRITORIES – AUS – Australia – Australia
The States and Territories within Australia are represented by the following:
State or Territory Name
Abbreviation
Character Code
New South Wales
NSW
1 (or 01)
Victoria
VIC
2 (or 02)
Queensland
QLD
3 (or 03)
South Australia
SA
4 (or 04)
Western Australia
WA
5 (or 05)
Tasmania
TAS
6 (or 06)
NT
7 (or 07)
ACT
8 (or 08)
OT
9 (or 09)
Northern Territory
Australian Capital Territory
Other Territories
Note: PSMA has aligned Other Territories (OT) with the Australian Bureau of Statistics (ABS). It includes
the Territory of Christmas Island, Territory of Cocos (Keeling) Islands, Jervis Bay Territory and more
recently the inclusion of Norfolk Island. OT does not include any other external Territory. The Geoscape
dataset currently only includes Jervis Bay Territory from OT, which forms part of Australia’s main landmass.
PAGE 9
4. Data Content and Structure
The Geoscape Evaluation Dataset is a feature-based product. A data model is included (Appendix A)
with an associated data dictionary (Appendix B).
4.1
Feature-based data
The feature type is a spatial polygon or raster representation for the various Geoscape Evaluation
Dataset features. The table below outlines the features and their integration into related datasets.
Entity
Description
Integration
Rules
Building
A building feature will have one or
more spatial representations. Polygon
representations define the building’s
boundary as observed from an
elevated perspective.
A building’s spatial representation has:
Building polygons are a
minimum of 9m2 in area.

0 to many related G-NAF Address
records

0 to many CAD related records

0 to many Property related records

0 to many related Zoning records
Trees
An area classified as ‘trees’ will have
raster cells defining the boundary
No special rules
Surface
Cover
Each surface cover classification area
will have raster cells.
Building polygon
representations are used to
define the building class in
the 2m surface cover.
Where the building polygon
representation intersects the
majority of a pixel the
building classification
supersedes any existing
pixel classification with the
exception of the trees
classification.
Swimming
Pool
A swimming pool will not be
represented spatially
Elevation
A building will have vertices with Z
values, and be assigned a centroid
elevation value.
A swimming pool has:

No special rules
1 to many related G-NAF Address
records
4.2 Feature-based application schema (data model)
The Geoscape Evaluation Dataset Data Model Diagram is set out in Appendix A.
PAGE 10
4.3
Data dictionary
Feature-Based Feature Catalogue
The feature catalogue in support of the application schema is provided in Appendix B. Spatial
attributes are added to the feature catalogue in the same manner as other attributes for completeness
and conformance to the application schema.
The following table refers to all tables in the Feature Catalogue.
Column
Abbreviation
Description
Name
Name
The name of the column in the Integrated Database
Data Type
Data type
The Oracle data type of the column. Mapinfo TAB files have similar data types.
Description
Description
A description of the column and what the expected contents are
Primary Key?
Prim Key
If 'Y' then this column must always have a unique value. (has # entry in the data
model tables)
Obligation
Man
Y = mandatory. If 'Y' (mandatory), this column is populated with data.
That is, all ACTIVE records must have values in this column.
Foreign Key Table
F K TABLE
Represents a column in the 'Foreign Key Table' that this column is referred to by
another table. (has * entry in the data model tables)
Foreign Key
Column
F K Col
Represents a table in the Integrated Database that this column is referred to.
10 Character Alias
10 Char Alias
An alias for this column name - up to 10 characters maximum. Used to define the
name of the column when in ESRI Shapefile format.
4.4 Feature-based content scope
All geometry and metadata for polygons within the Geoscape Evaluation Dataset.
PAGE 11
5. Reference System
5.1
Spatial reference system
Vertical Datum
The Australian Height Datum (AHD) is the target vertical datum.
Horizontal Datum
The Geocentric Datum of Australia 1994 (GDA94) is the target horizontal datum.
Coordinate System
Vector Data spatial data is represented using:
Geographic Coordinate System Geocentric Datum of Australia 1994 (GDA94).
Raster spatial data is represented using:
A Universal Transverse Mercator projection appropriate for Australia, the Map Grid of Australia
Geocentric Datum of Australia 1994 (GDA94) at a zone appropriate for the spatial dataset being
delivered. For the Geoscape Evaluation Dataset, this is MGA94 Zone 54.
5.2
Temporal reference system
Gregorian calendar
5.3
Reference system scope
The spatial objects and temporal collection periods for the Geoscape Evaluation Datasets.
PAGE 12
6. Data Quality
6.1 Positional accuracy
Positional accuracy is an assessment of the closeness of the location of the spatial objects in relation
to their true positions on the earth’s surface.
The positional accuracy includes:
•
a horizontal accuracy assessment
•
a vertical accuracy assessment
The horizontal and vertical positional accuracy are the assessed accuracy after all transformations
have been carried out.
Horizontal accuracy
Horizontal positional accuracy of Geoscape data reflects the positional accuracy of source sensors
utilised in data collection, and the reliability of feature classification and associated orthogonalisation
processes.
Feature extraction of buildings was completed across satellite imagery resampled to 50cm resolution.
The horizontal positional accuracy of source imagery varies across collected strips. The horizontal
positional accuracy of imagery used for the extraction of features ranges from +/-0.5m CE90, to +/-2m
CE90. The positional accuracy of the vertices of unobstructed features will reflect the accuracy of the
source imagery from which it is extracted. Obstructed vertices will have their position estimated with
building shapes orthoganalised using specialised algorithms with some operator assistance.
Relative spatial accuracy between building features is +/- 2m in instances where feature vertices are
well defined. Relative accuracy between two obscured vertices will be influenced by the level of visual
obstruction.
The 2m surface cover was classified from satellite imagery at a 2m grid spacing. The horizontal
positional accuracy of source imagery varies across collected strips. The horizontal positional
accuracy of imagery used for the classification of surface cover pixels ranges from +/-0.5m CE90, to
+/-2m CE90. The positional accuracy of the 2m surface cover pixels will reflect the accuracy of the
source imagery from which it was classified as well as the classification process.
The trees dataset is derived from the 2m surface cover and inherits the horizontal positional accuracy
of the 2m surface cover dataset.
The 30m surface cover was classified from satellite imagery at a 30m grid spacing owing to the
resolution of source sensors active in the imagery collection. The horizontal positional accuracy of
source imagery used for the classification of surface cover pixels is +/-12m CE90. The positional
accuracy of the 30m surface cover pixels will reflect the accuracy of the source imagery from which it
was classified as well as the classification process.
Vertical accuracy
Source elevation data used for the derivation of building height attributes is a 0.5m resolution DSM
derived from high resolution satellite imagery. Absolute spatial accuracy of the DSM is +/-3m LE90, +/3m CE90 with relative accuracy +/-1m LE90, +/-2m CE90.
To determine building heights an elevation mask is applied to the building polygon to exclude tree
heights. The resultant polygon is then intersected with the DSM to attribute the minimum ground
surface, eave, and maximum roof elevations. Differences between these elevations are calculated and
attributed as heights to the building polygons.
PAGE 13
The attributed centroid elevation, and the elevation assigned to the building polygon vertices is
calculated by intersecting the centroid and the vertices of a building with the relevant corresponding
intersecting DEM, with the specific DEM recorded in the ground elevation source code attribute.
To determine tree heights the maximum intersecting DSM elevation is attributed to each tree pixel and
elevations are converted to heights by taking the difference between the maximum elevation and the
corresponding ground pixel value from a DEM derived from the DSM.
6.2
Thematic Quality
Thematic accuracy is defined as the accuracy of quantitative attributes and the correctness of nonquantitative attributes and of the classification of features and their relationships.
Classification Correctness - Building
Classification correctness is an assessment of the reliability of values assigned to features in the
dataset in relation to their true ‘real world’ values.
The Building Solar Panel attribute is classified using a combination of crowd sourcing, and machine
learning techniques. The rate of classification correctness of the solar panel attribute has been
measured at above 90% where a solar panel is present. Where a solar panel is not present it is
expected that the rate of classification correctness is greater than 95%.
The Building Roof Type attribute is spectrally classified from a combination of short wave infrared
(SWIR) and visible and near infrared (VNIR) imagery bands. The pixel size of SWIR imagery used in
the classification of the Building Roof Type attribute is 3.7m. Pixels that intersect the boundary of a
building polygon may return values from ground surfaces or neighbouring buildings impacting the
results obtained. Business rules have been introduced to mitigate this effect ensuring that all materials
attributed to a building are represented by a minimum number of intersecting SWIR pixels which
additionally compose at least 10% of the total roof area of the building polygon.
The rate of classification correctness of the Building Roof Type attribute is yet to be quantified. Initial
analysis has indicated the rate of classification correctness of residential buildings with roof types of
metal and tile is superior to the classification correctness of commercial and industrial buildings with
roof types of metal, tile, and flat concrete.
The Building Roof Shape attribute is classified by assessing the standard deviation of the elevation
values intersecting the building polygon once the vegetation mask has been applied. Characteristics of
a building that can impact the classification correctness of the roof shape include but are not limited to:
•
Roof furniture e.g. plant rooms, steeples, aerials.
•
Buildings that have a larger footprint than roof area.
•
Multiple buildings represented as a single building due to proximity.
•
Height of building.
The rate of classification correctness of the Building Roof Shape has been measured at above 90%.
Classification Correctness – Swimming Pool Address
The identification of a Swimming Pool at an Address is classified using a combination of crowd
sourcing, and machine learning techniques. Swimming pools are identified against a PSMA Property
Polygon and joined to matching addresses using a series of business rules. The rate of classification
correctness of a swimming pool at an address has been measured at above 85% where a swimming
pool is present. Where a swimming pool is not present at an address it is expected that the rate of
classification correctness is greater than 95%.
Classification Correctness – Surface Cover, Trees
PAGE 14
The 2m Surface Cover raster dataset and associated Trees raster is classified from visible and near
infrared (VNIR) imagery bands. The rate of classification correctness of the 2m Surface Cover has
been measured at above 90%.
The 30m Surface Cover raster dataset is classified from Landsat imagery. The rate of classification
correctness of the 30m Surface Cover has been measured at above 90%.
6.3 Logical consistency
Logical consistency is a measure of the degree to which data complies with the technical specification.
The test procedures are a mixture of software scripts and onscreen, visual checks.
The data structure has been tested for conformance with the data model. The following have been
tested and confirmed to conform:
•
File names
•
Attribute names
•
Attribute lengths
•
Attribute types
•
Attribute domains
•
Attribute order in file.
•
Object type
•
Compulsory attributes populated
6.4 Topological consistency
Topological consistency is the measure of how features spatially relate to other features within and
across themes. Topological inconsistencies are identified using a combination of automated rules, and
visual analysis. Where topological inconsistencies are identified they are notified back to the supplier
organisation for remediation at source. Some minor topological inconsistencies are corrected during
product processing using automated rules. The level of topological consistency is dependent on the
data supplied to PSMA.
Where topological inconsistencies exist they are identified within the product through the population of
the building polygon quality indicator attribute.
6.5 Temporal Accuracy
Temporal accuracy is an assessment of both temporal consistency (how well ordered lifecycle events
are) and temporal validity (validity of data with respect to time).
Building polygons within the Urban classification area are attributed with the capture date of the
imagery from which the outline has been captured.
6.6 Completeness
Completeness is an assessment of the extent and range of the dataset with regard to completeness of
coverage, completeness of classification and completeness of verification.
Dataset, theme, and layer coverage
For the Geoscape Evaluation Dataset the coverage will be 100% complete across the approximately
25 square kilometres as described in Section 3.6.
The Geoscape product contains a complete population of Geoscape layers.
Attribute completeness
All layers within the Evaluation Dataset area have a full population of attributes.
PAGE 15
6.7
Data Quality scope
All spatial and aspatial features including their attributes in the current time period for the Geoscape
Evaluation Dataset.
PAGE 16
7. Data Capture
Overarching data attributes across the themes for each of the classification are provided in the table
below:
Class / Attribute
Building Attributes
• Address count
• Roof shape
• Roof type
• Solar panel indicator
Building Polygon Attributes
• Roof outline polygon
• Ground level Z value for roof outline vertices and centroid
• Number of roof outline vertices
• Roof area
• Maximum roof height
• Eave height
PSMA Data linkages:
• G-NAF
- Residential land use indicator
- Swimming pool address indicator
• Cadastre boundary
• Property boundary
• Zoning
Surface Cover Attributes
Built up areas
Road and path
Bare Earth
Buildings
Tree coverage
Grass coverage
Unspecified vegetation
Water
Unknown
Unclassified
Vegetation Height
Tree Height
7.1
Urban
Delivery Category
Rural Balance
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
2m & 30m Resolution
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
30m Resolution Only
X
X
X
X
X
X
X
X
X
X
X
-
Buildings Theme
The digital representation of the building footprint features has been created via classified remotely
sensed sources using automated techniques from high quality, ortho-rectified, base imagery. The
base imagery used is selected from the available image catalog. Image quality factors including
currency, capture geometry, applicable weather conditions influence the specific image which can be
utilised for further processing. A suitable high quality Digital Surface Model is constructed to assist
with feature extraction. Each type of feature extracted follows a distinct (but related) processing
stream. The building footprints were classified from remotely sensed information on the WGS84
datum.
Further specific capture related information by feature is as follows;
Related Building Attributes:
A number of additional building related attributes are included in the Geoscape Evaluation Dataset
Building theme, specifically these attributes are
Centroid Elevation:
This value represents the building ground surface height in meters with respect to the Australian
Height Datum (AHD). The centroid is calculated as the geometric centroid of the building polygon, for
PAGE 17
irregular shaped features the centroid is ensured to lie within the bounds of the polygon. This centroid
location is intersected with, where available, a 5m Digital Elevation Model (DEM) supplied by
Geoscience Australia, or the national SRTM hydrologically enforced 1sec Digital Elevation Model
(DEM), to determine the building centroid height.
Number Vertices:
A count of the number of vertices for all rings of the polygon feature representing a building. Users
should note that a typical rectangular polygon feature has four vertices.
Area:
The area attribute value is a derived value calculated during processing. Area values are calculated
with features projected in a Transverse Mercator coordinate system.
Max Height:
Provided as an attribute on each building footprint by the supplier as a relative height in metres above
the ground surface. This is the maximum height identified within the building boundary and may
include the height of plant rooms and building fixtures.
Eave Height:
Provided as an attribute on each building footprint by the supplier as a relative height in metres above
the ground surface. All efforts have been taken to identify an ‘eave’ for each building boundary,
multilevel buildings and irregular facades may impact the accuracy of this value.
Roof Type:
Provided as an attribute on each building feature is the classification of the primary roof type. As a
large majority of buildings do not have an individual roof type an indicator on each roof type field
(Metal, Tile, Flat Concrete etc.) has been used to identify where various roof types may be present.
The Building Roof Type attribute is classified from a combination of short wave infrared (SWIR) and
visible and near infrared (VNIR) imagery bands which through a co-registration process are aligned to
provide a common pixel spatial resolution. The resulting stack of bands are processed through a
spectral matching algorithm to identify unique signatures of each surface present. Spectral analysis is
performed only on image pixels that intersect with the Building Polygon. The signatures are matched
to a spectral library of known material compositions to determine the best matching material for each
pixel.
Roof Shape:
Provided as an attribute on each building feature is the classification of the shape of a roof structure,
indicating whether a roof is flat, has a moderate pitch or complexity, or has a steep pitch or is highly
complex. This attribute has been classified using a statistical assessment of the roof heights found
across the building surface.
Solar Panel:
Provided as an attribute on each building feature is an indicator of the presence or absence of a solar
panel on the roof surface. Solar Panels have been identified using crowd sourcing and machine
learning techniques and provided to PSMA. Various types of solar panels may have been identified
and may contribute to a positive indication of their presence, these may include both photo-voltaic and
solar hot water.
Quality Indicator:
A quality flag has been included to identify buildings that have been modified during automated data
correction processes, or that a quality issue was identified but an automatic correction could not be
made. Over time, and with the further development of the product it may be possible to remove more
PAGE 18
of these issues, however for the purposes of this Evaluation Dataset, these features have been
included.
Overlaps within the building theme were automatically removed where possible. Any overlaps that
were removed, were removed from the building feature geometry which shared the longest line with
the overlap geometry. The Quality Indicator for features that have had an overlapped section removed
will be flagged to identify the overlap removal. Where quality issues were identified to a tolerance of
1mm but an automatic change could not be made, the Quality Indicator has been used to identify the
overlap.
Complex and Multi-part Building polygons have been split into simple polygons where the area is
greater than 9m2. Each simple feature has the same supplied Max and Eave Heights, relationship to
Building and Capture Date as the original multipart feature. The number of vertices and polygon_pid
will reflect the new simple feature. Each new simple feature will have the Quality Indicator flagged to
identify the split.
Small areas within building polygons including courtyards have been maintained where the area is
greater than 9m2 and the diagonal length of the area is greater than 4m. Other small areas have been
filled in and the Quality Indicator flagged to identify the removal of these features.
Has Residential:
The linkage table between address and building, features a separate attribute that has been included
to indicate if the address has been identified as being residential. The original source of the residential
indicator is derived from Commonwealth Government sources considered reliable. No personal
information is included in any data supplied to PSMA Australia.
Building Address Linkage:
A linkage between building and address features (from G-NAF) has been included to support the
usage of both datasets. Buildings are linked to the G-NAF product using a series of spatial
relationships. Not all addresses are used in this relationship with only addresses meeting the
following criteria used;
•
•
•
Principal addresses only (no Alias addresses),
Confidence 2, 1 or 0 only (no retired addresses or confidence -1),
All geocode types except Street Locality and Locality (no ‘UNK’, ‘STL’ or ‘LOC’ in
ADDRESS_DEFAULT_GEOCODE table)
The below relationships outline the connection between an address default geocode and buildings. In
the case of SA, where multiple geocodes are provided for a single address, address site geocodes
have also been used in this process:
PAGE 19
Building Address Process Type 1
BUILDING polygon spatially contains exactly 1 ADDRESS feature. The BUILDING is associated with
the 1 ADDRESS feature.
BUILDING polygon spatially contains more than 1 ADDRESS feature. The BUILDING is associated
with the multiple ADDRESS features.
BUILDING polygon does not spatially contain an ADDRESS, but has a spatial overlap of more than
80% with a PROPERTY that spatially contains exactly 1 ADDRESS feature. The BUILDING is
associated with the 1 ADDRESS feature.
BUILDING polygon does not spatially contain an ADDRESS, but has a spatial overlap of more than
80% with a PROPERTY boundary which spatially contains more than 1 ADDRESS feature. The
BUILDING is associated with the multiple ADDRESS features.
PAGE 20
BUILDING polygon does not spatially contain an ADDRESS, but the BUILDING spatially intersects
multiple PROPERTY boundaries which spatially intersect one or more ADDRESS feature(s). The
BUILDING is associated with the 1 or more ADDRESS feature(s).
ADDRESS feature(s) not associated with a BUILDING feature, but the ADDRESS feature(s) are within
a PROPERTY boundary associated with a BUILDING feature. The ADDRESS feature is associated
with the 1 or more BUILDING feature(s).
BUILDING polygon does not spatially contain an ADDRESS, but there is an ADDRESS within 15m of
the PROPERTY and the PROPERTY is the closest PROPERTY to that ADDRESS.
PAGE 21
BUILDING polygon does not spatially contain an ADDRESS, but the PROPERTY polygon it falls
within has the same PROPERTY PID as another PROPERTY polygon that contains an ADDRESS
that is within 1km distance of the original PROPERTY.
Building CAD Linkage:
A linkage between building and cadastre features (from CadLite) has been included to support the
usage of both datasets. Buildings are linked to the cadastre dataset using a series of spatial
relationships. Not all cadastral parcels are used in this relationship with only cadastral parcels meeting
the following criteria used;
•
•
Parcel Status of Registered
Parcel Type of Lot Parcel, Strata (including Horizontal and Vertical, and Stratum)
The below relationships outline the connection between the cadastre (CAD) and buildings:
Building CAD Process Type 1
The BUILDING POLYGON is completely contained by a CAD POLYGON feature. The CAD feature is
associated with the BUILDING feature.
PAGE 22
The BUILDING POLYGON completely contains a CAD POLYGON feature. The CAD feature is
associated with one or more BUILDING features.
The BUILDING POLYGON has a spatial overlap of more than 80% of the buildings area with a CAD
POLYGON feature. The CAD feature is associated with the BUILDING feature.
The BUILDING POLYGON has a spatial overlap of less than 80% but more than 10% of the buildings
area with a CAD POLYGON feature. The CAD feature is associated with the BUILDING feature.
PAGE 23
The BUILDING POLYGON has a spatial overlap of less than 10% of the buildings area with a CAD
POLYGON feature. The CAD feature is associated with the BUILDING feature.
The BUILDING POLYGON is completely contained by a CAD POLYGON feature that also contains a
CAD POINT feature. The CAD feature is associated with the BUILDING feature.
The BUILDING POLYGON has a spatial overlap of more than 80% of the buildings area with a CAD
POLYGON feature that also contains a CAD POINT feature. The CAD feature is associated with the
BUILDING feature.
PAGE 24
The BUILDING POLYGON has a spatial overlap of less than 80% of the buildings area with a CAD
POLYGON feature that also contains a CAD POINT feature. The CAD feature is associated with the
BUILDING feature.
Building Property Linkage:
A linkage between building and property features (from CadLite) has been included to support the
usage of both datasets. Buildings are linked to the property dataset using a series of spatial
relationships. Some States/Territories including SA, do not supply property points therefore no
relationships will be created for these States using the below relationship types of 3 or 4. The below
relationships outline the connections between property and buildings features:
Building Property Process Type 1
The BUILDING POLYGON is completely contained by a PROPERTY POLYGON feature. The
PROPERTY feature is associated with the BUILDING feature.
PAGE 25
The BUILDING POLYGON completely contains a PROPERTY POLYGON feature. The PROPERTY
feature is associated with one or more BUILDING features.
The BUILDING POLYGON has a spatial overlap of more than 80% of the buildings area with a
PROPERTY POLYGON feature. The PROPERTY feature is associated with the BUILDING feature.
The BUILDING POLYGON has a spatial overlap of less than 80% but more than 10% of the buildings
area with a PROPERTY POLYGON feature. The PROPERTY feature is associated with the
BUILDING feature.
PAGE 26
The BUILDING POLYGON has a spatial overlap of less than 10% of the buildings area with a
PROPERTY POLYGON feature. The PROPERTY feature is associated with the BUILDING feature.
The BUILDING POLYGON is completely contained by a PROPERTY POLYGON feature that also
contains a PROPERTY POINT feature. The PROPERTY feature is associated with the BUILDING
feature.
The BUILDING POLYGON has a spatial overlap of more than 80% of the buildings area with a
PROPERTY POLYGON feature that also contains a PROPERTY POINT feature. The PROPERTY
feature is associated with the BUILDING feature.
PAGE 27
The BUILDING POLYGON has a spatial overlap of less than 80% of the buildings area with a
PROPERTY POLYGON feature that also contains a PROPERTY POINT feature. The PROPERTY
Zoning Linkage:
The building / zone relationship has been determined via a spatial intersection between building
feature geometries and base zoning polygon datasets supplied from jurisdictions. A building is related
to all zones it intersects.
7.2
Trees Theme
Trees are a pixel representation of areas identified as having a tree coverage in remotely sensed
source imagery.
Trees have been identified by their spectral signature using remotely sensed information and are also
represented as raster cells within the surface cover dataset. Areas classified as Trees have been
integrated with Digital Surface Model (DSM) and Digital Elevation Model (DEM) Information to extract
a height value for every cell.
Although all efforts to provide an accurate height for all tree pixels have been undertaken, due to
proximity to other features, resolution and anomalies within the Digital Surface Model (DSM) and/or
the Digital Elevation Model (DEM) heights for a small portion of pixels are higher than the real world
feature they represent. To reduce the impact of these on the user, PSMA has assigned all trees that
are higher than plausible tree heights in the area to a height of 25m. The tree metadata dataset
identifies pixels that have been modified, the Tree Metadata AUT table describes the reason a tree
pixel has been modified any treatment that has occurred.
PAGE 28
7.3
Swimming Pools Theme
Surface cover features are contiguous pixel representations of basic surfaces as identified and
classified via automatic feature extraction routines over satellite imagery.
This theme contains 2 variations; one a high resolution (2m) dataset representing surface cover within
urban areas, the other a national resolution (30m) dataset representing surface coverage nationally.
A richer series of feature identification / classifications may be possible dependent on market
feedback.
7.4
Swimming Pools Theme
Properties that contain swimming pools have been identified using crowd sourcing techniques and
provided to PSMA.
Addresses identified within a property have been linked to the swimming pool. Not all Addresses are
used in this relationship with only addresses meeting the following criteria used;
•
•
•
Principal addresses only (no Alias addresses),
Confidence 2, 1 or 0 only (no retired addresses or confidence -1),
All geocode types except Street Locality and Locality (no ‘UNK’, ‘STL’ or ‘LOC’ in
ADDRESS_DEFAULT_GEOCODE table)
In the case of SA, where multiple geocodes are provided for a single address, address site geocodes
have also been used in this process.
PAGE 29
7.5
Elevation Theme
Elevation is a digital representation of the terrain, national coverage of terrain elevation is currently
available from Geoscience Australia. Geoscape will utilise the National 1 sec hydrologically enforced
SRTM to assign buildings Z vertices and centroid elevations where data of higher resolution/accuracy
cannot be sourced. The SRTM provides a terrain surface that supports relative heights provided for
buildings.
The national SRTM is available to use with the Geoscape Evaluation Dataset Product at the following
location:
http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_a05f7893-0050-7506-e04400144fdd4fa6
7.6
Data capture scope
Data for all objects included in the dataset in the current time period.
PAGE 30
8. Data Maintenance
Maintenance of the data is carried out at PSMA Australia using data supplied by third party providers,
Australian jurisdictions and PSMA. Several applications and database technologies are utilised during
production processes.
8.1
Update frequency
Maintenance activities are triggered by PSMA receiving updated data from data contributors according
to an agreed delivery schedule. At present, this schedule defines a quarterly update process. Updates
will be inserted into the Geoscape product as they are supplied by data contributors.
8.2
Maintenance scope
PSMA Australia’s data maintenance occurs for all existing objects with changed geometry, attributes
and/or metadata, as well as data for new objects within the release time period.
PAGE 31
9. Data Product Delivery
9.1 PSMA Partner Network Delivery Format Information
For the purposes of the product Evaluation Dataset;
Vector and aspatial data will be made available using only the Shape and MapInfo TAB formats
described below.
Raster data will be made available using only the Tagged Image File Format described below.
Dependant on market feedback the national product may be available in additional formats.
MapInfo TAB
Format Name:
TAB – MapInfo Professional™
Specification:
The MapInfo TAB format is a popular geospatial vector data format for geographic information
systems software. It is developed and regulated by MapInfo as a proprietary format. This format
includes files with the following extensions: *.tab, *.dat, *.id, *.map
TAB files support geospatial standards such as Open GIS, the OGC, ISO, W3C and others.
Language:
English
Shape
Format name:
Shape – ESRI™
Specification:
This format includes files with the following extensions: *.shp, *.shx, *.dbf
ESRI Shapefile Technical Description, an ESRI White Paper, July 1998. Follow this
link: www.esri.com/library/whitepapers/pdfs/shapefile.pdf
Language:
English
PAGE 32
Tiff
Format name:
Tagged Image File Format
Specification:
This format includes files with the following extensions: *.tif
A popular image format for storing and manipulating raster graphic images. The latest specification 6.0
was published in 1992 and maintained by Adobe Systems.
Language:
English
9.2
Organisation responsible for delivery
PSMA was formed by the governments of Australia in 1993 to collate, transform and deliver their
geospatial data as national datasets. PSMA’s establishment reflected the desire of Australian
governments to work together to establish a national location information infrastructure to advance the
emerging information economy. The organisation’s first major initiative was to support the 1996
Census through the provision of Australia’s first digital map at a national street-level.
The value of PSMA’s datasets is in the richness of the data, which enables a broad range of
innovations and applications. To support the use of this data in business-ready formats, PSMA makes
our data available to the market through a value-added reseller and integrator network. Our network
includes traditional geospatial specialists and data engineers as well as software developers,
marketing service providers, systems integrators and consultancies.
Contact us to provide feedback on the Geoscape Evaluation Dataset or for further information on
accessing PSMA Data:
PSMA Australia Limited
Unit 6, 113 Canberra Avenue, Griffith ACT 2603
T: 02 6260 9000
F: 02 6260 9001
E: enquiries@psma.com.au
W: www.psma.com.au
PAGE 33
10.
PSMA Data
DATASET
ACCESS
THEME
LAYER
Administrative
Boundaries
Open Data
(www.data.gov.au)
PSMA Partner
Network
ABS Boundaries
Mesh Blocks (MB) 2011
Indigenous Location
(ILOC)
Indigenous Areas (IARE)
Indigenous Region
(IREG)
Remoteness Areas (RA)
Socio-Economic Indexes
for Areas (SEIFA)
Urban Centre Localities
/Section of State
Significant Urban Areas
(SUA)
Electoral
Boundaries
Commonwealth Electoral
Boundaries
State Electoral
Boundaries
Local Government
Areas (LGAs)
Suburbs/Localities
State Boundaries
Town Points
Wards
CadLite
PSMA Partner
Network
Cadastre
G-NAF
Open Data
(www.data.gov.au)
PSMA Partner
Network
Geocoded physical addresses
Land Tenure
PSMA Partner
Network
Land Tenure
PSMA Partner
Network
Postcodes
PSMA Partner
Network
Spatial postcodes
PSMA Partner
Network
Transport
Transport &
Topography
Property
Postcode Polygons
Postcode Centroids
Roads
Rail
Rail Stations
Airports
Hydrology
Hydrology
Greenspace
Greenspace
PAGE 34
Appendix A – Geoscape Evaluation
Dataset Data Model Diagram
dm Geoscape
BUILDING_QUALITY_INDICATOR_AUT
BUILDING_CAD
*PK CODE: VARCHAR2(2)
NAME: VARCHAR2(50)
DESCRIPTION: VARCHAR2(254)
BUILDING_CAD_PROCESS_AUT
*PK BUILDING_CAD_PID: VARCHAR2(16)
*
DATE_CREATED: DATE
DATE_RETIRED: DATE
*FK BUILDING_POLY GON_PID: VARCHAR2(16) 0..*
*FK CAD_PID: VARCHAR2(15)
*FK PROCESS_TY PE_CODE: VARCHAR2(2)
1
0..*
1
CADCAD
0..*
BUILDING_POLYGON
1
*PK BUILDING_POLY GON_PID: VARCHAR2(16)
*
DATE_CREATED: DATE
DATE_LAST_MODIFIED: DATE
DATE_RETIRED: DATE
*FK BUILDING_PID: VARCHAR2(16)
*
CAPTURE_DATE: DATE
*
CENTROID_ELEVATION: NUMBER(7,2)
1
*
NUMBER_VERTICES: NUMBER(5)
FK QUALITY _INDICATOR: VARCHAR2(2)
*
AREA: NUMBER(10,2)
MAX_HEIGHT: NUMBER(7,2)
EAVE_HEIGHT: NUMBER(7,2)
FK GROUND_ELEVATION_SOURCE_CODE: VARCHAR2(2)
*
GEOMETRY : SDO_GEOMETRY
1
1
*PK CAD_PID: VARCHAR2(15)
0..*
BUILDING_PROPERTY
*PK BUILDING_PROPERTY _PID: VARCHAR2(16)
*
DATE_CREATED: DATE
DATE_RETIRED: DATE
0..*
*FK BUILDING_POLY GON_PID: VARCHAR2(16)
0..* *FK PROPERTY _PID: VARCHAR2(15)
BUILDING_PROPERTY_PROCESS_AUT
1
1
BUILDING_ADDRESS
*PK BUILDING_ADDRESS_PID: VARCHAR2(16)
DATE_CREATED: DATE
0..* *
0..*
DATE_RETRIED: DATE
*FK ADDRESS_DETAIL_PID: VARCHAR2(15)
0..*
HAS_RESIDENTIAL: VARCHAR2(1)
0..*
1..*
PROPERTY
PROPERTY
*PK PROPERTY _PID: VARCHAR2(15)
0..*
1
1..*
BUILDING_ADDRESS_PROCESS_AUT
1
ADDRESS
ADDRESS_DETAIL
1
*PK ADDRESS_DETAIL_PID: VARCHAR2(15)
*
ADDRESS_STRING: VARCHAR2(500)
BUILDING_ZONE
1
1
*PK BUILDING_ZONE_PID: VARCHAR2(16)
*
DATE_CREATED: DATE
DATE_RETIRED: DATE
*FK ZONE_CODE: VARCHAR2(2)
GROUND_ELEVATION_SOURCE_AUT
*
NAME: VARCHAR2(50)
0..*
1
ZONE_AUT
SWIMMING_POOL_ADDRESS
*PK SWIMMING_POOL_ADDRESS_PID: VARCHAR2(16)
*
SWIMMING_POOL_PID: VARCHAR2(16)
*
DATE_CREATED: DATE
0..1
DATE_RETIRED: DATE
*FK ADDRESS_DETAIL_PID: VARCHAR2(15)
SOLAR_PANEL_AUT
*
NAME: VARCHAR2(50)
NAME: VARCHAR2(50)
1 *
TREES_METADATA_AUT
1
0..*
BUILDING
ROOF_SHAPE_AUT
*PK BUILDING_PID: VARCHAR2(16)
*
DATE_CREATED: DATE
DATE_LAST_MODIFIED: DATE
DATE_RETIRED: DATE
0..*
*
STATE_PID: VARCHAR2(15)
*
ADDRESS_COUNT: NUMBER(5)
FK SOLAR_PANEL_CODE: VARCHAR2(2)
FK ROOF_SHAPE_CODE: VARCHAR2(2)
FK ROOF_TY PE_CODE: VARCHAR2(2)
0..*
TILE: VARCHAR2(5)
METAL: VARCHAR2(5)
PLASTIC: VARCHAR2(5)
FLAT_CONCRETE: VARCHAR2(5)
UNCLASSIFIED: VARCHAR2(5)
UNKNOWN: VARCHAR2(5)
*PK CODE: NUMBER(2)
*
NAME: VARCHAR2(50)
Legend
Spatial Attribute Table
Textual Attribute Table
Authority Code Table
1
*
NAME: VARCHAR2(50)
1
0..*
Raster Dataset
Elev ation Dataset (Not Included)
TREES_METADATA
ROOF_TYPE_AUT
1
*pf K TREE_METADATA_CODE: NUMBER(2)
*
NAME: VARCHAR2(50)
DIGITAL ELEVEVATION MODEL (DEM)
SURFACE COVER_2m
*pf K SURFACE_COVER_CODE: NUMBER(2)
TREES
*PK HEIGHT: number
DIGITAL SURFACE MODEL (DSM)
0..*
SURFACE_COVER_TYPE_AUT
*PK CODE: NUMBER(2)
*
NAME: VARCHAR2(50)
SURFACE COVER_30m
1
*pf K SURFACE_COVER_CODE: NUMBER(2)
1
0..*
PAGE 35
Appendix B – Data Dictionary
BUILDING
Table 1: BUILDING
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
building_pid
varchar2 (16)
The Persistent Identifier is unique to the real world feature this record
represents.
Y
Y
-
-
bld_pid
date_created
date
Date this record was created.
N
Y
-
-
dt_create
date_last_modified
date
Date this record was last modified from its previous state.
N
N
-
-
dt_lt_mod
date_retired
date
Date this record was retired.
N
N
-
-
dt_retire
state_pid
varchar2 (15)
The Persistent Identifier for the State or Territory.
N
Y
-
-
state_pid
address_count
number (5)
The count of addresses (principal > -1 confidence and address default
geocodes not ‘UNK’ ‘LOC’ or ‘STL’) within the same spatial property as
the building geometry.
N
Y
-
-
add_count
solar_panel
varchar2 (2)
Identifies if the roof surface has a visible solar panel or not.
N
N
solar_panel_aut
code
slr_pnl
roof_shape_code
varchar2 (2)
Identifies if a roof is of a complex or steep shape
N
Y
roof_shape_aut
code
rf_shp_typ
roof_type_code
varchar2 (2)
Identifies the likely dominant roof surface material
N
N
roof_type_aut
code
rf_typ
tile
varchar2 (5)
Indicator that the tile roof type has been identified
N
N
-
-
tile
metal
varchar2 (5)
Indicator that the metal roof type has been identified
N
N
-
-
metal
plastic
varchar2 (5)
Indicator that the plastic roof type has been identified
N
N
-
-
plastic
flat_concrete
varchar2 (5)
Indicator that the flat concrete roof type has been identified
N
N
-
-
flat_conc
unclassified
varchar2 (5)
Indicator that a roof type could not be classified
N
N
-
-
unclass
unknown
varchar2 (5)
Indicator that an unknown roof type has been identified
N
N
-
-
unknown
PAGE 36
Table 2: BUILDING POLYGON
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char
Alias
building_polygon_pid
varchar2 (16)
The Persistent Identifier is unique to the real world
feature this record represents.
Y
Y
-
-
bld_pg_pid
building_pid
varchar2 (16)
The Persistent Identifier is unique to the real world
N
Y
building
building_pid
bld_pid
date_created
date
N
Y
-
-
dt_create
date_last_modified
date
Date this record was last modified from its previous
state.
N
N
-
-
dt_lt_mod
date_retired
date
N
N
-
-
dt_retire
capture_date
date
The date the imagery was taken from which the
feature has been derived.
N
Y
-
-
capt_date
centroid_elevation
number (7,2)
The derived elevation at the centroid of the building
in metres on the Australian Height Datum (AHD)
N
Y
-
-
cent_ele
area
number (10,2)
The area of the building geometry in square metres
N
Y
-
-
area
number_vertices
number (5)
The number of vertices comprising the polygon, this
will return the start and end of each ring as
separate vertices. For distinct/unique vertex count
subtract 1 from this value
N
Y
-
-
numb_vert
max_height
number (7,2)
Maximum height of the building in metres
N
N
-
-
max_hght
eave_height
number (7,2)
Eave height of the building in metres
N
N
-
-
eave_hght
quality_indicator
varchar2 (2)
Description of known data quality issue
N
N
building_quality_indicator_aut
code
qual_ind
ground_elevation_source_code
varchar2 (2)
Source DEM for Z and centroid elevation values
N
N
ground_elevation_source_aut
code
grd_src_cd
geometry
SDO_GEOMETRY
polygon geometry
N
Y
-
-
geometry
PAGE 37
Table 3: BUILDING_ADDRESS
ADDRESS_DETAIL records are joined to BUILDING based on them having ADDRESS_DETAIL.CONFIDENCE > -1, ALIAS_PRINCIPAL not having a value of ‘A’
(alias) and ADDRESS_DEFAULT_GEOCODE.GEOCODE_TYPE_CODE not having a value of ‘UNK’ (unknown), ‘LOC’ (locality) or ‘STL’ (street locality).
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char
Alias
building_address
varchar2 (16)
This is the unique persistent identifier for each
building address relationship
Y
Y
-
-
bld_ad_pid
varchar2 (15)
The Persistent Identifier is unique to the building
N
Y
building_polygon
building_polgyon_pid
bld_pg_pid
address_detail_pid
varchar2 (15)
ADDRESS_DETAIL record.
N
Y
ADDRESS_DETAIL*
address_detail_pid
add_dt_pid
date_created
date
N
Y
-
-
dt_create
date_retired
date
N
N
-
-
dt_retire
process_type_code
varchar2 (2)
Processing value indicating reliability of association
between the building and an address
N
Y
building_address_process_aut
code
proc_type
has_residential
varchar2 (1)
A value of Y allocated where address information
has identified the landuse as residential
N
N
-
-
has_resi
_pid
* ADDRESS_DETAIL table is not included in this product, it is available in G-NAF.
Table 4: BUILDING_CAD
CAD_PID records are joined to BUILDING based on having CAD.PARCEL_STATUS of ‘1’ (registered), PARCEL_TYPE having a value of either ‘1’ (Lot Parcel), ‘2’
(Strata), ‘201’ (Horizontal Strata), ‘202’ (Vertical Strata) or 3 (Stratum).
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
building_cad
varchar2 (16)
building cad relationship
Y
Y
-
-
bld_cd_pid
varchar2 (16)
N
Y
building_polgyon
bld_pg_pid
cad_pid
varchar2 (15)
This is the unique persistent identifier for each CAD
record
N
Y
CAD*
cad_pid
cad_pid
_pid
PAGE 38
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
date_created
date
N
Y
-
-
dt_create
date_retired
date
N
N
-
-
dt_retire
process_type_code
varchar2 (2)
between the building and a cad record
N
Y
building_cad_process_aut
code
proc_type
* CAD table is not included in this product. It is available in CADLite
Table 5: BUILDING_PROPERTY
PROPERTY records are joined to BUILDING based on PROPERTY_PID.
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
building_property
varchar2 (16)
building property relationship
Y
Y
-
-
bld_pr_pid
varchar2 (16)
N
Y
building_polgyon
bld_pg_pid
property_pid
varchar2 (15)
Property record.
N
Y
PROPERTY*
property_pid
prop_pid
date_created
date
N
Y
-
-
dt_create
date_retired
date
N
N
-
-
dt_retire
process_type_code
varchar2 (2)
between the building and a property record
N
Y
building_property_process_aut
code
proc_type
_pid
* PROPERTY table is not included in this product. It is available in CADLite.
Table 6: BUILDING _ZONE
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
building_zone_pid
varchar2 (16)
building zone relationship
Y
Y
-
-
bld_zn_pid
PAGE 39
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
varchar2 (16)
N
Y
building_polygon
bld_pg_pid
zone_code
varchar2 (2)
A code relating to identifying the zone that the
building relates to.
N
Y
zone_code_aut
code
zone_code
date_created
date
N
Y
-
-
dt_create
date_retired
date
N
N
-
-
dt_retire
Table 7: BUILDING_QUALITY_INDICATOR_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
varchar2 (2)
Code identifying unique quality indicator.
Y
Y
-
-
code
name
varchar2 (50)
Name of the cleansing activity performed on the
feature.
N
Y
-
-
name
description
varchar2 (254)
Description of the cleansing activity performed
on the feature.
N
N
-
-
descriptn
Table 8: BUILDING_QUALITY_INDICATOR_AUT Codes
Code
Name
Description
O
Overlap
A section of the feature may overlap another feature
IR
Inner Rings
Small inner ring/s less than 9sqm has been removed
M
Multiple
A combination of cleansing processes has occurred on this feature
S
Split Complex Polygon
A complex polygon has been split into multiple simple parts
OR
Overlap Removed
A section of the feature has been removed due to an overlap with another feature
PAGE 40
Table 9: BUILDING_ADDRESS_PROCESS_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
varchar2 (2)
Code identifying unique process types.
Y
Y
-
-
code
description
varchar2 (254)
Description of the process type.
N
N
-
-
descriptn
Table 10: BUILDING_ADDRESS_PROCESS_AUT Codes
CODE
Description
1
BUILDING polygon spatially contains exactly 1 ADDRESS feature. The BUILDING is associated with the 1 ADDRESS feature.
2
BUILDING polygon spatially contains more than 1 ADDRESS feature. The BUILDING is associated with the multiple ADDRESS features.
3
BUILDING polygon does not spatially contain an ADDRESS, but has a spatial overlap of more than 80% with a PROPERTY polygon that spatially contains exactly 1 ADDRESS feature. The
BUILDING is associated with the 1 ADDRESS feature.
BUILDING polygon does not spatially contain an ADDRESS, but has a spatial overlap of more than 80% with a PROPERTY polygon which spatially contains more than 1 ADDRESS
feature. The BUILDING is associated with the multiple ADDRESS features.
BUILDING polygon does not spatially contain an ADDRESS, but the BUILDING spatially intersects multiple PROPERTY polygon which spatially intersect one or more ADDRESS feature(s).
The BUILDING is associated with the 1 or more ADDRESS feature(s).
ADDRESS feature(s) not associated with a BUILDING feature, but the ADDRESS feature(s) are within a PROPERTY polygon associated with a BUILDING feature. The ADDRESS feature
is associated with the 1 or more BUILDING feature(s).
BUILDING polygon does not spatially contain an ADDRESS, but there is an ADDRESS within 15m of the PROPERTY and the PROPERTY is the closest PROPERTY to that ADDRESS.
4
5
6
7
8
BUILDING polygon does not spatially contain an ADDRESS, but the PROPERTY polygon it falls within has the same PROPERTY PID as another PROPERTY polygon that contains an
ADDRESS that is within 1km distance of the original PROPERTY.
Table 11: BUILDING_CAD_PROCESS_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
varchar2 (2)
Y
Y
-
-
code
description
varchar2 (254)
N
N
-
-
descriptn
Table 12: BUILDING_CAD_PROCESS_AUT Codes
CODE
Description
1
The BUILDING polygon is completely contained by a CAD polygon feature. The CAD feature is associated with the BUILDING feature.
2
The BUILDING polygon completely contains a CAD polygon feature. The CAD feature is associated with one or more BUILDING features.
PAGE 41
CODE
Description
3
The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with a CAD polygon feature. The CAD feature is associated with the BUILDING feature.
4
The BUILDING polygon has a spatial overlap of less than 80% but more than 10% of the buildings area with a CAD polygon feature. The CAD feature is associated with the BUILDING
feature.
5
The BUILDING polygon has a spatial overlap of less than 10% of the buildings area with a CAD polygon feature. The CAD feature is associated with the BUILDING feature.
6
The BUILDING polygon is completely contained by a CAD polygon feature that also contains a CAD point feature. The CAD feature is associated with the BUILDING feature.
7
The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with a CAD polygon feature that also contains a CAD point feature. The CAD feature is associated with
the BUILDING feature.
8
The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with a CAD polygon feature that also contains a CAD point feature. The CAD feature is associated with
the BUILDING feature.
Table 13: BUILDING_PROPERTY_PROCESS_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
varchar2 (2)
Y
Y
-
-
code
description
varchar2 (254)
N
N
-
-
descriptn
Table 14: BUILDING_PROPERTY_PROCESS_AUT Codes
CODE
Description
1
The BUILDING polygon is completely contained by a PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.
2
The BUILDING polygon completely contains a PROPERTY polygon feature. The PROPERTY feature is associated with one or more BUILDING features.
3
The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with a PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.
4
The BUILDING polygon has a spatial overlap of less than 80% but more than 10% of the buildings area with a PROPERTY polygon feature. The PROPERTY feature is associated with the
BUILDING feature.
The BUILDING polygon has a spatial overlap of less than 10% of the buildings area with a PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.
5
6
7
8
The BUILDING polygon is completely contained by a PROPERTY polygon feature that also contains a PROPERTY point feature. The PROPERTY feature is associated with the BUILDING
feature.
The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with a PROPERTY polygon feature that also contains a PROPERTY POINT feature. The PROPERTY
The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with a PROPERTY polygon feature that also contains a PROPERTY point feature. The PROPERTY
PAGE 42
Table 15: GROUND_ELEVATION_SOURCE_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number (2)
Code identifying unique zone codes.
Y
Y
-
-
code
name
varchar2 (50)
Name of the zone type.
N
Y
-
-
name
description
varchar2 (500)
Description of the zone type.
N
N
-
-
descriptn
Table 16: GROUND_ELEVATION_SOURCE_AUT Codes
Code
Name
Description
1
SRTM (DEM-H)
1 Second SRTM Derived Hydrological Digital Elevation Model (DEM-H) Version 1.0.
2
5 metre DEM for South Australia
Digital Elevation Model (DEM) of Australia derived from LiDAR 5 Metre Grid.
Table 17: ZONE_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number (2)
Code identifying unique zone codes.
Y
Y
-
-
code
name
varchar2 (50)
N
Y
-
-
name
description
varchar2 (500)
N
N
-
-
descriptn
Table 18: ZONE_AUT Codes
Code
Name
Description
1
Commercial/Business
Areas where the permitted use is described as commercial focus.
2
Community Use
Areas where the permitted use is described as community use.
3
Conservation/National Park
Areas where the permitted use is described as National Park or areas where there is a conservation requirement.
4
Industrial/Utilities
Areas where the permitted use is described as industrial activities and utility facilities.
5
Mixed Use
Areas where the permitted use is described as for mixed use.
6
Recreational/Open Space
Areas where the permitted use is described as recreational activities and or open space.
7
Residential
Areas where the permitted use is described as residential.
PAGE 43
Code
Name
Description
8
Rural/Primary Production
Areas where the usage permits rural and primary production activities.
9
Special Use
Areas where the permitted use is described as special use.
10
Transport/Infrastructure
Areas where the permitted use is described as relating to transport and other infrastructure.
11
Water
Areas where the permitted use is described as relating to waterways.
0
Unknown
Areas where the permitted use is not known.
Table 19: SOLAR_PANEL_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number (2)
Code identifying unique solar panel codes
Y
Y
-
-
code
name
varchar2 (50)
N
Y
-
-
name
description
varchar2 (500)
N
N
-
-
descriptn
Table 20: SOLAR_PANEL_AUT Codes
Code
Name
Description
0
Unknown
The building has not been identified as either having or not having solar panels.
1
Yes
The building has been identified as having solar panels.
2
No
The building has been identified as not having solar panels.
3
Undecided
It is undecided if the building does or does not have solar panels.
Table 21: ROOF_SHAPE_TYPE_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number (2)
Code identifying unique roof shape types codes
Y
Y
-
-
code
name
varchar2 (50)
Name of the each roof shape type
N
Y
-
-
name
description
varchar2 (500)
Description of the roof shape type
N
N
-
-
descriptn
PAGE 44
Table 22: ROOF_SHAPE_TYPE_AUT Codes
Code
Name
Description
0
Unknown
The roof geometry of the building is unknown.
1
Flat
The roof geometry of the building has been identified as flat.
2
Moderate pitch or complexity
The roof geometry of the building has been identified as being moderately pitched or moderately complex.
3
Steep pitch or high complexity
The roof geometry of the building has been identified as being pitched and/or varied.
Table 23: ROOF_TYPE_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number (2)
Code identifying unique roof types codes
Y
Y
-
-
code
name
varchar2 (50)
Name of the each roof type
N
Y
-
-
name
description
varchar2 (500)
Description of the roof type
N
N
-
-
descriptn
Table 24: ROOF_TYPE_AUT Codes
Code
Name
Description
0
Unknown
Building has not been assessed
1
Unclassified
The roof type could not be classified
2
Metal
A roofing system made from metal sheets or tiles, this may include galvanised steel, zinc, aluminium, lead or tin.
3
Tile
A roofing system constructed from roof tiles traditionally made from locally materials such as terracotta or slate.
4
Fiberglass/Plastic
A roofing system typically made from a corrugated polycarbonate material.
5
Flat Concrete
A roofing system constructed from individual concrete slabs, the concrete may be a blend of broken stone, gravel and sand.
PAGE 45
SWIMMING POOL
Table 25: SWIMMING_POOL_ADDRESS
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
swimming_pool_address
varchar2(16)
swimming pool address relationship
Y
Y
-
-
sp_ad_pid
swimming_pool_pid
varchar2(16)
instance of swimming pool site.
N
Y
-
-
sp_pid
address_detail_pid
varchar2(15)
ADDRESS_DETAIL persistent Identifier
N
Y
ADDRESS_DETAIL
address_detail_pid
add_dt_pid
date_created
date
N
Y
-
-
dt_create
date_retired
date
N
N
-
-
dt_retire
_pid
* ADDRESS_DETAIL table is not included in this product. It is available in G-NAF.
SURFACE_COVER
Table 26: SURFACE_COVER_TYPE_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number(2)
Code identifying unique
surface_cover_type_code.
Y
Y
-
-
code
name
varchar2(50)
Name of the surface cover type.
N
Y
-
-
name
description
varchar2(100)
Description of the surface cover type.
N
N
-
-
descriptn
Table 27: SURFACE_COVER_TYPE_AUT Codes
code
Name
Description
2
Bare Earth
Includes sand dunes, desert, rock outcrops, bare soil other than bare agricultural land, and sparsely vegetated areas of
grass and shrub. Non-vegetated strip mines and quarries except where covered by development or water.
3
Road and Path
Roads and parking lots covered in a man-made material. Not to include hard packed dirt trails.
PAGE 46
code
Name
Description
4
Grass
Grass and herbaceous areas. Category may include herbaceous wetlands if images are collected during dry season or
periods of drought.
5
Trees
All trees including deciduous and evergreen woody vegetation.
6
Unspecified Vegetation
Any other vegetative material not included within the Grass or Tree class. This may include, but is not limited to, shrub,
scrub, agriculture, and aquatic plants.
7
Built-up Areas
Any areas of man-made environments and infrastructure excluding road and paths and buildings.
8
Water
Depending on the resolution quality of the imagery used, natural water will include streams, canals, ponds, lakes,
reservoirs, estuaries and bays.
9
Buildings
Where the majority of a pixel intersects a PSMA Geoscape vector building polygon representation.
10
Cloud
Area covered in cloud on date of collection.
11
Shadow
Area covered in shadow on date / time of collection.
TREES
Table 28: TREE_METADATA_AUT
Name
Data Type
Description
Prim
Key
Man
F K TABLE
F K Col
10 Char Alias
code
number(2)
Code identifying unique tree metadata code
Y
Y
-
-
code
name
varchar2(50)
Name of the tree metadata type.
N
Y
-
-
name
description
varchar2(100)
Description of the tree metadata type.
N
N
-
-
descriptn
Table 29: TREE_METADATA_AUT Codes
Code
Name
Description
1
Low Trees
Tree pixel did not meet minimum height requirement. Set to unspecified vegetation in SURFACE COVER 2M dataset.
2
High Trees
Tree pixel did not meet maximum height restriction. Tree height set to 25m.
PAGE 47

Data Product Description

Transcription

Similar documents

Level 5 – 03

a PDF of This Case Study

InsulStar Tech Bulletin

My Account quick access guide

Skoda Roomster - Platinum Motor Group

apartment 6.8 6th / 7th floor | 3 rooms | 106.7 m2

What is a Popsel? - University System of Georgia

Sportsmaster Brochure

SUSTAINABLE HARDSCAPES SUSTAINABLE HARDSCAPES

Lamella Roof