Reference · built on requestCommons signalWeather & climate

GeoSphere Austria Data Hub

Austrian station values, gridded analyses and NWP forecasts from GeoSphere Austria through one dataset API with OpenAPI docs.

About

GeoSphere Austria is the federal institute for geology, geophysics, climatology and meteorology, successor to ZAMG. Its Dataset API serves every dataset through one URL pattern, host/v1/type/mode/resource_id, where type is grid, timeseries or station and mode is historical, current or forecast. Resources include the TAWES weather station network at 10-minute resolution, INCA hourly analyses, SPARTACUS daily grids, SNOWGRID, WINFORE, APOLIS, the Air Quality Index for Austria, and Numerical Weather Prediction and Ensemble Forecast grids.

Through Fibric, an operator calls the resource for a station or grid cell, reads the metadata for units and parameters, and proposes a start time, a setpoint or a frost action for a person to approve.

This is a reference listing. It documents what Fibric would read from GeoSphere Austria Data Hub and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The dataset index at https://dataset.api.hub.geosphere.at/v1/datasets, listing every type, mode and resource combination that exists
  • TAWES station values through station/current/tawes-v1-10min with parameters such as TL and station_ids such as 11035 (WIEN/HOHE WARTE)
  • Gridded analyses: INCA hourly, SPARTACUS v3 daily, SNOWGRID CL v2, WINFORE v2 and APOLIS short daily
  • Forecast grids: Numerical Weather Prediction v2 and Ensemble Forecast v2 1km
  • Synop weather station series and the Air Quality Index for Austria
  • Metadata for any dataset by appending /metadata, and the OpenAPI document at /v1/openapi-docs

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Start plant on the NWP forecast

    Read the forecast temperature for a building's grid cell and propose when the plant should start to be warm at occupancy.

    With Optimal Start

  • Freeze protection from 10-minute station values

    Watch TL at the nearest TAWES station and propose freeze protection when it approaches zero.

    With Freeze Protection

  • Guest comfort from INCA hourly

    Feed hourly analysed temperature and humidity near a property to comfort proposals for guest rooms.

    With Guest Comfort

  • Compare a season against SPARTACUS

    Pull the SPARTACUS v3 daily grid over your regions and attach this season's values to the demand outlook.

    With Demand Outlook

Requirements

  • Resource ids picked from the /v1/datasets index, since not every type and mode exists for every resource
  • Request sizing under the value limit: parameters × time steps × locations, missing values included
  • A rate-aware client that reads the x-ratelimit headers and backs off on 429
  • Attribution under CC BY 4.0 for data that needs no authentication
Authentication
None. The user guide states that currently no authentication is required to access data via the API.

Limits

  • Requests are limited to 5 per second and 240 per hour; the server answers 429 above that
  • A request may cover at most 1,000,000 values as JSON or CSV, or 10,000,000 values as NetCDF
  • The size check counts missing values, so an empty period can still exceed the limit
  • The former host dataset.api.hub.zamg.ac.at is deprecated

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request GeoSphere Austria Data Hub ↗

Questions and answers

How are requests limited?
To 5 requests per second and 240 per hour per user, reported in x-ratelimit-limit and x-ratelimit-remaining headers, with 429 when exceeded. Each request is also capped at 1,000,000 values for JSON or CSV and 10,000,000 for NetCDF, computed before processing as parameters times time steps times locations.
How is an endpoint addressed?
As host/v1/type/mode/resource_id. Type is grid, timeseries or station; mode is historical, current or forecast; resource_id comes from the /v1/datasets index. For example, /v1/station/current/tawes-v1-10min?parameters=TL&station_ids=11035 returns air temperature at WIEN/HOHE WARTE. Append /metadata for parameter and station details.
Under which license is the data published?
All data that requires no authentication is licensed under Creative Commons Attribution 4.0. Currently no authentication is required for the API, and the user guide points to the license page under Resources for further details.
Ask about GeoSphere Austria Data Hub

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.