Skip to main content

Data Quality, Limitations, and Best Practices

Quality Expectations​

  • Outputs are designed to be Sentinel-2 compatible, but modelled reconstruction can differ from raw source pixels because processing includes more aggressive atmospheric cleanup and harmonization steps.
  • Availability and timeliness are primarily driven by source data acquisition and upstream provider latency, and can vary by model; if delivery timing is critical, contact us to confirm current expectations.

Common Limitations​

  • Some combinations of date/area/model can be partially available at request time, depending on source acquisition and ingest status.
  • Data volume from the same constellation can vary by geography. For similar AOI size and date windows, high-latitude areas (for example Sweden) often have more Sentinel-1 acquisitions than lower-latitude areas (for example Brazil).
  • Orders include one month of storage by default; after retention expires, previously produced data can become unavailable for download unless longer storage was configured.
  • Large AOIs that span multiple UTM zones require careful EPSG and UTM mode choices; there is no perfect reprojection that preserves all zones equally.

Best Practices​

  • Use POST /api/tasking/orders/estimate before creating large or automated orders, since it reflects what is currently orderable for your request.
  • Validate availability before bulk downloads.
  • For AOIs crossing UTM zones, prefer tile/minitile ordering so you can intentionally select zone-specific coverage.
  • Prefer UTM EPSG outputs for best geometric consistency.
  • Use consistent model/constellation settings for time-series comparability.
  • If one month of storage is not enough, increase retention (StorageMonths) at order time.
  • Keep canonical technical assumptions in sync with Data specification.