OpenAerialMap

hotosm.org · Storage · 1 record · JSON

OpenAerialMap (HOT / Open Imagery Network) Storage

caveatemailno cardRper-object-cap

imagery.hotosm.org/contribute · open drone/satellite imagery commons · storage/openaerialmap · JSON · compare

Free tier	Free hosting for anyone with nowhere to publish. The rewrite of the uploader is explicitly scoped to 'Handle files up to 100GB with resume capability, using S3 multipart upload with presigned URLs (direct browser-to-S3)'. No per-account total published; the catalog holds 21,460 datasets. unit mixed; metered on unstated
Price	none stated
Per-object cap	100 GB/file (100000000000 bytes)
Retention	not stated
Egress	free — and note the two-tier model: providers who already have cloud storage can 'Register a catalog', in which case OAM stores only metadata and links out ('Indexing uses none of your bandwidth and gives OAM no rights over the imagery')
Identity	email email — sign in with a Google account (documented third-party walkthrough: 'Sign in using your google account'), no affiliation or review
Limits	per-object-cap 100 GB/file source geospatial raster only (GeoTIFF/COG orthomosaics); target 100 GB/file with resumable S3 multipart; account needed for API access and upload
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	cli uploader web app at upload.imagery.hotosm.org; STAC API at api.imagery.hotosm.org/stac; eoAPI (raster/vector/stac) behind it
Tooling	stactools-hotosm; STAC client; no CLI uploader yet
Composes with	Output is a COG + STAC item, i.e. cloud-native GeoTIFF — directly readable with GDAL/rio-tiler and range-friendly. But the payload must be an orthomosaic with georeferencing.
Reliability	The uploader was historically unreliable for large files and is mid-rewrite by a UC Berkeley Code-for-Good team (Spring 2026), so the 100 GB target is a workplan goal, not a shipped, verified capability. I could not find a live /api/upload route (404 on four candidates).
Notes	Free hosting for anyone with nowhere to publish. The rewrite of the uploader is explicitly scoped to 'Handle files up to 100GB with resume capability, using S3 multipart upload with presigned URLs (direct browser-to-S3)'. No per-account total published; the catalog holds 21,460 datasets.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 100.0 GB

Evidence (5)

date	source	what it proved
2026-10-21	imagery.hotosm.org/contribute	'If you cannot host imagery yourself, upload it'; the catalog-registration path stores metadata only
2026-10-21	github.com/hotosm/openaerialmap/discussions/258	'Handle files up to 100GB with resume capability, using S3 multipart upload with presigned URLs'; new API api.imagery.hotosm.org
2026-10-21	api.openaerialmap.org/meta?limit=1	200, {"meta":{..."found":21460},"results":[{..."uuid":"https://oin-hotosm-temp.s3.amazonaws.com/...tif"}]}
2026-10-21	api.imagery.hotosm.org/stac/collections	live STAC collections (cop-dem-glo-30, ...)
2026-10-21	withheld	api.openaerialmap.org/{upload,uploads,api/upload,upload/} — 404 on all four (no documented REST upload endpoint reached)

Unknown or withheld values (5)

$.evidence[4].url private-url
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.