Cadastre & Title
Resolve any address or PFI into a complete parcel record — area, frontage, ownership, title reference and encumbrances.
Methodology
Every valuation report begins with the parcel: who owns it, exactly where the boundaries are, and what is registered against the title. The Cadastre & Title module fetches that information for any Australian property in a single call, returning a normalised JSON record plus a parcel polygon ready to drop into a map.
The module reads from the Insitive cadastral graph (12.4M+ parcels, refreshed nightly from state authorities) or, if you operate one, a private endpoint inside your own Land Information System. Either way, the rest of the Valuation App sees the same shape — your downstream methods, overlays and report fragments do not need to know.
When to use it
- First step in every valuation engagement — establishes the subject.
- Pre-populates the report writer’s subject-property section.
- Feeds the Hypothetical Development module with site geometry.
Standards & references
- API ANZVTIP 1 — Valuation Procedures, subject-property identification.
- IVS 102 — Investigations & Compliance.
- State land-titles legislation (TLA 1958 VIC, RPA 1900 NSW, etc.).
Plugin interface
Every method is a self-contained module that plugs into the Valuation App. It exposes a typed input/output schema so it can be invoked from a report writer, a workflow, or your own backend.
- query : PFI | AddressPFI string or Australian address.
- state : StateCodeOptional state filter for ambiguous addresses.
- parcel : ParcelGeometry, area, frontage, depth, lot/plan.
- title : TitleRecordVolume, folio, owner type, registered encumbrances.
- lga : stringLocal Government Area name.