EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in    
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  **Platforms Position** Subscribe RSS
Institution:  EMODnet Physics   (Dataset ID: EP_INSITU_PLATFORMS_POSITION)
Range: longitude = -3.373075E38 to 3.373074E38°E, latitude = -9999.99 to 119.233°N, time = (?) to 2019-05-24T13:30:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
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 {
    String long_name "EMODnet Platform ID";
    String long_name "EMODnet Platform Type";
    String value_meanings "CT: CTD, DB: Drifting Buoy, FB: FerryBox, GL: Glider, ML: Mini Logger, MM: Marine Mammals, MO: Mooring, TG: Tide Gauge";
    String long_name "EMODnet Platform Code";
    String long_name "EMODnet Platform Link";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range NaN, 1.5587046e+9;
    String axis "T";
    String calendar "Gregorian";
    String ioos_category "Time";
    String long_name "Valid Time GMT";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
    Int16 _FillValue -32767;
    Int16 actual_range 0, 57;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "quality flag";
    String units "1";
    Int16 valid_range 0, 9;
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range -9999.99, 119.233;
    String axis "Y";
    String ioos_category "Location";
    String latitude\.reference_datum "geographical coordinates, WGS84 projection";
    String latitude_reference_datum "geographical coordinates, WGS84 projection";
    String long_name "Latitude";
    Float32 missing_value 9.96921e+36;
    String standard_name "latitude";
    String units "degrees_north";
    Float32 valid_max 90.0;
    Float32 valid_min -90.0;
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range -3.373075e+38, 3.373074e+38;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String longitude\.reference_datum "geographical coordinates, WGS84 projection";
    String longitude_reference_datum "geographical coordinates, WGS84 projection";
    Float32 missing_value 9.96921e+36;
    String standard_name "longitude";
    String units "degrees_east";
    Float32 valid_max 180.0;
    Float32 valid_min -180.0;
    Int16 _FillValue -32767;
    Int16 actual_range 0, 32;
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed not_used nominal_value interpolated_value missing_value";
    String long_name "quality flag";
    String units "1";
    Int16 valid_range 0, 9;
  site_code {
  platform_code {
  platform_name {
  pi_name {
  area {
  author {
  source {
  contributor_name {
  contributor_url {
  data_assembly_center {
  institution_edmo_code {
  institution_references {
  institution {
  wmo_platform_code {
    String cdm_data_type "Other";
    String citation "Data are the property of the producer/owner distributed through EMODnet Physics. EMODnet Physics and the partners are not responsible for improper use";
    String contact "contacts@emodnet-physics.eu";
    String Conventions "CF-1.6 OceanSITES-Manual-1.2 Copernicus-InSituTAC-SRD-1.3 Copernicus-InSituTAC-ParametersList-3.0.0, COARDS, ACDD-1.3";
    String coriolis_platform_code "9901176";
    String creator_email "contacts@emodnet-physics.eu";
    String creator_name "EMODnet Physics";
    String creator_type "institution";
    String creator_url "http://www.emodnet-physics.eu/";
    String data_character_set "utf8";
    String data_language "eng";
    String data_mode "R";
    String data_type "OceanSITES vertical profile";
    String date_update "2019-05-24T05:05:44Z";
    String defaultDataQuery "&time>=now-7day";
    String distribution_statement "Data used in this [type of derived work: e.g. publication/report/model/map…] was made available by the EMODnet Physics project, www.emodnet-physics.eu/map, funded by the European Commission Directorate General for Maritime Affairs and Fisheries. EMODnet Physics and data originators strive to provide access to data with the highest quality available, but the user must be aware that the quality of the different datasets can vary considerably. Users should also take note that all portals are still under development so some features may not be complete and new datasets, parameters and tools are made available regularly. For instance, estimates of data quality are progressively being incorporated along with the datasets, but it is the responsibility of the user to assess the adequacy of those data for his/her particular work purposes: neither EMODnet Physics nor the data originators are liable for any negative consequences following direct or indirect use of EMODnet portal information, services, products and/or data.";
    Float64 Easternmost_Easting 3.373074e+38;
    String family_code "TE";
    String family_label "etc";
    String format_version "1.2";
    Float64 geospatial_lat_max 119.233;
    Float64 geospatial_lat_min -9999.99;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 3.373074e+38;
    Float64 geospatial_lon_min -3.373075e+38;
    String geospatial_lon_units "degrees_east";
    String history 
"2019-05-25T15:36:26Z (local files)
2019-05-25T15:36:26Z http://erddap.emodnet-physics.eu/tabledap/EP_INSITU_PLATFORMS_POSITION.das";
    String infoUrl "http://www.emodnet-physics.eu";
    String institution "EMODnet Physics";
    String keywords "data, earth, Earth Science > Oceans, global, ins, latitude, longitude, natural, ocean, oceans, quality, research, science, sea, seawater, system, time, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String last_date_observation "2019-05-21T13:50:00Z";
    String last_latitude_observation "-59.80000";
    String last_longitude_observation "106.87000";
    String license "These data are public and free of charge. User assumes all risk for use of data. User must display citation in any publication or product using data. User must contact PI prior to any commercial use of data.";
    String metadata_character_set "utf8";
    String metadata_language "eng";
    String naming_authority "OceanSITES";
    String netcdf_version "3.5";
    Float64 Northernmost_Northing 119.233;
    String publisher_email "contacts@emodnet-physics.eu";
    String publisher_name "EMODnet Physics";
    String publisher_type "institution";
    String publisher_url "http://www.emodnet-physics.eu/";
    String qc_manual "OceanSITES User's Manual v1.2";
    String quality_control_indicator "6";
    String quality_index "A";
    String reference_system "EPSG:4326";
    String references "http://marine.copernicus.eu,http://www.coriolis.eu.org";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -9999.99;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Platforms Position. EMODnet Physics data from a local source.";
    String testOutOfDate "now-7days";
    String time_coverage_end "2019-05-24T13:30:00Z";
    String title "**Platforms Position**";
    String update_interval "daily";
    Float64 Westernmost_Easting -3.373075e+38;


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
For example,
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 1.82
Disclaimers | Privacy Policy | Contact