Model and satellite observational data to analyze microphysical processes in mixed-phase clouds

Open data API in a single place

Provided by Zenodo

Get early access to Model and satellite observational data to analyze microphysical processes in mixed-phase clouds API!

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

Dataset information

Country of origin
Updated
2026.02.24 00:00
Created
2025.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

These data were used for the analysis in the publication cited as Reference below. See Methods in the main article and Supplementary Sect. A.1. The model data were created using EC-Earth3-AerChem, NorESM2-MM, and ECHAM6.3-HAM2.3. For each of the models, 16 experiments were run (see Supplementary Table C2), and the additional experiment 'Meyers' for EC-Earth.All_models_Ref_iwc_lwc.zip contains zonal annual means of Ice Water Content (IWC) and Liquid Water Content (LWC) for the Ref experiment.The naming convention of the SLF (Supercooled Liquid Fraction), IWC and LWC model data is: {model}_{experiment}_{variable}_2018_monthly-annual_[zonal,box]_mean.nc. The geographical boxes are used in Fig. 3 in the main article and refer to: Northern polar (90-60° N), Northern mid-latitudes (60-30° N), Tropics (30° N-30° S), Southern mid-latitudes (30-60° S), Southern polar (60-90° S). All variables have the dimension T (temperature), since the data were binned every 5 K (see Results in the main manuscript). All averaging was done using CDO. Note that latitudes in ECHAM are reversed compared to the other models and GOCCP. The original source of the data in GOCCP_Observations.zip is https://climserv.ipsl.polytechnique.fr/cfmip-obs/Calipso_goccp.html. The data were zonally and annually averaged using CDO. Please refer to the article for more details.
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