BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [ALFA data - Indonesian Through Flow Region] - Advanced Laser Fluorescence
Analyzer (ALFA) data from the Indonesian Through Flow Region from the R/V Roger
Ravelle (RR2201) from January to March 2022 (Collaborative Research: Mesoscale
variability in nitrogen sources and food-web dynamics supporting larval
southern bluefin tuna in the eastern Indian Ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_944302_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 cruise_ID (unitless) ?          "BLOOFINZ_2022"    "BLOOFINZ_2022"
 Date (unitless) ?          "2022-01-26"    "2022-03-11"
 TIME_UTC (unitless) ?          "00:00:00"    "23:59:59"
 time (Iso_datetime_utc, UTC) ?              
 latitude (degrees_north) ?          -17.18643    6.599072
  < slider >
 longitude (degrees_east) ?          113.911    136.5437
  < slider >
 CDOM (rfu) ?          0.0    18288.4
 Chl_a (mg m-3) ?          0.0    33.16278
 Fv_Fm (unitless) ?          2.3E-4    5770.185
 PE_1 (rfu) ?          0.0    174543.0
 PE_2 (rfu) ?          0.0    63818.64
 PE_3 (rfu) ?          0.0    300838.8
 
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 {
  cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  TIME_UTC {
    String long_name "Time_utc";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    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 -17.18643, 6.599072;
    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 113.911, 136.5437;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  CDOM {
    Float32 actual_range 0.0, 18288.4;
    String long_name "Cdom";
    String units "rfu";
  }
  Chl_a {
    Float32 actual_range 0.0, 33.16278;
    String long_name "Chl_a";
    String units "mg m-3";
  }
  Fv_Fm {
    Float32 actual_range 2.3e-4, 5770.185;
    String long_name "Fv_fm";
    String units "unitless";
  }
  PE_1 {
    Float32 actual_range 0.0, 174543.0;
    String long_name "Pe_1";
    String units "rfu";
  }
  PE_2 {
    Float32 actual_range 0.0, 63818.64;
    String long_name "Pe_2";
    String units "rfu";
  }
  PE_3 {
    Float32 actual_range 0.0, 300838.8;
    String long_name "Pe_3";
    String units "rfu";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.944302.1";
    Float64 Easternmost_Easting 136.5437;
    Float64 geospatial_lat_max 6.599072;
    Float64 geospatial_lat_min -17.18643;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 136.5437;
    Float64 geospatial_lon_min 113.911;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-10-07T22:39:02Z (local files)
2025-10-07T22:39:02Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_944302_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/944302";
    String institution "BCO-DMO";
    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 6.599072;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -17.18643;
    String summary "The  Automatic Laser Fluorometric Analyzer (ALFA)  is a state-of-the-art instrument, that combines high-resolution spectral measurements of blue (405 nm) and green (532 nm) laser-stimulated fluorescence, with spectral deconvolution techniques to estimate CDOM, phytoplankton variable fluorescence (Fv/Fm), Chl a and three types of phycobiliprotein pigments. This data was collected using the ALFA in Underway fluorescence mode and sampling in the western Eastern Indian Ocean Upwelling region on the R/V Roger Ravelle in January - March 2022 (BLOOFINZ). In underway mode, the ALF is connected to the ship's uncontaminated seawater flow-through system allowing for continuous measurements in water drawn from approximately 5m below the surface. All fluorescence values are Raman-normalized, with the exception of Chl a, which was calibrated with acetone extracted samples measured in a Turner Designs® Trilogy Fluorometer. The instrument is set up to make these measurements approx. every minute. See RR2201 cruise report in related publications.";
    String title "[ALFA data - Indonesian Through Flow Region] - Advanced Laser Fluorescence Analyzer (ALFA) data from the Indonesian Through Flow Region from the R/V Roger Ravelle (RR2201) from January to March 2022 (Collaborative Research: Mesoscale variability in nitrogen sources and food-web dynamics supporting larval southern bluefin tuna in the eastern Indian Ocean)";
    Float64 Westernmost_Easting 113.911;
  }
}

 

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