Interesting Repos for BiG CZ Toolbox: IWN-Ingest

[aufdenkampe]

Here's another interesting Repo to consider including in the BiG CZ Toolbox, or perhaps even the BiG CZ Portal or our ODM2 software stack such as ODM2WebSDL:

• https://github.com/LimnoTech/IWN-Ingest
• for ingestion of observation data into an Interoperable Watershed Network (IWN) 52N SOS-based data appliance. The IWN is EPA's pilot portal for discovery of and access to continuous water quality sensor data collected by agencies around the United States.

The metadata files for the OGC Sensor Observation Service (SOS) seem very similar to what we have discussed for YODA files and what we need to "register" for every station within the ODM2WebSDL.

What do you think @emiliom & @horsburgh?

[emiliom]

After a quick look, I would say IWN-Ingest is an entirely different beast compared to https://github.com/heigeo/climata (from your other issue) or ulmo. In some ways it parallels the complete end-to-end architecture we're shooting for in BiG-CZ/ODM2, the CUAHSI HIS architecture and -- unsurprisingly -- the IOOS architecture.

What I would suggest is a conference call with that team to exchange experience and see if there are any reasonable areas of collaboration or fruitful overlap. They're a pilot project and we're under a short time frame, so it may be hard to align things at this stage. I'd be up for a web conference call next week or later. As you know I've known about that project for some time, but hadn't been in the loop on its progress. I have an extra interest from my IOOS/NANOOS perspective.

[aufdenkampe]

??Yes, I agree that IWN-Ingest is very different as it is about streaming data into an SOS database, whereas the other Repos were about pulling data from databases. I see that my issue post wasn't clear about what I was thinking, which is in short a comment that we might want to consider: * ??listing this as another possible tool for moving data in/out of large data systems * working (slowly?) toward aligning our streaming time-series work with SOS, especially given that we are presently working out similar metadata issues with ODM2WebSDL for the EnviroDIY Citizen Science work. I'm not at all working on the LimnoTech team developing IWN-Ingest, so I'm not quite ready to set up a meeting yet until I learn more. Anthony

…

_____________________________________ Anthony K. Aufdenkampe, Ph.D. Senior Environmental Scientist 7300 Hudson Blvd, Suite 295, Oakdale, MN 55128 Office: 651-330-6038 x306 Direct: 651-219-4076 email: [email protected] LimnoTech www.limno.com<http://www.limno.com/> Water Environment | Scientists Engineers

________________________________ From: Emilio Mayorga <[email protected]> Sent: Tuesday, January 3, 2017 11:36 AM To: BiG-CZ/BiG-CZ-Toolbox Cc: Anthony Aufdenkampe; Author Subject: Re: [BiG-CZ/BiG-CZ-Toolbox] Interesting Repos for BiG CZ Toolbox: IWN-Ingest (#2) After a quick look, I would say IWN-Ingest is an entirely different beast compared to https://github.com/heigeo/climata (from your other issue) or ulmo. In some ways it parallels the complete end-to-end architecture we're shooting for in BiG-CZ/ODM2, the CUAHSI HIS architecture and -- unsurprisingly -- the IOOS architecture. What I would suggest is a conference call with that team to exchange experience and see if there are any reasonable areas of collaboration or fruitful overlap. They're a pilot project and we're under a short time frame, so it may be hard to align things at this stage. I'd be up for a web conference call next week or later. As you know I've known about that project for some time, but hadn't been in the loop on its progress. I have an extra interest from my IOOS/NANOOS perspective. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#2 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AE7T1H11IHaqa_KEmHYq5bbURIS_kptCks5rOocMgaJpZM4LZz6O>.

[emiliom]

Thanks for the clarification. That all sounds like it's beyond our burning priorities and possibilities within the BiGCZ funding time frame, IMHO.

I'd still be interested in learning more, eventually.