Buildings - geoscape.com.au · 1.2 Data Product Specification Title Buildings Product Description 1.3 Data Scope Buildings is a digital dataset representing buildings across Australia

Buildings Product Description Version 1.5

Buildings Product Description (Version 1.5) Page 2

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

Version History Date Version Applicability

March 2020 1.5 Release 1.5 onwards


Contents 1. Overview ....................................................................................................... 6

1.1 Delivery Organisation - about PSMA ............................................................... 6

1.2 Data Product Specification Title ..................................................................... 6

1.3 Data Scope ................................................................................................ 6

1.4 Reference Date .......................................................................................... 6

1.5 Responsible Party ....................................................................................... 6

1.6 Language .................................................................................................. 6

1.7 Topic Category ........................................................................................... 7

1.8 Informal Description of the Data Product ........................................................ 7

1.9 Distribution Format ..................................................................................... 7

1.10 Copyright and disclaimer ............................................................................. 7

1.11 Privacy ...................................................................................................... 7

1.12 Definitions, Acronyms and Abbreviations ........................................................ 8

2. Specification Scope ........................................................................................ 9

2.1 Scope Identification .................................................................................... 9

2.2 Extent ....................................................................................................... 9

3. Data Product Identification .......................................................................... 10

3.1 Title ....................................................................................................... 10

3.2 Alternate Titles ......................................................................................... 10

3.3 Abstract .................................................................................................. 10

3.4 Description .............................................................................................. 10

3.5 Purpose .................................................................................................. 11

3.6 Topic Category ......................................................................................... 11

3.7 Geographic Description .............................................................................. 11

3.8 Geographic Extent Name ........................................................................... 12

4. Data Content and Structure ......................................................................... 13

4.1 Feature-Based Data .................................................................................. 13

4.2 Feature-Based Application Schema (Data Model) ........................................... 13

4.3 Data Dictionary ........................................................................................ 13

5. Reference System ........................................................................................ 14

5.1 Spatial Reference System .......................................................................... 14

5.2 Temporal Reference System ....................................................................... 14

5.3 Reference System Scope ............................................................................ 14

6. Data Quality ................................................................................................ 15

6.1 Positional Accuracy ................................................................................... 15

6.2 Horizontal Accuracy .................................................................................. 15

6.3 Vertical Accuracy ...................................................................................... 15

6.4 Thematic Quality ...................................................................................... 16

6.5 Logical Consistency ................................................................................... 17

6.6 Topological Consistency ............................................................................. 18

6.7 Temporal Accuracy ................................................................................... 18

6.8 Completeness .......................................................................................... 18


6.9 Data Quality Scope ................................................................................... 18

7. Data Capture ............................................................................................... 19

7.1 Buildings Theme ....................................................................................... 21

8. Data Updates and Maintenance .................................................................... 52

8.1 Update Frequency ..................................................................................... 52

8.2 Update Scope ........................................................................................... 52

8.3 Update Rules ........................................................................................... 53

8.4 Building Change Management ..................................................................... 56

9. Delivery Format ........................................................................................... 62

9.1 Components ............................................................................................ 62

10. PSMA Partner Network .............................................................................. 64

11. PSMA Data Products ................................................................................. 65

Appendix A –Buildings Data Model ..................................................................... 66

Appendix B – Data Dictionary ............................................................................ 68

Appendix C - Building Address Process Type Examples ....................................... 87

1. Building Address Process Type 1 (BA01) .......................................................... 87









10. Building Address Process Type 10 (BA10) ..................................................... 97



13. Building Address Process Type 13 (BA13) ....................................................100



Appendix D – Building-CAD Process Type Examples .......................................... 103

16. Building CAD Process Type 1 (BC01) ...........................................................103











1. Overview

1.1 Delivery Organisation - about PSMA Geoscape is created by PSMA Australia. It is consistently formatted spatial data that

describes the buildings, addresses, land and transport networks across Australia’s complex

cities, regional centres and rural communities.

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 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 national

digital basemap at street-level.

The value of Geoscape data is in its richness, which enables a broad range of innovations

and applications. To support use of the data, it is available through online subscription

services in business-ready formats, as well as customised enterprise plans. PSMA has a

network of solution partners that integrate Geoscape data into other products and services.

The partner network includes traditional geospatial specialists and data engineers, as well

as software developers, marketing service providers, systems integrators and

consultancies.

1.2 Data Product Specification Title Buildings Product Description

1.3 Data Scope Buildings is a digital dataset representing buildings across Australia

There will be a Release Report provided with each update which will detail the specific

update areas and any issues contained within Buildings.

1.4 Reference Date March 2020

1.5 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: [email protected]

URL: www.geoscape.com.au

1.6 Language English.


1.7 Topic Category Boundaries for buildings and related characteristics within Australia.

1.8 Informal Description of the Data Product Buildings is a national digital dataset representing buildings for each State and Territory in

Australia.

Additionally, licencing includes access to linkages of other PSMA products, including:

• G-NAF

• CadLite (Cadastre and Property)

• Administrative Boundaries (Mesh Blocks and Suburbs/Localities)

Users should note that the listed PSMA products above are not part of Buildings and G-NAF

and Administrative Boundaries are available through PSMA’s Partner Network or under an

open licence from the Commonwealth of Australia at www.data.gov.au

The Mesh Block data is sourced from the Australian Bureau of Statistics (ABS) and is part

of their Australian Statistical Geography Standard (ASGS).

Data quality and potential capture timelines will vary across Australia based on three

categories, each category has been developed based on a number of factors including the

probability of the occurrence of natural events (e.g. flooding), population distribution and

industrial/commercial activities. Areas with a population greater than 200, or with

significant industrial/commercial activity in a visual assessment have been defined as

‘Urban’, areas meeting the same criteria however with known cultural or accessibility

sensitivities have been defined as ‘Remote Communities’, and all other regions have been

defined as ‘Rural Balance’.

PSMA welcomes your feedback on the Buildings Dataset. We also publish regular updates

on the development of our products on PSMA’s website.

1.9 Distribution Format This document is available in PDF format. For other formats and use of this document,

contact PSMA Support ([email protected])

1.10 Copyright and disclaimer Please see www.psma.com.au/psma-data-copyright-and-disclaimer

1.11 Privacy PSMA products and services should not contain any personal or business names or other

sensitive information. PSMA undertakes reasonable data cleansing steps as part of its

production processes to ensure that is the case. If you think that personal information may

have inadvertently been included in PSMA products or services, please contact

[email protected]

http://www.psma.com.au/psma-data-copyright-and-disclaimer


1.12 Definitions, Acronyms and Abbreviations Term Definition

Buffer Zone The inclusive area difference between Surface Cover 2M coverage and Urban and Remote coverage.

Building A structure generally permanent in nature which has been constructed to meet a specific objective (e.g. housing, storage, and workplace) and less permanent structures such as caravans and other portable housing may also be represented. All buildings are represented spatially both as polygons and points.

Building Point The automated calculation of the Building Polygon centroid.

Building Polygon A Building Polygon is a digital representation of the roof outline of a building which has been classified from remotely sensed information that identifies every structure that is greater than 9m2 and falls within an area defined by PSMA for the capture of buildings.

CE90 Abbreviation for circular error at 90% confidence, which is the location error in the horizontal plane. It is the radial error distance centred at zero within which 90% of the data points fall.

Contours A line connecting points of equal elevation/height used to display a 3D surface on a 2D map or image.

Digital Elevation Model (DEM) (Bare earth model on a 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 dataset. 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 in a regular grid as a DTM. In this context, refer to the alternate DTM definition in this document.

Digital Surface Model (DSM) - 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 (DSM) - Regular Grid (Surface model on a 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 dataset. The DSM represents surfaces including ground, vegetation, buildings and other constructed features.

Digital Terrain Model (DTM) (Bare earth model on the 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 in a regular grid as a DTM. In this context, refer to the specific DEM definition in this document.

Elevation This is a measure of vertical position relative to a known vertical datum.

Height This is a measure of the relative vertical difference between two known points on the same vertical datum.

LE90 Abbreviation for linear error at 90% confidence, which is the location error in the vertical plane. It is the absolute value error distance from zero within which 90% of the vertical data points fall.

Minimum resolution The lowest detail/most coarse representation of a building outline acceptable to PSMA.

Raster Resolution This is a measure of image pixel/cell dimension, providing information on the level of detail of features it represents. The smaller the value the higher the level of detail represented.

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.


2. Specification Scope

2.1 Scope Identification The Buildings dataset consists of one (1) theme and one (1) layer. The theme and layer

have a defined extent and scope.

Identification Of Buildings Dataset As Theme And Layer.

Dataset Theme Layer

Buildings Buildings Buildings

2.2 Extent Spatial coverage of Buildings includes Australia’s land mass. The dataset has areas

classified that meet certain criteria based on the occurrence of natural events (e.g.

flooding), population distribution and industrial/commercial activities. The classifications

are “Urban”, “Rural Balance” and “Remote Communities” and data captured varies based

on these three classifications.


3. Data Product Identification

3.1 Title Buildings

3.2 Alternate Titles • Formerly known as ‘Geoscape’.

• Buildings for Australia

3.3 Abstract Buildings is a spatial dataset which represents Australia’s built environment derived from

remotely sensed imagery. The dataset comprises of one theme and one layer:

• Building Theme: Building Layer

Buildings has relationships with other PSMA products:

• G-NAF

• CadLite and

• Administrative Boundaries (Suburb/Locality and Mesh Blocks).

3.4 Description Buildings represents Australia’s built environment: Buildings

The buildings theme (buildings layer) consists of digital representations of the roof outline

of a building which have been digitised from remotely sensed imagery using a combination

of automated and manual processes to identify, extract and orthogonalise objects

resembling a building structure greater than 9m2. The process also determines building

roof materials, and solar panel and swimming pool detection.


Data quality and potential capture timelines will vary across Australia based on three

categories. Each category has been developed based on several factors defined by the

population distribution, industrial/commercial activities and the probability of natural

events (e.g. flooding). Population distribution are categorised based on population size.

• Urban - areas with a population greater than 200, or with significant

industrial/commercial activity in a visual assessment

• Remote Communities - meeting the 'Urban' criteria with known cultural or

accessibility sensitivity and

• Rural Balance – all other areas

3.5 Purpose The purpose of the Buildings is to spatially represent building related features for use by

industry and government in geographic information systems and/or other information

systems.

3.6 Topic Category Vector spatial data defined by coordinates (latitude and longitude) with associated textual

(aspatial) metadata.

3.7 Geographic Description The spatial coverage of Buildings includes Australia’s land mass. The dataset has classified

areas within this coverage that meet certain criteria based on the occurrence of natural

events (e.g. flooding), population distribution and industrial/commercial activities. The

classifications are “Urban”, “Rural Balance” and “Remote Communities” and data captured

varies based on these three classifications. The Bounding Box for this data is as follows:

• North bounding latitude: -9˚

• South bounding latitude: -44˚

• East bounding longitude: 160˚

• West bounding longitude: 100˚

The area covers the land mass of Australia, including offshore islands. PSMA has plans for

Buildings to include data for other territories of Christmas Island, Cocos (Keeling) Islands

and Norfolk Island based on market demand.


3.8 Geographic Extent Name 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)

West Australia WA 5 (or 05)

Tasmania TAS 6 (or 06)

Northern Territory NT 7 (or 07)

Australian Capital Territory

ACT 8 (or 08)

Other Territories OT 9 (or 09)

Note: PSMA has adopted the Australian Bureau of Statistics (ABS) definition of ‘Other

Territories’ (OT). 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.


4. Data Content and Structure The Buildings 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 Buildings 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. Point representations are based on the centroid calculated from the polygon.

A building’s representation has:

0 to many related G-NAF Address records

0 to many CAD related records

0 to many Property related records

0 to one Suburb/Locality record

0 to many related Mesh Blocks

0 to one State/Territory record

0 to many related Zoning records

0 to many Swimming Pool records

4.2 Feature-Based Application Schema (Data Model) 4.3 Data Dictionary

4.3.1 Feature-Based Feature Catalogue

Spatial attributes are added to the feature catalogue in the same manner as other

attributes for completeness and conformance to the application schema.

Column Abbreviation Description

Name Name The name of the column in the Integrated Database.

Data Type Data type The data type of the column based on the types defined in ISO 19103:2015. Parentheses capture Scale, Precision and Maximum Length, where applicable.

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.3.2 Feature-Based Content Scope

All geometry and metadata for polygons within the Buildings Dataset.


5. Reference System

5.1 Spatial Reference System The Buildings product includes vector data (Building Polygons and Points).

5.1.1 Vector Data

GDA94

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: Geographic Coordinate System Geocentric Datum of Australia 1994

(GDA94).

GDA2020

Vertical Datum: The Australian Height Datum (AHD) is the target vertical datum.

Horizontal Datum: The Geocentric Datum of Australia 2020 (GDA2020) is the target

horizontal datum.

Coordinate System: Geographic Coordinate System Geocentric Datum of Australia 2020

(GDA2020).

5.2 Temporal Reference System Gregorian calendar

5.3 Reference System Scope The spatial objects and temporal collection periods for the Buildings dataset.


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. Positional accuracy consists of 2

assessments:

• Horizontal accuracy assessment, and

• Vertical accuracy assessment.

The horizontal and vertical positional accuracy is the assessed accuracy after all

transformations have been carried out.

6.2 Horizontal Accuracy The horizontal positional accuracy of Buildings data reflects the positional accuracy of

source sensors utilised in data collection, and the reliability of feature classification and

associated orthogonalisation processes.

The horizontal positional accuracy of source imagery varies across col lected strips. The

horizontal positional accuracy of imagery used for the extraction of urban buildings range

from +/-0.2m to +/-2.5m Circular Error 90% (CE90).

The horizontal positional accuracy of rural buildings is known to be less than 10.9m CE90

and has been measured across various rural locations with CE90 accuracy between 1.8m

and 7m.

The positional accuracy of the vertices of unobstructed building features will reflect the

accuracy of the source imagery from which it is extracted. Obstructed vertices will have

their position estimated with building shapes orthogonalised using trained algorithms with

some operator assistance.

6.3 Vertical Accuracy Source elevation data used for the derivation of building height attributes is a digital

surface model (DSM). Absolute spatial accuracy of the DSM ranges from +/-0.34m to +/-

2m Linear Error 90% (LE90), +/-0.2m to +/-2m CE90 with relative accuracies of +/-1m

LE90, +/-1m CE90.

Multiple factors can impact the quality of the assigned elevation or height, these include

but are not limited to:

• Age of source imagery: Where any imagery used within the production of the DSM is

older than the date of construction of a building then the heights attributed to that

building are likely to be erroneous.

• Correct classification of the feature: Where building is not correctly defined (i.e. the

highest point is not within the representation) then the height assigned to the feature

has an increased likelihood of being erroneous.

• The omission of the feature: Where a building is not captured it cannot be assigned a

height.

• Obscured building: Where a building is obscured by a tree or other feature then there

is an increased likelihood of erroneous height values being assigned despite processes

being run to limit this impact.

• Tree coverage surrounding a building: Where a building is surrounded by trees then

the algorithm to calculate the roof height may struggle to obtain a representative

ground elevation value. In these circumstances, there is an increased likelihood of an

erroneous height assignment.


• The off-nadir angle of source imagery: Where imagery used for the classification of

buildings is off-nadir then the side of a building may be represented within the

boundary of the footprint. Intersecting this part of the building against the DSM will

return lower elevation values than those expected for the roof of the building. Where

this occurs, there is an increased likelihood of an erroneous value being assigned to the

eave height. The likelihood and impact of this issue are increased relative to the height

of a building.

6.4 Thematic Quality Thematic accuracy is defined as the accuracy of quantitative attributes, the correctness of

non-quantitative attributes, and of the classification of features and their relationships.

6.4.1 Classification Correctness

Classification correctness is an assessment of the reliability of values assigned to features

in the dataset in relation to their true ‘real world’ values.

Building

The rate of classification correctness of the HAS_SOLAR_PANEL attribute has been

measured at above 85% where a photovoltaic solar panel is visible within the source

imagery. Where a photovoltaic solar panel is not visible in the source imagery it is

expected that the rate of classification correctness (in the negative) is greater than 90%.

Other types of solar panels (e.g. solar hot water) may be captured, however, classification

rates for these solar panels are known to be lower.

Building Roof and Roof Material

The PRIMARY_ROOF_MATERIAL_CODE & ROOF_MATERIAL_CODE attributes are

spectrally classified from imagery with pixel sizes greater than the imagery used to extract

the building polygon feature. Pixels that intersect the boundary of a building polygon may

return values from ground surfaces or neighbouring buildings impacting the results

obtained. All materials attributed to a building are represented by a minimum number of

intersecting pixels which comprise at least 10% of the total roof area of the building

polygon.

The rate of classification correctness of the ROOF_MATERIAL_CODE attribute has been

measured in excess of 70% across suburban residential areas. Commercial, industrial, and

higher density residential areas are known to have lower classification correctness of the

Roof Material Code.

Characteristics of a building that can impact the ROOF_TYPE_CODE 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.

• The height of the building.

• Overhanging trees.

The rate of classification correctness of the ROOF_TYPE_CODE has been measured at

above 90% on unobstructed buildings.


Swimming Pool and Swimming Pool Address

The rate of classification correctness of a swimming pool has been measured at above 85%

where a swimming pool is present.

The identification of a swimming pool at an address is matched against a PSMA Property or

CAD parcel polygon and joined to matching addresses. There are a small number of remote

communities, regional community areas (‘Urban’ outback areas) and settlements on the

edges of urban boundaries that are contained within significantly large property polygon/s

(greater than 1km). Addresses and Buildings in these areas will not have a relationship to

any swimming pools and therefore the buildings within these areas will have a

HAS_SWIMMING_POOL_ADJACENT attribute of ‘0’ (Unknown).

Zoning

The ZONE_CODE attribute is classified by mapping state, territory or local government

planning zone scheme information against high-level, generalised national zoning codes

developed by PSMA Australia (see

Table 57). The mapping of the planning schemes to the national zoning codes is a

generalised process and is not based on a detailed examination of each scheme. The

classification does not take into consideration standard planning overlays, multi-zoned

areas or amendments which may be made to planning schemes from time to time which

may not be reflected in the base zoning datasets.

The generalised national zoning codes attempt to reflect the general intention of the

individual planning schemes. However, they do not reflect differences in planning

legislation or its interpretation by state, territory and local government planning

authorities.

The ZONE_CODE attribute provides only a general indication of the planning zone for a

building and should not be treated as authoritative. It is therefore not suitable for purposes

such as planning and development decision making. Users should contact the relevant

state, territory or local government planning authority for authoritative planning scheme

information.

The source of data for the allocation of zones to buildings has large areas where no zoning

information exists. This is in predominately rural areas for the state/territory of NT, WA

and North West NSW. As a result, there will be no BUILDING_ZONE features for these

areas.

6.5 Logical Consistency Logical consistency is a measure of the degree to which data complies to a technical

specification. The test procedures are a mixture of software scripts and manual visual

analysis. The data structure of Buildings has been tested for conformance to 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 the file

• Object type

• Compulsory attributes populated


6.6 Topological Consistency Topological consistency is the measure of how features spatially relate to other features

within and across Buildings theme. 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 for remediation. Some minor topological

inconsistencies are corrected during product processing. The level of topological

consistency is dependent on the data supplied to PSMA. Where topological inconsistencies

continue to exist after supplier remediation they are identified within the product through

the population of the BUILDING_QUALITY, QUALITY_INDICATOR_CODE attribute.

6.7 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 are attributed with the capture date of the imagery from which the outline has

been captured.

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

Components that makeup Buildings includes Dataset, Theme, and Layer Coverage and

coverage will be 100% complete across the areas captured to date. The Buildings product

contains a complete population of Buildings layer.

Attribute Completeness

The layer within the Buildings have a full population of attributes in accordance with the

data model.

Feature Completeness

Building features are considered to have an omission rate below 3% in urban areas, with

the majority of omission being smaller buildings such as garden sheds. In rural areas,

buildings with an area of less than 100m2 are considered to have an omission rate of less

than 10% and buildings with an area of greater than 100m2 are considered to have an

omission rate below 3%.

6.9 Data Quality Scope All spatial features including their attributes in the current time period for the Buildings

Dataset.


7. Data Capture Attribution, data quality and potential capture timelines will vary across Australia based on

three categories. Each category has been developed based on several factors defined by

the population distribution, industrial/commercial activities and the probability of natural

events (e.g. flooding). Population distribution are categorised based on population size.

• Urban - areas with a population greater than 200, or with significant

industrial/commercial activity in a visual assessment

• Remote Communities - meeting the 'Urban' criteria with known cultural or

accessibility sensitivity and

• Rural Balance – all other areas

The age of source imagery used for Buildings also varies across each of the categories to

enable national coverage. ‘Urban’ areas have been captured with as recent as possible

source imagery, where possible within 18 months of the building feature creation date.

‘Rural Balance’ age of capture can fluctuate more, and in worst case scenarios could be

around 5-10 years old, the image below was provided to us from our supplier identifying

the potential age of source imagery used for building capture in the ‘Rural Balance’

category.

Age Of Rural Balance Source Imagery

Overarching data attributes available across the three classifications are provided in the

table below:


Building layer and attribution for different Area Categories

Class / Attribute Area Category

Urban Rural Balance Remote Communities

Building Attributes

Address count Y Y Y

Building centroid (point) Y Y Y

Building outline (polygon) Y Y Y

Eave height Y N Y

Ground elevation Y N Y

Ground level Z value for vertices and centroid*

Y Y Y

Maximum roof height Y N Y

Maximum tree height Y N Y

Number vertices for a polygon Y Y Y

Polygon area Y Y Y

Roof material Y N Y

Roof type Y N Y

Solar panel indicator Y N Y

Swimming pool adjacent Y N Y

Zoning Y Y Y

PSMA Data linkages

Cadastre Y Y Y

G-NAF Y Y Y

- Residential indicator Y Y Y

- Swimming pool address indicator Y N Y

Locality Y Y Y

Mesh blocks Y Y Y

Property Y Y Y

State/Territory Y Y Y

*Not available in MapInfo TAB format


7.1 Buildings Theme The building theme (building layer) consists of digital representations of the roof outline of

a building which have been digitised from remotely sensed imagery using a combination of

automated and manual processes to identify, extract and orthogonalise objects resembling

a building structure greater than 9m2. Image quality factors including currency, capture

geometry, and 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. Building footprints are classified on the WGS84 datum.

Further specific capture related information by feature is as follows:

7.1.1 Related Building Attributes

A number of additional building related attributes are included in the Buildings theme,

specifically, these attributes are:

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.

Centroid Elevation

This value represents the building ground surface height in meters with respect to the

Australian Height Datum (AHD). The centroid is the building point calculated as the

geometric centroid of the building polygon, for irregularly shaped features the centroid is

ensured to lie within the bounds of the polygon. This centroid location is intersected with

the best available data to assign building Z vertices and centroid elevations.

Source of the data used for elevation for each building feature is contained within the

SOURCE_AUT table.

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. Source of the data used for calculating the height is contained within the

SOURCE_AUT table.

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 currently or having previously

thought to be residential. The source of the residential indicator is currently derived from

Commonwealth Government sources, which PSMA considers reliable. No personal

information is included in any data supplied to PSMA Australia.

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. Source of the

data used for calculating the height is contained within the SOURCE_AUT table.

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.


Quality Indicator

A quality flag has been included to identify a spatial representation of buildings (points and

polygons) that have been modified during data correction processes, or that a quality issue

was identified but an automatic correction could not be made.

Overlaps

Many buildings share a common boundary. In some cases, new buildings are supplied that

either have minor overlaps with adjacent buildings or overlap existing buildings. Where

possible and where a building has a small overlap (less than 5% of the buildings area) the

overlap will be removed. Where an overlap removed, a quality indicator of “OR” is used.

Where an overlap exists and is unable to be removed, or has been introduced during

further processing, a quality indicator of “O” is used.

Inner Rings

All buildings are assessed to find and remove small inner rings, similar to the one

represented below. Features that have had an inner ring removed by this process are

flagged with a quality indicator of ‘IR’.

Inner Ring Within Building Polygon

Self-Intersections

Where possible all contributed building geometries are checked and repaired to fix any

issues, this includes self-intersections. In some cases, these are unable to be automatically

resolved and/or have been introduced by further processing. Buildings in these cases may

cause concern in loading into some applications, therefore, a quality indicator of ‘SI’ is

used to identify the buildings impacted.

Complex Geometries

When buildings are received, each building is assessed to ensure it is not considered a

complex or multipart polygon. Where a polygon is complex or multipart polygon, each part

of the existing feature is separated into unique ‘simple’ segments. This may mean each

part has attributes that relate to the other adjoining portions, attributes like height, roof

material and roof type will be impacted where a building has been split into multiple parts.

Where a building has been split, a quality indicator of ‘S’ is used.

Invalid Relationships

During the process of assigning relationships to other PSMA products, there are occasions

where the spatial relationship has not been created due to invalid geometries. Where there

is an invalid CAD Polygon this will impact the Building CAD relationships. Where there is an

invalid Property Polygon this will impact the Building Property relationships and also may

impact the Building Address relationship. Where buildings intersect invalid relational

features, a quality indicator of ‘IP’ or ‘IC’ is used.


Varying State Relationships

Spatial representation of the Borders of the Australian States and Territories can vary

across spatial datasets and authoritative sources of information. For example, there is a

variation between the State boundaries used for State allocation and the borders used for

Locality and Mesh Block linkages. Where a building is impacted by these variations and has

linkages to data in other State/Territories, a quality indicator ‘VSR’ is used.

Spike

Where possible all contributed buildings geometries are checked and repaired to fix any

issues, this includes spikes to ensure proper representation of the real world. Spikes are

identified and removed by altering the polygon geometry. Where a building is impacted by

a spike, a building quality indicator ‘SR’ is used.

Small Building

Buildings considers a building to be small if it has an area of less than nine (9) metres

squared. Supplied buildings that are less than three (3) metres squared are removed from

the product. Where a building area is less than 9 metres squared, a quality indicator ‘SB’ is

used.

Remediated Heights

A building height is calculated by identifying the intersection of the minimum ground pixel

within a buffer of the building. Where smoothing, ‘spill over’, or lack of sharpness between

buildings has impacted the method of calculating ground elevations, both building height

and eave height are adjusted by intersecting each affected building polygon to an

alternative source of ground height. Where a building height or eave height is remediated,

a quality indicator of ‘RH’ is used.

No Ground Centroids

All buildings that intersect a supplied source for elevation are assigned a ground centroid

elevation. Where there is no known or suitable source of elevation available, buildings will

have no Z values and no ground centroid elevations assigned. To identify these buildings, a

quality indicator of ‘NE’ is used.

Roof Material Type

Provided as an attribute on each building roof feature is the classification of the primary

roof material found across the building surface. As a large majority of buildings do not have

an individual roof material, each roof material type (Metal, Tile, Flat Concrete etc.) is

identified.

The Building Roof Type attribute is classified from image pixels that intersect the Building

Polygon. The image signature of the intersecting pixels is matched to a spectral library of

known material compositions to determine the best matching material for each pixel.

Roof Type

Provided as an attribute on each building feature is the classification of the shape type 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. Various types of solar panels may have been identified

and may contribute to a positive indication of their presence, these may include both

photovoltaic and solar hot water.

Swimming Pool:

Properties that contain swimming pools have been identified and provided to PSMA.


Tree

Provided as an attribute on each building feature for the maximum height of all trees that

intersect with the building.

Z Values

Provided as an additional Z coordinate for each vertex as part of the geometry of a feature.

This Z coordinate represents the ground elevation at this XY location. MapInfo TAB formats

are unable to store Z coordinates with the geometry, therefore each vertex of a building

will be represented by an XY coordinate only.

7.1.2 Linkages

Buildings uses the following PSMA products for inputs into the processing:

• G-NAF

• CadLite (Property and Cadastre)

• Administrative Boundaries (Suburbs/Localities and ABS mesh blocks).

The linkages with buildings are explained in detail below.

Building Mesh Block Linkage

The building/mesh block relationship has been captured in the BUILDING_MESH_BLOCK

table via a spatial intersection between building feature geometries and the 2011 and 2016

mesh block polygon datasets from the Australian Bureau of Statistics (ABS).

A building is related to every mesh block that a building intersects greater than or equal to

5% of the buildings area.

Building Mesh Block Linkage


Building State/Territory Linkage

The building/state relationship has been captured in the BUILDING table via a spatial

intersection between building polygon and a state/territory boundaries dataset. There is an

ongoing issue of alignment between State/Territory borders which may impact on the

allocation of a State/Territory.

A building will be allocated to the State or Territory boundary that the majority of the

building’s polygon area intersects.

Building State/Territory linkage

Building Suburb/Locality Linkage

The building’s relationship with Suburbs/Localities has been captured in the BUILDING

table via a spatial intersection between building polygon and PSMA’s Suburbs/Localities

product. There is an ongoing issue of alignment at State/Territory borders which may

impact on the allocation of a Suburb/Locality.

A building will be allocated to the GAZETTED Suburb/Locality where the building’s area

intersects a single GAZETTED Suburb/Locality.

Building Suburb/Locality linkage - single


If a building’s area intersects more than one GAZETTED Suburb/Locality, the building wil l

be allocated to the GAZETTED Suburb/Locality that the majority of the building’s area falls

within.

Building Suburb/Locality linkage - majority

If a building has not been allocated a GAZETTED Suburb/Locality, the building will be

assessed against HUNDRED and DISTRICT boundaries. A building will be allocated to the

HUNDRED or DISTRICT where the building’s area intersects a single HUNDRED or

DISTRICT.

Building Hundred/District linkage – single


If a building has not been allocated a GAZETTED Suburb/Locality, the building will be

assessed against HUNDRED and DISTRICT boundaries. If a building’s area intersects with

more than one HUNDRED or DISTRICT, the building will be allocated to the HUNDRED or

DISTRICT that the majority of the building’s area falls within.

Building Hundred/District linkage - majority

Building Swimming Pool Adjacent

The BUILDING table’s SWIMMING_POOL_ADJACENT attribute will be assigned a ‘YES’ if a

building intersects, by more than 10% of the buildings area, a property that has been

identified as containing a swimming pool. If the building intersects, by more than 10% of a

building’s area, a property that has been identified as NOT containing a swimming pool the

SWIMMING_POOL_ADJACENT attribute will be assigned a ‘NO’. Where the building does not

intersect a property that has been assessed for a swimming pool or does not intersect by

more than 10% of the buildings area, the building will be assigned an ‘Unknown’.

Building Swimming Pool linkage - majority

Note: The property boundaries used are derived from multiple sources and may not align

with the property data in the PSMA CadLite product used in the linkage between a

building and a property.


Building Swimming Pool Linkage


A building to swimming pool relationship will be captured in the

BUILDING_SWIMMING_POOL table for every building that intersects, by more than 10% of

the buildings area, a property that has been identified as containing a swimming pool.

Building Swimming Pool linkage – single

Swimming Pool Address Linkage


An address to swimming pool relationship will be captured in the

SWIMMING_POOL_ADDRESS table for every valid address site geocode that falls within a

property that has been identified as containing a swimming pool.

Swimming Pool Address linkage

Note: The property boundaries used are derived from multiple sources and may not align

with the property data in the PSMA CadLite product used in the linkage between a

building and a property.

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),

• Only BC, PAPS, PC, FCS, EAS and PCM geocode types.

In the case of SA, where multiple geocodes are provided for a single address, address site

geocodes with the best relationship with the building are used.


Building Zone Linkage

The building/zone relationship captured in the BUILDING_ZONE table via a spatial

intersection between building feature geometries and the zoning polygon datasets supplied

from state, territory or local government after the generalised national zoning codes

developed by PSMA have been applied.

A building to zoning relationship will be created for every zone a building intersects by

greater than 10% of the building area.

Building Zone Linkage

Please refer to Classification Correctness under section 6.2 re Thematic Quality for more

detail about the Zone Code attribute.

7.1.3 Building Address Linkage

A linkage between the 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),

• Geocode types BC, PAPS, PC, FCS, EAS and PCM in ADDRESS_SITE_GEOCODE table.

Where the relationship between Building and an Address has been made using CAD

polygons, the cadastral parcels which meet the following criteria are matched first:

• Parcel Status of Registered

• Parcel Type of Lot Parcel, Strata (including Horizontal and Vertical, and Stratum)

Properties and cadastre parcels that were 10,000sqkm or above are not included in the

building address assignment process. The removal of these areas results in buildings in

these rural areas being assigned only address geocodes that fall directly inside the building

extent. Although this means there are fewer relationships made in these areas, the

relationships built are considered more reliable.

The ‘Base’ properties in Victoria have been removed prior to assigning building address

relationships due to a large number of building address relationships being made. This

prevents addresses that fall within complex sites from being assigned to all buildings that

are in the same property.

The process types use different geocode types and for the purposes of creating the

relationships between addresses and buildings, the geocode types have been placed into

three category types when explaining the process that is used. The three categories are

building, property and gap and their relationship to the geocode type from G-NAF are

shown in the following table.


Geocode Type Codes

Geocode Type Code Name Geocode Category

BC Building Centroid Building

PAPS Property Access Point Setback Property

PC Property Centroid Property

PCM Property Centroid Manual Property

FCS Frontage Centre Setback Property

GG Gap Geocode Gap

EAS Emergency Access Secondary Property

Some jurisdictions have multiple geocodes for an address, to reduce the effect these

additional geocodes have on relationships within Buildings and to ensure the most

applicable address site geocode is used the geocodes are filtered to ensure there was only

one geocode for any particular address. This filter orders the geocode types to obtain the

address likely to have the best relationship with a building. As different States/Territories

have different geocodes and ways of addressing, the following priority is applied:

ACT

1. BC (Building Centroid)

2. PC (Property Centroid)

3. FCS (Front Centre Setback)

4. PCM (Property Centroid Manual)

SA


2. PAPS (Property Access Point Setback)

3. EAS (Emergency Access Setback)

VIC


2. FCS (Front Centre Setback)

3. PAPS (Property Access Point Setback)

The below relationships outline the connection between an address default geocode and

buildings. In the case where multiple geocodes are provided for a single address, address

site geocodes with the best relationship with the building are used: The process types

listed below are located within the PROCESS_TYPE_AUT and are numbered in the order that

each of the rules are considered for making the connection between the address and the

building in the BUILDING_ADDRESS table.


Building Address Process Type 1 (BA01)

BUILDING polygon spatially contains exactly 1 building geocode ADDRESS feature. The

BUILDING is associated with the 1 ADDRESS feature.



BUILDING polygon spatially contains multiple building geocode ADDRESS features. The

BUILDING is associated with the multiple ADDRESS features.



BUILDING polygon spatially contains exactly 1 property geocode ADDRESS feature. The





BUILDING polygon spatially contains multiple properties geocode ADDRESS features. The

BUILDING is associated with the multiple ADDRESS features.



PROPERTY polygon contains or intersects greater than 80% with a single BUILDING

polygon feature and spatially contains exactly 1 property geocode ADDRESS feature. A

single BUILDING is associated with the 1 ADDRESS feature.




PROPERTY polygon contains or intersects greater than 80% with multiple BUILDING

polygon features and spatially contains exactly 1 property geocode ADDRESS feature.

Multiple BUILDINGS are associated with the 1 ADDRESS feature.



PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature

and spatially contains multiple properties geocode ADDRESS features. A single BUILDING is

associated with multiple ADDRESS features.




PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature

and spatially contains multiple properties geocode ADDRESS features. Multiple BUILDINGS

are associated with multiple ADDRESS features.



BUILDING polygon partially intersects a single PROPERTY polygon with 1 or more property

geocodes ADDRESS features. A BUILDING is associated with 1 or more ADDRESS features.




BUILDING polygon partially intersects multiple PROPERTY polygons with 1 or more property

geocode ADDRESS features. A BUILDING is associated with multiple ADDRESS features.



PROPERTY polygon spatially contains 1 or more building geocode ADDRESS features

allocated a BUILDING feature and 1 or more BUILDING polygons intersect PROPERTY

polygon not allocated ADDRESS. Multiple BUILDINGS associated with 1 or more ADDRESS

features.




ADDRESS has not been allocated a BUILDING. The BUILDING polygon area intersects by

more than 10% a single PROPERTY polygon with 1 or more ADDRESS features allocated a

BUILDING. A single BUILDING is associated with multiple ADDRESS features.



BUILDING not allocated an ADDRESS and BUILDING polygon spatially contain or intersects

PROPERTY polygon that has an ADDRESS within 15 metres and the closest PROPERTY to

the ADDRESS. A single BUILDING is associated with a single ADDRESS feature.




BUILDING not allocated ADDRESS and BUILDING polygon intersect with PROPERTY polygon

with the same PROPERTY_PID as PROPERTY polygon no more than 1km containing

ADDRESS feature. A single BUILDING is associated with 1 or more ADDRESS features.



BUILDING not allocated an ADDRESS and PROPERTY polygon intersect with BUILDING

polygon where PROPERTY polygon contains 1 or more gap geocode ADDRESS features. A

single BUILDING is associated with 1 or more ADDRESS features.




CAD polygon contains or intersects greater than 80% with a single BUILDING polygon

feature and spatially contains exactly 1 property geocode ADDRESS feature. A single




CAD polygon contains or intersects greater than 80% with multiple BUILDING polygon

features and spatially contains exactly 1 property geocode ADDRESS feature. Multiple

BUILDINGS are associated with the 1 ADDRESS feature.




CAD polygon contains or intersects greater than 80% with BUILDING polygon feature and

spatially contains multiple properties geocode ADDRESS features. A single BUILDING is




CAD polygon contains or intersects greater than 80% with BUILDING polygon feature and

spatially contains multiple properties geocode ADDRESS features. Multiple BUILDINGS are





BUILDING polygon partially intersects a single CAD polygon with 1 or more property

geocodes ADDRESS features. A BUILDING is associated with 1 or more ADDRESS features.



BUILDING polygon partially intersects multiple CAD polygons with 1 or more property

geocode ADDRESS features. A BUILDING is associated with multiple ADDRESS features.




CAD polygon spatially contains 1 or more building geocode ADDRESS features allocated a

BUILDING feature and 1 or more BUILDING polygons intersect CAD polygon not allocated

ADDRESS. Multiple BUILDINGS associated with 1 or more ADDRESS features.



ADDRESS has not been allocated a BUILDING. The BUILDING polygon area intersects by

more than 10% a single CAD polygon with 1 or more ADDRESS features allocated a

BUILDING. A single BUILDING is associated with multiple ADDRESS features.




BUILDING not allocated an ADDRESS and BUILDING polygon spatially contain or intersects

CAD polygon that has an ADDRESS within 15 metres and the closest CAD to the ADDRESS.

A single BUILDING is associated with a single ADDRESS feature.



BUILDING not allocated ADDRESS and BUILDING polygon intersect with CAD polygon with

same CAD_PID as CAD polygon no more than 1km containing ADDRESS feature. A single

BUILDING is associated with 1 or more ADDRESS features.




BUILDING not allocated an ADDRESS and CAD polygon intersect with BUILDING polygon

where CAD polygon contains 1 or more gap geocode ADDRESS features. A single BUILDING

is associated with 1 or more ADDRESS features.


Building CAD Linkage

A linkage between the 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

cadastral parcels meeting the following criteria being matched first:

• Parcel Status of Registered

• Parcel Type of Lot Parcel, Strata (including Horizontal and Vertical, and Stratum)

Any building not assigned will then be matched based on cadastral parcels that have the

following criteria:

• Parcel Status of Unregistered

• Parcel type of Lot Parcel, Strata (including Horizontal, Vertical and Stratum).

The below relationships outline the connection between the cadastre (CAD) and buildings

captured in the BUILDING_CAD table. The process types listed below are located within the

PROCESS_TYPE_AUT and are numbered in the order that each of the rules is considered for

making the connection between the cadastre (CAD) and the building.


Building CAD Process Type 1 (BC01)

The BUILDING polygon is completely contained by CAD polygon feature. The CAD feature is

associated with the BUILDING feature.



The BUILDING polygon completely contains CAD polygon feature. The CAD feature is

associated with one or more BUILDING features.




The BUILDING polygon has 80% or more spatial overlap of the buildings area with 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.




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

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

CAD polygon feature that also contains CAD point feature. The CAD feature is associated

with the BUILDING feature.



The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with

CAD polygon feature that also contains CAD point feature. The CAD feature is associated





The BUILDING polygon has a spatial overlap of the buildings area with CAD polygon feature

that has ‘NOT REGISTERED. The CAD feature is associated with the BUILDING feature.


7.1.4 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 and captured in the BUILDING_PROPERTY table.

Some States/Territories do not supply property points, therefore, no relationships will be

created for these States using the below relationship process types of 6, 7 or 8. The below

relationships outline the connections between property and buildings features. The process

types listed below are located within the PROCESS_TYPE_AUT and are numbered in the

order that each of the rules is considered for making the connection between the property

and the building.

Building Property Process Type 1 (BP01)

The BUILDING polygon is completely contained by non-proposed PROPERTY polygon

feature. The PROPERTY feature is associated with the BUILDING feature.




The BUILDING polygon completely contains PROPERTY polygon feature. The PROPERTY

feature is associated with one or more BUILDING features.



The BUILDING polygon has 80% or more spatial overlap of the buildings area with

PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING

feature.




The BUILDING polygon has a spatial overlap of less than 80% but 10% or more of the

buildings area with PROPERTY polygon feature. The PROPERTY feature is associated with

the BUILDING feature.




PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING

feature.




The BUILDING polygon completely contained by PROPERTY polygon feature that also

contains 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

PROPERTY polygon feature that also contains PROPERTY point feature. The PROPERTY

feature is associated with the BUILDING feature.

Building Property Process Type (BP07)



PROPERTY polygon feature that also contains PROPERTY point feature. The PROPERTY




8. Data Updates and Maintenance PSMA completed delivery of the national Buildings product in October 2018 and has since

commenced the update, maintenance and improvement program. More information on the

proposed update schedule is available from the Geoscape website.

8.1 Update Frequency Updates to Buildings are applied and released on a quarterly schedule.

8.2 Update Scope Buildings updates occurs for all existing objects with changed geometry, attributes and/or

metadata, as well as data for new objects supplied prior to the release time period.

Updates to the product include:

1. Feature level building change management:

a. Addition of newly captured buildings,

b. Retiring of non-identified buildings,

c. Validation of existing building geometry,

d. Updates to building geometry to improve real-world representation, and

e. Updates to building attribution: height, roof material, roof type.

2. The inclusion of any new capture of Buildings, Solar Panels, Swimming Pools,

Surface Cover, or Trees received from third-party partners for inclusion within

Buildings.

3. All Buildings relationships to other PSMA products (G-NAF, CadLite, and

Administrative Boundaries) to account for any changes in either product.

4. Corrections and/or improvements to production processes in generating Buildings.

Refer to Section 8.4 for details on the building change management process.


8.3 Update Rules The update process describes rules that are applied to records to determine persistency. A

record can be updated, retired or created.

The following table outlines the required attributes needed to be changed to cause a record

to be retired. For example, BUILDING_ROOF requires BUILDING_PID, ROOF_TYPE_CODE

and PRIMARY_ROOF_MATERIAL to change to retire a record.

Attributes Used For Persistency

Table Name Attributes Used For Persistency

BUILDING BUILDING_PID

BUILDING_POLYGON BUILDING_PID, GEOMETRY

BUILDING_POINT BUILDING_PID, GEOMETRY

BUILDING_ADDRESS BUILDING_PID, ADDRESS_DETAIL_PID, PROCESS_TYPE_CODE

BUILDING_PROPERTY BUILDING_PID, PROPERTY_PID, PROCESS_TYPE_CODE

BUILDING_CAD BUILDING_PID, CAD_PID, PROCESS_TYPE_CODE

HEIGHT_ABOVE_GROUND BUILDING_PID

ELEVATION BUILDING_PID, SOURCE_CODE, ELEVATION

BULDING_ZONE BUILDING_PID, ZONE_CODE

BUILDING_MESH_BLOCK BUILDING_PID, MESH_BLOCK_CODE

BUILDING_ROOF BUILDING_PID, PRIMARY_ROOF_MATERIAL, ROOF_TYPE_CODE

ROOF_MATERIAL BUILDING_ROOF_PID

BUILDING_TREE BUILDING_PID, MAX_TREE_HEIGHT

BUILDING_QUALITY BUILDING_GEOMETRY_PID, QUALITY_INDICATOR_CODE

BUILDING_ROOF_QUALITY BUILDING_GEOMETRY_PID, QUALITY_INDICATOR_CODE

SWIMMING_POOL SWIMMING_POOL_PID

BUILDING_SWIMMING_POOL BUILDING_PID, SWIMMING_POOL_PID

SWIMMING_POOL_ADDRESS SWIMMING_POOL_PID, ADDRESS_DETAIL_PID, PROCESS_TYPE_CODE

Create, Retire and Update Building, Building Polygon And Building Point Records

Refer to Section 8.4 for details on persistency for creating, retiring and updating buildings,

building polygons and building point records

Updating Building Locality

All BUILDING_POLYGON records from the previous version are compared with the specified

version of PSMA’s LOCALITY boundaries for a match with the corresponding BUILDING

record. Unmatched records will trigger modification to attributions LOCALITY_PID and the

DATE_LAST_MODIFIED in the BUILDING table.


Create, Retire and Update Building Address Relationships

All relationship types between a building and an address are compared to the previous

version:

• A building address relationship is retired if a BUILDING_PID has been retired or if there

are no matching BUILDING_PID and ADDRESS_DETAIL_PID records from the previous

version.

• A building address relationship is updated if a PROCESS_TYPE_CODE differs to a

matched BUILDING_PID and ADDRESS_DETAIL_PID record from the previous version.

The DATE_LAST_MODIFIED will also be updated to the date the record was modified.

• A building address relationship is created for all new building features.

In addition, all ADDRESS_COUNT values are updated for each BUILDING record linked to

the corresponding BUILDING_ADDRESS record/s. The DATE_LAST_MODIFIED attributes in

the BUILDING table are updated if counts differed to the previous version.

Create, Retire and Update Building Cad Relationships

All relationship types between a building and a CAD feature are compared to the previous

version:

• A building CAD relationship is retired if a BUILDING_PID has been retired or if there are

no matching BUILDING_PID and CAD_PID records from the previous version.

• A building CAD relationship is updated if a PROCESS_TYPE_CODE differs to a matched

BUILDING_PID and CAD_PID record to the previous version. The

DATE_LAST_MODIFIED will also be updated to the date the record was modified.

• A building CAD relationship is created for all new building features.

Create, Retire and Update Building Property Relationships

All relationship types between a building and a property feature are compared to the

previous version:

• A building property relationship is retired if a BUILDING_PID has been retired or if there

are no matching BUILDING_PID and PROPERTY_PID records from the previous version.

• A building property relationship is updated if a PROCESS_TYPE_CODE differs to a

matched BUILDING_PID and PROPERTY_PID record to the previous version. The

DATE_LAST_MODIFIED will also be updated to the date the record was modified.

• A building property relationship is created for all new building features.

Retire and Create Building Height Above Ground Record

A building and its height above ground record are compared to the previous version:

• A record is retired if a BUILDING_PID has been retired or if a BUILDING_PID and

HEIGHT_TYPE_CODE record differs from the previous version based on the

HEIGHT_TYPE_CODE.

• A record is created for all new buildings, or if a record has been retired due to a

differing HEIGHT and HEIGHT_TYPE_CODE record from the previous version.

Retire and Create Building Elevation Record

A building and elevation record are compared to the previous version:

• A record is retired if a BUILDING_PID has been retired or if a BUILDING_PID,

SOURCE_CODE and ELEVATION record differs from the previous version.

• A record is created for all new buildings, or if a record has been retired due to differing

ELEVATION and SOURCE_CODE record from the previous version.

Retire and Create Building Zone Record

A building and planning zone record is compared to the previous version:

• A building zone record is retired if a BUILDING_PID has been retired or if a

BUILDING_PID and ZONE_CODE record differs from the previous version.


• A building zone record is created for all new buildings, or if a record has been retired

due to differing BUILDING_PID and ZONE_CODE record from the previous version.

Retire and Create Building Roof Record

A building and roof record are compared to the previous version:

• A building roof record is retired if a BUILDING_PID has been retired or if a

BUILDING_PID, PRIMARY_ROOF_MATERIAL and ROOF_TYPE_CODE record differs from

the previous version.

• A building roof record is created for all new buildings, or if a record has been retired

due to differing BUILDING_PID, PRIMARY_ROOF_MATERIAL and ROOF_TYPE_CODE

record from the previous version.

Retire and Create Roof Material Record

A building and roof material record is compared to the previous version:

• A roof material record is retired if a BUILDING_ROOF_PID has been retired

• A roof material record is created for all new buildings and BUILDING_ROOF_PID

records.

Retire and Create Building Tree Relationship

A relationship between a building and tree pixel are compared to the previous version:

• A building tree relationship is retired if a BUILDING_PID has been retired or there is no

matching BUILDING_PID and MAX_TREE_HEIGHT record from the previous version.

• A building tree relationship is created for all new buildings that intersect a tree pixel, or

if a record has been retired due to differing BUILDING_PID and MAX_TREE_HEIGHT

record from the previous version.

Retire and Create Building Quality And Building Roof Quality Relationship

A building and its quality indicator code are compared to the previous version:

• A building quality record is retired if a BUILDING_GEOMETRY_PID has been retired.

• A building quality record is created if there is no matching record with the same

BUILDING_GEOMETRY_PID and QUALITY_INDICATOR_CODE from the previous version.

Create, Retire and Update Swimming Pool Address Relationships

All relationship types between a swimming pool and an address are compared to the

previous version:

• A swimming pool address relationship is retired if there are no matching

SWIMMING_POOL_PID and ADDRESS_DETAIL_PID record to the previous version.

• A building address relationship is updated if a PROCESS_TYPE_CODE differs to a

matched SWIMMING_POOL_PID and ADDRESS_DETAIL_PID record to the previous

version. The DATE_LAST_MODIFIED will also be updated to the date the record was

modified.

• A swimming pool address relationship is created for all new building features.

In addition, all ADDRESS_COUNT is updated for each BUILDING record linked to the

corresponding SWIMMING_POOL_ADDRESS record/s. The DATE_LAST_MODIFIED attributes

are updated if counts differed to the previous version.


8.4 Building Change Management The update phase of Buildings focuses on areas with a high degree of change in urban

areas, including central business districts and new residential development areas. For each

updated area, recently captured imagery is used to identify and extract all building features

in line with the original specifications.

Newly captured buildings are compared against existing features in Buildings to determine

if a footprint is new, an existing footprint no longer exists, or an existing footprint can be

better represented with confidence to increase fidelity and accuracy. The logic for several

change management scenarios is outlined in the sections below.

The following applies to all change management scenarios:

• Where a new BUILDING, BUILDNG_POLYGON and BUILDING_POINT record is created,

new related aspatial records are also created.

• Where an existing BUILDING, BUILDING_POLYGON and BUILDING_POINT record is

retired, all existing related aspatial records are also retired.

• Where an update will affect the geometry or topology of neighbouring

BUILDING_POLYGON records, the existing BUILDING, BUILDING_POLYGON and

BUILDING_POINT record is retained. The new BUILDING_POLYGON and

BUILDING_POINT record is not included in this update.

Adds and Retires

Add New Building

Where a new BUILDING_POLYGON record does not spatially intersect an existing

BUILDING_POLYGON record, a new BUILDING, BUILDING_POLYGON and BUILDING_POINT

record is created.

Add New Building ExamplesAdd New Building - Table Updates

BUILDING table

BUILDING_PID New

DATE_CREATED Date of processing for current update

BUILDING_POLYGON and BUILDING_POINT tables

BUILDING_POLYGON_PID, BUILDING_POINT_PID New


CAPTURE_DATE Date of imagery capture for current update


Retire Non-Identified Building

Where an existing BUILDING_POLYGON record does not spatially intersect with any newly

captured BUILDING_POLYGON records, the existing BUILDING, BUILDING_POLYGON and

BUILDING_POINT record is retired. Retired records are not supplied as part of Buildings.

Retire non-identified building examples

Building Representation Updates

The development of the building change management logic is an evolving process. The

current focus for updating buildings is to provide the most correct representation available.

New features will be included where there is confidence that the new representation will

improve the existing representation of a building. Where there is less confidence, the

current logic will retain the existing features in the product as the more correct

representation. As the change management process and logic continues to evolve, both

retired features and new features not included in the current update will be reassessed and

processed and may be included in future Buildings updates.

Single Building Update

Where a new BUILDING_POLYGON record is similar or matches the existing representation

of a single existing, intersecting BUILDING_POLYGON record, the existing BUILDING record

is retained. The existing BUILDING_POLYGON and BUILDING_POINT record is retired, and

the new BUILDING_POLYGON and BUILDING_POINT record is created. Retired records are

not supplied as part of Buildings.


Example of single building features updated

Example of single building updates affecting topology.

The new BUILDING_POLYGON record for ‘Building A’ affects the topology (overlap) of the

BUILDING_POLYGON records for ‘Building B’. In this case, the existing

BUILDING_POLYGON records for both ‘Building A’ and ‘Building B’ are retained and the

new BUILDING_POLYGON records are not included in this update.

Where a new BUILDING_POLYGON record provides a significantly different representation

of a single existing, intersecting BUILDING_POLYGON record, there is currently a low

confidence in assigning the correct representation. The current logic will retain the existing

BUILDING, BUILDING_POLYGON and BUILDING_POINT records. The new

BUILDING_POLYGON and BUILDING_POINT record is not included in this update. These

records may be included in future updates as the change management process evolves.


Example of retaining single existing buildings because of lower confidence in new

representation

Single building feature updated – table updates

BUILDING table

BUILDING_PID Retain existing

DATE_CREATED Retain existing

DATE_LAST_MODIFIED Date of processing for current update


BUILDING_POLYGON_PID, BUILDING_POINT_PID New



Single building feature retained – table updates

BUILDING table



DATE_LAST_MODIFIED NULL


BUILDING_POLYGON_PID, BUILDING_POINT_PID Retain existing



CAPTURE_DATE Retain existing


Single Building to Multiple Buildings

Where the existing representation of connected real-world buildings is a single

BUILDING_POLYGON record, and the new representation splits the building into multiple

BUILDING_POLYGON records representing the connected components, the existing

BUILDING, BUILDING_POLYGON and BUILDING_POINT record is retired. Multiple new

BUILDING, BUILDING_POLYGON and BUILDING_POINT records created. Retired records are

not supplied as part of Buildings.

Example of single building to multiple buildings update

Example of single building to multiple buildings update affecting topology

One of the new BUILDING_POLYGON records for ‘Building B’ affects the topology (causes

an overlap) with the BUILDING_POLYGON record for ‘Building C’. As all new

BUILDING_POLYGON record geometries for ‘Building B’ are adjacent (share a common

boundary), the exclusion of any record will affect the representation of the building. In

this case, the existing BUILDING_POLYGON records for both ‘Building B’ and ‘Building C’

are retained and all new BUILDING_POLYGON records are not included in this update.


Single building to multiple building – table updates

BUILDING table

BUILDING_PID Multiple new



BUILDING_POLYGON_PID, BUILDING_POINT_PID Multiple new



Multiple Buildings to Single Building

Where the existing representation of a building includes multiple BUILDING_POLYGON

records, and the new representation provides a single BUILDING_POLYGON record, there is

currently a low confidence in assigning the correct representation. The current logic will

retain the existing BUILDING, BUILDING_POLYGON and BUILDING_POINT records. The new

BUILDING, BUILDING_POLYGON and BUILDING_POINT record is not included in this

update. These records may be included in future updates as the change management

process evolves.

Example of retaining multiple buildings because of lower confidence in new

representation

Multiple buildings to single building – table updates

BUILDING table





BUILDING_POLYGON_PID, BUILDING_POINT_PID Retain existing



CAPTURE_DATE Retain existing


9. Delivery Format

9.1 Components The Buildings product will include vector components. The following table identifies what

components will be delivered in vector formats as well as the file format options available

for each component. The data is separated into each State and Territory, with the

exception that ACT and NSW are combined. Also, ACT/NSW includes Jervis Bay Territory

raster data. OT includes all Jervis Bay Territory vector data used for ACT/NSW but only for

the Jervis Bay Territory area.

Vector and aspatial data will be made available using only the Shape, MapInfo TAB and File

Geodatabase formats described below.

Supplied formats

Vector Formats

Theme ESRI Shapefile MapInfo TAB File Geodatabase

Buildings X X* X

*Z values not included in BUILDING_POLYGON data

9.1.1 MapInfo TAB

Format Name

TAB – MapInfo Professional™

Specification

This format includes files with the following extensions: *.tab, *.dat, *.id, *.map

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. TAB files support geospatial standards such as Open GIS, the OGC, ISO, W3C and

others.

Language

English

9.1.2 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


9.1.3 File Geodatabase

Format name

File Geodatabase – ESRI™

Specification

This format includes files with the following extensions: *.gdb

ESRI File Geodatabase Technical Description. Follow this link:

http://desktop.arcgis.com/en/desktop/latest/manage-data/administer-file-gdbs/file-

geodatabases.htm

Language

English


10. PSMA Partner Network The value of PSMA’s products is in the richness of the partner networks who have specialist

skills and knowledge to provide business-ready solutions. Our network includes traditional

geospatial specialists, data engineers, software developers, marketing service providers,

system integrator, independent software vendors, research organisations and

consultancies.

Contact us to provide feedback on the Buildings product or for further information on

accessing PSMA Data:

PSMA Australia Limited

Unit 6, 113 Canberra Avenue, Griffith ACT 2603

T: 02 6260 9000

E: [email protected]

W: www.psma.com.au

http://www.psma.com.au/


11. PSMA Data Products

DATASET ACCESS THEME LAYER

Administrative Boundaries

Open Data (www.data.gov.au)

PSMA Partner Network

ABS Boundaries 2011

2011 ABS Mesh Blocks

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)

ABS Boundaries 2016

2016 ABS Mesh Blocks and Statistical Areas

2016 ABS Indigenous Regions, Areas and Locations

2016 Urban Centre and Locality - Section of State - Significant Urban Area

2016 Remoteness Areas (RA)

2016 Socio-Economic Indexes for Areas (SEIFA)

Electoral Boundaries

Commonwealth Electoral Boundaries

State Electoral Boundaries

Local Government Areas (LGAs)

Suburbs/Localities

State Boundaries

Town Points

Wards

CadLite PSMA Partner Network Cadastre

Property

Surface Cover PSMA Partner Network Buildings

Surface Cover 2 Metres

30 Metres

Buildings PSMA Partner Network Buildings

Trees PSMA Partner Network Trees

G-NAF Open Data (www.data.gov.au)

Geocoded physical addresses

PSMA Partner Network

Land Tenure PSMA Partner Network Land Tenure

Features of Interest PSMA Partner Network Features of Interest

Postcodes PSMA Partner Network Postcode Boundaries

Transport & Topography

PSMA Partner Network Transport Roads

Rail

Rail Stations

Airports

Hydrology

Greenspace

http://www.data.gov.au/


Appendix A –Buildings Data Model

Linkages with PSMA other data products


Buildings Data Model


Appendix B – Data Dictionary The following table refers to the columns used in all tables that form part of the data dictionary, with the exception of tables for the

authority code tables.

Table 1: Data Columns

Column Abbreviation Description

Name Name The name of the column in the Integrated Database (UPPERCASE).

Data Type Data type The data type of the column based on the types defined in ISO 19103:2015. Parentheses capture Scale, Precision and Maximum Length, where applicable.

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 a * 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. The name will be UPPERCASE.

Table 2: BUILDING

Name Data Type Description Prim Key Man F K TABLE F K Col 10 Char Alias

BUILDING_PID CharacterString (16) The persistent identifier is unique to the building 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

QUALITY_CLASS_CODE CharacterString (4) The quality class is based on the coverage of the building when processing the data (e.g. Urban, Rural or Remote).

N N QUALITY_CLASS_AUT

CODE QUAL_CL_CD

LOCALITY_PID CharacterString (15) The persistent identifier for the Suburb or Locality*.

N N LOCALITY* LOCALITY_PID LOC_PID

STATE_PID CharacterString (15) The persistent identifier for the State or Territory*.

N Y STATE* STATE_PID 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

HAS_SWIMMING_POOL_ ADJACENT

CharacterString (4) A code allocated based on if a swimming pool has been identified to be more than 10% within a boundary associated with the building.

N N SWIMMING_POOL_ADJACENT_AUT

CODE HAS_SP_ADJ

SWIMMING_POOL_REVIEW_DATE

Date The date of the last assessment of the HAS_SWIMMING_POOL_ADJACENT attribute.

N N - - SWMP_REVDT

HAS_SOLAR_PANEL CharacterString (4) A code allocated based on if a visible solar panel is identified for the building.

N N SOLAR_PANEL_AUT CODE SOLAR_P

SOLAR_PANEL_REVIEW_ DATE

Date The date of the last assessment of the HAS_SOLAR_PANEL attribute.

N N - - SOLP_REVDT

*LOCALITY and STATE tables are NOT in the Buildings product, they are located in PSMA’s Administrative Boundaries

product.

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_SITE_GEOCODE.GEOCODE_TYPE_CODE not having a value of ‘UNK’ (unknown), ‘LOC’ (locali ty)

or ‘STL’ (street locality).


BUILDING_ADDRESS_PID CharacterString (16) This is the unique persistent identifier for each building address relationship.

Y Y - - BLD_AD_PID

BUILDING_PID CharacterString (16) The persistent identifier is unique to the building feature this record represents.

N Y BUILDING BUILDING_PID BLD_PID



N N - - DT_LT_MOD


ADDRESS_DETAIL_PID CharacterString (15) This is the unique persistent identifier for each ADDRESS_DETAIL record*.

N Y ADDRESS_DETAIL* ADDRESS_DETAIL_PID

ADD_DT_PID

PROCESS_TYPE_CODE CharacterString (4) Processing value indicating the reliability of association between the building and an address.

N Y PROCESS_TYPE_AUT

CODE PROC_TYPE



HAS_RESIDENTIAL CharacterString (1) A value of Y allocated where address information has identified the land use as residential.

N N - - HAS_RESI

*ADDRESS_DETAIL table is not included in this product, it is available in PSMA’s G-NAF product.

Table 4: BUILDING_CAD

The CAD_POLYGON_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). Any BUILDING not assigned

will be joined based on having CAD.PARCEL_STATUS of ‘2’ (unregistered), PARCEL_TYPE having a value of either ‘1’ (Lot Parcel), ‘2’

(Strata), ‘201’ (Horizontal Strata), ‘202’ (Vertical Strata) or 3 (Stratum). The CAD_PID is derived from the CAD_POLYGON_PID.


BUILDING_CAD_PID CharacterString (16)

This is the unique persistent identifier for each building cad relationship.

Y Y - - BLD_CD_PID

BUILDING_PID CharacterString (16)

The persistent identifier is unique to the building feature that this record represents.




N N - - DT_LT_MOD


PROCESS_TYPE_CODE CharacterString (4) Processing value indicating the reliability of association between the building and a cad record.

N Y PROCESS_TYPE_AUT CODE PROC_TYPE

CAD_PID CharacterString (15)

This is the unique persistent identifier for each CAD record*.

N Y CAD* CAD_PID CAD_PID

* CAD table is not included in this product. It is available in the CadLite product.

Table 5: BUILDING_MESH_BLOCK


BUILDING_MESH_BLOCK _PID

CharacterString (16)

The unique persistent identifier for each building mesh block relationship.

Y Y - - BLD_MB_PID








MESH_BLOCK_VERSION CharacterString (6) The year of release and version of mesh block code attributed to a building.

N Y MESH_BLOCK_RELEASE _AUT

CODE MB_VERS

MESH_BLOCK_CODE CharacterString (15)

The ABS mesh block code assigned to a building. N Y - - MB_CODE

Table 6: BUILDING_POINT


BUILDING_POINT_PID CharacterString (16)

The unique persistent identifier for each building point feature.

Y Y - - BLD_PT_PID


The persistent identifier is unique to the building feature this record represents.




N N - - DT_LT_MOD


CAPTURE_DATE Date The date the source data was taken from which the feature has been derived.

N N - - CAPT_DATE

GEOMETRY Vector Point geometry. N Y - - GEOMETRY

Table 7: BUILDING_POLYGON


BUILDING_POLYGON _PID


The unique persistent identifier for each building polygon feature.

Y Y - - BLD_PG_PID






N N - - DT_LT_MOD



N N - - CAPT_DATE

NUMBER_VERTICES Integer (5) The number of vertices comprising the polygon, this will return the start and end of each ring as separate

N Y - - NUMB_VERT



vertices. For distinct/unique vertex count subtract 1 from this value.

AREA Decimal (10,2) The area of the building geometry in square metres calculated in Albers projection.

N Y - - AREA

GEOMETRY Vector Polygon geometry*. N Y - - GEOMETRY

*The BUILDING_POLYGON geometry for Shape and File Geodatabase formats also contain a Z coordinate that ties the geometry to the ground surface, this is in addition to capturing the X and Y coordinate vertices.

Table 8: BUILDING_PROPERTY

PROPERTY records are joined to BUILDING using the property polygon and are used to derive the PROPERTY_PID.

Name Data Type Description Prim Key

Man F K TABLE F K Col 10 Char Alias

BUILDING_PROPERTY_ PID


This is the unique persistent identifier for each building property relationship.

Y Y - - BLD_PR_PID






N N - - DT_LT_MOD


PROCESS_TYPE_CODE CharacterString (4)

Processing value indicating the reliability of association between the building and a property record

N Y PROCESS_TYPE_AUT CODE PROC_TYPE

PROPERTY_PID CharacterString (15)

This is the unique persistent identifier for each Property record.

N Y PROPERTY* PROPERTY_PID PR_PID

* PROPERTY table is not included in this product. It is available in the CadLite product.

Table 9: BUILDING_QUALITY


BUILDING_QUALITY_PID


This is the unique persistent identifier for each quality indicator associated with the building geometry.

Y Y - - BLD_QY_PID

BUILDING_GEOMETRY _PID


The persistent identifier is unique to the building geometry feature that this record represents.

N Y BUILDING_POINT

BUILDING_POLYGON

BUILDING _POINT_PID

BLD_GY_PID



BUILDING_ POLYGON_ PID



QUALITY_INDICATOR_ CODE

CharacterString (4) Description of known data quality issue. N Y QUALITY_INDICATOR _AUT

CODE QUAL_IND

Table 10: BUILDING_ROOF


BUILDING_ROOF_PID CharacterString (16)

This is the unique persistent identifier for each building roof relationship.

Y Y - - BLD_RF_PID






N N - - DT_LT_MOD



N N - - CAPT_DATE

PRIMARY_ROOF_ MATERIAL_CODE

CharacterString (4) Identifies the likely dominant roof surface material N Y ROOF_MATERIAL_AUT CODE PRF_MAT_CD

ROOF_TYPE_CODE CharacterString (4) Identifies if a roof is of a complex or steep shape. N Y ROOF_TYPE_AUT CODE RF_TYP_CD

Table 11: BUILDING_ROOF_QUALITY


BUILDING_ROOF_ QUALITY_PID


This is the unique persistent identifier for each quality indicator associated with the building roof.

Y Y - - BLD_RQ_PID

BUILDING_ROOF_PID CharacterString (16)

The persistent identifier is unique to the building roof feature that this record represents.

N Y BUILDING_ROOF BUILDING _ROOF_PID

BLD_RF_PID



QUALITY_INDICATOR_ CODE

CharacterString (4) Description of known data quality issue. N Y QUALITY_INDICATOR _AUT

CODE QUAL_IND


Table 12: BUILDING_SWIMMING_POOL


BUILDING_SWIMMING_ POOL_PID


The unique persistent identifier for each building swimming pool relationship.

Y Y - - BLD_SP_PID






SWIMMING_POOL_PID CharacterString (16)

The unique persistent identifier for each building swimming pool.

N Y SWIMMING_POOL - SP_PID

Table 13: BUILDING_TREE


BUILDING_TREE_PID CharacterString (16)

This is the unique identifier for each building tree feature.

Y Y - - BLD_TR_PID


The persistent unique identifier to the building feature that this record represents.




MAX_TREE_HEIGHT Decimal (7,2) The maximum height of all trees intersecting with the building.

N Y - - TREE_HGT

Table 14: BUILDING_ZONE


BUILDING_ZONE_PID CharacterString (16)

This is the unique persistent identifier for each building zone relationship.

Y Y - - BLD_ZN_PID






ZONE_CODE CharacterString (4) A code relating to identifying the zone that the building relates to.

N Y ZONE_AUT CODE ZONE_CODE


Table 15: ELEVATION


ELEVATION_PID CharacterString (16)

This is the unique persistent identifier for each elevation feature.

Y Y - - ELEV_PID






CAPTURE_DATE Date Where available, the date the source data was taken from which the feature has been derived.

N N - - CAPT_DATE

ELEVATION Decimal (7,2) The elevation in metres on the Australian Height Datum (AHD).

N Y - - ELEV

ELEVATION_TYPE _CODE

CharacterString (4) The type of elevation being measured (e.g. building elevation).

N Y ELEVATION_TYPE _AUT

CODE ELEV_TY_CD

SOURCE_CODE CharacterString (4) Source for calculating elevation values. N Y SOURCE_AUT CODE SOURCE_CD

Table 16: ELEVATION_TYPE_AUT


CODE CharacterString (4) Code identifying unique elevation types. Y Y - - CODE

NAME CharacterString (50) Name of the elevation type. N Y - - NAME

DESCRIPTION CharacterString (254)

Description of the elevation type. N N - - DESCRIPTN

Table 17: ELEVATION_TYPE_AUT codes

CODE NAME DESCRIPTION

BC Building Ground Centroid

The ground surface height at the building centroid in metres above the Australian Height Datum (AHD). The centroid is the BUI LDING POINT and is calculated as the geometric centroid of the building polygon and within the bounds of the polygon.

Table 18: HEIGHT_ABOVE_GROUND


HEIGHT_PID CharacterString (16) The persistent identifier is unique to the real-world feature that this record represents.

Y Y - - HEIGHT_PID



BUILDING_PID CharacterString (16) The persistent identifier is unique to the building feature that this record represents.




CAPTURE_DATE Date Where available, the date the source data was taken from which the feature has been derived.

N N - - CAPT_DATE

HEIGHT Decimal (7,2) The height measured in metres. N Y - - HEIGHT

HEIGHT_TYPE_CODE CharacterString (4) The type of height being measured (e.g. maximum roof height, eave height)

N Y HEIGHT_TYPE_AUT CODE HEIGHT_CD

SOURCE_CODE CharacterString (4) Source for calculating height values. N Y SOURCE_AUT CODE SOURCE_CD

Table 19: HEIGHT_TYPE_AUT


CODE CharacterString (4) Code identifying unique height types. Y Y - - CODE

NAME CharacterString (50) Name of the height type. N Y - - NAME


Description of the height type. N N - - DESCRIPTN

Table 20: HEIGHT_TYPE_AUT codes


E1 Average Eave Height The average eave height is the relative height of the eave elevation to the ground elevation and is calculated by taking the median eave elevation minus the minimum ground elevation.

R1 Maximum Roof Height

The maximum roof height is the relative height of the roof elevation to the ground elevation and is calculated by taking the maximum roof elevation minus the minimum ground elevation.

Table 21: MESH_BLOCK_VERSION_AUT


CODE CharacterString (6) Code identifying the unique ABS mesh block version. Y Y - - CODE

NAME CharacterString (50) Name of the ABS mesh block version. N Y - - NAME


Description of the ABS mesh block version. N N - - DESCRIPTN


Table 22: MESH_BLOCK_VERSION_AUT Codes


201101 2011 ABS mesh blocks version 1 The 1st version release of the 2011 ABS mesh blocks.

201601 2016 ABS mesh blocks version 1 The 1st version release of the 2016 ABS mesh blocks.

Table 23: PROCESS_TYPE_AUT


CODE CharacterString (4) Code identifying unique process types. Y Y - - CODE

NAME CharacterString (50) Name of the process type. N Y - - NAME


Description of the process type. N N - - DESCRIPTN

Table 24: PROCESS_TYPE_AUT Codes


BA01 Building Address Process Type 1 BUILDING polygon spatially contains exactly 1 building geocode ADDRESS feature. The BUILDING is associated with the 1 ADDRESS feature.

BA02 Building Address Process Type 2 BUILDING polygon spatially contains multiple building geocode ADDRESS features. The BUILDING is associated with the multiple ADDRESS features.

BA03 Building Address Process Type 3 BUILDING polygon spatially contains exactly 1 property geocode ADDRESS feature. The BUILDING is associated with the 1 ADDRESS feature.

BA04 Building Address Process Type 4 BUILDING polygon spatially contains multiple properties geocode ADDRESS features. The BUILDING is associated with the multipl e ADDRESS features.

BA05 Building Address Process Type 5 PROPERTY polygon contains or intersects greater than 80% with a single BUILDING polygon feature and spatially contains exactl y 1 property geocode ADDRESS feature. A single BUILDING is associated with the 1 ADDRESS feature.

BA06 Building Address Process Type 6 PROPERTY polygon contains or intersects greater than 80% with multiple BUILDING polygon features and spatially contains exact ly 1 property geocode ADDRESS feature. Multiple BUILDINGS are associated with the 1 ADDRESS feature.

BA07 Building Address Process Type 7 PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple proper ties geocode ADDRESS features. A single BUILDING is associated with multiple ADDRESS features.

BA08 Building Address Process Type 8 PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple proper ties geocode ADDRESS features. Multiple BUILDINGS are associated with multiple ADDRESS features.

BA09 Building Address Process Type 9 BUILDING polygon partially intersects a single PROPERTY polygon with 1 or more property geocodes ADDRESS features. A BUILDING is associated with 1 or more ADDRESS features.

BA10 Building Address Process Type 10

BUILDING polygon partially intersects multiple PROPERTY polygons with 1 or more property geocode ADDRESS features. A BUILDING is associated with multiple ADDRESS features.


PROPERTY polygon spatially contains 1 or more building geocode ADDRESS features allocated a BUILDING feature and 1 or more BU ILDING polygons intersect PROPERTY polygon not allocated ADDRESS. Multiple BUILDINGS associated with 1 or more ADDRESS features.


ADDRESS has not been allocated a BUILDING. The BUILDING polygon area intersects by more than 10% a single PROPERTY polygon wi th 1 or more ADDRESS features allocated a BUILDING. A single BUILDING is associated with multi ple ADDRESS features.




BUILDING not allocated an ADDRESS and BUILDING polygon spatially contain or intersects PROPERTY polygon that has an ADDRESS w ithin 15 metres and the closest PROPERTY to the ADDRESS. A single BUILDING is associated with a single ADDRESS feature.


BUILDING not allocated ADDRESS and BUILDING polygon intersect with PROPERTY polygon with the same PROPERTY_PID as PROPERTY polygon no more than 1km containing ADDRESS feature. A single BUILDING is associated with 1 or more ADDRESS features.


BUILDING not allocated an ADDRESS and PROPERTY polygon intersect with BUILDING polygon where PROPERTY polygon contains 1 or m ore gap geocode ADDRESS features. A single BUILDING is associated with 1 or more ADDRESS features.


CAD polygon contains or intersects greater than 80% with a single BUILDING polygon feature and spatially contains exactly 1 p roperty geocode ADDRESS feature. A single BUILDING is associated with the 1 ADDRESS feature.


CAD polygon contains or intersects greater than 80% with multiple BUILDING polygon features and spatially contains exactly 1 property geocode ADDRESS feature. Multiple BUILDINGS are associated with the 1 ADDRESS feature.


CAD polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple propert ies geocode ADDRESS features. A single BUILDING is associated with multiple ADDRESS features.


CAD polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple propertie s geocode ADDRESS features. Multiple BUILDINGS are associated with multiple ADDRESS features.


BUILDING polygon partially intersects a single CAD polygon with 1 or more property geocodes ADDRESS features. A BUILDING is associated with 1 or more ADDRESS features.


BUILDING polygon partially intersects multiple CAD polygons with 1 or more property geocode ADDRESS features. A BUILDING is a ssociated with multiple ADDRESS features.


CAD polygon spatially contains 1 or more building geocode ADDRESS features allocated a BUILDING feature and 1 or more BUILDIN G polygons intersect CAD polygon not allocated ADDRESS. Multiple BUILDINGS associated with 1 or more ADDRESS features.


ADDRESS has not been allocated a BUILDING. The BUILDING polygon area intersects by more than 10% a single CAD polygon with 1 or more ADDRESS features allocated a BUILDING. A single BUILDING is associated with multiple ADDRESS features.


BUILDING not allocated an ADDRESS and BUILDING polygon spatially contain or intersects CAD polygon that has an ADDRESS within 15 metres and the closest CAD to the ADDRESS. A single BUILDING is associated with a single ADDRESS feature.


BUILDING not allocated ADDRESS and BUILDING polygon intersect with CAD polygon with same CAD_PID as CAD polygon no more than 1km containing ADDRESS feature. A single BUILDING is associated with 1 or more ADDRESS features.


BUILDING not allocated an ADDRESS and CAD polygon intersect with BUILDING polygon where CAD polygon contains 1 or more gap g eocode ADDRESS features. A single BUILDING is associated with 1 or more ADDRESS features.

BC01 Building CAD Process Type 1 The BUILDING polygon is completely contained by CAD polygon feature. The CAD feature is associated with the BUILDING feature.

BC02 Building CAD Process Type 2 The BUILDING polygon completely contains CAD polygon feature. The CAD feature is associated with one or more BUILDING feature s.

BC03 Building CAD Process Type 3 The BUILDING polygon has 80% or more spatial overlap of the buildings area with CAD polygon feature. The CAD feature is associated with the BUILDING feature.

BC04 Building CAD Process Type 4 The BUILDING polygon has a spatial overlap of less than 80% but 10% or more of the buildings area with CAD polygon feature. The CAD feature is associated with the BUILDING feature.

BC05 Building CAD Process Type 5 The BUILDING polygon has a spatial overlap of less than 10% of the buildings area with CAD polygon feature. The CAD feature i s associated with the BUILDING feature.



BC06 Building CAD Process Type 6 The BUILDING polygon is completely contained by a CAD polygon feature that also contains CAD point feature. The CAD feature i s associated with the BUILDING feature.

BC07 Building CAD Process Type 7 The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with CAD polygon feature that also contains CAD p oint feature. The CAD feature is associated with the BUILDING feature.

BC08 Building CAD Process Type 8 The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with CAD polygon feature that also contains CAD point feature. The CAD feature is associated with the BUILDING feature.

BC09 Building CAD Process Type 9 The BUILDING polygon has a spatial overlap with ‘NOT REGISTERED’ CAD polygon feature.

BP01 Building Property Process Type 1

The BUILDING polygon is completely contained by non-proposed PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.


The BUILDING polygon completely contains PROPERTY polygon feature. The PROPERTY feature is associated with one or more BUILDI NG features.


The BUILDING polygon has 80% or more spatial overlap of the buildings area with PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.


The BUILDING polygon has a spatial overlap of less than 80% but 10% or more of the buildings area with 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 PROPERTY polygon feature. The PROPERTY feature is associated with the BUILDING feature.


The BUILDING polygon completely contained by PROPERTY polygon feature that also contains 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 PROPERTY polygon feature that also con tains PROPERTY point feature. The PROPERTY feature is associated with the BUILDING feature.


The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with PROPERTY polygon feature that also con tains PROPERTY point feature. The PROPERTY feature is associated with the BUILDING feature.

Table 25: QUALITY_CLASS_AUT


CODE CharacterString (4) Code identifying unique quality class types. Y Y - - CODE

NAME CharacterString (50) Name of the quality class type. N Y - - NAME


Description of the quality class type. N N - - DESCRIPTN

Table 26: QUALITY_CLASS_AUT codes


1 Urban Areas with a population greater than 200 or with significant industrial/commercial activity in a visual assessment with no known cultural or accessibility sensitivities.



2 Rural Balance All other areas not defined as Urban or Remote Communities.

3 Remote Communities Areas with a population greater than 200 or with significant industrial/commercial activity in a visual assessment with known cultural or accessibility sensitivities.

Table 27: QUALITY_INDICATOR_AUT


CODE CharacterString (4) Code identifying unique quality indicator. Y Y - - CODE

NAME CharacterString (50) Name of the cleansing activity performed on the feature.

N Y - - NAME


Description of the cleansing activity performed on the feature.

N N - - DESCRIPTN

Table 28: QUALITY_INDICATOR_AUT Codes


IC Invalid CAD Polygon A relationship between the building geometry and the CAD polygon was unable to be made due to invalid geometries.

IP Invalid Property Polygon A relationship between the building geometry and the property polygon was unable to be made due to invalid geometries.

IR Inner Rings Small inner ring/s less than 9 square metres that have been removed.

NE No Ground Centroid Elevation

A building that does not intersect a source of ground elevation and will have no ground centroid elevation and each vertex wi ll have a z value of 0.

O Overlap A section of the feature may overlap another feature.

OR Overlap Removed A section of the feature that has been removed due to an overlap with another feature.

RH Remediated Height A building in a high density and or high-rise area that has been reviewed and remediated to improve source ground elevations. The Roof Height and Eave Height have been altered.

S Split Complex Polygon A complex polygon that has been split into multiple simple parts.

SB Small Building A building that has a total area of fewer than 9 metres squared.

SI Self-Intersection Vertices of the polygon self-intersect.

SR Spike Removed A feature with geometry that has an identified 'spike' has been altered to remove the portion of the geometry containing the spike.

URF Unknown Roof Material A building roof material reclassified to another identified roof material.

VSR Varying State Relationship A building that has relationships to Localities or Mesh Blocks in another State / Territory.


Table 29: ROOF_MATERIAL



ROOF_MATERIAL_PID CharacterString (16) This is the unique persistent identifier for each roof material feature.

Y Y - - RF_MAT_PID

BUILDING_ROOF_PID CharacterString (16) The persistent identifier is unique to the building roof feature that this record represents.

N Y BUILDING_ROOF BUILDING_ROOF _PID

BLD_RF_PID



CAPTURE_DATE Date The date when the source data was taken from which the feature has been derived.

N N - - CAPT_DATE

ROOF_MATERIAL_CODE CharacterString (4) The code that reflects the most likely roof surface material.

N Y ROOF_MATERIAL_AUT CODE RF_MAT_CD

Table 30: ROOF_MATERIAL_AUT


CODE CharacterString (4) Code identifying unique roof types codes Y Y - - CODE

NAME CharacterString (50) Name of each roof type. N Y - - NAME


Description of the roof type. N N - - DESCRIPTN

Table 31: ROOF_MATERIAL_AUT Codes


0 Unknown The building has not been assessed for roof material and therefore the roof material is not known. Default value.

1 Unclassified The roof system constructed from a material that does not belong to a known class/type.

2 Metal A roofing system constructed 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 local materials such as terracotta or slate.

4 Fiberglass/Plastic A roofing system constructed 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.

Table 32: ROOF_TYPE_AUT


CODE CharacterString (4) Code identifying unique roof shape type codes. Y Y - - CODE



NAME CharacterString (50) Name of each roof shape type. N Y - - NAME


Description of the roof shape type. N N - - DESCRIPTN

Table 33: ROOF_TYPE_AUT Codes


0 Unknown The roof geometry of the building is not known. Default value.

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 com plex.

3 Steep pitch or high complexity

The roof geometry of the building has been identified as being pitched and/or varied.

Table 34: SOLAR_PANEL_AUT


CODE CharacterString (4) A code identifying unique solar panel codes. Y Y - - CODE

NAME CharacterString (50) Name of the solar panel type. N Y - - NAME


Description of the solar panel type. N N - - DESCRIPTN

Table 35: SOLAR_PANEL_AUT Codes


0 Unknown The building has not been assessed and therefore is not known if the building has solar panels or not. Default value.

1 Yes The building has been identified as having solar panels.

2 No The building has been identified as not having solar panels.

3 Unclassified The building could not be determined as either having or not having solar panels.

Table 36: SOURCE_AUT


CODE CharacterString (4) Code identifying unique source codes. Y Y - - CODE

NAME CharacterString (50) Name of the source type. N Y - - NAME




Description of the source type. N N - - DESCRIPTN

Table 37: SOURCE_AUT Codes


0 1 Second SRTM Hydro (DEM-H) Version 1.0

DEM representing hydro enforced smoothed ground surface topography derived from SRTM data acquired by NASA in Feb 2000. Full metadata http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_72759

1 ACT 5m DEM GA produced 5 metre (bare earth) DEM which has been derived from ACT LIDAR survey 2015-2016.

2 NSW 25m DEM (z55) NSW Spatial Services produced, NSW DTDB Landform Theme 50 k x 50 k Digital Terrain Models is a data series of 25m grid large-scale Digital Terrain Models for NSW.

3 SA State 5m DEM Mosaic GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

4 0.5m Digital Surface Model DigitalGlobe produced DSM derived from high-quality satellite imagery.

5 NSW State 5m DEM Mosaic

GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

6 QLD State 5m DEM Mosaic GA produced national 5 meters (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

7 NSW 25m DEM (z56) NSW Spatial Services produced, NSW DTDB Landform Theme 50 k x 50 k Digital Terrain Models is a data series of 25m grid large -scale Digital Terrain Models for NSW.

8 NT State 5m DEM Mosaic GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

9 TAS State 5m DEM Mosaic GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

10 VIC State 5m DEM Mosaic GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

11 WA State 5m DEM Mosaic GA produced national 5 metre (bare earth) DEM which has been derived from LIDAR surveys between 2001 and 2015. Metadata http://pid.geoscience.gov.au/dataset/ga/89644

12 VIC State 10m DEM Mosaic

VIC DELWP 10m DTM constructed from source data of various resolutions, accuracies and ages. Metadata http://services.land.vic.gov.au/catalogue/metadata?anzlicId=ANZVI0803003582&publicId=guest&extractionProviderId=3

13 VIC State 20m DEM Mosaic

VIC DELWP 20m DTM constructed from source data of various resolutions, accuracies and ages. Metadata http://services.land.vic.gov.au/catalogue/metadata?anzlicId=ANZVI0803003584&publicId=guest&extractionProviderId=3

14 NSW State 1m DEM Mosaic

NSW Spatial Services 1m metre Digital Elevation Models (DEM) produced using TIN (Triangular Irregular Network) method of aver aging ground heights to formulate a regular grid. Derived from C3 LiDAR (Light Detection and Ranging) from an ALS50ii (Airborne Laser Scanner).

15 0.5m Aerial derived DSM Digital Surface model resampled from stereo derived aerial imagery

http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_72759

http://pid.geoscience.gov.au/dataset/ga/89644







http://services.land.vic.gov.au/catalogue/metadata?anzlicId=ANZVI0803003582&publicId=guest&extractionProviderId=3

http://services.land.vic.gov.au/catalogue/metadata?anzlicId=ANZVI0803003584&publicId=guest&extractionProviderId=3


Table 38: SWIMMING_POOL


SWIMMING_POOL_PID CharacterString (16) This is the unique persistent identifier for each swimming pool.

Y Y - - SP_PID


DATE_LAST_MODIFIED Date Date the record was last modified. N N - - DT_LT_MOD


ADDRESS_COUNT Integer (5) The count of addresses associated with the swimming pool.

N Y - - ADD_COUNT

SWIMMING_POOL_ REVIEW_DATE

Date The date of the last assessment of the swimming pool attribute.

N N - - SWMP_REVDT

Table 39: SWIMMING_POOL_ADDRESS



SWIMMING_POOL_ ADDRESS_PID

CharacterString (16) This is the unique persistent identifier for each swimming pool address relationship.

Y Y - - SP_AD_PID

SWIMMING_POOL_PID CharacterString (16) This is the unique persistent identifier for each instance of the swimming pool site.

N Y - - SP_PID



ADDRESS_DETAIL_PID CharacterString (15) ADDRESS_DETAIL persistent Identifier. N Y ADDRESS_DETAIL* ADDRESS_DETAIL _PID

ADD_DT_PID

* ADDRESS_DETAIL table is not included in this product. It is available in G-NAF.

Table 40: SWIMMING_POOL_ADJACENT_AUT


CODE CharacterString (4) Code identifying unique swimming pool adjacent codes. Y Y - - CODE

NAME CharacterString (50) Name of the swimming pool adjacent type. N Y - - NAME


Description of the swimming pool adjacent type. N N - - DESCRIPTN


Table 41: SWIMMING_POOL_ADJACENT_AUT Codes


0 Unknown The building has not been assessed and therefore it is not known if the building has a swimming pool adjacent or not. Default value.

1 Yes The building has been identified as having a swimming pool adjacent.

2 No The building has been identified as not having a swimming pool adjacent.

3 Unclassified The building could not be determined as either having or not having a swimming pool adjacent.

Table 42: ZONE_AUT


CODE CharacterString (4) Code identifying unique zone codes. Y Y - - CODE

NAME CharacterString (50) Name of the zone type. N Y - - NAME


Description of the zone type. N N - - DESCRIPTN

Note: Please refer to section 6.2 regarding Thematic Quality for further information about the reliability of the Zone Code attribute

Table 43: ZONE_AUT Codes


0 Unknown Areas where the planning zone is not known.

1 Commercial/Business Areas where the state, territory or local government planning scheme generally indicate a commercial or business focus.

2 Community Use Areas where the state, territory or local government planning scheme generally indicate community use.

3 Conservation/National Park Areas where the state, territory or local government planning scheme generally indicate National Park or a conservation requirement.

4 Industrial/Utilities Areas where the state, territory or local government planning scheme generally indicate industrial activities and/or utility facilities.

5 Mixed Use Areas where the state, territory or local government planning scheme generally indicate mixed use.

6 Recreational/Open Space Areas where the state, territory or local government planning scheme generally indicate recreational activities and or open space.

7 Residential Areas where the state, territory or local government planning scheme generally indicate residentially.

8 Rural/Primary Production Areas where the state, territory or local government planning scheme generally indicate rural and/or primary production activities.

9 Special Use Areas where the state, territory or local government planning scheme generally indicate special use.

10 Transport/Infrastructure Areas where the state, territory or local government planning scheme generally indicate transport and/or other infrastructure.

11 Water Areas where the state, territory or local government planning scheme generally indicate waterways or other water areas.


Note: Please refer to section 6.2 regarding Thematic Quality for further information about the reliability of the Zone Code attribute


Appendix C - Building Address Process Type Examples The following list of examples shows data demonstrating each of the process types used for making a linkage between buildings and

addresses. Each diagram shows address points (labelled with geocode types: BC = Building Centroid, PAPS = Property Access Point

Setback, PC = Property Centroid, PCM = Property centroid Manual, FCS = Frontage Centre Setback, GG = Gap Geocode, EAS =

Emergency Access Secondary), building polygons and property polygons (red boundaries).

1. Building Address Process Type 1 (BA01) BUILDING polygon spatially contains exactly 1 building geocode ADDRESS feature. The BUILDING is associated with the 1 ADDRESS

feature.

Building Address Process Type 1 examples (BA01)


2. Building Address Process Type 2 (BA02) BUILDING polygon spatially contains multiple building geocode ADDRESS features. The BUILDING is associated with the multiple

ADDRESS features.



3. Building Address Process Type 3 (BA03) BUILDING polygon spatially contains exactly 1 property geocode ADDRESS feature. The BUILDING is associated with the 1 ADDRESS

feature.



4. Building Address Process Type 4 (BA04) BUILDING polygon spatially contains multiple properties geocode ADDRESS features. The BUILDING is associated with the multipl e

ADDRESS features.

Building Address Process Type 4 example (BA04)


5. Building Address Process Type 5 (BA05) PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains exactly 1 property

geocode ADDRESS feature. A single BUILDING is associated with the 1 ADDRESS feature.



6. Building Address Process Type 6 (BA06) PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains exactly 1 property

geocode ADDRESS feature. Multiple BUILDINGS are associated with the 1 ADDRESS feature.



7. Building Address Process Type 7 (BA07) PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple properties

geocode ADDRESS features. A single BUILDING is associated with multiple ADDRESS features.



8. Building Address Process Type 8 (BA08) PROPERTY polygon contains or intersects greater than 80% with BUILDING polygon feature and spatially contains multiple properties

geocode ADDRESS features. Multiple BUILDINGS are associated with multiple ADDRESS features.



It is known that where a large number of addresses fall within a property with a large number of unassigned buildings this relationship

code will produce a significant number of building address records. An example of this is shown below where the property cont ains 85

geocodes, each of the 207 buildings has a building address record for each of the 85 geocodes within the property.

Building Address Process Type 8 example – multiple (BA08)


9. Building Address Process Type 9 (BA09) BUILDING polygon partially intersects a single PROPERTY polygon with 1 or more property geocodes ADDRESS features. A single

BUILDING is associated with 1 or more ADDRESS features.



10. Building Address Process Type 10 (BA10) BUILDING polygon partially intersects multiple PROPERTY polygons with 1 or more property geocode ADDRESS features. A single

BUILDING is associated with multiple ADDRESS features.



11. Building Address Process Type 11 (BA11) PROPERTY polygon spatially contains 1 or more building geocode ADDRESS features allocated a BUILDING feature and 1 or more

BUILDING polygons intersect PROPERTY polygon not allocated ADDRESS. Multiple BUILDINGS associated with 1 or more ADDRESS

features.



12. Building Address Process Type 12 (BA12) ADDRESS has not been allocated a BUILDING. The BUILDING polygon area intersects by more than 10% a single PROPERTY polygon wi th

1 or more ADDRESS features allocated a BUILDING. A single BUILDING is associated with multiple ADDRESS features.



13. Building Address Process Type 13 (BA13) BUILDING not allocated an ADDRESS and BUILDING polygon spatially contain or intersects PROPERTY polygon that has an ADDRESS

within 15 metres and the closest PROPERTY to the ADDRESS. A single BUILDING is associated with a single ADDRESS feature.



14. Building Address Process Type 14 (BA14) BUILDING not allocated ADDRESS and BUILDING polygon intersect with PROPERTY polygon with the same PROPERTY_PID as PROPERTY

polygon no more than 1km containing ADDRESS feature. A single BUILDING is associated with 1 or more ADDRESS features.



15. Building Address Process Type 15 (BA15) BUILDING not allocated an ADDRESS and PROPERTY polygon intersect with BUILDING polygon where PROPERTY polygon contains 1 or

more gap geocode ADDRESS features. A single BUILDING is associated with 1 or more ADDRESS features.



Appendix D – Building-CAD Process Type Examples The following list of examples shows data demonstrating each of the process types used for making a linkage between buildings and CAD.

Each diagram shows the CAD boundaries in black.

16. Building CAD Process Type 1 (BC01) The BUILDING polygon is completely contained by CAD polygon feature. The CAD feature is associated with the BUILDING feature.

Building CAD Process Type 1 examples (BC01)


17. Building CAD Process Type 2 (BC02) The BUILDING polygon completely contains CAD polygon feature. The CAD feature is associated with one or more BUILDING features.



18. Building CAD Process Type 3 (BC03) The BUILDING polygon has 80% or more spatial overlap of the buildings area with CAD polygon feature. The CAD feature is assoc iated




19. Building CAD Process Type 4 (BC04) The BUILDING polygon has a spatial overlap of less than 80% but 10% or more of the buildings area with CAD polygon feature. The CAD




20. Building CAD Process Type 5 (BC05) The BUILDING polygon has a spatial overlap of less than 10% of the buildings area with CAD polygon feature. The CAD feature i s




21. Building CAD Process Type 6 (BC06) The BUILDING polygon is completely contained by a CAD polygon feature that also contains CAD point feature. The CAD feature i s




22. Building CAD Process Type 7 (BC07) The BUILDING polygon has a spatial overlap of more than 80% of the buildings area with CAD polygon feature that also contains CAD

point feature. The CAD feature is associated with the BUILDING feature.



23. Building CAD Process Type 8 (BC08) The BUILDING polygon has a spatial overlap of less than 80% of the buildings area with CAD polygon feature that also contains CAD point

feature. The CAD feature is associated with the BUILDING feature.



24. Building CAD Process Type 9 (BC09) The BUILDING polygon has a spatial overlap with ‘NOT REGISTERED’ CAD polygon feature.


Documents

Buildings - geoscape.com.au · 1.2 Data Product Specification Title Buildings Product Description 1.3 Data Scope Buildings is a digital dataset representing buildings across Australia