Make A Graph

Dataset Title:	SB Kringla Datalogger
Institution:	SO-CHIC (Dataset ID: SOCHIC_2022_SB)
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

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:

Dimensions

Start

Stop

cells

specify just 1 value →

time (UTC)

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:

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 {
  cells {
    Float64 actual_range 0, 39;
    String long_name "Cells";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.641812951e+9, 1.6580718e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Time in seconds, UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  vel_east {
    Float64 _FillValue NaN;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String description "East speed corrected for magnetic declination and GPS movement";
    String long_name "East speed corrected";
    String standard_name "eastward_sea_water_velocity";
    String units "m s$^{-1}$";
  }
  vel_north {
    Float64 _FillValue NaN;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String description "North speed corrected for magnetic declination and GPS movement";
    String long_name "North speed corrected";
    String standard_name "northward_sea_water_velocity";
    String units "m s$^{-1}$";
  }
  strength {
    Float64 _FillValue NaN;
    String description "Averaged signal from the four beams. The signal strength is calculated for each beam for each ping and averaged at the end of the interval.";
    String long_name "Strength";
    String standard_name "strength";
    String units "dB";
  }
  NC_GLOBAL {
    String area "Southern Ocean";
    String cdm_data_type "Grid";
    String contact "sebastiaan.swart@marine.gu.se";
    String contributor_email "sebastiaan.swart@gu.se; isgiddy@gmail.com; johan.edholm@gu.se";
    String contributor_name "Giddy, Isabelle; Edholm, Johan M.; Spira, Theo; Swart, Sebastiaan; Biddle, Louise; du Plessis, Marcel";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String conventions "CF-1.6, ACDD-1.3";
    String creator_email "johan.edholm@gu.se";
    String creator_name "Johan Edholm";
    String creator_url "https://polargliders.com";
    String DOI "https://doi.org/10.5281/zenodo.7494998";
    String history 
"2024-10-18T07:24:03Z (local files)
2024-10-18T07:24:03Z https://erddap.sochic-h2020.eu/griddap/SOCHIC_2022_SB.das";
    String id "SB Kringla Datalogger SO-CHIC";
    String infoUrl "https://zenodo.org/records/11059426";
    String institution "SO-CHIC";
    String instrument "sbe41 aa4831 wlbb2fl magnetometer";
    String instrument_id "1812";
    String instrument_name "Kringla";
    String keywords "cells, circulation, corrected, currents, data, datalogger, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, east, eastward, eastward_sea_water_velocity, gothenburg, kringla, north, northward, northward_sea_water_velocity, ocean, oceans, science, sea, seawater, speed, strength, time, university, vel_east, vel_north, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY";
    String owner "Sebastiaan Swart";
    String pi_name "Sebastiaan Swart";
    String platform "Uncrewed surface vehicle";
    String processing_date "2023-01-02";
    String processing_level "2";
    String project "SO-CHIC";
    String project_infoUrl "www.sochic-h2020.eu";
    String quality_control_version "1.12";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "WING_ROLL_FILTERED_PEAK, WIND_FROM_STDDEV, WIND_SPEED_STDDEV, TEMP_IR_SEA_WING_UNCOMP_MEAN, TEMP_IR_SEA_WING_UNCOMP_STDDEV, ASVCO2_GENERAL_ERROR_FLAGS, ASVCO2_ZERO_ERROR_FLAGS, ASVCO2_SPAN_ERROR_FLAGS, ASVCO2_SECONDARYSPAN_ERROR_FLAGS, ASVCO2_EQUILIBRATEANDAIR_ERROR_FLAGS, ASVCO2_RTC_ERROR_FLAGS, ASVCO2_FLOWCONTROLLER_FLAGS, ASVCO2_LICOR_FLAGS, trajectory";
    String summary "This dataset contains atmospheric and oceanic observations of wind speed, air and sea temperature, salinity, and currents. The Sailbuoy was deployed at the Maud Rise seamount in the eastern part of the Weddell Sea from the 10th of January 2022, and recovered on the 17th of June 2022. There was a brief period in March where she was recovered and repaired by Polarstern and subsequently re-deployed, losing around three days of data. The ADCP data were processed using Edholm, J. M. (2022). Sailbuoy processing (v1.0.0)";
    String time_coverage_end "2022-07-17T15:30:00Z";
    String time_coverage_start "2022-01-10T11:09:11Z";
    String time_coverate_end "2022-07-17T15:30:00.000000000";
    String time_coverate_start "2022-01-10T11:09:11.000000000";
    String title "SB Kringla Datalogger";
  }
}

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its projection 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. It makes 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.

ERDDAP, Version 2.24
Disclaimers | Privacy Policy | Contact