ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	Network for the Collection of Knowledge on meLt of Antarctic iCe shElves (NECKLACE)
Institution:	SOOS (Dataset ID: NECKLACE)
Range:	longitude = -126.3 to 171.68°E, latitude = -82.8574 to -67.2342°N
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Draw land mask:

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

)

Click on the map to specify a new center point.

Zoom:

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Site_name {
    String long_name "Site Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -82.8574, -67.2342;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "Deployment Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -126.3, 171.68;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "Deployment Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Retrieval_Latitude {
    Float32 _FillValue NaN;
    Float32 actual_range -70.0564, -70.0379;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String long_name "R_Latitude";
    String units "degrees_north";
  }
  Retrieval_Longitude {
    Float32 _FillValue NaN;
    Float32 actual_range 38.6454, 38.6709;
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String long_name "R_Longitude";
    String units "degrees_east";
  }
  Program {
    String long_name "Program";
  }
  Nation {
    String long_name "Nation";
  }
  Status {
    String long_name "Status";
  }
  Deployment_Date {
    String long_name "Deployment Date";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Retrieval Date";
    String source_name "Retrieval 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";
  }
  Email_Address {
    String long_name "Email Address";
  }
  Link_to_raw_data {
    String long_name "Link To Raw Data";
  }
  Link_to_processed_data {
    String long_name "Link To Processed Data";
  }
  Sensor_Serial_Number {
    String long_name "Sensor Serial Number";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.2";
    String creator_name "SOOS";
    String creator_type "institution";
    String creator_url "https://soos.aq/endorsed-projects/necklace";
    Float64 Easternmost_Easting 171.68;
    Float64 geospatial_lat_max -67.2342;
    Float64 geospatial_lat_min -82.8574;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 171.68;
    Float64 geospatial_lon_min -126.3;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-06T09:25:09Z (local files)
2024-11-06T09:25:09Z https://er1.s4oceanice.eu/tabledap/NECKLACE.das";
    String infoUrl "https://soos.aq/endorsed-projects/necklace";
    String institution "SOOS";
    String keywords "necklace, soos";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    Float64 Northernmost_Northing -67.2342;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -82.8574;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "This layer provides time series of basal melt rates from Antarctic ice shelves from the Network for the Collection of Knowledge on meLt of Antarctic iCe shElves (NECKLACE) programme.";
    String title "Network for the Collection of Knowledge on meLt of Antarctic iCe shElves (NECKLACE)";
    Float64 Westernmost_Easting -126.3;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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