Use nccsv for example datasets for simplicity/visbility

[srstsavage]

Using the text-based nccsv format allows us to the self describing/embedded metadata features of NetCDF while also allowing easy visibility and browsing of the source data (text is more accessible than binary files).

https://coastwatch.pfeg.noaa.gov/erddap/download/NCCSV.html

[MathewBiddle]

My concern with this is IOOS does link to these files as Gold Standard Example datasets for the IOOS Metadata Profile and I don't think we want to be recommending nccsv as the standard format. https://ioos.github.io/ioos-metadata/ioos-metadata-profile-v1-2.html#gold-standard-example-datasets

IMO we should be exemplifying how to load datasets from a variety of formats. So, I propose that we only change one of these netCDF files to nccsv, but leave the rest as nc. If it would be beneficial to the community, we can provide a .cdl next to the .nc for readability on GH.

[srstsavage]

@MathewBiddle That’s a valid concern. I hate violating DRY but what if we kept both nccsv and nc copies of the example datasets here, made the nc files the default, and included a script to generate the nc files from the nccsv files? That way we could use the nccsv files as the source of truth and cleanly track changes to them via git, but also demonstrate running ERDDAP with standard nc datasets.

[MathewBiddle]

That seems like a viable approach. I'm onboard with it, and interested in what the script would look like.

[MathewBiddle]

@srstsavage FYI

The default branch has been renamed! master is now named main

See https://github.com/ioos/erddap-gold-standard/issues/52

[srstsavage]

Closing in favor of the CDL approach in #70