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:  USAP-DC Datasets repository Subscribe RSS
Institution:  U.S. ANTARCTIC PROGRAM DATA CENTER   (Dataset ID: USAP-DC_Datasets_repository_points)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 dataset_uid ?      
   - +  ?
 doi ?          "10.15784/600026"    "doi"
 landing_page ?          "https://www.usap-d..."    "url_link"
 title ?          " Subglacial Precip..."    "title"
 abstract ?          " every hour and ta..."    "summary"
 locations ?          "location"    "location"
 persons ?          "Abrahams, Lauren"    "person"
 awards ?          "0087151 Cole-Dai, ..."    "award"
 latitude (degrees_north) ?          -90.0    81.0
  < slider >
 longitude (degrees_east) ?          -180.0    180.0
  < slider >
 science_programs ?          "ANDRILL"    "program"
 nsf_funding_programs ?          "Antarctic Astrophy..."    "founding_program"
 time (UTC) ?              
 timestamp (UTC) ?          2023-05-18T08:13:31.956Z    2023-05-18T09:21:57.938Z
 author ?          "terra"    "terra"
 command ?          0    0
 
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 {
  dataset_uid {
    String long_name "Dataset Uid";
  }
  doi {
    String long_name "Doi";
  }
  landing_page {
    String long_name "Landing Page";
  }
  title {
    String long_name "Title";
  }
  abstract {
    String long_name "Abstract";
  }
  locations {
    String long_name "Locations";
  }
  persons {
    String long_name "Persons";
  }
  awards {
    String long_name "Awards";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -90.0, 81.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "Latitude [degrees_north]";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -180.0, 180.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "Longitude [degrees_east]";
    String standard_name "longitude";
    String units "degrees_east";
  }
  science_programs {
    String long_name "Science Programs";
  }
  nsf_funding_programs {
    String long_name "Nsf Funding Programs";
  }
  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 time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  timestamp {
    Float64 actual_range 1.684397611956e+9, 1.684401717938e+9;
    String comment "The values in this column are added by ERDDAP to identify when each row of data was added to the data file. NOTE! This is an unusual dataset in that the data files are actually log files. Normally, when you request data from this dataset, ERDDAP processes the insert (command=0) and delete (command=1) commands in the log files to return data from the current version of this dataset. However, if you make a request which includes &timestamp<= , then ERDDAP will return the dataset as it was at that point in time. Or, if you make a request which includes &timestamp> (or >= or =), e.g., &timestamp>0, then ERDDAP will return the raw data from the log files.";
    String ioos_category "Time";
    String long_name "Timestamp";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.000Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  author {
    String comment "The values in this column identify the author who added each row of data to the dataset.";
    String long_name "Author";
  }
  command {
    String _Unsigned "false";
    Byte actual_range 0, 0;
    String comment "This is an unusual dataset in that the data files are actually log files. Normally, when you request data from this dataset, ERDDAP processes the insert (command=0) and delete (command=1) commands in the log files to return data from the current version of this dataset. However, if you make a request which includes &timestamp<= , then ERDDAP will return the dataset as it was at that point in time. Or, if you make a request which includes &timestamp> (or >= or =), e.g., &timestamp>0, then ERDDAP will return the raw data from the log files.";
    String flag_meanings "insert delete";
    Byte flag_values 0, 1;
    String long_name "Command";
    Byte missing_value 127;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 180.0;
    Float64 geospatial_lat_max 81.0;
    Float64 geospatial_lat_min -90.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 180.0;
    Float64 geospatial_lon_min -180.0;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-22T01:28:44Z (local files)
2024-11-22T01:28:44Z http://erddap.emodnet-physics.eu/erddap/tabledap/USAP-DC_Datasets_repository_points.html";
    String httpGetDirectoryStructure "dataset_uid";
    String httpGetRequiredVariables "dataset_uid";
    String infoUrl "https://www.usap-dc.org/";
    String institution "U.S. ANTARCTIC PROGRAM DATA CENTER";
    String keywords "dataset, USAP";
    String license "CC-BY";
    Float64 Northernmost_Northing 81.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -90.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "dataset_uid";
    String summary "The U.S. Antarctic Program Data Center (USAP-DC) supports investigators funded by the National Science Foundation in documenting, preserving, and disseminating their research results. We provide a central USAP Project Catalog for all projects funded by the NSF Antarctic program and a Data Repository for research datasets derived from these projects. Data managed include the NSF research related glaciology data collection formerly managed through NSIDC. We register datasets in the Antarctic Metadata Directory (AMD) to comply with the Antarctic Treaty and represent the U.S. in Scientific Committee on Antarctic Research (SCAR) activities.";
    String testOutOfDate "now-1day";
    String title "USAP-DC Datasets repository";
    Float64 Westernmost_Easting -180.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.24
Disclaimers | Privacy Policy | Contact