Sorry Pixelchaser I thought you were talking about the track surface data, not terrain.
Is the track surface quality comparable to the Oulton Park mesh I uploaded the other year?
Or is it more like the lidar data that was posted from the Highways Agency from their on-van scanners?
Yes you can end up over thinking what the data tells you.
That's why mk1 eyeball is better for the track surface than 'algorithms' you just fiddle with without base reference.
I've worked from 50m grids down to sub 5mm noise floor laser scans on public roads.
I'd *always* go with my eye over any other process for the track shape itself, if you can't directly use the dataset to get the road form correct.
Quite often bits of cars not removed from the scans properly, or maybe even a couple of points on a cone or something, throw results off.
Like you, you'd prefer to paint in PS over have textures automated, and so it stands here with track surfacing.
For the very best track surface with non-perfect data, the old slow way is still the best way
What is the track btw? Care to share the laz file?
PS, the U.K. OS lidar, dtm, dsm data is now also joined by ortho photo tiles.
They're an odd compressed format but should convert ok in xnview 32bit with plugin I think.
So they'll be nice to drape over dsm/dtm or underlay as references perfectly aligned to your dataset!
I'm still thinking for a semi-pro track that a decent drone pass + photogrammetry is best.
You get lidar like quality for less price, with fantastic colour data baked in by design. So you can perfectly model over it and see track edges etc.
Hmmmm.