Data Access Form

Dataset Title:	Gap-filled suface currents in the south-eastern Bay of Biscay by AZTI
Institution:	AZTI (Spain) (Dataset ID: 2DVAR_2021_EMODNET)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Files \| Make a graph

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.

Dimensions	Size	Spacing
time (UTC)	6654	1h 12m 25s (uneven)

latitude (degrees_north)	35	0.02250265 (even)

longitude (degrees_east)	55	0.03080972 (even)

Grid Variables (which always also download all of the dimension variables)

NSCT (North-south current component, m s-1)

EWCT (West-east current component, m s-1)

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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6097472e+9, 1.6386516e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    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 43.3, 44.06509;
    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 -3.0, -1.336275;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  NSCT {
    String long_name "North-south current component";
    String standard_name "northward_sea_water_velocity";
    String units "m s-1";
  }
  EWCT {
    String long_name "West-east current component";
    String standard_name "eastward_sea_water_velocity";
    String units "m s-1";
  }
  NC_GLOBAL {
    String acknowledgement "These data were processed by AZTI and made freely available";
    String area "South-Eastern Bay of Biscay";
    String cdm_data_type "Grid";
    String citation "These data were processed by ULCO & AZTI and made freely available";
    String comment "Gap-filled 2DVAR surface currents";
    String contact_email "lsolabarrieta@azti.es, arubio@azti.es, alexei.sentchev@univ-littoral.fr, sloane.bertin@univ-littoral.fr";
    String contact_name "Lohitzune Solabarrieta, Anna Rubio, Alexei Sentchev, Sloane Bertin";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "lsolabarrieta@azti.es, arubio@azti.es, alexei.sentchev@univ-littoral.fr, sloane.bertin@univ-littoral.fr";
    String creator_name "Lohitzune Solabarrieta, Anna Rubio, Alexei Sentchev, Sloane Bertin";
    String creator_type "person";
    String creator_url "https://www.azti.es/, https://www.univ-littoral.fr/";
    String data_assembly_center "AZTI";
    String data_language "eng";
    String data_mode "D";
    String data_type "Gap-fille surface currents from HFR-EUSKOOS";
    String date_update "0071-12-03 21:00";
    String distribution_statement "These data are public and free of charge. User assumes all risk for use of data. User must display citation in any publication or product using data. User must contact PI prior to any commercial use of data";
    Float64 Easternmost_Easting -1.336275;
    String format_version "1.4";
    Float64 geospatial_lat_max 44.06509;
    Float64 geospatial_lat_min 43.3;
    Float64 geospatial_lat_resolution 0.02250264705882355;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -1.336275;
    Float64 geospatial_lon_min -3.0;
    Float64 geospatial_lon_resolution 0.03080972222222222;
    String geospatial_lon_units "degrees_east";
    String history 
"Mon Oct 30 12:27:52 2023: ncpdq -a EWCT,o,c,TIME,Longitude,Latitude  HFR-EUSKOOS-2DVAR_2021_12_04_2100.nc HFR-EUSKOOS_2DVAR_2021_12_04_2100.nc
2024-12-21T12:31:44Z (local files)
2024-12-21T12:31:44Z http://erddap.emodnet-physics.eu/erddap/griddap/2DVAR_2021_EMODNET.das";
    String infoUrl "https://www.azti.es/, https://www.univ-littoral.fr/";
    String institution "AZTI (Spain)";
    String institution_edmo_code "1623";
    String institution_references "AZTI";
    String keywords "azti, bay, biscay, circulation, component, current, currents, data, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, east, eastern, eastward, eastward_sea_water_velocity, EWCT, filled, frequency, gap, gap-filled, HF, hf radar, hfr, hfradar, high, latitude, longitude, north, north-south, northward, northward_sea_water_velocity, NSCT, ocean, oceans, radar, science, sea, seawater, south, south-eastern, spain, suface, time, velocity, water, west, west-east";
    String keywords_vocabulary "GCMD Science Keywords";
    String last_update "2023-08-17 17:34";
    String license "this dataset is licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this work. If not, see https://creativecommons.org/licenses/by/4.0/";
    String metadata_language "eng";
    String naming_authority "AZTI";
    String NCO "4.7.2";
    Int32 nco_openmp_thread_number 1;
    String NetCDF_format "netcdf4_classic";
    String NetCDF_version "netCDF-4 classic model";
    Float64 Northernmost_Northing 44.06509;
    String publisher_email "lsolabarrieta@azti.es, arubio@azti.es";
    String publisher_name "Lohitzune Solabarrieta, Anna Rubio";
    String publisher_type "institution";
    String publisher_url "www.azti.es";
    String references "2DVAR method is described in M. Yaremchuk, A. Sentchev, 2009. Mapping radar-derived sea surface currents with a variational method. Continent. Shelf Res., 29 (14) (2009), pp. 1711-1722, 10.1016/j.csr.2009.05.016; Please use the contact_email for more information on the parameter’s settings and the accuracy of the distributed datasets ";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.3;
    String Standard_name_vocabulary "NetCDF Climate and Forecast Metadata Convention Standard Name Table Version 1.6; and https://www.seadatanet.org/Standards/Common-Vocabularies. ISO 19115, related to the geographical information";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "2DVAR gap filled currents derived from High Frequency Radar (HFR) - EUSKOOS";
    String time_coverage_end "2021-12-04T21:00:00Z";
    String time_coverage_start "2021-01-04T08:00:00Z";
    String title "Gap-filled suface currents in the south-eastern Bay of Biscay by AZTI";
    String update_interval "void";
    Float64 Westernmost_Easting -3.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.