copc.io

What It Is

COPC (Cloud Optimized Point Cloud) 1.0 is a cloud-optimized point cloud file specification designed by Hobu, Inc. In essence, it is a LAZ 1.4 file, but with point data organized inside the file using a clustered octree, while COPC info VLR and hierarchy VLR records describe the octree hierarchy, data block offsets, and sizes. Its goal is similar to Cloud Optimized GeoTIFF in the point cloud world: keeping large datasets compatible with a mainstream container while enabling incremental, spatial subset reads via HTTP range requests.

Core Capabilities and Ecosystem

Functionally, COPC supports sequential reading, as well as direct access to LAZ chunks by clients that understand the hierarchy structure and query by spatial extent. The specification explicitly requires the use of LAS PDRF 6, 7, or 8 only, and the data must include an info VLR and a hierarchy VLR. Compared with EPT, it has no ept.json, does not support ept-sources.json, and does not support binary point arrangements. Its advantage is that it compresses the EPT-style organization of “many small files” into a single LAZ file, reducing cloud storage, migration, and deletion costs.

In terms of ecosystem, the documentation mentions LAZ decompression implementations such as LASzip, laz-rs, and laz-perf, with laz-rs and laz-perf usable in JavaScript clients. It also provides sample datasets such as Autzen Stadium, SoFi Stadium, and Millsite, browser viewer links, the validate.copc.io online validator, and copcverify, a C++ metadata validation tool on GitHub.

Pricing and Deployment

The documentation does not mention any commercial pricing, subscriptions, or paid features, so COPC should be viewed more as an open specification and collection of supporting tools. For deployment, COPC files can be self-hosted on an HTTP server. To support streaming access, the server must allow Range requests, and CORS must also be configured if the files are accessed cross-origin from a browser.

Pros, Cons, and Who It’s For

The main advantages are reuse of the LAZ ecosystem, easier management through a single-file format, a hierarchical index well suited to online browsing of large-scale point clouds, and highly engineering-oriented definitions of structures, offsets, and read validation steps in the specification. The drawbacks are that the format is relatively constrained and only supports specific PDRFs and LAZ; it is not a full SaaS product or SDK, and lacks platform capabilities such as commercial support, permissions, hosting, and billing.

COPC is suitable for GIS platforms, LiDAR data publishing, 3D visualization, and development teams building point cloud processing tools. The documentation provides no information about access from China. Many sample datasets are hosted on GitHub/S3, so real-world network stability may vary by environment. There is no payment information. Alternatives or related approaches include EPT, traditional LAS/LAZ, and COG in the raster domain as a design analogy.