Sentinel-5P Methane Density at 2 km from 2021-12 to 2023-11 Monthly Aggregation Time-series Reconstructed

Open data API in a single place

Provided by Zenodo

Get early access to Sentinel-5P Methane Density at 2 km from 2021-12 to 2023-11 Monthly Aggregation Time-series Reconstructed API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.07.10 00:00
Created
2023.01.01
Available languages
English
Keywords
ch4, s5p
Quality scoring

Dataset description

General Description The monthly aggregated Methane Volume Mixing Ratio dataset is derived from Sentinel-5P to generate a time-series reconstructed monthly aggregated map. The dataset time spans from December 2021 to November 2023 and provides data that covers the entire globe. The mission is still underway and expected to update periodically. For more info about the s5p Methane product see: https://maps.s5p-pal.com/ch4/. The dataset can be used in many applications like emission tracing, livestock monitor, and greenhouse gas monitor. Monthly time-series: Methane monthly average value December 2021 – November 2023. Derived using the eumap and scikitmap package in Python . We derived three standard statistics: (1) 10th percentile (p10), median (p50), and 90th percentile (p90). Data Details Time period: December 2021 – November 2023 Type of data: Methane Volume Mixing Ratio (Unit: ppbv) How the data was collected or derived: Derived from 2km Sentinel-5P Menthane using Python running in a local HPC. The time-series analysis were computed using the Scikit-map and eumap Python package. Statistical methods used: percentiles 10, 50, and 90. Limitations or exclusions in the data: The dataset is not completed gap-filled. Certain areas have no data in the whole time series Coordinate reference system: EPSG:4326 Bounding box (Xmin, Ymin, Xmax, Ymax): (-180.00000, -61.9966697, 180.0000072, 87.37000) Spatial resolution: 1/60 d.d. = 0.016666667 (2km) Image size: 21,600 x 8,962 File format: Cloud Optimized Geotiff (COG) format. Support If you discover a bug, artifact or inconsistency, or if you have a question please use some of the following channels: Technical issues and questions about the code: https://gitlab.com/openlandmap/global-layers/-/issues General questions and comments: https://disqus.com/home/forums/landgis/ Name convention To ensure consistency and ease of use across and within the projects, we follow the standard Open-Earth-Monitor file-naming convention. The convention works with 10 fields that describes important properties of the data. In this way users can search files, prepare data analysis etc, without needing to open files. The fields are: generic variable name: ch4.vmr = methane density methane volume mixing ratio variable procedure combination: m.seacov = monthly aggregated and gap filled by seasonal convolution Position in the probability distribution / variable type: p10/p50/p90 = 10th/50th/90th percentile Spatial support: 2km Depth reference: a = above surface Time reference begin time: 20211201 = 2021-12-01 Time reference end time: 20231131 = 2023-11-31 Bounding box: go = global (without Antarctica) EPSG code: epsg.4326 = EPSG:4326 Version code: v20230628 = 2023-12-08 (creation date)
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks