Transmission corridors
Conductors and structures out of the cloud, catenaries fitted per span, and vegetation flagged against a clearance distance you choose.
Raw LiDAR in. Deliverables out.
LAZweaver is a hosted processing service for survey point clouds: classification, terrain and surface models, contours, corridor work, tiles and a report, from one submission.
One submission, one folder of deliverables
One command runs the baseline every dataset needs and writes one folder: the classified cloud, a colourised copy, DTM, DSM and CHM rasters, contours, a georeferencing record, a tile pyramid and an HTML report. The same command accepts a single file or a directory of flight strips.
Nothing is retyped between stages and nothing depends on a desktop licence being available at the moment you need it. The same operations are reachable from a browser, from a script, and from an assistant that holds a conversation with you about the file.
What it is for
Forest and canopy
Ground under canopy, canopy height and cover, strata and per-tree segmentation, on slopes where a simple ground filter gives up.
Earthworks and sites
Surfaces, contours, cross-sections and cut-and-fill volumes between two epochs of the same site, as numbers rather than as a picture.
Measured, not advertised
Every timing on this site is one run, on one machine, on one named dataset — because a figure without those three is a benchmark nobody can repeat.
- A synthetic baseline
- Measured on a two-core sandbox: a three-million-point cloud runs the whole baseline in about twenty-eight seconds, end to end.
- A substation survey
- Measured on a thirty-five-million-point substation survey on a ten-core laptop: the full preset — powerline, clearance at five metres, trees, footprints, roads and bridges, native COPC and the PDF report — takes seventy-eight seconds.
- A steep forested parcel
- Measured on a five-point-eight-million-point parcel on a twenty-four per cent forested slope: sixteen seconds from raw, unlabelled points.
Where the data stays
All processing of Indian point-cloud data on LAZweaver takes place, and all such data is stored, exclusively within the India data plane (in-mumbai-1, AWS Mumbai). Point coordinates, classified clouds and derived surfaces do not transit foreign edge proxies, international CDN workers, overseas key-value stores or international log aggregators.
How that sits with Indian geospatial regulation
Getting in
Access is by invitation while the validation deployment runs: sign-up is closed, and an account is opened for a survey firm we have talked to.