How to read Districts flood and planning data

Zone code and name as recorded in the state or council planning layer, with the retrieval date. Overlays listed by category (flood, bushfire, heritage, environmental and others) with the layer name where the source gives one. These are source data. Districts does not interpret what a zone or overlay permits. The scheme text does that. See zoning and overlays.

Where a flood overlay has been retrieved, Districts intersects it with the official parcel and reports the share of the lot affected, labelled as a Districts calculation on official layers. Split GIS tiles for one overlay are merged so the result is one figure. Boundary-only touches are flagged. The result is a screen: a mapped flood-planning layer covers that share of the parcel. It does not state floor level, depth, velocity or premium. Every flood result on the page says it is not a flood certificate. See flood and the planning and flood methodology. A 4 per cent intersection on a large lot can miss the dwelling. An 80 per cent intersection usually does not. Write the share, then look at where the building sits. The percentage alone is not the story.

Applications recorded against the parcel in the register, with description, status and a link to the source. Separate from the nearby pipeline. Where the register has no adapter or was not queried, this is unknown. See this-lot DA history.

A listing that says “not flood affected” is recorded as a listing observation. It does not change the official result. When the two disagree (listing says no flood, overlay intersects 40 per cent of the lot) both are shown and the overlay is the one to act on. When the official layer is unknown and the listing says something, the hint is shown as a hint, with low confidence, and the check stays unknown.

These mistakes skip retrievedAt or the scheme text.

• Reading not loaded as no overlay.
• Reading floodShare as how deep the water gets.
• Using the listing hint when the official layer disagrees.
• Treating zone.name as permission.
• Ignoring the retrieval date on a layer that councils update weekly or fortnightly.

A 4 per cent intersection on a large lot can miss the dwelling. An 80 per cent intersection usually does not. Write the share, then look at where the building sits.

They do not establish a floor level, a BAL, a heritage significance finding, or a clean-soil certificate. They do not replace the planning certificate or vendor statement used in that state. They do not tell you what an insurer or lender will do. Screening-level government maps often say they are indicative. The page repeats that limit.

Re-open the official portal for that state. Write the date. Order the certificate or vendor statement used in that jurisdiction through your conveyancer. Ask an insurer about the address. See how to verify. If floodShare is loaded and the listing is silent, believe the overlay and ask the insurer. If floodShare is not loaded and the listing is loud, believe neither until the layer is retrieved or council flood information is in the file. retrievedAt is part of the finding. A layer retrieved last year is a last-year screen.