SO-CHIC ERDDAP
Easier access to scientific data
   
Brought to you by SO-CHIC    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  SOCHIC-SOSCEx_STORM2_Glider_Data/day_length Subscribe RSS
Institution:  University of Gothenburg   (Dataset ID: SOCHIC_SOSCEx_STORM2_Glider_Data_day_length)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 time (Date, UTC) ?          2018-12-19T00:00:01Z    2019-02-08T00:25:01Z
  < slider >
 daylength ?          15.1    17.15
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.545177601e+9, 1.549585501e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date";
    String source_name "date";
    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";
  }
  daylength {
    Float64 actual_range 15.1, 17.15;
    String long_name "Daylength";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String EDMO_code "3984";
    String history 
"2024-12-22T22:03:59Z (local files)
2024-12-22T22:03:59Z https://erddap.sochic-h2020.eu/erddap/tabledap/SOCHIC_SOSCEx_STORM2_Glider_Data_day_length.html";
    String infoUrl "https://doi.org/10.1029/2021JC017760";
    String institution "University of Gothenburg";
    String keywords "data, date, daylength, local, source, time";
    String license "CC BY-NC 4.0 https://creativecommons.org/licenses/by-nc/4.0/";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "SOCHIC-SOSCEx_STORM2_Glider_Data/day_length";
    String time_coverage_end "2019-02-08T00:25:01Z";
    String time_coverage_start "2018-12-19T00:00:01Z";
    String title "SOCHIC-SOSCEx_STORM2_Glider_Data/day_length";
  }
}

 

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