Skip to main content

Composite Downloads

Composite downloads generate imagery for custom geometries and are the default download mode for most API workflows.

Endpoints​

  • POST /api/satelliteimages/process/composite/available
  • POST /api/satelliteimages/process/composite/estimate
  • POST /api/satelliteimages/process/composite

Required Inputs​

  • One geometry mode: Wkt or GeoJson
  • Date
  • Resolution
  • EpsgProjection
  • Model
  • SatelliteConstellations
  • Bandnames

Important Options​

  • EpsgProjection: choose explicit UTM EPSG (326xx/327xx) or 47000 for auto-EPSG mode
  • PixelSelectionMode: intersect or contained
  • DataType: INT16 or UINT8
  • UtmDataSelectionMode: UTM handling strategy for UTM-aware outputs (explicit UTM or auto-EPSG workflows)
  • UtmGridForcePixelResolutionSize: controls fixed pixel-size behavior when reprojection is involved
  • AllowPartialImage: strict vs partial behavior
  • UploadUrl: server-side upload target instead of binary response

Usage Notes​

  • You can use composite downloads even when the original order was tile/minitile-based.
  • Use tile/minitile endpoints only when you specifically need grid-aligned retrieval behavior.
  • For detailed UTM mode behavior and tradeoffs, see CRS / EPSG / UTM guidance.

See Processing / download endpoints for full contract.