Italian Arctic Data Center ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	GVB Sulphate apportionment in PM10
Institution:	University of Florence (Dataset ID: traversi_nya_gvb_pm10_so4)
Range:	longitude = 11.86587 to 11.86587°E, latitude = 78.92136 to 78.92136°N
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  station_id {
    String actual_range 
"Gruvebadet
Gruvebadet";
    String cf_role "timeseries_id";
    String long_name "Id of the station in the TimeSeries";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 78.92136, 78.92136;
    String axis "Y";
    String ioos_category "Location";
    String long_name "latitude position of the station";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 11.86587, 11.86587;
    String axis "X";
    String ioos_category "Location";
    String long_name "longitude position of the station";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    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";
  }
  Actual_sampling_volume {
    String long_name "Actual Sampling Volume";
    String units "m3";
  }
  sea_salt {
    String long_name "Sea Salt";
    String standard_name "mass_concentration_of_sulfate_ambient_aerosol_particles_in_air";
    String units "ng m-3";
  }
  crustal {
    String long_name "Crustal";
    String standard_name "mass_concentration_of_sulfate_ambient_aerosol_particles_in_air";
    String units "ng m-3";
  }
  biogenic {
    String long_name "Biogenic";
    String standard_name "mass_concentration_of_sulfate_ambient_aerosol_particles_in_air";
    String units "ng m-3";
  }
  anthropic {
    String long_name "Anthropic";
    String standard_name "mass_concentration_of_sulfate_ambient_aerosol_particles_in_air";
    String units "ng m-3";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id, longitude, latitude";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_name "Rita Traversi";
    String creator_type "person";
    Float64 Easternmost_Easting 11.86587;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 78.92136;
    Float64 geospatial_lat_min 78.92136;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 11.86587;
    Float64 geospatial_lon_min 11.86587;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-29T14:00:05Z (local files)
2024-04-29T14:00:05Z https://data.iadc.cnr.it/tabledap/traversi_nya_gvb_pm10_so4.das";
    String infoUrl "https://metadata.iadc.cnr.it/geonetwork/srv/eng/catalog.search#/metadata/a72d871b-01f0-4b20-993d-d6855eefb0d6";
    String institution "University of Florence";
    String keywords "AEROSOLS, ATMOSPHERIC CHEMISTRY, SULFUR COMPOUNDS";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC BY-NC: This license allows reusers to distribute, remix, adapt, and build upon the material in any medium or format for noncommercial purposes only, and only so long as attribution is given to the creator.";
    Float64 Northernmost_Northing 78.92136;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 78.92136;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Sulphate contributions to PM10 aerosol sampled at Gruvebadet Observatory (Ny Alesund)";
    String title "GVB Sulphate apportionment in PM10";
    Float64 Westernmost_Easting 11.86587;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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