Global Forest Watch & Resource Watch Dataset Explorer
Pricing
from $0.49 / 1,000 results
Global Forest Watch & Resource Watch Dataset Explorer
Browse the shared environmental dataset catalog behind Global Forest Watch, Resource Watch, Aqueduct, PREP, Forest Atlas and Open Data. Search by keyword and filter by source application, with provider and tag metadata per dataset.
Pricing
from $0.49 / 1,000 results
Rating
0.0
(0)
Developer
vexaloom-labs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Global Forest Watch & Resource Watch Dataset & Alert Explorer
Global Forest Watch, Resource Watch, Aqueduct, PREP, Forest Atlas and the Open Data portal share one environmental data catalog. This actor exposes that catalog and the public GFW alert summary tables in a single keyless workflow: discover datasets, inspect their metadata and fields, then pull alert counts or alert statistics for a country, admin area, geostore or custom polygon.
Everything runs against public endpoints with no API key, login, cookie or proxy configuration.
Modes
| Mode | What it returns |
|---|---|
datasets | Resource Watch catalog entries: the shared index behind GFW, Resource Watch, Aqueduct, PREP, Forest Atlas and Open Data. Filter by application, provider, connector type or keyword. |
gfwDatasets | The GFW Data API catalog: dataset slug, title/subtitle, source, license, citation, coverage, update frequency, resolution, tags and available versions. |
datasetDetails | Full metadata for one or more datasets. Resource Watch records include layer/widget counts; GFW records include the latest version and asset links. |
datasetFields | The field dictionary for a GFW dataset version: field name, unit, data type, no-data value and coded-value meanings. |
alerts | Alert counts for an area from the GFW Data API summary tables: date, alert system, confidence category, alert count and alert area. Works for ISO3, ISO3:ADM1, ISO3:ADM1:ADM2 and geostore IDs with precomputed rows. |
statistics | The same alert rows grouped by day, week, month or year, with confidence breakdowns and area totals. |
Input
| Field | Type | Default | Used by | Description |
|---|---|---|---|---|
mode | select | datasets | all | Which workflow to run. |
searchQuery | string | – | datasets, gfwDatasets | Free-text query; every word must appear in the name, description, tags, version or ID. |
application | select | any | datasets, gfwDatasets | Resource Watch application filter; in GFW mode it matches tags, names and IDs. |
provider | select | any | datasets | Resource Watch data provider (CARTO, GFW, Earth Engine, ArcGIS, CSV, …). |
connectorType | select | any | datasets | Resource Watch connector type (REST, document, WMS, vector, …). |
datasetIds | string list | – | datasetDetails | Resource Watch UUIDs, GFW dataset slugs or dataset API URLs. |
dataset | string | umd_tree_cover_loss | datasetFields | GFW dataset slug. |
version | string | latest | datasetFields | GFW version such as latest or v1.9.1. |
area | string | – | alerts, statistics | ISO3 code (BRA), admin area (BRA:15 or BRA:15:139), Resource Watch geostore ID, GFW geostore UUID, or latitude,longitude. |
alertSystem | select | glad | alerts, statistics | glad or integrated alert layer. |
polygon | string | – | alerts, statistics | GeoJSON Geometry, Feature or FeatureCollection. Overrides area. |
radiusKm | integer | 5 | alerts, statistics | Radius used when area is a lat,lng pair (1–100 km). |
startDate / endDate | string | 2020-01-01 / 2021-12-31 | alerts, statistics | YYYY-MM-DD alert period. |
aggregateBy | select | month | statistics | Time bucket: day, week, month or year. |
gladConfirmOnly | boolean | false | alerts, statistics | Keep only high/highest-confidence alerts. |
maxItems | integer | 20 | all | Maximum records (1–1000); in statistics it caps the number of buckets. |
Saved-task compatibility
Tasks saved against the first release keep working: legacy keys such as query, app, limit, geostore, start/end, confirmedOnly, modeType and datasetSlug are mapped onto the new inputs in code. Only the new names appear in the input form.
Examples
Browse GFW-tagged Resource Watch datasets about mangroves:
{"mode": "datasets","application": "gfw","searchQuery": "mangrove","maxItems": 50}
List GFW Data API datasets about alerts:
{"mode": "gfwDatasets","searchQuery": "alerts","maxItems": 30}
Inspect two datasets by reference:
{"mode": "datasetDetails","datasetIds": ["umd_tree_cover_loss", "48064dbb-3354-469a-b07f-d0503cb329ea"],"maxItems": 2}
Read the field dictionary for tree cover loss:
{"mode": "datasetFields","dataset": "umd_tree_cover_loss","version": "latest","maxItems": 200}
Pull confirmed GLAD alert counts for Brazil in 2021:
{"mode": "alerts","area": "BRA","alertSystem": "glad","startDate": "2021-01-01","endDate": "2021-12-31","gladConfirmOnly": true,"maxItems": 100}
Summarize Brazil by month:
{"mode": "statistics","area": "BRA","alertSystem": "glad","startDate": "2021-01-01","endDate": "2021-12-31","aggregateBy": "month","maxItems": 12}
Drill into one admin-1 area (Pará, GADM code 15):
{"mode": "statistics","area": "BRA:15","alertSystem": "integrated","startDate": "2025-01-01","endDate": "2025-03-31","aggregateBy": "month","maxItems": 12}
Aggregate a small custom polygon (geostore summary rows only):
{"mode": "statistics","polygon": "{\"type\":\"Polygon\",\"coordinates\":[[[-55,-7.2],[-54.85,-7.2],[-54.85,-7.05],[-55,-7.05],[-55,-7.2]]]}","alertSystem": "glad","startDate": "2021-01-01","endDate": "2021-12-31","aggregateBy": "month","maxItems": 12}
Output fields
Catalog records (datasets, gfwDatasets, datasetDetails) use a shared vocabulary: datasetId, catalog, slug, name, subtitle, description, provider, connectorType, tableName, connectorUrl, applications, tags, published, hasGeoInfo, createdAt, updatedAt, dataLastUpdated, citation, license, source, geographicCoverage, updateFrequency, spatialResolution, resolutionDescription, versions, latestVersion, isDownloadable, isLatest, isMutable, assets, layerCount, widgetCount and datasetUrl.
Field records add fieldName, unit, dataType, noDataValue, valueCount, values and defaultMeaning.
Area alert records include areaId, areaName, iso, adm1, adm2, adminLevel, alertDate, alertSystem, confidenceCategory, alertCount, alertAreaHectares, confirmed, source and recordType: "alert".
Statistic records include areaId, areaName, period, aggregateBy, alertSystem, alertCount, alertAreaHectares, confirmedAlertCount, confidenceCounts, firstAlertDate, lastAlertDate, totalAlerts, totalAlertAreaHectares and the requested startDate/endDate.
Every record also carries recordType (dataset, gfwDataset, datasetDetail, field, alert or statistic) and scrapedAt. Empty fields are omitted, never emitted as null or an empty string.
Use cases
- Environmental researchers — inventory which forest, land-use, water-risk and climate datasets exist before requesting the underlying data.
- GIS and data-engineering teams — resolve dataset slugs, versions and field dictionaries for a downstream pipeline.
- Journalists and NGOs — quantify recent GLAD alerts inside a country, protected area or custom polygon without an API key.
- Monitoring teams — schedule a daily alert count for one AOI and compare time buckets across a season.
FAQ
Does this need an API key or account? No. The catalog endpoints and the public GFW data gateway are called directly and anonymously.
Does alerts return integrated alerts? Yes. Set alertSystem to integrated for integrated deforestation alerts, or keep glad for the GLAD layer.
Why do my GLAD alert dates stop in 2021? The public GLAD summary tables cover the legacy GLAD series for most countries. Switch to alertSystem: integrated for newer alert data.
Can I use a polygon instead of a geostore? Yes. Pass GeoJSON in polygon; the actor creates a temporary geostore automatically. Area tables only have precomputed rows for geostores in the GFW summary set, so countries and admin areas are the reliable choice.
How do I pick an admin area code? Use the GADM numeric code after the ISO3, for example BRA:15 for Pará. Add the GADM admin-2 code for a district, for example BRA:15:139. Not every admin-2 area has precomputed alert rows.
What does gladConfirmOnly mean? It keeps only high/highest-confidence alerts.
How fresh is the catalog? Every run queries the live API, so titles, versions, fields and tags reflect the state of the catalog at run time.
Is this affiliated with Global Forest Watch, Resource Watch or the World Resources Institute? No. This is an independent tool that reads publicly accessible APIs and is not operated by or affiliated with those organizations. Dataset metadata and alerts retain their original licenses and attribution; see each record's citation, license and source.
Data sources and attribution
- Resource Watch API — catalog, metadata, vocabulary, layers and widgets.
- GFW Data API — GFW dataset catalog, versions, assets and field dictionaries.
- GFW public Data API gateway — alert summary tables by country, admin area and geostore.
- GFW public data gateway — GLAD and integrated alert summary rows used for area counts and statistics.
- GLAD alerts: Hansen et al., University of Maryland Global Land Analysis & Discovery (GLAD).
Alert data and dataset metadata remain subject to the upstream licenses. This actor does not rehost or resell the datasets themselves.