-
Notifications
You must be signed in to change notification settings - Fork 0
ERDDAP Requirements for Data explorer datasets
These are the requirements for getting an ERDDAP dataset into CEDA:
-
ERDDAP version >= 1.80
-
Tabledap only, grids are not supported
-
Datasets must contain at least one of the supported Ocean Variables
-
Datasets must have variables -
time
,latitude
,longitude
. Ifdepth
isn't available, the depth defaults to 0. Supported variable names for the depth variable are limited todepth
andaltitude
-
For datasets that have two lat/longs use a variable like
precise_lat
/precise_lon
. See https://coastwatch.pfeg.noaa.gov/erddap/download/setupDatasetsXml.html#cdmTimeSeries -
cdm_data_type
must be one ofTimeSeries
,TimeSeriesProfile
,Profile
. Can't be aPoint
/Trajectory
/TrajectoryProfile
/Other
- If you aren't sure which cdm_data_type to use, see:
-
platform
is strongly recommended in either SeaVoX Platform Categories or IOOS Platform Vocabulary formats. It will categorized based on groupings defined in the L06 vocabulary, for example, 'research vessel' will appear in CDE under 'surface vessel'. See this example in ERDDAP:
platform: land/onshore structure
platform_vocabulary: https://vocab.nerc.ac.uk/collection/L06/current/
-
cde_ingest
is an optional dataset gobal to tell CDE not to harvest a dataset. Setcde_ingest
to 'false' to disable harvesting. -
Changes to your erddap dataset will take at least 24 hours to be reflected in the data explorer