NSW Property Sales
Sales records are sourced from NSW Valuer General property sales data. These records can include contract dates, settlement dates, prices, property identifiers, land area, and locality details where available.
The sales files are public record datasets. They are useful for finding completed transactions and comparing recorded sales activity across suburbs, LGAs, dates, property types, and land sizes. Komand does not create the sale record, set the sale price, or decide whether a transaction should be included. The site prepares the records for searching and filtering, while the NSW Valuer General remains the source to check for official publication details.
Some sales records are more useful than others for comparison. A standard residential sale with clear address, price, date, and land area fields is usually easier to interpret than a partial interest, multi-lot sale, unusual property type, or record with missing land details. Komand keeps those records visible where possible because excluding them can hide useful context, but users should read the fields carefully before treating a sale as comparable evidence.
NSW Planning Records
Planning records are drawn from public NSW Planning sources, including State Significant Development and State Significant Infrastructure project pages. Komand stores selected public metadata locally so the map and filters can run quickly.
Planning records can include project numbers, project names, project type, assessment status, location text, proponent names, determination dates, modification references, and links to official project pages. The exact fields vary between records. Older projects, modified projects, corridor projects, and projects with broad site descriptions may have less consistent location information than newer records.
Komand does not replace the NSW Planning Portal. The planning map is intended to help users find potentially relevant projects faster, see nearby activity, and move from a map point back to the official record. If a project is important to a decision, users should open the official project page and review the documents, dates, status, assessment material, and any agency notices directly.
Geocoding
Where a planning record includes a street address, Komand may use geocoding to estimate an address-based map point. This helps compare the address location with source coordinates where both are available.
Geocoding is helpful but imperfect. Address text may describe a road corridor, a broad locality, a large rural parcel, a project area, a lot and DP, or a sentence copied from source material rather than a clean street address. In those cases an address-based point can land at an approximate location, the centre of a road, a locality centroid, or no useful point at all. Komand treats geocoded locations as checking aids rather than official boundaries.
When both source coordinates and geocoded coordinates are present, Komand can compare the two and flag records that appear to need review. A difference does not automatically mean either point is wrong. It means the record deserves a closer look, especially where the project is near a search area or where the official source text is unclear.
Update Cadence
Sales data is checked on a scheduled basis. Planning data is refreshed from public sources using controlled imports. Some official records may change before the local copy is updated.
Weekly sales files are normally checked after the expected publication window. If the source file is not yet published, or if source access is temporarily unavailable, the next scheduled run or a controlled manual import may be used. Komand records import results so missed updates can be investigated instead of silently treated as no data.
Planning records are refreshed separately from sales records. Planning updates can involve new projects, status changes, project modifications, revised locations, and source-page changes. Because planning records come from public pages rather than a single stable bulk sales file, those updates may need extra checks before they are shown in the map.
Limits
Public datasets can contain missing fields, changed project names, duplicate references, approximate coordinates, or delayed updates. Komand highlights source links and location review signals where possible, but users should verify important facts with the official source.
Records may also be republished, corrected, renamed, or grouped differently by the source agency over time. A sale appearing in a later file does not always mean a brand-new transaction. A planning modification may share a location with its base project. A map point may represent a project reference location rather than the full physical extent of works.
For that reason, Komand is best used as a starting point for property information work. It can reduce the time needed to find relevant records, but it cannot confirm legal title, valuation, development approval, zoning entitlement, acquisition impact, construction timing, or whether a specific property is affected by a project. Those questions should be checked with the official source material and, where necessary, a qualified professional.
Related Pages
For practical use, read the NSW property sales guide, the SSD and SSI planning guide, and the methodology page.