-
Notifications
You must be signed in to change notification settings - Fork 39
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
Turkiye reporting inconsistently #1047
Comments
This is one of the simpler adapters, so I doubt it is on our end, but I will investigate further before we close this issue. |
this could be an issue on ingestion as well. Definitely worth investigating a couple of different angles |
@majesticio any update on this? looks like we're still getting spotty coverage |
@russbiggs I have not identified any problems with the code, I will keep an eye on this manually and see if I can catch one of the discrepancies and troubleshoot from there |
So each request from the Turkiye adapter returns measurements for all 300+ stations for just one hour. My guess is that some of the responses are returning empty handed. Perhaps we can explore using the offset deployment to fetch the same url 2 or even 3 times per hour |
Turkiye's site has been down for weeks. We should continue to check on it periodically: |
Turkiye is apparently still live, but has been shut off to people outside of Turkiye. Possibility of using some kind of proxy to get the data should be explored. |
It looks like we're getting spotty coverage from Turkiye. Looking a number of locations many hourly measurements are missing e.g. sensor_node 368956
The text was updated successfully, but these errors were encountered: