When you look at the sequence of time series for HG, your 01.Original is up to date but the 02.Editable is stuck at Aug 3rd.  The rating curve and discharge rely on this. The really weird part is that the data is actually there.  You can see on my graph below that the time series is showing data up to the 21st and the blue line perfectly covers the red.  I've seen this before and the problem isn't obvious.  I've done a delete of the agent and reloaded and refreshed with no luck.  Time to call Mr Wizard. Steve!!

Can you change the default quality on the 01.Original agent to 200 and adjust the quality of the 01.Original timeseries from August 3rd to 200?

Even if it doesn't fix this it should help prevent other issues down the road.  In the mean time you could change the Q 01.Original timeseries to use HG 01.Original timeseries so that you have flow data coming in until the HG 02.Edited timeseries can be fixed.

Jenn & Chris

No, it has not.

Thanks for posting Claire,

Does it transfer if you increase the quality from 254 to 200?

Hello,

I do not have any Q values on record since 08/03. In WISKI, at a first glance, it seems like the last HG datum also dates back from 08/03. However, when I plot the data (without selecting "apply time range") values appear until today's date, 08/08 (albeit a few hours behind). The gauge in question is Gauge - Bear Brook River near Bourget.

Any ideas on what is happening and how to fix it? Attached are some screen shots.

Thanks,

Claire

Hello everyone,


I thought that I would reach out on the forum and re-introduce myself since I have changed positions and will now be working more closely with many of you.

My name is Massimo Narini and my previous position was with Lower Trent Conservation as their Database Technician for the BQRAP program, but have since moved positions and am currently the WISKI Data Management Analyst for Quinte Conservation and the Hub.

I have only spent a couple of days this week in the position, but am excited to be able to work with everyone on some tasks that will benefit the Hub as a whole, as well as specific areas of need that have been determined through discussions with individuals.

I will be rolling out a small user guide that I created when in my previous position, mainly dealing with discrete WQ and Bio data, importing, station creation, that type thing, but have a few small edits to do before that happens.

I will be in contact with many of you over the coming weeks for some input, so look out for my emails!


Enjoy the long weekend!



-Massimo Narini
WISKI Data Management Analyst

Hi all,

Please see below for the response from our support team. It seems like you can build up a table mapping of exchange numbers / GOES ID's to ensure smooth transition of the data and avoid a plethora of replace functions.

To do so, simply open KiDAT and navigate to:

1. File > Edit Exchange # Lookup
2. Define the old and new numbers
3. Open the task that requires this mapping, select "Advanced Options" and navigate to "Use Exchange # Lookup".


Cheers,

Steve with KISTERS

Hi Chris,

I tried changing the minimum aggregation value from 0 to 1 and think that it solved the problem, but I'm not familiar enough with your data to know for certain. Is there a specific month you were using as a benchmark to check the 30 vs 31 day minimum?

Steve with KISTERS

Hi Daniel,

During the latest release the developers decided to remove the option of changing the time zone via the Set Properties to Time Series button. This was a result of people using this function and not shifting their data to account for it, causing larger headaches down the line when they realized what happened.

If you'd like to bulk change the time zone for the timeseries, you will need to do it via the backend. I recommend coordinating a time with Curtis Vance and our Support team to work through this.

Cheers,

Steve with KISTERS

Hi T Daniel Dickson,

This is what our Support team came up with regarding calling the data via KiWIS - the agent config is still under review. Can you give this a try and let me know if it works?

Steve with KISTERS

---------------------------------------------------

Regarding the KiWIS... The solution will be to use "Agent Comment" field in KiWIS to get those remarks from edited time series. But you can still get the same remarks from Original time series by using "Data Comment" field.
That happens because when you use "Copy time series agent" for Edited time series wiski will automatically change remark association from "Data values" (specified in the Original time series) to the "Agent" (edited time series)
There is a way to have the remarks association to be consistent across all the time series within parameter by using "Parameter" remarks. After that "Parameter" comment can be used to get the remarks for Original and Edited time series.