Scott Ensign

Instructions for uploading csv data to Monitor My Watershed are in section 7 of the Monitor My Watershed Sensor Data Manual. Note that there are different instructions for “Uploading EnviroDIY Monitoring Station Data – Filling Data Gaps” and “Uploading CSV Sensor Data Not Already Formatted for MonitorMW”.

Hi Jake, I’ve checked with the Seagull developer at GLOS. It is technically possible but will require them to do some coding on their end. I’ll keep you posted.

Neil, there is a faster and more flexible way to extract data from Monitor My Watershed. Instead of using the CSV download button, try using either python or R to extract specific time periods of data for specific sensors and stations. Sara has documented these methods here:  python version and R version.

Yes, the Stroud Center has a Campbell Scientific phycocyanin sensor deployed on a Mayfly Data Logger. @shicks might be able to share code with you.

@tahicksonstthomas-edu: @srdamiano developed a way to query the Monitor My Watershed database for a specific parameter and specific time/date range. This is a huge improvement over using the Download button to retrieve your data, because you can limit the timeframe of data being retrieved and thus speed up the response. See Sara’s code here for R…[Read more]

Hi Andrew. Thanks for sharing this code; I hope others have been able to implement this. @brianjastram recently asked if an “alarm” feature would be built into Monitor My Watershed (hopefully someday as resources allow). Until then, I suggested that your code might benefit from the work @srgdamiano did to specify parameter and time/date range…[Read more]

Brian, note that @andrewglaros3 developed a similar function here. That python code might be enhanced by targeting a more precise time period with each call to Monitor My Watershed, and @srgdamiano developed python (and R) code to do just that. See her Github repo on this: https://gist.github.com/SRGDamia1

Hi Brian. We’ve discussed adding this feature for a long time. I didn’t see this noted as a Github issue, so I added it here. Feel free to add suggestions to that issue.

@rhouck, @damiano moved this post to a new thread here. I noticed that you reposted to a different thread. Please reply to this thread.

You should not need to take any further action besides clicking the check box. I can confirm that it is not working for me, either. I added this as a bug on Github.

The site may be slower to respond on the 5 minute, 15 minutes, and hourly intervals (although 1 minute seems extreme). Any device (with an accurate clock) posting data at these intervals hits the server at the same time, and response time of the site briefly slows at these moments. Several actions are being taken to eliminate this phenomenon in…[Read more]

@neilh20 Thanks for your questions. Please refer to the Terms of Use for details concerning use of Monitor My Watershed. @srgdamiano commented on the likely cause of missing data from September 26. We are continuing to improve Monitor My Watershed’s response time and performance; we will share details in early 2024.

@paulwilson Yes, the payment page for Monitor My Watershed subscriptions will begin accepting payments on 01 January 2024. Thank you for supporting Monitor My Watershed!