===================== 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 [#F1]_ * G-NAF Planning Insights uses simple spatial intersection to provide the relationship between a parcel and planning zones or overlays (for example, flood, bushfire or heritage overlays). If any part of a planning zone or overlay overlaps a parcel, it will be associated with the parcel, even if it does not overlap with the area of the parcel where a building is located. The joins used to link to these products are shown below, with attributes used in the joins described. .. graphviz:: digraph G { graph [pad="0.5", ranksep="1"]; fontname="ROBOTO" fontsize="10pt" node [fontname="ROBOTO" fontsize="8pt"] edge [fontname="ROBOTO" fontsize="8pt"] rankdir=LR; nodesep=0.5; subgraph cluster_planning_insights { label="Planning Insights" graph[style="dashed,rounded" color="#EA6B66"] planning_insights [shape=plain label=<
planning_insights
PK pi_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
state: varchar (3)
pi_zone_code: varchar (120)
flood: varchar (5)
bushfire: varchar (5)
infrastructure: varchar (5)
environment: varchar (5)
heritage: varchar (5)
industry: varchar (5)
permitted: varchar (2800)
permitted_with_controls: varchar (4800).
prohibited: varchar (4000)
permitted_use_apartment: varchar (5)
permitted_use_duplex: varchar (5)
permitted_use_mixeduse: varchar (5)
permitted_use_townhouse: varchar (5)
>]; planning_insights_zoning [ shape=plain label=<]
planning_insights_zoning
PK pi_zoning_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
zone_code: varchar (120)
zone_label1: varchar (230)
zone_label2: varchar (120)
>]; planning_insights_overlays [ shape=plain label=<]
planning_insights_overlays
PK pi_overlay_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
overlay_category: varchar (20)
overlay_group: varchar (120)
overlay_label: varchar (160)
overlay_value: varchar (270)
>]; planning_insights_address [shape=plain label=< ]
planning_insights_address
PK pi_address_pid: varchar (15)
FK address_detail_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
>]; planning_insights -> planning_insights_zoning [arrowhead=crownoneodot, dir=both, arrowtail=nonetee, label="base_cadastre_pid"] planning_insights -> planning_insights_overlays [arrowhead=crownoneodot, dir=both, arrowtail=nonetee, label="base_cadastre_pid"] planning_insights -> planning_insights_address [arrowhead=crownoneodot, dir=both, arrowtail=nonetee, label="base_cadastre_pid"] {rank=same; planning_insights; planning_insights_address} } subgraph cluster_cadastre { label="Cadastre" graph[style="dashed,rounded" color="#000000"] cadastre [shape=plain label=<
cadastre
PK cadastre_polygon_pid: varchar (15)
cadastre_pid: varchar (15)
contributor_id: varchar (20)
date_created: date
date_modified: date
state: varchar (3)
lot: varchar (15)
plan: varchar (20)
section: varchar (5)
parcel_id: varchar (60)
source: varchar (20)
contributor_status: varchar (35)
title_status: varchar (10)
parcel_type: varchar (10)
base_parcel: varchar (3)
FK base_cadastre_pid: varchar (15)
strata_type: varchar (10)
total_strata_count: number (5)
horizontal_strata_count: number (5)
vertical_strata_count: number (5)
area: number (12,2)
geometry: Polygon
>]; cadastre -> planning_insights [arrowhead=noneteenoneodot, dir=both, arrowtail=crownonetee, label="base_cadastre_pid"] } subgraph cluster_gnaf { label="G-NAF" graph[style="dashed,rounded" color="#000000"] address_detail [shape=plain label=<
ADDRESS_DETAIL
PK ADDRESS_DETAIL_PID: varchar (15)
DATE_CREATED: date
DATE_LAST_MODIFIED: date
DATE_RETIRED: date
BUILDING_NAME: varchar (200)
LOT_NUMBER_PREFIX: varchar (2)
LOT_NUMBER: varchar (5)
LOT_NUMBER_SUFFIX: varchar (2)
FK FLAT_TYPE_CODE: varchar (7)
FLAT_NUMBER_PREFIX: varchar (2)
FLAT_NUMBER: number (5)
FLAT_NUMBER_SUFFIX: varchar (2)
FK LEVEL_TYPE_CODE: varchar (4)
LEVEL_NUMBER_PREFIX: varchar (2)
LEVEL_NUMBER: number (3)
LEVEL_NUMBER_SUFFIX: varchar (2)
NUMBER_FIRST_PREFIX: varchar (3)
NUMBER_FIRST: number (6)
NUMBER_FIRST_SUFFIX: varchar (2)
NUMBER_LAST_PREFIX: varchar (2)
NUMBER_LAST: number (6)
NUMBER_LAST_SUFFIX: varchar (2)
FK STREET_LOCALITY_PID: varchar (15)
LOCATION_DESCRIPTION: varchar (2)
LOCALITY_PID: varchar (2)
ALIAS_PRINCIPAL: char (1)
POSTCODE: varchar (4)
PRIVATE_STREET: varchar (75)
LEGAL_PARCEL_ID: varchar (20)
CONFIDENCE: number (1)
ADDRESS_SITE_PID: varchar (15)
FK LEVEL_GEOCODED_CODE: number (2)
PROPERTY_PID: varchar (15)
GNAF_PROPERTY_PID: varchar (15)
PRIMARY_SECONDARY: varchar (1)
>]; address_default_geocode [shape=plain label=<
ADDRESS_DEFAULT_GEOCODE
PK ADDRESS_DEFAULT_GEOCODE_PID: varchar (15)
DATE_CREATED: date
DATE_RETIRED: date
FK ADDRESS_DETAIL_PID: varchar (15)
FK GEOCODE_TYPE_CODE: varchar (4)
FK GEOMETRY: Point
FK LONGITUDE: varchar (11,8)
LATITUDE: number (10,8)
>]; address_detail -> planning_insights_address [arrowhead=crownoneodot, dir=both, arrowtail=nonetee, label="ADDRESS_DETAIL_PID"] address_default_geocode -> address_detail[arrowhead=nonetee, dir=both, arrowtail=nonetee, label="ADDRESS_DETAIL_PID"] } subgraph cluster_legend { graph[style="" label="Legend" ] legend [shape=plain label=<
Spatial Attribute Table
Textual Attribute Table
>] key [shape=plain label=<
Zero or One
Zero or Many
One or Many
One
>] key2 [shape=plain label=<
>] key:i1 -> key2:i1 [arrowhead=noneteenoneodot] key:i2 -> key2:i2 [arrowhead=nonecrownoneodot] key:i3 -> key2:i3 [arrowhead=nonecrownonetee] key:i4 -> key2:i4 [arrowhead=nonetee] } } .. [#F1] 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: .. csv-table:: :header-rows: 1 :widths: 150,350 :file: technical_description/planning_insights_data_tables.csv ---------- Data Model ---------- .. graphviz:: digraph G { graph [pad="0.5", ranksep="1"]; fontname="ROBOTO" fontsize="10pt" node [fontname="ROBOTO" fontsize="8pt"] edge [fontname="ROBOTO" fontsize="8pt"] rankdir=LR subgraph cluster_planning_insights { label="Planning Insights" graph[style="dashed,rounded" color="#EA6B66"] planning_insights [shape=plain label=<
planning_insights
PK pi_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
state: varchar (3)
pi_zone_code: varchar (120)
flood: varchar (5)
bushfire: varchar (5)
infrastructure: varchar (5)
environment: varchar (5)
heritage: varchar (5)
industry: varchar (5)
permitted: varchar (2800)
permitted_with_controls: varchar (4800).
prohibited: varchar (4000)
permitted_use_apartment: varchar (5)
permitted_use_duplex: varchar (5)
permitted_use_mixeduse: varchar (5)
permitted_use_townhouse: varchar (5)
>]; planning_insights_zoning [ shape=plain label=<]
planning_insights_zoning
PK pi_zoning_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
zone_code: varchar (120)
zone_label1: varchar (230)
zone_label2: varchar (120)
>]; planning_insights_overlays [ shape=plain label=<]
planning_insights_overlays
PK pi_overlay_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
overlay_category: varchar (20)
overlay_group: varchar (120)
overlay_label: varchar (160)
overlay_value: varchar (270)
>]; planning_insights_address [shape=plain label=< ]
planning_insights_address
PK pi_address_pid: varchar (15)
FK address_detail_pid: varchar (15)
FK base_cadastre_pid: varchar (15)
date_created: date
>]; planning_insights -> planning_insights_zoning [arrowhead=crownoneodot, dir=both arrowtail=nonetee] planning_insights -> planning_insights_overlays [arrowhead=crownoneodot, dir=both arrowtail=nonetee] planning_insights -> planning_insights_address [arrowhead=crownoneodot, dir=both arrowtail=nonetee] {rank=same; planning_insights; planning_insights_address} } cadastre [ style=filled shape=Mrecord fillcolor="#7EA6E0" ] cadastre -> planning_insights [arrowhead=crownoneodot, dir=both arrowtail=crownonetee] ADDRESS_DETAIL [ style=filled shape=Mrecord fillcolor="#FFD966" ] ADDRESS_DETAIL -> planning_insights_address [arrowhead=crownoneodot, dir=both arrowtail=nonetee] subgraph cluster_legend { graph[style="" label="Legend" ] legend [shape=plain label=<
Spatial Attribute Table
Textual Attribute Table
>] key [shape=plain label=<
Zero or One
Zero or Many
One or Many
One
>] key2 [shape=plain label=<
>] key:i1 -> key2:i1 [arrowhead=noneteenoneodot] key:i2 -> key2:i2 [arrowhead=nonecrownoneodot] key:i3 -> key2:i3 [arrowhead=nonecrownonetee] key:i4 -> key2:i4 [arrowhead=nonetee] } } --------------- Data Dictionary --------------- .. csv-table:: planning_insights :header-rows: 1 :widths: 75,75,180,35,45 :file: technical_description/table_planning_insights.csv .. csv-table:: planning_insights_zoning :header-rows: 1 :widths: 75,75,180,35,45 :file: technical_description/table_planning_insights_zoning.csv .. csv-table:: planning_insights_overlays :header-rows: 1 :widths: 75,75,180,35,45 :file: technical_description/table_planning_insights_overlays.csv .. csv-table:: planning_insights_address :header-rows: 1 :widths: 75,75,180,35,45 :file: technical_description/table_planning_insights_address.csv ------------- Domain Values ------------- planning_insights ----------------- .. csv-table:: state :header-rows: 1 :widths: 75,425 :file: technical_description/state_domain.csv .. csv-table:: flood :header-rows: 1 :widths: 75,425 :file: technical_description/flood_domain.csv .. csv-table:: bushfire :header-rows: 1 :widths: 75,425 :file: technical_description/bushfire_domain.csv .. csv-table:: infrastructure :header-rows: 1 :widths: 75,425 :file: technical_description/infrastructure_domain.csv .. csv-table:: environment :header-rows: 1 :widths: 75,425 :file: technical_description/environment_domain.csv .. csv-table:: heritage :header-rows: 1 :widths: 75,425 :file: technical_description/heritage_domain.csv .. csv-table:: industry :header-rows: 1 :widths: 75,425 :file: technical_description/industry_domain.csv .. csv-table:: permitted_use_apartment :header-rows: 1 :widths: 75,425 :file: technical_description/permitted_use_apartment_domain.csv .. csv-table:: permitted_use_duplex :header-rows: 1 :widths: 75,425 :file: technical_description/permitted_use_duplex_domain.csv .. csv-table:: permitted_use_mixeduse :header-rows: 1 :widths: 75,425 :file: technical_description/permitted_use_mixeduse_domain.csv .. csv-table:: permitted_use_townhouse :header-rows: 1 :widths: 75,425 :file: technical_description/permitted_use_townhouse_domain.csv planning_insights_overlays -------------------------- .. csv-table:: overlay_category :header-rows: 1 :widths: 75,425 :file: technical_description/overlay_category_domain.csv -------- Overlays -------- An overlay on a parcel indicates that specific planning conditions may need to be met if a development application is lodged in relation to that parcel. For the avoidance of doubt, overlays do not represent risk. For example, if a parcel intersects with a flood overlay, it indicates that a flood study may be required if a development application is lodged for the parcel. However, it does not represent an assessment of the flood risk for that parcel or any buildings on that parcel. Users should note that councils across Australia have different study criteria for development applications. For example, some councils have a simple rating for flood overlays while others specify that a ‘1% AEP’ flood layer over a parcel may require a flood study. For this reason, users should apply their own judgement when using the overlay data and should use the relevant overlay_value values within the planning_insights_overlays tables to help guide their use. Overlays in the planning_insights_overlays table with overlay_category of 'flood', 'bushfire', 'infrastructure', 'environment', 'heritage' or 'industry', will typically trigger a ``'true'`` flag value (e.g. flood flag) for the corresponding planning_insights record. However, if the overlay has been deemed as not applicable at the parcel level, a 'true' value will not be assigned. For example, this occurs in QLD for flood overlays with overlay_value of ``'Basin 1% AEP'``, which do not trigger a ``'true'`` flood flag in the planning_insights table. This also happens in NSW for heritage overlays with overlay_value of ``'City of Broken Hill'`` which does not trigger a ``'true'`` heritage flag in the planning_insights table. ---------------- 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. .. csv-table:: Planning Insights Release Information :header-rows: 1 :file: technical_description/update_frequency.csv Planning Insights release frequency with correlating Cadastre and G-NAF release inputs. ----------------------------- 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. .. image:: technical_description/planning_insights_extent.png :alt: Extent map of planning data. A detailed description of the coverage for each State and Territory is provided in the table below. .. csv-table:: :header-rows: 1 :file: technical_description/planning_insights_state_coverage.csv --------------- 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 Geopackage ---------------- | **Format name** | Geopackage | | **Specification** | This format includes files with the following extensions: \*.gpkg | OGC Geopackage Standards. Follow this link: https://www.geopackage.org/ | | **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'.