Data Access Form

Dataset Title:	GeoKarla : Geophysical and petrophysical data of the Karla impact structure
Institution:	CEREGE UMR 7330 CNRS (Dataset ID: cerege_geokarla_f9b6_a49d_9df9)
Information:	Summary \| License \| Metadata \| Background \| Subset \| 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

or a List of Values

Maximum

url

name (File Name)

lastModified (UTC)

2021-03-31T14:28:41Z

2021-03-31T14:28:42Z

size (bytes)

1468.0

296818.0

fileType

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 {
  url {
    String ioos_category "Identifier";
    String long_name "URL";
  }
  name {
    String ioos_category "Identifier";
    String long_name "File Name";
  }
  lastModified {
    String ioos_category "Time";
    String long_name "Last Modified";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  size {
    String ioos_category "Other";
    String long_name "Size";
    String units "bytes";
  }
  fileType {
    String ioos_category "Identifier";
    String long_name "File Type";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String history 
"2024-10-30T05:42:42Z (local files)
2024-10-30T05:42:42Z http://erddap.osupytheas.fr/erddap/tabledap/cerege_geokarla_f9b6_a49d_9df9.html";
    String infoUrl "http://www.cerege.fr";
    String institution "CEREGE UMR 7330 CNRS";
    String keywords "cerege, cnrs, geokarla, geology, geophysical, impact, karla, petrophysical, russia, structure, tatarstan";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "(local files)";
    String subsetVariables "fileType";
    String summary "The GeoKarla dataset gathers geophysical and petrophysical data acquired over the Karla impact structure (Tatarstan, Russia).";
    String title "GeoKarla : Geophysical and petrophysical data of the Karla impact structure";
  }
}

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.