NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  OSMC Platform Locations Subscribe RSS
Institution:  Observing System Monitoring Center   (Dataset ID: osmc_rt60_locations)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 latitude (degrees_north) ?          -78.1525    1.7E38
  < slider >
 longitude (degrees_east) ?          -179.9    1.7E38
  < slider >
 platform_type ?          "ARGO"    "WEATHER BUOYS"
 platform_code ?          "0000"    "ZTNDLFM"
 
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 {
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -78.1525, 1.7e+38;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -179.9, 1.7e+38;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  platform_type {
    String ioos_category "Identifier";
    String long_name "Platform Type";
  }
  platform_code {
    String ioos_category "Identifier";
    String long_name "Platform Code";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "NCCSV-1.0, COARDS, CF-1.6, ACDD-1.3";
    String creator_name "Observing System Monitoring Center";
    String creator_type "group";
    String creator_url "https://www.noaa.gov/";
    Float64 Easternmost_Easting 1.7e+38;
    Float64 geospatial_lat_max 1.7e+38;
    Float64 geospatial_lat_min -78.1525;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 1.7e+38;
    Float64 geospatial_lon_min -179.9;
    String geospatial_lon_units "degrees_east";
    String history 
"2023-03-26T06:49:23Z (local files)
2023-03-26T06:49:23Z https://data.pmel.noaa.gov/pmel/erddap/tabledap/osmc_rt60_locations.html";
    String infoUrl "https://www.osmc.noaa.gov/";
    String institution "Observing System Monitoring Center";
    String keywords "center, code, data, identifier, latitude, locations, longitude, monitoring, observing, ocean, osmc, platform, platform_code, platform_type, system, type";
    String license 
"Data Licenses / Data Usage Restrictions
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.

Unless otherwise noted, data served through this ERDDAP server are 
not quality controlled.  Users may need to do quality control when using 
these data. These data are made available at the users own risk.";
    Float64 Northernmost_Northing 1.7e+38;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -78.1525;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "This is the most recent location for each platform that has reported to Observing System Monitoring Center (OSMC) in the past 60 days.";
    String title "OSMC Platform Locations";
    Float64 Westernmost_Easting -179.9;
  }
}

 

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