AdriaClim ERDDAP | ?    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Daily near-surface temperature in Trieste harbour from digital records (1986-
2015)
Subscribe RSS
Institution:  CNR-ISMAR   (Dataset ID: TS_SEA_WATER_TEMPERATURE_86_15_DIG)
Range: time = 1986-01-01T00:00:00Z to 2015-12-31T00:00:00Z
Information:  Summary ? | License ? | 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: 
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 5.049216e+8, 1.45152e+9;
    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";
  }
  a_2_m_SEA_TEMPERATURE {
    Float32 actual_range 4.0, 29.5;
    String ioos_category "water_temperature";
    String long_name "2-m SEA TEMPERATURE (deg C)";
    String units "degree_C";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.2";
    String creator_name "CNR-ISMAR";
    String creator_type "institution";
    String history 
"2024-09-18T10:32:48Z (local files)
2024-09-18T10:32:48Z https://erddap-adriaclim.cmcc-opa.eu/tabledap/TS_SEA_WATER_TEMPERATURE_86_15_DIG.das";
    String infoUrl "???";
    String institution "CNR-ISMAR";
    String keywords "1986-2015, 2-m, a_2_m_SEA_TEMPERATURE, cnr, cnr-ismar, council, daily, data, date, DATE_2_m_SEA_TEMPERATURE, day, digital, harbour, identifier, ismar, national, near, near-surface, records, research, sea, surface, temperature, trieste";
    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.";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "The data set includes daily near-surface sea temperatures measured in the harbour of Trieste (Italy) during 1899-2015. Two time series are formed: the first is derived from analogue measurements performed in the 1899-2008 period, the second is derived from digital records in 1986-2015. From these time series a composite time series for 1899-2015 is built. Data records consist of date and daily temperature in degrees Celsius to the 0.1 °C precision.";
    String time_coverage_end "2015-12-31T00:00:00Z";
    String time_coverage_start "1986-01-01T00:00:00Z";
    String title "Daily near-surface temperature in Trieste harbour from digital records (1986-2015)";
  }
}

 

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