Technology

First published

When the satellite list goes quiet, check where you are looking.

Our interpretation

If your farm adviser sends you a map update every week, ask where the list of new satellite images comes from. Copernicus is changing how it delivers that list. A team using the old direct storage bucket needs to change its setup by 20 January; a team using the supported catalogue API does not. Before the 20 January switch, compare product IDs for the same Sentinel platform and inventory dates. After it, use the supported catalogue API.

The Signal in brief

What changed

Copernicus publishes inventories of available satellite products. A file in that catalogue lists products; it is not a satellite image or a verdict on crop health. On 18 November the operator announced that it would replace the old browsing interface on 20 January 2027. The old and new views are available together until then.

Why it matters

A map reader can mistake a list that stopped updating for a week with no new satellite coverage. A change to how the list is delivered can explain the silence instead.

Who it affects

People who rely on a supplier’s satellite-based maps and the teams that prepare those maps.

Where

Worldwide users of the EU Copernicus Data Space daily product inventories; especially people relying on a supplier’s map updates.

What to watch

If the two lists differ, mark that map update as unconfirmed while the supplier checks dates and delivery. If the IDs match, the inventory comparison passed for those dates only. It does not prove that a usable picture covers your field, that skies were clear or that nothing changed on the ground. After the switch, check a newly available date by the supported route. No missed field update, data loss or paid migration has been verified.

No missing imagery, wrong farm map, paid migration, customer outage or completed paired comparison has been verified.

Explore this signal

Emerging data

A list is not a picture

Copernicus publishes inventories of available satellite products. A file in that catalogue lists products; it is not a satellite image or a verdict on crop health. On 18 November the operator announced that it would replace the old browsing interface on 20 January 2027. The old and new views are available together until then.

Find out which route your supplier uses

A person opening the existing catalogue website will get the new interface after the change. A scheduled job reading the underlying storage bucket directly is different: that location will be removed. Copernicus advises those users to switch to its catalogue API, the service through which software requests a list. The same notice says the API itself is unaffected. A dashboard that already uses it does not need to be rebuilt on account of this change.

Which route needs to change?
  • Existing browser addressSame address gets the new interface on 20 January 2027.
  • Direct inventory storage bucketThis route retires. Move to the supported CSV Catalogue API.
  • Supported CSV Catalogue APIUnchanged by this transition.
Inventory access update only; this does not report a satellite or customer outage.

Compare the names, not just the totals

Before the switch, ask the map supplier to choose one Sentinel platform and three past Sentinel inventory content dates relevant to its work. For each day, read the old and replacement inventories with the same filters, compare the sets of listed product identifiers, and record which appear on just one side. Equal totals can still hide different products. Record both retrieval times; a later rebuild or a different date filter can explain a mismatch. This is a proposed test, not a comparison we ran.

Before 20 January 2027: compare the inventory IDs
View branches
Before 20 January 2027: compare the inventory IDs
QuestionAnswerNext step
Do both routes show the same IDs for like inventory dates?YesCheck whether a usable image covers your area. Matching lists alone cannot tell you.
Do both routes show the same IDs for like inventory dates?NoDo matching filters and generation times explain the difference?
Do matching filters and generation times explain the difference?YesRecord the cause rather than calling it a satellite outage.
Do matching filters and generation times explain the difference?NoMark the update unconfirmed and ask your supplier to check.
Proposed check, not a test OnTheRice conducted. After the cutover, check a new date using only the supported route.

Three dates mean different things

The date an inventory list applies to is different from when that list first appeared and when it was last generated. None of those fields, on its own, tells you when an image was taken. A rebuilt list is not necessarily a new observation. Do not apply this date test unchanged to Copernicus Land Monitoring Service entries: their catalogue content date is empty.

Three different dates for one inventory
Three different dates for one inventory
FieldWhat it means
Content dateThe date the inventory list applies to, not proof of when a picture was taken.
First publishedWhen the inventory first appeared.
Last generatedWhen it was last built; a rebuild can be later.
Copernicus Land Monitoring Service entries do not contain a content date. These fields do not establish cloud cover or local ground conditions.

What to tell the map reader

If the two lists differ, mark that map update as unconfirmed while the supplier checks dates and delivery. If the IDs match, the inventory comparison passed for those dates only. It does not prove that a usable picture covers your field, that skies were clear or that nothing changed on the ground. After the switch, check a newly available date by the supported route. No missed field update, data loss or paid migration has been verified.

Report this passage

The connection

A person opening the existing catalogue website will get the new interface after the change. A scheduled job reading the underlying storage bucket directly is different: that location will be removed. Copernicus advises those users to switch to its catalogue API, the service through which software requests a list. The same notice says the API itself is unaffected. A dashboard that already uses it does not need to be rebuilt on account of this change.

Report this passage

The opportunity

Before the switch, ask the map supplier to choose one Sentinel platform and three past Sentinel inventory content dates relevant to its work. For each day, read the old and replacement inventories with the same filters, compare the sets of listed product identifiers, and record which appear on just one side. Equal totals can still hide different products. Record both retrieval times; a later rebuild or a different date filter can explain a mismatch. This is a proposed test, not a comparison we ran.

What could happen next

  1. First-order consequence

    Identify which link supplies the inventory.

  2. Second-order consequence

    If it is the retiring route, name its replacement.

  3. Third-order consequence

    If lists differ, compare the filter and rebuild dates.

  4. Fourth-order consequence

    If differences persist, withhold a claim that there was no new coverage.

  5. Fifth-order consequence

    If supported-route checks remain reliable across multiple dates, routine reporting may resume; field interpretation still needs imagery.

Costs, benefits and assumptions

Illustration only: two paid staff hours at an assumed €30 per hour represent €60 of staff time. No cash saving or migration fee reported; if an existing job already uses the supported API, this notice alone does not justify new paid work.

What would change our view?

Do not diagnose a satellite outage from a blank list. If the blank has a documented date-filter or delivery cause, address that cause instead.

Alternative explanation

If your supplier already uses the catalogue API, this notice does not require that service to change its setup. A blank list may have another cause.

What would confirm it

On matching Sentinel dates and filters, compare product IDs before the cutover. After it, check a fresh date on the supported route and confirm what the map actually covers.

What would disprove it

Do not diagnose a satellite outage from a blank list. If the blank has a documented date-filter or delivery cause, address that cause instead.

Evidence and sources

  • Copernicus notice: new catalogue CSV interface

    Publisher: Copernicus Data Space Ecosystem

    Original language: English

    published date precision: day

    retrieved date precision: day

    Source publication date 2026-11-18

    Source retrieval date 2026-11-19

    Coverage and independence

    Displayed issue date; date in page URL is not the publication clock.

    View source
  • Copernicus official RSS publication timestamp, node 4310

    Publisher: Copernicus Data Space Ecosystem

    Original language: English

    published date precision: day

    retrieved date precision: day

    Source publication date 2026-11-18

    Source retrieval date 2026-11-19

    Coverage and independence

    18 Nov 13:25:14 UTC = 21:25:14 SGT. Matching article title and link, author and exact item pubDate; feed is rolling.

    View source
  • Copernicus CSV catalogue documentation

    Publisher: Copernicus Data Space Ecosystem

    Original language: English

    retrieved date precision: day

    Source retrieval date 2026-11-19

    Coverage and independence

    Reference for content, first-publication and generation dates; the service provider, not independent verification.

    View source
  • Replacement Copernicus CSV interface

    Publisher: Copernicus Data Space Ecosystem

    Original language: English

    retrieved date precision: day

    Source retrieval date 2026-11-19

    Coverage and independence

    Replacement public interface, no additional event clock.

    View source

Gaps in the evidence

One operator; notice, feed, interface and documentation corroborate different aspects, not downstream results. Publication clock is the exact matching RSS item; a different date embedded in the page address is not the source clock.

Explore the research

Research layers

Research entries

  1. Layer name

    01 Money flow

    Research and limitations

    No paid orders in the notice.

  2. Layer name

    02 Orders and deposits

    Research and limitations

    No new service deposit confirmed.

  3. Layer name

    03 Bottlenecks

    Research and limitations

    The dependency is the old direct inventory path, not the sensor.

  4. Layer name

    04 Other beneficiaries

    Research and limitations

    A map user may avoid a false blank alert; no measured benefit.

  5. Layer name

    05 Company finances

    Research and limitations

    No issuer financial claim.

  6. Layer name

    06 Costs and payback

    Research and limitations

    Illustration only; use actual staff time and cost.

  7. Layer name

    07 Ownership

    Research and limitations

    No equipment purchase implied.

  8. Layer name

    08 Hiring

    Research and limitations

    No new hire established.

  9. Layer name

    09 Public procurement

    Research and limitations

    EU service notice, not an awarded tender.

  10. Layer name

    10 Foreign-language evidence

    Research and limitations

    English notice; no separate language evidence claimed.

  11. Layer name

    11 Behaviour and payments

    Research and limitations

    Actual products listed, not downstream delivered maps.

  12. Layer name

    12 Contradictory readings

    Research and limitations

    A website redirect does not keep a retired storage path alive.

  13. Layer name

    13 Missing expected evidence

    Research and limitations

    Missing notifications do not establish absent observations.

  14. Layer name

    14 Pilots and approvals

    Research and limitations

    Paired comparison proposed but not performed.

  15. Layer name

    15 Alternatives

    Research and limitations

    Supported API users are an unaffected comparator.

  16. Layer name

    16 Cross-border scope

    Research and limitations

    Worldwide users; no claim about a particular local parcel.

  17. Layer name

    17 Historical comparison

    Research and limitations

    No earlier OTR outcome verified.

  18. Layer name

    18 Pricing and awareness

    Research and limitations

    Not an investment signal.

  19. Layer name

    19 Counter-evidence

    Research and limitations

    A matching inventory need not have imagery suitable for the user.

  20. Layer name

    20 Action and stop rule

    Research and limitations

    Compare before 20 January; retest later, stop diagnosing a satellite outage from the list alone.

Back to Signals

AI powered research