Data Access Form

Dataset Title:	Volume equivalent diameters and bin widths for the PSD
Institution:	Institute of Polar Sciences (Dataset ID: d0852967-fce4-49fe-abe2-1c274de5e942)
Information:	Summary \| License \| Metadata \| Background \| Files \| Make a graph

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.

Variable	Optional Constraint #1		Optional Constraint #2		Minimum	Maximum
Volume_Equivalent_diameter_in_micron					0.0104	14.1862
dlogDp					0.004146	0.033858

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

File type: (more information)

(Documentation / Bypass this form )

(Please be patient. It may take a while to get the data.)

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Volume_Equivalent_diameter_in_micron {
    Float32 actual_range 0.0104, 14.1862;
    String long_name "Volume Equivalent Diameter In Micron";
    String standard_name "number_size_distribution_of_aerosol_particles_in_air";
  }
  dlogDp {
    Float32 actual_range 0.004146, 0.033858;
    String long_name "Dlog Dp";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String contributor_email "mauro.mazzola@cnr.it";
    String contributor_institution "Institute of Polar Sciences";
    String contributor_name "Mauro Mazzola";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "mauro.mazzola@cnr.it";
    String creator_name "Mauro Mazzola";
    String history 
"Volume equivalent diameters and bin widths for the PSD
2026-02-20T04:37:33Z (local files)
2026-02-20T04:37:33Z https://data.iadc.cnr.it/erddap/tabledap/d0852967-fce4-49fe-abe2-1c274de5e942.html";
    String infoUrl "https://www.isp.cnr.it";
    String institution "Institute of Polar Sciences";
    String keywords "aps, diameter, dlogDp, polar, psd, sciences, smps, volume, Volume_Equivalent_diameter_in_micron";
    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.";
    String publisher_name "Italian Arctic Data Center";
    String publisher_type "group";
    String publisher_url "https://iadc.cnr.it";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Volume equivalent diameters and bin widths for the PSD";
    String title "Volume equivalent diameters and bin widths for the PSD";
  }
}

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.