Reference · built on requestCommons signalHazards & public safety

Copernicus Emergency Management Service

Satellite mapping activations for disasters worldwide from Copernicus EMS, with a JSON API for activations, AOIs, and map products.

About

The Copernicus Emergency Management Service On-Demand Mapping component produces maps and vector data from satellite imagery when an Authorised User requests it for a disaster. Rapid Mapping products come as First Estimate, Reference, Delineation, and Grading for each area of interest; Risk and Recovery Mapping covers the preparedness and recovery phases. The European Commission's Joint Research Centre manages the service. Each activation carries a code such as EMSR932, a hazard category such as Flood, Wildfire, Storm, or Earthquake, the countries affected, a centroid and extent in WKT, and a closed flag. A JSON API lists activations, and the Rapid Mapping API returns AOIs, products, versions, layers, and imagery metadata for any code.

Through Fibric, an operator reads new activations that intersect your sites or supplier regions and proposes the review, chase, or briefing for your approval.

This is a reference listing. It documents what Fibric would read from Copernicus Emergency Management Service and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The activations list at mapping.emergency.copernicus.eu/activations/api/activations/, paged with limit and offset, with code, name, category, countries, centroid, activationTime, lastUpdate, drmPhase, closed, n_aois, and n_products
  • A short record per activation at /activations/api/activations/{code}/
  • Rapid Mapping details at rapidmapping.emergency.copernicus.eu/backend/dashboard-api/public-activations/?code=, with reason, activator, eventTime, subCategory, sensitive, gdacsId, extent, stats, and reportLink
  • Areas of interest per activation, each with number, name, extent, blpPath, and a products array
  • Products typed FEP, REF, DEL, or GRA, with feasible, expectedDelivery, a version with statusCode W, I, F, or N, and downloadPath to the product zipfile
  • Product layers as vector tiles, GeoJSON, or Cloud Optimized GeoTIFF in the aws_bucket, each with a matching .sld style file
  • Source imagery per product: sensorType optical or sar, resolutionClass HR, VHR1, VHR2, or Aerial, sensorName, acquisitionTime; plus the RSS news feed at /latest/feed/

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase purchase orders inside a mapped disaster

    When a new Flood, Storm, or Wildfire activation's extent covers a supplier's location, the operator lists the open orders from that supplier and proposes a delay review and a chase message.

    With Inbound Delay, PO Chase

  • Flag a vendor site inside an activation

    The operator matches each activation's AOI extents to vendor addresses and proposes an outage watch with the reportLink and grading product attached.

    With Vendor Outage

  • Order inspections from the grading map

    For properties inside a Grading product's extent, the operator reads the damage layers from the S3 bucket and proposes an inspection list ordered by mapped damage.

    With Inspection Scheduling

  • Brief the board on a regional event

    The operator drafts a slide from the activation's stats, such as event extent, built-up area, and roads affected, with the map product and the Copernicus citation.

    With Board Pack

Requirements

  • A polygon per site or supplier region to test against each activation's extent and AOI extents, which arrive as WKT
  • Paging through the activations list with limit and offset; the documented sample pages by 20
  • The activation code to fetch Rapid Mapping details, AOIs, and products for that event
  • A GIS or tile reader for vector tiles, GeoJSON, COG, and the SLD style files stored under aws_bucket
  • The Copernicus source citation on anything you distribute, as the terms and conditions require
Authentication
No key or account. The activations API and the Rapid Mapping public-activations endpoint answer plain GET requests; only records flagged sensitive are restricted.

Limits

  • Activations happen only when an Authorised User requests one; the service is on demand, not continuous monitoring
  • Products can be delayed or not produced: statusCode W means waiting for data, N not produced, and feasible false records an unproduced product
  • Data flagged sensitive is restricted under article 53 of Regulation (EU) 2021/696 and needs registration
  • Data are provided as is; the terms note that errors, omissions, and frequent changes without prior notice can occur

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Copernicus Emergency Management Service ↗

Questions and answers

Who can trigger a Copernicus EMS activation?
Only Authorised Users: National Focal Points in EU Member States and in countries of the EU Civil Protection Mechanism, European Commission services, the EEAS Situation Room, and EU delegations. Other public authorities channel a request through an Authorised User. Products, once made, are public unless flagged sensitive.
What product types does Rapid Mapping deliver?
Per AOI: FEP First Estimate, REF Reference, DEL Delineation, and GRA Grading, plus monitoring versions. Each product carries a version statusCode of W waiting for data, I for a product being produced, F production finished, or N not produced, a deliveryTime, and a downloadPath zip.
Under what terms can I reuse the maps and data?
Free, full, and open access without warranty: reproduction, distribution, communication to the public, and adaptation are allowed. You must inform recipients of the source using the Copernicus citation guidelines. Data flagged sensitive is restricted and requires registration.
Ask about Copernicus Emergency Management Service

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.