IADC Italian Arctic Data Center ERDDAP
Easier access to scientific data
log in    
Brought to you by CNR-ISP IADC Portal    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  EGUsphere-2023-1376 Meteo Data Subscribe RSS
Institution:  CNR-ISP   (Dataset ID: gilardoni_acp_met_2023)
Range: longitude = 11.86587 to 11.86587°E, latitude = 78.92136 to 78.92136°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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 {
  station_id {
    String actual_range 
"CCT
CCT";
    String cf_role "timeseries_id";
    String long_name "Id of the station in the TimeSeries";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 78.92136, 78.92136;
    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 11.86587, 11.86587;
    String axis "X";
    String ioos_category "Location";
    String long_name "longitude position of the station";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    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 units "seconds since 1970-01-01T00:00:00Z";
  }
  Temperature {
    Float32 _FillValue NaN;
    Float32 actual_range 244.46, 284.21;
    String long_name "Temperature";
  }
  Relative_humidity {
    Float32 _FillValue NaN;
    Float32 actual_range 32.85, 95.99;
    String long_name "Relative Humidity";
    String standard_name "relative_humidity";
  }
  Pressure {
    Int16 actual_range 962, 1029;
    String long_name "Pressure";
  }
  Radiation {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 408.65;
    String long_name "Radiation";
  }
  Wind_speed {
    Float32 actual_range 0.41, 15.77;
    String long_name "Wind Speed";
    String standard_name "wind_speed";
  }
  Wind_direction {
    Int32 actual_range 86, 340;
    String long_name "Wind From Direction";
    String standard_name "wind_from_direction";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String Conventions "ACDD-1.3, COARDS, CF-1.6";
    String creator_email "stefania.gilardoni@cnr.it";
    String creator_name "Stefania Gilardoni";
    String creator_type "person";
    Float64 Easternmost_Easting 11.86587;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 78.92136;
    Float64 geospatial_lat_min 78.92136;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 11.86587;
    Float64 geospatial_lon_min 11.86587;
    String geospatial_lon_units "degrees_east";
    String history 
"TO-DO
2024-04-29T09:24:10Z (local files)
2024-04-29T09:24:10Z https://data.iadc.cnr.it/tabledap/gilardoni_acp_met_2023.das";
    String infoUrl "TO-DO";
    String institution "CNR-ISP";
    String keywords "air temperature, meteo, pressure, relative humidity, shortwave radiation, wind";
    String license "CC BY-NC: This license allows reusers to distribute, remix, adapt, and build upon the material in any medium or format for noncommercial purposes only, and only so long as attribution is given to the creator.";
    String license_url "https://spdx.org/licenses/CC-BY-4.0.html";
    Float64 Northernmost_Northing 78.92136;
    String project_URL "https://iadc.cnr.it";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 78.92136;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Daily averages of temperature, relative humidity, surface pressure, shortwave downwelling radiation, wind speed and wind direction measured at the Climate change tower. Averages are calculated from 1-minute time resolution data.";
    String title "EGUsphere-2023-1376 Meteo Data";
    Float64 Westernmost_Easting 11.86587;
  }
}

 

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