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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CGBN US Arctic Flux 1994-1998 Subscribe RSS
Institution:  NOAA PMEL   (Dataset ID: CGBN_US)
Range: longitude = 173.3 to 220.0°E, latitude = 69.0 to 83.4°N, time = 1994-07-26T18:00:00Z to 1998-10-15T21:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   
 
(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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
Time range:    |<   -       
[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 {
  ID {
    String actual_range 
"CGBN_US
CGBN_US";
    String cf_role "timeseries_id";
    String long_name "Ship ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 7.752456e+8, 9.084852e+8;
    String axis "T";
    String ioos_category "Time";
    String long_name "TAXIS";
    String source_name "TAXIS";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  TAU {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range 0.0, 0.759;
    String long_name "Tau";
    Float64 missing_value -1.0e+34;
    String units "N/m2";
  }
  QS {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -26.172, 166.285;
    String long_name "Q sensible";
    Float64 missing_value -1.0e+34;
    String units "W/m2";
  }
  QL {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -8.843, 122.018;
    String long_name "Q latent";
    Float64 missing_value -1.0e+34;
    String units "W/m2";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -9999.0;
    Float64 actual_range 173.3000031, 220.0;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String history "From inputcoareSD.asc";
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value -9999.0;
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -9999.0;
    Float64 actual_range 69.0, 83.4000015;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String history "From inputcoareSD.asc";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value -9999.0;
    String standard_name "latitude";
    String units "degrees_north";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "ID";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    Float64 Easternmost_Easting 220.0;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 83.4000015;
    Float64 geospatial_lat_min 69.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 220.0;
    Float64 geospatial_lon_min 173.3000031;
    String geospatial_lon_units "degrees_east";
    String history 
"PyFerret V7.5 (optimized) 14-Oct-20
2024-04-13T15:28:39Z (local files)
2024-04-13T15:28:39Z https://data.pmel.noaa.gov/pmel/tabledap/CGBN_US.das";
    String infoUrl "https://www.pmel.noaa.gov/cwi/arctic-surface-fluxes";
    String institution "NOAA PMEL";
    String keywords "bnds, data, latent, latitude, local, longitude, sensible, source, tau, taxis, TAXIS_bnds, time";
    String license 
"Data Licenses / Data Usage Restrictions
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.

Unless otherwise noted, data served through this ERDDAP server are 
not quality controlled.  Users may need to do quality control when using 
these data. These data are made available at the users own risk.";
    Float64 Northernmost_Northing 83.4000015;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 69.0;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "ID";
    String summary "Arctic Flux calculated for observations collected from CCGS Louis S. St-Laurent (CGBN) between 1994 and 1998 in US Waters";
    String time_coverage_end "1998-10-15T21:00:00Z";
    String time_coverage_start "1994-07-26T18:00:00Z";
    String title "CGBN US Arctic Flux 1994-1998";
    Float64 Westernmost_Easting 173.3000031;
  }
}

 

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 2.18
Disclaimers | Privacy Policy | Contact