Data Access Form

Dataset Title:	EuroFleets cruises metadata
Institution:	EuroFleets (Dataset ID: EUROFLEETS_CRUISE_METADATA)
Information:	Summary \| License \| Metadata \| Background \| Subset \| Files \| Make a graph

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable

Optional
Constraint #1

Optional
Constraint #2

Minimum

or a List of Values

Maximum

cruise_ID

research_vessel

time (Start Date, UTC)

date_end (End Date, UTC)

ICES_shipcode

"11BU"

"GLSW"

details_link

"http://rvinfobase...."

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

File type: (more information)

(Documentation / Bypass this form )

(Please be patient. It may take a while to get the data.)

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  cruise_ID {
    String long_name "Cruise ID";
  }
  research_vessel {
    String long_name "Research Vessel";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Start Date";
    String source_name "date_start";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  date_end {
    String ioos_category "Time";
    String long_name "End Date";
    String standard_name "time2";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  ICES_shipcode {
    String long_name "ICES Shipcode";
  }
  details_link {
    String long_name "Details Link";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String eurofleets_cruise_programs "https://evior.eurofleets.eu/v_eurofleets_v1/browse_step.asp?step=00120210101|20221231";
    String history 
"2025-11-05T19:18:26Z (local files)
2025-11-05T19:18:26Z http://erddap.emodnet-physics.eu/erddap/tabledap/EUROFLEETS_CRUISE_METADATA.html";
    String infoUrl "https://www.eurofleets.eu/";
    String institution "EuroFleets";
    String keywords "cruise, cruise_ID, ICES_shipcode, research_vessel, vessel";
    String license "CC-BY 4.0";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "research_vessel, cruise_ID";
    String summary "Collection of metadata of EuroFleets cruises. This dataset contains eurofleets camapaign metadata and vessels information";
    String title "EuroFleets cruises metadata";
  }
}

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its selection constraints (external link)

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.