Runs a TerraScan-style macro: noise → ground → water → bridges → wires → vehicles → fences → buildings (trees on roofs separated) → structures → vegetation → small structures. Every step is a measurable rule; untick any you don't want. Points you classified by hand are kept.
Output classes
ArcGX utility spec (veg 4, structure 20, conductor 21, shield 22, guy 23)
ASPRS (veg 5, tower 15, wire 14, guard 13)
Edit specification…
Allow editing protected classes by hand
Never change classes
Steps
Isolated / noise points
Ground (+ 0–1 m low points)
Water 9
Bridges 17
Wires (conductor, shield, guy)
Vehicles (cars, trucks, trailers) 16
Fences & walls 11
Buildings (planar roofs/walls)
Separate trees from houses they touch
Structures (poles, towers, light posts)
Vegetation
Small structures (sheds, signs) 5
Substations (bus work, transformers) 26
Keep my manual edits
Run auto-classify as soon as a file is opened
Parameters
Reset parameters
Run auto-classify
After auto-classify, every detected object is measured and checked against simple rules — size, height, single/multiple returns, distance to wires. Objects that break a rule are listed below with the rule, the numbers and a suggested class. You decide : accept, keep, or open it and edit.
1 · Rule check of objects
Structures
Wires
Buildings
Vehicles
Other objects
Trees
Report trees closer to a wire than m
Run the check after every auto-classify
Check objects
2 · Needs human review
Accept all suggestions
Nothing yet.
3 · Accuracy
A LAS/LAZ file holds no right answers, so accuracy needs either a classified reference of the same area (a tile an operator finished, or national LiDAR) or a spot check : random points from every class that you mark right or wrong.
Reference in ASPRS codes
Reference in output-scheme codes
Load reference…
Remove
Points per class
Start spot check
Right (Y)
Wrong (N)
Skip (S)
Back
Stop
The rules
Building lower than the minimum building height, or with a roof smaller than the minimum area (→ vehicle / unclassified), or with many multiple returns (→ vegetation).
Tree that is tall and thin with few multiple returns (→ structure), or a wide one with single returns only (→ building), or close to a wire (clearance report).
Structure shorter than the minimum, unusually wide, or with no wire nearby.
Wire piece that is short and sparse (→ vegetation), or that comes down near the ground.
Vehicle that is unusually long or high.
Other object that looks like a building, a vehicle, a pole next to a wire, or vegetation.
Limits come from Automate → Parameters .
Which class? Object guide
Where common objects belong under the active output scheme, from the ArcGX spec (Scope_Lidar ) and ASPRS LAS 1.4. Click a row to make it the To class.
Individual objects built from the current classes: buildings, trees, poles and wires. Click a row to zoom to it.
Rebuild objects
All kinds
Building Tree Structure Wire Vehicle Object
Set class
Remove
Check rules
Export CSV
Export GeoJSON
Add structure top / bottom synthetic points (classes 46 / 47) for structures ≥ 10 m (33 ft) tall to the exported LAS
Fix stray points near objects
Use this when a file is already classified and only some points are wrong. Example: a few points on a wire are still class 0 (never classified). You say which objects, how close, which wrong class and what it should become. The tool shows exactly what would change before anything is applied.
How to use it (example)
Step 1: tick 14 Wire – conductor (and 13 Wire – guard if the file has points in it). The list shows the classes found in your file.
Step 2: leave the distance at 1.5 m. Points farther away are never touched.
Step 3: tick 0 Created, never classified .
Step 4: keep "the same class as the object next to them". Class 0 points next to a conductor become 14, next to a guard wire 13, next to a tower 15.
Press Preview : the points that would change stay bright, everything else is dimmed, and the numbers are listed. If it looks right press Apply . Undo (toolbar) restores it.
2. How close? Only points within this distance of the object change.
3. Which points are wrong? Tick the classes to fix. A lock means the class is protected and is never changed.
tick the unclassified classes
4. Change them to
the same class as the object next to them
one class:
Preview
Apply
Clear
Tell Claude in plain words what to change in the loaded LAS/LAZ — for example "make object 12 a building" , "everything in class 1 above 3 m is vegetation" or, with an area selected (K), "this is a shed, make it class 5" . Claude edits only through the app's tools; every change is one undo step (Ctrl+Z).
What is sent to Anthropic
Sent , straight from this browser to api.anthropic.com with your key: your messages and attached images; pictures of the current view (when ticked, when you attach an image, or when Claude asks for one) and pictures of single objects; with Review selection in the area panel, drawn 2D plan / side-section and 3D pictures of the selected points, close-up pictures of the detected objects in it, and per-class statistics (heights, intensity, geometry) and rule-check findings for them.
Scene data: the file name, point count, units and the file's coordinate extent; point counts per class; the object list (kind, class, size, height and centre coordinates in the file's coordinate system ); the selected area's bounding box and summary.
Not sent: the LAS/LAZ file itself or individual point records.
Requests use your Anthropic API account: they are billed to it and handled under your API account's terms.
Claude API key
API key
Remember the key in this browser
Forget key
Ask me before Claude removes objects or changes many points
Get a key at console.anthropic.com. The key is only ever sent to api.anthropic.com, and requests are charged at your account's API prices.
Edit with a prompt
Before your first message to Claude
Sent , straight from this browser to api.anthropic.com with your key: your messages and attached images; pictures of the current view (when ticked, when you attach an image, or when Claude asks for one) and pictures of single objects; with Review selection in the area panel, drawn 2D plan / side-section and 3D pictures of the selected points, close-up pictures of the detected objects in it, and per-class statistics (heights, intensity, geometry) and rule-check findings for them.
Scene data: the file name, point count, units and the file's coordinate extent; point counts per class; the object list (kind, class, size, height and centre coordinates in the file's coordinate system ); the selected area's bounding box and summary.
Not sent: the LAS/LAZ file itself or individual point records.
Requests use your Anthropic API account: they are billed to it and handled under your API account's terms.
Send to Claude
Cancel
You are asked once per browser. "What is sent to Anthropic" above shows this again.
Send a picture of the current view with my message (on automatically when an image is attached)
New conversation
Reading settings
Units
Auto (CRS / .prj / guess)
Metres
International feet
US survey feet
Classification byte
8-bit (TerraScan, codes 0–255)
5-bit + flags (ASPRS, codes 0–31)
Re-read file
Open the .prj together with the LAS/LAZ (multi-select) to take units from it. Processing is done in metres; the file's coordinates are never modified.
Identified point
Use the Identify tool and click a point.
Activity log export CSV
No changes yet.
Shortcuts
N / Esc Navigate
H · hold Space Hand: drag to move the view (Space works with any tool)
R L P B Rectangle, Lasso, Polygon, Brush
W G A U F M Wand, Object, Above line, Below line, Buffer line, Measure
K Measure & edit area
I S Identify, Section
T / O / V Top / 3D view / split 2D | 3D
Home / Z · Shift+Z · 0 Fit all · zoom to selection / object · reset view
+ / − · Arrow keys Zoom · pan active pane
, . Move section back / forward
[ ] Brush size
1–9 To class = that class code
Ctrl+Z / Ctrl+Y Undo / redo
Mouse Wheel zoom (towards cursor), right-drag pan, left-drag rotate (3D, pivots at the point under the cursor), double-click to centre on a point