Marine Institute Logo Marine Institute ERDDAP Server
Serving data from the Marine Institute (Ireland)
   
Brought to you by the Marine Institute(Ireland)    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Monitoring diving and space-use by harbour seals across the Irish Sea region
to better understand behaviour, and identify and mitigate interactions with
anthropogenic activities.
  RSS
Institution:  University College Cork   (Dataset ID: ucc_seal_tags)
Information:  Summary ? | License ? | FGDC | 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: 
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: 
[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 {
  midgid {
    String comment "The internal identifier for data granules (e.g. a CTD profile, a mooring deployment, a cruise of underway data, etc) managed by the Marine Institute.";
    String ioos_category "Identifier";
    String long_name "Marine Institute Data Granule Identifier";
  }
  animal_name {
    String comment "The name or identifier of the animal the tag was deployed on.";
    String ioos_category "Identifier";
    String long_name "animal name or identifier";
    String standard_name "platform_name";
  }
  gps_tag_model_name {
    String ioos_category "Other";
    String long_name "GPS tag make and model";
  }
  gps_tag_model_urn {
    String comment "This code is taken from the SeaVoX Device Catalogue (https://vocab.nerc.ac.uk/collection/L22/current/).";
    String ioos_category "Identifier";
    String long_name "SeaVox Device code for the GPS tag make and model";
  }
  gps_tag_serial_number {
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "GPS tag serial number";
    String sdn_parameter_name "Serial number of instrument";
    String sdn_parameter_urn "SDN:P01::SERNUMZZ";
    String sdn_units_name "Not applicable";
    String sdn_units_urn "SDN:P06::XXXX";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String calendar "julian";
    String ioos_category "Time";
    String long_name "time of measurement";
    String Processing_level "Raw instrument data";
    String QC_indicator "good data";
    String sdn_odv_parameter_urn "SDN:P01::DTUT8601";
    String sdn_odv_units_urn "SDN:P06::TISO";
    String sdn_parameter_name "Elapsed time relative to 1970-01-01T00:00:00Z";
    String sdn_parameter_urn "SDN:P01::ELTMEP01";
    String sdn_qc "1";
    String sdn_units_name "Seconds";
    String sdn_units_urn "SDN:P06::UTBB";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String axis "Z";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::5715";
    String ioos_category "Location";
    String long_name "depth of measurement";
    String positive "down";
    String Processing_level "Data manually reviewed";
    String QC_indicator "nominal value";
    String reference "mean_sea_level";
    String sdn_parameter_name "Depth (spatial coordinate) relative to water surface in the water body";
    String sdn_parameter_urn "SDN:P01::ADEPZZ01";
    String sdn_qc "7";
    String sdn_units_name "metres";
    String sdn_units_urn "SDN:P06::ULAA";
    String standard_name "depth";
    String units "m";
    Float64 valid_max 12000.0;
    Float64 valid_min 0.0;
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue 99999.0;
    String axis "Y";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "latitude of measurement";
    String Processing_level "Data manually reviewed";
    String QC_indicator "nominal value";
    String reference "WGS84";
    String sdn_parameter_name "Latitude north";
    String sdn_parameter_urn "SDN:P01::ALATZZ01";
    String sdn_units_name "Degrees north";
    String sdn_units_urn "SDN:P06::DEGN";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue 99999.0;
    String axis "X";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "longitude of measurement";
    String Processing_level "Data manually reviewed";
    String QC_indicator "nominal value";
    String reference "WGS84";
    String sdn_parameter_name "Longitude east";
    String sdn_parameter_urn "SDN:P01::ALONZZ01";
    String sdn_units_name "Degrees east";
    String sdn_units_urn "SDN:P06::DEGE";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  latitude_qc {
    Int32 _FillValue 9;
    String Conventions "SeaDataNet measurand qualifier flags";
    String flag_meanings "no_quality_control good_value probably_good_value probably_bad_value bad_value changed_value value_below_detection value_in_excess interpolated_value missing_value";
    String flag_values "0 1 2 3 4 5 6 7 8 9";
    String ioos_category "Quality";
    String long_name "latitude data quality flag";
    String sdn_conventions_urn "SDN:L20::";
    String standard_name "quality_flag";
  }
  longitude_qc {
    Int32 _FillValue 9;
    String Conventions "SeaDataNet measurand qualifier flags";
    String flag_meanings "no_quality_control good_value probably_good_value probably_bad_value bad_value changed_value value_below_detection value_in_excess interpolated_value missing_value";
    String flag_values "0 1 2 3 4 5 6 7 8 9";
    String ioos_category "Quality";
    String long_name "longitude data quality flag";
    String sdn_conventions_urn "SDN:L20::";
    String standard_name "quality_flag";
  }
  depth_qc {
    Int32 _FillValue 9;
    String Conventions "SeaDataNet measurand qualifier flags";
    String flag_meanings "no_quality_control good_value probably_good_value probably_bad_value bad_value changed_value value_below_detection value_in_excess interpolated_value missing_value";
    String flag_values "0 1 2 3 4 5 6 7 8 9";
    String ioos_category "Quality";
    String long_name "depth data quality flag";
    String sdn_conventions_urn "SDN:L20::";
    String standard_name "quality_flag";
  }
 }
  NC_GLOBAL {
    String acknowledgement "SeaMonitor has been funded by the EU's INTERREG VA programme, managed by the Special EU Programmes Body (SEUPB).";
    String area "North Atlantic Ocean";
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "gps_tag_serial_number";
    String contact "samantha.cox@ucc.ie M.Jessopp@ucc.ie";
    String contributor_email "samantha.cox@ucc.ie";
    String contributor_name "Sam Cox";
    String contributor_role "Researcher";
    String Conventions "Copernicus-InSituTAC-FormatManual-1.4, SeaDataNet_1.0, CF-1.6, OceanSITES-1.3, ACDD-1.2, COARDS";
    String data_mode "R";
    String data_type "OceanSITES trajectory data";
    String defaultDataQuery "&time>=now-30days";
    String defaultGraphQuery "&time>=now-30days";
    String featureType "Trajectory";
    String geospatial_lat_max "57.0965";
    String geospatial_lat_min "50.7651";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_max "-3.1472";
    String geospatial_lon_min "-10.3913";
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_max "0";
    String geospatial_vertical_min "0";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2020-08-10: Data first made available on MI Erddap.
2022-09-24T23:45:09Z (source database)
2022-09-24T23:45:09Z https://erddap3.marine.ie/tabledap/ucc_seal_tags.das";
    String id "ie.marine.data:dataset.4272";
    String infoUrl "http://data.marine.ie/geonetwork/srv/eng/catalog.search#/metadata/ie.marine.data:dataset.4272";
    String institution "University College Cork";
    String institution_edmo_code "2125";
    String institution_references "https://www.ucc.ie";
    String keywords "Seal behaviour";
    String keywords_vocabulary "SeaDataNet Parameter Discovery Vocabulary";
    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 license_URL "https://creativecommons.org/licenses/by/4.0/legalcode";
    String naming_authority "Marine Institute";
    String principal_investigator "Mark Jessopp";
    String principal_investigator_email "m.jessopp@ucc.ie";
    String principal_investigator_url "https://www.ucc.ie/en/bees/staff/mjessop/";
    String processing_level "Instrument data that has been converted to geophysical values";
    String project "SeaMonitor";
    String publisher_email "data_requests@marine.ie";
    String publisher_name "Marine Institute";
    String publisher_url "https://www.marine.ie";
    String source "land-sea mammals";
    String source_platform_category_code "77";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v79";
    String subsetVariables "gps_tag_serial_number";
    String summary "Telemetry studies are a useful tool for assessing potential interactions between marine biota and anthropogenic activities. For seals, that are exposed to multiple threats stemming from, for example, aquaculture and commercial fisheries alongside specifically noise-generating activities such as shipping, oil and gas exploration and marine contraction projects, GPS-GSM tags can be used to track movements in near-real time across large spatial extents for a period of several months. This information can then be used to assess interactions between seals and these potentially impactful anthropogenic activities.  Here, we focus on tracking the behaviours and distributions of rehabilitated juvenile harbour seals, that may be particularly vulnerable to disturbance from human interference. Using Fastloc technology, which requires less than 1 second at the surface to obtain a fix, tags were programmed to record a location roughly every 15 minutes, subsequently providing high resolution data on seal movements.  Tags also had an inbuilt time-depth recorder, programmed to log summarised dive events (summarised using a broken-stick algorithm to 10 inflexion points including the maximum depth).  Together this information was transmitted by the GSM mobile phone network when a seal came within range.  This data is/was collected as part of the INTERREG funded SeaMonitor project, with an aim to better understand the dive behaviour, movements, space use (alongside interactions with anthropogenic activities), and survival of rehabilitated juvenile harbour seals (Phoca vitulina) from Northern Ireland.";
    String time_coverage_duration "P1Y8M236D";
    String time_coverage_end "2021-07-11T04:49:56Z";
    String time_coverage_resolution "PT15M";
    String time_coverage_start "2019-11-17T15:34:25Z";
    String title "Monitoring diving and space-use by harbour seals across the Irish Sea region to better understand behaviour, and identify and mitigate interactions with anthropogenic activities.";
  }
}

 

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