EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in|?   
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  GRDC MEAN MONTHLY DISCHARGE (MQ) Subscribe RSS
Institution:  GRDC   (Dataset ID: GRDC_MEAN_MONTHLY_DISCHARGE)
Range: time = 1806-01-01 to 2019-04-01
Information:  Summary ? | License ? | 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: 
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 ? )
   
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 {
  GRDCno {
    String long_name "GRDC number";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -5.17536e+9, 1.5540768e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "YYYY-MM-DD";
    String source_name "YYYY-MM-DD";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Original {
    Float32 _FillValue -999.0;
    Float32 actual_range 0.0, 39400.0;
    String long_name "original (provided) data";
  }
  Calculated {
    Float32 _FillValue -999.0;
    Float32 actual_range 0.0, 30163.33;
    String long_name "GRDC calculated from daily data";
  }
  Flag {
    String _Unsigned "false";
    Byte actual_range 0, 100;
    String long_name "percentage of valid values used for calculation from daily data";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "GRDC";
    String creator_type "institution";
    String creator_url "https://www.bafg.de/GRDC/EN/01_GRDC/grdc_node.html";
    String history 
"2024-10-07T21:53:22Z (local files)
2024-10-07T21:53:22Z https://erddap.emodnet-physics.eu/tabledap/GRDC_MEAN_MONTHLY_DISCHARGE.das";
    String infoUrl "https://www.bafg.de/GRDC/EN/01_GRDC/grdc_node.html";
    String institution "GRDC";
    String keywords "calculated, data, discharge, flag, grdc, grdcno, hh_mm, identifier, mean, month, monthly, original, time, yyyy, yyyy-mm-dd";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "GRDCno";
    String summary "GRDC Mean Monthly Discharge (mq). GRDC data from a local source.";
    String time_coverage_end "2019-04-01";
    String time_coverage_start "1806-01-01";
    String title "GRDC MEAN MONTHLY DISCHARGE (MQ)";
  }
}

 

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