# Earth Observation Evidence — NASA and Copernicus (`civicdataforge/earth-observation-evidence`) Actor

Receipt-bound official NASA HLS and Copernicus Sentinel scene metadata for a bounded area and time window, with rights, freshness, source hashes, and explicit non-interpretation limits.

- **URL**: https://apify.com/civicdataforge/earth-observation-evidence.md
- **Developed by:** [Bryan](https://apify.com/civicdataforge) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Earth Observation Evidence — NASA and Copernicus

Query current official NASA HLS and Copernicus Sentinel scene catalogs for one bounded area and time window. The Actor returns a receipt-bound multimodal evidence entry that agents and data teams can consume directly.

### What you get

- official NASA HLS Landsat and Sentinel-2 catalog records;
- official Copernicus Sentinel-2 L2A and Sentinel-1 GRD catalog records;
- acquisition time, intersecting geometry, platform, instruments, cloud cover where published, nominal resolution, and official asset links;
- a separate query receipt for every selected source, including the response hash and retained count;
- endpoint-shape receipts that preserve observed keys and distinguish missing, explicit `null`, and explicit `false` fields even when the publisher still returns HTTP 200;
- source-rights and attribution receipts;
- coverage, freshness, entry, and run hashes;
- explicit `SOURCE_UNAVAILABLE` or `SCOPE_INCOMPLETE` state when a selected source fails.

The Actor queries public STAC metadata. It does **not** download imagery pixels, run object detection, identify a person, or claim that a catalog record proves ownership, permit status, legality, causation, damage, safety, or responsibility.

### Quick start

```json
{
  "aoiId": "orlando-demo-001",
  "bbox": [-81.45, 28.45, -81.25, 28.65],
  "startDate": "2026-08-01",
  "endDate": "2026-08-25",
  "sources": [
    "nasa_hls_landsat",
    "copernicus_sentinel_2_l2a"
  ],
  "maxItemsPerSource": 10,
  "maxCloudCover": 60
}
```

`bbox` is `[west, south, east, north]` in WGS84 coordinates. The Actor limits requests to 25 square degrees, 366 days, 100 items per source, and the four named official catalogs.

### Output contract

The default dataset contains one `civicdataforge.multimodal-evidence-entry.v1` object. Its `observations` keep official catalog-query receipts and individual Earth-observation scene records separate. `SOURCE-MANIFEST` v2 and `RUN-RECEIPT` are also written to the default key-value store. Each successful source entry includes a payload shape receipt and record-set shape receipt so publisher representation drift remains independently diffable from record-value changes.

Use `coverage.complete_for_declared_scope` before relying on the bounded query. A completed zero-result query means only that the named catalog returned no retained records for the exact area, time, source, and cloud filter; it is not a universal no-imagery claim.

### Source and rights boundary

- NASA CMR STAC: [NASA Earthdata](https://www.earthdata.nasa.gov/home)
- Landsat reuse: [USGS Landsat restrictions and redistribution](https://www.usgs.gov/faqs/are-there-any-restrictions-use-or-redistribution-landsat-data)
- Copernicus STAC: [Copernicus Data Space STAC API](https://documentation.dataspace.copernicus.eu/APIs/STAC.html)
- Copernicus terms: [Terms and conditions](https://dataspace.copernicus.eu/terms-and-conditions)

CivicDataForge redistributes normalized public catalog metadata and official source links, not satellite imagery bytes or publisher-created visualizations. Upstream attribution remains attached to every observation.

### Agent access

- Actor: `civicdataforge/earth-observation-evidence`
- MCP: `https://mcp.apify.com/?tools=civicdataforge/earth-observation-evidence`
- Support: `civicdataforgehq@gmail.com`

For an area plus permit, facility, telemetry, or other official-record evidence, use the CivicDataForge Evidence Gateway and keep each layer's meaning, clocks, rights, and uncertainty intact.

# Actor input Schema

## `aoiId` (type: `string`):

Your stable reference for this area of interest.

## `bbox` (type: `array`):

\[west, south, east, north] in WGS84 decimal degrees. Maximum area is 25 square degrees.

## `startDate` (type: `string`):

Inclusive UTC date or timestamp. Defaults to 30 days before execution.

## `endDate` (type: `string`):

Inclusive UTC date or timestamp. Defaults to execution time.

## `sources` (type: `array`):

Official NASA and Copernicus STAC collections to query.

## `maxItemsPerSource` (type: `integer`):

Newest catalog records returned per source.

## `maxCloudCover` (type: `number`):

Optional post-retrieval filter for sources that publish eo:cloud\_cover. Radar scenes and missing cloud values are retained.

## Actor input object example

```json
{
  "aoiId": "orlando-demo-001",
  "bbox": [
    -81.45,
    28.45,
    -81.25,
    28.65
  ],
  "sources": [
    "nasa_hls_landsat",
    "nasa_hls_sentinel",
    "copernicus_sentinel_2_l2a",
    "copernicus_sentinel_1_grd"
  ],
  "maxItemsPerSource": 10
}
```

# Actor output Schema

## `results` (type: `string`):

API URL for the default dataset entry.

## `sourceManifest` (type: `string`):

No description

## `runReceipt` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("civicdataforge/earth-observation-evidence").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("civicdataforge/earth-observation-evidence").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call civicdataforge/earth-observation-evidence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,civicdataforge/earth-observation-evidence"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/hLegZU9lt9g5hT2sQ/builds/JTRq7I5eJ1ZgszXLw/openapi.json