Package a visualization client with the deployment

lewismc commented 1 year ago

We should leverage the CMC to provide the tag visualization capability. This task will research impact on architecture, identification of components, integration with docker-compose and other necessary configuration.

vtsontos commented 1 year ago

On the matter of CMC (aka COVERAGE Data Viewer) and as a precursor to our next tagup on the topic, just wanted to pass along some links below with a representative range of views illustrating support for both animal tagging data but also diverse oceanographic in-situ data from field campaigns more generally. As mentioned when we talked, I did recently integrate the full collection of MEOP (Marine Mammal animal telemetry) collection, comprised of 1,263 tag datasets. This was done mainly to test whether the tool could handle it given the large number of tag deployments present in this collection. Seems fine, which I think bodes well for the ICCAT work if this kind of visualization capability is of interest to the customer ultimately. (FYI, I have recently reached out to some marine mammal tagging folks at IMOS-Australia involved in MEOP and the new AniBOS-GOOS network on this, and they are taking a closer look).

The Viewer is pretty intuitive to use, but there is also online help (? Icon) and a User Guide providing a complete “how to” description of functionality. (At some point I need to put together a short tutorial video to help jump start new users). Chrome is the preferred browser but should be ok with Firefox also. One more recent feature included that is not mentioned in the current version of the Guide is the ability to click on individual points in an XY chart panel (eg. top Temperature vs Salinity plot in the MEOP Weddell Seal example – say an outlier) and see where along the trajectory on the map this point of interest occurred. The current time in the time control widget (bottom left) is also updated accordingly.

There are currently 2 containerized deployments of the Viewer on OIIP as you may notice via some of the URLs below ("Data-Viewer" and "Data-Viewer-Dev"). The datasets in both are identical, but the Dev version has some of the newest improvements. Since we have now effectively wrapped up the COVERAGE Phase-C project, Flynn has just pushed the latest updates that are ready for prime-time (eg. navigation feature mentioned above) into the "ops" version online and the JPL approved open source GitHub repo for the CMC Viewer software. (there are some additional features in the Dev. version that are experimental/not finalized, so not ready to be pushed to Dev. - eg. prototype integration with a satellite-insitu matchup/colocation service separately under development under the NASA/ACCESS-CDMS project).

In terms of other, backend software components needed for the Viewer:

POSTGRES (with PostGIS extension installed and and the 3 materialized Views mentioned: MVIEW_Data, MVIEW_Titles, MVIEW_Variables for the data, and then dataset and variable metadata respectively)
SOLR (conduit of metadata and data from postgres in a form the CMC-client application can consume easily)
GEOSERVER (conduit of spatial vector/point data in a standard form the CMC-client application can consume easily)
The satellite imagery available in the Viewer is via WMTS servers such as GIBS and/or OnEarth, deployed by COVERAGE with all the non-NASA ocean satellite data being converted into tile form and integrated on an on-going basis. For a couple of satellite products (Seascapes, Sargassum) we also connect to external THREDDS-WMS servers to get that data as imagery on-demand from the native netCDFs (no pre-tiling, so less performant but okay for region and lower resolution dataset). All such web-service pointers and satellite dataset descriptive information for each dataset layer are maintained compactly in a single postgres metadata table in the Postgres "Satellite" DB, consistent with what is done for the in-situ data.

We can go over these more detailed aspects further when we talk next if that would be helpful. But this should give you a general sense of what would be involved if we were to provide ICCAT with Viewer capability.

Ecological Data (animal telemetry, fish population census) IATTC Bigeye Tuna tag with Fishery Catch

MEOP (D.Costa, N. Elephant Seals, 2014 CA-current)

MEOP (IMOS Elephant [Seals)]

MEOP (IMOS Weddell Seals 2014 Antarctica)

Filtered Listing of all MEOP datasets in the Viewer

SPURS 1 & 2 Field Campaign SPURS1 Tenuse+Crate Glider, Seasoar

SPURS1 ADCP

SPURS1 Neutrally Buoant Float

SPURS1 Argo

SPURS1 R/V Endeavor TSG

SPURS2 Waveglider

SPURS2 Seaglider