Deliver corridor lidar as a link

A corridor survey does not come back as a tidy file. A drone or helicopter lidar pass over a transmission line, a pipeline right-of-way or a highway alignment lands as several gigabytes of LAS or LAZ, often hundreds of millions of points, sometimes more than a billion once the strips are merged. The engineer, the asset owner and the construction lead all need to look at it, and none of them are going to install TerraScan to do so.

What the client actually needs to do

• Open the corridor and fly along it, on whatever machine they have, including a laptop on site.
• Read elevations and distances off the cloud: conductor to ground, structure to structure, edge of easement to nearest tree.
• See classification, so ground, vegetation, wire and structure separate at a glance.
• Leave a note pinned to a structure and send it back without a meeting.
• Do all of it from the Teams channel where the project already lives.

How ViewerFX handles it

You upload the LAS or LAZ once. ViewerFX converts it to a streaming spatial format on the server, so the file size stops mattering: a 4 GB corridor with half a billion points opens as fast as a small site scan, because the viewer only fetches the points on screen. You get one link. Paste it into Teams, an email or a text and the recipient opens the full corridor in a browser with the ruler, spot elevations, classification colouring and annotations already there. Nothing to install, no account on their end, nothing to pay.

Coordinate systems come through intact. UTM, state plane, MGA and any other projected CRS declared in the file is read on conversion and shown in the viewer, and distances and elevations report in metres or feet.

QA and accuracy checks

The same link works for internal review. Drop an RTK accuracy check or a strip-alignment pass in, share it with the office, and let the reviewer pin annotations exactly where the misalignment or the vertical bust sits. Revoke the link when the deliverable is final, or leave it live as the record of what was delivered and when.

Sizes that work

There is no per-file cap. Customers push 4 GB files and 500-million-point corridors through the Starter plan today; the only limit is your total storage. Conversion of a multi-gigabyte corridor typically finishes in 15 to 40 minutes, and you do not need to stay on the page while it runs.

Security

Links are unguessable tokens. Add a password when the corridor is sensitive, revoke a link the moment a contract ends, and download the optimised LAZ any time you want your data somewhere else. Your originals stay private to your account.

Try it on a real corridor

The free plan covers 2 GB and two files, enough to deliver a real job and see how the client reacts. For a quick look at a file on your own machine first, the free browser viewer opens LAS and LAZ up to about 500 MB with nothing uploaded.