GIS Export QA Checklist
Records source-to-export GIS QA by destination format, compares record counts and checks pasted GeoJSON coordinates against RFC 7946.
Project and review scope
A QA record for one GIS export, from source to the receiving system. It records what a person checked and how; it does not convert data, validate geometry or open any file except GeoJSON you paste or load into the optional check below.
Formats, counts and field names
Choose the source and destination formats in the project details to see the capability matrix. Counts are the ones you read from the source and from the reopened export.
- Note: Choose source and destination formats to see what each can carry.
GeoJSON check (optional, read locally)
If the export is GeoJSON, paste or load it to count features and test coordinate ranges against RFC 7946 (WGS 84 longitude, latitude). The file is read in this browser and never changed. Geometry validity is not checked.
Review status: Not reviewed
Review progress 0 of 17 applicable rows verified (0%)
Outstanding critical findings
- Correct CRS assigned (not just assumed) — Not started
- CRS and axis semantics declared — Not started
- No invalid or self-intersecting geometry — Not started
- Record and field counts compared — Not started
- Export reopened independently and findings recorded — Not started
Review rows
12 row(s) do not apply to the project settings above; they are hidden but kept in the record.
Source and destination
0/1 verifiedSource and destination format versions recorded
Coordinate reference
0/4 verifiedCorrect CRS assigned (not just assumed)
Critical
All layers in the same CRS
Datum / projection stated
CRS and axis semantics declared
Critical
Geometry
0/3 verifiedNo invalid or self-intersecting geometry
Record the tool and check you ran; this checklist cannot see the geometry.
Critical
No unintended duplicates
Topology checked where required
Attributes
0/4 verifiedKey fields populated (no blanks)
Field names and types consistent
Domains / codes valid
Truncation, null and encoding effects reviewed
Destination format
0/2 verifiedCorrect format for the recipient
Shapefile, GeoPackage, GeoJSON…
All sidecar files included (e.g. .prj)
Round-trip verification
0/2 verifiedRecord and field counts compared
Critical
Export reopened independently and findings recorded
Critical
Metadata
0/1 verifiedMetadata: source, date, accuracy, contact
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
- Enter the layer, the source and destination formats, the CRS, geometry type, schema, receiving system and export date. Rows for the destination format appear automatically.
- Compare the record and field counts you read from the source with those of the reopened export. For Shapefile, paste field names to see which exceed 10 characters or collide.
- If the export is GeoJSON, paste or load it to count features and test coordinate ranges, then work through the review rows and export or print the record.
How it works
The capability matrix shows, as orientation, what each format carries: required files, field-name limits, geometry types per layer, how the CRS is stored, null support and text encoding. Confirm against the receiving software's documentation.
The GeoJSON check reads the file locally without changing it. RFC 7946 GeoJSON is WGS 84 longitude, latitude in decimal degrees and has no crs member, so positions outside ±180 / ±90 are reported as projected coordinates and a crs member is flagged. Pairs inside both ranges cannot prove the order or datum.
Nothing here converts data or validates geometry. Record and field count mismatches block “Ready for reviewer”; progress is verified ÷ applicable rows and the readiness label is your declaration, not certification.
Worked example
MGA coordinates in a GeoJSON export. A 120-feature layer in GDA2020 / MGA zone 50 is exported to GeoJSON without reprojecting. The check reads positions such as 391234.5, 6464321.2, reports them outside the longitude ±180 / latitude ±90 range as projected coordinates, and flags the file's crs member as not part of RFC 7946. The feature count matches the 120 source records. Choosing Shapefile instead adds sidecar and field-name rows: INSTALL_DATE_1 (14 characters) collides in its first 10 characters with INSTALL_DATE_2.
Frequently asked questions
What has actually been checked?
Only what a person marked Verified, with the evidence they recorded — plus the counts you entered and, if supplied, the GeoJSON file read in your browser. 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. Record your receiver's format and CRS requirements in the project details and evidence fields. 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 or confirm the receiving system accepts the data; that is for the data custodian and receiver.
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
- CRS Job Setup Checklist
- Attribute Table Completeness Checker
- Spatial Metadata Completeness Checker
- Datum and Projection Job Sheet
- Map Purpose and Audience Checklist
- Survey Plan Submission QA Sheet
Explore more in Surveying, Coordinates, GIS & CAD.
Cite this tool
Zerdly. (2026). GIS Export QA Checklist. Retrieved from https://www.zerdly.com/tools/gis-export-qa-checklist/
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.