Supported files and exports
A synthetic-beta register of bundled fictional examples, dormant real-file paths and generated outputs. No client file is requested.
Demo scope and exports
Bundled fictional sources remain visible so the demo can be checked without client data.
Exported outputs need user review before downstream use.
Pick a bundled fictional example to explore. Real report, point and PDF files are not requested during the synthetic public beta.
Load the bundled fictional report in Report Reader; no client report is needed.
Open the report exampleLoad the built-in fictional point rows; real-file selection stays disabled.
Open the point exampleExplore the bundled linework example and its advisory generated outputs.
Open the map exampleOpen the bundled PDF evidence set; no client PDF is needed.
Open the PDF exampleThe examples are bundled and fictional. Real report, point and PDF selection stays disabled; the dormant limits below are reference information, not an invitation to provide files. See the documentation for how each tool works. Every result stays advisory and unverified; registered surveyor review remains required.
Format matrix
Direction matters: an accepted input, narrow context file, generated export and fixed demo are different capabilities.
During the synthetic public beta, browser file examples are demo-only and authenticated project inputs are unavailable. Dormant upload limits remain visible as future-scope reference only. Every output remains advisory and requires project review.
Synthetic examples · browser-local demos
These public tools load bundled fictional examples. Real report and point-file selection is disabled during the synthetic public beta.
| Format | Direction | Surface | Status | Enforced limit / budget | Processing & automated checks | Context & outputs | Boundary |
|---|---|---|---|---|---|---|---|
| .rpt / .txt | Demo | Public Report Reader | Demo | Bundled fictional .rpt / .txt example only; client-file selection is disabled | Loads the bundled fictional report in the browser. No customer file is selected, stored or sent. Checks Labelled warning/error, misclosure, residual and sigma lines; setup metadata; F1/F2 spread; parse confidence and unparsed-line fallback. | Synthetic report walkthrough with source-line references. It is not a review of a visitor's report. Outputs On-screen source-linked summary · Local advisory HTML summary | Demo-only during the synthetic public beta. Do not select, paste or send a client report. |
| .csv / .txt point file | Demo | Point File Validator | Demo | Built-in fictional point-row example only; client-file selection is disabled | Loads the built-in fictional point rows in the browser. No customer point file is selected, stored or sent. Checks Malformed rows, duplicate IDs, coordinate order/range, coincident points and optional feature-code context. | Synthetic point-row walkthrough covering id, E, N, optional RL and optional code fields. Outputs On-screen advisory findings | Demo-only during the synthetic public beta. Do not select, paste or send a client point file. |
Unavailable · real-file project inputs
Authenticated project intake is dormant during the synthetic public beta. The rows document future real-file-pilot scope only and do not invite files.
| Format | Direction | Surface | Status | Enforced limit / budget | Processing & automated checks | Context & outputs | Boundary |
|---|---|---|---|---|---|---|---|
| .fld | Not accepted | Project workspace / authenticated QA API | Not accepted | Unavailable during the synthetic public beta | Real-file project intake and processing are disabled in this release. Checks No checks run on customer files in the synthetic public beta. | Use the bundled fictional demonstrations instead; no client file is needed. Outputs None | This is dormant real-file-pilot capability, not an active public input or invitation. |
| .rpt / .txt | Not accepted | Project workspace / authenticated QA API | Not accepted | Unavailable during the synthetic public beta | Real-file project intake and processing are disabled in this release. Checks No checks run on customer files in the synthetic public beta. | Use the bundled fictional demonstrations instead; no client file is needed. Outputs None | This is dormant real-file-pilot capability, not an active public input or invitation. |
| Not accepted | Project workspace / PDF report workflow | Not accepted | Unavailable during the synthetic public beta | Real-file project intake and processing are disabled in this release. Checks No checks run on customer files in the synthetic public beta. | Use the bundled fictional demonstrations instead; no client file is needed. Outputs None | This is dormant real-file-pilot capability, not an active public input or invitation. |
Context and generated outputs
These rows are not survey-file ingestion promises. They describe narrow browser context or files generated from user-drawn or caller-supplied geometry.
| Format | Direction | Surface | Status | Enforced limit / budget | Processing & automated checks | Context & outputs | Boundary |
|---|---|---|---|---|---|---|---|
| .csv feature-code table | Demo | Map Linework code dictionary | Demo | Bundled fictional feature-code context only during the synthetic public beta | Uses fictional feature-code context in the browser; no customer code register is requested. Checks Bounded CSV structure and field-length checks only. | Supplies the fictional legend used by the synthetic linework example. Outputs Browser-local feature-code table · Feature-code CSV export | Demo-only during the synthetic public beta. This does not invite a customer code table or survey file. |
| .csv / .dxf / .geojson / .kml | Export | Map Linework browser / project export API | Now + pilot | Browser-local export; server route: 1 MiB request, 500 geometries, 50,000 vertices and 8 MiB output | Generated from user-drawn browser geometry or caller-supplied structured project geometry. Checks Geometry shape, finite coordinate, CRS representation and bounded-output safety checks before server publication. | CSV/DXF use supplied projected coordinates; GeoJSON/KML require supplied geographic coordinates on the server path. Outputs CSV · DXF · GeoJSON · KML | Export-only. These four formats are not accepted as project uploads, and the server export route does not transform supplied coordinates. |
| Fixed synthetic QA dataset | Demo | Public QA demo | Demo | Fixed fictional payload; no file selection | Deterministic structured checks on bundled fictional data. Checks The structured demo rule set only; it is separate from FLD/RPT/PDF file parsing. | Safe walkthrough of advisory finding presentation. Outputs On-screen advisory findings · Optional plain-language explanation | No file is uploaded. Demo behavior is not evidence that another file format is accepted. |
Not accepted or not performed
These boundaries are explicit so a generated-output format or dormant parser code is not mistaken for a live ingestion path.
| Format | Direction | Surface | Status | Enforced limit / budget | Processing & automated checks | Context & outputs | Boundary |
|---|---|---|---|---|---|---|---|
| OCR / text-derived checks from image-only .pdf | Not accepted | PDF processing | Not accepted | Unavailable during the synthetic public beta | Real-file project intake and processing are disabled in this release. Checks No checks run on customer files in the synthetic public beta. | Use the bundled fictional demonstrations instead; no client file is needed. Outputs None | This is dormant real-file-pilot capability, not an active public input or invitation. |
| .csv / .dxf / .geojson / .kml linework import | Not accepted | Project upload / Map Linework | Not accepted | — | No live survey-linework ingestion route is wired for these formats. Checks None as uploaded linework files. | Use the drawing workspace or the structured project export request instead. Outputs None | A DXF parser module exists in the codebase but is not connected to an accepted upload route. |
| .job / .jxl / .dc / .dwg / LandXML or other XML | Not accepted | Core file QA | Not accepted | — | No accepted parser route. Checks None. | Convert to an explicitly accepted input only when that conversion is appropriate for the project. Outputs None | File discovery or archive presence does not establish product support. |
Download synthetic references and output examples.
Use fictional data to inspect the workflow without real client material. A downloadable example does not make its extension an accepted input.
- .rptReport Reader — synthetic .rptDownload
- 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.
- .txtReport Reader — synthetic .txtDownload
- 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.
- .csvMap Linework — synthetic .csvDownload
- 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.
- .geojsonMap Linework — synthetic .geojsonDownload
- 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 setDownload
- 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.
Review rules that apply to every format
SurveyMarkup keeps file handling visible, but the user remains responsible for professional review.
No OCR inference
A valid image-only PDF can remain visual review material, but imagery does not become extracted survey values or text-derived checks.
Inputs and outputs stay separate
CSV, DXF, GeoJSON and KML map exports are generated files, not project-upload formats.
Professional review remains
SurveyMarkup does not determine legal or cadastral status and does not provide coordinate assurance or professional sign-off.