Agricultural Drought Hazard Dataset – Crop Yield Loss (%) under Rainfed Conditions (EURO-CORDEX RCP8.5, İzmir Province) - CRIZ-ERS

Open data API in a single place

Provided by Zenodo

Get early access to Agricultural Drought Hazard Dataset – Crop Yield Loss (%) under Rainfed Conditions (EURO-CORDEX RCP8.5, İzmir Province) - CRIZ-ERS API!

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

Dataset information

Country of origin
Updated
2026.03.03 00:00
Created
2026.02.28
Available languages
English
Keywords
Quality scoring

Dataset description

This dataset represents the agricultural drought hazard quantified as percentage crop yield loss under rainfed conditions due to precipitation scarcity and increased evapotranspiration demand for İzmir, Türkiye under CLIMAAX Project The assessment follows the CLIMAAX Agricultural Drought Workflow and is based on: FAO-56 Penman–Monteith reference evapotranspiration (ET₀) Crop evapotranspiration potential (ETc) Actual evapotranspiration (ETa) Water stress coefficient (Ks) FAO Irrigation & Drainage Paper 33 (Doorenbos et al., 1979) Climate forcing is derived from: EURO-CORDEX EUR-11 Selected GCM–RCM combination RCP8.5 scenario 2066–2070 period (5-year climatological mean) Hazard Output Variable Yield loss (%) per grid cell Separate layers for: Maize Wheat Sorghum Barley Potato File Contents :  AGRICULTURE_DROUGHT_Hazard_izmir.ipynb Interactive Jupyter Notebook implementing the agricultural drought hazard assessment workflow for İzmir data_izmir mn30_grd Global Multi-resolution Terrain Elevation Data (GMTED2010). spam_folder SPAM 2010 v2.0 Global Crop Production Data (5 arc-min resolution) therm_clim FAO Thermal Climate Zones (ESRI GRID format) Hazard_izmir Crop Yield Loss Maps and data outputs
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