Technical Description

Planning Insights is created by spatially intersecting planning zone and overlay data with Geoscape’s Cadastre product. The G-NAF (Geocoded National Address File) product is then spatially related to the linked cadastre parcels via a point (G-NAF address) in polygon (Cadastre) relationship. Source attributes are mapped and standardised to provide a coherent definition across Australia. Additional attributes have been generated and integrated by Geoscape to support the source information as well as to provide convenience in the use and representation of the dataset. Planning Insights is updated and released regularly and has integrated relationships with other Geoscape Products. Further information regarding attributes, quality, coverage, and product release details are outlined below.

Linkages

Planning Insights is integrated with the following Geoscape products:

• Cadastre [1]

• G-NAF

The joins used to link to these products are shown below, with attributes used in the joins described.

[1]

The cadastre table included with the Planning Insights product has an additional base_cadastre_pid attribute that is used for linkage purposes. This field does not exist in the standard Cadastre product.

Data Tables

Planning Insights consists of four tables:

Data Table	Description
planning_insights	Provides a broad compilation of information related to planning zone, overlay categories, and permitted and prohibited uses for each parcel.
planning_insights_zoning	Provides detailed planning zone information for each cadastral parcel including the zone code or codes applied to the parcel and their associated descriptive labels.
planning_insights_overlays	Provides detailed overlay information, such as flood, bushfire and heritage overlays for each cadastral parcel.
planning_insights_address	Provides a linkage between Geoscape’s G-NAF (Geocoded National Address File) product and Planning Insights through the address_detail_pid and base_cadastre_pid. Geoscape create this linkage through spatial intersection between G-NAF points and Cadastre polygons that have a primary linkage to Planning Insights.

Data Model

Data Dictionary

planning_insights

Attribute	Data Type	Description	Primary Key	Mandatory
pi_pid	Character String (15)	Unique persistent identifier for the planning_insights record.	Yes	Yes
base_cadastre_pid	Character String (15)	The cadastral identifier used to traverse Planning Insights tables and link to Cadastre.	No	Yes
date_created	Date	The date the record is first introduced to the Geoscape product.	No	Yes
state	Character String (3)	The abbreviated name of the State or Territory that the record resides within.	No	Yes
pi_zone_code	Character String (120)	The planning zone code provided by the jurisdiction or council that is related to the parcel. Where two or more zones relate to the parcel, a single zone code has been selected to preserve the 1:1 relationship to the cadastre table. Detailed zoning information is obtained from the planning_insights_zoning table that provides the many to one relationships to planning zones.	No	No
flood	Character String (5)	Indicates if a flood overlay intersects the parcel.	No	No
bushfire	Character String (5)	Indicates if a bushfire overlay intersects the parcel.	No	No
infrastructure	Character String (5)	Indicates if an infrastructure overlay intersects the parcel.	No	No
environment	Character String (5)	Indicates if an environment overlay intersects the parcel.	No	No
heritage	Character String (5)	Indicates if a heritage overlay intersects the parcel.	No	No
industry	Character String (5)	Indicates if an industry overlay intersects the parcel.	No	No
permitted	Character String (2800)	A list of uses permitted at the parcel separated by a ‘;’ character.	No	No
permitted_with_controls	Character String (4600)	A list of uses permitted, with permission, at the parcel separated by a ‘;’ character.	No	No
prohibited	Character String (4000)	A list of uses prohibited at the parcel separated by a ‘;’ character.	No	No
permitted_use_apartment	Character String (5)	Indicates whether apartments are permitted at the parcel.	No	No
permitted_use_duplex	Character String (5)	Indicates whether duplexes are permitted at the parcel.	No	No
permitted_use_mixeduse	Character String (5)	Indicates whether mixed use developments are permitted at the parcel.	No	No
permitted_use_townhouse	Character String (5)	Indicates whether townhouses are permitted at the parcel.	No	No

planning_insights_zoning

Attribute	Data Type	Description	Primary Key	Mandatory
pi_zoning_pid	Character String (15)	Unique persistent identifier for the planning_insights_zoning record.	Yes	Yes
base_cadastre_pid	Character String (15)	The cadastral identifier used to traverse Planning Insights tables and link to Cadastre.	No	Yes
date_created	Date	The date the record is first introduced to the Geoscape product.	No	Yes
zone_code	Character String (120)	The planning zone code provided by the jurisdiction or council.	No	Yes
zone_label1	Character String (230)	Descriptive information about the planning zone or planning zone use.	No	No
zone_label2	Character String (120)	Ancillary descriptive information about the planning zone or planning zone use.	No	No

planning_insights_overlays

Attribute	Data Type	Description	Primary Key	Mandatory
pi_overlay_pid	Character String (15)	Unique persistent identifier for the planning_insights_overlays record.	Yes	Yes
base_cadastre_pid	Character String (15)	The cadastral identifier used to traverse Planning Insights tables and link to Cadastre.	No	Yes
date_created	Date	The date the record is first introduced to the Geoscape product.	No	Yes
overlay_category	Character String (20)	A high-level grouping for flood, bushfire, heritage, infrastructure, environment and industry overlay types only. Relates to the high-level overlay attributes provided in the planning_insights table (e.g. flood, bushfire, environment, etc. attributes)	No	No
overlay_group	Character String (120)	A low-level grouping of overlay types that covers all records.	No	Yes
overlay_label	Character String (160)	A label describing the overlay.	No	No
overlay_value	Character String (270)	Ancillary information describing the overlay.	No	No

planning_insights_address

Attribute	Data Type	Description	Primary Key	Mandatory
pi_address_pid	Character String (15)	Unique persistent identifier for the planning_insights_address record.	Yes	Yes
address_detail_pid	Character String (15)	The G-NAF identifier used to link Planning Insights to addresses.	No	Yes
base_cadastre_pid	Character String (15)	The cadastral identifier used to traverse Planning Insights tables and link to Cadastre.	No	Yes
date_created	Date	The date the record is first introduced to the Geoscape product.	No	Yes

Domain Values

planning_insights

state

Domain Value	Description
ACT	The data is located within the Australian Capital Territory.
NSW	The data is located within the state of New South Wales.
NT	The data is located within the Northern Territory.
QLD	The data is located within the state of Queensland.
SA	The data is located within the state of South Australia.
TAS	The data is located within the state of Tasmania.
VIC	The data is located within the state of Victoria.
WA	The data is located within the state of Western Australia.

flood

Domain Value	Description
true	Indicates that a flood overlay intersects the parcel.
false	Indicates that a flood overlay does not intersect the parcel. This can occur when no flood overlays are available for a particular area.

bushfire

Domain Value	Description
true	Indicates that a bushfire overlay intersects the parcel.
false	Indicates that a bushfire overlay does not intersect the parcel. This can occur when no bushfire overlays are available for a particular area.

infrastructure

Domain Value	Description
true	Indicates that an infrastructure overlay intersects the parcel.
false	Indicates that an infrastructure overlay does not intersect the parcel. This can occur when no infrastructure overlays are available for a particular area.

environment

Domain Value	Description
true	Indicates that an environment overlay intersects the parcel.
false	Indicates that an environment overlay does not intersect the parcel. This can occur when no environment overlays are available for a particular area.

heritage

Domain Value	Description
true	Indicates that a heritage overlay intersects the parcel.
false	Indicates that a heritage overlay does not intersect the parcel. This can occur when no heritage overlays are available for a particular area.

industry

Domain Value	Description
true	Indicates that an industry overlay intersects the parcel.
false	Indicates that an industry overlay does not intersect the parcel. This can occur when no industry overlays are available for a particular area.

permitted_use_apartment

Domain Value	Description
true	Indicates that apartments can be built at the site based on zoning information.
false	Indicates that apartments cannot be built at the site based on zoning information.
maybe	Indicates that apartments can potentially be built at the site based on zoning information. A ‘maybe’ flag signifies that other factors besides the zoning may come into play to determine whether apartments can be built. This could relate to the location of the cadastre (whether it is in a city centre or rural town), the size of the parcel (potentially more cadastre would have to be purchased alongside the cadastre to meet total area requirements to build this type of building) as well as other factors. For example, in NSW there are standardised zone codes that are applied across the state (e.g. R3 Medium Density Residential). There will likely be different expectations of what can be developed for a parcel with this zone type in a rural town like Bathurst in comparison with a city centre like Parramatta. It is recommended that local controls and specifics of the site are consulted where a ‘maybe’ value exists to better understand local constraints.
<NULL>	It is unknown whether duplexes can be built at the site. This can occur if no zone or permitted use information can be linked to the parcel.

permitted_use_duplex

Domain Value	Description
true	Indicates that duplexes can be built at the site based on zoning information.
false	Indicates that duplexes cannot be built at the site based on zoning information.
maybe	Indicates that duplexes can potentially be built at the site based on zoning information. A ‘maybe’ flag signifies that other factors besides the zoning may come into play to determine whether duplexes can be built. This could relate to the location of the cadastre (whether it is in a city centre or rural town), the size of the parcel (potentially more cadastre would have to be purchased alongside the cadastre to meet total area requirements to build this type of building) as well as other factors. For example, in NSW there are standardised zone codes that are applied across the state (e.g. R3 Medium Density Residential). There will likely be different expectations of what can be developed for a parcel with this zone type in a rural town like Bathurst in comparison with a city centre like Parramatta. It is recommended that local controls and specifics of the site are consulted where a ‘maybe’ value exists to better understand local constraints.
<NULL>	It is unknown whether duplexes can be built at the site. This can occur if no zone or permitted use information can be linked to the parcel.

permitted_use_mixeduse

Domain Value	Description
true	Indicates that mixed use developments can be built at the site based on zoning information.
false	Indicates that mixed use developments cannot be built at the site based on zoning information.
maybe	Indicates that mixed use developments can potentially be built at the site based on zoning information. A ‘maybe’ flag signifies that other factors besides the zoning may come into play to determine whether mixed use developments can be built. This could relate to the location of the cadastre (whether it is in a city centre or rural town), the size of the parcel (potentially more cadastre would have to be purchased alongside the cadastre to meet total area requirements to build this type of building) as well as other factors. For example, in NSW there are standardised zone codes that are applied across the state (e.g. R3 Medium Density Residential). There will likely be different expectations of what can be developed for a parcel with this zone type in a rural town like Bathurst in comparison with a city centre like Parramatta. It is recommended that local controls and specifics of the site are consulted where a ‘maybe’ value exists to better understand local constraints.
<NULL>	It is unknown whether mixed use developments can be built at the site. This can occur if no zone or permitted use information can be linked to the parcel.

permitted_use_townhouse

Domain Value	Description
true	Indicates that townhouses can be built at the site based on zoning information.
false	Indicates that townhouses cannot be built at the site based on zoning information.
maybe	Indicates that mixed townhouses can potentially be built at the site based on zoning information. A ‘maybe’ flag signifies that other factors besides the zoning may come into play to determine whether townhouses can be built. This could relate to the location of the cadastre (whether it is in a city centre or rural town), the size of the parcel (potentially more cadastre would have to be purchased alongside the cadastre to meet total area requirements to build this type of building) as well as other factors. For example, in NSW there are standardised zone codes that are applied across the state (e.g. R3 Medium Density Residential). There will likely be different expectations of what can be developed for a parcel with this zone type in a rural town like Bathurst in comparison with a city centre like Parramatta. It is recommended that local controls and specifics of the site are consulted where a ‘maybe’ value exists to better understand local constraints.
<NULL>	It is unknown whether townhouses can be built at the site. This can occur if no zone or permitted use information can be linked to the parcel.

planning_insights_overlays

overlay_category

Domain Value	Description
flood	The overlay falls within the high-level overlay category of ‘flood’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘flood’ attribute.
bushfire	The overlay falls within the high-level overlay category of ‘bushfire’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘bushfire’ attribute.
infrastructure	The overlay falls within the high-level overlay category of ‘infrastructure’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘infrastructure’ attribute.
environment	The overlay falls within the high-level overlay category of ‘environment’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘environment’ attribute.
heritage	The overlay falls within the high-level overlay category of ‘heritage’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘heritage’ attribute.
industry	The overlay falls within the high-level overlay category of ‘industry’. The related record (match on base_cadastre_pid) in the planning_insights table will have a ‘true’ value for the ‘industry’ attribute.

Update Frequency

Planning Insights is continuously updated and released with the most up to date data available on a quarterly schedule in the months of March, June, September and December.

Planning Insights Release Month	Cadastre Release Month used in Planning Insights	G-NAF Release Month used in Planning Insights
March	February	February
June	May	May
September	August	August
December	November	November

Extent/Geographic Description

Planning Insights is an aspatial dataset and therefore has no spatial coverage unless joined to Cadastre or G-NAF. Once joined to Cadastre, Planning Insights has spatial coverage across Australia. Planning information may not be available for land held by the Commonwealth, as this land is not managed by State or Local Government authorities.

A detailed description of the coverage for each State and Territory is provided in the table below.

State or Territory Name	State Abbreviation	Coverage
Australian Capital Territory	ACT	Complete coverage.
New South Wales	NSW	Complete coverage.
Northern Territory	NT	Complete coverage.
Other Territories	OT	Christmas and Cocos (Keeling) Islands No Coverage. Jervis Bay No Coverage. Norfolk Island No Coverage.
Queensland	QLD	State wide coverage.
South Australia	SA	State wide coverage.
Tasmania	TAS	State wide coverage.
Victoria	VIC	Complete coverage.
Western Australia	WA	Complete coverage.

Delivery Format

Planning Insights is provided at the State/Territory level. The data is made available in PSV (Pipe Separated Values) file format.

PSV Files

Format name

Pipe Separated Value files

Specification

PSV files may be used in relational database applications and may be viewed in spreadsheets. This format provides files with the following extension *.psv

Language

English

Product Versioning

Planning Insights versioning is managed through incrementing when there is a change to the product schema or a significant change in data population, these are described further below:

• A schema change can affect a major or minor increment to the versioning. Additive changes (changes that won’t break customers’ ability to work with the data) will be incremented with a minor version increment, an example is the addition of a new attribute. Removal of attributes or changing the structure of the Planning Insights schema will enact a major change to identify that this requires the attention of all customers and partners.

• Where a significant geography of Australia either has a new population of data for an attribute or is populated from a much higher quality source a minor increment will be applied to the product version.

Therefore, Planning Insights versioning will not increment with every data update. Published releases will have a name e.g. ‘March 2023’ and will reference a version of the Planning Insights product e.g. ‘1.0’.