ERDDAP > Data Provider Form - Part 1

This is part 1 (of 4) of the Data Provider Form.
Need help? Send an email to the administrator of this ERDDAP (marco dot alba at ettsolutions dot com).

Your Contact Information

This will be used by the ERDDAP administrator to contact you. This won't go in the dataset's metadata or be made public.

What is your name?
What is your email address?
This dataset submission's timestamp is 2024-11-22T05:38:30+00:00.

The Data

ERDDAP deals with a dataset in one of two ways: as gridded data or as tabular data.

Gridded Data
ERDDAP can serve data from various types of data files (and from OPeNDAP servers like Hyrax, THREDDS, GrADS, ERDDAP) that contain multi-dimensional gridded data, for example, Level 3 sea surface temperature data (from a satellite) with three dimensions: [time][latitude][longitude].

The data for a gridded dataset can be stored in one file or many files (typically with one time point per file).

If your dataset is already served via an OPeNDAP server, skip this form and just email the dataset's OPeNDAP URL to the administrator of this ERDDAP (marco dot alba at ettsolutions dot com).

How is your gridded data stored?

Tabular Data
ERDDAP can also serve data that can be represented as a single, database-like table, where there is a column for each type of data and a row for each observation. This includes:

Data that is currently stored in a relational database.
Please read the information about the EDDTableFromDatabase dataset type in ERDDAP, especially the initial ~2 screens of information which talk about the need to create a denormalized table. That may sound crazy. Please trust enough to read the rationale for this.
All in situ data.
Examples: a time series from an instrument or several similar instruments, profile data from a CTD or a group of CTD's, or data collected during a ship's cruise (the similar cuises over several years).
Non-geospatial data that can be represented as a table of data.
Examples: data from a laboratory experiment, genetic sequence data, or a list of bibliographic references.
Collections of other types of files (for example, image or audio files).
ERDDAP can present the file names in a table and let users view or download the files.

The data for a tabular dataset can be stored in one file or many files (typically with data for one station, one glider, one animal, or one cruise per file). We recommend making one dataset with all of the data that is very similar, and not a lot of separate datasets. For example, you might make one dataset with data from a group of moored buoys, a group of gliders, a group of animals, or a group of cruises (for example, annually on one line).

How is your tabular data stored?

Frequency of Changes
Some datasets get new data frequently. Some datasets will never be changed.
How often will this data be changed?

Finished with part 1?

Click to send this information to the ERDDAP administrator and move on to part 2 (of 4).