ERDDAP
Easier access to scientific data
?
log in

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Numerical lagrangian data issued from river sources in Indonesia (2016-2020) -
Coast status
Subscribe RSS
Institution:  IRD   (Dataset ID: coast_status)
Range: time = 2016-03-31T00:00:00Z to 2020-05-30T00:00:00Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
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.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
   
Time range:    |<   -       
[The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  ptc_id {
    UInt32 _FillValue 4294967295;
    UInt32 actual_range 0, 1889840;
    String comment "Unique identifier for the simulated particle";
    String long_name "particle ID";
    String standard_name "ptc_id";
  }
  river_index {
    Int16 _FillValue -1;
    Int16 actual_range 0, 20;
    String comment "particle originating river (see River_names, River_longitude and River_latitude for characteristics)";
    String long_name "Particle River Index";
    String standard_name "river_index";
  }
  d_covered_zone {
    Float32 actual_range 0.0, 6655909.0;
    String comment "diagonal of the rectangle encompassing the zone covered by the particle trajectory";
    String long_name "Diagonal Of The Covered Zone";
    String standard_name "d_covered_zone";
    String units "m";
  }
  ptc_distance {
    Float32 actual_range 0.0, 4.870402e+7;
    String comment "distance covered by the particle";
    String long_name "Particle Trajectory Distance";
    String standard_name "ptc_distance";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.4593824e+9, 1.5907968e+9;
    String axis "T";
    String comment "stranding date of the particles";
    String ioos_category "Time";
    String long_name "Stranding Itime";
    String source_name "stranding_itime";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  stranding_iT {
    Float32 actual_range -1.0, 656.8104;
    String comment "stranding longitude index, in grid-C T coordinate (see lon and lat variables). Indices begin at 0.";
    String long_name "stranding_iT";
    String standard_name "stranding_it";
  }
  stranding_jT {
    Float32 actual_range -1.0, 718.4996;
    String comment "stranding latitude index, in grid-C T coordinate (see lon and lat variables). Indices begin at 0.";
    String long_name "stranding_jT";
    String standard_name "stranding_jt";
  }
  stranding_age {
    Int16 _FillValue 32767;
    Int16 actual_range -1, 1470;
    String comment "if stranding_age == -1, the particle has not stranded, else age of stranding";
    String long_name "Stranding Age";
    String standard_name "stranding_age";
    String units "days";
  }
  stranding_zone {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 230;
    String comment "If stranding_zone == 0, the particle has not stranded, else zone of stranding (see stranding_location_names for a correspondence between the value and the name)";
    String long_name "Stranding Zone";
    String standard_name "stranding_zone";
  }
 }
  NC_GLOBAL {
    String author "Delphine Dobler and Christophe Maes (IRD/LOPS - Plouzane, France)";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String corresponding_email "christophe.maes@ird.fr";
    String description "This file contains time series of simulated particle status with respect to their fate (stranding, out of domain, still at sea)";
    String eps_coast "0.001";
    String eps_coast_comment "eps_coast is expressed in grid cell unit and corresponds to the threshold distance between the particle and the coast below which a particle is considered as stranded.";
    String eps_moving "0.001";
    String eps_moving_comment "(OBSOLETE: not use in the current case) eps_moving is expressed in grid cell unit and corresponds to the threshold distance between 2 consecutive record of the particle trajectory below which the particle is considered unmoving.";
    String history 
"Created Mon Sep 14 16:08:58 2020
2024-04-30T00:36:09Z (local files)
2024-04-30T00:36:09Z https://erddap.ifremer.fr/tabledap/coast_status.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 "age, contains, covered, d_covered_zone, data, diagonal, distance, domain, fate, file, index, itime, out, particle, ptc, ptc_distance, ptc_id, respect, river, river_index, sea, series, simulated, status, still, stranding, stranding_age, stranding_it, stranding_jt, stranding_zone, their, time, time series, trajectory, with, zone";
    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 time series of simulated particle status with respect to their fate (stranding, out of domain, still at sea)";
    String time_coverage_end "2020-05-30T00:00:00Z";
    String time_coverage_start "2016-03-31T00:00:00Z";
    String title "Numerical lagrangian data issued from river sources in Indonesia (2016-2020) - Coast status";
  }
}

 

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