Local Storage
Komand stores selected public records in a local database so users can search, filter, and map records in a quicker and easier way than the original source website.
The local database is used to make repeated checking practical. A user may need to filter by suburb, LGA, date range, price, project status, project type, land area, or project number several times during one session. Preparing public records locally means those filters can run together and return a consistent result set without requiring every page view to re-query the original source.
Local storage also allows Komand to keep useful display fields together. For example, a planning project can be shown with its project number, status, location text, map point, base application grouping, and source link in the same interface. A sales record can be displayed with formatted price, dates, area, zoning, and locality fields. The stored copy is not treated as more authoritative than the source; it is a working copy for search and display.
Planning Locations
Planning records may include source coordinates, street addresses, or both. Where a street address is available, Komand may compare the source coordinate with a geocoded address point to identify records that may need review.
Location handling is deliberately cautious. Source coordinates are kept when they are available because they come from the project source material or an associated official dataset. Address-based coordinates are kept separately because they are derived from address text. Keeping both values separate makes it possible to compare them, review differences, and avoid overwriting a source point without evidence.
When a record is reviewed, Komand can store a corrected display location for the map. That reviewed point is a display improvement for this site, not a change to the official project record. The original source values remain important because they explain why the record appeared where it did and allow later review if the source record changes.
Geocoded Points
Geocoded points are estimates based on address text. They can be affected by incomplete addresses, broad site descriptions, road corridors, rural properties, and third-party geocoder limits. Users should treat them as a location aid, not an official project boundary or approval location.
Komand uses geocoding mainly to help find possible location errors and to make records easier to browse on a map. A clean street address may geocode well. A description such as a road upgrade, water pipeline, transmission corridor, mining area, regional locality, or large development precinct may not. The point shown on the map should therefore be read alongside the project name and official source link.
Distance comparisons are used as review signals, not automatic corrections. A large distance between a source point and a geocoded point can be caused by a bad address, a broad address, a project that genuinely covers a wide area, or a source coordinate that points to an administrative reference location. The review process is designed to surface those cases for checking rather than hide them.
Project Modifications
Planning modifications are grouped with their base application where the project number makes that relationship clear. This keeps related records together and reduces duplicate markers on the map.
A modification record often belongs with the original project. If every modification is plotted as a separate marker at the same coordinate, the map becomes slower and harder to use, and the top marker can hide the other records. Grouping modifications by base application keeps the map clearer while still allowing users to open the related modification records from the project list.
This grouping is based on the project number pattern where it is clear enough to identify the base application. It does not merge unrelated projects simply because they are nearby. If two different base projects share the same coordinates, they remain separate records; the map may show overlapping or slightly offset markers depending on the display context.
Interpretation
Komand does not decide whether a property is suitable, valuable, compliant, or affected by a planning matter. The site is intended to help users find records for further checking.
Property sales and planning records are different kinds of evidence. Sales records describe completed market activity. Planning records describe proposals, assessments, determinations, modifications, and major infrastructure or development activity. Looking at both together can help users understand a place more clearly, but the records still need context.
Important decisions should not be made from one field or one map point. Users should check official documents, current planning controls, title details, survey information, development consents, agency notices, and professional advice where relevant. Komand's role is to reduce search friction and make public records easier to inspect.
Related Pages
For more context, read the data sources page, the NSW property sales guide, and the SSD and SSI planning guide.