Nautilos    ERDDAP NAUTILOS
Easier access to scientific data
   
Brought to you by Nautilos    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  NAUTILOS - CEiiA Lander with UL-FE Deep Ocean CTD - Metadata - CEiiA / UL-FE Subscribe RSS
Institution:  CEiiA, UL-FE   (Dataset ID: CTD_lander_ceiia_metadata)
Range: time = 2024-05-23T20:39:55Z to 2024-07-14T11:30:16Z
Information:  Summary ? | License ? | Metadata | Background | Data Access Form | Files
 
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 {
  mission_id {
    String long_name "Mission Id";
  }
  title {
    String long_name "Title";
  }
  project_name {
    String long_name "Project Name";
  }
  project_code {
    String long_name "Project Code";
  }
  project_id {
    Int32 _FillValue 2147483647;
    Int32 actual_range 101000825, 101000825;
    String long_name "Project Id";
  }
  project_statement {
    String long_name "Project Statement";
  }
  Project_DOI {
    String long_name "Project DOI";
  }
  project_edmerp {
    Int16 _FillValue 32767;
    Int16 actual_range 13720, 13720;
    String long_name "Project Edmerp";
  }
  naming_authority {
    String long_name "Naming Authority";
  }
  cdm_data_type {
    String long_name "Cdm Data Type";
  }
  Conventions {
    String long_name "Conventions";
  }
  infoUrl {
    String long_name "Info Url";
  }
  institution {
    String long_name "Institution";
  }
  institution_country {
    String long_name "Institution Country";
  }
  institution_references {
    String long_name "Institution References";
  }
  keywords {
    String long_name "Keywords";
  }
  keywords_vocabulary {
    String long_name "Keywords Vocabulary";
  }
  licence {
    String long_name "Licence";
  }
  standard_name_vocabulary {
    String long_name "Standard Name Vocabulary";
  }
  summary {
    String long_name "Summary";
  }
  platform_type {
    String long_name "Platform Type";
  }
  variables {
    String long_name "Variables";
  }
  contributors_email {
    String long_name "Contributors Email";
  }
  contributors_name {
    String long_name "Contributors Name";
  }
  contributors_orcid {
    String long_name "Contributors Orcid";
  }
  contributors_role {
    String long_name "Contributors Role";
  }
  creator_email {
    String long_name "Creator Email";
  }
  creator_name {
    String long_name "Creator Name";
  }
  creator_type {
    String long_name "Creator Type";
  }
  creator_url {
    String long_name "Creator Url";
  }
  geospatial_lat_max {
    Float64 actual_range 41.185828646062284, 41.185828646062284;
    String long_name "Geospatial Lat Max";
  }
  geospatial_lat_min {
    Float64 actual_range 41.185828646062284, 41.185828646062284;
    String long_name "Geospatial Lat Min";
  }
  geospatial_lat_resolution {
    String long_name "Geospatial Lat Resolution";
  }
  geospatial_lat_units {
    String long_name "Geospatial Lat Units";
  }
  geospatial_lon_max {
    Float64 actual_range -8.704694078785254, -8.704694078785254;
    String long_name "Geospatial Lon Max";
  }
  geospatial_lon_min {
    Float64 actual_range -8.704694078785254, -8.704694078785254;
    String long_name "Geospatial Lon Min";
  }
  geospatial_lon_resolution {
    String long_name "Geospatial Lon Resolution";
  }
  geospatial_lon_units {
    String long_name "Geospatial Lon Units";
  }
  geospatial_vertical_max {
    String long_name "Geospatial Vertical Max";
  }
  geospatial_vertical_min {
    String long_name "Geospatial Vertical Min";
  }
  geospatial_vertical_positive {
    String long_name "Geospatial Vertical Positive";
  }
  geospatial_vertical_units {
    String long_name "Geospatial Vertical Units";
  }
  inspire {
    String long_name "Inspire";
  }
  institution_edmo_code {
    String long_name "Institution Edmo Code";
  }
  references {
    String long_name "References";
  }
  source {
    String long_name "Source";
  }
  time_coverage_duration {
    String long_name "Time Coverage Duration";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.716496795e+9, 1.720956616e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time Coverage End";
    String source_name "time_coverage_end";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time_coverage_resolution {
    String long_name "Time Coverage Resolution";
  }
  time_coverage_start {
    Float64 actual_range 1.715943277e+9, 1.720192166e+9;
    String ioos_category "Time";
    String long_name "Time Coverage Start";
    String source_name "time_coverage_start";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  platform_id_orig {
    String long_name "Platform Id Orig";
  }
  sensor_model {
    String long_name "Sensor Model";
  }
  data_doi {
    String long_name "Data Doi";
  }
  oceanographic_campaign {
    String long_name "Oceanographic Campaign";
  }
  ship_name {
    String long_name "Ship Name";
  }
  ship_imo {
    String long_name "Ship Imo";
  }
  ship_call_sign {
    String long_name "Ship Call Sign";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String history 
"2025-04-18T19:42:54Z (local files)
2025-04-18T19:42:54Z https://data-nautilos-h2020.eu/tabledap/CTD_lander_ceiia_metadata.das";
    String infoUrl "https://data-nautilos-h2020.eu/erddap/index.html";
    String institution "CEiiA, UL-FE";
    String institution_country "PRT, LTU";
    String institution_references "CEiiA is an engineering and product development centre that designs, develops and productizes new technologies, products and services towards a more sustainable society. From Portugal, we work by bridging together cities, industries and universities around product development programs in high-tech sectors such as Mobility, Aeronautics, Space and Ocean. / The Faculty of Electrical Engineering at the University of Ljubljana is a high-tech educational and scientific research institution in the field of electrical engineering.";
    String keywords "ocean conductivity, ocean pressure, ocean temperature";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY 4.0";
    String naming_authority "NAUTILOS";
    String platform_type "submersible";
    String project_code "NAUTILOS";
    String Project_DOI "https://doi.org/10.3030/101000825";
    String project_edmerp "13720";
    String project_id "101000825";
    String project_name "New Approach to Underwater Technologies for Innovative, Low-cost Ocean obServation";
    String project_statement "This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 101000825 (NAUTILOS). This output reflects only the author's view and the European Union cannot be held responsible for any use that may be made of the information contained therein";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "NAUTILOS - CEiiA Lander with UL-FE Deep Ocean CTD - Metadata - CEiiA / UL-FE";
    String time_coverage_end "2024-07-14T11:30:16Z";
    String time_coverage_start "2024-05-23T20:39:55Z";
    String title "NAUTILOS - CEiiA Lander with UL-FE Deep Ocean CTD - Metadata - CEiiA / UL-FE";
  }
}

 

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