NOAA The NOAA GEO-IDE UAF ERDDAP
Easier access to scientific data
log in | ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Under Development: JSATS California Fish Tracking: Detections table only Subscribe RSS
Institution:  NOAA/NMFS/SWFSC/FED   (Dataset ID: FED_JSATS_detects)
Range: time = 2012-04-18T17:52:05Z to 2023-09-19T13:33:08Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | 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 ? )
    [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 {
  dep_id {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 5562;
    String description "a unique number that identifies a single deployment";
    String ioos_category "Identifier";
    String long_name "Deployment ID";
  }
  fish_id {
    String description "Identifies the fish that was tagged. It is unique in that no two fish have the same FishID. Format is 2 or more letters that describe the type of the fish (e.g. WR for WinterRun), followed by the year (YYYY), followed by a dash, then a sequential three digit number (e.g. 001 to 999)";
    String ioos_category "Identifier";
    String long_name "Fish ID";
  }
  first_time {
    String description "The first detection datetime of the hour-gap detection event. Date-time of the tag transmission when it is recorded by a receiver. This is a string stored as yyyy-mm-dd hh:mm:ss.SSSSSS (e.g. 2016-05-06 23:28:37.585200) to the second and in PST";
    String ioos_category "Time";
    String long_name "First Receiver Detection Time";
    String units "PST";
  }
  last_time {
    String description "The last detection datetime of the hour-gap detection event. Date-time of the tag transmission when it is recorded by a receiver. This is a string stored as yyyy-mm-dd hh:mm:ss.SSSSSS (e.g. 2016-05-06 23:28:37.585200) to the second and in PST";
    String ioos_category "Time";
    String long_name "Last Receiver Detection Time";
    String units "PST";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.334771525e+9, 1.695130388e+9;
    String axis "T";
    String description "UTC time of the tag transmission when it is recorded by a receiver, stored to the micro second.";
    String ioos_category "Time";
    String long_name "First Receiver Detection Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  detection_count {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 935030;
    String description "total number of detection in the hour-gap detection event";
    String ioos_category "Other";
    String long_name "Receiver Detection Count";
  }
  receiver_serial_number {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 2100189;
    String description "the serial number of the acoustic receiver that recorded the detection. If this value is 1, then the record is not a receiver detection but is the release date-time and location. Every tagged fish has at least one record in the table";
    String ioos_category "Identifier";
    String long_name "Receiver Serial Number";
  }
  receiver_river_km {
    Float32 actual_range -73.0, 590.0;
    String description "abbreviation for River Kilometer. This is the river kilometer for a specific receiver LOC. There cannot be duplicate RKMs (i.e. no two LOC with the same RKM). RKM = zero at the Golden Gate Bridge and increases upstream.";
    String ioos_category "Location";
    String long_name "Receiver River Kilometer";
    Float32 missing_value -999.0;
    String units "km";
  }
  study_id {
    String description "Identifies a group of tagged fish that belong to a study. Format is text description of place followed by year (YYYY). A single StudyID can have fish release on multiple days within a year and/or at multiple locations within a year.";
    String ioos_category "Identifier";
    String long_name "Study ID";
  }
  receiver_general_river_km {
    Float32 actual_range -73.0, 590.0;
    String description "River kilometer for the GeneralLocation of a single or group of receivers. Must be unique for each GeneralLocation. The Golden Gate Bridge is rkm 0. Values increase the further upstream.   All the multiple receivers that are within a GeneralLocation will have the same Genrkm.";
    String ioos_category "Location";
    String long_name "General River Kilometer";
    Float32 missing_value -999.0;
    String units "km";
  }
  receiver_location {
    String description "The name for the location of a single receiver";
    String ioos_category "Location";
    String long_name "Receiver Location (GPS name)";
  }
  receiver_general_location {
    String description "A name for the geographic location of one or more receivers.";
    String ioos_category "Location";
    String long_name "General Receiver Location";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "CF-1.6, ACDD-1.3, COARDS, NCCSV-1.1";
    String creator_email "Lynn.Dewitt@noaa.gov";
    String defaultGraphQuery "time,receiver_river_km&time>now-6months&.draw=markers&.marker=5|5&.color=0x000000&.colorBar=|||||";
    String history 
"2024-05-04T00:50:29Z (local files)
2024-05-04T00:50:29Z http://upwell.pfeg.noaa.gov/tabledap/FED_JSATS_detects.das";
    String infoUrl "https://oceanview.pfeg.noaa.gov/CalFishTrack";
    String institution "NOAA/NMFS/SWFSC/FED";
    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 sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "study_id,receiver_general_location";
    String summary "(This dataset contains only Detections data) Detections of acoustically tagged fish within an array of real-time JSAT receivers deployed in the Central Valley CA. A collaboration between NOAA/NMFS/SWFSC/FED/Biophysical Ecology Team, U.S. Bureau of Reclamation, California Department of Fish and Wildlife, U.S. Geological Survey, and Univ. Of California, Davis";
    String time_coverage_end "2023-09-19T13:33:08Z";
    String time_coverage_start "2012-04-18T17:52:05Z";
    String title "Under Development: JSATS California Fish Tracking: Detections table only";
  }
}

 

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://upwell.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://upwell.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.23
Disclaimers | Privacy Policy | Contact