Annex A - User Guide

Contributor IDs and how to find valuation information

The contributor_id is the property identifier provided by the jurisdiction that is searchable for land valuation and rates purposes.

An example of this can be seen for the Queensland property parcel (orange polygon) with contributor_id of ‘40056701’ (white text) located at 148.18481°, -25.51161° shown on the image below.

contributor_id example.

Queensland property parcel with © Aerometrex Ltd Aerial Imagery [Aerometrex, 2023].

Note

Properties with base_property = ‘Yes’ are the only searchable properties in Queensland.

The valuation for this parcel can be found through the Queensland land valuation website: https://www.resources.qld.gov.au/qld/environment/land/title/valuation/search.

To do this, input the contributor_id of the parcel (40056701) into the search bar as this is the Property ID. The returned valuation information for this property is shown below.

Queensland land valuation website.

Screenshot taken from Queensland land valuation website [Queensland Government, 2024]. Available under CC BY 4.0 licence.

Base polygons and how they represent a non-overlapping property layer

Base property features are properties that have been flagged with the intention of providing a non-overlapping layer representation of properties. A user can simply identify these records by selecting where base_property = ‘Yes’.

Below, the two images show the property layer with no filter applied (left), as well as only where base_property equals ‘Yes’ (right).

No filter applied base property example. 'Yes' Filter Applied base property example.

No Filter applied.

Filtered on base_property = ‘Yes’.

Below, the base property layer is shown for a site in Queensland (orange polygons) with the searchable contributor_ids labelled in white text.

Linking Cadastre and Property

The property_cadastre table provides a linkage between Property and Cadastre through the property_pid and cadastre_pid.

Property to Cadastre

For example, at 130.84019138, -12.43302423 in the Northern Territory, there is a property polygon with a property_pid of ‘prpafc82e6b6d7e’ and contributor_id of ‘CUFT/778/934’. When this property_pid is searched in the property_cadastre table, the property_pid is shown to link to three cadastre_pids (shown below).

property_cadastre example records.

The three cadastre_pids relate to three cadastre records, with the related parcel_ids shown below.

property_cadastre cadastre records.

Cadastre to Property

An example of the link in the other direction can be seen for the Victorian cadastre polygon at 144.962222249, -37.772255012 with cadastre_pid of ‘cad7de4f40ee0d9’ and parcel_id of ‘1TP619430’. This cadastre_pid links to 16 property_pids (shown below) in the property_cadastre table.

Cadastre to Property example.

These 16 property_pids relate to 16 property records, with related contributor_ids shown below.

Cadastre to Property example property records.

Linking CadLite to Property

A linkage table has been included to facilitate the transition between the CadLite Property theme and the new Property product. This table enables the link between the Property_Point and Property_Polygon features in CadLite to their corresponding Property feature where possible. The link was created by matching the CadLite jurisdiction_id with the Property contributor_id, supported by a spatial comparison where there was more than one match resulting from the join.

Property to Cadlite linkages.

If a property does not have a record in the linkage table, a link between CadLite and Property could not be created. This occurred where:

  • There was no match between the CadLite jurisdiction_id and a Property contributor_id. This may happen if:

    – The feature is no longer represented in Property, - The CadLite jurisdiction_id no longer exists, – The Property contributor_id is new, or – The values could not confidently be joined during the linking process

  • There were multiple matches between a CadLite jurisdiction_id and a Property contributor_id and:

    – The spatial check did not support the join, or – The spatial check could not identify a one-to-one link