EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data 		log in|?   
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  EMODnet Physics - Collection of air temperature in dry bulb (DRYT)
TimeSeries - MultiPointTimeSeriesObservation Subscribe RSS
Institution:  EMODnet Physics   (Dataset ID: TS_DRYT)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Make a graph
 
Variable ?   Optional
Constraint #1 ? 		Optional
Constraint #2 ? 		   Minimum ?
   or a List of Values ? 		   Maximum ?
 
 PLATFORMCODE (EMODnet Platform Code) ?      
   - +  ?
 SOURCE ?      
   - +  ?
 SENSOR (Platform Sensor) ?              
 time (Valid Time GMT, UTC) ?          1970-01-01T00:00:00Z    2025-04-30T00:04:20Z
  < slider >
 TIME_QC (TIME quality flag, 1) ?          0    1
 depth (m) ?          -12000.0    12000.0
  < slider >
 DEPTH_QC (DEPTH quality flag, 1) ?          -32768    32763
 latitude (degrees_north) ?          -999.0    112.4254
  < slider >
 longitude (degrees_east) ?          -999.0    289.19812
  < slider >
 POSITION_QC (POSITION quality flag, 1) ?          -127    7
 DRYT (degree_Celsius) ?          -2.147483647E9    4.29496736E8
 DRYT_QC (DRYT quality flag, 1) ?          -127    9
 DRYT_DM ?              R
 url_metadata (Metadata Link) ?              
 qc_entity ?          0    25
 
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 {
  PLATFORMCODE {
    String cf_role "timeseries_id";
    String long_name "EMODnet Platform Code";
  }
  SOURCE {
    String long_name "source";
  }
  SENSOR {
    String long_name "Platform Sensor";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 0.0, 1.74597146e+9;
    String axis "T";
    String calendar "Gregorian";
    String ioos_category "Time";
    String long_name "Valid Time GMT";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  TIME_QC {
    Int16 _FillValue -32767;
    Int16 actual_range 0, 1;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "TIME quality flag";
    String standard_name "time_qc";
    String units "1";
    Int16 valid_range 0, 9;
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue 9.969209968386869e+36;
    Float64 actual_range -12000.0, 12000.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  DEPTH_QC {
    Int16 _FillValue -32767;
    Int16 actual_range -32768, 32763;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "DEPTH quality flag";
    String standard_name "depth";
    String units "1";
    Int16 valid_range 0, 9;
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue 9.969209968386869e+36;
    Float64 actual_range -999.0, 112.4254;
    String axis "Y";
    String ioos_category "Location";
    String latitude_reference_datum "geographical coordinates, WGS84 projection";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue 9.969209968386869e+36;
    Float64 actual_range -999.0, 289.19812;
    String axis "X";
    String ioos_category "Location";
    String latitude_reference_datum "geographical coordinates, WGS84 projection";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  POSITION_QC {
    Int16 _FillValue -32767;
    Int16 actual_range -127, 7;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "POSITION quality flag";
    String standard_name "position_qc";
    String units "1";
    Int16 valid_range 0, 9;
  }
  DRYT {
    Float64 _FillValue 9.969209968386869e+36;
    Float64 actual_range -2.147483647e+9, 4.29496736e+8;
    String ep_parameter_group "Meteorological";
    String long_name "air temperature in dry bulb";
    String p01 "SDN:P01::CTMPZZ01";
    String p33 "METEOROLOGICAL";
    String sample_rate_comment "Hourly: 3600, Daily: 8.64e4, Monthly: 2.628e6, Yearly: 3.154e7";
    String sample_rate_units "seconds";
    String source_variable_name "DRYT";
    String standard_name "air_temperature";
    String units "degree_Celsius";
  }
  DRYT_QC {
    Int16 _FillValue -32767;
    Int16 actual_range -127, 9;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "DRYT quality flag";
    String standard_name "dryt_qc";
    String units "1";
    Int16 valid_range 0, 9;
  }
  DRYT_DM {
    String actual_range 
"\u0000
R";
    String flag_meanings "real-time provisional delayed-mode mixed";
    String flag_values "R, P, D, M";
    String long_name "DRYT method of data processing";
  }
  url_metadata {
    String long_name "Metadata Link";
  }
  qc_entity {
    Int32 actual_range 0, 25;
    String qc_reference_table "\"https://er2webapps.emodnet-physics.eu/erddap/tabledap/qc_reference_table.htmlTable";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "PLATFORMCODE,SOURCE,latitude,longitude";
    String citation "Data are the property of the producer/owner distributed through EMODnet Physics. EMODnet Physics and the partners are not responsible for improper use";
    String contact "contacts@emodnet-physics.eu";
    String Conventions "CF-1.6 OceanSITES-Manual-1.2 Copernicus-InSituTAC-SRD-1.3 Copernicus-InSituTAC-ParametersList-3.0.0, COARDS, ACDD-1.3";
    String creator_type "institution";
    Float64 Easternmost_Easting 289.19812;
    String ep_parameter_group "Atmospheric";
    String featureType "TimeSeries";
    String geometryType "Point";
    Float64 geospatial_lat_max 112.4254;
    Float64 geospatial_lat_min -999.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 289.19812;
    Float64 geospatial_lon_min -999.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 12000.0;
    Float64 geospatial_vertical_min -12000.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-04-30T15:10:48Z (local files)
2025-04-30T15:10:48Z http://ercompwebapps.emodnet-physics.eu/erddap/tabledap/TS_DRYT.html";
    String info "https://www.bas.ac.uk/";
    String infoUrl "http://www.emodnet-physics.eu";
    String institution "EMODnet Physics";
    String institution_normalizzato "1";
    String institution_oldName "Australian Antarctic Data Centre";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    String metadata_dataset "https://er2webapps.emodnet-physics.eu/erddap/tabledap/TS_DRYT_METADATA.html";
    String metadata_document "https://metadata.emodnet-physics.eu/datasetfile/emodnet/TS_DRYT";
    Float64 Northernmost_Northing 112.4254;
    String platformType_dataFeatureType "timeseries";
    String platformType_description "Weather Station";
    String platformType_trajectory "False";
    String publisher_type "institution";
    String qc_reference_table "https://er2webapps.emodnet-physics.eu/erddap/tabledap/qc_reference_table.html";
    String SDN "SDN:P01::CTMPZZ01";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -999.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String stato "A";
    String subsetVariables "PLATFORMCODE,SOURCE";
    String summary "EMODnet Physics - Collection of air temperature in dry bulb (DRYT) TimeSeries - MultiPointTimeSeriesObservation";
    String testOutOfDate "now-7days";
    String time_coverage_end "2025-04-30T00:04:20Z";
    String time_coverage_start "1970-01-01T00:00:00Z";
    String title "EMODnet Physics - Collection of air temperature in dry bulb (DRYT) TimeSeries - MultiPointTimeSeriesObservation";
    Float64 Westernmost_Easting -999.0;
  }
}

 

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