Make A Graph

Dataset Title:	NCOM Southern CA Regional Forecast (3km)
Institution:	Fleet Numerical Meteorology and Oceanography Center (Dataset ID: NCOM_SOCAL)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Show advanced settings : Privacy / Content settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Internet Explorer: "Tools : Internet Options : Security : Internet : Custom level :
          Sripting/ Active Scripting : Enable : OK : OK"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:
X Axis:
Y Axis:
Color:

Dimensions

Start

Stop

time (UTC)

specify just 1 value →

depth (m)

specify just 1 value →

latitude (degrees_north)

longitude (degrees_east)

Graph Settings
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.3762656e+9, 1.5496704e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    Int32 NAVO_code 13;
    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";
    Float64 actual_range 0.0, 5000.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    Int32 NAVO_code 5;
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 25.0, 40.098487854003906;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Int32 NAVO_code 1;
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_range 25.0, 40.09849166870117;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 235.0, 249.0985870361328;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    Int32 NAVO_code 2;
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_range 235.0, 249.0985870361328;
  }
  water_u {
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String ioos_category "Currents";
    String long_name "Zonal Current";
    Int32 NAVO_code 17;
    String standard_name "eastward_sea_water_velocity";
    String units "m.s-1";
  }
  water_v {
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String ioos_category "Currents";
    String long_name "Meridional Current";
    Int32 NAVO_code 18;
    String standard_name "northward_sea_water_velocity";
    String units "m.s-1";
  }
  water_temp {
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Water Temperature";
    Int32 NAVO_code 15;
    String standard_name "sea_water_temperature";
    String units "degree_Celsius";
  }
  salinity {
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Salinity";
    Int32 NAVO_code 16;
    String standard_name "sea_water_salinity";
    String units "1e-3";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.DefaultConvention";
    String cdm_data_type "Grid";
    String classification_authority "not applicable";
    String classified_by "not applicable";
    String comment "The date of issue or publication given below refers to the date on which the NCOM global model was made operational.";
    String contact "FNMOC, N5";
    String Conventions "NAVO_netcdf_v1.0, COARDS, CF-1.6, Unidata Dataset Discovery v1.0";
    String creator_email "ncom_webmaster@nrlssc.navy.mil";
    String creator_name "Naval Research Lab (NRL)";
    String creator_url "https://www.ncdc.noaa.gov/data-access/model-data/model-datasets/navoceano-ncom-glbglb8_3b/html/index.html";
    String date_issued "2006-02-19";
    String derived_from "not applicable";
    String distribution_statement "Approved for public release; distribution is unlimited.";
    String downgrade_date "not applicable";
    Float64 Easternmost_Easting 249.0985870361328;
    String generating_model "NCOM_4.3";
    Float64 geospatial_lat_max 40.098487854003906;
    Float64 geospatial_lat_min 25.0;
    Float64 geospatial_lat_resolution 0.03332999526270178;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 249.0985870361328;
    Float64 geospatial_lon_min 235.0;
    Float64 geospatial_lon_resolution 0.03332999299322178;
    String geospatial_lon_units "degrees_east";
    String history 
"not applicable
2019-11-18T09:58:27Z (local files)
2019-11-18T09:58:27Z http://erddap.axiomdatascience.com/griddap/NCOM_SOCAL.das";
    String infoUrl "https://www.ncdc.noaa.gov/data-access/model-data/model-datasets/navoceano-ncom-glbglb8_3b/html/index.html";
    String initial_time "2000010100";
    String input_data_source "not_applicable";
    String institution "Fleet Numerical Meteorology and Oceanography Center";
    String keywords "3km, circulation, coastal, current, currents, density, Earth Science > Oceans > Ocean Circulation > Ocean Currents, Earth Science > Oceans > Ocean Pressure > Sea Level Pressure, Earth Science > Oceans > Ocean Temperature > Sea Surface Temperature, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Salinity, eastward, eastward_sea_water_velocity, forecast, laboratory, level, meridional, model, naval, navy, navy coastal ocean model, ncom, northward, northward_sea_water_velocity, ocean, oceans, pressure, regional, research, salinity, sea, sea_water_salinity, sea_water_temperature, seawater, southern, surface, temperature, velocity, water, zonal";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "The source code and results of this model are in the public domain and may be used without charge for any lawful purpose so long as you do not: 1) claim it is your own (e.g., by claiming copyright for NWS information), 2) use it in a manner that implies an endorsement or affiliation with NOAA/NWS, or 3) modify its content and then present it as official government material. You also cannot present information of your own in a way that makes it appear to be official government information. (License information taken from https://www.weather.gov/disclaimer)";
    String Metadata_Conventions "NAVO_netcdf_v1.0, COARDS, CF-1.6, Unidata Dataset Discovery v1.0";
    String metadata_link "http://www.opc.ncep.noaa.gov/newNCOM/NCOM_currents.shtml";
    Float64 Northernmost_Northing 40.098487854003906;
    String operational_status "operational";
    String publisher_email "ncep.list.opc_web@noaa.gov";
    String publisher_name "National Weather Service Ocean Prediction Center";
    String publisher_url "http://www.opc.ncep.noaa.gov/newNCOM/NCOM_currents.shtml";
    String releasable_to "not applicable";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 25.0;
    String standard_name_vocabulary "CF Standard Names Vocabulary V27";
    String summary "The Regional NCOM models have a resolution of 1/36 deg. (3 km). The U.S. Navy Operational Global Ocean Model (NCOM), developed by the Naval Research Laboratory and maintained by the Naval Oceanographic Office, provides boundary conditions for the regional models. The Navy Coupled Ocean Data Assimilation System (NCODA) provides the data assimilation for NCOM including SSH, SST, and in situ observations. For more information about NCOM see:  http://www.opc.ncep.noaa.gov/newNCOM/NCOM_currents.shtml https://www.nrl.navy.mil/research/nrl-review/2003/ocean-science/barron/";
    String time_coverage_end "2019-02-09T00:00:00Z";
    String time_coverage_start "2013-08-12T00:00:00Z";
    String time_origin "2019-01-16 00:00:00";
    String title "NCOM Southern CA Regional Forecast (3km)";
    Float64 Westernmost_Easting 235.0;
  }
}

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its projection 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. It makes 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.