Attribute Table Completeness Checker
Checks a pasted attribute table against your schema — required values, types, allowed values and duplicate IDs — and records the GIS review.
Project and review scope
A review of one attribute table against the schema you supply. The table check below runs in this browser on the CSV you paste or load; the rows record what a person verified. Geometry is not inspected — an attribute-only table cannot show whether features are valid.
Attribute table check
Paste or load the attribute table as CSV. Cells are kept exactly as typed (no trimming, no number formatting), and the table is read in this browser only. Limits: 10 MiB, 100,000 records, 200 fields per record.
name, type, required, allowed values, column. Types: text, integer, number, date (YYYY-MM-DD), boolean (true/false). Allowed values are separated by |. Column defaults to the field name (or give a column number).- Note: No table supplied yet. Paste or load a CSV to run the attribute checks; the review rows work without one.
- Note: Geometry: NOT INSPECTED — this is an attribute-only table; spatial validity must be checked in the GIS.
Review status: Not reviewed
Review progress 0 of 15 applicable rows verified (0%)
Outstanding critical findings
- Schema and null-token policy selected — Not started
- Unique ID field mapped and duplicates checked — Not started
- Required values checked without treating 0 or false as missing — Not started
- Geometry reported Not inspected for attribute-only data — Not started
Review rows
Schema and null policy
0/2 verifiedField names follow the agreed schema
Schema and null-token policy selected
Critical
Identifiers
0/3 verifiedA unique ID field on every feature
No blank or duplicate IDs.
No duplicate features for the same real-world object
Unique ID field mapped and duplicates checked
Critical
Required values
0/2 verifiedAll required attribute fields present
Required values checked without treating 0 or false as missing
Critical
Types and domains
0/3 verifiedCorrect data type per field
Text, integer, date, etc.
Domains / pick-lists respected
Values match the allowed set.
Types and domains checked per supplied schema
Consistency
0/3 verifiedUnits consistent within a field
Dates in one consistent format
Spelling and capitalisation consistent
Geometry and metadata
0/2 verifiedMetadata / data source recorded
Geometry reported Not inspected for attribute-only data
Geometry validity needs the spatial data itself; record where it was checked, or why it was not.
Critical
Add your own row
Keep, share and print
Nothing leaves your browser. Saving on this device is optional and only happens when you press it.
How to use this calculator
- Paste or load the attribute table as CSV. Cells are kept exactly as typed — 001 stays 001 and quoted commas or line breaks stay inside their cell.
- Write the schema, one field per line (name, type, required, allowed values), choose the unique-ID column and list any null tokens your project uses, such as -9999 or TBC.
- Read the findings by record and line, download the findings CSV or an annotated copy, then work through the review rows — including geometry, which this table cannot show.
How it works
Each record is checked against your schema: required fields must not be blank or a listed null token, integers and numbers are parsed strictly (no commas, NaN or Infinity), dates must be real YYYY-MM-DD dates, booleans must be true or false, and allowed values are matched exactly. 0 and false are values unless you list them as null tokens.
Duplicate and blank IDs are compared as text, so 001 and 1 are different IDs. Records with the wrong number of fields are skipped and reported, and the counts separate physical lines from logical records.
Geometry is always reported as not inspected — an attribute-only table cannot show whether features are valid. The review rows record what a person verified; progress is verified ÷ applicable rows and “Ready for reviewer” is your declaration, not certification.
Worked example
Three assets, three findings. Schema: asset_id text required; depth number required; status text required, allowed ACTIVE|ABANDONED. Table: 001,0,ACTIVE / 002,(blank),ACTIVE / 001,1.20,active. Line 2 passes — a depth of 0 is a value. Line 3 is flagged “Required value is blank”. Line 4 is flagged twice: “Duplicate ID — first used by record 2” and status “active” differs only in letter case from ACTIVE.
Frequently asked questions
What has actually been checked?
Only what a person marked Verified, with the evidence they recorded — plus the table check, which reads only the CSV you supplied against the schema you wrote. Everything else stays Not started, Action required or Unknown — the checklist never marks a row as checked on its own.
Can I use my own project requirements?
Yes. Write your own schema, ID column and null-token rule; nothing is assumed about which values mean missing. Add your own rows (they get stable IDs), and mark rows that do not apply as N/A with a reason — an N/A without a reason still counts as unresolved.
Does a complete checklist prove the work complies?
No. “Ready for reviewer” is your declaration that the applicable rows are verified and nothing critical is open. It does not validate geometry, topology or the meaning of the values; the data custodian or client decides acceptance.
Is this official course material?
No. It is free study support mapped to surveying course levels — not official North Metropolitan TAFE content or advice. Always follow your lecturer and the official assessment brief, and check your own working.
Related tools
- Survey CSV Cleaner
- Coordinate CSV Schema Builder
- Spatial Metadata Completeness Checker
- GIS Export QA Checklist
- Thematic Map Class Break Helper
- Point List Duplicate and Gap Checker
Explore more in Surveying, Coordinates, GIS & CAD.
Cite this tool
Zerdly. (2026). Attribute Table Completeness Checker. Retrieved from https://www.zerdly.com/tools/attribute-table-completeness-checker/
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.



