Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FGDC writer time-currentness tag is in wrong location #173

Closed
stansmith907 opened this issue Jan 19, 2018 · 0 comments
Closed

FGDC writer time-currentness tag is in wrong location #173

stansmith907 opened this issue Jan 19, 2018 · 0 comments
Labels
bug Unexpected problem or unintended behavior

Comments

@stansmith907
Copy link
Contributor

The FGDC writer outputs the time currentness tag in the wrong location. This is happening in both the data identification and linage source sections.

Data identification section should be:

    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>2017-12-01</caldate>
          <time/>
        </sngdate>
      </timeinfo>
      <current>time info currentness</current>
    </timeperd>

Lineage source section should be:

        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>2017-12-17</begdate>
              <begtime/>
              <enddate>2017-12-18</enddate>
              <endtime/>
            </rngdates>
          </timeinfo>
          <srccurr>description</srccurr>
        </srctime>
@stansmith907 stansmith907 added the bug Unexpected problem or unintended behavior label Jan 19, 2018
@stansmith907 stansmith907 changed the title FGDC writer time currentness tag is in wrong location FGDC writer time-currentness tag is in wrong location Jan 19, 2018
stansmith907 added a commit to stansmith907/mdTranslator that referenced this issue Jan 19, 2018
Refactor minitests.
Closes issue adiwg#173
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant