Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  Ca rbonTracker CT2009, Carbontracker CT2009 Fluxes (ct flux) [date][calendar_
components], 2000-2001
Subscribe RSS
Institution:  NOAA ESRL   (Dataset ID: noaa_pmel_5774_f0a5_faf3)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    << - +
< slider >
calendar_components ?     specify just 1 value →
    << -
< <
Graph Settings
Marker Type:   Size: 
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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.466902e+8, 1.001889e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date";
    String source_name "date";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  calendar_components {
    Int32 actual_range 1, 6;
    String ioos_category "Time";
    String long_name "Calendar Components";
  date_components {
    String comment "Calendar date components as integers.  Times and dates are UTC.";
    String ioos_category "Time";
    String long_name "integer components of UTC date";
    Int32 missing_value -9;
    String order "year, month, day, hour, minute, second";
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "";
    String creator_name "NOAA/ESRL";
    String creator_type "institution";
    String creator_url "";
    String disclaimer 
"CarbonTracker is an open product of the NOAA Earth System Research 
Laboratory using data from the Global Monitoring Division greenhouse 
gas observational network and collaborating institutions.  Model results 
including figures and tabular material found on the CarbonTracker 
website may be used for non-commercial purposes without restriction,
but we request that the following acknowledgement text be included 
in documents or publications made using CarbonTracker results: 

     CarbonTracker results provided by NOAA/ESRL,
     Boulder, Colorado, USA,

Since we expect to continuously update the CarbonTracker product, it
is important to identify which version you are using.  To provide
accurate citation, please include the version of the CarbonTracker
release in any use of these results.

The CarbonTracker team welcomes special requests for data products not
offered by default on this website, and encourages proposals for
collaborative activities.  Contact us at";
    String email "";
    String history 
"Created on Mon Nov 02 2009 22:37:07 GMT
by script 'Time-stamp: < - 31 Oct 2008 (Fri) 09:30:03 MDT>'
    String id "ct_flux";
    String infoUrl "";
    String institution "NOAA ESRL";
    String keywords "calendar_components, carbontracker, components, ct2009, data, date, date_components, earth, esrl, flux, fluxes, integer, laboratory, noaa, rbontracker, research, system, time";
    String license "We request that the following acknowledgement text be included in documents or publications made using CarbonTracker results: CarbonTracker results provided by NOAA/ESRL, Boulder, Colorado, USA,";
    String Notes "This file contains CarbonTracker surface CO2 fluxes.";
    String source "CarbonTracker release CT2009";
    String sourceUrl "";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Ca rbonTracker CT2009, Carbontracker CT2009 Fluxes";
    String time_coverage_end "2001-09-30T22:30:00Z";
    String time_coverage_start "2000-01-01T01:30:00Z";
    String title "Ca rbonTracker CT2009, Carbontracker CT2009 Fluxes (ct flux) [date][calendar_components], 2000-2001";
    String url "";


Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its projection 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.

griddap request URLs must be in the form{?query}
For example,[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.

ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact