OCG ERDDAP
Easier Access To GOOS Data
| ?    
Brought to you by GOOS OCG    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  JCOMMPS Active WMO ID LIST Subscribe RSS
Institution:  OSMC JCOMMOPS   (Dataset ID: wmo_list)
Range: time = 1900-01-01 to 2025-12-31
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Data Access Form
 
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 {
  WMO {
    String long_name "WMO";
  }
  TELECOM_ID {
    String long_name "TELECOM ID";
  }
  TELECOM_SYSTEM {
    String long_name "TELECOM SYSTEM";
  }
  PTFM_NAME {
    String long_name "PTFM NAME";
  }
  PTFM_FAMILY {
    String long_name "PTFM FAMILY";
  }
  PTFM_TYPE {
    String long_name "PTFM TYPE";
  }
  CONTACT_NAME {
    String long_name "CONTACT NAME";
  }
  EMAIL {
    String long_name "EMAIL";
  }
  PROGRAM {
    String long_name "PROGRAM";
  }
  ROLE {
    String long_name "ROLE";
  }
  AGENCY {
    String long_name "AGENCY";
  }
  COUNTRY {
    String long_name "COUNTRY";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -2.2089888e+9, 1.7671392e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "ALLOC DATE";
    String source_name "ALLOC_DATE";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  DEALLOC_DATE {
    Float64 actual_range -6.14920032e+10, 1.707264e+9;
    String ioos_category "Time";
    String long_name "DEALLOC DATE";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  ARGOS_PROG {
    String long_name "ARGOS PROG";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String history 
"2024-04-19T16:39:38Z (local files)
2024-04-19T16:39:38Z https://osmc.noaa.gov/tabledap/wmo_list.das";
    String infoUrl "???";
    String institution "OSMC JCOMMOPS";
    String keywords "agency, alloc, argos, ARGOS_PROG, contact, CONTACT_NAME, country, data, date, dealloc, DEALLOC_DATE, email, family, local, meteorological, name, organisation, prog, program, ptfm, PTFM_FAMILY, PTFM_NAME, PTFM_TYPE, role, source, system, telecom, TELECOM_ID, TELECOM_SYSTEM, time, type, wmo, world";
    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 v55";
    String subsetVariables "ARGOS_PROG,TELECOM_SYSTEM,PTFM_NAME,PTFM_FAMILY,PTFM_TYPE,PROGRAM,ROLE,AGENCY,COUNTRY";
    String summary "JCOMMPS Active WMO ID LIST";
    String time_coverage_end "2025-12-31";
    String time_coverage_start "1900-01-01";
    String title "JCOMMPS Active WMO ID LIST";
  }
}

 

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