NOAA ERDDAP
Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CalCOFI Cruises Subscribe RSS
Institution:  NOAA SWFSC   (Dataset ID: erdCalCOFIcruises)
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    [The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  cruise {
    String description "Six-digit cruise code (YYYYMM)";
    String ioos_category "Identifier";
    String long_name "Cruise Code";
  }
  ship {
    String ioos_category "Identifier";
    String long_name "Ship Name";
  }
  ship_code {
    String description "Two-digit CalCOFI ship code";
    String ioos_category "Identifier";
    String long_name "Ship Code";
  }
  year {
    Int32 actual_range 1951, 2017;
    String description "Year in which cruise began";
    String ioos_category "Identifier";
    String long_name "Year";
  }
  month {
    Int32 actual_range 1, 12;
    String description "Month in which cruise primarily occured";
    String ioos_category "Identifier";
    String long_name "Month";
  }
  cruise_type {
    String description "Primary purpose of cruise. Some cruises are listed twice, e.g., CalCOFI and Trawling";
    String ioos_category "Identifier";
    String long_name "Cruise Type";
  }
 }
  NC_GLOBAL {
    String acknowledgment "National Oceanic and Atmospheric Administration, California Department of Fish and Wildlife, University of California, San Diego Scripps Institution";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.0, Unidata Dataset Discovery v1.0, NCCSV-1.0";
    String date_issued "2016-05-24";
    String date_modified "2016-05-24";
    String history 
"2018-07-18T02:51:31Z (source database)
2018-07-18T02:51:31Z http://coastwatch.pfeg.noaa.gov/tabledap/erdCalCOFIcruises.das";
    String infoUrl "https://oceanview.pfeg.noaa.gov/CalCOFI/calcofi_info.html";
    String institution "NOAA SWFSC";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String project "CalCOFI";
    String publisher_email "ed.weber@noaa.gov";
    String publisher_name "Ed Weber";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF-11";
    String subsetVariables "cruise,ship,ship_code,year,month,cruise_type";
    String summary "Cruises using one or more ships conducted as part of the California Cooperative Oceanic Fisheries Investigations (CalCOFI) program and other related cruises conducted by the NOAA Southwest Fisheries Science Center from 1951 to present. Multi-purpose cruises e.g., CalCOFI and trawling, include a listing for each cruise type.";
    String title "CalCOFI Cruises";
  }
}

 

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.

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.


 
ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact