AdriaClim ERDDAP | ?    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  AdriaClim RESM - WRFHydro - projection - runoff v1 Subscribe RSS
Institution:  CMCC   (Dataset ID: adriaclim_resm_wrfhydro_proj_runoff_v1)
Range: longitude = 11.60275 to 20.22737°E, latitude = 39.19572 to 45.80203°N, time = 2022-01-01T00:00:00Z to 2050-12-31T12: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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6409952e+9, 2.5561008e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Column#1";
    String source_name "Column#1";
    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";
  }
  station_id {
    UInt16 actual_range 0, 144;
    String ioos_category "Unknown";
    String long_name "Column#2";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 11.60275, 20.22737;
    String axis "X";
    String ioos_category "Location";
    String long_name "Column#3";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 39.19572, 45.80203;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Column#4";
    String standard_name "latitude";
    String units "degrees_north";
  }
  streamflow_m {
    Float32 actual_range 0.0, 16720.69;
    String ioos_category "Unknown";
    String long_name "Column#5";
  }
  streamflow_feet {
    Float32 actual_range 0.005, 590491.0;
    String ioos_category "Unknown";
    String long_name "Column#6";
  }
  water_level {
    Float32 actual_range 0.001, 9.513;
    String ioos_category "Unknown";
    String long_name "Column#7";
  }
 }
  NC_GLOBAL {
    String adriaclim_dataset "model";
    String adriaclim_model "WRFHydro";
    String adriaclim_scale "adriatic";
    String adriaclim_timeperiod "hourly";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.2";
    String creator_name "CMCC";
    String creator_type "institution";
    String creator_url "https://www.ec.gc.ca/scitech/default.asp?lang=En&n=61B33C26-1#cmc";
    Float64 Easternmost_Easting 20.22737;
    Float64 geospatial_lat_max 45.80203;
    Float64 geospatial_lat_min 39.19572;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 20.22737;
    Float64 geospatial_lon_min 11.60275;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-18T10:35:44Z (local files)
2024-09-18T10:35:44Z https://erddap-adriaclim.cmcc-opa.eu/tabledap/adriaclim_resm_wrfhydro_proj_runoff_v1.das";
    String infoUrl "https://www.cmcc.it";
    String institution "CMCC";
    String keywords "adriaclim, cmcc, column, Column_0, Column_2, Column_3, Column_4, Column_5, Column_6, Column_7, data, projection, resm, runoff, time, wrfhydro";
    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 45.80203;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.19572;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "station_id, longitude, latitude";
    String summary "AdriaClim RESM - WRFHydro - projection - runoff v1";
    String time_coverage_end "2050-12-31T12:00:00Z";
    String time_coverage_start "2022-01-01T00:00:00Z";
    String title "AdriaClim RESM - WRFHydro - projection - runoff v1";
    Float64 Westernmost_Easting 11.60275;
  }
}

 

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