Point Code Parser
Counts survey feature codes from the column you map, keeping every raw spelling. Choose case and space rules, split compound codes if you want, check against a code dictionary and approve any clean-up before it changes a file.
Point file and code rules
Counts the code column you map. Raw codes are kept exactly; the comparison policy only decides what is counted together.
Paste or open a point file, map the code column and press Parse codes.
How to use this calculator
- Paste the point file or open it, check the delimiter and header toggle, and map the code column (and optionally the ID column) in the preview.
- Choose the comparison policy — case-sensitive or not, and how spaces are treated — and whether compound codes are split. Optionally paste or import a dictionary of known codes.
- Press Parse codes. Read the frequency bars and table, the unknown and suspicious codes, open the source rows for any code, and approve any proposed rewrites before downloading a corrected file.
How it works
The code is read from the column you map — never from the last token on the line — so a quoted description such as "gum, 0.6 m trunk" cannot shift it.
Each raw code is kept exactly. A separate comparison key applies the selected policy: case-insensitive comparison upper-cases the key, and the space options trim or collapse it. TREE and tree are counted together only under the case-insensitive policy; the raw spellings are still listed.
Blank codes form their own group. With compound splitting on, each code field is split at the separator characters you set, and both the point count and the token count are reported.
Suspicious variants are spellings that differ only by case or spaces, unknown codes one character away from a dictionary code, and rare codes one character from a much more common one. Proposed rewrites change only the code field of rows you approve.
Worked example
TREE, FENCE, TREE, KERB. Four points coded TREE, FENCE, TREE and KERB give 3 distinct codes over 4 points: TREE ×2, FENCE ×1, KERB ×1. Add a fifth point coded tree: case-sensitive comparison keeps it separate and flags it as a case variant; case-insensitive comparison counts TREE ×3 and lists the spellings “TREE” ×2 and “tree” ×1.
Frequently asked questions
Why choose the code column?
Exports differ: some put the code last, others put a description or attribute after it. Mapping the column means a quoted comma or an extra attribute can never move the code you are counting.
Are compound codes split?
Only if you turn splitting on and choose the separator characters. The result then shows both the number of points and the number of code tokens.
Will codes be rewritten?
Not unless you approve a proposal. The counts never change your data, and an approved rewrite changes only the code field of the rows listed in the before-and-after table.
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
- Linework Code Cheat Sheet Builder
- Survey CSV Cleaner
- Point List Duplicate and Gap Checker
- Point List Renumber Tool
- Coordinate CSV Schema Builder
- Coordinate Import Template Generator
Explore more in Surveying, Coordinates, GIS & CAD.
Cite this tool
Zerdly. (2026). Point Code Parser. Retrieved from https://www.zerdly.com/tools/point-code-parser/
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.



