Thanks Gord. We'll fire this over to you once its complete.

Hi All,

This is to gauge the community's interest in access to a CoCoRaHS task / converter. If you already have access to one, please comment on this post so that we aren't redeveloping anything. Otherwise, a shareable task / workflow is anticipated in the near future.

@cmcguire @Dave Eastcott @Gord Gallant

Cheers,

Steve

Sure Holly no problem. Can you give me some more information? Namely:
1. Does this station have any other data associated with it? If not, you could simply rename the old Station to meet the new criteria.
2. Is the new Station assigned to be a WQ station in the station characteristics? If not, please turn that on.

With that said, if you're looking for a comprehensive grab of all the data and metadata, I'd recommend exporting the data out as a CSV (takes about 2 minutes) using all the columns you're interested in. Save that Export configuration, as you can re-use it for the Import.
Bulk change the Site / Station Name / Station Number as needed to meet the new Station info.
Re-import, using the Export configuration to pull in whatever data you decided to bring along.

All in all this should take about 10 minutes or so - if you run into issues please let me know.

Cheers,

Steve with KISTERS

Perfect! Could you use the "mark thread as resolved" button to indicate that this is topic has been cleared? It helps me sleep at night .

Cheers,

Steve with KISTERS

Hi Stacey,

The person that knows the most about connecting IP modems is either Chris McGuire (MVCA) or Brandon. I'd try Chris first if you can, as he's gone through the whole process fairly recently. I'll follow up with an email to you with his information.

Cheers,

Steve with KISTERS

Hi everyone,

Just a quick heads up here - if you change to the GOES platform from any other telemetered logger, you need to update the Timezone of the Time Series to reflect those changes. Typically you're setting the time series timezone to Eastern (UTC - 5), but the GOES platform does not use a shift (i.e. UTC 0).

Best practices here are to deactivate your old import agent and add a note indicating that this was the old telemetered station agent. Then add a new, active import agent with the updated GOES exchange number and timezone fields.

Credit to Mark Helsten and Scott Drebit for this one.

Steve

Hi Holly,

I I sent over a copy of all the webscrapes that we've developed so far to Massimo after we spoke about the list you had generated. I think the plan is to compare what we've already created to the list you generated.

That said, I don't think this RT site is on there - I'll start a discussion for the Eastern hub for how to proceed with the missing sources, and check in with the other groups to see what they've got.

Cheers,

Steve

Awesome, thanks Holly!

Iryna, can you take a look and mark this thread as complete if Holly's approach will work for you?

Cheers,

Steve

Hi Iryna,

I think quite a few people are doing this. If you need a refresher after our meeting with Massimo last week, I'd be happy to sit down and review all this stuff with you again.

Just to recap the major principles:

Required inputs:
- long term normals
- monthly input time series

Calculation: (monthly input / long term normals) * 100

You can do this in a few different ways. One way is the General correction agent, set to "Divide". You'll want to add your input time series, then your long term normals (i.e. order is important).

After that, go to the Transformation and either use the Eval() or Factor() statements. I prefer Eval() because its clearer "Eval(value*100)" versus the Factor(100) approach. It reminds me in a few months that I'm actually multiplying.

As an aside, I asked the Developers if they could change Factor() to Multiply() but they weren't biting .

Cheers,

Steve

Hi everyone,

I was wondering how you've got your KiDAT tasks set up to handle the WSC format of approvals, codes, and remarks. Are you combining those into one field, separating them, or ignoring them all together?

Cheers,

Steve with KISTERS

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

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

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

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