geologicAge new object

[stansmith907]

Schema rules for geologicAge {object}: "A name, code, or date describing an event or period in geologic time, expressed either as an absolute date calculated using a named dating method, or as a relative date that is drawn from stratigraphy or biostratigraphy"

Rules:

• optional

• geologicAge appears in both single date and time period in FGDC. However I have only added geologicAge to timePeriod and timeInstant in ADIwg. ADIwg uses timePeriod or temporalExtent in all places geologic age might be appropriate. In ADIwg date is 'typed' to objects other than the information resource such as citation or metadata.

Element Definitions:

• ageTimeScale: {string} "Name of a recognized geologic time scale. This includes “Absolute” as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time"
• ageEstimate: {string} "Either an absolute geologic date or a relative geologic age name describing an event or period in geologic time based on the Geologic_Time_Scale"
• ageUncertainty: {string} "The error estimate for the geologic time. This should include the units of measure, a description of what the error estimate represents and how it was calculated"
• ageExplanation: {string} "The name and/or description of the method used to calculate the ageEstimate. Detailed information about the method may be provided through references contained in the ageReference"
• ageReference: [{citation}] "Citation for works providing detailed information about any element of the
  *geologicAge"

Element Rules:

• ageTimeScale required
• ageEstimate required
• ageUncertainty optional
• ageExplanation optional
• ageReference array, optional

mdJson:

{
   "geologicAge": {
      "ageTimeScale": "",
      "ageEstimate": "",
      "ageUncertainty": "",
      "ageExplanation": "",
      "ageReference": []
   }
}

FGDC single date mapping:

<metadata>
  <idinfo>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20170820</caldate>
          <time>13:30:00</time>
          <geolage>
            <geolscal>time scale</geolscal>
            <geolest>geologic estimate</geolest>
            <geolun>geologic uncertainty</geolun>
            <geolexpl>method to estimate</geolexpl>
            <geolcit>
              <citeinfo>
                <origin>citation party</origin>
                <pubdate>20170615</pubdate>
                <title>citation title</title>
              </citeinfo>
            </geolcit>
            <geolcit></geolcit>
          </geolage>
        </sngdate>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
  </idinfo>
  <metainfo>
    <mettc>universal time</mettc>
  </metainfo>
</metadata>

FGDC timePeriod mapping:

<metadata>
  <idinfo>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>19900701</begdate>
          <begtime>12:30:00</begtime>
          <enddate>2016</enddate>
          <endtime>17:30:00</endtime>
          <beggeol>{see geolage above}</beggeol>
          <endgeol>{see geolage above}</endgeol>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
  </idinfo>
  <metainfo>
    <mettc>universal time</mettc>
  </metainfo>
</metadata>

ISO 19115-2/3 mapping:
Does not map to ISO 19115-2/3.