ERDDAP > tabledap > Make A Graph

Dataset Title:	GLIDERS_MISSIONS_2024 Apr_Jun_V1
Institution:	OOI Coastal Endurance   (Dataset ID: GLIDERS_2024_04_06_V1)
Range:	longitude = -127.99492 to -70.89158°E, latitude = 30.947945 to 47.13317°N, depth = -0.08925338 to 1001.7873m, time = 2004-06-15T14:23:56Z to 2024-07-23T01:01:47Z
Information:	Summary | License | FGDC | ISO 19115 | Metadata | Background | Subset | Data Access Form | Files

 

Graph Type:  lines linesAndMarkers markers sticks vectors X Axis:  time latitude longitude depth temperature salinity Y Axis:  time latitude longitude depth temperature salinity Color:  time latitude longitude depth temperature salinity   Constraints Optional Constraint #1 Optional Constraint #2 trajectory time latitude longitude depth temperature salinity     != =~ <= >= = < >     != =~ <= >= = < >     trajectory time latitude longitude depth temperature salinity     != =~ <= >= = < >     != =~ <= >= = < >     trajectory time latitude longitude depth temperature salinity     != =~ <= >= = < >     != =~ <= >= = < >     trajectory time latitude longitude depth temperature salinity     != =~ <= >= = < >     != =~ <= >= = < >     trajectory time latitude longitude depth temperature salinity     != =~ <= >= = < >     != =~ <= >= = < >       Server-side Functions  distinct() orderBy orderByDescending orderByClosest orderByCount orderByLimit orderByMax orderByMin orderByMinMax orderByMean orderBySum (" trajectory time latitude longitude depth temperature salinity trajectory time latitude longitude depth temperature salinity trajectory time latitude longitude depth temperature salinity trajectory time latitude longitude depth temperature salinity ")   Graph Settings Marker Type:  None Plus X Dot Square Filled Square Circle Filled Circle Up Triangle Filled Up Triangle Borderless Filled Square Borderless Filled Circle Borderless Filled Up Triangle  Size:  3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Color:  Color Bar:  BlackBlueWhite BlackGreenWhite BlackRedWhite BlackWhite BlueWhiteRed BlueWideWhiteRed LightRainbow Ocean OceanDepth Rainbow Rainbow2 Rainfall ReverseRainbow RedWhiteBlue RedWhiteBlue2 RedWideWhiteBlue Spectrum Topography TopographyDepth WhiteBlueBlack WhiteGreenBlack WhiteRedBlack WhiteBlack YellowRed KT_algae KT_amp KT_balance KT_curl KT_deep KT_delta KT_dense KT_gray KT_haline KT_ice KT_matter KT_oxy KT_phase KT_solar KT_speed KT_tempo KT_thermal KT_turbid EK80  Continuity:  Continuous Discrete  Scale:  Linear Log    Minimum:   Maximum:   N Sections:  2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Draw land mask:  under over outline off Y Axis Minimum:   Maximum:    Ascending Descending Linear Log   Redraw the Graph (Please be patient. It may take a while to get the data.)   Optional: Then set the File Type: .asc .csv .csvp .csv0 .dataTable .das .dds .dods .esriCsv .fgdc .geoJson .graph .help .html .htmlTable .iso19115 .itx .json .jsonlCSV1 .jsonlCSV .jsonlKVP .mat .nc .ncHeader .ncCF .ncCFHeader .ncCFMA .ncCFMAHeader .nccsv .nccsvMetadata .ncoJson .odvTxt .parquet .parquetWMeta .subset .tsv .tsvp .tsv0 .wav .xhtml .kml .smallPdf .pdf .largePdf .smallPng .png .largePng .transparentPng (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:  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 second(s) minute(s) hour(s) day(s) month(s) year(s)

 

---

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 {
  trajectory {
    String comment "A trajectory is a single deployment of a glider and may span multiple data files.";
    String ioos_category "Identifier";
    String long_name "Trajectory/Deployment Name";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.087309436492e+9, 1.721696507084e+9;
    String axis "T";
    String calendar "gregorian";
    String comment "Timestamp at each point in the time-series";
    String ioos_category "Time";
    String long_name "Precise Time";
    String observation_type "measured";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 30.947945290322583, 47.133169498363124;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String comment "Interpolated latitude at each point in the time-series";
    String coordinate_reference_frame "urn:ogc:crs:EPDG::4326";
    String ioos_category "Location";
    String long_name "Precise Latitude";
    String observation_type "measured";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -127.99491926998851, -70.89157779664312;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String comment "Interpolated longitude at each point in the time-series";
    String coordinate_reference_frame "urn:ogc:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "Precise Longitude";
    String observation_type "measured";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range -0.08925337765735997, 1001.7872685986343;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String comment "Depth below the surface, corrected for average latitude";
    String ioos_category "Location";
    String long_name "Depth";
    Float64 missing_value NaN;
    String observation_type "calculated";
    String positive "down";
    String reference_datum "sea-surface";
    String standard_name "depth";
    String units "m";
    Float64 valid_max 2000.0;
    Float64 valid_min 0.0;
  }
  temperature {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 28.204200744628906;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String comment "Temperature (in situ) corrected for thermistor first-order lag";
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    Float64 missing_value NaN;
    String observation_type "measured";
    String standard_name "sea_water_temperature";
    String units "degree_C";
    Float64 valid_max 40.0;
    Float64 valid_min -5.0;
  }
  salinity {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 37.51340792383124;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String comment "Salinity corrected for thermal-inertia effects (PSU)";
    String ioos_category "Salinity";
    String long_name "Sea Water Practical Salinity";
    Float64 missing_value NaN;
    String observation_type "calculated";
    String standard_name "sea_water_practical_salinity";
    String units "1e-3";
    Float64 valid_max 40.0;
    Float64 valid_min 0.0;
  }
 }
  NC_GLOBAL {
    String background "https://gliders.ioos.us/erddap/index.html";
    String cdm_data_type "Point";
    String Conventions "CF-1.10, COARDS, ACDD-1.3";
    String creator_name "University of South Florida";
    String creator_type "institution";
    Float64 Easternmost_Easting -70.89157779664312;
    String featureType "Point";
    Float64 geospatial_lat_max 47.133169498363124;
    Float64 geospatial_lat_min 30.947945290322583;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -70.89157779664312;
    Float64 geospatial_lon_min -127.99491926998851;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1001.7872685986343;
    Float64 geospatial_vertical_min -0.08925337765735997;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Observational Slocum glider data from source dba file usf-jaialai-2024-177-2-190-sbd(02370190)
2025-05-03T17:25:08Z (local files)
2025-05-03T17:25:08Z https://erddap.aoml.noaa.gov/hdb/tabledap/GLIDERS_2024_04_06_V1.das";
    String id "ce_382-20240618T1940";
    String infoUrl "???";
    String institution "OOI Coastal Endurance";
    String keywords "20240710225436z, conductivity, data, density, deployment, depth, earth, Earth Science > Oceans > Ocean Pressure > Water Pressure, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Conductivity, Earth Science > Oceans > Salinity/Density > Density, Earth Science > Oceans > Salinity/Density > Salinity, florida, identifier, jaialai, latitude, longitude, name, ocean, oceans, practical, precise, pressure, profile, salinity, salinity/density, science, sea, sea_water_practical_salinity, sea_water_temperature, seawater, south, temperature, time, trajectory, trajectory/deployment, university, usf, usf-jaialai-20240710225436z, vertical, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"All OOI data including data from OOI core sensors and all proposed sensors added
by Principal Investigators, will be rapidly disseminated, open, and freely
available (within constraints of national security). Rapidly disseminated
implies that data will be made available as soon as technically feasible, but
generally in near real-time, with latencies as small as seconds for the cabled
components. In limited cases, individual PIs who have developed a data source
that becomes part of the OOI network may request exclusive rights to the data
for a period of no more than one year from the onset of the data stream. The
reliability, quality and completeness of data obtained through OOI are intended
to be used in an education or research context. It is assumed that outages and
errors can occur and are dealt with by the users of the data. These data and
software are not for use in operational or decision-making settings. The OOI
program makes reasonable efforts to ensure that the data provided are accurate.
However, there may be no Quality Control (QC) performed on data acquired and
provided through the OOI program, and there may be no Quality Assurance (QA)
provided on information on those data sets. If QC/QA is performed, it is
described in the metadata.

The OOI program both produces and, through collaborations within the geosciences
community, gains access to data sets which may be redistributed either directly
or indirectly at no cost and with no restrictions.

With regard to data distribution, all users must comply with any applicable U.S.
export laws and regulations. The OOI Program is not responsible for the use of
the data it provides. The full data policy is available at
http://oceanobservatories.org/usage-policy.";
    String Metadata_Conventions "CF-1.6, Unidata Dataset Discovery v1.0";
    Float64 Northernmost_Northing 47.133169498363124;
    String platform_type "Slocum Glider";
    String project "Coastal Endurance Array";
    String references "http://oceanobservatories.org/";
    String sea_name "Northeast Pacific Ocean";
    String source "Observational data from a profiling glider";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 30.947945290322583;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "longitude, trajectory, latitude";
    String summary 
"The Endurance Array is a multi-scaled array utilizing fixed and mobile assets to
observe cross-shelf and along-shelf variability in the coastal upwelling region
off the Oregon and Washington coasts. The array also provides an extensive
spatial footprint that encompasses a prototypical eastern boundary current
regime and connectivity with the Cabled Array. OOI Coastal Glider deployments
bridge the distances between the fixed sites of the Coastal Endurance Array and
allow for adaptive sampling of the coastal waters of Washington and Oregon.
This dataset contains raw Slocum glider data parsed directly from the native
glider file format. No corrections or other quality control algorithms have been
applied.";
    String time_coverage_end "2024-07-23T01:01:47Z";
    String time_coverage_start "2004-06-15T14:23:56Z";
    String title "GLIDERS_MISSIONS_2024 Apr_Jun_V1";
    Float64 Westernmost_Easting -127.99491926998851;
  }
}

 

---

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 Data Access Protocol (DAP) and its selection constraints.

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