Cadastre

Disclaimer

Geoscape 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 Geoscape Australia.

Overview

Cadastre is a spatial representation of cadastral parcels defined by the State and Territory governments of Australia. Cadastre aggregates the complex representations unique to each jurisdiction into a consistent seamless representation of the cadastral fabric of Australia. Geoscape welcomes your feedback on the Cadastre product. We also publish regular product development updates on our website ( www.geoscape.com.au ).

Release Summary

This product was released to customers on 20 December 2023 with data extracted on 11 December 2023.

• This release is a full national data population for Version 1.0 of the Cadastre product, described by the Cadastre Product Guide v1.0.

Any issues that have been identified for this release are described in the Issues section.

Change Notifications

Release frequency change from quarterly to monthly

From September 2023, the Cadastre and Property datasets have been and will continue to be, released on a monthly schedule.

Some jurisdictions only supply data on a quarterly schedule so updates for these will not occur in every monthly release.

Esri Shapefile width increase

Commencing with the February 2024 release, the width of numeric fields within Esri Shapefiles will increase by one. This is due to a bug fix in our packaging application. This change only impacts Shapefile metadata, the values and precision remain unchanged.

VIC alignment changes

The state of Victoria is conducting a modernisation of their cadastre data. This includes a realignment of the cadastre parcels that will result in a shift of the cadastre parcels. For further information on the areas that have undergone the realignment and the schedule for further areas please see https://land.vic.gov.au/maps-and-spatial/spatial-data/updates-to-vicmap .

Removal of the ‘Documents’ folder from data packages

From November 2023, Geoscape will be progressively moving product descriptions, guides and reports online to https://docs.geoscape.com.au

Commencing with the May 2024 release, data packages will no longer include the Documents folder.

Issues

New Issues

Supply issues for New South Wales data

Due to issues with the NSW jurisdictional supply, no new source data was received. Therefore, there is no update for the Cadastre data within the state of NSW for this release.

Resolved Issues

No resolved issues.

Known Issues

Inconsistencies between state strata count assignment

There are inconsistencies in the way strata counts are calculated across states caused by differences in how data is supplied by jurisdictions. In some states, strata counts are assigned to a plan (or equivalent) through an aspatial linkage; whereas, in other states, they are assigned for each polygon by spatial intersection between strata polygons and lot polygons. Differences in strata count will only be found when there is a lot parcel comprised of multiple parts with the same cadastre_pid i.e. multi-part polygons. In states where strata count is assigned by plan, the strata count at each polygon part with identical cadastre_pid will be equal. In states where strata count is assigned by polygon, the strata count at each polygon part with identical cadastre_pid can be different as they are identified per polygon.

Occurrences of Geoscape Australia parcels created where lot parcel already exists in WA

In Western Australia, there are Geoscape Australia source parcels being created where a Lot parcel already exists. At these locations, the Geoscape Australia parcel should not be created and strata counts should be assigned to the existing Lot parcel. This issue affects 349 parcels. An example of the issue can be seen at 115.811419860, -31.929084097, where the cadastre_polygon_pid relating to the created Geoscape Australia parcel is ‘cp19b3049807aa9’.

Occurrences of Lot parcels not assigned with Geoscape Australia source in ACT

In the Australian Capital Territory, there are 68 records that should be assigned as Geoscape Australia source parcels but are not where they duplicate a stratum parcel. These parcels should be assigned a source of ‘Geoscape Australia’ and should have reduced attribution. An example of this issue can be seen at 149.14167043, -35.31639048, where the related cadastre_polygon_pid is ‘cp310945032d5f1’.

Geoscape Australia parcels created from multiple plans in SA are populated with a plan and parcel_id

In South Australia, there are Geoscape Australia parcels created from multiple plans where strata parcels relating to different plans overlap. Where this occurs, a plan and parcel_id are currently assigned to the Geoscape Australia parcel. This is incorrect, as the Geoscape Australia parcel is an amalgamation of more than one plan. We intend to make the plan and parcel_id values for these parcels null in a future release. An example of this can be seen at 138.623771408, -35.551103052 for cadastre_polygon_pid of ‘cp7d42c855c495e’.

Occurrences of horizontal strata incorrectly assigned as vertical in SA

In South Australia, strata parcels are being assigned as ‘Vertical’ strata_type, when they should be assigned as ‘Horizontal’. This affects up to 2,316 strata sites. These sites relate to common property parcels with lot of ‘UCP’ and ‘FCP’ that are incorrectly being used to assign the site as containing vertical strata. An example of this can be seen at 138.593404803, -34.906232784 for cadastre_polygon_pid of ‘cp2692c4d8a3dbc’, ‘cp6477bc587c188’ and ‘cp87d76136d1456’.

Occurrences of Geoscape Australia parcel not created under ‘LP’ plan parcel in VIC

In Victoria, Geoscape Australia Lot parcels are not being created underneath strata parcels where the plan attribute starts with ‘LP’. This is causing gaps in the base parcel layer and no strata counts being assigned to a base Lot parcel at these locations. There are 555 locations where there is no Lot parcel underneath a strata parcel with ‘LP’ plan. For example, at 145.10846622, -37.82698677 for cadastre_polygon_pid of ‘cp999f0427245e0’ and ‘cpb212f6c7cac3a’, no Geoscape Australia Lot parcel has been created under the two strata parcels with plan of ‘LP45149’.

Occurrences of the same strata count assigned to many base parcels with the same plan in VIC

In Victoria, there are locations where a strata count is assigned to many parcels with the same plan. This issue occurs due to the way strata counts are assigned by plan in VIC. Geoscape Australia will assign these strata counts for only the related Lot parcel in a future release. An example of this can be seen at 144.890093, -37.745250 where many parcels with the plan of ‘LP10094’ have been assigned with the total strata count of ‘14’. Most of the parcels that have a plan of ‘LP10094’ do not have strata parcels present and therefore should not have a strata count.

Occurrences of strata parcels incorrectly assigned with ‘Horizontal’ strata_type in VIC

In Victoria, there are sites where strata parcels have a ‘Horizontal’ strata_type value where they should have a null strata_type value. This has occurred due to scenarios where the supplied jurisdictional data for a plan indicates Horizontal and unknown (null) strata_type. This happens at denser urban sites such as some high-rise locations. An example of this can be seen at 144.959846109, -37.817743046 where there are strata parcels that have a strata_type of ‘Horizontal’ where the assigned value should be null. We have consulted the jurisdiction and based on advice this issue cannot be resolved at this time.

Occurrences of strata parcels that have null strata type in SA

In South Australia, there are 96 strata parcels that have a null value for strata_type. These records should be assigned with a strata_type of ‘Vertical’ or ‘Horizontal’. An example of this is at 138.509756063, -34.975420154 where the parcel with cadastre_polygon_pid of ‘cp830d626622a7e’ should be assigned with a strata_type of ‘Vertical’.

Occurrences where spike removal greatly reduces size of the parcel

There are records where the area of a parcel has drastically reduced in size upon the removal of a spike in the geometry. An example of this can be seen at 138.5837373502, -34.8929002242 in South Australia, where the road parcel with cadastre_polygon_pid of ‘cp0a576702cc4db’ has a very small area, in comparison to the original geometry supplied by the jurisdiction, after having a spike removed.

Occurrences of Geoscape Australia parcels created where Lot parcel already exists in SA

In South Australia, there are locations at complex sites where Geoscape Australia parcels have been created where a Lot parcel already exists. The Geoscape Australia parcel should not be created as the existing Lot covers the area of the Geoscape Australia parcel and can be used for representing the strata count information. At 138.6106967727, -34.9261691336 the Geoscape Australia parcel with cadastre_polygon_pid of ‘cpb1cf357085127’ should not be created.

Strata counts not applied for 62 locations in ACT

In the Australian Capital Territory, there are 62 sites where there are Registered strata parcels present but no total_strata_count or horizontal_strata_count is assigned to the base Lot parcel. For example, the base Lot parcel with cadastre_polygon_pid of ‘cp086eb50a3d169’ at 149.09141609, -35.30718633 should have a value of ‘23’ assigned for total_strata_count and horizontal_strata_count.

Occurrences of overlaps in base parcels in ACT

In the Australian Capital Territory, there are parcels with base_parcel = ‘Yes’ where one parcel contains the other parcel. In these scenarios the container Lot parcel should have a base_parcel = ‘Yes’ value and the other, contained parcel, should not be assigned as a base. An example of this can be seen at 148.999462, -35.205932 where the parcel with cadastre_polygon_pid of ‘cp4a6f189f96c0f’ is contained by a parcel with cadastre_polygon_pid of ‘cp576d3e2baacd2’ and therefore should not be assigned as a base parcel.

Occurrences where strata count not applied to stratum locations in ACT

In the Australian Capital Territory, there are locations where a strata count has not been assigned at sites where multiple stratum are also present. An example of this can be seen at 149.1326548, -35.2634898 where a total_strata_count and vertical_strata_count of ‘27’ should be assigned to the base Lot parcel with cadastre_polygon_pid of ‘cp4bb9eab68d5d4’.

Occurrences of strata parcels with incorrect unit value in NT

In the Northern Territory, there are 3 strata parcels that have incorrectly assigned unit values of ‘001’, ‘002’ and ‘003’ for the parcel_id. The parcel_id’s are currently ‘550//11697/001’, ‘550//11698/002’ and ‘550//11699/003’ respectively. These records are located at 130.8530065953, -12.3753733558 with cadastre_polygon_pid of ‘cpfa5e64fdcdfe2’, ‘cpcc06de0368ff8’ and ‘cp4e7926a730daf’. These parcel_ids should instead have parcel_id values of ‘550//11699/1’, ‘550//11699/2’ and ‘550//11699/3’, respectively.

Occurrences where common property strata parcel not created in NT

In the Northern Territory, there are sites where a common property parcel with lot value of ‘0’ is not created. This will not affect strata counts on the base parcel as common property is not counted for this. For example, at 130.8384752474, -12.4498182246 there are 4 strata parcels created. At this site there should be an additional strata parcel created with unit of ‘0’ (parcel_id would be ‘200//1130/0’ for this additional common property parcel).

Occurrences of parcels that have unit part of parcel_id assigned incorrectly in NT

In the Northern Territory, there are 97 parcels with duplicate parcel_id’s due to the unit number part of the parcel_id being incorrectly assigned. For example, at 130.849408619, -12.388793357 there are parcels that have been assigned with a unit part for the parcel_id of ‘404’ where the values should be ‘404’, ‘404B’, ‘404C’ and ‘404D’ for cadastre_polygon_pids of ‘cpaa42fdc2eb39b’, ‘cpd6ae0da64d496’, ‘cp8344a9f3083dc’ and ‘cp91b43229d9091’, respectively. This will cause the total_strata_count at these sites to count these 4 parcels as 1 for the base Lot parcel as they are not differentiated by the alphabetical suffix.

Strata counts at locations where the only strata parcels present have donut holes receiving null count for the base Lot parcel in VIC

In Victoria, strata parcels with inner rings / donuts are excluded from strata count attributes as they most often represent carparks or storage. There are sites where all strata parcels have inner rings / donuts preventing strata counts being calculated. An example of this can be seen at 144.94851078, -37.81014644 where 400 strata parcels are not counted for the base parcel as they all contain donut holes. We have consulted the jurisdiction and based on advice this issue cannot be resolved at this time.

Multiple Geoscape Australia parcels created at 17 sites in VIC

In Victoria, there are 17 sites where Geoscape Australia parcels are created incorrectly. An example of this can be seen at 144.99670577, -37.79617741, where 4 Geoscape Australia parcels have been created, the cadastre_polygon_pids are ‘cp630299cb69579’, ‘cp83b823f82eac8’, ‘cpbc6224d15123e’ and ‘cpb7f2707cf9728’. This relates to Geoscape Australia parcels that have been created for strata parcels that have a plan beginning with ‘LP’ or ‘SP’.

Parcel_ids relating to unidentified records have unsearchable parcel_id in NSW

In New South Wales, there are 6,006 records that have parcel_ids that are not searchable in the land registry. This is because they are undefined parcels (contributor_status = ‘Undefined’) that do not have a lot and have a plan provided by the jurisdiction that is also not searchable (e.g. plan = ‘4083 - 2119 R’). We have included this information in the parcel_id to allow identification of these records. For example, at 149.7986276, -35.8891955 the parcel with cadastre_polygon_pid of ‘cpe309d8986c29d’ has a plan of ‘415 - 3085’ and parcel_id of ‘415 - 3085’ that is not searchable in the land registry.

Road parcels with ‘DP’ plan not being assigned a parcel_id in NSW

In New South Wales, road parcels are not currently being assigned with a parcel_id as they generally do not have lot or plan information that is searchable in the land registry. However, there are 22,282 road records that have a ‘DP’ plan and a populated lot value and can sometimes be searched in the land registry. We will be looking to add parcel_ids for these ‘DP’ road features with populated lot values in a future release, even though some of these records are not searchable.

Occurrences of strata parcels with same parcel_id overlapping in TAS

In Tasmania, there are locations where strata parcels overlap but have the same parcel_id. Geoscape Australia will investigate to see if a dissolve of these polygons to form a single polygon would provide a more consistent representation in comparison with other states. For example, at 147.320947913, -42.881563797 the parcels with cadastre_polygon_pids of ‘cpebf21621323f4’ and ‘cpacc509effb1da’ overlap each other and have the same parcel_id of ‘56829/2´and could potentially be dissolved. If the dissolve is implemented, there will be no change in the strata counts for the base Lot parcel as the number of unique parcel_ids relating to the base Lot parcel will not change.

Water parcels in OT (Jervis Bay) should be removed

In OT (Jervis Bay) there are two parcels with cadastre_polygon_pids of ‘cp00c33ab12e95d’ and ‘cpa03c5a7b5e6a7’ at 150.71848399, -35.12314250 and 150.7037874, -35.1231480 respectively. These are parcels that cover ocean but are not identified as water parcels by the jurisdiction. For consistency in the product, these water parcels will be removed in a future release.

Occurrences of strata overcount where accessory lots not assigned in VIC

In Victoria, there are sites where carparks or storage areas are not flagged as accessory lots. Where this occurs, these parcels will be counted for the strata count attributes for the base Lot parcel. This is causing overcounts for the strata counts on the base Lot parcel as these strata parcels have different parcel_ids than those relating to dwellings. For example, at 144.7937467270, -37.7421506258 there is a carpark parcel with cadastre_polygon_pid of ‘cpb3a181268d05f’ that is incorrectly counted for the strata counts on the base Lot parcel. At this site there are 5 carpark parcels that have not been flagged as accessory lots and incorrectly included in the strata counts for the base Lot parcel. The expected count for the base Lot parcel at this site (cadastre_polygon_pid = ‘cp027b55944be03’) would be ‘5’ instead of the current value of ‘10’.

Occurrences of high strata counts in strata developments with the same plan in VIC

In Victoria, there are sites where all the parcels are on the same plan and are assigned as strata parcels. An example of this can be seen at 144.776291316, -37.910000939 where there are 1,984 parcels in the same development that have a plan of ‘PS611333’ and are strata parcels. At this location we are creating Geoscape Australia parcels based on a dissolve of these parcels with the same plan. This is resulting in many Geoscape Australia parcels being created across the site, each with a total_strata_count of ‘1984’.

Future Considerations

This section outlines enhancements under consideration, but not planned into a specific release. For further details on these please contact Geoscape Australia Support. Contact details are provided in the Introduction section. Enhancements of datasets are ongoing, currently there are no specific changes planned for upcoming releases.

Annex A – Release Counts

Additional, retired and total Cadastre counts and the percent change to the previous release have been listed in the table below.

Statistics November 2023 to December 2023

TABLE		ACT	NSW	NT	OT	QLD	SA	TAS	VIC	WA	TOTAL
cadastre	Additional	1,165	0	158	0	8,459	8,667	710	132,291	0	151,450
	Retired	838	0	23	0	5,161	5,718	600	128,773	0	141,113
	Updated	154	0	4	0	173	360	45	4,846	15	5,597
	Total	194,025	5,791,732	105,521	3,651	3,598,314	1,155,226	395,629	4,705,409	1,793,579	17,743,086
	% Change	0.17%	0.00%	0.13%	0.00%	0.09%	0.26%	0.03%	0.07%	0.00%	0.06%