Skip to main content

Source Attribution and External Use

This page explains how to handle source attribution and external sharing when using ClearSKY outputs. Terms in your signed agreement, Order, and source-data terms control. This page is operational guidance for implementation in dashboards, APIs, reports, and exported files.

Why This Matters​

ClearSKY outputs can combine multiple satellite sources in one fused product.

Because of that, required attribution can vary by:

  • selected constellations,
  • model and supported configuration,
  • fallback sources used during processing,
  • source metadata associated with the delivered output.

What You Must Pass Through​

When publishing, sharing, redistributing, exporting, or otherwise making outputs available outside your internal organization, you must preserve and pass through required source attribution notices and related license/provenance notices identified by ClearSKY.

The required notice is source-data provenance, not product branding.

Where to Get the Required Attribution Notice​

Use the attribution notice identified by ClearSKY for the specific output, including where provided in:

  • Documentation,
  • Order details,
  • ordering flow selections,
  • Delivered Data metadata and delivery files,
  • API responses,
  • other written ClearSKY instructions.

If source-specific or per-order attribution metadata is provided, that metadata controls for the relevant output.

Where Attribution Can Be Shown​

Use a location appropriate to the medium, such as:

  • map attribution area,
  • info icon or About/Data Sources panel,
  • report footer,
  • export caption,
  • metadata sidecar or documentation.

For internal use only, keep attribution/license/provenance metadata where reasonably practical. Visible attribution is not always required internally unless your Order, Documentation, or source terms require it.

External Sharing Boundaries​

Unless explicitly permitted by your agreement, do not redistribute Delivered Data as a standalone dataset, bulk export, API, tile service, or replacement data service.

Example Attribution Notices​

Unless ClearSKY specifies a different notice for a given output, examples include:

  • "Contains modified Copernicus Sentinel data [Year], processed by ClearSKY."
  • "Contains Landsat data courtesy of the U.S. Geological Survey/NASA, processed by ClearSKY."
  • "Contains modified Copernicus Sentinel data [Year] and Landsat data courtesy of the U.S. Geological Survey/NASA, processed by ClearSKY."
  • "Contains modified CBERS/Amazonia-1 data from INPE/MCTI, licensed under CC BY 4.0, processed by ClearSKY."

No Implied Endorsement​

Attribution must not imply endorsement by ClearSKY, Copernicus, ESA, EU institutions, NASA, USGS, INPE, MCTI, ISRO, NRSC, or other upstream providers unless expressly approved in writing.