Frequently Asked Questions

Use this page for quick answers. For implementation and policy details, follow the linked canonical pages.

Access and Product

How do I access cloudless Sentinel-2-compatible imagery?

Use the dashboard for no-code workflows or the API for automation. If you are new, start with Get credentials and API key.

What does "cloud-free" mean in ClearSKY?

In ClearSKY, cloud-free means reconstruction, not only masking. The pipeline combines optical and SAR evidence to handle cloud, shadow, haze, and missing optical pixels. See What is ClearSKY?.

What satellites are used in production?

Core inputs include Sentinel-2 optical and Sentinel-1 SAR, with other supported constellations depending on model and region. See Satellite inputs and coverage.

Is this the same as a mosaic or monthly composite?

No. Traditional mosaics/composites mostly select clear pixels across a window. ClearSKY reconstructs cloud-affected areas to keep operational continuity. See What is ClearSKY?.

Where can I find runnable Python examples?

Use End-to-end Python workflow for an in-doc baseline, and use Clearsky-Vision/clearsky_api_tools for script-first examples and a lightweight Python client.

Data Outputs

What file format do you deliver?

ClearSKY delivers multi-spectral GeoTIFF outputs. For encoding, metadata tags, and scaling rules, see Bands, formats, scaling, and metadata.

Do you support TOA and BOA outputs?

Yes, depending on model and request settings (Level). See Data product overview and Bands, formats, scaling, and metadata.

Do you support harmonized and non-harmonized outputs?

Yes, for models and configurations that support both modes. Keep Level and Harmonize settings consistent across a time series. See Bands, formats, scaling, and metadata.

Can I choose projection and resolution?

Yes. Projection and resolution are selected at request time. For best quality and temporal consistency, keep settings stable across dates. See Data product overview.

Ordering and AOI

What AOI formats are accepted?

Polygon ordering accepts Wkt or GeoJson geometry inputs. Tile/minitile ordering uses predefined GUIDs. See Choose an order type, Define an area with polygon ordering, and Define an area with tiles and minitiles ordering.

What is the minimum order size?

For polygon ordering, the current default minimum billable area for production models is 0.5 km2. Smaller valid geometries can still be accepted and billed at the minimum. Limits are model-scoped and can change by model, so validate final settings with estimate/dashboard flows. See Define an area with polygon ordering.

Can I mix tiles and minitiles?

Yes. You can combine full tiles and minitiles in the same order when grid-based ordering fits your workflow. See Define an area with tiles and minitiles ordering.

Can I order partial tiles or partial minitiles?

No. Tile and minitile footprints are fixed grid units. Use polygon ordering when you need exact boundaries. See Choose an order type.

What do ImageFrequency and ReferenceDate control?

ImageFrequency controls revisit cadence; ReferenceDate anchors cadence alignment across orders. See Ordering overview and Historical vs recurring orders.

What is the difference between historical and recurring orders?

Historical uses From and To for a fixed window. Recurring uses From with empty To and continues month over month until recurrence is canceled before 00:00 UTC on the first day of the next month. See Historical vs recurring orders.

Can I cancel or modify an order after placing it?

Orders in Review can be canceled completely. After acceptance, full cancellation is no longer available. Recurring cancellation stops only future renewal (if done before monthly UTC cutoff) and does not undo already-created coverage. See Cancel or modify recurring orders.

Pricing and Billing

Do I need a subscription to order data?

No. Usage is pay-as-you-go through credits and tiered rates. Subscriptions mainly govern support, limits, and platform capabilities. See Pricing overview and Subscriptions and plans.

What is billed at ordering time versus download time?

Order creation uses order credits (EUR). Downloads consume processing units. These are separate pools. See Order credits vs processing units.

How do monthly spend tiers work?

Tier level depends on cumulative spend in the current calendar month. Effective EUR/km2 decreases as you move into higher tiers, and tiers reset monthly. See Monthly spend tiers.

Availability, Retrieval, and Sharing

Why did a download fail even with remaining credits?

Credits are only one requirement. Availability conditions, request mismatch, retention/storage limits, or validation errors can still block retrieval. See Check availability, Troubleshooting, and Storage and extra requests.

How can I reduce failed download attempts in automation?

Preflight with availability endpoints before processing/download calls, and keep request settings consistent with the order configuration. See Check availability.

Do I need attribution when sharing outputs externally?

Yes. Preserve and pass through source attribution and provenance notices required for the specific output. See Source attribution and external use.

Can I redistribute delivered data as a standalone data service?

Not unless your agreement explicitly allows it. See external sharing boundaries in Source attribution and external use.