After some modifications and tests, we are on to version 4!


https://quinteconservationwiski.shinyapps.io/DamOperationsDashboardV4/


There were issues with the slider for filtering on the far most left column ending up off the screen when displaying it on an iPhone, so you can now rearrange the column by dragging and dropping them in a new order so that you can access the slider for the column you need.

This idea could be used not only for tables, but also for graphs.

I think that many people would benefit from the creation of a dashboard to handle their DPC rather then the clunky Excel spreadsheets that seem to be common place around the Hub (personal opinion only).

Contact me if interested in learning more!



Massimo Narini, M.Sc | WISKI Data Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122

Hi everyone,



for those of you that are interested in viewing your data in different ways that are NOT within the WISKI environment, this may be of interest to you!

I have created a "Dam Operations Dashboard", which effectively allows our dam operators to have access to their data in table format from both historical data and the new data that is being imported to WISKI through Survey 123.

The link is here: https://quinteconservationwiski.shinyapps.io/Dam_Operations_V1/

It was created using R Statistical Program, a few different packages that are associated with it and KIWIS. I am sure there are potentially easier or more efficient ways of doing this, but I am proficient in R and know that I can fix this if it does malfunction, uses open source software and is fairly customizable if others would like something similar.

Each dam has its own tab, with each table being searchable, filterable by column and the time frame can be selected. It is not the fastest to load, but it is bringing in data from 2000 to current, so that kind of makes sense. It is also pulling data from a local CSV file until we are able to grab comments from a TS using KIWIS.


If anyone is interested in this code or understanding what is possible, feel free to get in touch with me and we can see what we can do!


Massimo Narini, M.Sc | WISKI Data Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122 

Hi Everyone,


I have had a few inquiries about the EC Climate Stations that are found in WISKI, mainly that they have not been updating for a few weeks.

The majority of the stations are polled by a custom spreadsheet made by Dave Eastcott at Quinte Conservation. Unfortunately, EC has changed their data format at the location that Dave had been scrapping the data from. In the coming weeks, he will rewrite the scripts that are running to pull the data from this location and it should be working again.

I do not have an official timeline, but was assured that it would happen soon.


If anyone has any better ways to get the data from here (Such as a KiDAT task): https://dd.weather.gc.ca/climate/                                 or an approximate location, please let me know.



Massimo Narini, M.Sc | WISKI Database Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122

There had been discussions here about doing the same, but nothing ever came of it.

I do not have any tasks that would be able to help you.

Sorry!



Massimo Narini, M.Sc | WISKI Database Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122

For anyone following this topic, I was able to modify the original task that Steve sent (MVCA_Goes_DIRECT_HopperExample.tsk ) and made it work with our PGMN wells that are operational using the new Hoppers!


I have added it on the master KiDAT task list on the server (PGMN Hopper GOES Task). For now, it is a shared task, but I would think this can be something that everyone will get their own version of due to the large number of stations that have the potential to be polled through it. It will need to be a different task than the already used GOES tasks.

The weird thing that I needed to do was to tell KiDAT that HG was parameter 4 and TW was parameter 3, even if they were not under those columns in the transmission and it is up and working now.

If there is anyone that would like this task or would like me to add their stations to it that do not have access to the master list, please email me!


Massimo Narini, M.Sc | WISKI Database Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122

I have been working with some Users in order to import historical data sets to stations that are already connected to a data source via a specific Import Number. With this type of data, it is difficult to create an Import number using the ZRXP conversion tool in KiDAT that will perfectly match the Import numbers that are already assigned to the time series due to differences in import number format for different data sources.

One way to get around this is to use the "Import/Export Import Numbers" tool in WISKI in order to quickly change import numbers for the time series of interest to match those found in the Historical data files and then change them back to not disturb the data connections that were made previously.

The attached file is a simple write-up of how to go about doing this.

Feel free to let me know if this is difficult to follow in any way and I will modify it and repost it.

Thanks!

Massimo Narini, M.Sc | WISKI Database Management Analyst
Quinte Conservation
MNarini@quinteconservation.ca
Phone: (613) 968-3434  ext 122 

@SteveWKISTERS  May be able to help or you will need to talk to Brandon at Kisters to get this sorted out.

Also, please include your name at the end of your posts so that everyone knows who you are 


-Massimo Narini
WISKI Hub Database Analyst, QC

@SteveWKISTERS


I am not sure which system the "8080" KiWIS URL is relating to, so Steve may be your best bet to get this sorted.


-Massimo Narini
WISKI Database Management Analyst, Eastern WISKI Hub

@SteveWKISTERS @cmcguire


I am opening this topic back up because I have also gotten stuck at the same point that Chris seems to have gotten, using very similar settings (which according to the help files should work), but doing the calculations outside of WISKI has gotten vastly different numbers. The manually calculated values I computed are very similar to the posted normals, making me think that the ones run through WISKI are not correct.

Any help would be greatly appreciated, but if no one has the answer, I will bring the question to Kisters support directly and inform everyone of the answer.

Thanks!

-Massimo Narini

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

Since there might have been other people following this post, I figured that I would tie it up since Steve and I have figured it out.

Basically you can bulk upload Locations as names (EG: Location 1, Location 2 etc) through the Keylist importer. When you are importing the data, you can then associate the location with a lat/long coordinate. I was under the impression that you could import a Location with its lat/long coordinates, but that was incorrect. Importing the Locations is the same as any other Keylist import.


Hope that helps anyone else that might have the same issue!

Hi Everyone!

Glad I was able to meet some of you at the last Eastern WISKi hub meeting, where I was told that we should be using the forum when questions come up, so here is the first one!

I am trying to import a large amount of WQ data with many individual "Sampling Locations" (many depth measurements at different coordinates), but they are all considered the same "Station". I can add "Sampling Locations" manually in the key list, but I need to bulk upload them since there are so many points of data.

Has anyone else bulk uploaded "Sampling Locations"?  I know how to do it for "Observation Spots" in the KiECO side of things, but of course they are slightly different.

In the key list for "Sampling Location", there is "name" as a column header, but it isn't in the importer dialog, so I am not able to add in new names. I have tried using "Label" in the importer, but it imports it into the WISKi abyss instead of into the key list.

Any help would be greatly appreciated.



*EDIT: Since currently "Sampling Location" is a key list, I can bulk import new entries to the key list, but this is still not properly using the "Sampling Location" function in WISKi. It won't allow me to import coordinates in WKT to the key list "Sampling Locations".

Thanks!

-Massimo