OCEAN:ICE ERDDAP
Easier access to scientific data 		log in    
Brought to you by OCEAN:ICE    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  DomeC_SP02 Subscribe RSS
Institution:  CNR-ISP   (Dataset ID: DomeC_SP02)
Range: longitude = 123.0 to 123.0°E, latitude = -75.0 to -75.0°N, time = 2006-01-01T12:00:00Z to 2010-01-26T12:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.1361168e+9, 1.2645072e+9;
    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 time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  AOD_500nm {
    Int32 actual_range 0, 0;
    String long_name "AOD(500nm)";
  }
  alpha {
    Int32 actual_range 1, 2;
    String long_name "Alpha";
  }
  station_id {
    String cf_role "timeseries_id";
    String long_name "Id of the station in the TimeSeries";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -75.0, -75.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "latitude position of the station";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 123.0, 123.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "longitude position of the station";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String Conventions "COARDS, CF-1.10, ACDD-1.3, NCCSV-1.2";
    String creator_email "simone.pulimeno@cnr.it";
    String creator_name "Italian National Research Council - Institute of Polar Sciences";
    String creator_url "https://bo.isp.cnr.it/erddap";
    Float64 Easternmost_Easting 123.0;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max -75.0;
    Float64 geospatial_lat_min -75.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 123.0;
    Float64 geospatial_lon_min 123.0;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-06T09:38:09Z (local files)
2024-11-06T09:38:09Z https://er1.s4oceanice.eu/tabledap/DomeC_SP02.das";
    String infoUrl "https://bo.isp.cnr.it/erddap";
    String institution "CNR-ISP";
    String keywords "500nm, aerosol, alpha, aod, AOD_500nm, cnr, council, data, depth, domec, institute, italian, national, optical, polar, research, sciences, sp02, time";
    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.";
    Float64 Northernmost_Northing -75.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -75.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Aerosol Optical Depth (AOD) 500nm &amp; alpha. Italian National Research Council - Institute of Polar Sciences data from a local source.";
    String time_coverage_end "2010-01-26T12:00:00Z";
    String time_coverage_start "2006-01-01T12:00:00Z";
    String title "DomeC_SP02";
    Float64 Westernmost_Easting 123.0;
  }
}

 

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