PermafrostNet PermafrostNet ERDDAP
Easier access to scientific data
log in    
Brought to you by PermafrostNet, and The Digital Research Alliance of Canada    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Ground temperature observations for site DST WT Control Subscribe RSS
Institution:  (1) University of Victoria (2) Northwest Territories Geological Survey   (Dataset ID: NTGS2017-009_DST_WT_Control)
Range: longitude = -135.2978 to -135.2978°E, latitude = 67.24305 to 67.24305°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | 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: 
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 {
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 67.24305, 67.24305;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -135.2978, -135.2978;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  elevation {
    Float32 actual_range 467.813, 467.813;
    String ioos_category "Location";
    String standard_name "height_above_reference_ellipsoid";
    String units "m";
  }
  time {
    Int32 _ChunkSizes 512;
    String _CoordinateAxisType "Time";
    String axis "T";
    String calendar "gregorian";
    String cf_role "profile_id";
    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";
  }
  site_name {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Borehole or site name";
    String standard_name "platform_name";
  }
  depth_below_ground_surface {
    String _CoordinateAxisType "Height";
    Float32 actual_range 0.05, 1.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth below ground surface";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  ground_temperature {
    Int32 _ChunkSizes 1, 1, 4;
    Float32 actual_range -19.103, 73.067;
    String coordinates "site_name depth latitude longitude";
    String ioos_category "Temperature";
    String long_name "Ground temperature";
    String platform "site_name";
    String standard_name "temperature_in_ground";
    String units "degree_C";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.3,hdf5=1.10.6";
    String cdm_altitude_proxy "depth_below_ground_surface";
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "latitude, longitude, elevation, site_name";
    String Conventions "COARDS, CF-1.8, ACDD-1.3";
    String creator_email "(1) tlantz@uvic.ca (2) Steve_Kokelj@gov.nt.ca";
    Float64 Easternmost_Easting -135.2978;
    String environment_description "Gentle tundra slope adjacent to DST Flow";
    String featureType "TimeSeriesProfile";
    String geospatial_bounds "POINT(-135.2978057861328 67.24304962158203)";
    Float64 geospatial_lat_max 67.24305;
    Float64 geospatial_lat_min 67.24305;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -135.2978;
    Float64 geospatial_lon_min -135.2978;
    String geospatial_lon_units "degrees_east";
    Float64 ground_slope_angle 14.257678;
    Float64 ground_slope_direction 20.8248;
    String history 
"2024-05-26T17:47:56Z https://app.nwtgeoscience.ca/Searching/ReferenceSearch.aspx
2024-05-26T17:47:56Z http://data.permafrostnet.ca/tabledap/NTGS2017-009_DST_WT_Control.das";
    String id "NTGS2017-009_DST WT Control";
    String infoUrl "https://app.nwtgeoscience.ca/Searching/ReferenceSearch.aspx";
    String institution "(1) University of Victoria (2) Northwest Territories Geological Survey";
    String license "The use of the published data will not carry restrictions. Full citation of referenced publications and reports by users is required.";
    Float64 Northernmost_Northing 67.24305;
    Float32 observation_depth_max 1.0;
    Float32 observation_depth_min 0.05;
    String organic_matter_thickness "Thin (0-10 cm)";
    String overburden_thickness ">1m";
    String platform_name "DST WT Control";
    String project "A Watershed Approach to Monitoring Cumulative Impacts of Landscape Change";
    String publisher_email "NTGS@gov.nt.ca";
    String publisher_institution "Northwest Territories Geological Survey";
    String publisher_name "Northwest Territories Geological Survey";
    String publisher_type "institution";
    String publisher_url "https://www.nwtgeoscience.ca/";
    String sourceUrl "https://app.nwtgeoscience.ca/Searching/ReferenceSearch.aspx";
    Float64 Southernmost_Northing 67.24305;
    String subsetVariables "latitude, longitude, elevation, site_name";
    String summary "Ground temperature data obtained from NTGS data report 2017-009";
    String surface_cover "Other Vegetation";
    String surficial_geology "Till";
    String time_coverage_duration "P722DT7H0M0S";
    String time_coverage_resolution "P0DT2H0M0S";
    String title "Ground temperature observations for site DST WT Control";
    String vegetation_type "Shrub";
    Float64 Westernmost_Easting -135.2978;
  }
}

 

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