Skip to main content

Tile and Minitile Downloads

Use tile/minitile downloads when your workflow is grid-based, covers very large areas, or needs tighter control near UTM transition zones.

Endpoints​

  • POST /api/satelliteimages/process/tile
  • POST /api/satelliteimages/process/minitile

Required Inputs​

  • Endpoint-specific GUID selector:
    • tile endpoint: tile GUID input
    • minitile endpoint: minitile GUID input
  • Date
  • Resolution
  • EpsgProjection
  • Model
  • SatelliteConstellations
  • Bandnames

Tile/minitile downloads use the same core processing settings as composite downloads. The key difference is AOI input: GUID-based selection instead of Wkt/GeoJson.

EPSG / UTM Behavior​

  • Tile/minitile processing supports UTM EPSG workflows.
  • You can use explicit UTM EPSGs (326xx/327xx) or 47000 for auto-EPSG mode.
  • With 47000, ClearSKY chooses the most suitable UTM EPSG for the request.

Important Options​

  • EpsgProjection: choose explicit UTM EPSG (326xx/327xx) or 47000 for auto-EPSG mode
  • 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

Notes​

  • Response can be direct bytes or upload via UploadUrl.
  • Tile purchases can still be retrieved as composites when needed.
  • Composite downloads are still the default in many workflows; use tile/minitile when their grid behavior is specifically needed.

For endpoint-specific field names and full request contract, see Processing / download endpoints. For ordering semantics, see Choose an order type.