Archiving beach profile data

[emiliom]

Email to IOOS from 11/5/2018, to start connecting about archiving beach profile data. NCEI IOOS point person is Julie Bosch.

TO DO:

• Add follow up information from that email thread.
• See also my document notes.md, for a lot more information on this
• See also page 13 in the NANOOS DMP -- the entry for this dataset.
• Geospatial layer for sites
  • See the Geoserver layer Don and I created. It's nvs_test:BeachMapping, in the geoserver-dev (here's the link to the OpenLayers view)
  • Simple map demo: http://data.nanoos.org/files/beachmapping/. But currently (11/1/2018) I can't get the geopackage file to load as a layer w/o errors in geoserver-dev. For now, I created a shape file version manually and redefined the data store to use it. Note that it currently excludes WA points, because the SLD style excludes them!
  • WFS request that returns GeoJSON: http://data.nanoos.org/geoserver-dev/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=nvs_test:BeachMapping&outputFormat=json
  • I uploaded that GeoJSON as file Geoserver-devWFS-nvs_test_BeachMapping.json into this github repo, so it's easily accessible, visualized on a map. Likewise, I uploaded a csv as file Geoserver-devWFS-nvs_test_BeachMapping.csv, so it's easily browseable on github as a table.

Hi Julie and Kathy,

I'm writing to consult about archiving of a NANOOS dataset that is not a conventional sensor-based time series. This "beach shoreline" dataset is a series of annual surveys of beach profiles at a regular set of transects, carried out in order to document the seasonal, interannual, and long-term changes taking place at a range of spatial scales, in support of hazard mitigation.

NANOOS supports shoreline data collection in Oregon and Washington, carried out by two different teams, but initially we would probably focus on the Oregon data. Jon Allan (cc'd here) is the NANOOS PI responsible for this dataset.

NANOOS previously set up an NCEI Submission Agreement (SA) for a collection of fixed-location sensor monitoring time series (see http://www.nanoos.org/documents/certification/DMP/NANOOS-NCEI-Submission_Agreement_2017-03-13T19-51-12.pdf). As that's a more conventional set of ongoing sensor data, we set up the expected automated process using netcdf files that follow the NCEI template. The plan is to reuse many of the metadata conventions we adopted in that SA, for consistency across NANOOS submissions. But clearly we're now dealing with a dataset that's very different, and it's unclear to us what the best approaches will be regarding data format, metadata encodings, submission process, etc.

We'd like to start discussing this with you to help us arrive at appropriate technical decisions.

In the meantime, you can find more information about this dataset on the NANOOS Beach and Shoreline Changes application; for an example, see the plots here. The Data Management Plan for this dataset is here.

[emiliom]

If we go with archiving netcdf files, we'll likely use NCEI NCEI NetCDF Templates v2.0, specifically the trajectory Feature Type Gold standard. A complication may be that this requires "A series of data points along a path through space with monotonically increasing times", whereas the data file I've seen doesn't have times associated with each point; it only has a date associated with the whole transect.