geoprimsField-grade geospatial math

Dataset size estimate

An estimate of how much storage a mapping job needs: the raw images, the orthomosaic (uncompressed and over a compression range), and a lidar point cloud as and .

Planning and education aid. Not for primary navigation. Full disclaimer

7.5GB

The orthomosaic is about 7.5 GB uncompressed, 0.75 to 3.75 GB compressed.

Orthomosaic at the least compression
Orthomosaic at the most compression
Assumptions
Provenance
Computed by
drone.sensors.dataset-size 1.0.1, core 0.1.0
Model
Orthomosaic bytes = area ÷ GSD² × bands × bits ÷ 8, then divided by an assumed compression range; raw = images × MB each; LAS = 375 + points × the LAS 1.4 record size of the chosen point format; LAZ = LAS ÷ an assumed ratio. 1 GB = 10⁹ bytes
Accuracy
An estimate: compression depends on the content, and processing software adds overviews and tiles. The ratios shown are assumptions you can change, not measurements
Notes
None
Cites
American Society for Photogrammetry and Remote Sensing, LAS Specification 1.4 R15

Something look off?

Your values

Showing an example. Change anything.
More options 6
Lidar sensor profiles

Loading…

Run many at once from a CSV

Loading…

How we got thisFormula, worked example, sources, and proof

Model: Orthomosaic bytes = area ÷ GSD² × bands × bits ÷ 8, then divided by an assumed compression range; raw = images × MB each; LAS = 375 + points × the LAS 1.4 record size of the chosen point format; LAZ = LAS ÷ an assumed ratio. 1 GB = 10⁹ bytes

Show your work

  1. Pixels in the mosaic

    area ÷ GSD²

    1,000,000 m² ÷ (0.02 m)² = 2,500,000,000

  2. Orthomosaic, uncompressed

    pixels × bands × bits ÷ 8

    2,500,000,000 × 3 × 8 ÷ 8 = 7.5 GB

The same steps an agent gets from the MCP server with explain: true.

Accuracy: An estimate: compression depends on the content, and processing software adds overviews and tiles. The ratios shown are assumptions you can change, not measurements

When to use this: Use this when you quote or plan a mapping job and need to know how much storage it takes. Give the area and ground sampling distance for the orthomosaic, the image count and size for the raw capture, or the lidar point count, and it estimates each in gigabytes. Use the numbers to size memory cards, drives, upload time, and cloud storage before the flight.

Limitations: The orthomosaic is figured from pixel count, bands, and bit depth, then divided by an assumed compression range that your data may not match. Processing software adds overviews, tiles, and side products such as surface models that are not counted. The LAZ size uses an assumed ratio to LAS. A gigabyte here is a billion bytes, which some systems show differently.

Worked example: 1 km² at 2 cm GSD, RGB 8-bit. Source: add-practitioner-essentials orthomosaic scenario: 7.5 GB uncompressed, with a compressed range at the assumed ratios. It is golden test vector v001, and every build checks the tool still gives its answer within its tolerance.

You enter

Mapped area
1 km2
Ground sample distance
2 cm

You get

Orthomosaic, uncompressed
7.5 GB
Orthomosaic at the least compression
3.75 GB
Orthomosaic at the most compression
0.75 GB
Assumptions
orthomosaic 3 bands of 8 bits, compressed 2:1 to 10:1 (assumed); 1 GB = 10⁹ bytes; an estimate, not a measurement

Review: Not yet independently reviewed by a Part 107 remote pilot.

Last verified: 2026-09-22, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.

Status: version 1.0.1, core 0.1.0. See this tool in the verification report.

Changes

Checked against: 20 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.

Constants this tool assumes

Values you do not enter, and where each comes from.

LAS 1.4 public header block
375 bytes — LAS Specification 1.4 R15
LAS 1.4 minimum point-record sizes for formats 0 through 10
20, 28, 26, 34, 57, 63, 30, 36, 38, 59, 67 bytes — LAS Specification 1.4 R15
Default LAS point format
6 — LAS Specification 1.4 R15

Sources

Terms

LAS: LASer file format
The ASPRS standard file format for lidar point clouds: a header, then one fixed-size record per point. Source: LAS Specification 1.4 R15
LAZ: compressed LAS
A losslessly compressed LAS file, usually several times smaller. Source: LAS Specification 1.4 R15

LAS — LASer file format

The ASPRS standard file format for lidar point clouds: a header, then one fixed-size record per point.

Source: LAS Specification 1.4 R15

LAZ — compressed LAS

A losslessly compressed LAS file, usually several times smaller.

Source: LAS Specification 1.4 R15