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

ERDDAP > griddap > Make A Graph ?

Dataset Title:  EMODnet Physics - Total Suspended Matter - GridSeriesObservation -
Concentration of total suspended matter - BALTIC SEA
Subscribe RSS
Institution:  CNR   (Dataset ID: TSM_BALTICSEA)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?     specify just 1 value →
    |< -
< <
longitude (degrees_east) ?
    +
    -
< slider >
latitude (degrees_north) ?
    +
    -
< slider >
 
Graph Settings
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0228896e+9, 1.33056e+9;
    String axis "T";
    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";
  }
  longitude {
    UInt32 _ChunkSizes 6635;
    String _CoordinateAxisType "Lon";
    Float32 actual_range 9.999476, 30.85674;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    Float32 valid_max 30.856739;
    Float32 valid_min 9.999476;
  }
  latitude {
    UInt32 _ChunkSizes 3986;
    String _CoordinateAxisType "Lat";
    Float32 actual_range 53.47149, 66.00031;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
    Float32 valid_max 66.00031;
    Float32 valid_min 53.471493;
  }
  conc_tsm_mean {
    String colorBarScale "Log";
    String coordinates "lat lon";
    String long_name "conc_tsm_mean";
  }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.4,hdf5=1.10.6";
    String cdm_data_type "Grid";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 30.85674;
    Float64 geospatial_lat_max 66.00031;
    Float64 geospatial_lat_min 53.47149;
    Float64 geospatial_lat_resolution 0.0031439949811794218;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 30.85674;
    Float64 geospatial_lon_min 9.999476;
    Float64 geospatial_lon_resolution 0.0031439951763641847;
    String geospatial_lon_units "degrees_east";
    String history 
"Thu May 20 18:07:59 2021: ncks -x -v conc_tsm_mean,conc_tsm_sigma,crs,metadata,num_obs,num_passes 2012_03.nc.tmp 2012_03.nc
Thu May 20 18:07:52 2021: ncap2 -s defdim(\"time\",1);time[$time]=0;time@units=\"days since 2012-03-01T00:00:00Z\"; conctsmmean[$time,$lon,$lat]=conc_tsm_mean 2012-03.nc 2012_03.nc.tmp
2024-12-03T12:22:26Z (local files)
2024-12-03T12:22:26Z http://erddap.emodnet-physics.eu/griddap/TSM_BALTICSEA.das";
    String infoUrl "https://map.emodnet-physics.eu/";
    String institution "CNR";
    String keywords "conc_tsm_mean, concentration, data, local, matter, source, suspended, time, total";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    String metadata_profile "beam";
    String metadata_version "0.5";
    String NCO "netCDF Operators version 4.9.3 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 66.00031;
    String product_type "BINNED-L3";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 53.47149;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String start_date "01-MAR-2012 00:00:00.000000";
    String stop_date "30-MAR-2012 00:00:00.000000";
    String summary "EMODnet Physics - Total Suspended Matter - GridSeriesObservation - Concentration of total suspended matter - BALTIC SEA";
    String TileSize "64:64";
    String time_coverage_end "2012-03-01T00:00:00Z";
    String time_coverage_start "2002-06-01T00:00:00Z";
    String title "EMODnet Physics - Total Suspended Matter - GridSeriesObservation - Concentration of total suspended matter - BALTIC SEA";
    Float64 Westernmost_Easting 9.999476;
  }
}

 

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