Skip to main content
Public samples · fictional data

Synthetic samples for a safe first look.

Download fictional report, linework and evidence examples, plus starter inputs for three browser-local field tools. This page has no uploader and requests no real client data.

Files
08
Workflows
06
Data
Fictional only
Upload controls
None
Download register

Use the matching fictional file, then open its tool.

Each direct download is registered below with its purpose, likely review cues and next step. The files contain synthetic coordinates or evidence only and are not survey deliverables.

Synthetic downloads and starter inputs
README
PUBLIC BETA — ADVISORY ONLY. Not for survey deliverables. These files are synthetic — use them to try the tools without uploading real or confidential client data. Every result is advisory and unverified; a registered surveyor must confirm it.
  • Demonstrates
    A full plain-text reduction report with instrument, station, misclosures, residual and control points.
    May trigger
    Missing face observation, unclear setup method, high residual (UNVERIFIED), pole-height (ADVISORY) and parse-confidence warnings.
    Next step
    Review the parsed metadata and advisory panels, then export the HTML summary. Every professional decision remains with the registered surveyor.
  • Demonstrates
    A simpler plain-text report with a single caution line and a clean error count.
    May trigger
    One advisory warning line; low overall warning count.
    Next step
    Compare the extracted summary lines against the original; treat all output as advisory.
  • Demonstrates
    Coded survey points (KERB, BLDG) with fictional MGA-style coordinates.
    May trigger
    Missing feature code, a near-duplicate point and an open polygon for the data-quality checks to flag.
    Next step
    Run the field-data QA checks and review the export-readiness checklist before any export.
  • Demonstrates
    The same synthetic linework as GeoJSON features, carrying the advisory note.
    May trigger
    CRS / coordinate correctness must be confirmed by a surveyor before downstream use.
    Next step
    Inspect the geometry in your GIS, but confirm CRS and coordinates before relying on it.
  • .jsonPDF Markup — synthetic evidence set
    Demonstrates
    Four evidence items: one linked, one unlinked, one needs-review and one missing, with a measurement and reviewer notes.
    May trigger
    NEEDS REVIEW (missing + needs-review), ADVISORY (unlinked) and UNVERIFIED (measurement) advisories.
    Next step
    Review linked vs unlinked evidence and the missing-evidence advisories, then export the evidence summary.
  • .csvSet-out Sheet — synthetic starter points
    Demonstrates
    A small fictional design-point list with point IDs, MGA-style coordinates and optional reduced levels.
    May trigger
    No intentional input warning; station, backsight, datum and project context still need independent confirmation.
    Next step
    Paste the rows into the design-points field, enter a fictional station and backsight, then review the browser-local sheet.
  • Demonstrates
    A closed fictional four-corner boundary using MGA-style Easting and Northing values.
    May trigger
    The repeated first row records explicit closure; the coordinates and boundary order remain fictional working data.
    Next step
    Paste the coordinate rows into Lot Area, then review the area, perimeter, orientation and per-leg working.
  • .csvPoint File Validator — synthetic starter input
    Demonstrates
    The fictional rows used by the built-in example, including IDs, MGA-style coordinates, levels and feature codes.
    May trigger
    Duplicate-ID, coordinate-order, extent, proximity, unreadable-row and code-table review findings.
    Next step
    Use Load worked example in the synthetic public beta; keep this download as a format reference and do not provide a real client file.