Hi Everyone,

Here's the actual waterlevel.gc web scraper task that you might be looking for. Brandon and I worked on this with Stacey Van Opstal of Hamilton CA last week. Thought it might be useful.

Steve with KISTERS

Changing the timestamp format can have unintended consequences - WISKI may catch some values, but likely won't recognize all of them and you may end up with truncation. You need to figure out how to get your timestamp values into 1 consistent format with the script that you're running.

Has anyone else run into this problem before? See attached CSV screencap as an example. About halfway though the timestamp shifts from a String with values in 24 format to a Number/Date in non-24 time (although it's displayed in 24 hour time).

Steve with KISTERS

This is what I just sent to Steve via email. I don't know what is happening with the time dropping the seconds but it doesn't seem to be causing a problem for WISKI (time format appears to have changed going September to October):

09/30/2018         10:00:00 PM       1.20
09/30/2018         11:00:00 PM       0.20
10/01/2018         12:00:00 AM      0.20
10/01/2018         01:00:00 AM      0.00
10/01/2018         02:00:00 AM      0.00
10/01/2018         03:00:00 AM      0.00
10/01/2018         04:00:00 AM      0.00
10/01/2018         05:00:00 AM      0.00
10/01/2018         06:00:00 AM      0.00

The script formats the date as "MM/dd/yyyy HH:mm:ss". How it gets to be AM and PM from that I don't know but it does.And that is in the data not at the end where the problem we are having is the data is not up to date..

Hi Pat,

After reviewing the files you sent, it appears that KiDAT is not converting files that use a timestamp that is different than expected. At some point through the Hobo file the timestamp switches to a new format, and KiDAT ignores these values.

I believe Holly Evan's post on the Hobo ProTemp Logger solves this issue. She recommends forcing a download in 24 hour time to standardize the timestamp throughout the file. See below.

Quote from: hevans on April 20, 2018, 10:13:35 AM
Hi,

The issue is with exporting from the HOBOware. Need to identify 24-hour time format in the Export settings under Preferences. If this isn't done then the exported file flips back and forth between formats / doesn't always recognize the date time stamp as a date.

- Holly Evans

I'm actually starting to roll out Precipitation Intensity as a parameter.  I think it will be useful in distinguishing the shorter but more intense rain events we are seeing with climate change.  Before seeing this post, I worked with Noah at Kisters Support to come up with this simple transformation to change the unit of measure from Precip in (mm) to (mm/hr).  I'm also totaling the precip per hour off the 02.Edited time series.  This should work regardless if the rain gauge is tipping bucket giving 15 min totals or the more accurate accumulators.

I'm developing a web page for our flood duty officers that is responsive (viewable on a cell phone browser) and gets the latest values via Kiwis calls...

http://waterdata.quinteconservation.ca/KiWIS/qc_flood.html

What do you think?
David M

Hi Sue Lee,

When importing the water quality data there is the ability to map any symbols (I. E. < > ~) to the Symbol attribute. These are stored with each applicable value result in the system.

You can find the the symbol column if you navigate to Import > Sampling > Available Columns tab.

Note that if the symbol and value are stored in the same column in Excel,  I believe you will need to use the split function to separate the symbol from the value.

Steve with KISTERS

Hello, 

I was wondering when importing data with less then (<) values do you keep the (<) symbol or do you edit the data? For example if a value reads <1 do you edit it to read 0.5, as entering 1 is an incorrect value?  I know in excel (<) values can't be worked with you have to edit the value to get rid of the (<) symbol. Is WISKI the same?  Any help would be greatly appreciated. 
Thanks, Sue Lee (A Newbie to WISKI)

@SteveWKISTERS @massimo.narini

Hi everyone,

Sorry for the long absence. I checked this out today and the issue was resolved - there are Q values up to the current date. Does anyone know how this was resolved?

Steve with KISTERS

@SteveWKISTERS

Terrible graph..