Data Access Form

Dataset Title:	Bantry Bay model particle track analysis
Institution:	Irish Marine Institute (Dataset ID: BANTRY_PARTICLES)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| 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)	31	1 day 0h 48m 0s (uneven)

release_location (count)	6	1.0 (even)

latitude (degrees_north)	420	0.001809524 (even)

longitude (degrees_east)	520	0.002903846 (even)

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

particle_hours (particle transport probability, hours)

File type: (more info)

(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.7321472e+9, 1.7348256e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "time since initialization, 2000-1-1";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  release_location {
    Int16 actual_range 0, 5;
    String ioos_category "Unknown";
    String units "count";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 51.140912310003, 51.899102770785255;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -10.848548076923, -9.3414519231008;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  particle_hours {
    Float64 _FillValue -999.0;
    String colorBarMaximum "200";
    String colorBarMinimum "0";
    String colorBarPalette "KT_turbid";
    String coordinates "release latitude longitude";
    String ioos_category "Statistics";
    String long_name "particle transport probability";
    Float64 missing_value -999.0;
    String standard_name "particle_hours";
    String units "hours";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    Float64 Easternmost_Easting -9.3414519231008;
    Float64 geospatial_lat_max 51.899102770785255;
    Float64 geospatial_lat_min 51.140912310003;
    Float64 geospatial_lat_resolution 0.0018095237727500054;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -9.3414519231008;
    Float64 geospatial_lon_min -10.848548076923;
    Float64 geospatial_lon_resolution 0.0029038461538;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-22T06:43:32Z http://milas.marine.ie/thredds/dodsC/BANTRY_PARTICLES/PARTICLE_TRACKS
2024-12-22T06:43:32Z http://erddap.digitalocean.ie/erddap/griddap/BANTRY_PARTICLES.das";
    String infoUrl "http://milas.marine.ie/thredds/";
    String institution "Irish Marine Institute";
    String license "Creative Commons Attribution 4.0 (https://creativecommons.org/licenses/by/4.0/)";
    Float64 Northernmost_Northing 51.899102770785255;
    String sourceUrl "http://milas.marine.ie/thredds/dodsC/BANTRY_PARTICLES/PARTICLE_TRACKS";
    Float64 Southernmost_Northing 51.140912310003;
    String summary "Aggregate model particle track data";
    String time_coverage_end "2024-12-22T00:00:00Z";
    String time_coverage_start "2024-11-21T00:00:00Z";
    String title "Bantry Bay model particle track analysis";
    Float64 Westernmost_Easting -10.848548076923;
  }
}

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.