EMODnet   ERDDAP server @ EMODnet
    Easier access to scientific data
?    
Brought to you by EMODnet    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Presence/Absence maps of phytoplankton in the Greater Baltic Sea Subscribe RSS
Institution:  SMHI   (Dataset ID: biology_6618_table_8b1e_5c90_9a2c)
Range: longitude = 9.093333 to 36.906666°E, latitude = 52.028572 to 67.97143°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | 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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
[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 {
  aphiaid {
    Int32 _FillValue 2147483647;
    Int32 actual_range 802, 1380043;
    String long_name "Life Science Identifier - World Register of Marine Species";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 52.028571428571425, 67.97142857142858;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 9.093333333333334, 36.906666666666666;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  probability_occurrence {
    Float64 _FillValue -99999.9;
    Float64 actual_range 0.0, 1.0;
    String long_name "Probability of occurrence of biological entity";
    Float64 missing_value -99999.9;
  }
 }
  NC_GLOBAL {
    String acknowledgement "European Marine Observation Data Network (EMODnet) Biology project (EASME/EMFF/2017/1.3.1.2/02/SI2.789013), funded by the European Union under Regulation (EU) No 508/2014 of the European Parliament and of the Council of 15 May 2014 on the European Maritime and Fisheries Fund";
    String cdm_data_type "Other";
    String citation "Daniela Figueroa, Markus Lindh, Luuk van der Heijden, Willem Stolte & Lisa Sundqvist (2020). Presence/Absence maps of phytoplankton in the Greater Baltic Sea.";
    String comment "Uses attributes recommended by https://cfconventions.org";
    String Conventions "CF-1.8, COARDS, ACDD-1.3";
    String creator_email "daniela.figueroa@smhi.se";
    String creator_institution "Swedish Meteorological and Hydrological Institute (SMHI)";
    String creator_name "Figueroa Daniela";
    String creator_type "person";
    String creator_url "www.smhi.se";
    String date_created "2022-08-10";
    String date_issued "2020-12-24";
    String date_metadata_modified "2021-03-08";
    String date_modified "2021-03-08";
    Float64 Easternmost_Easting 36.906666666666666;
    Float64 geospatial_lat_max 67.97142857142858;
    Float64 geospatial_lat_min 52.028571428571425;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 36.906666666666666;
    Float64 geospatial_lon_min 9.093333333333334;
    String geospatial_lon_units "degrees_east";
    String grid_mapping_geographic_crs_name "WGS 84";
    String grid_mapping_GeoTransform "-180 0.08333333333333333 0 90 0 -0.08333333333333333";
    Float64 grid_mapping_inverse_flattening 298.257223563;
    String grid_mapping_long_name "Coordinate Reference System";
    Float64 grid_mapping_longitude_of_prime_meridian 0.0;
    String grid_mapping_name "latitude_longitude";
    String grid_mapping_prime_meridian_name "Greenwich";
    String grid_mapping_reference_ellipsoid_name "WGS 84";
    Float64 grid_mapping_semi_major_axis 6378137.0;
    Float64 grid_mapping_semi_minor_axis 6356752.314245179;
    String grid_mapping_spatial_ref "GEOGCS[\"WGS 84\",DATUM[\"WGS_1984\",SPHEROID[\"WGS 84\",6378137,298.257223563]],PRIMEM[\"Greenwich\",0],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AXIS[\"Latitude\",NORTH],AXIS[\"Longitude\",EAST],AUTHORITY[\"EPSG\",\"4326\"]]";
    String history 
"https://github.com/EMODnet/EMODnet-Biology-Phytoplankton-Greater-BalticSea
2023-12-01T12:39:54Z (local files)
2023-12-01T12:39:54Z https://erddap.emodnet.eu/tabledap/biology_6618_table_8b1e_5c90_9a2c.das";
    String infoUrl "https://www.emodnet-biology.eu/data-catalog?module=dataset&dasid=6618";
    String institution "SMHI";
    String keywords "absence, aphiaid, baltic, baltic sea, biological, data, entity, greater, hydrological, identifier, institute, latitude, life, longitude, maps, marine, marine/coastal, meteorological, occurrence, phytoplankton, presence, presence/absence, probability, probability_occurrence, register, science, sea, smhi, species, swedish, world";
    String license "CC-BY";
    String metadata_link "https://www.emodnet-biology.eu/data-catalog?module=dataset&dasid=6618";
    String naming_authority "emodnet-biology.eu";
    Float64 Northernmost_Northing 67.97142857142858;
    String product_version "1";
    String project "EMODnet-Biology";
    String publisher_email "bio@emodnet.eu";
    String publisher_institution "Flanders Marine Institute (VLIZ)";
    String publisher_name "EMODnet Biology Data Management Team";
    String publisher_type "group";
    String publisher_url "www.emodnet-biology.eu";
    String references "https://www.emodnet-biology.eu/blog/presenceabsence-maps-phytoplankton-greater-baltic-sea";
    String sea_name "Baltic Sea";
    String source "https://github.com/EMODnet/EMODnet-Biology-Phytoplankton-Greater-BalticSea";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 52.028571428571425;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "The project aims to produce comprehensive data product of the occurence and absence of (phyto)plankton species. As a basis, data from EMODnet Biology are used. The selection of relevant datasets is optimized in order to find all planktonic species, and exclude all species that are not planktonic. The occurences from EMODnet Biology were complemenented with absence data assuming fixed species lists within each dataset and year. The products are presented as maps of the distribution of the 20 most common species of (phyto)plankton in the Greater Baltic Sea.";
    String title "Presence/Absence maps of phytoplankton in the Greater Baltic Sea";
    Float64 Westernmost_Easting 9.093333333333334;
  }
}

 

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