National Property¶
Disclaimer
Overview¶
National Property is a seamless national representation of Australia’s property parcels. The product includes a national polygon representation of property boundaries and their legal identifiers across Australia.
Geoscape welcomes your feedback on the National Property product. We also publish regular product development updates on our website ( www.geoscape.com.au ).
Release Summary¶
This product was released to customers on 17 August 2026 with data extracted on 5 August 2026.
This release is a full national data population for Version 1.2 of the National Property product, described by National Property Product Guide v1.2.
Any issues that have been identified for this release are described in the Issues section.
Change Notifications¶
Versioning Update (Effective June 2026)¶
Beginning June 2026, all data products will transition to a standardised versioning format: MAJOR-MINOR-EXTRACT (e.g., 004-000-001). This approach provides a clear and consistent structure, making it easier for users to identify product versions and understand update levels at a glance. The change is intended to improve transparency, reduce ambiguity, and support more efficient integration and usage of our data products.
Implementation of New Zip File Naming and Packaging Standards (Effective August 2026)¶
As part of ongoing improvements to product consistency and packaging standards, updates to zip file naming conventions and internal packaging structure will be implemented, starting in August 2026.
Zip File Naming
Two standard naming patterns will be used, depending on whether an extract contains spatial information:
Spatial Tables:
{PRODUCT-NAME}_{RELEASE YYYYMM}_{REGION}_{CRS}_{FORMAT}_{VERSION MAJOR-MINOR-EXTRACT}.zip
Aspatial (Insights) Tables:
{PRODUCT-NAME}_{RELEASE YYYYMM}_{REGION}_NODATUM_{FORMAT}_{VERSION MAJOR-MINOR-EXTRACT}.zip
Packaging Structure
From this release, we have updated the folder structure in product packages. Previously, we provided a contents.txt file and a number of internal folders. The .ZIP file packages now only contain data files. We have applied this change to simplify accessing the data.
Product File Changes
To align the naming of the Australia region product files with the state and territory files, an 'australia_' prefix has been added to the table and layer names.
For example:
July 2026 > August 2026
file name:
property.gdb>australia_property.gdblayer name:
property>australia_propertyIn GeoJSON, JSON and PSV files, date fields are now represented in YYYY-MM-DD format (e.g. 2026-03-31) where previously they were provided in DD-MM-YYYY format (e.g. 31-03-2026).
These changes ensure consistent packaging across all products, reduce complexity, and support improved automation and user experience.
QLD Property Large Update Counts¶
We have ingested the new source data in GDA2020 coordinate reference system (CRS), when previously we used GDA94 CRS data. This has resulted in very small geometry differences between the July 2026 and August 2026 release data. Geoscape has mitigated these changes by mapping the previous property_polygon_pid and date_created values to the new records where possible. This change has resulted in ~2,800,000 date_modified value updates.
QLD Common Property property_cadastre linkage update¶
Queensland recently transitioned its cadastre data supply to a new data model. We have assessed these changes and have updated our processes for ingesting and processing the new data for the August 2026 release. This means that the QLD data which had not been updated since the May 2026 release how now been updated. As Cadastre and Property are interrelated, the QLD Property data has also been updated for the August 2026 release to align with the Cadastre update.
The Property logic has largely remained the same, as QLD has not changed the data model of their property data. However, QLD has changed its representation of Common Property cadastre which previously had a lot value of ‘0’ which has now changed to ‘CP’. Geoscape has adjusted it’s Common Property property_cadastre linkages so that ‘CP’ parcels are now linked instead of ‘0’ parcel.
VIC property_cadastre source changes¶
We have noticed a ~29,000 record increase in the VIC property_cadastre table. This increase has not corresponded with a similar count increase in either the VIC property or cadastre tables. We have investigated this change and have found that it relates to more properties being linked to proposed cadastre, often where common property is involved. We believe this to be a valid change in the VIC source data.
Issues¶
New Issues¶
No new issues to note.
Resolved Issues¶
No QLD Data Update¶
Queensland recently transitioned its cadastre data supply to a new data model. We have assessed these changes and have updated our processes for ingesting and processing the new data for the August 2026 release. This means that the QLD data which had not been updated since the May 2026 release has now been updated. As Property and Cadastre are interconnected, we have now also updated QLD Property for the August 2026 release.
Known Issues¶
Property valuations and maintenance¶
The timing of property valuations and maintenance by Geoscape’s supplying jurisdictions can sometimes misalign, resulting in property polygons not being represented for a period of time in the Geoscape Property product. This can happen when a property is cancelled prior to a new property being created within the jurisdiction’s records.
Missing property parcels in South Australia¶
The SA jurisdiction has retired property parcels across the state that have not been replaced with new parcels. While the jurisdiction has taken action to resolve most of these missing parcels there were still approximately 200 gaps in the property layer in the July 2024 release. The corresponding cadastre parcels for these locations are present, however, there was no link between the two layers as the property records were missing.
Missing property records in WA¶
In the May 2023 supply of WA property data, a small number of properties were attributed as no longer active but have not been replaced by new, active records. This resulted in approximately 395 missing property polygons in the Property product. We are investigating this issue with the jurisdiction.
Occurrences of overlaps in base property¶
Overlapping 'base_property = 'Yes'' parcels exist in the dataset. These are mostly located in high density residential areas like Adelaide CBD. An example of this can be seen at 138.59832, -34.93268 where there are two base property parcels that have a valid overlap. These parcels are overlapping each other but are not contained by another parcel, so are assigned as 'base_property = 'Yes''. These sites relate to valid overlaps in the base layer.
Parcels with the same contributor_id and very similar geometry in SA¶
In South Australia, there are approximately 250 records with the same contributor_id and with a very similar (but different) geometry. For example, at 138.57227, -34.90376 there are two properties with the same contributor_id of ‘’’25501810600000’’’ but with slightly different geometries (property_polygon_pid = ‘ppd19408402744b’ and ‘pp8852442b8bf6b’). This occurs due to floor level impacts in SA. These geometries are essentially the same and we will look to represent these as a single polygon representation in a future release.
QLD property large base parcels under standalone residential parcels¶
In QLD property it is common at townhouse/unit complexes to have a large base parcel representing the land valuation area of the entire complex, with small parcels overlapping the large base parcel. It has been identified that this is also incorrectly occurring under areas of standalone residential parcels. These parcels are caused due to a production issue where parcels without valuation are entering the product. This will be corrected by removing the large parcels in a future release. Examples of the parcels can be found at 152.77014, -27.64291 or '"property_pid" = 'prpff39d89bd00e''.
Future Considerations¶
This section outlines enhancements or changes under consideration, but not planned into a specific release. For further details on future initiatives, please contact Geoscape Support.
Annex A – Release Counts¶
Additional, retired and total counts and the percent change to the previous release have been listed in the table below.
TABLE |
STATISTIC |
ACT |
NSW |
NT |
OT |
QLD |
SA |
TAS |
VIC |
WA |
TOTAL |
|---|---|---|---|---|---|---|---|---|---|---|---|
property |
Additional |
40 |
6,662 |
569 |
0 |
13,802 |
1,380 |
635 |
13,101 |
40,681 |
76,870 |
Retired |
53 |
5,007 |
488 |
0 |
5,902 |
826 |
554 |
12,220 |
37,750 |
62,800 |
|
Updated |
2 |
383 |
0 |
0 |
2,801,183 |
286 |
0 |
1,773 |
50 |
2,803,677 |
|
Total |
138,309 |
4,190,397 |
81,394 |
0 |
2,832,468 |
1,108,627 |
322,105 |
4,331,364 |
1,230,022 |
14,234,686 |
|
% Change |
-0.01% |
0.04% |
0.10% |
0.00% |
0.28% |
0.05% |
0.03% |
0.02% |
0.24% |
0.10% |
|
property_cadastre |
Total |
160,027 |
4,408,611 |
93,740 |
0 |
3,232,068 |
1,139,044 |
333,617 |
6,303,153 |
1,550,143 |
17,220,403 |