|
CalCOFI ERDDAP
Easier access to scientific data |
|
Brought to you by CalCOFI |
| Dataset Title: | CalCOFI CTD Cast Files — full resolution (pre-thinning)
|
| Institution: | CalCOFI (Dataset ID: calcofi_ctd-cast_full) |
| Information: | Summary
| License
| FGDC
| ISO 19115
| Metadata
| Background
| Subset
| Data Access Form
|
Click on the map to specify a new center point.
Zoom:
|
Attributes {
s {
sample_key {
String ioos_category "Identifier";
String long_name "Sample key";
}
cruise_key {
String ioos_category "Identifier";
String long_name "Cruise key";
}
grid_key {
String ioos_category "Identifier";
String long_name "Grid key";
}
time {
String _CoordinateAxisType "Time";
String axis "T";
String ioos_category "Time";
String long_name "Time";
String standard_name "time";
String time_origin "01-JAN-1970 00:00:00";
String units "seconds since 1970-01-01T00:00:00Z";
}
latitude {
String _CoordinateAxisType "Lat";
String axis "Y";
String ioos_category "Location";
String long_name "Latitude";
String standard_name "latitude";
String units "degrees_north";
}
longitude {
String _CoordinateAxisType "Lon";
String axis "X";
String ioos_category "Location";
String long_name "Longitude";
String standard_name "longitude";
String units "degrees_east";
}
depth {
String _CoordinateAxisType "Height";
String _CoordinateZisPositive "down";
String axis "Z";
String ioos_category "Location";
String long_name "Depth";
String positive "down";
String standard_name "depth";
String units "m";
}
measurement_type {
String ioos_category "Other";
String long_name "Measurement type";
}
measurement_value {
String ioos_category "Other";
String long_name "Measurement value";
}
measurement_qual {
String ioos_category "Other";
String long_name "Measurement qual";
}
}
NC_GLOBAL {
String cdm_data_type "Point";
String Conventions "COARDS, CF-1.10, ACDD-1.3";
String creator_name "CalCOFI";
String creator_url "https://calcofi.org";
String dataset_key "calcofi_ctd-cast";
String db_release "v2026.08.08";
String featureType "Point";
String geospatial_lat_units "degrees_north";
String geospatial_lon_units "degrees_east";
String geospatial_vertical_positive "down";
String geospatial_vertical_units "m";
String history
"2026-08-11T05:51:11Z (source database)
2026-08-11T05:51:11Z http://localhost:8090/tabledap/calcofi_ctd-cast_full.das";
String infoUrl "https://calcofi.org/data/oceanographic-data/ctd-cast-files/";
String institution "CalCOFI";
String license "CC-BY 4.0";
String references "https://calcofi.io/workflows/publish_to-erddap.html";
String sourceUrl "(source database)";
String standard_name_vocabulary "CF Standard Name Table v79";
String subsetVariables "cruise_key, measurement_type";
String summary "CTD downcast profiles with temperature, salinity, oxygen, fluorescence, and other sensors at standard depths. 1 m-binned final data for 1993-2002 come from the SIO-CalCOFI Technical Group's own archive (J. Wilkinson), which covers the decade calcofi.org does not publish finals for; 1998 and 2003 onward come from calcofi.org. Where both publish the same cruise, calcofi.org is used; the two agree on 130 of 140 comparable files, and the four cruises that differ are recorded in question calcofi_ctd-cast_20. The full series before adaptive thinning. Much larger than the headline table and provided for scan-level work; most analyses want the thinned table. Source: CalCOFI integrated database release v2026.08.08. Citation: CalCOFI. (2023). CalCOFI CTD Cast Files. CalCOFI.org..";
String title "CalCOFI CTD Cast Files — full resolution (pre-thinning)";
}
}
Data Access Protocol (DAP)
and its
selection constraints
.
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.
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.