glenglat: Global englacial temperature database
<p>Open-access database of englacial temperature measurements compiled from data submissions and published literature. It is developed on <a href="https://github.com/mjacqu/glenglat">GitHub</a> and published to <a href="https://doi.org/10.5281/zenodo.11516611">Zenodo</a>. This version (1.0.0) of the dataset is described in the following publication:</p> <blockquote> <p>Mylène Jacquemart, Ethan Welty, Marcus Gastaldello, and Guillem Carcanade (2025). glenglat: A database of global englacial temperatures. Earth System Science Data 17(4): 1627–1666. <a href="https://doi.org/10.5194/essd-17-1627-2025">https://doi.org/10.5194/essd-17-1627-2025</a></p> </blockquote> <h2>Dataset structure</h2> <p>The dataset adheres to the Frictionless Data <a href="https://specs.frictionlessdata.io/tabular-data-package">Tabular Data Package</a> specification. The metadata in <code>datapackage.json</code> describes, in detail, the contents of the tabular data files in the <code>data</code> folder:</p> <ul> <li><code>source.csv</code>: Description of each data source (either a personal communication or the reference to a published study).</li> <li><code>borehole.csv</code>: Description of each borehole (location, elevation, etc), linked to <code>source.csv</code> via <code>source_id</code> and less formally via source identifiers in <code>notes</code>.</li> <li><code>profile.csv</code>: Description of each profile (date, etc), linked to <code>borehole.csv</code> via <code>borehole_id</code> and to <code>source.csv</code> via <code>source_id</code> and less formally via source identifiers in <code>notes</code>.</li> <li><code>measurement.csv</code>: Description of each measurement (depth and temperature), linked to <code>profile.csv</code> via <code>borehole_id</code> and <code>profile_id</code>.</li> </ul> <p>For boreholes with many profiles (e.g. from automated loggers), pairs of <code>profile.csv</code> and <code>measurement.csv</code> are stored separately in subfolders of <code>data</code> named <code>{source.id}-{glacier}</code>, where <code>glacier</code> is a simplified and kebab-cased version of the glacier name (e.g. <code>flowers2022-little-kluane</code>).</p> <h3>Supporting information</h3> <p>The folder <code>sources</code>, available on <a href="https://github.com/mjacqu/glenglat">GitHub</a> but omitted from dataset releases on <a href="https://doi.org/10.5281/zenodo.11516611">Zenodo</a>, contains subfolders (with names matching column <code>source.id</code>) with files that document how and from where the data was extracted.</p> <h2>Tables</h2> <p>Jump to: <a href="#source"><code>source</code></a> · <a href="#borehole"><code>borehole</code></a> · <a href="#profile"><code>profile</code></a> · <a href="#measurement"><code>measurement</code></a></p> <h3><a name="source"></a><code>source</code></h3> <p>Sources of information considered in the compilation of this database. Column names and categorical values closely follow the Citation Style Language (CSL) 1.0.2 specification. Names of people in non-Latin scripts are followed by a latinization in square brackets (e.g. В. С. Загороднов [V. S. Zagorodnov]) and non-English titles are followed by a translation in square brackets. The family name of Latin-script names is wrapped in curly braces when it is not the last word of the name (e.g. Emmanuel {Le Meur}, e.g. {Duan} Keqin) or the name ends in two or more unabbreviated words (e.g. Jon Ove {Hagen}). The family name of a Chinese name (and of the latinization) is wrapped in curly braces when it is not the first character.</p> <table> <tbody> <tr> <th>name</th> <th>type</th> <th>description</th> </tr> </tbody> <tbody> <tr> <td><code>id</code> (required)</td> <td>string</td> <td>Unique identifier constructed from the first author's lowercase, latinized, family name and the publication year, followed as needed by a lowercase letter to ensure uniqueness (e.g. Загороднов 1981 → zagorodnov1981a).</td> </tr> <tr> <td><code>author</code></td> <td>string</td> <td>Author names (optionally followed by their ORCID or contact email in parentheses) as a pipe-delimited list.</td> </tr> <tr> <td><code>year</code> (required)</td> <td>year</td> <td>Year of publication.</td> </tr> <tr> <td><code>type</code> (required)</td> <td>string</td> <td>Item type.<br>- article-journal: Journal article<br>- book: Book (if the entire book is relevant)<br>- chapter: Book section<br>- document: Document not fitting into any other category<br>- dataset: Collection of data<br>- map: Geographic map<br>- paper-conference: Paper published in conference proceedings<br>- personal-communication: Personal communication between individuals<br>- speech: Presentation (talk, poster) at a conference<br>- report: Report distributed by an institution<br>- thesis-phd: Doctor of Philosophy (PhD) thesis<br>- thesis-msc: Master of Science (MSc) thesis<br>- webpage: Website or page on a website</td> </tr> <tr> <td><code>title</code> (required)</td> <td>string</td> <td>Item title.</td> </tr> <tr> <td><code>url</code></td> <td>string</td> <td>URL (DOI if available).</td> </tr> <tr> <td><code>language</code> (required)</td> <td>string</td> <td>Language as ISO 639-1 two-letter language code.<br>- da: Danish<br>- de: German<br>- en: English<br>- es: Spanish<br>- fr: French<br>- ja: Japanese<br>- ko: Korean<br>- ru: Russian<br>- sv: Swedish<br>- zh: Chinese</td> </tr> <tr> <td><code>container_title</code></td> <td>string</td> <td>Title of the container (e.g. journal, book).</td> </tr> <tr> <td><code>volume</code></td> <td>integer</td> <td>Volume number of the item or container.</td> </tr> <tr> <td><code>issue</code></td> <td>string</td> <td>Issue number (e.g. 1) or range (e.g. 1-2) of the item or container, with an optional letter prefix (e.g. F1) or part number (e.g. 75pt2).</td> </tr> <tr> <td><code>page</code></td> <td>string</td> <td>Page number (e.g. 1) or range (e.g. 1-2) of the item in the container, with an optional letter prefix (e.g. S1).</td> </tr> <tr> <td><code>version</code></td> <td>string</td> <td>Version number (e.g. 1.0) of the item.</td> </tr> <tr> <td><code>editor</code></td> <td>string</td> <td>Editor names (e.g. of the containing book) as a pipe-delimited list.</td> </tr> <tr> <td><code>collection_title</code></td> <td>string</td> <td>Title of the collection (e.g. book series).</td> </tr> <tr> <td><code>collection_number</code></td> <td>string</td> <td>Number (e.g. 1) or range (e.g. 1-2) in the collection (e.g. book series volume).</td> </tr> <tr> <td><code>publisher</code></td> <td>string</td> <td>Publisher name.</td> </tr> </tbody> </table> <h3><a name="borehole"></a><code>borehole</code></h3> <p>Metadata about each borehole.</p> <table> <tbody> <tr> <th>name</th> <th>type</th> <th>description</th> </tr> </tbody> <tbody> <tr> <td><code>id</code> (required)</td> <td>integer</td> <td>Unique identifier.</td> </tr> <tr> <td><code>source_id</code> (required)</td> <td>string</td> <td>Identifier of the source of the earliest temperature measurements. This is also the source of the borehole attributes unless otherwise stated in <code>notes</code>.</td> </tr> <tr> <td><code>glacier_name</code> (required)</td> <td>string</td> <td>Glacier or ice cap name (as reported).</td> </tr> <tr> <td><code>glims_id</code></td> <td>string</td> <td>Global Land Ice Measurements from Space (GLIMS) glacier identifier.</td> </tr> <tr> <td><code>location_origin</code> (required)</td> <td>string</td> <td>Origin of location (<code>latitude</code>, <code>longitude</code>).<br>- submitted: Provided in data submission<br>- published: Reported as coordinates in original publication<br>- digitized: Digitized from published map with complete axes<br>- estimated: Estimated from published plot by comparing to a map (e.g. Google Maps, CalTopo)<br>- guessed: Estimated with difficulty, for example by comparing <code>elevation</code> to a map (e.g. Google Maps, CalTopo)</td> </tr> <tr> <td><code>latitude</code> (required)</td> <td>number [degree]</td> <td>Latitude (EPSG 4326).</td> </tr> <tr> <td><code>longitude</code> (required)</td> <td>number [degree]</td> <td>Longitude (EPSG 4326).</td> </tr> <tr> <td><code>elevation_origin</code> (required)</td> <td>string</td> <td>Origin of elevation (<code>elevation</code>).<br>- submitted: Provided in data submission<br>- published: Reported as number in original publication<br>- digitized: Digitized from published plot with complete axes<br>- estimated: Estimated from elevation contours in published map<br>- guessed: Estimated with difficulty, for example by comparing location (<code>latitude</code>, <code>longitude</code>) to a map of contemporary elevations (e.g. CalTopo, Google Maps)</td> </tr> <tr> <td><code>elevation</code> (required)</td> <td>number [m]</td> <td>Elevation above sea level.</td> </tr> <tr> <td><code>mass_balance_area</code></td> <td>string</td> <td>Mass balance area.<br>- ablation: Ablation area<br>- equilibrium: Near the equilibrium line<br>- accumulation: Accumulation area</td> </tr> <tr> <td><code>label</code></td> <td>string</td> <td>Borehole name (e.g. as labeled on a plot).</td> </tr> <tr> <td><code>date_min</code></td> <td>date (%Y-%m-%d)</td> <td>Begin date of drilling, or if not known precisely, the first possible date (e.g. 2019 → 2019-01-01).</td> </tr> <tr> <td><code>date_max</code></td> <td>date (%Y-%m-%d)</td> <td>End date of drilling, or if not known precisely, the last possible date (e.g. 2019 → 2019-12-31).</td> </tr> <tr> <td><code>drill_method</code></td> <td>string</td> <td>Drilling method.<br>- mechanical: Push, percussion, rotary<br>- thermal: Hot point, electrothermal, steam<br>- combined: Mechanical and thermal</td> </tr> <tr> <td><code>ice_depth</code></td> <td>number [m]</td> <td>Starting depth of continuous ice. Infinity (INF) indicates that only snow, firn, or intermittent ice was reached.</td> </tr> <tr> <td><code>depth</code></td> <td>number [m]</td> <td>Total borehole depth (not including drilling in the underlying bed).</td> </tr> <tr> <td><code>to_bed</code></td> <td>boolean</td> <td>Whether the borehole reached the glacier bed.</td> </tr> <tr> <td><code>temperature_uncertainty</code></td> <td>number [°C]</td> <td>Estimated temperature uncertainty (as reported).</td> </tr> <tr> <td><code>notes</code></td> <td>string</td> <td>Additional remarks about the study site, the borehole, or the measurements therein as a pipe-delimited list. Sources are referenced by <code>source.id</code>. Quality concerns are prefixed with '[flag]'.</td> </tr> <tr> <td><code>curator</code></td> <td>string</td> <td>Names of people who added the data to the database, as a pipe-delimited list.</td> </tr> <tr> <td><code>investigators</code></td> <td>string</td> <td>Names of people and/or agencies who performed the work, as a pipe-delimited list. Each entry is in the format 'person (agency; ...) {notes}', where only person or one agency is required. Person and agency may contain a latinized form in square brackets.</td> </tr> <tr> <td><code>funding</code></td> <td>string</td> <td>Funding sources as a pipe-delimited list. Each entry is in the format 'funder [rorid] > award [number] url', where only funder is required and rorid is the funder's ROR (https://ror.org) ID (e.g. 01jtrvx49).</td> </tr> </tbody> </table> <h3><a name="profile"></a><code>profile</code></h3> <p>Date and time of each measurement profile.</p> <table> <tbody> <tr> <th>name</th> <th>type</th> <th>description</th> </tr> </tbody> <tbody> <tr> <td><code>borehole_id</code> (required)</td> <td>integer</td> <td>Borehole identifier.</td> </tr> <tr> <td><code>id</code> (required)</td> <td>integer</td> <td>Borehole profile identifier (starting from 1 for each borehole).</td> </tr> <tr> <td><code>source_id</code> (required)</td> <td>string</td> <td>Source identifier.</td> </tr> <tr> <td><code>measurement_origin</code> (required)</td> <td>string</td> <td>Origin of measurements (<code>measurement.depth</code>, <code>measurement.temperature</code>).<br>- submitted: Provided as numbers in data submission<br>- published: Numbers read from original publication<br>- digitized-discrete: Digitized with Plot Digitizer from discrete points of depth versus temperature<br>- digitized-continuous: Digitized with Plot Digitizer from a continuous data source (e.g. line plot of depth versus temperature)</td> </tr> <tr> <td><code>date_min</code></td> <td>date (%Y-%m-%d)</td> <td>Measurement date, or if not known precisely, the first possible date (e.g. 2019 → 2019-01-01).</td> </tr> <tr> <td><code>date_max</code> (required)</td> <td>date (%Y-%m-%d)</td> <td>Measurement date, or if not known precisely, the last possible date (e.g. 2019 → 2019-12-31).</td> </tr> <tr> <td><code>time</code></td> <td>time (%H:%M:%S)</td> <td>Measurement time.</td> </tr> <tr> <td><code>utc_offset</code></td> <td>number [h]</td> <td>Time offset relative to Coordinated Universal Time (UTC).</td> </tr> <tr> <td><code>equilibrium</code></td> <td>string</td> <td>Whether and how reported temperatures equilibrated following drilling.<br>- true: Equilibrium was measured<br>- estimated: Equilibrium was estimated (typically by extrapolation)<br>- false: Equilibrium was not reached</td> </tr> <tr> <td><code>notes</code></td> <td>string</td> <td>Additional remarks about the profile or the measurements therein as a pipe-delimited list. Sources are referenced by <code>source.id</code>. Quality concerns are prefixed with '[flag]'.</td> </tr> </tbody> </table> <h3><a name="measurement"></a><code>measurement</code></h3> <p>Temperature measurements with depth.</p> <table> <tbody> <tr> <th>name</th> <th>type</th> <th>description</th> </tr> </tbody> <tbody> <tr> <td><code>borehole_id</code> (required)</td> <td>integer</td> <td>Borehole identifier.</td> </tr> <tr> <td><code>profile_id</code> (required)</td> <td>integer</td> <td>Borehole profile identifier.</td> </tr> <tr> <td><code>depth</code> (required)</td> <td>number [m]</td> <td>Depth below the glacier surface.</td> </tr> <tr> <td><code>temperature</code> (required)</td> <td>number [°C]</td> <td>Temperature.</td> </tr> </tbody> </table>
ShareScore
56/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 12
- Harmonization
- 8
- Access
- 16
- Reuse readiness
- 8
- Engagement
- 12