BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [seal_location_tracking] - Locations of satellite-tagged harbor seals in the
San Juan Islands, WA from 2007-2009 (Responses of Seals and Sea Lions to
Increased Rockfish Density)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3704)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 seal_id (unitless) ?          "89736"    "Y1514"
 pttno (unitless) ?          35921    92047
 inst (unitless) ?          "Mk10"    "SPOT5"
 latitude (degrees_north) ?          8.818    61.208
  < slider >
 longitude (degrees_east) ?          -175.813    179.802
  < slider >
 lat2 (Latitude, decimal degrees) ?          -61.832    78.886
 lon2 (Longitude, decimal degrees) ?          -179.999    179.991
 month (mm) ?          "01"    "12"
 day (dd) ?          "01"    "31"
 year (unitless) ?          2007    2009
 date (unitless) ?          "01/01/2008"    "12/31/2007"
 time2 (Time, HHMM) ?          "0000"    "2359"
 satellite (unitless) ?          "A"    "P"
 loc_q_flaq (unitless) ?          "0"    "Z"
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  seal_id {
    String bcodmo_name "sealname";
    String description "Unique seal identification.";
    String long_name "Seal Id";
    String units "unitless";
  }
  pttno {
    Int32 _FillValue 2147483647;
    Int32 actual_range 35921, 92047;
    String bcodmo_name "tagid";
    String description "PTT tag number.";
    String long_name "Pttno";
    String units "unitless";
  }
  inst {
    String bcodmo_name "inst_model";
    String description "Name of the instrument (MK10 or SPOT 5; both manufactured by Wildlife Computers).";
    String long_name "Inst";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 8.818, 61.208;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Primary latitude. (See Acquisition Description.)";
    String ioos_category "Location";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -175.813, 179.802;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Primary longitude. (See Acquisition Description.)";
    String ioos_category "Location";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "degrees_east";
  }
  lat2 {
    Float32 _FillValue NaN;
    Float32 actual_range -61.832, 78.886;
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Secondary estimate of latitude provided by Argos. (See Acquisition Description.)";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "decimal degrees";
  }
  lon2 {
    Float32 _FillValue NaN;
    Float32 actual_range -179.999, 179.991;
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Secondary estimate of longitude provided by Argos. (See Acquisition Description.)";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "decimal degrees";
  }
  month {
    String bcodmo_name "month";
    String description "Month of year (01 to 12).";
    String long_name "Month";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/MNTHXXXX/";
    String units "mm";
  }
  day {
    String bcodmo_name "day";
    String description "Day of month (01 to 31).";
    String long_name "Day";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DAYXXXXX/";
    String units "dd";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2007, 2009;
    String bcodmo_name "year";
    String description "4-digit year. in yyyy format";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "unitless";
  }
  date {
    String bcodmo_name "date";
    String description "Date, in mm/dd/yyyy format.";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String source_name "date";
    String time_precision "1970-01-01";
    String units "unitless";
  }
  time2 {
    String bcodmo_name "time";
    String description "Time, 24-hour clock.";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "HHMM";
  }
  satellite {
    String bcodmo_name "unknown";
    String description "Identification of the Argos satellite transmitting the signal: A = METOP-A (MA); K = NOAA-15 (NK); L = NOAA-16 (NL); M = NOAA-17 (NM); N = NOAA-18 (NN); P = NOAA-N (NP). See more information.";
    String long_name "Satellite";
    String units "unitless";
  }
  loc_q_flaq {
    String bcodmo_name "q_flag";
    String description "Location quality flag. The Argos system classifies points with decreasing precision: 3 > 2 > 1 > 0 > A > B. See Acquisition Description for code definitions.";
    String long_name "Loc Q Flaq";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"Seals were captured and tagged in April or May of 2007 and 2008 following the
methods of Jeffries et al. (1993) at three sites: Padilla Bay, Bird/Belle
Rocks, and Protection Island. In 2009, seals were captured on Protection
Island. In 2007-2008, animals were tagged with time-depth recorders (TDR;
Wildlife Computers, model Mk-9 or Mk-10F) and satellite tags. The TDR tags
were placed on the dorsal midline of the animals and the satellite tags were
placed on top the head. In 2009, animals were tagged with a combined
satellite-linked TDR and Fastloc GPS receiver (Wildlife Computers, model
Mk10AF). These instruments were epoxied to the animals on the dorsal midline
so that satellite tags would be exposed to the air when the back of the seal
reached the surface.
 
Position transmissions were received via the ARGOS satellite network. Tags
transmitted locations daily. TDR sensors were programmed to sample every 10
seconds. TDR tags were equipped with a VHF transmitter to allow for the device
to be recovered when it was shed during the animal's annual molt.
 
The Argos system provides 2 position estimates (lat/lon and lat2/lon2). Argos
usually picks the correct lat/lon pair (of the two it generates), but
occasionally it does not. When working with these data, one of the first steps
is to check the lat/lon pairs to see if swapping out the lat/lon pair for the
lat2/lon2 pair improves the data and is more biologically reasonable.
 
The Argos positioning system uses the following system for classifying
location quality. These codes are used in the loc_q_flag column. Standard
locations are those with > 4 uplinks from the tag; auxiliary locations are
those with 4 or less uplinks from the tag.
 
loc_q_flag codes (according to Ward et al.):  
 Standard locations:  
 3 = 68th percentile predicted accuracy < 150 m  
 2 = 68th percentile predicted accuracy 150 - 350 m  
 1 = 68th percentile predicted accuracy < 1,000 m
 
Auxiliary locations:  
 0 = 4 uplinks, with > 1,000 m predicted accuracy  
 A = 3 uplinks, with no predicted accuracy  
 B = 2 uplinks, with no predicted accuracy";
    String awards_0_award_nid "54955";
    String awards_0_award_number "OCE-0550443";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0550443";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "David L. Garrison";
    String awards_0_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"Locations of Harbor Seals tagged and tracked at the San Juan Islands, 2007-2009 
 Lead PI: Alejandro Acevedo-Gutierrez 
 Version: 28 Nov 2012";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.3  19 Dec 2019";
    String date_created "2012-08-29T17:55:32Z";
    String date_modified "2019-03-01T20:28:35Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.3704.1";
    Float64 Easternmost_Easting 179.802;
    Float64 geospatial_lat_max 61.208;
    Float64 geospatial_lat_min 8.818;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 179.802;
    Float64 geospatial_lon_min -175.813;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-21T15:56:48Z (local files)
2024-11-21T15:56:48Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_3704.html";
    String infoUrl "https://www.bco-dmo.org/dataset/3704";
    String institution "BCO-DMO";
    String instruments_0_acronym "TDR";
    String instruments_0_dataset_instrument_description "TDR's were epoxied to seals along the dorsal midline. All TDR tags were equipped with an Eco-tech floatation pack and a VHF radio transmitter to allow for tracking and retrieval of the device once it became detached from the animal. TDR sensors were set to sample every 10 seconds and record only dives >2 m in depth or >30 s in duration. In 2009, the TDR's used contained an MK10-AF Argos transmitter.";
    String instruments_0_dataset_instrument_nid "5755";
    String instruments_0_description "Time depth recorders (TDR's) manufactured by Wildlife Computers, Redmond WA) are designed for studies of seals, penguins, fish, and marine mammals. Standard TDR's are mounted externally on the animal's body, where they record temperature and depth. See more information from the manufacturer.";
    String instruments_0_instrument_name "Wildlife Computers Time-Depth Tag (TDR)";
    String instruments_0_instrument_nid "668";
    String instruments_0_supplied_name "Wildlife Computers TDR";
    String instruments_1_acronym "SPOT5";
    String instruments_1_dataset_instrument_description "In 2007-2008, SPOT5 transmitters were epoxied to the tops of seals heads. Satellite locations were obtained daily.";
    String instruments_1_dataset_instrument_nid "5756";
    String instruments_1_description "The SPOT5 is an Argos transmitter manufactured by Wildlife Computers (Redmond, WA) and designed for deployment on marine mammals, fish, or seabirds. SPOT5 devices use the Argos satellite network to transmit locations of animals with an accuracy of +/- 350-meters. See more information from the manufacturer.";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/POS17/";
    String instruments_1_instrument_name "SPOT5 Argos Transmitter";
    String instruments_1_instrument_nid "669";
    String instruments_1_supplied_name "SPOT5 Argos Transmitter";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, date, day, dmo, erddap, flaq, inst, lat2, latitude, loc, loc_q_flaq, lon2, longitude, management, month, oceanography, office, preliminary, pttno, satellite, seal, seal_id, time, time2, year";
    String license "https://www.bco-dmo.org/dataset/3704/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3704";
    Float64 Northernmost_Northing 61.208;
    String param_mapping "{'3704': {'lat': 'flag - latitude', 'lon': 'flag - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3704/parameters";
    String people_0_affiliation "Western Washington University";
    String people_0_affiliation_acronym "WWU";
    String people_0_person_name "Alejandro Acevedo-Gutierrez";
    String people_0_person_nid "51487";
    String people_0_role "Lead Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "United States Geological Survey";
    String people_1_affiliation_acronym "USGS";
    String people_1_person_name "Jeffrey F Bromaghin";
    String people_1_person_nid "51491";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Washington Department of Fish and Wildlife";
    String people_2_person_name "Steven J Jeffries";
    String people_2_person_nid "51489";
    String people_2_role "Co-Principal Investigator";
    String people_2_role_type "originator";
    String people_3_affiliation "University of Alaska,  Anchorage";
    String people_3_affiliation_acronym "UAA";
    String people_3_person_name "John M Kennish";
    String people_3_person_nid "51490";
    String people_3_role "Co-Principal Investigator";
    String people_3_role_type "originator";
    String people_4_affiliation "Washington Department of Fish and Wildlife";
    String people_4_person_name "Monique  M Lance";
    String people_4_person_nid "51488";
    String people_4_role "Co-Principal Investigator";
    String people_4_role_type "originator";
    String people_5_affiliation "National Marine Fisheries Service";
    String people_5_affiliation_acronym "NMFS";
    String people_5_person_name "Philip S Levin";
    String people_5_person_nid "51492";
    String people_5_role "Co-Principal Investigator";
    String people_5_role_type "originator";
    String people_6_affiliation "Woods Hole Oceanographic Institution";
    String people_6_affiliation_acronym "WHOI BCO-DMO";
    String people_6_person_name "Shannon Rauch";
    String people_6_person_nid "51498";
    String people_6_role "BCO-DMO Data Manager";
    String people_6_role_type "related";
    String project "Seal_response_to_prey";
    String projects_0_acronym "Seal_response_to_prey";
    String projects_0_description 
"From NSF proposal:
This project is a collaborative study of the responses of harbor seals and other mammalian predators to changes in prey density in Puget Sound. The general study approach will involve multi-year field estimates to observe the responses of predators to rockfish density in protected areas, candidate marine reserves, and unprotected sites.
The collaborating investigators will estimate 1) rockfish density using visual and mark and recapture techniques; 2) predator abundance using aerials surveys and dedicated land observations; and 3) predator food consumption using scat to describe diet, tagging of harbor seals to describe individual foraging sites, and population-based and individual bioenergetics models to describe consumption of rockfish. The investigators will also take into account confounding factors that might explain predator behavior, such as environmental variables and alternative prey, by creating a GIS database from available information from the area. The different field observations and database estimates are explicitly linked through a common hypothesis and coordinated methodologies, and their results will be integrated into a model describing the impact of predation on rockfish populations. The responses of top predators to changes in prey density and their impact on fish populations of interest are unknown. This study will evaluate the effectiveness of MPAs as fish refugia, offer a framework for the management and conservation of marine resources, and provide an exciting opportunity for students to participate in ecological and conservation research.
Hypotheses:
1) Harbor seals and other pinniped species show aggregative responses to changes in prey density. Hence, their abundance will increase with fish density.
2) Harbor seals and other pinniped species show Type 2 or 3 functional responses to changes in prey density. Thus, their consumption rate of a particular prey type follows an asymptotic or sigmoidal curve relative to the prey’s density, respectively.
3) Predation by harbor seals and other pinniped species is sufficiently intense that it impedes recovery of depleted fish populations.
Objectives:
1) Quantify the number of harbor seals and other pinniped species in relation to rockfish density and other environmental (confounding) factors.
2) Estimate the consumption rate of harbor seals and other pinniped species in relation to rockfish density and other prey species.
3) Correlatively estimate the influence of predation by harbor seals and other pinniped species on survivorship and population size of rockfish.
Publications resulting from this NSF award:Bjorland, R. H., Pearson, S. F, Jeffries, S. J, Lance, M. M., Acevedo- Gutiérrez, A. & Ward, E. J. 2015. Stable isotope mixing models elucidate sex and size effects on the diet of a generalist marine predator. Marine Ecology Progress Series 526: 213-225. DOI: 10.3354/meps11230Bromaghin, J. F., Lance, M. M., Elliott, E. W., Jeffries, S. J., Acevedo-Gutierrez, A. & Kennish, J. M. 2013. New insights into the diets of harbor seals in the Salish Sea of western North America revealed by quantitative fatty acid signature analysis. Fishery Bulletin 111: 13-26. DOI: 10.7755/FB.111.1.2Buzzell, B.1, Lance, M. & Acevedo-Gutiérrez, A. 2014. Spatial and temporal variation in river otter (Lontra canadensis) diet and predation on rockfish (Genus Sebastes) in the San Juan Islands, Washington. Aquatic Mammals 40: 150- 161. DOI: 10.1578/AM.40.2.2014.150Howard, S., Lance, M., Jeffries, S. & Acevedo-Gutierrez, A. 2013. Fish consumption by harbor seals (Phoca vitulina) in the San Juan Islands, WA. Fishery Bulletin 111: 27-41. DOI: 10.7755/FB.111.1.3Lance, M. M., Chang, W.-Y., Jeffries, S. J., Pearson, S. F. & Acevedo-Gutierrez, A. 2012. Harbor seal diet in northern Puget Sound: implications for the recovery of depressed fish stocks. Marine Ecology Progress Series 464:257-271. DOI:10.3354/meps09880Luxa, K. & Acevedo-Gutierrez, A. 2013. Food habits of harbor seals (Phoca vitulina) in two estuaries in the central Salish Sea. Aquatic Mammals 39: 10- 22. DOI: 10.1578/AM.39.1.2013.10Peterson, S., Lance, M. M., Jeffries, S. J. & Acevedo-Gutierrez, A. 2012. Long distance movements and disjunct spatial use of harbor seals (Phoca vitulina) in the inland waters of the Pacific Northwest. PLoS ONE 7: e39046. DOI: 10.1371/journal.pone.0039046Thomas, AC; Lance, MM; Jeffries, SJ; Miner, BG; Acevedo-Gutierrez, A. 2011. Harbor seal foraging response to a seasonal resource pulse, spawning Pacific herring. Marine Ecology-Progress Series, v.441. p. 225. DOI: 10.3354/meps09370Ward, EJ; Levin, PS; Lance, MM; Jeffries, SJ; Acevedo-Gutierrez, A. 2012. Integrating diet and movement data to identify hot spots of predation risk and areas of conservation concern for endangered species. Conservation Letters, v.5, p. 37. DOI: 10.1111/j.1755-263X.2011.00210.xWilson, K.2, Lance, M., Jeffries, S. & Acevedo-Gutiérrez, A. 2014. Fine-scale variability in harbor seal foraging behavior. PLoS ONE 9: e92838. DOI: 10.1371/journal.pone.0092838.";
    String projects_0_end_date "2012-03";
    String projects_0_geolocation "Salish Sea, USA and Canada";
    String projects_0_name "Responses of Seals and Sea Lions to Increased Rockfish Density";
    String projects_0_project_nid "2205";
    String projects_0_project_website "http://biol.wwu.edu/mbel/?page=research";
    String projects_0_start_date "2006-04";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 8.818;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Coordinates of tagged seals in the San Juan Islands are reported. Seals were captured and tagged during 2007 to 2009 at several sites in Padilla Bay and the Rosario Strait of the Pacific Northwest coast. Seals were tagged with satellite-linked time-depth recorders (TDR's) and GPS receivers.";
    String title "[seal_location_tracking] - Locations of satellite-tagged harbor seals in the San Juan Islands, WA from 2007-2009 (Responses of Seals and Sea Lions to Increased Rockfish Density)";
    String version "1";
    Float64 Westernmost_Easting -175.813;
    String xml_source "osprey2erddap.update_xml() v1.3";
  }
}

 

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