Public sources / EU

Copernicus Browser

View and compare satellite imagery and metadata over time. Retain collection, scene identifier and display settings to distinguish the acquisition from the exported rendering.

Mapping workspace with a map, compass and illustrative coastal image.

AI-generated illustration

Read this source in practice

Does a cloud filter guarantee a readable area?

Copernicus Browser combines collection, period, cloud coverage and visualisation choices. Filters select products; then check the useful area's visibility and displayed processing.

Checks to perform

  1. Keep collection, product and acquisition date.
  2. Describe area and chosen cloud filter.
  3. Compare the view with product information.

The reference documents the reading method. The example is fictional; this note does not attest a portal test today or a mission outcome.

On a small screen, scroll the table horizontally to read all columns.

A global threshold is insufficient for the area of interest
ScopeObservationInterpretation
Whole product15 %Below the 20% threshold
Area of interestCloud-coveredLocal observation obstructed

Interpretation limit

A search threshold does not guarantee every studied pixel is usable. Colour changes can reflect processing rather than ground changes.

Record to retain

Product, area, period, threshold, bands or visualisation and obstruction observed in the target area.

Consulted reference : Copernicus Data Space — About the Browser · Consulted on

Updated on :

Provenance and evidence type

Operator or reference institution
Copernicus Data Space Ecosystem
Result type
Observation image or product

Record sensor, acquisition date, product and processing. Two views of one satellite product are not independent acquisitions.

    What this source helps you find

    View and compare satellite imagery and metadata over time. Retain collection, scene identifier and display settings to distinguish the acquisition from the exported rendering.

    Limit to retain in your conclusion

    Cloud cover, resolution, processing and acquisition date constrain interpretation.

    Useful search anchors

    • Place / coordinates
    • Reference period
    • Layer / product / sensor

    Fields to record when citing a result

    • Document identifier
    • Capture / acquisition date
    • Layer / product / sensor
    • Scale / resolution

    Evidence record to retain

    Product identifier, sensor, acquisition date, area, resolution, cloud cover and processing applied.

    Check before drawing a conclusion

    Publication and acquisition dates differ; inspect clouds over the precise area of interest.

    Official reference page

    Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.

    Cross-check this source in a research route

    Useful methods

    Other sources in this family

    Before export or reuse

    Coverage
    EU
    Identifiers to retain
    Document identifier · Capture / acquisition date · Layer / product / sensor · Scale / resolution

    Licence and rights

    Inspect the exact resource and its terms. Being viewable does not authorise redistribution; retain the resource licence and restrictions instead of inferring them from the portal.

    Date and version

    Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.

    What object does the result describe?

    Result unit
    Satellite scene or layer; separate acquisition and processing
    Time reference to retain
    Acquisition, product, processing and version; viewing date is not scene date.

    Documentation and access

    The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.

    Open producer documentation

    Can a map screenshot be freely published?

    Check each layer’s terms and required attribution. Inclusion in a viewer does not automatically give identical rights for every basemap and product.

    How can images be compared without confusing processing and real change?

    Align area, acquisition, sensor, resolution and rendering. Check clouds and masks locally; different palettes or composites can create visual differences.

    Verify the context of a public image
    Geographic sources and observation imagery

    DOCUMENTED REFERENCE

    Sentinel-2: the 13 bands have different native spacing

    MSI acquires four bands at 10 m, six at 20 m and three at 60 m. This table describes native acquisition, not the pixel size of any export. Spectral descriptions are indicative; exact responses depend on the instrument. The diagram compares the same 60 m square extent: 36 cells at 10 m, 9 at 20 m or 1 at 60 m.

    10 m3620 m960 m160 m × 60 m
    Sentinel-2: the 13 bands have different native spacing
    ReferenceValue or formWhat it identifies
    B0160 mCoastal and aerosol band.
    B0210 mBlue band.
    B0310 mGreen band.
    B0410 mRed band.
    B0520 mRed-edge band.
    B0620 mAnother red-edge band.
    B0720 mAnother red-edge band.
    B0810 mBroad near-infrared band.
    B8A20 mNarrower near-infrared band: distinguish it from B08.
    B0960 mWater-vapour absorption band.
    B1060 mCirrus band; not provided as surface reflectance in the L2A product described.
    B1120 mShort-wave infrared band.
    B1220 mAnother short-wave infrared band.

    B01: native spacing 60 m; nominal square cell area 3600 m². Area ratio to a 10 m cell: 36.

    Geometric calculation from documented spacing; neither a ground measurement nor a count of independent observations.

    Implication for the record

    L1C provides top-of-atmosphere reflectance; L2A provides surface reflectance after atmospheric correction. Retain level, band, tile, date and processing version. Resampling a 20 m band to 10 m does not make it a 10 m acquisition.

    Does a 10 m grid cell allow exact measurement of a 10 m object?

    No. Grid spacing guarantees neither object separation nor positional accuracy. Contrast, optical response, mixed pixels and processing also matter. The integrated comparison calculates only nominal square-grid cell areas.

    Primary documentation

    Documentation consulted on .

    DOCUMENTED REFERENCE

    SCL: a class code is not a probability

    The Sentinel-2 L2A scene-classification mask contains codes 0 to 11. The technical names below follow the consulted Copernicus table. SCL is produced at 20 m and may be resampled; it is not a continuous land-cover measurement.

    SCL: a class code is not a probability
    ReferenceValue or formWhat it identifies
    0NO_DATANo data: do not replace with zero reflectance.
    1SATURATED_OR_DEFECTIVESaturated or defective pixel.
    2CAST_SHADOWSCast shadow, distinct from cloud shadow; check processing version for an archive.
    3CLOUD_SHADOWSCloud shadow.
    4VEGETATIONVegetation class.
    5NOT_VEGETATEDNon-vegetated class.
    6WATERWater class.
    7UNCLASSIFIEDUnclassified pixel: distinct from class 0 with no data.
    8CLOUD_MEDIUM_PROBABILITYMedium-probability cloud class. Code 8 does not mean 8%.
    9CLOUD_HIGH_PROBABILITYHigh-probability cloud class. Code 9 does not mean 9%.
    10THIN_CIRRUSThin-cirrus class.
    11SNOW / ICESnow or ice class.

    Implication for the record

    Classification is algorithmic and can contain errors. Define excluded classes, retain the mask and baseline, and visually inspect the area. Averaging SCL codes does not yield an average probability.

    Is it possible to interpolate codes like a reflectance image?

    Bilinear interpolation may create values that identify no class. Use a categorical method and document the rule; Copernicus describes mode resampling for the 60 m SCL output.

    Primary documentation

    Documentation consulted on .

    DEEPER READING / PRACTICE

    Read a source profile as a starting point

    A list indicates where to look for and what limits to keep in mind. It helps to prepare a consultation but does not replace the reading of the obtained document.

    Updated on .

    Priority checks

    Select a precise question, open the source and raise the request, result and date. Compare the possibilities announced with the information actually available at the time of the consultation.

    Interpretation pitfalls

    The availability of a service and its content may vary. The directory does not turn an absent, partial or ambiguous result into a definitive response.

    Working record to retain

    The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.