Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, a web toolkit designed to help citizens, conservation practitioners, municipal decision-makers, researchers, educators, and students advance knowledge and stewardship of fresh water. New to EnviroDIY? Start here

wofpy Timeout

Home Forums Monitor My Watershed wofpy Timeout

Tagged: , ,

Viewing 3 reply threads
  • Author
    • #17413

      Hello, I’m attempting to poll the wofpy REST endpoint for the most recent data from a site, however the requests timeout after 10-20 minutes. Is there another way to extract the most recent data for a particular site or series of sites?

    • #17418
      Scott Ensign

      @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:


      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).


    • #17421

      Hi Scott, thanks for your reply! I may have been unclear on what I’m attempting to do. I’d like to poll MMW every 5-10 minutes and return the current conditions at a site, not download the all time historical data as a CSV.

    • #17441
      Sara Damiano

      The WoFpy end-point should be usable.  Can you give an example URL that you’re trying?

      Are you setting up a system to regularly poll Monitor My Watershed?  If this is something you plan do to automatically and frequently, please email help@monitormywatershed.org so we can talk directly with to make sure you’re using the most efficient endpoint possible.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.