=====================
Technical Description
=====================
Planning is created through the spatial intersection of Cadastre cadastral polygon centroids with planning zone spatial boundaries. Through this process, a planning zone code and its associated descriptive information are associated with a cadastral polygon. In areas where State and local Government planning zone sources are both used to build the dataset, and these overlap one another, the local Government source has been prioritised for the relationship.
All non-Road Cadastre polygons are utilised in the assignment process, inclusive of all parcel_status values.
Planning is created from a range of State, Territory and local Government data which is revised regularly and supplied in varying formats and levels of quality. Planning zone code values for these source datasets differ greatly across jurisdictions and local governments due to unique planning regulations between States and also between Local Government Areas (LGAs). A ‘psma_description’ attribute has been included for each planning record to serve as a general description of the planning zone codes across Australia and ease understanding of the data at a national level. Planning zone codes are not necessarily unique across Australia or by LGA.
Planning uses a process of spatial intersection at the centroid of a parcel and in the case of overlapping planning zones chooses a single planning zone classification. Therefore, it is not suitable for uses that require definitive planning information. In such cases, users should contact the relevant State, Territory or local Government planning authority for authoritative planning scheme information.
Geoscape Australia welcomes your feedback on the Planning product. We also publish regular updates on the development of our products on the Geoscape website ( `www.geoscape.com.au <https://www.geoscape.com.au>`_ ).
----------
Attributes
----------
Zone Code
---------
The Zone Code is the code related to the planning zone provided by each jurisdiction or council. The Zone Code is related to the cadastral polygon that intersects with the supplied planning zone polygon. In areas where data was supplied by a local Government this was prioritised over a supply from the State government.
Primary Zone Description
------------------------
The Primary Zone Description is directly related to the Zone Code and informs about the meaning of the code. This description can be used as a brief explanation of the planning zone or planning zone use that is related to the cadastral polygon.
Where the Zone Code is supplied as a description the Primary Zone Description may be the same as the Zone Code.
Secondary Zone Description
--------------------------
The Secondary Zone Description can give further information on the planning zone or planning zone use related to the cadastral polygon. Generally, this describes what is currently built or planned to be developed within the planning zone.
PSMA Description
----------------
The PSMA Description gives a generalised description used by Geoscape Australia for the Zone Code assigned to a cadastral polygon. This information was created by Geoscape Australia to provide a nationally consistent description of the planning zones across Australia.
Source
------
The Source provides the name of the State or local Government authority that the planning data was sourced from.
URL
---
The URL attribute provides a direct link to the planning website of the State or local Government that the planning zone data was sourced from. This URL can be used to access further information and detailed descriptions about the planning zone codes directly from each jurisdiction.
----------
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 { label="Geoscape Planning"
graph[style="dashed,rounded" color="#EA6B66"]
planning [shape=plain
label=<<TABLE BGCOLOR="#FFD966"
BORDER="1"
CELLBORDER="0"
style="rounded"
CELLSPACING="0"
CELLPADDING="5">
<TR>
<TD COLSPAN="2">planning</TD>
</TR>
<TR>
<TD BGCOLOR="white" >PK</TD>
<TD BGCOLOR="white" ALIGN="LEFT" >cad_polygon_pid: varchar (15) </TD>
</TR>
<TR>
<TD BGCOLOR="white" >PK</TD>
<TD BGCOLOR="white" ALIGN="LEFT" >cad_pid: varchar (15) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >date_created: date </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >state: varchar (3) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >zone_code: varchar (90) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >primary_zone_description: varchar (100) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >secondary_zone_description: varchar (350) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >psma_description: varchar (30) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >source: varchar (40) </TD>
</TR>
<TR>
<TD BGCOLOR="white" ></TD>
<TD BGCOLOR="white" ALIGN="LEFT" >url: varchar (125) </TD>
</TR>
</TABLE>>];
}
cadastre [ style=filled shape=Mrecord fillcolor="#7EA6E0" ]
cadastre -> planning [arrowhead=noneteenoneodot dir=both arrowtail=nonetee]
subgraph cluster_legend {
graph[style="" label="Legend" ]
legend [shape=plain
label=<<TABLE
CELLBORDER="0"
Border="0">
<TR>
<TD BGCOLOR="#7EA6E0" BORDER="1"> </TD>
<TD>Spatial Attribute Table</TD>
</TR>
<TR>
<TD BGCOLOR="#FFD966" BORDER="1"> </TD>
<TD>Textual Attribute Table</TD>
</TR>
</TABLE>>]
key [shape=plain label=<<table border="0" cellpadding="1" cellspacing="0" cellborder="0">
<tr><td port="i1"> Zero or One </td> </tr>
<tr><td port="i2"> One </td> </tr>
</table>>]
key2 [shape=plain label=<<TABLE border="0" cellpadding="1" cellspacing="0" CELLBORDER="0">
<tr><td port="i1"> </td></tr>
<tr><td port="i2"> </td></tr>
</TABLE>>]
key:i1 -> key2:i1 [arrowhead=noneteenoneodot]
key:i2 -> key2:i2 [arrowhead=nonetee]
}
planning -> legend [style=invis]
}
.. raw:: latex
\begin{landscape}
---------------
Data Dictionary
---------------
.. csv-table:: planning
:header-rows: 1
:widths: 130,110,180,50,50,80,100,80
:file: technical_description/table_planning.csv
.. raw:: latex
\end{landscape}
-------------
Domain Values
-------------
.. csv-table:: psma_description
:header-rows: 1
:file: technical_description/domain_psma_description.csv
----------------
Update Frequency
----------------
Planning is released on a quarterly schedule against the latest Cadastre data, with planning data updated bi-annually.
.. csv-table::
:header-rows: 1
:file: technical_description/update_frequency.csv
-----------------------------
Extent/Geographic Description
-----------------------------
Planning is an aspatial dataset and therefore has no spatial coverage unless joined to Cadastre. Once joined to Cadastre, Planning has spatial coverage across all States and Territories. 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_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
:widths: 100,80,220
:file: technical_description/planning_state_coverage.csv
---------------
Delivery Format
---------------
Planning is provided at a National and State/Territory level, depending on the file format selected. The data is made available in the File Geodatabase, JSON, ESRI Shapefile (DBF) and MapInfo TAB formats described below.
.. csv-table::
:header-rows: 1
:file: technical_description/delivery_format.csv
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
JSON
-----
| **Format name**
| JSON
|
| **Specification**
| This format includes files with the following extensions: \*.json
| JSON specification: https://www.json.org/json-en.html
|
| **Language**
| English
ESRI Shapefile (\*.dbf)
-----------------------
| **Format name**
| Shape – ESRI™
|
| **Specification**
| This format includes files with the following extensions: \*.dbf
| ESRI Shapefile Technical Description, an ESRI White Paper, July 1998. Follow this link: https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf
|
| **Language**
| English
|
| **Size Limitations**
| Where a DBF file exceeds the file size limit of 2GB, the file will be split into two (or more) files. The NSW Planning DBF exceeds the 2GB limit and has been split into two parts, one named ‘nsw_planning.dbf’ and the other named ‘nsw_planning_1.dbf’. Files exceeding the next 2GB increment will be suffixed by ‘_2’, then ‘_3’ for the next increment, and so on.
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
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 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 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 versioning will not increment with every data update, published releases will have a name e.g. ‘June 2020’ and will reference a version of the Planning product e.g. ‘1.1’.