@ensign
Active 6 days, 14 hours agoForum Replies Created
-
AuthorPosts
-
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 the development of release v0.18, including “Batch upload protocol extension” and “Implement AWS SQS for post requests from devices“.
I would not expect that the lags you are experiencing to be persistent.
2023-12-28 at 8:30 AM in reply to: Changes coming January 1, 2024 for Monitor My Watershed users #18279@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.
2023-12-21 at 8:19 AM in reply to: Changes coming January 1, 2024 for Monitor My Watershed users #18265@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!
2023-12-01 at 12:19 PM in reply to: Changes coming January 1, 2024 for Monitor My Watershed users #18202@w3asa – Thanks for sharing your thoughts on our subscription plan pricing structure. We arrived at this pricing structure after exploring all the options for most equitably distributing costs across the diverse community of users and organizations. We hope users appreciate the extra value that Monitor My Watershed provides in comparison to other for-profit commercial services. We value your participation in growing one of the largest environmental datasets in the world collected and shared using open source hardware and software!
2023-12-01 at 12:00 PM in reply to: Changes coming January 1, 2024 for Monitor My Watershed users #18201@juleschultz – We certainly understand how valuable it is for Monitor My Watershed users to share their data on their own websites. While there isn’t a direct way to share Monitor My Watershed webpages, there are several ways to automate the data download process for reprocessing and posting your data in a separate service. First, you can retrieve a csv file of all of a parameter’s data by copying the url from that sensor’s observations page. Look for the cloud download button; the url will look like this (with a different result_id):
https://monitormywatershed.org/api/csv-values/?result_id=5081
There are more sophisticated methods for retrieving data using Monitor my Watershed’s Time Series Analyst endpoint. If you use Python, check out Sara Damiano’s GitHub Gist notebook for instructions.
To share a link on your website to all of your organization’s sites use this link:
https://monitormywatershed.org/browse/?organizations=Spokane%20Riverkeeper
Modify this link for other use with other organizations using the release notes on GitHub.
2023-04-13 at 11:21 AM in reply to: MMW last-reported observation not updating after site update #17732@millerlp: are you seeing current data now? We are aware of the issue but it should be resolved now. If you are still seeing issues can you report them to help@monitormywatershed.org?
On a Mayfly V1.0 Rev A3, is power to the 2X10 analog header controlled by pin 22 or is the header constantly powered? I’m trying to utilize power from the 2X10 analog header while the grove ports are not powered (pin 22 is low) if this is possible.
@wcb_data: you can access csv formatted data for a parameter at a site by specifying the parameter ID. For example, I can retrieve all of the specific conductivity data for site https://monitormywatershed.org/sites/CR_UTFZ/ with this url: https://monitormywatershed.org/api/csv-values/?result_id=5081
You can grab this url for any parameter at a given site by right clicking the download button (see attached screenshot).
Alternatively, you can access all data for a given site; here’s an example for the site used earlier:
https://monitormywatershed.org/api/csv-values/?result_ids=5081,5082,5084,5085,5088,5089,5091,5093
The url is available by right clicking the “Download Sensor Data” button at the top of the “Sensor Observations at this Site” section (see attached screenshot).
Attachments:
Given the popularity, complexity, and expense of turbidity sensors, the team here at the Stroud Center has compiled a snapshot of some commercially-available options that may help people decide on the best option. This table likely excludes many vendors and models, and it only summarizes sensors that we have recently used or investigated. In addition to these commercially-available options, you might consider do-it-yourself options like OpenOBS, a well-document project on Github with a peer-reviewed background. Another open-source DIY turbidity sensor is described by Droujko and Molnar 2022 in Nature, Scientific Reports.
- Campbell Scientific Clari-Vue (recently replaced the OBS3)
- no wiper
- pre-calibrated
- SDI-12 at 5V
- 9.6-18V (nominally 12V)
- compatible with Mayfly version 1.1 (or any Mayfly version with an interface board with separate 12V supply)
- compatible with Modular Sensors
- $$ on a scale of $ (<$1000), $$ ($1000 – $2000), and $$$ (>$2000)
- Yosemitech Y511-A
- includes wiper (the Yosemitech Y510-B does not include a wiper)
- pre-calibrated
- Modbus over RS485
- 5-12V (nominally 12V)
- compatible with Mayfly version 1.1 with EnviroDIY RS485 adapter (or any Mayfly with both separate 12V power supply and RS485 adapter)
- compatible with Modular Sensors library
- $
- Turner Designs Turbidity Plus
- available with and without wiper
- not pre-calibrated
- analog voltage communication
- 3-15V
- compatible with Mayfly version 1.1 with multi-purpose 6 pin screw terminal grove adapter (or any Mayfly with a voltage divider with separate 12V power supply)
- not compatible with Modular Sensors library
- $$
- Turner Designs Cyclops 7
- no wiper, but has an optional cap to protect the sensor window
- not pre-calibrated
- analog voltage communication
- 3-15V
- compatible with any Mayfly version with multi-purpose 6 pin screw terminal grove adapter
- compatible with Modular Sensors library
- $$
- Analite NEP-5000
- includes wiper
- pre-calibrated
- SDI-12 or Modbus over RS485 or analog communication
- 8-30V
- compatible with Mayfly version 1.1 (additional adapters required depending on communication protocol used)
- not compatible with Modular Sensors library
- $$$
-
AuthorPosts