-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameters start_date and end_date not working as expected. #859
Comments
Dear @TheAnalystx , apparently when I run the code I get actual data: station_id dataset ... value quality
0 05490 temperature_air ... 99880.0 2.0
1 05490 temperature_air ... 99850.0 2.0
2 05490 temperature_air ... 99820.0 2.0
3 05490 temperature_air ... 99810.0 2.0
4 05490 temperature_air ... 99800.0 2.0
.. ... ... ... ... ...
355 05490 precipitation ... 0.0 2.0
356 05490 precipitation ... 0.0 2.0
357 05490 precipitation ... 0.0 2.0
358 05490 precipitation ... 0.0 2.0
359 05490 precipitation ... NaN NaN Could you give more details on your environment and the request? What would |
Interesting, it works now for me too. It was late in the night, I will try to reproduce it. Maybe I can find a pattern. Thanks for your fast feedback! |
Issue re-appeared, time of execution was 23:11 Berlin Time.
|
Thanks for the report! I also did a request just now and still got values: station_id dataset ... value quality
0 05490 temperature_air ... 99330.0 2.0
1 05490 temperature_air ... 99310.0 2.0
2 05490 temperature_air ... 99310.0 2.0
3 05490 temperature_air ... 99290.0 2.0
4 05490 temperature_air ... 99280.0 2.0
.. ... ... ... ... ...
355 05490 precipitation ... 0.0 2.0
356 05490 precipitation ... NaN NaN
357 05490 precipitation ... NaN NaN
358 05490 precipitation ... NaN NaN
359 05490 precipitation ... NaN NaN Did you switch off the cache for once and try the same request? |
Yes, the issues persisted when I turned it of by using |
Thanks for the feedback! I just ran it again and again got values: station_id dataset ... value quality
0 05490 temperature_air ... 98630.0 2.0
1 05490 temperature_air ... 98620.0 2.0
2 05490 temperature_air ... 98620.0 2.0
3 05490 temperature_air ... 98620.0 2.0
4 05490 temperature_air ... 98590.0 2.0
.. ... ... ... ... ...
355 05490 precipitation ... 0.0 2.0
356 05490 precipitation ... 0.0 2.0
357 05490 precipitation ... 0.0 2.0
358 05490 precipitation ... NaN NaN
359 05490 precipitation ... NaN NaN |
Hi a short question, does this code work for you?
Because I receive:
I tried to create a completly new conda env because of the other error. As for the other error: |
The given code also throws an error for me. It is caused because for the specific method we throw together different metadata of all requested datasets and then some stations are not existing in all datasets. I'll try to figure a solution as soon as possible. Until then try to request the datasets separately! |
@gutzbenj Thank you for your answer, should I create a different ticket for the issue? |
@TheAnalystx I think it falls in the same category as the skip_empty issue, so guess no separate ticket required |
Dear @TheAnalystx , I tried working on some improvements regarding the problem of having empty data at #889 . The main idea there is that you set There are currently some problems: This will result in the parameters not being considered empty in the calculation step of data availability simply because they are not present in the resulting dataframe. Thus tendentially the rate of available data is higher that it should be because empty datasets are not taken into account. This is not the case for parameters in the available datasets because there we have the given date range of that dataset that is being taken even for completely empty parameters. The whole topic is quite complex to explain, should we have another chat? |
Dear @gutzbenj yes lets have another chat, is there such a functionality on github? sounds complicated, but would be a huge boost in accessablity in my oppinion. |
I found some solution, but if you like we can still have a chat and I may introduce you to the whole library. There's no such functionality but we could just do a skype/whatever call. |
I just pushed some changes to main, so if you install now the live from from Github the code should be working for you. You can select the criteria for missing values like E.g. if you request "precipitation_height" and "temperature_air_mean_200" and have the following availabilities
the station would fail for the above setting with |
Hello @gutzbenj, is it possible for you to take some time to see a similar problem? I just learned about this project and find the time filter quite confusing. I run the example dwd_obs_station_gaussian_model.py in the example folder. I debug the code and the station_data_one_year has the value attached. Notice: this example also has a small mistake, it generates an empty figure with no reason, if I find where the cause is, I will update it. dwd_obs_climate_summary_describe_fields.py file in the example folder also have errors. |
Dear @ricoeo , Thanks for reporting this! I'll have a look at this and answer to you later this day! |
Describe the bug
Parameters start_date and end_date not working as expected. They don't return stations data even tough there should be data available.
To Reproduce
You can see that data is available for the specific interval if you comment out start_date and end_date.
Expected behavior
Should return data for only the time frame specified.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: