-
Notifications
You must be signed in to change notification settings - Fork 8
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
Download Sensor Data failing #738
Comments
This worked today. It maybe that it is sensitive to the size of the database being downloaded, and might need an indication that work is in progress. |
I'm not getting this on firefox looks like its firefox timing out after 5minutes. Sorta feels like >NULL |
@neilh10, thanks for bringing this to our attention. The CSV download endpoint is unfortunately one of those The current CSV download endpoint is very inefficient and I'm guessing that your long time series are causing it to fail. @ptomasula and I will look into it further, and also prioritize the following issues for the next round of maintenance work expected later this winter.
cc: @ScottEnsign, @SRGDamia1, @s-hicks2 |
Thanks @neilh10. I agree with everything @aufdenkampe noted above, but will add that server logs confirm that this is a server timeout issue. As a short term work around I would suggest trying to download timeseries for individual parameters as opposed to the download all the station data. ![]() Downloading the timeseries for the single parameter still takes a good number of seconds (~30-40 seconds) but did successfully complete for me, and was well below the timeout threshold of 300 seconds. The URL in your screenshot above includes 8 result_ids, which with the 30-40 seconds per timeseries is right around that timeout limit. |
@ptomasula thanks for the tip of being able to get some data out. @aufdenkampe thanks for the response and insights. i hear the story, and technologies have discrete increments - and like the metaphor of the chain the weakest link in the chain defines the chain. Software has creative ways of being fixed, often by characterizing and detecting weak links before they become visible to everyone. oh well.! |
@neilh10, I'm glad that you now have a solution for getting what you need while while you wait for the fix. As you can see by the dates on related "download" issues, we've been aware of this issue from long before we inherited the codebase (see #312 from 2018) but were only able to complete one (#651) of the three tasks we identified to fix the problem (see #650 (comment)). We had to prioritize other more pressing issues. Fortunately, we've been able to take care of those bigger issues and can now prioritize this one. |
Given the timescales, and I contributed absolute basic features in 2018, maybe its a conversation about the simplest vision of a working system. |
@neilh10, there is faster and more flexible method of retrieving data from Monitor My Watershed using R and python scripts. @SRGDamia1 shared the python version and R version. |
@ScottEnsign thanks for the suggestion - I'm trying to support real-world landowners, there is a good chance if they ask a question its likely ~ with a grin ~ to be about where do they get a Python to ask for the data. |
For a node on monitormywatershed.org, When I press the "DOWNLAOD SENSOR DATA" there is no action. In the past this results in a download of all stored data. There is no feedback to say its failed.
eg for the following in Chrome or Firefox
https://monitormywatershed.org/sites/nh_LCC45/
I tried this over 4 hours a number of times today - and no download any time
Monitoring MMW uptime doesn't seem to indicate any failures in DataStream bit.ly/mmw-uptime
Should I expect to be able to diagnose a failure -for user facing Homepage
The data stream does show an earlier failure
The text was updated successfully, but these errors were encountered: