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:  EXAODEP-2020 surface UV irradiance at Hornsund Svalbard station Subscribe RSS
Institution:  Institute of Polar Sciences, National Research Council (CNR-ISP)   (Dataset ID: uv-hornsund)
Range: longitude = 15.55 to 15.55°E, latitude = 77.0 to 77.0°N, time = 2018-03-01T12:00:00Z to 2020-07-31T12:00:00Z
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 cf_role "timeseries_id";
    String long_name "Id of the station in the TimeSeries";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 77.0, 77.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 15.55, 15.55;
    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";
    Float64 actual_range 1.5199056e+9, 1.5961968e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date and time of the measurement";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  UVS_AE_T_UVE {
    Float32 actual_range 35.8, 2523.72;
    String long_name "UVS-AE-T Hornsund Daily Erythemal Dose (Jm-2)";
    String units "Jm-2";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "b.petkov@isac.cnr.it";
    String creator_name "Boyan Petkov";
    String creator_type "person";
    String creator_url "https://www.isp.cnr.it/index.php/it/";
    Float64 Easternmost_Easting 15.55;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 77.0;
    Float64 geospatial_lat_min 77.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 15.55;
    Float64 geospatial_lon_min 15.55;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-28T19:51:34Z (local files)
2024-03-28T19:51:34Z https://data.iadc.cnr.it/tabledap/uv-hornsund.das";
    String infoUrl "https://metadata.iadc.cnr.it/geonetwork/srv/api/records/77556de7-c3ec-48f7-883e-6d9e6ad3c03c";
    String institution "Institute of Polar Sciences, National Research Council (CNR-ISP)";
    String keywords "2020, cnr, cnr-isp, council, data, exaodep, exaodep-2020, institute, isp, national, polar, research, sciences";
    String keywords_vocabulary "GCMD Science Keywords";
    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.";
    Float64 Northernmost_Northing 77.0;
    String project "EXAODEP-2020";
    String project_URL "https://iadc.cnr.it";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 77.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "The data were provided by WG6 of the Atmospheric Flagship Programme (https://nyalesundresearch.no/research-and-monitoring/atmosphere/). Dataset contains measurements of surface UV irradiance performed at Hornsund Svalbard station within the period from 2018 to 2020. The data were collected to describe the Arctic ozone depletion occurred in 2020 and its effect on the UV irradiance reaching the ground.";
    String time_coverage_end "2020-07-31T12:00:00Z";
    String time_coverage_start "2018-03-01T12:00:00Z";
    String title "EXAODEP-2020 surface UV irradiance at Hornsund Svalbard station";
    Float64 Westernmost_Easting 15.55;
  }
}

 

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