Difference between revisions of "Creating a LiPD file"
m (→What is LiPD?) |
(→How do I get my data into LiPD?: What constitutes a LiPD file) |
||
| Line 22: | Line 22: | ||
== How do I get my data into LiPD?== | == How do I get my data into LiPD?== | ||
| + | |||
| + | As of April 2017, the most efficient way to get you paleoclimate dataset in LiPD format is to fill our our Excel Template [link] and use the Python [[LiPD Utilities]] to convert the template into a [[Linked Paleo Data | LiPD]] file. Make sure you are using the latest version of the template for compatibility. | ||
| + | |||
| + | By the end of 2017, a web-based interface should be able to automate a lot of the manual steps. | ||
=== General Guidelines === | === General Guidelines === | ||
==== What constitutes a LiPD file?==== | ==== What constitutes a LiPD file?==== | ||
| + | |||
| + | As its most fundamental level, all the data and metadata that are part of the same study should be placed in the same LiPD file. There are exceptions to this rule of thumb. For instance, if the study involves two physical samples in drastically different locations (i.e., different regimes), then each physical sample and associated data and metadata should be placed in separate LiPD files. In other words, if the data from each specific physical sample can be reused on their own in another study, then each should be placed in its own LiPD files. | ||
==== What constitutes a [[:Category:MeasurementTable © | measurement table]]? ==== | ==== What constitutes a [[:Category:MeasurementTable © | measurement table]]? ==== | ||
Revision as of 20:50, 11 April 2017
The most straightforward way to upload a dataset onto the wiki is to first create a LiPD file and upload it directly.
Contents
What is LiPD?
LiPD (Linked Paleo Data) is a convenient way to store and exchange paleoclimate data format and provides the backbone of the LinkedEarth edifice. LiPD is closely aligned with the LinkedEarth Ontology; changes in one are mirrored in the other.
How to read a LiPD file?
LiPD was designed so that is can capture much richer sets of (meta)data than ASCII or Excel files and to have a fixed backbone around which scientific codes can be built. There is a price to pay for this power: LiPD is undoubtedly more difficult to interact with than a plain text file. Although it is possible to unzip a LiPD file and navigate through the native JSON-LD and csv files, this not the best way to harness the power of LiPD files.
The easiest way to interact with a LiPD file is by using this very wiki, which allows you to navigate the hierarchical structure of the file easily.
In addition, we have developed several utilities to read and write LiPD files in Matlab, Python, and R.
What can I do with a LiPD file?
LiPD was designed to facilitate coding around paleoclimate data. We have already developed software in R and Python to analyze and visualize paleoclimate data:
In addition, CSciBox (an integrated system for age-model reconstruction) makes use of LiPD.
How do I get my data into LiPD?
As of April 2017, the most efficient way to get you paleoclimate dataset in LiPD format is to fill our our Excel Template [link] and use the Python LiPD Utilities to convert the template into a LiPD file. Make sure you are using the latest version of the template for compatibility.
By the end of 2017, a web-based interface should be able to automate a lot of the manual steps.
General Guidelines
What constitutes a LiPD file?
As its most fundamental level, all the data and metadata that are part of the same study should be placed in the same LiPD file. There are exceptions to this rule of thumb. For instance, if the study involves two physical samples in drastically different locations (i.e., different regimes), then each physical sample and associated data and metadata should be placed in separate LiPD files. In other words, if the data from each specific physical sample can be reused on their own in another study, then each should be placed in its own LiPD files.
