Climate change: Daily minimum temperature projections, daily data, RCP4.5 scenario, resolution 0.125°

Open data API in a single place

Provided by AGENCIJA REPUBLIKE SLOVENIJE ZA OKOLJE

Get early access to Climate change: Daily minimum temperature projections, daily data, RCP4.5 scenario, resolution 0.125° API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
podnebje, projekcije, podnebne spremembe, Slovenija
Quality scoring

Dataset description

The database contains a time series of daily climate projections of the daily lowest air temperature in the period 1981-2100 for the scenario of greenhouse gas emissions RCP4.5 above Slovenia in the correct grid, resolution 0.125°. Simulations of six regional climate models are available for RCP4.5. The simulations are the result of regional models of the EURO-CORDEX project. Their resolution is 0.11°. The data are corrected according to measurements in Slovenia in the period 1981-2010 (the so-called bias correction). Find out more about the EURO-CORDEX project through additional links. The data is in NetCDF format files, which are divided into 30-year periods due to their size. There are four files available for each model. Each 30-year period is marked with the year of the last year of the period. Model projection files have names that contain information about the name of the variable, models, projection time, version, etc. separated by underscores. The components of the names are: name of variable (tasmin: daily minimum air temperature), model resolution (12 km: 0.125°), the name of the global climate model that gave marginal conditions to the regional, abbreviated greenhouse gas emissions scenario (rcp45: RCP4.5), ensemble parameters (e.g. r1i1p1), regional climate model name, projection version, projection time step (day: 1 day) and start and end dates of the projection (as YYYYMMDD where YYYY is year, MM month and DD day). The model results represent the physically possible states of the climate system in the future relative to the day, which in this case is the path of greenhouse gas concentration. As greenhouse gas concentrations cannot be predicted, the International Panel on Climate Change (IPCC) in its fifth report from 2014 produced four plausible scenarios for it, given the socio-economic evolution of humanity in the future. Since model results differ from one another and each of them represents a possible state of the climate, their results must be statistically processed. The differences between them form the basis for assessing the uncertainty of the projections. A summary of analyses of climate change by the end of the century in Slovenia can be found among additional links. There is also the first synthesis report on climate change in Slovenia, which contains a more detailed description of the methodology and results of climate projections. About climate projections are discussed in Chapter 1, on regional climate models, Chapter 3.2, and on the correction of errors or bias of models Chapter 4.3. One of the options for working with NetCDF files (extraction, aggregation, etc.) is the CDO program. Reading and statistical processing on NetCDF files are also possible with the statistical package R, especially its ncdf4 and raster packages. Links to CDO and R programs can be found in additional links.
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