RAISE ERDDAP
Easier access to scientific data
   
Brought to you by    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Lagrangian dispersal around the Portofino promontory Italy for the month of
July 2022
Subscribe RSS
Institution:  CNR-ISMAR   (Dataset ID: cnr-ismar_dispersion_model_portofino_2022)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 time (UTC) ?              2022-07-20T23:00:00Z
 latitude (degrees_north) ?          44.26582070174364    44.362059811128184
  < slider >
 longitude (degrees_east) ?          8.866512270700184    9.275527917323652
  < slider >
 
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";
    Float64 actual_range NaN, 1.658358e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    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";
    Float64 _FillValue NaN;
    Float64 actual_range 44.26582070174364, 44.362059811128184;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value NaN;
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range 8.866512270700184, 9.275527917323652;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value NaN;
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  NC_GLOBAL {
    String acquisition_frequence "hourly";
    String acquisition_methodology "Numerical model";
    String acquisition_mode "delayed";
    String cdm_data_type "Point";
    String contributors_email "marcellogatimu.magaldi@cnr.it";
    String contributors_name "Magaldi, Marcello";
    String contributors_orcid "0000-0002-0742-9673";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "roberta.sciascia@cnr.it";
    String creator_name "Sciascia, Roberta";
    String creator_orcid "0000-0001-5593-2516";
    String creator_type "Institution";
    String data_doi "10.5281/zenodo.18926320";
    String data_format_original "zarr";
    String data_version "1";
    String description "Particle tracking trajectories from Meda locations";
    String documentation "https://s4raise.it/dssmare/warning_zooplankton/, https://s4raise.it/dssmare/distributed_monitoring/, https://raise-spoke3.s4raise.it/project01";
    Float64 Easternmost_Easting 9.275527917323652;
    String featureType "Point";
    Float64 geospatial_lat_max 44.362059811128184;
    Float64 geospatial_lat_min 44.26582070174364;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 9.275527917323652;
    Float64 geospatial_lon_min 8.866512270700184;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-04-03T04:33:53Z (local files)
2026-04-03T04:33:53Z https://erddap.s4raise.it/erddap/tabledap/cnr-ismar_dispersion_model_portofino_2022.html";
    String infoUrl "https://www.raiseliguria.it/spoke-3/";
    String inspire "Oceanographic geographical features";
    String institution "CNR-ISMAR";
    String institution_country "IT";
    String institution_edmo_code "134";
    String keywords "connectivity, dispersal, gelatinous, lagrangian";
    String keywords_vocabulary "GCMD Science Keywords";
    String language "XML";
    String license "CC-BY 4.0";
    String maintainer "ETT S.p.A.";
    String naming_authority "RAISE";
    Float64 Northernmost_Northing 44.362059811128184;
    String owner "CNR-ISMAR";
    String owner_url "https://www.ismar.cnr.it/web-content/";
    String project_code "RAISE";
    String project_id "ECS00000035";
    String project_name "Robotics and AI for Socio-economic Empowerment";
    String project_statement "RAISE: Robotics and AI for Socio-economic Empowerment is an innovation ecosystem funded by the Ministry of University and Research under the National Recovery and Resilience Plan (NRRP, Mission 4, Component 2, Investment 1.5)";
    String project_url "https://www.raiseliguria.it/";
    String publisher "ETT S.p.A.";
    String references "10.5281/zenodo.18926320";
    String source "Numerical model";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.26582070174364;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "During July 2022, a Lagrangian dispersal experiment was carried out around the Portofino Promontory (Italy) to simulate the summer dynamics of gelatinous organism blooms. Virtual particles were released in the coastal circulation field to represent the transport and spreading of these organisms under typical seasonal current conditions. The resulting trajectories highlight how coastal currents can rapidly redistribute biological material along the Portofino coastline, illustrating the potential spatial extent and coastal impact of gelatinous blooms during summer.";
    String theme_eu_data "http://publications.europa.eu/resource/authority/data-theme/ENVI";
    String theme_eurovoc "http://publications.europa.eu/resource/authority/eurovoc/100224";
    String time_coverage_end "2022-07-20T23:00:00Z";
    String time_coverage_resolution "hourly";
    String title "Lagrangian dispersal around the Portofino promontory Italy for the month of July 2022";
    String visibility "public";
    Float64 Westernmost_Easting 8.866512270700184;
  }
}

 

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.25_1
Disclaimers | Privacy Policy | Contact