Set-out Upload File Validator

Checks a set-out point file before controller upload against controller-neutral rules you set: IDs, finite coordinates, 2D or 3D heights, codes and conflicting duplicate IDs. Findings are row-specific and nothing is swapped, rounded or transformed.

100% FreeRuns in your browserBasic

Set-out file and rules

Checks structure and values against controller-neutral rules you set. Nothing is swapped, rounded or transformed.

Project reference (shown on the result)

Paste, or open a local file — it is read in this browser and never uploaded. Limits: 10 MiB, 100,000 records, 200 fields per record and 100,000 characters per field. Nothing is ever truncated — a file over a limit is refused with the reason.

Rules

No vendor profile is offered: passing here is not a compatibility claim for any controller.

From your controller's documentation.

A heuristic against this file's own median position (5+ points). It never swaps anything.

Paste or open the file you plan to upload, confirm the mapping and press Validate file.

One logical record can span lines
Illustrative
One logical record can span linesFour physical lines of a CSV file hold three logical records. The quoted note on record 2 contains a line break, so it continues onto line 3 inside the same cell. The comma inside the quotes on line 4 is text, not a delimiter. The ID 0007 and the decimal 123.4500 are kept exactly as typed.line1234ID,Easting,Northing,Note0007,123.4500,456.78,"two spacesnext line"0008,100.0,200.10,"kerb, east side"← same record4 physical lines · 3 logical records · 4 fields each
Lines 2 and 3 are one record: the quoted line break stays inside the Note cell. A comma inside quotation marks is not a delimiter. 0007 keeps its leading zeros and 123.4500 keeps its decimal places.

Tip: Enter any known values to calculate the remaining results.

Designed to run locally in your browser. Tool inputs are not intentionally stored by Zerdly unless stated otherwise.