-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Hi,
for our visualisations on klimadashboard.at, we use the klima-v2-1d dataset for a variety of stations. We’re only requesting stations that have a start date before 1900, but even then we’ll often find gaps in the data between the start and end date. As an example, station ID 6 has metadata suggesting operation from 1896 until today, but there are gaps in temperature data f.ex. from 1981-05-01 to 1985-04-30.
The only way to discover these gaps is actually downloading the data repeatedly and checking whether the gaps still exist. It would be great to have data gaps included (and potentially explained) in a more performant metadata file, either by setting an "has_complete_data" boolean value or by including an array of data gaps, each with a start point and end point. This would make it very easy to filter all stations that have complete datasets from date X to date Y.
I raise this issue also because we’re repeatedly encountering timeouts on API requests even when we’re well below the 1000000 limit provided in the documentation. So it’s often not possible to download data for one station from start to finish, but only in smaller chunks, which makes identifying data gaps even more cumbersome.
Any pointers would be much appreciated, thank you!
Greetings,
David