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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  CVTEMP: Meteorology Inputs Subscribe RSS
Institution:  NOAA/SWFSC Fisheries Ecology Division   (Dataset ID: cvtempMetInput)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 time (Time (PST), UTC) ?              
 latitude (degrees_north) ?          40.6009    40.6009
  < slider >
 longitude (degrees_east) ?          -122.4445    -122.4445
  < slider >
 SimulationStartTime (Time of simulation) ?      
   - +  ?
 ScenarioName (Name of scenario) ?      
   - +  ?
 ModelType (Name of Model) ?      
   - +  ?
 Air_Temperature_Inputs (Deg F) ?          24.30466    112.5595
 Relative_Humidity_Inputs (Percent) ?          4.005292    100.0
 Solar_Radiation_Inputs (Watt per square foot) ?          0.0    91.12366
 Wind_Speed_Inputs (Miles per hour) ?          0.3415333    38.3241
 Cloud_Cover_Inputs (Fraction sky) ?          0.0    2.23694
 Year (Years) ?          2003.0    2022.0
 
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 {
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Time (PST)";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 40.6009, 40.6009;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -122.4445, -122.4445;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  SimulationStartTime {
    String ioos_category "Time";
    String long_name "Time of simulation";
  }
  ScenarioName {
    String ioos_category "Identifier";
    String long_name "Name of scenario";
  }
  ModelType {
    String ioos_category "Identifier";
    String long_name "Name of Model";
  }
  Air_Temperature_Inputs {
    Float32 actual_range 24.30466, 112.5595;
    String ioos_category "Temperature";
    String long_name "Model input for air temperature";
    String units "Deg F";
  }
  Relative_Humidity_Inputs {
    Float32 actual_range 4.005292, 100.0;
    String ioos_category "Meteorology";
    String long_name "Model input for relative humidity";
    String units "Percent";
  }
  Solar_Radiation_Inputs {
    Float32 actual_range 0.0, 91.12366;
    String ioos_category "Heat Flux";
    String long_name "Model input for solar radiation";
    String units "Watt per square foot";
  }
  Wind_Speed_Inputs {
    Float32 actual_range 0.3415333, 38.3241;
    String ioos_category "Wind";
    String long_name "Model input for wind speed";
    String units "Miles per hour";
  }
  Cloud_Cover_Inputs {
    Float32 actual_range 0.0, 2.23694;
    String ioos_category "Temperature";
    String long_name "Model input for air temperature";
    String units "Fraction sky";
  }
  Year {
    Float32 actual_range 2003.0, 2022.0;
    String ioos_category "Time";
    String long_name "Year of historical meteorological data for forecast";
    String units "Years";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "CF-1.6, ACDD-1.3, COARDS, NCCSV-1.1";
    String CreationTime "2023-11-28 03:20:24";
    String creator_email "Lynn.Dewitt@noaa.gov";
    String defaultGraphQuery "time%2CAir_Temperature_Inputs&ModelType=%22USBR_NO_W2%22&ScenarioName=%22APR_22_2018_INPUT_90_OUTPUT_90_10L3MTO%22&.draw=lines";
    Float64 Easternmost_Easting -122.4445;
    Float64 geospatial_lat_max 40.6009;
    Float64 geospatial_lat_min 40.6009;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -122.4445;
    Float64 geospatial_lon_min -122.4445;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-27T10:04:05Z (local files)
2024-04-27T10:04:05Z http://upwell.pfeg.noaa.gov/erddap/tabledap/cvtempMetInput.html";
    String infoUrl "https://oceanview.pfeg.noaa.gov/CVTEMP";
    String institution "NOAA/SWFSC Fisheries Ecology Division";
    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.";
    Float64 Northernmost_Northing 40.6009;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.6009;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "SimulationStartTime,ScenarioName,ModelType";
    String summary "The River Assessment for Forecasting Temperature (RAFT) model is a one-dimensional heat budget model for the Sacramento River. RAFT takes the discharge temperature and flow from Keswick Dam and applies meteorological forcings from weather forecasts and historical conditions to predict the downstream temperatures for every two-kilometers of river at a sub-hourly timestep. RAFT has been run retrospectively to produce the temperature landscape for the entire river from 1990-2016. RAFT can be run in forecast mode for operations, where it predicts water temperatures 7 days out. RAFT can also be run in planning mode, where it takes output from various planning scenarios and predicts water temperatures for the entire temperature management season (February through October). One of the primary advantages of the RAFT model is that it allows for the detailed estimating of thermal exposure of salmon redds by location - which allows for calculating the egg development time and survival probability (see Survival tab). The RAFT model was developed with funding from NASA Applied Sciences and the details of the RAFT model are described in Pike et al. 2013";
    String title "CVTEMP: Meteorology Inputs";
    Float64 Westernmost_Easting -122.4445;
  }
}

 

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