...
The descending portion of the cast is then extracted (this will be user configuration in the future, as well as cast detection, alignment, binning parameters). This data product is only used with aligned and depth binned data and extracted down casts. Also, this data product includes data from sensors that are connected to the parent device. The naming convention of for these plots informs what data has been included in that particular plot; the different types of data are delineated by two '_' at . At the end of the filename is are the start and end date dates of the cast which is separated by one '_'. An example of the filename when the plot is created through datasearch can be seen below. These plots are also available through the geospatial map for community fishers, when these plots are downloaded from the geospatial map the filename has -large appended to the file name, there is also an example of these file format formats below.
- SalishSeaMarineSurvivalProject_Irvines_Sechelt_temperature__practicalSalinity__chlorophyll__oxygenSaturation__20180510T214842Z_20180510T215129Z.png
- SalishSeaMarineSurvivalProject_Irvines_Sechelt_temperature__practicalSalinity__chlorophyll__oxygenSaturation__20180607T222420Z_20180607T222608Z-large.png
This data product is very similar to the Cast Profile plots, documented here: 56. The major difference is that each profile within the image is for one cast and one sensor. This data product is currently constrained to aligned and depth binned sensors on Community Fishers casting devices (CTD, oxygen sensor, fluorometer), and when used for at the device level will only display the four major ocean properties: Temperature, Practical Salinity, Chlorophyll and Oxygen Saturation. An example of a device level cast scalar mulit-profile plot can be seen Cast Scalar Multi-ProfilePplot is available below.
Oceans 2.0 API filter: dataProductCode=CSMPP
...