ERDDAP
Easier access to scientific data
?
log in

ERDDAP > griddap > Data Access Form ?

Dataset Title:  Numerical lagrangian data issued from river sources in Indonesia (2016-2020) -
Traj lonlat init t0
Subscribe RSS
Institution:  IRD   (Dataset ID: traj_lonlat_init_t0)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Dimensions ? Start ? Stride ? Stop ?  Size ?    Spacing ?
 frame (count) ?      1522    1.0 (even)
  < slider >
 ntraj (count) ?      1889841    1.0 (even)
  < slider >
 
Grid Variables (which always also download all of the dimension variables) 
 traj_lon_init_t0 (Longitude of trajectory vs time since simu t0, degrees_east) ?
 traj_lat_init_t0 (Latitude of trajectory vs time since simu t0, degrees_north) ?
 traj_iU_init_t0 (longitude index of trajectory vs time since simu t0) ?
 traj_jV_init_t0 (latitude index of trajectory vs time since simu t0) ?

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 {
  frame {
    Int32 actual_range 0, 1521;
    String long_name "Frame";
    String units "count";
  }
  ntraj {
    Int32 actual_range 0, 1889840;
    String long_name "Ntraj";
    String units "count";
  }
  traj_lon_init_t0 {
    Float32 _FillValue 9.96921e+36;
    String cf_role "trajectory_id";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    Float64 least_significant_digit 4;
    String long_name "Longitude of trajectory vs time since simu t0";
    String standard_name "longitude";
    String units "degrees_east";
  }
  traj_lat_init_t0 {
    Float32 _FillValue 9.96921e+36;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    Float64 least_significant_digit 4;
    String long_name "Latitude of trajectory vs time since simu t0";
    String standard_name "latitude";
    String units "degrees_north";
  }
  traj_iU_init_t0 {
    Float32 _FillValue 9.96921e+36;
    Float64 least_significant_digit 4;
    String long_name "longitude index of trajectory vs time since simu t0";
    String standard_name "longitude index in model u-grid";
  }
  traj_jV_init_t0 {
    Float32 _FillValue 9.96921e+36;
    Float64 least_significant_digit 4;
    String long_name "latitude index of trajectory vs time since simu t0";
    String standard_name "latitude index in model v-grid";
  }
  NC_GLOBAL {
    String author "Delphine Dobler and Christophe Maes (IRD/LOPS - Plouzane, France)";
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "traj_lon_init_t0,traj_lat_init_t0";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String corresponding_email "christophe.maes@ird.fr";
    String description "This file contains trajectories of simulated particles in grid indices and lat/lon coordinates. The position remains unchanged once the particle is considered as stranded.";
    String featureType "Trajectory";
    String history 
"Created Mon Sep 14 16:10:00 2020
2024-06-22T14:00:52Z (local files)
2024-06-22T14:00:52Z https://erddap.ifremer.fr/erddap/griddap/traj_lonlat_init_t0.das";
    String how_to_cite "Dobler D., Martinez E., Rahmania R., Gautama B.G., Farhan A.R., Maes C. 2021. Floating marine debris along Indonesian coasts. An atlas of strandings based on Lagrangian modelling. \"Monitoring and modelling the circulation of marine debris in Indonesia\" project funded by AFD. Jakarta: IRD, 92 p";
    String infoUrl "https://doi.org/10.12770/8dea4c5c-f2c2-4771-9372-9ce60c878c49";
    String institution "IRD";
    String keywords "considered, contains, coordinates, data, file, frame, grid, index, indices, latitude, latitude index in model v-grid, longitude, longitude index in model u-grid, model, ntraj, once, particle, particles, position, remains, simu, simulated, since, time, traj_iU_init_t0, traj_jV_init_t0, traj_lat_init_t0, traj_lon_init_t0, trajectories, trajectory, u-grid, unchanged, v-grid";
    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.";
    String reference_test "test21_2016_2020_uo_utide_ustokes_ptc_scenario4_1d";
    String source "netCDF4 python module";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "This file contains trajectories of simulated particles in grid indices and lat/lon coordinates. The position remains unchanged once the particle is considered as stranded.";
    String title "Numerical lagrangian data issued from river sources in Indonesia (2016-2020) - Traj lonlat init t0";
  }
}

 

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.

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.


 
ERDDAP, Version 2.18
Disclaimers | Privacy Policy | Contact