Create LiPD

Coming soon!

- Ensemble and distribution table creating and editing is under development. Ensemble data is visible but has limited functionality.

- "Take the tour!" option will allow you to become familiar with all aspects of this page.


We have updated your file from LiPD version v{{pageMeta.oldVersion}} to v1.3

Load & Validate

  1. Wiki Ready"Insert fields to meet Linked Earth Wiki requirements. NOTE: Column keys are only inserted for existing columns"NOAA Ready (Beta)"Insert fields to meet NOAA requirements. NOTE: Column keys are only inserted for existing columns"
  2. {{ feedback.errCt}} errors
    • {{err}}
    {{ feedback.wrnCt }} warnings
    • {{wrn}}
  3. Invalid LiPD file
    Valid LiPD file
    Wiki requirements not met
    Wiki requirements met
    NOAA requirements not met
    NOAA requirements met
  4. {{files.fileCt}} files in LiPD
    • {{ file.filenameShort }}

Root

We'll update your LiPD file to the latest version during uploadPlease include name, location, and year in your dataset nameStandard format is: "SiteName.AuthorLastName.PublicationYear"
{{method}}Where did this file originate from? How was the LiPD file created?{{archive}}Which ProxyArchive underlies this ProxySystem?
Use the format: LastName, FirstName; LastName, FirstName; ...
Use to add information that does not fit elsewhere in the dataset

NOAA

{{tu}}
What is the digital object identifier associated with the dataset? Example: 10.1000/sample123

FundingSource of monetary support underlying the collection/creation/analysis/curation of the Dataset

funding {{$index+1}}
Which entity was the Dataset funded by?What was the Funding source for the Dataset?
Who was the lead on the source of Funding for the Dataset?Which nation funded the Dataset?

Publication

publication {{$index+1}}
What is the digital object identifier associated with the resource? Enter a valid DOI and we'll fetch the information. Example: 10.1000/sample123

What is the title of the Publication?
What is the name of the journal in which the resource can be found?
{{yr}}What year was the Publication issued? (not required for dataCitations)In what pages of the Publication can the reference to the resource be found? (not required for dataCitations)In which volume of the Publication does the reference to the Datatset appear?
In what issue of the journal can the resource be found?
Who wrote (i.e., created) the resource, such as a Publication? Use format: LastName, FirstName

GeographyThe geographic data and metadata for the dataset

{{pageMeta.decimalDegrees? "Decimal Degrees": "Degrees-Minutes-Seconds"}}LiPD stores coordinates as Decimal Degrees. You may switch to Degrees-Minutes-Seconds format and we will convert the values for you.
The latitude value in decimal degrees from -90 to 90The longitude value in decimal degrees from -180 to 180
Latitude
Longitude
The location's elevation value expressed in metersAll elevation values must be expressed in meters
{{country.name}} ({{country.code}})ISO 3166 standard country list
Example: Continent>North America>United States of America>Baltimore

PaleoData *

paleo {{$parent.$index+1}} > measurement {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.
Parse Values
Delimiter{{ delimiter.view }}Generally, copy/pasting data results in a 'Tab' delimiter. Please note if another delimiter is in use.Header: {{ pageMeta.header? "Yes": "No"}}If your values include a variable name header, feel free to include it. They must use the same formatting as the values, and not include any unitsKeep Existing Columns: {{ pageMeta.keepColumnMeta? "Yes" : "No"}}If you have a table full of metadata, and ONLY want to update the values, you can choose 'Keep Existing Columns' to preserve the metadata. Choosing 'No' will replace all current data with the newly parsed data.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
paleo {{$parent.$index+1}} > model 1 > method
paleo {{$parent.$index+1}} > model 1 > summary {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.
Parse Values
Delimiter{{ delimiter.view }}Generally, copy/pasting data results in a 'Tab' delimiter. Please note if another delimiter is in use.Header: {{ pageMeta.header? "Yes": "No"}}If your values include a variable name header, feel free to include it. They must use the same formatting as the values, and not include any unitsKeep Existing Columns: {{ pageMeta.keepColumnMeta? "Yes" : "No"}}If you have a table full of metadata, and ONLY want to update the values, you can choose 'Keep Existing Columns' to preserve the metadata. Choosing 'No' will replace all current data with the newly parsed data.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
paleo {{$parent.$index+1}} > model 1 > ensemble {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
Table Type{{ table.name }}DataTable containing PaleoData Variables

chronDataThe data, metadata, and Model that describe the set of Variables used to relate depth/position to time (chronological information)

chron {{$parent.$index+1}} > measurement {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.
Parse Values
Delimiter{{ delimiter.view }}Generally, copy/pasting data results in a 'Tab' delimiter. Please note if another delimiter is in use.Header: {{ pageMeta.header? "Yes": "No"}}If your values include a variable name header, feel free to include it. They must use the same formatting as the values, and not include any unitsKeep Existing Columns: {{ pageMeta.keepColumnMeta? "Yes" : "No"}}If you have a table full of metadata, and ONLY want to update the values, you can choose 'Keep Existing Columns' to preserve the metadata. Choosing 'No' will replace all current data with the newly parsed data.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
chron {{$parent.$index+1}} > model 1 > method
chron {{$parent.$index+1}} > model 1 > summary {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.
Parse Values
Delimiter{{ delimiter.view }}Generally, copy/pasting data results in a 'Tab' delimiter. Please note if another delimiter is in use.Header: {{ pageMeta.header? "Yes": "No"}}If your values include a variable name header, feel free to include it. They must use the same formatting as the values, and not include any unitsKeep Existing Columns: {{ pageMeta.keepColumnMeta? "Yes" : "No"}}If you have a table full of metadata, and ONLY want to update the values, you can choose 'Keep Existing Columns' to preserve the metadata. Choosing 'No' will replace all current data with the newly parsed data.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
chron {{$parent.$index+1}} model 1 ensemble {{$index+1}}
Automated field. This field is disabled to preserve standardized naming.LiPD uses 'NaN' as the standard missing value. Please note if your data uses a different missing value.
Automated field. This field is disabled to preserve standardized naming.

Columns
column {{$index+1}}: {{entry3.variableName}}
Standard fields
In what unit of measure is (are) the Variable(s) expressed?
This is a preview of the value data. You cannot edit this directly. Use the "Parse CSV" box where necessary.
Don't see the field you want? Add your custom field and press enter.
Additional fields
Table Type{{ table.name }}DataTable containing Variables pertaining to chronological information