Make A Graph

Dataset Title:	Harbour seal GPS tracks - SeaMonitor deployments (N. Ireland)
Institution:	University College Cork (Dataset ID: ucc_seal_tags)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background

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:

[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 {
  midgid {
    String cf_role "trajectory_id";
    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";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  SeaVox_SeaArea {
    String comment "This field is populated from the SeaVoX salt and fresh water body gazetteer (https://vocab.nerc.ac.uk/collection/C19/current/).";
    String ioos_category "Identifier";
    String long_name "SeaVox Sea-Area";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  SeaVox_SeaArea_urn {
    String comment "This field is populated with the code from the SeaVoX salt and fresh water body gazetteer (https://vocab.nerc.ac.uk/collection/C19/current/).";
    String ioos_category "Identifier";
    String long_name "SeaVox Sea-Area code value";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  ICES_ecoregion {
    String comment "The ecoregions are based on biogeographic and oceanographic features and existing political, social, economic, and management divisions. They are developed through an iterative process of consultations between scientists and stakeholders led by the ICES Advisory Committee (ACOM). See: https://www.ices.dk/SiteCollectionImages/advice/ICES_ecoregions.jpg";
    String ioos_category "Identifier";
    String long_name "ICES ecoregion";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  ICES_area {
    String comment "See: https://www.ices.dk/data/Documents/Maps/ICES-Ecoregions-hybrid-statistical-areas.png";
    String ioos_category "Identifier";
    String long_name "ICES area";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  ICES_statistical_rectangle {
    String comment "ICES statistical rectangles are used for the gridding of data to make simplified analysis and visualization. ICES statistical rectangles (StatRecs) have been in use since the 1970's, and were first officially referenced in CM document 1977/Gen:3 document 'ICES Statistical Rectangle Coding System'. ICES statistical rectangles provide a grid covering the area between 36 degrees N and 85 degrees 30 minutes N and 44 degrees W and 68 degrees 30 minutes E. See: https://www.ices.dk/data/maps/Pages/ICES-statistical-rectangles.aspx";
    String ioos_category "Identifier";
    String long_name "ICES statistical rectangle";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  MSFD_region {
    String comment "This field is populated with the MSFD region (https://www.eea.europa.eu/data-and-maps/data/europe-seas/marine-regions-and-subregions-1/technical-document).";
    String ioos_category "Identifier";
    String long_name "Marine Strategy Framework Directive region";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  MSFD_subregion {
    String comment "This field is populated with the MSFD sub-region (https://www.eea.europa.eu/data-and-maps/data/europe-seas/marine-regions-and-subregions-1/technical-document).";
    String ioos_category "Identifier";
    String long_name "Marine Strategy Framework Directive sub-region";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  WFD_waterbody_type {
    String comment "This field is populated with the WFD water body type (http://gis.epa.ie/GetData/Download).";
    String ioos_category "Identifier";
    String long_name "Water Framework Directive waterbody type";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  WFD_waterbody_name {
    String comment "This field is populated with the WFD water body name (http://gis.epa.ie/GetData/Download).";
    String ioos_category "Identifier";
    String long_name "Water Framework Directive waterbody name";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  SWD_shellfish_waterbody {
    String comment "This field is populated with the SWD water body name (http://gis.epa.ie/GetData/Download).";
    String ioos_category "Identifier";
    String long_name "Shellfish Water Directive shellfish water";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  comp4_assessment_area_name {
    String comment "This field is populated with the 4th Application of OSPAR Common Procedure Assessment Area names.";
    String ioos_category "Identifier";
    String long_name "OSPAR Comp4 Assessment Area Name";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  ore_site {
    String comment "Name of an actual or prospective ORE site";
    String ioos_category "Identifier";
    String long_name "ORE site name";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  transect {
    String comment "A name given to a repeat transect as a grouping of repeat stations or collection of stations along a geographically defined transect.";
    String ioos_category "Other";
    String long_name "Named transect of repeat stations";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  station_id {
    String comment "A name used to identify a location that has over time been revisited for the purpose of repeat measurement as part of a long-term observation series. Sometimes termed a \"site\" and OceanSITES define as a defined geographic location where sustained oceanographic, meteorological or other observations are made. Note: A site should be thought of as a point in space, i.e. a nominal position, with a small area extent around it, such that successive observations from anywhere within this area reasonably represent conditions at the nominal position for the major scientific questions that the observations address.";
    String ioos_category "Identifier";
    String long_name "Station name";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  site_bathy_depth {
    String comment "The sea-floor depth at the location identified by the positional metadata in the dataset.";
    String ioos_category "Bathymetry";
    String long_name "sea floor depth below sea surface";
    String sdn_parameter_name "Sea-floor depth (below instantaneous sea level) {bathymetric depth} in the water body";
    String sdn_parameter_urn "SDN:P01::MBANZZZZ";
    String sdn_uom_name "Metres";
    String sdn_uom_urn "SDN:P06::ULAA";
    String standard_name "sea_floor_depth_below_sea_surface";
    String technical_data "true";
    String units "m";
  }
  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 sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String standard_name "platform_name";
    String technical_data "true";
    String units "Not applicable";
  }
  gps_tag_model_name {
    String comment "A metadata variable containing the GPS tag make and model.";
    String ioos_category "Other";
    String long_name "GPS tag make and model";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  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";
    String sdn_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  gps_tag_serial_number {
    String comment "A metadata variable containing the GPS tag serial number.";
    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_uom_name "Not applicable";
    String sdn_uom_urn "SDN:P06::XXXX";
    String technical_data "true";
    String units "Not applicable";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String calendar "standard";
    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_uri "https://vocab.nerc.ac.uk/collection/P01/current/ELTMEP01/";
    String sdn_parameter_urn "SDN:P01::ELTMEP01";
    String sdn_qc "1";
    String sdn_uom_name "Seconds";
    String sdn_uom_uri "https://vocab.nerc.ac.uk/collection/P06/current/UTBB/";
    String sdn_uom_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";
    String whp_name "DATE,TIME";
  }
  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 "sea level";
    String sdn_parameter_name "Depth (spatial coordinate) relative to water surface in the water body";
    String sdn_parameter_uri "https://vocab.nerc.ac.uk/collection/P01/current/ADEPZZ01/";
    String sdn_parameter_urn "SDN:P01::ADEPZZ01";
    String sdn_qc "7";
    String sdn_uom_name "metres";
    String sdn_uom_uri "https://vocab.nerc.ac.uk/collection/P06/current/ULAA/";
    String sdn_uom_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_uri "https://vocab.nerc.ac.uk/collection/P01/current/ALATZZ01/";
    String sdn_parameter_urn "SDN:P01::ALATZZ01";
    String sdn_uom_name "Degrees north";
    String sdn_uom_uri "https://vocab.nerc.ac.uk/collection/P06/current/DEGN/";
    String sdn_uom_urn "SDN:P06::DEGN";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
    String whp_name "LATITUDE";
  }
  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_uri "https://vocab.nerc.ac.uk/collection/P01/current/ALONZZ01/";
    String sdn_parameter_urn "SDN:P01::ALONZZ01";
    String sdn_uom_name "Degrees east";
    String sdn_uom_uri "https://vocab.nerc.ac.uk/collection/P06/current/DEGE/";
    String sdn_uom_urn "SDN:P06::DEGE";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
    String whp_name "LONGITUDE";
  }
 }
  NC_GLOBAL {
    String acknowledgement "SeaMonitor has been funded by the EU's INTERREG VA programme, managed by the Special EU Programmes Body (SEUPB).";
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "animal_name,midgid";
    String contact "samantha.cox@ucc.ie";
    String contributor_name "Sam Cox";
    String contributor_role "author";
    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 date_created "2025-05-12T10:47:54.723Z";
    String date_modified "2025-05-12T10:50:30.010Z";
    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.
2026-07-14T13:12:58Z (source database)
2026-07-14T13:12:58Z http://erddap.digitalocean.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_edmo_uri "https://edmo.seadatanet.org/report/2125";
    String institution_references "https://www.ucc.ie/en/";
    String keywords "Seal behaviour";
    String keywords_type "parameter";
    String keywords_uri "https://vocab.nerc.ac.uk/collection/P02/current/SEBH/";
    String keywords_urn "SDN:P02::SEBH";
    String keywords_vocabulary "SeaDataNet Parameter Discovery Vocabulary";
    String keywords_vocabulary_uri "https://vocab.nerc.ac.uk/collection/P02/current/";
    String license "CC-BY-4.0";
    String license_uri "https://spdx.org/licenses/CC-BY-4.0";
    String license_URL "https://creativecommons.org/licenses/by/4.0/";
    String naming_authority "Marine Institute";
    String principal_investigator "Mark Jessopp";
    String processing_level "Instrument data that has been converted to geophysical values";
    String project "SeaMonitor";
    String publisher_email "datarequests@marine.ie";
    String publisher_name "Marine Institute";
    String publisher_url "http://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 v94";
    String subsetVariables "animal_name";
    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 "Harbour seal GPS tracks - SeaMonitor deployments (N. Ireland)";
  }
}

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.