https://wiki.esipfed.org/w/api.php?action=feedcontributions&user=Graybeal&feedformat=atomEarth Science Information Partners (ESIP) - User contributions [en]2024-03-29T09:13:11ZUser contributionsMediaWiki 1.35.14https://wiki.esipfed.org/w/index.php?title=Semantic_Technologies&diff=66542Semantic Technologies2019-07-21T01:09:41Z<p>Graybeal: /* More Information */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%" cellpadding="0" cellspacing="0" style="zborder-top:1px solid #aaaaaa; border-collapse: collapse;" <br />
<br />
|bgcolor="#FFFFBB" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
= Get Involved=<br />
* Join Our [http://lists.esipfed.org/mailman/listinfo/esip-semanticweb Email List]<br />
<br />
==Meetings==<br />
<br />
===SemTech Monthly Telecon===<br />
* 4th Tuesday of each month at 4pm Eastern<br />
* GoToMeeting: https://www.gotomeeting.com/join/976796333<br />
* Phone Access: United States: +1 (872) 240-3212<br />
* Access Code: 976-796-333<br />
<br />
===Community Ontology Repository Cluster Monthly Telecon===<br />
* 1st Tuesday of each month at 5pm Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/395054533<br />
* Phone Access: United States: +1 (872) 240-3412 <br />
* Access Code: 395-054-533<br />
<br />
===Semantic Harmonization Cluster Monthly Telecon===<br />
* 2nd Monday of each month at noon Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/373181901<br />
* Phone Access: United States: +1 (571) 317-3112<br />
* Access Code: 373-181-901<br />
<br />
|bgcolor="pink" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
<br />
===Products===<br />
<br />
*[http://wiki.esipfed.org/index.php/COR_ST Community Ontology Repository: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/LDAS Linked Data-As-A-Service: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/Sweet_Ontology SWEET Ontology: ]<br />
<br />
*[https://github.com/ESIPFed/science-on-schema.org science-on-schema.org ]<br />
<br />
*[https://github.com/ESIPFed/pyldn Linked Data Notifications Service]<br />
<br />
===More Information===<br />
*[http://wiki.esipfed.org/index.php/About_The_Comittee About the Comittee]<br />
*[http://wiki.esipfed.org/index.php/Current_Work Previous Work]<br />
*[http://wiki.esipfed.org/index.php/Semantic_Web_Telecons Monthly Telecon Notes]<br><br />
*[http://wiki.esipfed.org/index.php/Previous_Presentations Previous Presentations]<br />
*Running Notes from ESIP meetings<br />
**[https://docs.google.com/document/d/1zc0I9izLAGdbHgv8KrlNtwjCHKJvA8-o20U5hnUwQD8/edit Semantic Technology Committee Business Meeting]<br />
**[https://docs.google.com/document/d/1A1kWKDrDQt3bi5C_PAgGfP3TOcPA7T5N-yROMZ_bqRQ/edit Community Ontology Repository Working Meeting]<br />
<br />
===Contacts=== <br />
*Lewis John McGibbney, Chair, lewis.j.mcgibbney [at] jpl [dot] nasa [dot] gov<br />
*Pier Luigi Buttigieg, Co-Chair, pbuttigi [at] mpi-bremen [dot] de<br />
*Zachary Robbins, ESIP Community Fellow, zjrobbin [at] NCSU [dot] edu<br />
|}<br />
<br />
==Vision of the Semantic Technologies Committee==<br />
#Promote research and development of semantic technologies in support of Earth science data discovery, dissemination, and analysis<br />
#Collaborate with ESIP members, working groups, clusters, and standing committees on semantic related topics<br />
#Foster sharing and reuse of ontologies and controlled vocabularies<br />
#To provide a collaborative environment for the development of ontologies and ontology-based standards<br />
#To maintain a long-term agenda and roadmap for evaluation of semantic technologies within ESIP<br />
#To collaborate with external agencies, on behalf of ESIP, in regards to semantic technologies<br />
<br />
<br />
==Github Collaboration Area==<br />
* [https://github.com/ESIPFed/stc SemTech Github Repository]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Semantic_Technologies&diff=66541Semantic Technologies2019-07-21T01:07:41Z<p>Graybeal: /* More Information */ cleanup</p>
<hr />
<div>__NOTOC__<br />
{| width="100%" cellpadding="0" cellspacing="0" style="zborder-top:1px solid #aaaaaa; border-collapse: collapse;" <br />
<br />
|bgcolor="#FFFFBB" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
= Get Involved=<br />
* Join Our [http://lists.esipfed.org/mailman/listinfo/esip-semanticweb Email List]<br />
<br />
==Meetings==<br />
<br />
===SemTech Monthly Telecon===<br />
* 4th Tuesday of each month at 4pm Eastern<br />
* GoToMeeting: https://www.gotomeeting.com/join/976796333<br />
* Phone Access: United States: +1 (872) 240-3212<br />
* Access Code: 976-796-333<br />
<br />
===Community Ontology Repository Cluster Monthly Telecon===<br />
* 1st Tuesday of each month at 5pm Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/395054533<br />
* Phone Access: United States: +1 (872) 240-3412 <br />
* Access Code: 395-054-533<br />
<br />
===Semantic Harmonization Cluster Monthly Telecon===<br />
* 2nd Monday of each month at noon Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/373181901<br />
* Phone Access: United States: +1 (571) 317-3112<br />
* Access Code: 373-181-901<br />
<br />
|bgcolor="pink" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
<br />
===Products===<br />
<br />
*[http://wiki.esipfed.org/index.php/COR_ST Community Ontology Repository: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/LDAS Linked Data-As-A-Service: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/Sweet_Ontology SWEET Ontology: ]<br />
<br />
*[https://github.com/ESIPFed/science-on-schema.org science-on-schema.org ]<br />
<br />
*[https://github.com/ESIPFed/pyldn Linked Data Notifications Service]<br />
<br />
===More Information===<br />
*[http://wiki.esipfed.org/index.php/About_The_Comittee About the Comittee]<br />
*[http://wiki.esipfed.org/index.php/Current_Work Previous Work]<br />
*[http://wiki.esipfed.org/index.php/Semantic_Web_Telecons Monthly Telecon Notes]<br><br />
*[http://wiki.esipfed.org/index.php/Previous_Presentations Previous Presentations]<br />
*Notes from ESIP meetings<br />
**[https://docs.google.com/document/d/1zc0I9izLAGdbHgv8KrlNtwjCHKJvA8-o20U5hnUwQD8/edit Semantic Technology Committee Business Meeting]<br />
**[https://docs.google.com/document/d/1A1kWKDrDQt3bi5C_PAgGfP3TOcPA7T5N-yROMZ_bqRQ/edit Community Ontology Repository Working Meeting]<br />
<br />
===Contacts=== <br />
*Lewis John McGibbney, Chair, lewis.j.mcgibbney [at] jpl [dot] nasa [dot] gov<br />
*Pier Luigi Buttigieg, Co-Chair, pbuttigi [at] mpi-bremen [dot] de<br />
*Zachary Robbins, ESIP Community Fellow, zjrobbin [at] NCSU [dot] edu<br />
|}<br />
<br />
==Vision of the Semantic Technologies Committee==<br />
#Promote research and development of semantic technologies in support of Earth science data discovery, dissemination, and analysis<br />
#Collaborate with ESIP members, working groups, clusters, and standing committees on semantic related topics<br />
#Foster sharing and reuse of ontologies and controlled vocabularies<br />
#To provide a collaborative environment for the development of ontologies and ontology-based standards<br />
#To maintain a long-term agenda and roadmap for evaluation of semantic technologies within ESIP<br />
#To collaborate with external agencies, on behalf of ESIP, in regards to semantic technologies<br />
<br />
<br />
==Github Collaboration Area==<br />
* [https://github.com/ESIPFed/stc SemTech Github Repository]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Semantic_Technologies&diff=66540Semantic Technologies2019-07-21T01:04:31Z<p>Graybeal: /* More Information */ added links to ESIP meetings</p>
<hr />
<div>__NOTOC__<br />
{| width="100%" cellpadding="0" cellspacing="0" style="zborder-top:1px solid #aaaaaa; border-collapse: collapse;" <br />
<br />
|bgcolor="#FFFFBB" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
= Get Involved=<br />
* Join Our [http://lists.esipfed.org/mailman/listinfo/esip-semanticweb Email List]<br />
<br />
==Meetings==<br />
<br />
===SemTech Monthly Telecon===<br />
* 4th Tuesday of each month at 4pm Eastern<br />
* GoToMeeting: https://www.gotomeeting.com/join/976796333<br />
* Phone Access: United States: +1 (872) 240-3212<br />
* Access Code: 976-796-333<br />
<br />
===Community Ontology Repository Cluster Monthly Telecon===<br />
* 1st Tuesday of each month at 5pm Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/395054533<br />
* Phone Access: United States: +1 (872) 240-3412 <br />
* Access Code: 395-054-533<br />
<br />
===Semantic Harmonization Cluster Monthly Telecon===<br />
* 2nd Monday of each month at noon Eastern<br />
* GoToMeeting: https://global.gotomeeting.com/join/373181901<br />
* Phone Access: United States: +1 (571) 317-3112<br />
* Access Code: 373-181-901<br />
<br />
|bgcolor="pink" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
<br />
===Products===<br />
<br />
*[http://wiki.esipfed.org/index.php/COR_ST Community Ontology Repository: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/LDAS Linked Data-As-A-Service: ]<br />
<br />
*[http://wiki.esipfed.org/index.php/Sweet_Ontology SWEET Ontology: ]<br />
<br />
*[https://github.com/ESIPFed/science-on-schema.org science-on-schema.org ]<br />
<br />
*[https://github.com/ESIPFed/pyldn Linked Data Notifications Service]<br />
<br />
===More Information===<br />
*[http://wiki.esipfed.org/index.php/About_The_Comittee About the Comittee]<br />
*[http://wiki.esipfed.org/index.php/Current_Work Previous Work]<br />
*[http://wiki.esipfed.org/index.php/Semantic_Web_Telecons Monthly Telecon Notes]<br><br />
*[http://wiki.esipfed.org/index.php/Previous_Presentations Previous Presentations]<br />
*Notes from ESIP meetings: [https://docs.google.com/document/d/1zc0I9izLAGdbHgv8KrlNtwjCHKJvA8-o20U5hnUwQD8/edit Semantic Technology Committee Business Meeting] — [https://docs.google.com/document/d/1A1kWKDrDQt3bi5C_PAgGfP3TOcPA7T5N-yROMZ_bqRQ/edit Community Ontology Repository Working Meeting]<br />
<br />
===Contacts=== <br />
*Lewis John McGibbney, Chair, lewis.j.mcgibbney [at] jpl [dot] nasa [dot] gov<br />
*Pier Luigi Buttigieg, Co-Chair, pbuttigi [at] mpi-bremen [dot] de<br />
*Zachary Robbins, ESIP Community Fellow, zjrobbin [at] NCSU [dot] edu<br />
|}<br />
<br />
==Vision of the Semantic Technologies Committee==<br />
#Promote research and development of semantic technologies in support of Earth science data discovery, dissemination, and analysis<br />
#Collaborate with ESIP members, working groups, clusters, and standing committees on semantic related topics<br />
#Foster sharing and reuse of ontologies and controlled vocabularies<br />
#To provide a collaborative environment for the development of ontologies and ontology-based standards<br />
#To maintain a long-term agenda and roadmap for evaluation of semantic technologies within ESIP<br />
#To collaborate with external agencies, on behalf of ESIP, in regards to semantic technologies<br />
<br />
<br />
==Github Collaboration Area==<br />
* [https://github.com/ESIPFed/stc SemTech Github Repository]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Semantic_Web_Ontology_Portal_Evaluation_Approach&diff=56480Semantic Web Ontology Portal Evaluation Approach2017-02-10T03:30:29Z<p>Graybeal: added reference to the current page on this topic</p>
<hr />
<div>= Introduction =<br />
<br />
<font color="red">This page is no longer the active planning document for evaluating possible ESIP ontoogy repository instances. The page you want for that is https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html.</font><br />
<br />
This wiki page supports ESIP's evaluation of semantic repository solutions in particular providing insight into;<br />
# '''what current and future ESIP Semantic Technologies Committee (STC) community requirements (CR) are''',<br />
# '''a comparative evaluation of different technology stacks/approaches'''; with the aim of assessing different solutions based upon how well they satisfy CR as defined within this document, and <br />
# '''a business cost justification model''' that could be used to justify funding semantic web technology stacks. <br />
<br />
All ESIP members (and anyone else with an account on this wiki) are encouraged to contribute towards this document.<br />
<br />
= Semantic Repository Implementation Requirements =<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
== Features/Services ==<br />
<br />
These are the functions we'd like to see offered by the repository: <br />
<br />
=== Ingest capabilities ===<br />
<br />
* It should be possible for a person with an ESIP account to upload their semantic resources to the repository<br />
* It should be possible for a person with an ESIP account to upload new versions of their semantic resources to the repository. <br />
<br />
=== Access capabilities ===<br />
<br />
* Publicly accessible resources in the should be accessible via a Permanent Identifier (PID) (such as a DOI or equivalent) at both the resource and individual concept level which implies namespaces, versioning, and redirect capabilities<br />
* When a Permanent Identifier technology dies (e.g., PURL's from OCLC) mechanisms to "fail over" to an alternate PID scheme relatively easily should be supported. This might be accomplished by supporting multiple PID technologies simultaneously and allowing resources to have multiple PID's at a variety of levels.<br />
<br />
=== Search capabilities ===<br />
<br />
==== User-specific search and update capabilities ====<br />
<br />
* A logged in user (i.e., one with an ESIP account) should be able to query to obtain a list of their own resources in the repository<br />
* A logged in user needs to be able to update their own information in the repository (i.e., profile including things like passwords, email addresses, etc.). Relevant updates need to proliferate to the resources that user has uploaded.<br />
<br />
==== General search and update capabilities ====<br />
<br />
* Users should be able to specify a term (e.g., seaIce) and have the portal return all concepts that include that term. The ontology or resource that the concept comes with should be included in the result and the ability to further examine that resource (definitions of the terms, other metadata such as usage constraints, version history, etc.). See [http://vocab.cc/v/search?query=publisher this set of results for a search for the term "publisher" in the site vocab.cc for examples.]<br />
<br />
=== Browse capabilities ===<br />
<br />
=== Display capabilities ===<br />
<br />
* Display a list of semantic resources (e.g., ontologies) <br />
* Display the terms and relationships for a particular version of a semantic resource<br />
<br />
=== Download capabilities ===<br />
<br />
=== Mapping capabilities ===<br />
<br />
=== Inferencing capabilities ===<br />
<br />
=== Query capabilities ===<br />
<br />
== Protocols ==<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
=== Ontology download formats ===<br />
<br />
=== Ontology upload formats ===<br />
<br />
=== URI format for concepts and artifacts ===<br />
<br />
=== API support ===<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
== Usability ==<br />
<br />
== Maintainability ==<br />
<br />
* It must be possible to migrate the content and functionality of the repository to new technologies as they change over time. For example, migrating from google code to github seemlessly...<br />
<br />
=== Ease of content submission ===<br />
<br />
=== Ease of content updates ===<br />
<br />
=== Documentation ===<br />
<br />
=== Responsiveness ===<br />
<br />
=== Reliability/Uptime ===<br />
<br />
== Authentication and Security ==<br />
<br />
What types of login features are supported?<br />
<br />
== Support for Teams and Roles ==<br />
<br />
Can teams be defined of multiple members? Can multiple members of a team edit the same ontology?<br />
<br />
== Cost ==<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
=== Installation ===<br />
<br />
=== Operations ===<br />
<br />
=== Maintenance ===<br />
<br />
= Comparative Evaluation of Portal Software =<br />
<br />
= Justifying Semantic Web Repository Business Costs =<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)<br />
<br />
= References =<br />
<br />
[1] ODM2 evaluation of MMI ORR: https://github.com/ODM2/ODM2/blob/07e4e30fc4d6763b8bcae771ffbb7228fc5a3f65/doc/ODM2Docs/concept_controlledvocabs.md</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Ontology_Repository_Evaluation_Roadmap&diff=53689Ontology Repository Evaluation Roadmap2016-04-26T22:00:02Z<p>Graybeal: /* Summary of Milestones */</p>
<hr />
<div>== Introduction ==<br />
<br />
This Ontology Repository Evaluation Roadmap is intended to lay out a candidate approach leading ESIP toward solutions for ontology repositories. <br />
<br />
The Roadmap is premised on the assessment that solutions are needed, and that ESIP is well situated to determine their requirements and identify a path toward sustainability.<br />
<br />
== Summary of Milestones ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left"<br />
|-<br />
! Date<br />
! Event<br />
! Milestone<br />
! Who<br />
|- <br />
| April 2016<br />
| (offline)<br />
| Agree on path to install ESIP BioPortal on AWS cloud <br />
| Line P, John G, Tom N<br />
|- <br />
| May 2016 <br />
| Semantic Committee mtg<br />
| finalize URLs for Community Ontology Repository deployment<br />
| Committee<br />
|-<br />
| May 2016 <br />
| Semantic Committee mtg<br />
| entrain repository services evaluation group/activity; present relevant approaches<br />
| (Ruth D?)<br />
|- <br />
| May 2016<br />
| Semantic Committee mtg<br />
| remove red warning text from COR site<br />
| John G<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Comparable repository installations available with commitment to keep operational for n years<br />
| Erin R, Tom N, Beth H, John G, Line P<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Present first real draft of [[Semantic Web Ontology Portal Evaluation Approach]]<br />
| Tom N, Beth H (having tasked the Committee with specific assignments)<br />
|- <br />
| August 2016 <br />
| Semantic Committee mtg<br />
| Show common ontologies, links, etc. in two repositories; assign test tasks to committee members<br />
| Line, John<br />
|-<br />
| September 2016<br />
| Semantic Committee mtg<br />
| Estimates for 2-year support for repositories provided to Semantic committee for review<br />
| Line P, John G, Erin R, Tom N, Beth H<br />
|- <br />
| October 2016<br />
| ? (some big event)<br />
| ESIP announces (press release) Earth Science Ontology Repository services and 1-year evaluation (includes 2-year service commitment, transition commitment, crowd-source evaluation, and creation of sustainability survey)<br />
| Erin R, Tom N, Beth H<br />
|-<br />
| 2016-2017<br />
| Winter meeting<br />
| Report out on progress and initial results; decide what adjustments are needed for evaluation and survey<br />
| Semantic Committee, Erin R<br />
|-<br />
| 2017<br />
| Summer meeting<br />
| Draft evaluation of repositories; completed analysis of sustainability survey and other sustainability issues<br />
| Semantic Committee, Erin R<br />
|-<br />
| 2017-2018<br />
| Winter meeting<br />
| Announcements: selected repository(ies); transition plan; service offerings and agreements<br />
| Erin R, Tom N, Beth H<br />
|}</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Ontology_Repository_Evaluation_Roadmap&diff=53688Ontology Repository Evaluation Roadmap2016-04-26T21:56:10Z<p>Graybeal: /* Summary of Milestones */ formatting</p>
<hr />
<div>== Introduction ==<br />
<br />
This Ontology Repository Evaluation Roadmap is intended to lay out a candidate approach leading ESIP toward solutions for ontology repositories. <br />
<br />
The Roadmap is premised on the assessment that solutions are needed, and that ESIP is well situated to determine their requirements and identify a path toward sustainability.<br />
<br />
== Summary of Milestones ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="left"<br />
|-<br />
! Date<br />
! Event<br />
! Milestone<br />
! Who<br />
|- <br />
| April 2016<br />
| (offline)<br />
| Agree on path to install ESIP BioPortal on AWS cloud <br />
| Line P, John G, Tom N<br />
|- <br />
| May 2016 <br />
| Semantic Committee mtg<br />
| finalize URLs for Community Ontology Repository deployment<br />
| Committee<br />
|-<br />
| May 2016 <br />
| Semantic Committee mtg<br />
| entrain repository services evaluation group/activity; present relevant approaches<br />
| (Ruth D?)<br />
|- <br />
| May 2016<br />
| Semantic Committee mtg<br />
| remove red warning text from COR site<br />
| John G<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Comparable repository installations available with commitment to keep operational for n years<br />
| John G<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Present first real draft of [[Semantic Web Ontology Portal Evaluation Approach]]<br />
| Tom, Beth (having tasked the Committee with specific assignments)<br />
|- <br />
| August 2016 <br />
| Semantic Committee mtg<br />
| Show common ontologies, links, etc. in two repositories; assign test tasks to committee members<br />
| Line, John<br />
|-<br />
| September 2016<br />
| Semantic Committee mtg<br />
| Estimates for 2-year support for repositories provided to Semantic committee for review<br />
| Line, John, Erin, Tom<br />
|- <br />
| October 2016<br />
| ? (some big event)<br />
| ESIP announces (press release) Earth Science Ontology Repository services and 1-year evaluation (includes 2-year service commitment, transition commitment, crowd-source evaluation, and creation of sustainability survey)<br />
| Erin, Tom, Beth<br />
|-<br />
| 2016-2017<br />
| Winter meeting<br />
| Report out on progress and initial results; decide what adjustments are needed for evaluation and survey<br />
| Semantic Committee, Erin<br />
|-<br />
| 2017<br />
| Summer meeting<br />
| Draft evaluation of repositories; completed analysis of sustainability survey and other sustainability issues<br />
| Semantic Committee, Erin<br />
|-<br />
| 2017-2018<br />
| Winter meeting<br />
| Announcements: selected repository(ies); transition plan; service offerings and agreements<br />
| Erin, Tom, Beth<br />
|}</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Ontology_Repository_Evaluation_Roadmap&diff=53687Ontology Repository Evaluation Roadmap2016-04-26T21:55:15Z<p>Graybeal: first draft</p>
<hr />
<div>== Introduction ==<br />
<br />
This Ontology Repository Evaluation Roadmap is intended to lay out a candidate approach leading ESIP toward solutions for ontology repositories. <br />
<br />
The Roadmap is premised on the assessment that solutions are needed, and that ESIP is well situated to determine their requirements and identify a path toward sustainability.<br />
<br />
== Summary of Milestones ==<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! Date<br />
| Event<br />
! Milestone<br />
| Who<br />
|- <br />
| April 2016<br />
| <br />
| Agree on path to install ESIP BioPortal on AWS cloud <br />
| Line P, John G, Tom N<br />
|- <br />
| May 2016 <br />
| Semantic Committee mtg<br />
| finalize URLs for Community Ontology Repository deployment<br />
| Committee<br />
|-<br />
| May 2016 <br />
| Semantic Committee mtg<br />
| entrain repository services evaluation group/activity; present relevant approaches<br />
| (Ruth D?)<br />
|- <br />
| May 2016<br />
| Semantic Committee mtg<br />
| remove red warning text from COR site<br />
| John G<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Comparable repository installations available with commitment to keep operational for n years<br />
| John G<br />
|- <br />
| July 2016<br />
| Summer meeting<br />
| Present first real draft of [[Semantic Web Ontology Portal Evaluation Approach]]<br />
| Tom, Beth (having tasked the Committee with specific assignments)<br />
|- <br />
| August 2016 <br />
| Semantic Committee mtg<br />
| Show common ontologies, links, etc. in two repositories; assign test tasks to committee members<br />
| Line, John<br />
|-<br />
| September 2016<br />
| Semantic Committee mtg<br />
| Estimates for 2-year support for repositories provided to Semantic committee for review<br />
| Line, John, Erin, Tom<br />
|- <br />
| October 2016<br />
| ? (some big event)<br />
| ESIP announces (press release) Earth Science Ontology Repository services and 1-year evaluation (includes 2-year service commitment, transition commitment, crowd-source evaluation, and creation of sustainability survey)<br />
| Erin, Tom, Beth<br />
|-<br />
| 2016-2017<br />
| Winter meeting<br />
| Report out on progress and initial results; decide what adjustments are needed for evaluation and survey<br />
| Semantic Committee, Erin<br />
|-<br />
| 2017<br />
| Summer meeting<br />
| Draft evaluation of repositories; completed analysis of sustainability survey and other sustainability issues<br />
| Semantic Committee, Erin<br />
|-<br />
| 2017-2018<br />
| Winter meeting<br />
| Announcements: selected repository(ies); transition plan; service offerings and agreements<br />
| Erin, Tom, Beth<br />
|}</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Semantic_Technologies&diff=53686Semantic Technologies2016-04-26T21:24:10Z<p>Graybeal: /* Collaboration Area Plan */ added link to Ontology Repository Evaluation Roadmap</p>
<hr />
<div>__NOTOC__<br />
{| width="100%" cellpadding="0" cellspacing="0" style="zborder-top:1px solid #aaaaaa; border-collapse: collapse;" <br />
<br />
|bgcolor="#FFFFBB" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
=== Get Involved===<br />
* [http://lists.esipfed.org/mailman/listinfo/esip-semanticweb Email List]<br />
* Meetings: <br />
** 4th Tuesday of each month at 4pm Eastern<br />
** GoToMeeting: https://www.gotomeeting.com/join/976796333<br />
** Phone Access: United States: +1 (872) 240-3212<br />
** Access Code: 976-796-333<br />
<br />
* '''Contact Chair:''' <br />
** Tom Narock, Chair, tnarock@marymount.edu<br />
** Beth Huffer, Co-Chair, beth@lingualogica.net<br />
<br />
|bgcolor="pink" style="border: 1px solid gray;padding-left:0.5em;padding-right:0.5em;" width="50%"|<br />
<br />
===Resources===<br />
[http://wiki.esipfed.org/index.php/Semantic_Web_Telecons Monthly Telecon Notes]<br><br />
<br />
Ontology Repositories<br />
* [http://esipsw.org/orr/ ESIP Testbed Ontology Portal]<br />
* [http://semanticportal.esipfed.org/ontologies Original Ontology Portal]<br />
* [http://wiki.esipfed.org/index.php/Semantic_Web_Ontology_Portal_Evaluation_Approach Ontology Portal Evaluation]<br />
<br />
|}<br />
<br />
==Vision of the Semantic Technologies Committee==<br />
#Promote research and development of semantic technologies in support of Earth science data discovery, dissemination, and analysis<br />
#Collaborate with ESIP members, working groups, clusters, and standing committees on semantic related topics<br />
#Foster sharing and reuse of ontologies and controlled vocabularies<br />
#To provide a collaborative environment for the development of ontologies and ontology-based standards<br />
#To maintain a long-term agenda and roadmap for evaluation of semantic technologies within ESIP<br />
#To collaborate with external agencies, on behalf of ESIP, in regards to semantic technologies<br />
<br />
==2015-2020 Strategic Plan Goals==<br />
* The committee's strategic plan is available here: [http://wiki.esipfed.org/index.php/Strategic_Vision Semantic Technologies Strategic Vision]<br />
<br />
Resources for ESIP's overall Strategic Plan: <br />
* [[2015-2020_Strategic_Plan | 2015-2020 Strategic Plan Executive Summary]] <br> <br />
* [https://docs.google.com/spreadsheets/d/16f8heiZX3KoLCPfxMKTbROiG-es6y2I7m9zkuXP-964/edit#gid=0 Strategic Plan Roadmap] <br><br />
<br />
==Collaboration Area Plan==<br />
<br />
Liaisons to external groups<br />
* Ruth Duerr - EarthCube Semantics Working Group<br />
* [[User:Brandonnodnarb|Brandon Whitehead]] - OGC and RDA communities; with a particular focus on GeoSciML, ESD WG, HydroWG, and RDA Provenance Group<br />
* Soren Scott - RDA Provenance Working Group<br />
* Stephen Richard - RDA Vocab Services, Terminology IG, and DataType Registry Working Groups<br />
* Stace Beaulieu - USGS CDI Semantic Web Working Group <br />
* Adam Shepherd - The Ontolog Community <br />
* Lewis McGibbney - W3C+OGC Spatial Data on the Web (SDW) <br />
* Bhaskar Ramachandran - The International Association for Ontology and its Applications (IAOA), http://www.iaoa.org/ <br />
* Pascal Hitzler - Ontology Design & Patterns Association <br />
* John Graybeal - Lead of MMI ORR, BioPortal projects<br />
<br />
===Current Projects and Collaborations===<br />
<br />
Semantic Projects in which Committee members are involved in can be found in [[Strategic_Vision#Current_Projects|this section]] of the Strategic Vision document.<br />
<br />
Current Collaboration Areas<br />
# We are working with [[Cloud_Computing | ESIP's Cloud Computing Cluster]] to explore efficient and extensible means of hosting ESIP-wide semantic resources<br />
# We are evaluating which ontology portal features (mappings, alignment, visualization, registering, etc.) are of need to the broad Earth science community. Currently, we have two versions of the BioPortal software running that have been tailored to the Earth science environment. We are designing an ESIP-wide [[Semantic_Web_Ontology_Portal_Evaluation_Approach | evaluation]] to understand what the community needs and what resources are necessary to support those needs.<br />
# We are considering how to establish an [[Ontology Repository Evaluation Roadmap]].<br />
# We are evaluating what it means to be a "good" ontology and what [[Ontology_Governance|governance]] looks like for community developed and maintained semantic resources (ontologies and taxonomies)<br />
# In conjunction with ESIP's [[Products_and_Services| Products and Services]] we are helping to evaluate software readiness levels and software reuse. <br />
<br />
[[category:CollabArea]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Strategic_Vision&diff=53685Strategic Vision2016-04-26T21:20:57Z<p>Graybeal: /* External (to ESIP) Projects to which Cluster members are contributing */ added MMI ORR, cleaned up link formatting</p>
<hr />
<div>== Introduction ==<br />
The ESIP Semantic Web cluster is approaching 10 years old and is one of the oldest clusters within ESIP. During this decade of existence the tide has shifted to federal agencies such as NASA, DOE, and NSF CISE fully embracing semantic technologies. The amount of Linked Data is increasing at a staggering rate. There are new improvements for dataset descriptions (e.g. time and space) within commercial efforts such as schema.org. Semantic Web Technologies are now a mainstay in the geoscience information and data management community.<br />
<br />
The time has come to move beyond prototypes and proofs of concept. To this end, the Semantic Web Cluster is developing a Strategic Vision and Road Map for the next 3 to 5 years. We aim to create a living document that will synthesize existing semantic efforts and guide future research and development. We want to coalesce our broad knowledge base and develop towards a common long term cyberinfrastructure. We would like to continue the tradition of the geosciences being an early adopter and feedback loop for the broader Semantic Web community.<br />
<br />
In organizations such as the Research Data Alliance there is no semantics cluster or semantics working group. This is because Semantic Technologies permeate all aspects of data and information management. Within ESIP, we would also like to evolve to a position where these technologies and methodologies are similarly common place. To achieve these goals the Cluster will focus its efforts around<br />
<br />
== Current Projects == <br />
<br />
=== Test Bed Projects ===<br />
<br />
=== Funding Friday Projects ===<br />
<br />
[[Semantic Models for the ESIP Community]] (Brandon 16:20, 29 August 2015 (MDT))<br />
<br />
=== External (to ESIP) Projects to which Cluster members are contributing ===<br />
* '''Global Change Master Directory (GCMD) Ontology''' - A GCMD Platform-Instrument-Sensor ontology that utilizes existing GCMD keyword hierarchies and SKOS concepts, as of 8/2015 the ontology was under review by NASA and not publicly available<br />
<br />
* [https://data.globalchange.gov/|'''Global Change Information System'''] - from the GCIS website "The GCIS is an open-source, web-based resource for traceable, sound global change data, information, and products. Designed for use by scientists, decision makers, and the public, the GCIS provides coordinated links to a select group of information products produced, maintained, and disseminated by government agencies and organizations. As well as guiding users to global change research products selected by the 13 member agencies, the GCIS serves as a key access point to assessments, reports, and tools produced by the USGCRP. The GCIS is managed, integrated, and curated by USGCRP."<br />
<br />
* [http://semanticportal.esipfed.org|'''ESIP Ontology Portal'''] - an ESIP hosted ontology portal, based off of BioPortal, to house and align Earth science ontologies<br />
<br />
* [http://mmisw.org/orr|'''MMI's Ontology Registry and Repository'''] - The Marine Metadata Interoperability project built and maintains this earth science ontology repository for the use of the marine and earth science communities. <br />
<br />
* [http://toolmatch.esipfed.org/index|'''ToolMatch'''] - a semantic-based system for matching data to software tools and answering use cases such “I have data and need to know which tools I can use”, with an example being “I just downloaded an AIR Level 2 Standard retrieval file. How can I look at it?”. In addition to the project homepage there is also the [ http://github.com/ESIPFed/Toolmatch ToolMatch GitHub Repository ]<br />
<br />
* [http://www.geolink.org|'''GeoLink'''] - The GeoLink project brings together experts from the geosciences, computer science, and library science in an effort to develop Semantic Web components that support discovery and reuse of data and knowledge. GeoLink's participating repositories include content from field expeditions, laboratory analyses, journal publications, conference presentations, theses/reports, and funding awards that span scientific studies from marine geology to marine ecosystems and biogeochemistry to paleoclimatology.<br />
<br />
* BCube - The BCube project is focused on demonstrating that brokering technologies can facilitate interoperability. As a part of this project, a web-scale crawler has been developed that finds and characterizes data and web service descriptions found on the web. Having scanned more than a million documents so far, a triple store containing these contents is being populated and will be available publicly.<br />
<br />
* ClearEarth - The ClearEarth project is using NLP/ML processes to auto-generate semantic resources. In particular we are trying to get at processes (e.g., freezing of sea water to form sea ice)<br />
<br />
In creating this inventory, we also aim to identify dependencies - both internal and external. That is, what projects are affected by or leverage other projects. Can we make enhancements in multiple areas through advances on certain topics? For instance, one of the TestBed projects (Marshall Ma) could be enhanced if more ontologies were available via the ESIP Ontology Portal<br />
<br />
=== Action Items ===<br />
# Identify internal and external dependencies<br />
<br />
== The Linked Science Cloud ==<br />
<br />
Linked Science Cloud or Linked Earth Science Cloud?<br />
<br />
The amount of Linked Data is increasing at a staggering rate. Yet, while there exists a handful of science datasets in the Linked Data Cloud, the potential for continuing to publish and interlink geoscience datasets is immense. To this end, the Cluster will coordinate the creation of the Linked Science Cloud.<br />
<br />
=== Action Items ===<br />
# Identify existing geoscience Linked Data sets which could be part of the Linked Science Cloud<br />
# Identify potential links between these datasets<br />
# Identify available GeoSPARQL endpoints for demonstration and evaluation of spatial and spatio-temporal queries<br />
<br />
== Provenance == <br />
<br />
The recent W3C PROV-O recommendation has provided an accessible solution for including provenance in semantic information systems. Moreover, the Cluster recognizes that provenance is becoming essential to many geoscience applications. To this end, semantic provenance should be an essential component of our semantic systems. The Cluster will take semantic provenance as a high priority when evaluating and planning future projects.<br />
<br />
== Ontology Development and Ontology Portal==<br />
<br />
not to go straight to encoding of an ontology…but rather to start with conceptual and information models to have a diversity of choices of how to encode. Need to think about Syntax, semantics, and pragmatics. Pragmatics for use. Keeping the human in the loop. Cognitive science aspect. Time to return to process ontologies (not just things, but also processes) (from peter fox's comments) NEED TO EXPAND ON THIS<br />
<br />
Also need to keep in mind the multiple perspectives on ontology engineering. There are domain ontologies and there is a relatively new methodology around so-called Ontology Design Patterns. The cluster should follow the broader semantic web community and watch as the current research in these areas<br />
<br />
=== Open Questions ===<br />
# How do we measure uptake and usage of ontologies in the portal?<br />
# What are reasonable metrics and goals in this area?<br />
<br />
== Ontology Governance ==<br />
The Cluster will adopt some form of the [ http://www.obofoundry.org/crit.shtml The Open Biological and Biomedical Ontologies] principals for ontology governance. Specifically how this is to be accomplished is still open for debate?<br />
<br />
== Long Term Cyberinfrastructure ==<br />
<br />
At present, there is a known challenge in transitioning from prototype applications to production quality cyberinfrastructure. There is often difficulty in identifying long term hosting and maintenance for our Semantic Web projects. To be fair, this is a common issue among most grant funded information technology projects. The Semantic Web Cluster, and ESIP in general, are committed to identifying new and promising solutions. We are continually working with [ Products_and_Services | ESIP Products and Services ] to explore possibilities.<br />
<br />
We have also identified a need to encourage real-time sharing of progress from Testbed projects with the broader ESIP community. The Semantic Web Cluster is exploring the use of Semantic Technologies in this area and will serve as a willing test bed for further development.<br />
<br />
=== Open Questions ===<br />
# Are we following all of the [http://wiki.obofoundry.org/wiki/index.php/OBO_Foundry_Principles_2008 OBO Foundry principals?] If no, then which subset will the Cluster abide by?<br />
<br />
== Ideas, Thoughts, Comments ==<br />
* Being a visual person, I think it would be a good idea to have a diagram of the different areas the cluster is exploring. Perhaps a network diagram with areas as nodes and relationships between the areas as named edges. It would also be useful to add the names of people working in that area to each node.<br />
* How do we evaluate/benchmark our progress along this road map?</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=SW_OPortal_Discussion&diff=53234SW OPortal Discussion2016-03-25T06:32:35Z<p>Graybeal: /* Ontology Portal Evaluation Approach */ reformatted headers</p>
<hr />
<div>= Ontology Portal Evaluation Approach: Introduction =<br />
<br />
This page supports ESIP's evaluation of semantic repository solutions. It considers both comparative evaluations of different technology approaches, and a business cost justification model that could be used to justify funding semantic web repositories. All ESIP members (and anyone else with an account on this wiki) are welcome to contribute.<br />
<br />
= Comparing Semantic Repository Implementations =<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
== Features/Services ==<br />
<br />
These are the functions offered by the repository. <br />
<br />
=== Ingest capabilities ===<br />
<br />
=== Search capabilities ===<br />
<br />
How detailed are the search options in the UI? Are faceted searches available? <br />
<br />
=== Browse capabilities ===<br />
<br />
=== Display capabilities ===<br />
<br />
What options are available for displaying and viewing concepts, ontologies, and metadata?<br />
<br />
=== Download capabilities ===<br />
<br />
=== Mapping capabilities ===<br />
<br />
=== Inferencing capabilities ===<br />
<br />
=== Query capabilities ===<br />
<br />
== Protocols ==<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
=== Ontology download formats ===<br />
<br />
=== Ontology upload formats ===<br />
<br />
=== URI format for concepts and artifacts<br />
<br />
=== API support ===<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
== Usability ==<br />
<br />
=== Ease of content submission ===<br />
<br />
=== Ease of content updates ===<br />
<br />
=== Documentation ===<br />
<br />
=== Responsiveness ===<br />
<br />
=== Reliability/Uptime ===<br />
<br />
== Authentication and Security ==<br />
<br />
What types of login features are supported?<br />
<br />
== Support for Teams and Roles ==<br />
<br />
Can teams be defined of multiple members? Can multiple members of a team edit the same ontology?<br />
<br />
== Cost ==<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
=== Installation ===<br />
<br />
=== Operations ===<br />
<br />
=== Maintenance ===<br />
<br />
= Justifying Semantic Web Repository Business Costs =<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)<br />
<br />
= References =<br />
<br />
[1] ODM2 evaluation of MMI ORR: https://github.com/ODM2/ODM2/blob/07e4e30fc4d6763b8bcae771ffbb7228fc5a3f65/doc/ODM2Docs/concept_controlledvocabs.md</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=SW_OPortal_Discussion&diff=53233SW OPortal Discussion2016-03-25T06:28:49Z<p>Graybeal: /* Justifying Semantic Web Repository Business Costs */ aded references</p>
<hr />
<div>= Ontology Portal Evaluation Approach =<br />
<br />
This page supports ESIP's evaluation of semantic repository solutions. It considers both comparative evaluations of different technology approaches, and a business cost justification model that could be used to justify funding semantic web repositories. All ESIP members (and anyone else with an account on this wiki) are welcome to contribute.<br />
<br />
== Comparing Semantic Repository Implementations ==<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
=== Features/Services ===<br />
<br />
These are the functions offered by the repository. <br />
<br />
==== Ingest capabilities ====<br />
<br />
==== Search capabilities ====<br />
<br />
How detailed are the search options in the UI? Are faceted searches available? <br />
<br />
==== Browse capabilities ====<br />
<br />
==== Display capabilities ====<br />
<br />
==== Download capabilities ====<br />
<br />
==== Mapping capabilities ====<br />
<br />
==== Inferencing capabilities ====<br />
<br />
==== Query capabilities ====<br />
<br />
<br />
=== Protocols ===<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
==== Ontology download formats ====<br />
<br />
==== Ontology upload formats ====<br />
<br />
==== URI format for concepts and artifacts<br />
<br />
==== API support ====<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
=== Usability ===<br />
<br />
==== Ease of content submission ====<br />
<br />
==== Ease of content updates ====<br />
<br />
==== Documentation ====<br />
<br />
==== Responsiveness ====<br />
<br />
==== Reliability/Uptime ====<br />
<br />
=== Authentication and Security ===<br />
<br />
What types of login features are supported?<br />
<br />
=== Support for Teams and Roles ===<br />
<br />
Can teams be defined of multiple members? Can multiple members of a team edit the same ontology?<br />
<br />
=== Cost ===<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
==== Installation ====<br />
<br />
==== Operations ====<br />
<br />
==== Maintenance ====<br />
<br />
== Justifying Semantic Web Repository Business Costs ==<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)<br />
<br />
== References ==<br />
<br />
[1] ODM2 evaluation of MMI ORR: https://github.com/ODM2/ODM2/blob/07e4e30fc4d6763b8bcae771ffbb7228fc5a3f65/doc/ODM2Docs/concept_controlledvocabs.md</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=SW_OPortal_Discussion&diff=53232SW OPortal Discussion2016-03-25T06:18:36Z<p>Graybeal: /* Usability */ adding categories</p>
<hr />
<div>= Ontology Portal Evaluation Approach =<br />
<br />
This page supports ESIP's evaluation of semantic repository solutions. It considers both comparative evaluations of different technology approaches, and a business cost justification model that could be used to justify funding semantic web repositories. All ESIP members (and anyone else with an account on this wiki) are welcome to contribute.<br />
<br />
== Comparing Semantic Repository Implementations ==<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
=== Features/Services ===<br />
<br />
These are the functions offered by the repository. <br />
<br />
==== Ingest capabilities ====<br />
<br />
==== Search capabilities ====<br />
<br />
How detailed are the search options in the UI? Are faceted searches available? <br />
<br />
==== Browse capabilities ====<br />
<br />
==== Display capabilities ====<br />
<br />
==== Download capabilities ====<br />
<br />
==== Mapping capabilities ====<br />
<br />
==== Inferencing capabilities ====<br />
<br />
==== Query capabilities ====<br />
<br />
<br />
=== Protocols ===<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
==== Ontology download formats ====<br />
<br />
==== Ontology upload formats ====<br />
<br />
==== URI format for concepts and artifacts<br />
<br />
==== API support ====<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
=== Usability ===<br />
<br />
==== Ease of content submission ====<br />
<br />
==== Ease of content updates ====<br />
<br />
==== Documentation ====<br />
<br />
==== Responsiveness ====<br />
<br />
==== Reliability/Uptime ====<br />
<br />
=== Authentication and Security ===<br />
<br />
What types of login features are supported?<br />
<br />
=== Support for Teams and Roles ===<br />
<br />
Can teams be defined of multiple members? Can multiple members of a team edit the same ontology?<br />
<br />
=== Cost ===<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
==== Installation ====<br />
<br />
==== Operations ====<br />
<br />
==== Maintenance ====<br />
<br />
== Justifying Semantic Web Repository Business Costs ==<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=SW_OPortal_Discussion&diff=53231SW OPortal Discussion2016-03-25T06:16:23Z<p>Graybeal: /* Reliability/Uptime */ added additional categories</p>
<hr />
<div>= Ontology Portal Evaluation Approach =<br />
<br />
This page supports ESIP's evaluation of semantic repository solutions. It considers both comparative evaluations of different technology approaches, and a business cost justification model that could be used to justify funding semantic web repositories. All ESIP members (and anyone else with an account on this wiki) are welcome to contribute.<br />
<br />
== Comparing Semantic Repository Implementations ==<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
=== Features/Services ===<br />
<br />
These are the functions offered by the repository. <br />
<br />
==== Ingest capabilities ====<br />
<br />
==== Search capabilities ====<br />
<br />
How detailed are the search options in the UI? Are faceted searches available? <br />
<br />
==== Browse capabilities ====<br />
<br />
==== Display capabilities ====<br />
<br />
==== Download capabilities ====<br />
<br />
==== Mapping capabilities ====<br />
<br />
==== Inferencing capabilities ====<br />
<br />
==== Query capabilities ====<br />
<br />
<br />
=== Protocols ===<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
==== Ontology download formats ====<br />
<br />
==== Ontology upload formats ====<br />
<br />
==== URI format for concepts and artifacts<br />
<br />
==== API support ====<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
=== Usability ===<br />
<br />
==== Documentation ====<br />
<br />
==== Responsiveness ====<br />
<br />
==== Reliability/Uptime ====<br />
<br />
=== Authentication and Security ===<br />
<br />
What types of login features are supported?<br />
<br />
=== Support for Teams and Roles ===<br />
<br />
Can teams be defined of multiple members? Can multiple members of a team edit the same ontology?<br />
<br />
=== Cost ===<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
==== Installation ====<br />
<br />
==== Operations ====<br />
<br />
==== Maintenance ====<br />
<br />
== Justifying Semantic Web Repository Business Costs ==<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=SW_OPortal_Discussion&diff=53230SW OPortal Discussion2016-03-25T06:12:45Z<p>Graybeal: first outline</p>
<hr />
<div>= Ontology Portal Evaluation Approach =<br />
<br />
This page supports ESIP's evaluation of semantic repository solutions. It considers both comparative evaluations of different technology approaches, and a business cost justification model that could be used to justify funding semantic web repositories. All ESIP members (and anyone else with an account on this wiki) are welcome to contribute.<br />
<br />
== Comparing Semantic Repository Implementations ==<br />
<br />
In general in this document:<br />
* 'ontology' refers to any semantic artifact, whether expressed in OWL/RDF, another OWL representation, or a simpler form like Excel or CSV that can be converted into a semantic artifact.<br />
* URI is used to mean a unique web identifier, aka IRI; it usually but not always is a URL.<br />
<br />
=== Features/Services ===<br />
<br />
These are the functions offered by the repository. <br />
<br />
==== Ingest capabilities ====<br />
<br />
==== Search capabilities ====<br />
<br />
How detailed are the search options in the UI? Are faceted searches available? <br />
<br />
==== Browse capabilities ====<br />
<br />
==== Display capabilities ====<br />
<br />
==== Download capabilities ====<br />
<br />
==== Mapping capabilities ====<br />
<br />
==== Inferencing capabilities ====<br />
<br />
==== Query capabilities ====<br />
<br />
<br />
=== Protocols ===<br />
<br />
Protocols describe how the repository makes its information, submissions, and entries available: what syntax, semantics, and specifications are supported in the data and commands that go into the system, and come out of it?<br />
<br />
==== Ontology download formats ====<br />
<br />
==== Ontology upload formats ====<br />
<br />
==== URI format for concepts and artifacts<br />
<br />
==== API support ====<br />
<br />
How many/which features are available to other applications via API calls? Are these calls REST-based?<br />
<br />
How is the URI for each concept in the repository represented? How is the URI for each artifact represented? Are the offered URIs versioned, unversioned, or both?<br />
<br />
=== Usability ===<br />
<br />
==== Documentation ====<br />
<br />
==== Responsiveness ====<br />
<br />
==== Reliability/Uptime ====<br />
<br />
=== Cost ===<br />
<br />
Costs are given in labor hours and funds required to start and operate the service.<br />
<br />
==== Installation ====<br />
<br />
==== Operations ====<br />
<br />
==== Maintenance ====<br />
<br />
== Justifying Semantic Web Repository Business Costs ==<br />
<br />
(see the [SW OPortal Discussion:Talk|Discussion] page for ideas.)</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52703P&S Telecon - January 19, 20162016-02-11T06:53:25Z<p>Graybeal: /* Technology Evaluation Framework Final Report */ really fixed it...</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
* [http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
* [http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
* [https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
* [http://wiki.esipfed.org/images/b/b6/TRL_Evaluation_Structure_-_Development_Branch.xlsx TEF TRL Development Spreadsheet] - an archival copy of a development path (with Fitness questions) not chosen<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52702P&S Telecon - January 19, 20162016-02-11T06:51:52Z<p>Graybeal: /* Technology Evaluation Framework Final Report */ prettifying</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
* [http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
* [http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
* [https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
* [http://wiki.esipfed.org/index.php/File:TRL_Evaluation_Structure_-_Development_Branch.xlsx TEF TRL Development Spreadsheet] - an archival copy of a development path (with Fitness questions) not chosen<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52701P&S Telecon - January 19, 20162016-02-11T06:51:16Z<p>Graybeal: /* Technology Evaluation Framework Final Report */ fixed link to uploaded file</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
[http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
[http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
[https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
[http://wiki.esipfed.org/index.php/File:TRL_Evaluation_Structure_-_Development_Branch.xlsx TEF TRL Development Spreadsheet] - an archival copy of a development path (with Fitness questions) not chosen<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52700P&S Telecon - January 19, 20162016-02-11T06:48:39Z<p>Graybeal: /* Technology Evaluation Framework Final Report */ added archival copy of development file</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
[http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
[http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
[https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
[[File:TRL_Evaluation_Structure_-_Development_Branch.xlsx]] - an archival copy of a development path (with Fitness questions) not chosen<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=File:TRL_Evaluation_Structure_-_Development_Branch.xlsx&diff=52699File:TRL Evaluation Structure - Development Branch.xlsx2016-02-11T06:45:53Z<p>Graybeal: Development branch version of TRL Evaluation file, containing additional questions for Fitness.</p>
<hr />
<div>Development branch version of TRL Evaluation file, containing additional questions for Fitness.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52698P&S Telecon - January 19, 20162016-02-11T06:44:18Z<p>Graybeal: fixed oopsie</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
[http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
[http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
[https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_January_19,_2016&diff=52697P&S Telecon - January 19, 20162016-02-11T06:43:01Z<p>Graybeal: /* Technology Evaluation Framework Final Report */</p>
<hr />
<div>[https://docs.google.com/document/d/1cgq1mV23SOAuGJYUboRP_1CBkJmxqWVHs9v0ZjFUaS8/edit?usp=sharing Google Doc Notes]<br />
<br />
[https://esipfed.webex.com/esipfed/ldr.php?RCID=1d3de2c45ad2b495561511810d9c2bba Webex Recording Streaming Access]<br />
<br />
[https://esipfed.webex.com/esipfed/lsr.php?RCID=f538be2fe4a01de24d3e236c74a5bfa1 Webex Recording Download] (note: to play the downloaded recording, you will need to install the [https://www.webex.com/play-webex-recording.html Webex ARF Player].)<br />
<br />
[[File:Example.jpg]]==Technology Evaluation Framework Final Report==<br />
<br />
TEF final report out and recommendations for the TEF given by John Graybeal. <br />
<br />
[http://wiki.esipfed.org/images/7/7d/ESIP_Technology_Evaluation_Framework_Recommendations_Slides.pdf Presentation Slides (pdf)]<br />
<br />
[http://wiki.esipfed.org/images/7/73/ESIP_Technology_Evaluation_Framework_Recommendations.pdf Final Report]<br />
<br />
[https://github.com/ESIPFed/technology-evaluation-framework TEF TRL Spreadsheet]<br />
<br />
Please read the provided documents and watch the first 20 minutes of the archived recording for the recommendations based on the development of the spreadsheet and the feedback from the evaluation teams. <br />
<br />
Final outcome is that the evaluation teams felt that the TEF-generated TRL score matched what they felt was an appropriate TRL for the project. Feedback from the evaluation teams indicated a need for some customization based on the kind of technology evaluated and guidance on handling situations where some kinds of information aren't, or can't be provided, by the PIs, such as source code, or where the evaluator felt the question was outside their knowledge/expertise. The larger question is to find a balance between repeatability and customization.<br />
<br />
No specific discussion for modifying the TEF for the next AIST evaluation round.<br />
<br />
==AIST updates from the Winter 2016 meeting==<br />
<br />
An update from Annie Burgess on the AIST evaluation session.<br />
<br />
From Mike Little: there's room to improve but impressed with the first evaluation round and will continue for another AIST evaluation round.<br />
<br />
There was a lot of discussion in the room and a good mix of people, computer scientists, managers, etc. A question of whether we could create a template for software evaluation and interest in creating and refining one as well as interest in using one. Also interest in comparing other sources of evaluation recommendations against those used for the TEF (sources listed in the report document).<br />
<br />
==New or Ongoing Evaluation Efforts==<br />
<br />
P&S awarded two new testbed projects in December 2015, one through the Disaster cluster and one through the Semantic Web Committee.<br />
<br />
We discussed the evaluation needs of both. For the Semantic Web testbed, they will be looking at current practices for evaluating ontologies and P&S and ESIP staff will be working with them to coordinate an evaluation process for those knowledge artifacts. The Disaster project is interested in data evaluation and possible use of the Data Maturity Matrix from the Data Stewardship committee. <br />
<br />
Data Maturity Matrix References:<br />
<br />
[http://live.commons.esipfed.bluedotapps.org/node/7956 Summer 2015 Session]<br />
<br />
[https://figshare.com/articles/NCDC_CICSNC_SDSMM_Template/1211954 template on figshare]<br />
<br />
Long-term maintenance and improvements for the Evaluation process, either with the TEF or either of the outcomes of the above testbed projects, will take additional effort. We should see who in ESIP is interested in the topics and in helping to identify evaluation needs and processes. ESIP hasn't been a longterm maintainer of projects previously, but will need to identify someone to handle the ongoing maintenance of the TEF at least through upcoming AIST evaluation rounds. <br />
<br />
Ken Keiser noted that EarthCube is also working to develop a testbed activity and evaluation processes for that community. There's interest in building off of lessons learned and products developed by ESIP for that effort with additional evaluation needs targeted at interoperability and re-use.<br />
<br />
In addition, there's earlier work from ESIP members on infusion potential evaluation, a self-assessment process from 4-5 years ago with Peter Fox and Chris Lynnes. Also efforts from ESDSWG (Karen Moe) as well. (References to come.) See also Bob Downs' [http://datascience.codata.org/articles/abstract/10.2481/dsj.009-007/ work] on reuse readiness levels presented at the winter meeting.<br />
<br />
We are (Soren Scott & Anne Wilson) discussing software evaluation rubrics and progressions through the Science Software cluster and BESSIG. John Graybeal noted that there aren't currently rubrics for that now. For BESSIG, that discussion will take place at the February meeting. We may also want to consider a cross-cluster working group, with members of the Science Software cluster, the Disasters cluster (stated interest in evaluating services) and Data Stewardship to start.<br />
<br />
==OGC 12/13 Testbed Update==<br />
<br />
The initial discussion came out of the Testbed session at the 2016 Winter meeting (Christine White and George Percival (OGC)). ESIP members can participate in OGC's Testbed 12 but the RFP deadline has passed so that is unfunded participation. Funding is available for participation in Testbed 13.<br />
<br />
We will continue the discussions, particularly as they relate to OGC Testbed 13, in early February.<br />
<br />
==Action Items==<br />
<br />
# Find resources for earlier infusion potential work;<br />
# Continue discussions with the Semantic Web and Disaster testbed participants about their evaluation needs and process development;<br />
# Look for other ESIP members interested in participating in a cross-cluster effort related to software/technology evaluation;<br />
# Participate in the OGC Testbed 12 & 13 participation and potential ESIP testbed integrations (early February);<br />
# Co-chair nominations and election.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=ESIP_Testbed_Amazon_Web_Services_Best_Practices&diff=50483ESIP Testbed Amazon Web Services Best Practices2015-07-17T16:40:43Z<p>Graybeal: /* Step 4: Get started with the EC2 instances */ added advice about instance costs</p>
<hr />
<div>This page outlines best practices, lessons learned, insights, and anything else relevant to deploying testbed instances on Amazon Web Services. This initial content describes the experience of the Discovery Cluster in deploying the Esri Geoportal Server on an Amazon instance as part of the [[Discovery Testbed Work Plan]]. <br />
<br />
== Steps to deploy an instance ==<br />
===Step 1: Create an AWS account===<br />
You'll need to go to the [http://aws.amazon.com/console/ Amazon Web Services website] and create an account. Note that you will need to associate your account with a payment method - this personal and independent account needs to be on file with Amazon as a backup, and Amazon will also use this account info to verify your identify. In Step 2, you will be added to the ESIP Consolidated billing account, and that is where the instance charging will be applied. So as long as you don't sign up for services that are outside the scope of the consolidated billing, your account on file should not be charged.<br />
<br />
After creating an account, Amazon will call you to verify your identity. For this to go most smoothly, recommendation is to use a phone number that does not have an extension associated with it.<br />
<br />
Be aware that all of the account activity will be subsumed under the ESIP framework, so if you have an existing Amazon account that you use for other purposes, you should create a new account for ESIP use.<br />
<br />
===Step 2: Consolidated Billing===<br />
Contact Erin Robinson and request that she add you to the ESIP AWS Consolidated billing account. This account should cover all your activity on AWS except [http://docs.amazonwebservices.com/AmazonDevPay/latest/DevPayGettingStartedGuide/Welcome.html?r=5486 Amazon DevPay].<br />
<br />
===Step 3: Set up an EC2 instance account===<br />
Once you have an AWS account, you will need to create an EC2 account. When you click on the EC2 tab from the AWS Management Console, you will be prompted to sign in or sign up. Proceed with signing up.<br />
<br />
===Step 4: Get started with the EC2 instances===<br />
Brief notes: US East instances are typically less expensive than West instances. Linux instances are less expensive than Windows, but hearsay is that support is better for Windows. <br />
<br />
There is very good step-by-step documentation on how to create and launch an instance - see the [http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/Welcome.html?r=2500 Amazon Getting Started Guide].<br />
<br />
As you review instance costs, you will see that the short-term or spot instances tend to have higher costs per compute cycle than long-term agreements. Also, some common resource combinations are only available in a long-term agreement. It is also the case that spot instance pricing can change, sometimes drastically, as demand for them varies. As this is being written, the shortest long-term agreement is 1 year, but cost savings can be more than 50% over spot instances. Depending on the schedules in your project, pre-purchasing a long-term instance may be the most cost-effective strategy, even if some of those cycles are unused at the end of the contract.<br />
<br />
===Step 5: Create and manage images (optional) ===<br />
After you've deployed an instance and done some work on your instance (e.g. deploy software, configure users, etc.) you may want to preserve that work by creating an image. Conceptually, creating the image works the same as creating an image using VM-based snapshot tools. Documentation for how to do this is available at [http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/Tutorial_CreateImage.html Creating an Image from a Running Instance]. '''IMPORTANT:''' Delete unused images, as the consolidated billing account will be charged for space stored on the Volumes associated with images).<br />
<br />
=== Step 6: How to Open Ports so you can access web apps deployed on instances (optional)===<br />
If you want external users to be able to access web (or other) applications that are hosted on your instance, you will need to configure the port access. There are two places where the ports will need to be configured: first in your amazon instance through the AWS Management Console, and also on the instance itself.<br />
<br />
For the configuration in the AWS Management Console, click on your EC2 instance. In the left navigation window, there is a section called “Security Groups” - click on this. The rules associated with your security group are displayed in the window at the bottom of the screen. You can add ports and access rules here; for example, a web application that requires port 8080 to be open would be added as shown in the following:<br />
<br />
[[File:openPorts1.png|200px|thumb|none|click to enlarge]]<br />
<br />
For the configuration on the Amazon instance, you will likely also need to configure ports. This section describes opening ports on a Windows Server 2008 R2 SP1 instance; for other instances, there are different methods.<br />
* Open the Windows Firewall with Advance Security menu:<br />
[[File:openPorts2.png|200px|thumb|none|click to enlarge]]<br />
* In the resulting window, select “Inbound Rules” from the left menu, and then click “New Rule” from the far right window. In the resulting dialog, select a new rule for “ports” - see below. Then click Next.<br />
[[File:openPorts3.png|200px|thumb|none|click to enlarge]]<br />
* In the next window, enter the "Specific Ports" for which you want to apply the rule. Click Next. <br />
* Now determine what should happen – e.g., “Allow the connection” and click Next.<br />
* You can accept the defaults for the rest of the settings (unless you have a reason not to), except where you are prompted to enter a name for the rule. Enter whatever name adequately describes your rule.<br />
<br />
You can following these same instructions for opening outbound ports, using the "Outbound Rules" option from the left menu.<br />
<br />
== Notes specific to the Discovery Cluster Testbed deployment ==<br />
===Instance details===<br />
In this deployment, Christine White worked to install the base software for the Esri Geoportal Server 1.2. It was deployed on a Windows Server 2008 R2 SP1 instance, configured with a 'Small' size, based on East Coast hosting resources. Estimated pricing for such an instance is reportedly ~ $0.115/hour, with one elastic IP address - see [http://aws.amazon.com/ec2/pricing/ EC2 Pricing].<br />
<br />
You can download a .zip file mp4 video of the deployment (warning: not so exciting, but at least its short), here: [[File:discovery_AWS_instance.zip]].<br />
<br />
The Geoportal Server deployment is accessible at http://23.23.211.222:8080/geoportal. As an anonymous user, you can search for resources using the Search tab (although not many are registered yet, just some ArcGIS Server services for test purposes). User logins will be added for testbed users interested in contributing/testing service endpoints - to become a user of the geoportal, [[User:Cwhite|contact Christine]] and she will add you.<br />
<br />
===Software Deployed===<br />
The following software - all open source - was downloaded and installed:<br />
<br />
{| style="border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #000"<br />
|-<br />
! style="border-style: solid; border-width: 1px"| Software<br />
! style="border-style: solid; border-width: 1px"| Function<br />
! style="border-style: solid; border-width: 1px"| Version<br />
! style="border-style: solid; border-width: 1px"| Download Link<br />
|-<br />
| style="border-style: solid; border-width: 1px"| PostgreSQL<br />
| style="border-style: solid; border-width: 1px"| RDBMS<br />
| style="border-style: solid; border-width: 1px"| 9.1.3<br />
| style="border-style: solid; border-width: 1px"| http://www.enterprisedb.com/products-services-training/pgbindownload<br />
|-<br />
| style="border-style: solid; border-width: 1px"| JDBC4 Postgresql Driver<br />
| style="border-style: solid; border-width: 1px"| JDBC driver<br />
| style="border-style: solid; border-width: 1px"| 9.1<br />
| style="border-style: solid; border-width: 1px"| http://jdbc.postgresql.org/download.html<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Java Development Kit (JDK)<br />
| style="border-style: solid; border-width: 1px"| Java controller<br />
| style="border-style: solid; border-width: 1px"| SE 6 Update 31 <br />
| style="border-style: solid; border-width: 1px"| http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u31-download-1501634.html<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache Tomcat<br />
| style="border-style: solid; border-width: 1px"| Web container<br />
| style="border-style: solid; border-width: 1px"| 6.0.35<br />
| style="border-style: solid; border-width: 1px"| http://tomcat.apache.org/download-60.cgi#6.0.35<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache DS<br />
| style="border-style: solid; border-width: 1px"| LDAP server<br />
| style="border-style: solid; border-width: 1px"| 1.5.7<br />
| style="border-style: solid; border-width: 1px"| http://directory.apache.org/apacheds/1.5/<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache Directory Studio<br />
| style="border-style: solid; border-width: 1px"| LDAP browser<br />
| style="border-style: solid; border-width: 1px"| 2.0 M3<br />
| style="border-style: solid; border-width: 1px"| http://directory.apache.org/studio/2.0/download/<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Esri Geoportal Server<br />
| style="border-style: solid; border-width: 1px"| Geoportal<br />
| style="border-style: solid; border-width: 1px"| 1.2<br />
| style="border-style: solid; border-width: 1px"| http://sourceforge.net/projects/geoportal/files/Distribution/v1.2/geoportal-1.2.zip/download<br />
|}<br />
<br />
==Moving to EC2 Micro Instance==<br />
At some point, you may want to move your Amazon instance to a smaller, more cost-effective instance. For notes on this, please see [[Documentation on moving to EC2 Micro Instance - Christine White]].<br />
----<br />
Back to the [[Testbed]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Talk:Testbed&diff=50482Talk:Testbed2015-07-17T16:23:41Z<p>Graybeal: /* -- Graybeal (talk) 10:11, 17 July 2015 (MDT) */</p>
<hr />
<div>== -- [[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 10:11, 17 July 2015 (MDT) ==<br />
<br />
=== Amazon accounts ===<br />
I added the warning about not using your existing personal account based on my own experience, where the account charges got transferred to ESIP. It may be there was some way to keep the ESIP activities and my activities separate, but I couldn't find it after a brief search.<br />
[[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 10:23, 17 July 2015 (MDT)<br />
<br />
=== Drupal page ===<br />
I have had problems with the Drupal site, such that the opportunities described in this item ("Access to the Testbed Portal (testbed.esipfed.org), a site based on Drupal for project documentation, content registration, and document sharing for your project") were not accessible to me.If that is not an actual capability in the current system, I prefer to change this bullet to reflect the reality.<br />
[[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 10:23, 17 July 2015 (MDT)</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Testbed&diff=50481Testbed2015-07-17T16:16:10Z<p>Graybeal: /* What resources are provided to Testbed projects? */ added GitHub repository, and clarified the testbed portal is the Drupal repository</p>
<hr />
<div>''Back to:'' [[Products and Services]]<br />
=ESIP Testbed Crash Course=<br />
This section answers basic questions about the ESIP Testbed.<br />
== What is the ESIP Testbed? ==<br />
The ESIP Testbed was developed as a framework for moving Earth science ideas and projects (software, data, etc…) through a development life cycle. The Testbed facilitates collaboration and innovation across all sectors of the ESIP Federation improving the availability, access, and mutual benefit of new technologies. <br />
== What resources are provided to Testbed projects? ==<br />
ESIP supports Testbed projects at each stage of the development life cycle in accordance with established best practices including, but not limited to: <br />
* Technology assessment appropriate to each stage of the development life cycle;<br />
* Assessment of project value to Earth Science community;<br />
* Match-making with other projects/ESIP groups/opportunities;<br />
* Solicitation of feedback from the ESIP Community;<br />
* Breakout sessions at the twice-annual ESIP meetings for planning, feedback and presentation of your work, and other project-related meetings; <br />
* Cloud computing infrastructure (within budget constraints); <br />
* Access to the Testbed Portal (testbed.esipfed.org), a site based on Drupal for project documentation, content registration, and document sharing for your project; <br />
* Access to the GitHub repository (github.com/esipfed), a project repository that provides basic management and wiki capability; and<br />
* Development funds.<br />
<br />
== How does a project benefit from going through the Testbed? ==<br />
ESIP provides Testbed projects with domain-specific expert input, visibility, and validation within the ESIP and Earth science communities.<br />
== What types of projects can enter the Testbed? ==<br />
The Testbed is currently accepting projects in the Incubation stage of the development life cycle, i.e. projects in the realm of good ideas ready to move beyond the proof-of-concept stage. The Testbed will soon support projects at the Prototype stage. <br />
== How can a project enter the Testbed? ==<br />
The ESIP Testbed is managed by the Products & Services (P&S) committee. The P&S committee will release periodic requests for proposals (RFP) for projects to enter the Testbed. The Testbed Configuration Board decides which projects will enter the Testbed and at what stage.<br />
= Current and Past Testbed Tasks =<br />
See [[Past Testbed Tasks]] and the [http://testbed.esipfed.org/ ESIP Testbed Site] for information on funded Testbed Projects.<br />
<br />
==Other Current or Ongoing Testbed Activities ==<br />
=== Amazon Web Services best practices ===<br />
ESIP has opened an Amazon Web Services account that can be leveraged to provide virtual instances for accessing the testbed projects. In an effort to save pain and share experiences, please read and contribute to the [[ESIP Testbed Amazon Web Services Best Practices]] topic if you are going to work on the Amazon instances or have and want to contribute insight.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Talk:Testbed&diff=50480Talk:Testbed2015-07-17T16:11:10Z<p>Graybeal: /* -- ~~~~ */ new section</p>
<hr />
<div>== -- [[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 10:11, 17 July 2015 (MDT) ==<br />
<br />
I added the warning about not using your existing personal account based on my own experience, where the account charges got transferred to ESIP. It may be there was some way to keep the ESIP activities and my activities separate, but I couldn't find it after a brief search.</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=ESIP_Testbed_Amazon_Web_Services_Best_Practices&diff=50479ESIP Testbed Amazon Web Services Best Practices2015-07-17T15:59:57Z<p>Graybeal: /* Step 1: Create an AWS account */ edited to reflect my experience</p>
<hr />
<div>This page outlines best practices, lessons learned, insights, and anything else relevant to deploying testbed instances on Amazon Web Services. This initial content describes the experience of the Discovery Cluster in deploying the Esri Geoportal Server on an Amazon instance as part of the [[Discovery Testbed Work Plan]]. <br />
<br />
== Steps to deploy an instance ==<br />
===Step 1: Create an AWS account===<br />
You'll need to go to the [http://aws.amazon.com/console/ Amazon Web Services website] and create an account. Note that you will need to associate your account with a payment method - this personal and independent account needs to be on file with Amazon as a backup, and Amazon will also use this account info to verify your identify. In Step 2, you will be added to the ESIP Consolidated billing account, and that is where the instance charging will be applied. So as long as you don't sign up for services that are outside the scope of the consolidated billing, your account on file should not be charged.<br />
<br />
After creating an account, Amazon will call you to verify your identity. For this to go most smoothly, recommendation is to use a phone number that does not have an extension associated with it.<br />
<br />
Be aware that all of the account activity will be subsumed under the ESIP framework, so if you have an existing Amazon account that you use for other purposes, you should create a new account for ESIP use.<br />
<br />
===Step 2: Consolidated Billing===<br />
Contact Erin Robinson and request that she add you to the ESIP AWS Consolidated billing account. This account should cover all your activity on AWS except [http://docs.amazonwebservices.com/AmazonDevPay/latest/DevPayGettingStartedGuide/Welcome.html?r=5486 Amazon DevPay].<br />
<br />
===Step 3: Set up an EC2 instance account===<br />
Once you have an AWS account, you will need to create an EC2 account. When you click on the EC2 tab from the AWS Management Console, you will be prompted to sign in or sign up. Proceed with signing up.<br />
<br />
===Step 4: Get started with the EC2 instances===<br />
Brief notes: US East instances are typically less expensive than West instances. Linux instances are less expensive than Windows, but hearsay is that support is better for Windows. <br />
<br />
There is very good step-by-step documentation on how to create and launch an instance - see the [http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/Welcome.html?r=2500 Amazon Getting Started Guide].<br />
<br />
===Step 5: Create and manage images (optional) ===<br />
After you've deployed an instance and done some work on your instance (e.g. deploy software, configure users, etc.) you may want to preserve that work by creating an image. Conceptually, creating the image works the same as creating an image using VM-based snapshot tools. Documentation for how to do this is available at [http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/Tutorial_CreateImage.html Creating an Image from a Running Instance]. '''IMPORTANT:''' Delete unused images, as the consolidated billing account will be charged for space stored on the Volumes associated with images).<br />
<br />
=== Step 6: How to Open Ports so you can access web apps deployed on instances (optional)===<br />
If you want external users to be able to access web (or other) applications that are hosted on your instance, you will need to configure the port access. There are two places where the ports will need to be configured: first in your amazon instance through the AWS Management Console, and also on the instance itself.<br />
<br />
For the configuration in the AWS Management Console, click on your EC2 instance. In the left navigation window, there is a section called “Security Groups” - click on this. The rules associated with your security group are displayed in the window at the bottom of the screen. You can add ports and access rules here; for example, a web application that requires port 8080 to be open would be added as shown in the following:<br />
<br />
[[File:openPorts1.png|200px|thumb|none|click to enlarge]]<br />
<br />
For the configuration on the Amazon instance, you will likely also need to configure ports. This section describes opening ports on a Windows Server 2008 R2 SP1 instance; for other instances, there are different methods.<br />
* Open the Windows Firewall with Advance Security menu:<br />
[[File:openPorts2.png|200px|thumb|none|click to enlarge]]<br />
* In the resulting window, select “Inbound Rules” from the left menu, and then click “New Rule” from the far right window. In the resulting dialog, select a new rule for “ports” - see below. Then click Next.<br />
[[File:openPorts3.png|200px|thumb|none|click to enlarge]]<br />
* In the next window, enter the "Specific Ports" for which you want to apply the rule. Click Next. <br />
* Now determine what should happen – e.g., “Allow the connection” and click Next.<br />
* You can accept the defaults for the rest of the settings (unless you have a reason not to), except where you are prompted to enter a name for the rule. Enter whatever name adequately describes your rule.<br />
<br />
You can following these same instructions for opening outbound ports, using the "Outbound Rules" option from the left menu.<br />
<br />
== Notes specific to the Discovery Cluster Testbed deployment ==<br />
===Instance details===<br />
In this deployment, Christine White worked to install the base software for the Esri Geoportal Server 1.2. It was deployed on a Windows Server 2008 R2 SP1 instance, configured with a 'Small' size, based on East Coast hosting resources. Estimated pricing for such an instance is reportedly ~ $0.115/hour, with one elastic IP address - see [http://aws.amazon.com/ec2/pricing/ EC2 Pricing].<br />
<br />
You can download a .zip file mp4 video of the deployment (warning: not so exciting, but at least its short), here: [[File:discovery_AWS_instance.zip]].<br />
<br />
The Geoportal Server deployment is accessible at http://23.23.211.222:8080/geoportal. As an anonymous user, you can search for resources using the Search tab (although not many are registered yet, just some ArcGIS Server services for test purposes). User logins will be added for testbed users interested in contributing/testing service endpoints - to become a user of the geoportal, [[User:Cwhite|contact Christine]] and she will add you.<br />
<br />
===Software Deployed===<br />
The following software - all open source - was downloaded and installed:<br />
<br />
{| style="border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #000"<br />
|-<br />
! style="border-style: solid; border-width: 1px"| Software<br />
! style="border-style: solid; border-width: 1px"| Function<br />
! style="border-style: solid; border-width: 1px"| Version<br />
! style="border-style: solid; border-width: 1px"| Download Link<br />
|-<br />
| style="border-style: solid; border-width: 1px"| PostgreSQL<br />
| style="border-style: solid; border-width: 1px"| RDBMS<br />
| style="border-style: solid; border-width: 1px"| 9.1.3<br />
| style="border-style: solid; border-width: 1px"| http://www.enterprisedb.com/products-services-training/pgbindownload<br />
|-<br />
| style="border-style: solid; border-width: 1px"| JDBC4 Postgresql Driver<br />
| style="border-style: solid; border-width: 1px"| JDBC driver<br />
| style="border-style: solid; border-width: 1px"| 9.1<br />
| style="border-style: solid; border-width: 1px"| http://jdbc.postgresql.org/download.html<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Java Development Kit (JDK)<br />
| style="border-style: solid; border-width: 1px"| Java controller<br />
| style="border-style: solid; border-width: 1px"| SE 6 Update 31 <br />
| style="border-style: solid; border-width: 1px"| http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u31-download-1501634.html<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache Tomcat<br />
| style="border-style: solid; border-width: 1px"| Web container<br />
| style="border-style: solid; border-width: 1px"| 6.0.35<br />
| style="border-style: solid; border-width: 1px"| http://tomcat.apache.org/download-60.cgi#6.0.35<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache DS<br />
| style="border-style: solid; border-width: 1px"| LDAP server<br />
| style="border-style: solid; border-width: 1px"| 1.5.7<br />
| style="border-style: solid; border-width: 1px"| http://directory.apache.org/apacheds/1.5/<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Apache Directory Studio<br />
| style="border-style: solid; border-width: 1px"| LDAP browser<br />
| style="border-style: solid; border-width: 1px"| 2.0 M3<br />
| style="border-style: solid; border-width: 1px"| http://directory.apache.org/studio/2.0/download/<br />
|-<br />
| style="border-style: solid; border-width: 1px"| Esri Geoportal Server<br />
| style="border-style: solid; border-width: 1px"| Geoportal<br />
| style="border-style: solid; border-width: 1px"| 1.2<br />
| style="border-style: solid; border-width: 1px"| http://sourceforge.net/projects/geoportal/files/Distribution/v1.2/geoportal-1.2.zip/download<br />
|}<br />
<br />
==Moving to EC2 Micro Instance==<br />
At some point, you may want to move your Amazon instance to a smaller, more cost-effective instance. For notes on this, please see [[Documentation on moving to EC2 Micro Instance - Christine White]].<br />
----<br />
Back to the [[Testbed]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=P%26S_Telecon_-_May_19,_2015&diff=49614P&S Telecon - May 19, 20152015-05-27T19:18:34Z<p>Graybeal: /* Review questions on just-released June "Incubation" RFP */ updated broken link to testbed RFP</p>
<hr />
<div>= Agenda =<br />
<br />
== Review questions on just-released June "Incubation" RFP ==<br />
* Reviewed posted [http://testbed.esipfed.org/sites/default/files/2015_06_15_ESIP_Testbed_RFP_0.pdf Testbed RFP]<br />
* Reviewed changes to ESIP [[Testbed]] wiki page, highlighting Annie's "Crash Course" FAQ<br />
* Noted updates to "[[Past Testbed Tasks]]" page: all projects moved to table format, request for group to review for missing information on older projects<br />
<br />
== Testbed Vision Topics ==<br />
=== Working on next fast-track proposal set for "prototype assessments"===<br />
Prototype RFP - similar format to the incubation <br />
* Post this RFP by mid-June, next P&S call can be similar to this one, where first half is Q&A <br />
* Annie do the first cut, P&S can help with review, input; AIST projects also providing input/review <br />
<br />
How does "Hacker Space" at Summer Meeting play into this RFP? <br />
* Messaging: "RFP madness! What is going on in the Testbed?"<br />
* Diagram, blog post, etc. that explains how this all connects<br />
<br />
As we work on this RFP, also think about these general topics:<br />
* Governance of the Testbed<br />
* Staff roles - what needs to be supported?<br />
* How do we publicize, clarify the Fast-track projects?<br />
* Business regarding Testbed - infrastructure, etc.?<br />
<br />
== Summer Meeting session and hackathon ==<br />
Independent Tech Evaluation session<br />
<br />
Hacker's Space - free form<br />
* Room for breakouts, designated for these connections/conversations<br />
* Able to reserve a table in the room for "project x" - assessment criteria, other topics, prototype, etc.<br />
* Overflow room too, if they want to keep working…?<br />
* 3rd way to do assessment - needs to be done in person<br />
* Additional FUNding Friday award for something worked on in the Hacker's space at the meeting<br />
* Messaging in advance on Hacker's Space resources<br />
<br />
== Next P&S call: Tuesday, June 16th, 11 Pacific ==<br />
* Can be similar to this one, where first half is Q&A on prototype solicitation<br />
* Q&A on Hacker's Space (?)</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Mappings&diff=49046Attribute Convention for Data Discovery Mappings2015-02-26T05:03:22Z<p>Graybeal: document no longer normative</p>
<hr />
<div><font color="red">These mappings are no longer normative—they represent the original relation of ACDD attributes to similar concepts in other specifications, but have not been updated for the latest changes.</font><br />
<br />
= ACDD Metadata Dialect Mappings =<br />
Many of these elements are included in the ISO 19115 Core specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
= Highly Recommended =<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#title_Attribute title]<br><br />
</td><br />
<td valign="top">A short description of the dataset.<br><br />
</td><br />
<td valign="top">dataset@name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString (M)<br><br />
</td><br />
<td>Title</td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#summary_Attribute summary]<br><br />
</td><br />
<td valign="top">A paragraph describing the dataset.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="summary"]<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract/gco:CharacterString (M)<br><br />
</td><br />
<td>Abstract</td> <br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_Attribute keywords]<br><br />
</td><br />
<td valign="top">A comma separated list of key words and phrases.<br><br />
</td><br />
<td valign="top">metadata/keyword<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br><br />
</td><br />
<td>Subject</td><br />
<td>Text Search</td><br />
</tr><br />
</table><br />
<br />
=Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#id_Attribute id]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The<br />
combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.<br><br />
</td><br />
<td rowspan="2" valign="top">dataset@id<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString (O)<br><br />
</td><br />
<td rowspan="2">Identifier</td><br />
<td rowspan="2">Identifier</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#naming_authority_Attribute naming_authority]<br><br />
</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_vocabulary_Attribute keywords_vocabulary]<br><br />
</td><br />
<td valign="top">If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.<br><br />
</td><br />
<td valign="top">metadata/keyword@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br><br />
</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#cdm_data_type_Attribute cdm_data_type]<br><br />
</td><br />
<td valign="top">The [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS data type] appropriate for this dataset.</td><br />
<td valign="top">metadata/dataType</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode<br> May need some extensions to this codelist. Current values: vector, grid, textTable, tin, stereoModel, video.<br />
</td><br />
<td></td><br />
<td>Other</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#history_Attribute history]<br></td><br />
<td valign="top">Provides an audit trail for modifications to the original data.</td><br />
<td valign="top">metadata/documentation[@type="history"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement/gco:CharacterString (O)</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#comment_Attribute comment]<br><br />
</td><br />
<td valign="top">Miscellaneous information about the data.</td><br />
<td valign="top">metadata/documentation<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:supplementalInformation<br><br />
</td><br />
<td></td><br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_created_Attribute date_created]</td><br />
<td valign="top">The date on which the data was created.<br><br />
</td><br />
<td valign="top">metadata/date[@type="created"]</td> <br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date (M)<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="creation"</br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_name_Attribute creator_name]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist. <br><br />
</td><br />
<td valign="top">metadata/creator/name<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
CI_RoleCode="originator" (O)</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_url_Attribute creator_url]<br><br />
</td> <br />
<td valign="top">metadata/creator/contact@url<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_email_Attribute creator_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/creator/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#institution_Attribute institution]<br><br />
</td><br />
<td valign="top">metadata/creator/name</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#project_Attribute project]<br><br />
</td><br />
<td valign="top">The scientific project that produced the data.<br><br />
</td><br />
<td valign="top">metadata/project<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:title/gco:CharacterString<br>DS_AssociationTypeCode="largerWorkCitation" and DS_InitiativeTypeCode="project"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="project"<br />
</td><br />
<td></td><br />
<td>Responsible Party</td> <br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#processing_level_Attribute processing_level]</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="processing_level"]</td><br />
<td></td><td></td><td></td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#acknowledgement_Attribute acknowledgement]</td><td valign="top">A place to acknowledge various type of support for the project that produced this data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="funding"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:credit/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">geospatial_bounds</td><br />
<td>Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the [http://en.wikipedia.org/wiki/Well-known_text Well-Known Text] (WKT) format.</td><br />
<td></td><br />
<td></td><br />
<td>BoundingPolygon</td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_min_Attribute geospatial_lat_min]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.<br/>The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.<br/>For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/start<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_max_Attribute geospatial_lat_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_min_Attribute geospatial_lon_min]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/start</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td> <br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_max_Attribute geospatial_lon_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_min_Attribute geospatial_vertical_min]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].</td><br />
<td valign="top">metadata/geospatialCoverage/updown/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:minimumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_max_Attribute geospatial_vertical_max]</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/size</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:maximumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_start_Attribute time_coverage_start]</td><br />
<td rowspan="4" colspan="1" valign="top">Describes the temporal coverage of the data as a time range.</td><br />
<td valign="top">metadata/timeCoverage/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_end_Attribute time_coverage_end]</td><br />
<td valign="top">metadata/timeCoverage/end</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:endPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_duration_Attribute time_coverage_duration]</td><br />
<td valign="top">metadata/timeCoverage/duration</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition provides an ISO8601 compliant description of the time period covered by the dataset. This standard supports descriptions of [http://en.wikipedia.org/wiki/ISO_8601#Durations durations].</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_resolution_Attribute time_coverage_resolution]</td><br />
<td valign="top">metadata/timeCoverage/resolution</td><br />
<td></td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute standard_name_vocabulary]<br><br />
</td><br />
<td valign="top">The name of the controlled vocabulary from which variable standard names are taken.<br><br />
</td><br />
<td valign="top">metadata/variables@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br></td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#license_Attribute license]</td><br />
<td valign="top">Describe the restrictions to data access and distribution. </td><br />
<td valign="top">metadata/documentation[@type="rights"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString<br></td><br />
<td></td><td></td><br />
</tr><br />
</table><br />
<br />
=Suggested=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_name_Attribute contributor_name]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The name and role of any individuals or institutions that contributed to the creation of this data.<br><br />
</td><br />
<td valign="top">metadata/contributor<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_role_Attribute contributor_role]<br><br />
</td><br />
<br />
<td valign="top">metadata/contributor@role</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode<br><br />
="principalInvestigator" | "author"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_name_Attribute publisher_name]<br><br />
</td><br />
<td rowspan="3" colspan="1" valign="top">The data publisher's name, URL, and email. The publisher may be an individual or an institution.</td><br />
<td valign="top">metadata/publisher/name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br>CI_RoleCode="publisher"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="dataCenter"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_url_Attribute publisher_url]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@url<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_email_Attribute publisher_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_modified_Attribute date_modified]<br><br />
</td><br />
<td valign="top">The date on which this data was last modified.<br><br />
</td><br />
<td valign="top">metadata/date[@type="modified"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="revision"</td><br />
<td>Modified</td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_issued_Attribute date_issued]<br><br />
</td><br />
<td valign="top">The date on which this data was formally issued.<br><br />
</td><br />
<td valign="top">metadata/date[@type="issued"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="publication"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_units_Attribute geospatial_lat_units]<br><br />
</td><br />
<td rowspan="7" colspan="1" valign="top">Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.<br><br />
<br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_resolution_Attribute geospatial_lat_resolution]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_units_Attribute geospatial_lon_units]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_resolution_Attribute geospatial_lon_resolution]</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_units_Attribute geospatial_vertical_units]<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/updown/units</td><br />
<td valign="top" rowspan="3">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:verticalCRS</td><br />
<td></td> <td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_resolution_Attribute geospatial_vertical_resolution]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/resolution<br><br />
</td> <br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_positive_Attribute geospatial_vertical_positive]<br><br />
</td><br />
<br />
<td valign="top">metadata/geospatialCoverage@zpositive<br><br />
</td><br />
<td></td><td>Extent</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#long_name_Attribute long_name]</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary).</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
<td rowspan="2" valign="top">At present the ISO 19115-2 Standard supports only one name for a variable. Standard names can be provided as keywords with the appropriate thesaurus.</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_Attribute standard_name]<br></td><br />
<td valign="top">A long descriptive name for the variable taken from a controlled vocabulary of variable names.</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#units_Attribute units]</td><br />
<td valign="top">The units of the variables data values. This attributes value should be a valid udunits string.</td><br />
<td valign="top">metadata/variables/variable@units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:contentInfo/gmi:MI_CoverageDescription/gmd:dimension/gmd:MD_Band/gmd:units</td><br />
</tr><br />
<tr><br />
<td valign="top">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data.</td><br />
<td valign="top"></td><br />
<td valign="top">The valid values in the MD_CoverageContentTypeCode list are image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, coordinate</td><br />
</tr><br />
</table><br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-1&diff=48982Attribute Convention for Data Discovery 1-12015-02-19T18:34:03Z<p>Graybeal: /* Version and Status */ finished tweaking the links</p>
<hr />
<div>== Version and Status ==<br />
<br />
This version is designated as Version 1.1. As of January 1 2015 it is no longer the current version; see [[Attribute Convention for Data Discovery]] for the current version.<br />
<br />
See the [http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page] for information on the history of this convention.<br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained at [[Attribute_Convention_for_Data_Discovery_(ACDD)_Working]].<br />
<br />
----<br />
<br />
The netCDF Group at Unidata has [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html recommended] netCDF attributes for data discovery. Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
==Metadata Link==<br />
The netCDF metadata model is focused on providing "use metadata" for the data included in the file (or granule). Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "Metadata_Link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
=Highly Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#title_Attribute title]<br><br />
</td><br />
<td valign="top">A short description of the dataset.<br><br />
</td><br />
<td valign="top">dataset@name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString (M)<br><br />
</td><br />
<td>Title</td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#summary_Attribute summary]<br><br />
</td><br />
<td valign="top">A paragraph describing the dataset.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="summary"]<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract/gco:CharacterString (M)<br><br />
</td><br />
<td>Abstract</td> <br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_Attribute keywords]<br><br />
</td><br />
<td valign="top">A comma separated list of key words and phrases.<br><br />
</td><br />
<td valign="top">metadata/keyword<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br><br />
</td><br />
<td>Subject</td><br />
<td>Text Search</td><br />
</tr><br />
</table><br />
<br />
=Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#id_Attribute id]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The<br />
combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.<br><br />
</td><br />
<td rowspan="2" valign="top">dataset@id<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString (O)<br><br />
</td><br />
<td rowspan="2">Identifier</td><br />
<td rowspan="2">Identifier</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#naming_authority_Attribute naming_authority]<br><br />
</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_vocabulary_Attribute keywords_vocabulary]<br><br />
</td><br />
<td valign="top">If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.<br><br />
</td><br />
<td valign="top">metadata/keyword@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br><br />
</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#cdm_data_type_Attribute cdm_data_type]<br><br />
</td><br />
<td valign="top">The [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS data type] appropriate for this dataset.</td><br />
<td valign="top">metadata/dataType</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode<br> May need some extensions to this codelist. Current values: vector, grid, textTable, tin, stereoModel, video.<br />
</td><br />
<td></td><br />
<td>Other</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#history_Attribute history]<br></td><br />
<td valign="top">Provides an audit trail for modifications to the original data.</td><br />
<td valign="top">metadata/documentation[@type="history"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement/gco:CharacterString (O)</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#comment_Attribute comment]<br><br />
</td><br />
<td valign="top">Miscellaneous information about the data.</td><br />
<td valign="top">metadata/documentation<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:supplementalInformation<br><br />
</td><br />
<td></td><br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_created_Attribute date_created]</td><br />
<td valign="top">The date on which the data was created.<br><br />
</td><br />
<td valign="top">metadata/date[@type="created"]</td> <br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date (M)<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="creation"</br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_name_Attribute creator_name]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist. <br><br />
</td><br />
<td valign="top">metadata/creator/name<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
CI_RoleCode="originator" (O)</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_url_Attribute creator_url]<br><br />
</td> <br />
<td valign="top">metadata/creator/contact@url<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_email_Attribute creator_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/creator/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#institution_Attribute institution]<br><br />
</td><br />
<td valign="top">metadata/creator/name</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#project_Attribute project]<br><br />
</td><br />
<td valign="top">The scientific project that produced the data.<br><br />
</td><br />
<td valign="top">metadata/project<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:title/gco:CharacterString<br>DS_AssociationTypeCode="largerWorkCitation" and DS_InitiativeTypeCode="project"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="project"<br />
</td><br />
<td></td><br />
<td>Responsible Party</td> <br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#processing_level_Attribute processing_level]</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="processing_level"]</td><br />
<td></td><td></td><td></td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#acknowledgement_Attribute acknowledgement]</td><td valign="top">A place to acknowledge various type of support for the project that produced this data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="funding"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:credit/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">geospatial_bounds</td><br />
<td>Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the [http://en.wikipedia.org/wiki/Well-known_text Well-Known Text] (WKT) format.</td><br />
<td></td><br />
<td></td><br />
<td>BoundingPolygon</td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_min_Attribute geospatial_lat_min]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.<br/>The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.<br/>For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/start<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_max_Attribute geospatial_lat_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_min_Attribute geospatial_lon_min]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/start</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td> <br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_max_Attribute geospatial_lon_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_min_Attribute geospatial_vertical_min]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].</td><br />
<td valign="top">metadata/geospatialCoverage/updown/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:minimumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_max_Attribute geospatial_vertical_max]</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/size</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:maximumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_start_Attribute time_coverage_start]</td><br />
<td rowspan="4" colspan="1" valign="top">Describes the temporal coverage of the data as a time range.</td><br />
<td valign="top">metadata/timeCoverage/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_end_Attribute time_coverage_end]</td><br />
<td valign="top">metadata/timeCoverage/end</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:endPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_duration_Attribute time_coverage_duration]</td><br />
<td valign="top">metadata/timeCoverage/duration</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition provides an ISO8601 compliant description of the time period covered by the dataset. This standard supports descriptions of [http://en.wikipedia.org/wiki/ISO_8601#Durations durations].</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_resolution_Attribute time_coverage_resolution]</td><br />
<td valign="top">metadata/timeCoverage/resolution</td><br />
<td></td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute standard_name_vocabulary]<br><br />
</td><br />
<td valign="top">The name of the controlled vocabulary from which variable standard names are taken.<br><br />
</td><br />
<td valign="top">metadata/variables@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br></td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#license_Attribute license]</td><br />
<td valign="top">Describe the restrictions to data access and distribution. </td><br />
<td valign="top">metadata/documentation[@type="rights"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString<br></td><br />
<td></td><td></td><br />
</tr><br />
</table><br />
<br />
=Suggested=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_name_Attribute contributor_name]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The name and role of any individuals or institutions that contributed to the creation of this data.<br><br />
</td><br />
<td valign="top">metadata/contributor<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_role_Attribute contributor_role]<br><br />
</td><br />
<br />
<td valign="top">metadata/contributor@role</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode<br><br />
="principalInvestigator" | "author"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_name_Attribute publisher_name]<br><br />
</td><br />
<td rowspan="3" colspan="1" valign="top">The data publisher's name, URL, and email. The publisher may be an individual or an institution.</td><br />
<td valign="top">metadata/publisher/name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br>CI_RoleCode="publisher"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="dataCenter"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_url_Attribute publisher_url]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@url<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_email_Attribute publisher_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_modified_Attribute date_modified]<br><br />
</td><br />
<td valign="top">The date on which this data was last modified.<br><br />
</td><br />
<td valign="top">metadata/date[@type="modified"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="revision"</td><br />
<td>Modified</td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_issued_Attribute date_issued]<br><br />
</td><br />
<td valign="top">The date on which this data was formally issued.<br><br />
</td><br />
<td valign="top">metadata/date[@type="issued"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="publication"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_units_Attribute geospatial_lat_units]<br><br />
</td><br />
<td rowspan="7" colspan="1" valign="top">Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.<br><br />
<br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_resolution_Attribute geospatial_lat_resolution]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_units_Attribute geospatial_lon_units]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_resolution_Attribute geospatial_lon_resolution]</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_units_Attribute geospatial_vertical_units]<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/updown/units</td><br />
<td valign="top" rowspan="3">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:verticalCRS</td><br />
<td></td> <td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_resolution_Attribute geospatial_vertical_resolution]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/resolution<br><br />
</td> <br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_positive_Attribute geospatial_vertical_positive]<br><br />
</td><br />
<br />
<td valign="top">metadata/geospatialCoverage@zpositive<br><br />
</td><br />
<td></td><td>Extent</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#long_name_Attribute long_name]</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary).</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
<td rowspan="2" valign="top">At present the ISO 19115-2 Standard supports only one name for a variable. Standard names can be provided as keywords with the appropriate thesaurus.</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_Attribute standard_name]<br></td><br />
<td valign="top">A long descriptive name for the variable taken from a controlled vocabulary of variable names.</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#units_Attribute units]</td><br />
<td valign="top">The units of the variables data values. This attributes value should be a valid udunits string.</td><br />
<td valign="top">metadata/variables/variable@units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:contentInfo/gmi:MI_CoverageDescription/gmd:dimension/gmd:MD_Band/gmd:units</td><br />
</tr><br />
<tr><br />
<td valign="top">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data.</td><br />
<td valign="top"></td><br />
<td valign="top">The valid values in the MD_CoverageContentTypeCode list are image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, coordinate</td><br />
</tr><br />
</table><br />
<br />
=Conformance Test=<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
=Examples=<br />
==Attribute Names==<br />
This sample includes the attribute names as the values. It can be used to test transforms.<br />
<pre><br />
<?xml version='1.0' encoding='UTF-8'?><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="UnidataDataDiscoveryAttributes"/><br />
<attribute name="naming_authority" value="naming_authority"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="title"/><br />
<attribute name="summary" value="summary"/><br />
<attribute name="keywords" value="keywords"/><br />
<attribute name="keywords_vocabulary" value="keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="standard_name_vocabulary"/><br />
<attribute name="history" value="history"/><br />
<attribute name="comment" value="comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-89.999 " type="float"/><br />
<attribute name="geospatial_lat_max" value="89.999 " type="float"/><br />
<attribute name="geospatial_lon_min" value="-99.999 " type="float"/><br />
<attribute name="geospatial_lon_max" value="99.999 " type="float"/><br />
<attribute name="geospatial_vertical_min" value="-99.99 " type="float"/><br />
<attribute name="geospatial_vertical_max" value="99.99 " type="float"/><br />
<attribute name="time_coverage_start" value="1888-08-08T08:08:08Z"/><br />
<attribute name="time_coverage_end" value="1777-07-07T07:07:07Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="8.888" type="float"/><br />
<attribute name="geospatial_lon_units" value="geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="9.999" type="float"/><br />
<attribute name="geospatial_vertical_units" value="geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="999.0" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="P2Y2M2D"/><br />
<attribute name="time_coverage_resolution" value="P1Y1M1D"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="acknowledgment"/><br />
<attribute name="creator_email" value="creator_email"/><br />
<attribute name="creator_name" value="creator_name"/><br />
<attribute name="creator_url" value="creator_url"/><br />
<attribute name="date_created" value="1666-06-06T06:06:06Z"/><br />
<attribute name="date_modified" value="1999-09-09T09:09:09Z"/><br />
<attribute name="date_issued" value="2111-01-01T01:01:01Z"/><br />
<attribute name="institution" value="institution"/><br />
<attribute name="project" value="project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="contributor_name"/><br />
<attribute name="contributor_role" value="contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="publisher_name"/><br />
<attribute name="publisher_url" value="publisher_url"/><br />
<attribute name="publisher_email" value="publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="processing_level"/><br />
<attribute name="license" value="license"/><br />
<attribute name="cdm_data_type" value="cdm_data_type"/><br />
<variable name="tv" type="float" shape="depdp"><br />
<attribute name="units" value="units"/><br />
<attribute name="name" value="testVariable"/><br />
<attribute name="long_name" value="Test Variable - long name"/><br />
<attribute name="standard_name" value="test_variable_standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==XPaths==<br />
Sometimes an example with XPaths is useful. Note that this example includes service endpoints in the Service Endpoints section that are added by the ncISO capability in the THREDDS Data Server. ''These are not typically included in the netCDF file'':<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="netcdf/attribute/@name=id"/><br />
<attribute name="naming_authority" value="netcdf/attribute/@name=naming_authority"/><br />
<attribute name="Metadata_Conventions" value="netcdf/attribute/@name=Metadata_Conventions"/><br />
<attribute name="Metadata_Link" value="netcdf/attribute/@name=Metadata_Link"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="netcdf/attribute/@name=thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="netcdf/attribute/@name=thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="netcdf/attribute/@name=thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="netcdf/attribute/@name=thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="netcdf/attribute/@name=title"/><br />
<attribute name="summary" value="netcdf/attribute/@name=summary"/><br />
<attribute name="keywords" value="netcdf/attribute/@name=keywords"/><br />
<attribute name="keywords_vocabulary" value="netcdf/attribute/@name=keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="netcdf/attribute/@name=standard_name_vocabulary"/><br />
<attribute name="history" value="netcdf/attribute/@name=history"/><br />
<attribute name="comment" value="netcdf/attribute/@name=comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="netcdf/attribute/@name=geospatial_lat_min" type="float"/><br />
<attribute name="geospatial_lat_max" value="netcdf/attribute/@name=geospatial_lat_max" type="float"/><br />
<attribute name="geospatial_lon_min" value="netcdf/attribute/@name=geospatial_lon_min" type="float"/><br />
<attribute name="geospatial_lon_max" value="netcdf/attribute/@name=geospatial_lon_max " type="float"/><br />
<attribute name="geospatial_vertical_min" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="geospatial_vertical_max" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="time_coverage_start" value="netcdf/attribute/@name=time_coverage_start"/><br />
<attribute name="time_coverage_end" value="netcdf/attribute/@name=time_coverage_end"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="netcdf/attribute/@name=geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="netcdf/attribute/@name=geospatial_lat_resolution" type="float"/><br />
<attribute name="geospatial_lon_units" value="netcdf/attribute/@name=geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="netcdf/attribute/@name=geospatial_lon_resolution" type="float"/><br />
<attribute name="geospatial_vertical_units" value="netcdf/attribute/@name=geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="netcdf/attribute/@name=geospatial_vertical_resolution" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="netcdf/attribute/@name=geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="netcdf/attribute/@name=time_coverage_duration"/><br />
<attribute name="time_coverage_resolution" value="netcdf/attribute/@name=time_coverage_resolution"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="netcdf/attribute/@name=acknowledgment"/><br />
<attribute name="creator_email" value="netcdf/attribute/@name=creator_email"/><br />
<attribute name="creator_name" value="netcdf/attribute/@name=creator_name"/><br />
<attribute name="creator_url" value="netcdf/attribute/@name=creator_url"/><br />
<attribute name="date_created" value="netcdf/attribute/@name=date_created"/><br />
<attribute name="date_modified" value="netcdf/attribute/@name=date_modified"/><br />
<attribute name="date_issued" value="netcdf/attribute/@name=date_issued"/><br />
<attribute name="institution" value="netcdf/attribute/@name=institution"/><br />
<attribute name="project" value="netcdf/attribute/@name=project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="netcdf/attribute/@name=contributor_name"/><br />
<attribute name="contributor_role" value="netcdf/attribute/@name=contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="netcdf/attribute/@name=publisher_name"/><br />
<attribute name="publisher_url" value="netcdf/attribute/@name=publisher_url"/><br />
<attribute name="publisher_email" value="netcdf/attribute/@name=publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="netcdf/attribute/@name=processing_level"/><br />
<attribute name="license" value="netcdf/attribute/@name=license"/><br />
<attribute name="cdm_data_type" value="netcdf/attribute/@name=cdm_data_type"/><br />
<variable name="netcdf/variable/@name" type="netcdf/variable/@type" shape="netcdf/variable/@shape"><br />
<attribute name="units" value="netcdf/variable/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable/attribute/@name=standard_name"/><br />
</variable><br />
<variable name="netcdf/variable2/@name" type="netcdf/variable2/@type" shape="netcdf/variable2/@shape"><br />
<attribute name="units" value="netcdf/variable2/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable2/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable2/attribute/@name=standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==Real-World Example==<br />
This NcML, taken from a very well documented CoastWatch file, includes real-world examples for all of the recommended attributes:<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="LMHchlaS8day_20100129000000"/><br />
<attribute name="naming_authority" value="gov.noaa.pfel.coastwatch"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Text Search --><br />
<attribute name="title" value="Chlorophyll-a, Aqua MODIS, NPP, 0.05 degrees, Global, Science Quality"/><br />
<attribute name="summary"<br />
value="NOAA CoastWatch distributes chlorophyll-a concentration data from NASA&apos;s Aqua Spacecraft. <br />
Measurements are gathered by the Moderate Resolution Imaging Spectroradiometer (MODIS) carried aboard the spacecraft.<br />
This is Science Quality data."/><br />
<attribute name="keywords" value="EARTH SCIENCE &gt; Oceans &gt; Ocean Chemistry &gt; Chlorophyll"/><br />
<attribute name="keywords_vocabulary" value="GCMD Science Keywords"/><br />
<attribute name="standard_name_vocabulary" value="CF-1.0"/><br />
<attribute name="history" value="NASA GSFC (G. Feldman): 2010-02-22T22:48:46Z NOAA CoastWatch (West Coast Node) and NOAA SFSC ERD"/><br />
<attribute name="comment" value="Text comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-90.0 " type="double"/><br />
<attribute name="geospatial_lat_max" value="90.0 " type="double"/><br />
<attribute name="geospatial_lon_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_lon_max" value="360.0 " type="double"/><br />
<attribute name="geospatial_vertical_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_max" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_positive" value="up"/><br />
<attribute name="time_coverage_end" value="2010-02-02T00:00:00Z"/><br />
<attribute name="time_coverage_start" value="2010-01-25T00:00:00Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="degrees_north"/><br />
<attribute name="geospatial_lat_resolution" value="0.041676313961565174" type="double"/><br />
<attribute name="geospatial_lon_units" value="degrees_east"/><br />
<attribute name="geospatial_lon_resolution" value="0.04167148975575877" type="double"/><br />
<attribute name="geospatial_vertical_units" value="m"/><br />
<attribute name="geospatial_vertical_resolution" value="1.0" type="double"/><br />
<attribute name="time_coverage_duration" value="P1D"/><br />
<attribute name="time_coverage_resolution" value="PT1M"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="NOAA NESDIS COASTWATCH, NOAA SWFSC ERD"/><br />
<attribute name="creator_email" value="dave.foley@noaa.gov"/><br />
<attribute name="creator_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="creator_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<attribute name="date_created" value="2010-02-22Z"/><br />
<attribute name="date_modified" value="2010-03-22Z"/><br />
<attribute name="date_issued" value="2010-02-22Z"/><br />
<attribute name="institution" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="project" value="CoastWatch (http://coastwatch.noaa.gov/)"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="NASA GSFC (G. Feldman)"/><br />
<attribute name="contributor_role" value="Source of level 2 data."/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_email" value="dave.foley@noaa.gov"/><br />
<attribute name="publisher_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="publisher_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="3"/><br />
<attribute name="license"<br />
value="The data may be used and redistributed for free but is not intended for legal use, since it may contain inaccuracies. Neither the data Contributor, CoastWatch, NOAA, nor the United States Government, nor any of their employees or contractors, makes any warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, or assumes any legal liability for the accuracy, completeness, or usefulness, of this information."/><br />
<attribute name="cdm_data_type" value="Grid"/><br />
</netcdf><br />
</pre><br />
=NetCDF Climate and Forecast (CF) Metadata Conventions=<br />
The [http://cf-pcmdi.llnl.gov/ NetCDF Climate and Forecast (CF) Metadata Conventions] are designed to promote the interoperable processing and sharing of data from netCDF files. They are focused on data ''use'' while the NetCDF Attribute Conventions are focused on data ''discovery''. Many of the discovery attributes that are related to extents can be calculated from the CF information:<br/><br />
geospatial_lat_min, geospatial_lat_max, geospatial_lat_units, geospatial_lat_res<br/><br />
geospatial_lon_min, geospatial_lon_max, geospatial_lon_units, geospatial_lon_res<br/><br />
geospatial_vertical_min, geospatial_vertical_max, geospatial_vertical_units, geospatial_vertical_res, geospatial_vertical_pos<br/><br />
time_coverage_start, time_coverage_end, time_coverage_units, time_coverage_duration, time_coverage_res<br/><br />
<br />
'''Note: We recommend explicitly listing these attributes in the file even though they can be calculated from the CF information in order to facilitate direct access to this information by tools that do not understand the CF Conventions.'''<br />
=Open Geospatial Consortium Catalog Service for the Web (CSW)=<br />
The [http://www.opengeospatial.org/standards/cat OGC CSW Service] includes ten core queryable elements that must be supported in all instances. CSW Profiles map these queryables to elements in various standards. The ISO Mappings are described in Section 7.2.3.1,Table 6 of OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile ([http://portal.opengeospatial.org/files/?artifact_id=21460 OGC 07-045]). The core queryables mapping is included in the Table above. An additional "any text" queryable covers all text in a record. Two core queryables are not covered by the NetCDF Attribute Convention for Dataset Discovery: Format and CRS.<br />
<br />
=ISO Translation Notes=<br />
The translation between the Attribute Conventions for Data Discovery is subject to a number of assumptions or conventions described here.<br />
==People==<br />
The ACDD includes several types of people:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td></tr><br />
<tr><br />
<td>creator_name, creator_email, creator_url, institution</td><br />
<td>citation/citedResponsibleParty role=originator, point of contact, and metadata contact</td><br />
<tr><br />
<tr><br />
<td>contributor_name, contributor_role</td><br />
<td>citation/citedResponsibleParty role=originator (may need adjustment)</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword, aggregation information (initiative type = project)</td><br />
</tr><br />
<br />
</table><br />
==Keywords==<br />
The ACDD includes several attributes that make sense as keywords in ISO:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td><br />
</tr><br />
<tr><br />
<td>keywords</td><br />
<td>theme keywords with thesaurus given by the keywords_vocabulary attribute</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword with unknown thesaurus and aggregation information (initiative type = project)</td><br />
</tr><br />
<tr><br />
<td>publisher_name</td><br />
<td>Data Center keyword with unknown thesaurus</td><br />
</tr><br />
<tr><br />
<td>standard_names for parameters</td><br />
<td>theme keywords with thesaurus = standard_name_vocabulary</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
=Translation Revisions=<br />
Several changes were introduced into [http://www.ngdc.noaa.gov/metadata/published/xsl/UnidataDD2MI.xsl Version 2.0.2] of the stylesheet for transforming NcML to ISO in order to improve the rubric score for the resulting ISO metadata. The changes included:<br />
#Including netcdf/@location in transform as distribution onlineResource<br />
#Added tagname to writeResponsibleParty so that responsibleParties with <br />
different UML roles could be supported (i.e. contact vs. distributor)<br />
#Added urlName and urlDescription to writeResponsibleParty to add <br />
content to the onlineResource<br />
#Moved publisher from citation to distributor and included publisher_name as a dataCenter keyword.<br />
#Added project as a keyword with type=project<br />
#Added distributionInfo section to ISO if publisher or location exist.<br />
<br />
=Determining an Order of Precedence=<br />
There can be conflicting information available from different sources within the THREDDS and CDM data models.<br />
The diagram below seeks to determine an order of precedence for what is recorded in the ncISO metadata when those attributes conflict.<br />
[[Image:Metadataprecedence.png]]<br />
<br />
A key part of this discussion is the ability to see identify potentially conflicting metdata between the differenc sources within THREDDS and NetCDF. Below we propose using groups to identify in the NCML what sources contain the relevant metadata that will be used in the ISO translation. <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<netcdf xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2 ../XSD/ncml-2.2.xsd"<br />
xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"<br />
location="http://localhost:8080/thredds/dodsC/test/crm_v1.nc"><br />
<br />
<!-- Metadata from the netCDF or NCML file global attributes --> <br />
<attribute name="Conventions" value="CF-1.4" /><br />
<attribute name="title" value="crm_v1.grd" /><br />
<attribute name="history" value="xyz2grd -R-80/-64/40/48 -I3c -Gcrm_v1.grd" /><br />
<attribute name="GMT_version" value="4.5.1 [64-bit]" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="geospatial_lon_units" value="degrees_east" /><br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_min" type="float" value="-80.0" /><br />
<attribute name="geospatial_lon_max" type="float" value="-64.0" /> <br />
<attribute name="geospatial_lat_max" type="float" value="48.0" /><br />
<attribute name="geospatial_lat_min" type="float" value="40.0" /><br />
<attribute name="geospatial_lon_resolution" type="double" value="8.33E-4" /><br />
<attribute name="geospatial_lat_resolution" type="double" value="8.33E-4" /><br />
<br />
<!-- Metadata calculated from the netCDF file axes based on CF conventions --><br />
<group name="CFMetadata"><br />
<attribute name="geospatial_lon_min" value="-80.0" type="float" /><br />
<attribute name="geospatial_lat_min" value="40.0" type="float" /><br />
<attribute name="geospatial_lon_max" value="-64.0" type="float" /><br />
<attribute name="geospatial_lat_max" value="48.0" type="float" /><br />
<attribute name="geospatial_lon_units" value="degrees_east" /> <br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_resolution" value="8.332899328159992E-4" /><br />
<attribute name="geospatial_lat_resolution" value="8.332465368190813E-4" /><br />
</group><br />
<br />
<!-- Metadata from the THREDDS catalog dataset --><br />
<group name="THREDDSMetadata"><br />
<attribute name="id" value="crm_v1" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="data_distribution" value="http://localhost:8080/thredds/dodsC/test/crm_v1.nc" /><br />
<attribute name="wms_service" value="http://localhost:8080//thredds/wms/crm/crm_vol9.nc" /><br />
<attribute name="wcs_service" value="http://localhost:8080//thredds/wcs/crm/crm_vol9.nc" /><br />
</group> <br />
<br />
<!-- Metadata from the ncISO service --><br />
<group name="NCISOMetadata"><br />
<attribute name="metadata_creation" value="2011-04-19" /><br />
</group><br />
<br />
<dimension name="x" length="19201" /><br />
<dimension name="y" length="9601" /><br />
<br />
<variable name="z" shape="y x" type="float"><br />
<attribute name="long_name" value="z" /><br />
<br />
<attribute name="_FillValue" type="float" value="NaN" /><br />
<attribute name="actual_range" type="double" value="-2754.39990234375 1903.0" /><br />
<attribute name="units" value="meters" /><br />
<attribute name="positive" value="up" /><br />
</variable><br />
<variable name="x" shape="x" type="double"><br />
<attribute name="long_name" value="x" /><br />
<attribute name="actual_range" type="double" value="-80.0 -64.0" /><br />
<attribute name="units" value="degrees_east" /><br />
<br />
<attribute name="_CoordinateAxisType" value="Lon" /><br />
</variable><br />
<variable name="y" shape="y" type="double"><br />
<attribute name="long_name" value="y" /><br />
<attribute name="actual_range" type="double" value="40.0 48.0" /><br />
<attribute name="units" value="degrees_north" /><br />
<attribute name="_CoordinateAxisType" value="Lat" /><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-1&diff=48981Attribute Convention for Data Discovery 1-12015-02-19T18:32:49Z<p>Graybeal: /* Version and Status */</p>
<hr />
<div>== Version and Status ==<br />
<br />
This version is designated as Version 1.1. As of January 1 2015 it is no longer the current version; see [[Attribute Convention for Data Discovery]] for the current version.<br />
<br />
See the [[http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page]] for information on the history of this convention.<br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained at [[Attribute_Convention_for_Data_Discovery_(ACDD)_Working]].<br />
<br />
----<br />
<br />
The netCDF Group at Unidata has [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html recommended] netCDF attributes for data discovery. Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
==Metadata Link==<br />
The netCDF metadata model is focused on providing "use metadata" for the data included in the file (or granule). Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "Metadata_Link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
=Highly Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#title_Attribute title]<br><br />
</td><br />
<td valign="top">A short description of the dataset.<br><br />
</td><br />
<td valign="top">dataset@name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString (M)<br><br />
</td><br />
<td>Title</td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#summary_Attribute summary]<br><br />
</td><br />
<td valign="top">A paragraph describing the dataset.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="summary"]<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract/gco:CharacterString (M)<br><br />
</td><br />
<td>Abstract</td> <br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_Attribute keywords]<br><br />
</td><br />
<td valign="top">A comma separated list of key words and phrases.<br><br />
</td><br />
<td valign="top">metadata/keyword<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br><br />
</td><br />
<td>Subject</td><br />
<td>Text Search</td><br />
</tr><br />
</table><br />
<br />
=Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#id_Attribute id]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The<br />
combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.<br><br />
</td><br />
<td rowspan="2" valign="top">dataset@id<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString (O)<br><br />
</td><br />
<td rowspan="2">Identifier</td><br />
<td rowspan="2">Identifier</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#naming_authority_Attribute naming_authority]<br><br />
</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_vocabulary_Attribute keywords_vocabulary]<br><br />
</td><br />
<td valign="top">If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.<br><br />
</td><br />
<td valign="top">metadata/keyword@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br><br />
</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#cdm_data_type_Attribute cdm_data_type]<br><br />
</td><br />
<td valign="top">The [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS data type] appropriate for this dataset.</td><br />
<td valign="top">metadata/dataType</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode<br> May need some extensions to this codelist. Current values: vector, grid, textTable, tin, stereoModel, video.<br />
</td><br />
<td></td><br />
<td>Other</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#history_Attribute history]<br></td><br />
<td valign="top">Provides an audit trail for modifications to the original data.</td><br />
<td valign="top">metadata/documentation[@type="history"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement/gco:CharacterString (O)</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#comment_Attribute comment]<br><br />
</td><br />
<td valign="top">Miscellaneous information about the data.</td><br />
<td valign="top">metadata/documentation<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:supplementalInformation<br><br />
</td><br />
<td></td><br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_created_Attribute date_created]</td><br />
<td valign="top">The date on which the data was created.<br><br />
</td><br />
<td valign="top">metadata/date[@type="created"]</td> <br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date (M)<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="creation"</br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_name_Attribute creator_name]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist. <br><br />
</td><br />
<td valign="top">metadata/creator/name<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
CI_RoleCode="originator" (O)</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_url_Attribute creator_url]<br><br />
</td> <br />
<td valign="top">metadata/creator/contact@url<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_email_Attribute creator_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/creator/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#institution_Attribute institution]<br><br />
</td><br />
<td valign="top">metadata/creator/name</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#project_Attribute project]<br><br />
</td><br />
<td valign="top">The scientific project that produced the data.<br><br />
</td><br />
<td valign="top">metadata/project<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:title/gco:CharacterString<br>DS_AssociationTypeCode="largerWorkCitation" and DS_InitiativeTypeCode="project"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="project"<br />
</td><br />
<td></td><br />
<td>Responsible Party</td> <br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#processing_level_Attribute processing_level]</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="processing_level"]</td><br />
<td></td><td></td><td></td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#acknowledgement_Attribute acknowledgement]</td><td valign="top">A place to acknowledge various type of support for the project that produced this data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="funding"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:credit/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">geospatial_bounds</td><br />
<td>Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the [http://en.wikipedia.org/wiki/Well-known_text Well-Known Text] (WKT) format.</td><br />
<td></td><br />
<td></td><br />
<td>BoundingPolygon</td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_min_Attribute geospatial_lat_min]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.<br/>The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.<br/>For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/start<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_max_Attribute geospatial_lat_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_min_Attribute geospatial_lon_min]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/start</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td> <br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_max_Attribute geospatial_lon_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_min_Attribute geospatial_vertical_min]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].</td><br />
<td valign="top">metadata/geospatialCoverage/updown/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:minimumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_max_Attribute geospatial_vertical_max]</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/size</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:maximumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_start_Attribute time_coverage_start]</td><br />
<td rowspan="4" colspan="1" valign="top">Describes the temporal coverage of the data as a time range.</td><br />
<td valign="top">metadata/timeCoverage/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_end_Attribute time_coverage_end]</td><br />
<td valign="top">metadata/timeCoverage/end</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:endPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_duration_Attribute time_coverage_duration]</td><br />
<td valign="top">metadata/timeCoverage/duration</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition provides an ISO8601 compliant description of the time period covered by the dataset. This standard supports descriptions of [http://en.wikipedia.org/wiki/ISO_8601#Durations durations].</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_resolution_Attribute time_coverage_resolution]</td><br />
<td valign="top">metadata/timeCoverage/resolution</td><br />
<td></td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute standard_name_vocabulary]<br><br />
</td><br />
<td valign="top">The name of the controlled vocabulary from which variable standard names are taken.<br><br />
</td><br />
<td valign="top">metadata/variables@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br></td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#license_Attribute license]</td><br />
<td valign="top">Describe the restrictions to data access and distribution. </td><br />
<td valign="top">metadata/documentation[@type="rights"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString<br></td><br />
<td></td><td></td><br />
</tr><br />
</table><br />
<br />
=Suggested=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_name_Attribute contributor_name]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The name and role of any individuals or institutions that contributed to the creation of this data.<br><br />
</td><br />
<td valign="top">metadata/contributor<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_role_Attribute contributor_role]<br><br />
</td><br />
<br />
<td valign="top">metadata/contributor@role</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode<br><br />
="principalInvestigator" | "author"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_name_Attribute publisher_name]<br><br />
</td><br />
<td rowspan="3" colspan="1" valign="top">The data publisher's name, URL, and email. The publisher may be an individual or an institution.</td><br />
<td valign="top">metadata/publisher/name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br>CI_RoleCode="publisher"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="dataCenter"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_url_Attribute publisher_url]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@url<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_email_Attribute publisher_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_modified_Attribute date_modified]<br><br />
</td><br />
<td valign="top">The date on which this data was last modified.<br><br />
</td><br />
<td valign="top">metadata/date[@type="modified"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="revision"</td><br />
<td>Modified</td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_issued_Attribute date_issued]<br><br />
</td><br />
<td valign="top">The date on which this data was formally issued.<br><br />
</td><br />
<td valign="top">metadata/date[@type="issued"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="publication"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_units_Attribute geospatial_lat_units]<br><br />
</td><br />
<td rowspan="7" colspan="1" valign="top">Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.<br><br />
<br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_resolution_Attribute geospatial_lat_resolution]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_units_Attribute geospatial_lon_units]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_resolution_Attribute geospatial_lon_resolution]</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_units_Attribute geospatial_vertical_units]<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/updown/units</td><br />
<td valign="top" rowspan="3">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:verticalCRS</td><br />
<td></td> <td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_resolution_Attribute geospatial_vertical_resolution]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/resolution<br><br />
</td> <br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_positive_Attribute geospatial_vertical_positive]<br><br />
</td><br />
<br />
<td valign="top">metadata/geospatialCoverage@zpositive<br><br />
</td><br />
<td></td><td>Extent</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#long_name_Attribute long_name]</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary).</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
<td rowspan="2" valign="top">At present the ISO 19115-2 Standard supports only one name for a variable. Standard names can be provided as keywords with the appropriate thesaurus.</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_Attribute standard_name]<br></td><br />
<td valign="top">A long descriptive name for the variable taken from a controlled vocabulary of variable names.</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#units_Attribute units]</td><br />
<td valign="top">The units of the variables data values. This attributes value should be a valid udunits string.</td><br />
<td valign="top">metadata/variables/variable@units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:contentInfo/gmi:MI_CoverageDescription/gmd:dimension/gmd:MD_Band/gmd:units</td><br />
</tr><br />
<tr><br />
<td valign="top">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data.</td><br />
<td valign="top"></td><br />
<td valign="top">The valid values in the MD_CoverageContentTypeCode list are image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, coordinate</td><br />
</tr><br />
</table><br />
<br />
=Conformance Test=<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
=Examples=<br />
==Attribute Names==<br />
This sample includes the attribute names as the values. It can be used to test transforms.<br />
<pre><br />
<?xml version='1.0' encoding='UTF-8'?><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="UnidataDataDiscoveryAttributes"/><br />
<attribute name="naming_authority" value="naming_authority"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="title"/><br />
<attribute name="summary" value="summary"/><br />
<attribute name="keywords" value="keywords"/><br />
<attribute name="keywords_vocabulary" value="keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="standard_name_vocabulary"/><br />
<attribute name="history" value="history"/><br />
<attribute name="comment" value="comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-89.999 " type="float"/><br />
<attribute name="geospatial_lat_max" value="89.999 " type="float"/><br />
<attribute name="geospatial_lon_min" value="-99.999 " type="float"/><br />
<attribute name="geospatial_lon_max" value="99.999 " type="float"/><br />
<attribute name="geospatial_vertical_min" value="-99.99 " type="float"/><br />
<attribute name="geospatial_vertical_max" value="99.99 " type="float"/><br />
<attribute name="time_coverage_start" value="1888-08-08T08:08:08Z"/><br />
<attribute name="time_coverage_end" value="1777-07-07T07:07:07Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="8.888" type="float"/><br />
<attribute name="geospatial_lon_units" value="geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="9.999" type="float"/><br />
<attribute name="geospatial_vertical_units" value="geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="999.0" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="P2Y2M2D"/><br />
<attribute name="time_coverage_resolution" value="P1Y1M1D"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="acknowledgment"/><br />
<attribute name="creator_email" value="creator_email"/><br />
<attribute name="creator_name" value="creator_name"/><br />
<attribute name="creator_url" value="creator_url"/><br />
<attribute name="date_created" value="1666-06-06T06:06:06Z"/><br />
<attribute name="date_modified" value="1999-09-09T09:09:09Z"/><br />
<attribute name="date_issued" value="2111-01-01T01:01:01Z"/><br />
<attribute name="institution" value="institution"/><br />
<attribute name="project" value="project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="contributor_name"/><br />
<attribute name="contributor_role" value="contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="publisher_name"/><br />
<attribute name="publisher_url" value="publisher_url"/><br />
<attribute name="publisher_email" value="publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="processing_level"/><br />
<attribute name="license" value="license"/><br />
<attribute name="cdm_data_type" value="cdm_data_type"/><br />
<variable name="tv" type="float" shape="depdp"><br />
<attribute name="units" value="units"/><br />
<attribute name="name" value="testVariable"/><br />
<attribute name="long_name" value="Test Variable - long name"/><br />
<attribute name="standard_name" value="test_variable_standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==XPaths==<br />
Sometimes an example with XPaths is useful. Note that this example includes service endpoints in the Service Endpoints section that are added by the ncISO capability in the THREDDS Data Server. ''These are not typically included in the netCDF file'':<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="netcdf/attribute/@name=id"/><br />
<attribute name="naming_authority" value="netcdf/attribute/@name=naming_authority"/><br />
<attribute name="Metadata_Conventions" value="netcdf/attribute/@name=Metadata_Conventions"/><br />
<attribute name="Metadata_Link" value="netcdf/attribute/@name=Metadata_Link"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="netcdf/attribute/@name=thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="netcdf/attribute/@name=thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="netcdf/attribute/@name=thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="netcdf/attribute/@name=thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="netcdf/attribute/@name=title"/><br />
<attribute name="summary" value="netcdf/attribute/@name=summary"/><br />
<attribute name="keywords" value="netcdf/attribute/@name=keywords"/><br />
<attribute name="keywords_vocabulary" value="netcdf/attribute/@name=keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="netcdf/attribute/@name=standard_name_vocabulary"/><br />
<attribute name="history" value="netcdf/attribute/@name=history"/><br />
<attribute name="comment" value="netcdf/attribute/@name=comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="netcdf/attribute/@name=geospatial_lat_min" type="float"/><br />
<attribute name="geospatial_lat_max" value="netcdf/attribute/@name=geospatial_lat_max" type="float"/><br />
<attribute name="geospatial_lon_min" value="netcdf/attribute/@name=geospatial_lon_min" type="float"/><br />
<attribute name="geospatial_lon_max" value="netcdf/attribute/@name=geospatial_lon_max " type="float"/><br />
<attribute name="geospatial_vertical_min" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="geospatial_vertical_max" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="time_coverage_start" value="netcdf/attribute/@name=time_coverage_start"/><br />
<attribute name="time_coverage_end" value="netcdf/attribute/@name=time_coverage_end"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="netcdf/attribute/@name=geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="netcdf/attribute/@name=geospatial_lat_resolution" type="float"/><br />
<attribute name="geospatial_lon_units" value="netcdf/attribute/@name=geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="netcdf/attribute/@name=geospatial_lon_resolution" type="float"/><br />
<attribute name="geospatial_vertical_units" value="netcdf/attribute/@name=geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="netcdf/attribute/@name=geospatial_vertical_resolution" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="netcdf/attribute/@name=geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="netcdf/attribute/@name=time_coverage_duration"/><br />
<attribute name="time_coverage_resolution" value="netcdf/attribute/@name=time_coverage_resolution"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="netcdf/attribute/@name=acknowledgment"/><br />
<attribute name="creator_email" value="netcdf/attribute/@name=creator_email"/><br />
<attribute name="creator_name" value="netcdf/attribute/@name=creator_name"/><br />
<attribute name="creator_url" value="netcdf/attribute/@name=creator_url"/><br />
<attribute name="date_created" value="netcdf/attribute/@name=date_created"/><br />
<attribute name="date_modified" value="netcdf/attribute/@name=date_modified"/><br />
<attribute name="date_issued" value="netcdf/attribute/@name=date_issued"/><br />
<attribute name="institution" value="netcdf/attribute/@name=institution"/><br />
<attribute name="project" value="netcdf/attribute/@name=project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="netcdf/attribute/@name=contributor_name"/><br />
<attribute name="contributor_role" value="netcdf/attribute/@name=contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="netcdf/attribute/@name=publisher_name"/><br />
<attribute name="publisher_url" value="netcdf/attribute/@name=publisher_url"/><br />
<attribute name="publisher_email" value="netcdf/attribute/@name=publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="netcdf/attribute/@name=processing_level"/><br />
<attribute name="license" value="netcdf/attribute/@name=license"/><br />
<attribute name="cdm_data_type" value="netcdf/attribute/@name=cdm_data_type"/><br />
<variable name="netcdf/variable/@name" type="netcdf/variable/@type" shape="netcdf/variable/@shape"><br />
<attribute name="units" value="netcdf/variable/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable/attribute/@name=standard_name"/><br />
</variable><br />
<variable name="netcdf/variable2/@name" type="netcdf/variable2/@type" shape="netcdf/variable2/@shape"><br />
<attribute name="units" value="netcdf/variable2/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable2/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable2/attribute/@name=standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==Real-World Example==<br />
This NcML, taken from a very well documented CoastWatch file, includes real-world examples for all of the recommended attributes:<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="LMHchlaS8day_20100129000000"/><br />
<attribute name="naming_authority" value="gov.noaa.pfel.coastwatch"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Text Search --><br />
<attribute name="title" value="Chlorophyll-a, Aqua MODIS, NPP, 0.05 degrees, Global, Science Quality"/><br />
<attribute name="summary"<br />
value="NOAA CoastWatch distributes chlorophyll-a concentration data from NASA&apos;s Aqua Spacecraft. <br />
Measurements are gathered by the Moderate Resolution Imaging Spectroradiometer (MODIS) carried aboard the spacecraft.<br />
This is Science Quality data."/><br />
<attribute name="keywords" value="EARTH SCIENCE &gt; Oceans &gt; Ocean Chemistry &gt; Chlorophyll"/><br />
<attribute name="keywords_vocabulary" value="GCMD Science Keywords"/><br />
<attribute name="standard_name_vocabulary" value="CF-1.0"/><br />
<attribute name="history" value="NASA GSFC (G. Feldman): 2010-02-22T22:48:46Z NOAA CoastWatch (West Coast Node) and NOAA SFSC ERD"/><br />
<attribute name="comment" value="Text comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-90.0 " type="double"/><br />
<attribute name="geospatial_lat_max" value="90.0 " type="double"/><br />
<attribute name="geospatial_lon_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_lon_max" value="360.0 " type="double"/><br />
<attribute name="geospatial_vertical_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_max" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_positive" value="up"/><br />
<attribute name="time_coverage_end" value="2010-02-02T00:00:00Z"/><br />
<attribute name="time_coverage_start" value="2010-01-25T00:00:00Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="degrees_north"/><br />
<attribute name="geospatial_lat_resolution" value="0.041676313961565174" type="double"/><br />
<attribute name="geospatial_lon_units" value="degrees_east"/><br />
<attribute name="geospatial_lon_resolution" value="0.04167148975575877" type="double"/><br />
<attribute name="geospatial_vertical_units" value="m"/><br />
<attribute name="geospatial_vertical_resolution" value="1.0" type="double"/><br />
<attribute name="time_coverage_duration" value="P1D"/><br />
<attribute name="time_coverage_resolution" value="PT1M"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="NOAA NESDIS COASTWATCH, NOAA SWFSC ERD"/><br />
<attribute name="creator_email" value="dave.foley@noaa.gov"/><br />
<attribute name="creator_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="creator_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<attribute name="date_created" value="2010-02-22Z"/><br />
<attribute name="date_modified" value="2010-03-22Z"/><br />
<attribute name="date_issued" value="2010-02-22Z"/><br />
<attribute name="institution" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="project" value="CoastWatch (http://coastwatch.noaa.gov/)"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="NASA GSFC (G. Feldman)"/><br />
<attribute name="contributor_role" value="Source of level 2 data."/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_email" value="dave.foley@noaa.gov"/><br />
<attribute name="publisher_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="publisher_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="3"/><br />
<attribute name="license"<br />
value="The data may be used and redistributed for free but is not intended for legal use, since it may contain inaccuracies. Neither the data Contributor, CoastWatch, NOAA, nor the United States Government, nor any of their employees or contractors, makes any warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, or assumes any legal liability for the accuracy, completeness, or usefulness, of this information."/><br />
<attribute name="cdm_data_type" value="Grid"/><br />
</netcdf><br />
</pre><br />
=NetCDF Climate and Forecast (CF) Metadata Conventions=<br />
The [http://cf-pcmdi.llnl.gov/ NetCDF Climate and Forecast (CF) Metadata Conventions] are designed to promote the interoperable processing and sharing of data from netCDF files. They are focused on data ''use'' while the NetCDF Attribute Conventions are focused on data ''discovery''. Many of the discovery attributes that are related to extents can be calculated from the CF information:<br/><br />
geospatial_lat_min, geospatial_lat_max, geospatial_lat_units, geospatial_lat_res<br/><br />
geospatial_lon_min, geospatial_lon_max, geospatial_lon_units, geospatial_lon_res<br/><br />
geospatial_vertical_min, geospatial_vertical_max, geospatial_vertical_units, geospatial_vertical_res, geospatial_vertical_pos<br/><br />
time_coverage_start, time_coverage_end, time_coverage_units, time_coverage_duration, time_coverage_res<br/><br />
<br />
'''Note: We recommend explicitly listing these attributes in the file even though they can be calculated from the CF information in order to facilitate direct access to this information by tools that do not understand the CF Conventions.'''<br />
=Open Geospatial Consortium Catalog Service for the Web (CSW)=<br />
The [http://www.opengeospatial.org/standards/cat OGC CSW Service] includes ten core queryable elements that must be supported in all instances. CSW Profiles map these queryables to elements in various standards. The ISO Mappings are described in Section 7.2.3.1,Table 6 of OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile ([http://portal.opengeospatial.org/files/?artifact_id=21460 OGC 07-045]). The core queryables mapping is included in the Table above. An additional "any text" queryable covers all text in a record. Two core queryables are not covered by the NetCDF Attribute Convention for Dataset Discovery: Format and CRS.<br />
<br />
=ISO Translation Notes=<br />
The translation between the Attribute Conventions for Data Discovery is subject to a number of assumptions or conventions described here.<br />
==People==<br />
The ACDD includes several types of people:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td></tr><br />
<tr><br />
<td>creator_name, creator_email, creator_url, institution</td><br />
<td>citation/citedResponsibleParty role=originator, point of contact, and metadata contact</td><br />
<tr><br />
<tr><br />
<td>contributor_name, contributor_role</td><br />
<td>citation/citedResponsibleParty role=originator (may need adjustment)</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword, aggregation information (initiative type = project)</td><br />
</tr><br />
<br />
</table><br />
==Keywords==<br />
The ACDD includes several attributes that make sense as keywords in ISO:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td><br />
</tr><br />
<tr><br />
<td>keywords</td><br />
<td>theme keywords with thesaurus given by the keywords_vocabulary attribute</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword with unknown thesaurus and aggregation information (initiative type = project)</td><br />
</tr><br />
<tr><br />
<td>publisher_name</td><br />
<td>Data Center keyword with unknown thesaurus</td><br />
</tr><br />
<tr><br />
<td>standard_names for parameters</td><br />
<td>theme keywords with thesaurus = standard_name_vocabulary</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
=Translation Revisions=<br />
Several changes were introduced into [http://www.ngdc.noaa.gov/metadata/published/xsl/UnidataDD2MI.xsl Version 2.0.2] of the stylesheet for transforming NcML to ISO in order to improve the rubric score for the resulting ISO metadata. The changes included:<br />
#Including netcdf/@location in transform as distribution onlineResource<br />
#Added tagname to writeResponsibleParty so that responsibleParties with <br />
different UML roles could be supported (i.e. contact vs. distributor)<br />
#Added urlName and urlDescription to writeResponsibleParty to add <br />
content to the onlineResource<br />
#Moved publisher from citation to distributor and included publisher_name as a dataCenter keyword.<br />
#Added project as a keyword with type=project<br />
#Added distributionInfo section to ISO if publisher or location exist.<br />
<br />
=Determining an Order of Precedence=<br />
There can be conflicting information available from different sources within the THREDDS and CDM data models.<br />
The diagram below seeks to determine an order of precedence for what is recorded in the ncISO metadata when those attributes conflict.<br />
[[Image:Metadataprecedence.png]]<br />
<br />
A key part of this discussion is the ability to see identify potentially conflicting metdata between the differenc sources within THREDDS and NetCDF. Below we propose using groups to identify in the NCML what sources contain the relevant metadata that will be used in the ISO translation. <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<netcdf xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2 ../XSD/ncml-2.2.xsd"<br />
xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"<br />
location="http://localhost:8080/thredds/dodsC/test/crm_v1.nc"><br />
<br />
<!-- Metadata from the netCDF or NCML file global attributes --> <br />
<attribute name="Conventions" value="CF-1.4" /><br />
<attribute name="title" value="crm_v1.grd" /><br />
<attribute name="history" value="xyz2grd -R-80/-64/40/48 -I3c -Gcrm_v1.grd" /><br />
<attribute name="GMT_version" value="4.5.1 [64-bit]" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="geospatial_lon_units" value="degrees_east" /><br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_min" type="float" value="-80.0" /><br />
<attribute name="geospatial_lon_max" type="float" value="-64.0" /> <br />
<attribute name="geospatial_lat_max" type="float" value="48.0" /><br />
<attribute name="geospatial_lat_min" type="float" value="40.0" /><br />
<attribute name="geospatial_lon_resolution" type="double" value="8.33E-4" /><br />
<attribute name="geospatial_lat_resolution" type="double" value="8.33E-4" /><br />
<br />
<!-- Metadata calculated from the netCDF file axes based on CF conventions --><br />
<group name="CFMetadata"><br />
<attribute name="geospatial_lon_min" value="-80.0" type="float" /><br />
<attribute name="geospatial_lat_min" value="40.0" type="float" /><br />
<attribute name="geospatial_lon_max" value="-64.0" type="float" /><br />
<attribute name="geospatial_lat_max" value="48.0" type="float" /><br />
<attribute name="geospatial_lon_units" value="degrees_east" /> <br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_resolution" value="8.332899328159992E-4" /><br />
<attribute name="geospatial_lat_resolution" value="8.332465368190813E-4" /><br />
</group><br />
<br />
<!-- Metadata from the THREDDS catalog dataset --><br />
<group name="THREDDSMetadata"><br />
<attribute name="id" value="crm_v1" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="data_distribution" value="http://localhost:8080/thredds/dodsC/test/crm_v1.nc" /><br />
<attribute name="wms_service" value="http://localhost:8080//thredds/wms/crm/crm_vol9.nc" /><br />
<attribute name="wcs_service" value="http://localhost:8080//thredds/wcs/crm/crm_vol9.nc" /><br />
</group> <br />
<br />
<!-- Metadata from the ncISO service --><br />
<group name="NCISOMetadata"><br />
<attribute name="metadata_creation" value="2011-04-19" /><br />
</group><br />
<br />
<dimension name="x" length="19201" /><br />
<dimension name="y" length="9601" /><br />
<br />
<variable name="z" shape="y x" type="float"><br />
<attribute name="long_name" value="z" /><br />
<br />
<attribute name="_FillValue" type="float" value="NaN" /><br />
<attribute name="actual_range" type="double" value="-2754.39990234375 1903.0" /><br />
<attribute name="units" value="meters" /><br />
<attribute name="positive" value="up" /><br />
</variable><br />
<variable name="x" shape="x" type="double"><br />
<attribute name="long_name" value="x" /><br />
<attribute name="actual_range" type="double" value="-80.0 -64.0" /><br />
<attribute name="units" value="degrees_east" /><br />
<br />
<attribute name="_CoordinateAxisType" value="Lon" /><br />
</variable><br />
<variable name="y" shape="y" type="double"><br />
<attribute name="long_name" value="y" /><br />
<attribute name="actual_range" type="double" value="40.0 48.0" /><br />
<attribute name="units" value="degrees_north" /><br />
<attribute name="_CoordinateAxisType" value="Lat" /><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-1&diff=48980Attribute Convention for Data Discovery 1-12015-02-19T18:32:19Z<p>Graybeal: /* Version and Status */</p>
<hr />
<div>== Version and Status ==<br />
<br />
This version is designated as Version 1.1. As of January 1 2015 it is no longer the current version; see [Attribute Convention for Data Discovery] for the current version.<br />
<br />
See the [[http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page]] for information on the history of this convention.<br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained at [[Attribute_Convention_for_Data_Discovery_(ACDD)_Working]].<br />
<br />
----<br />
<br />
The netCDF Group at Unidata has [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html recommended] netCDF attributes for data discovery. Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
==Metadata Link==<br />
The netCDF metadata model is focused on providing "use metadata" for the data included in the file (or granule). Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "Metadata_Link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
=Highly Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#title_Attribute title]<br><br />
</td><br />
<td valign="top">A short description of the dataset.<br><br />
</td><br />
<td valign="top">dataset@name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString (M)<br><br />
</td><br />
<td>Title</td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#summary_Attribute summary]<br><br />
</td><br />
<td valign="top">A paragraph describing the dataset.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="summary"]<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract/gco:CharacterString (M)<br><br />
</td><br />
<td>Abstract</td> <br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_Attribute keywords]<br><br />
</td><br />
<td valign="top">A comma separated list of key words and phrases.<br><br />
</td><br />
<td valign="top">metadata/keyword<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br><br />
</td><br />
<td>Subject</td><br />
<td>Text Search</td><br />
</tr><br />
</table><br />
<br />
=Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#id_Attribute id]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The<br />
combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.<br><br />
</td><br />
<td rowspan="2" valign="top">dataset@id<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString (O)<br><br />
</td><br />
<td rowspan="2">Identifier</td><br />
<td rowspan="2">Identifier</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#naming_authority_Attribute naming_authority]<br><br />
</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_vocabulary_Attribute keywords_vocabulary]<br><br />
</td><br />
<td valign="top">If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.<br><br />
</td><br />
<td valign="top">metadata/keyword@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br><br />
</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#cdm_data_type_Attribute cdm_data_type]<br><br />
</td><br />
<td valign="top">The [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS data type] appropriate for this dataset.</td><br />
<td valign="top">metadata/dataType</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode<br> May need some extensions to this codelist. Current values: vector, grid, textTable, tin, stereoModel, video.<br />
</td><br />
<td></td><br />
<td>Other</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#history_Attribute history]<br></td><br />
<td valign="top">Provides an audit trail for modifications to the original data.</td><br />
<td valign="top">metadata/documentation[@type="history"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement/gco:CharacterString (O)</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#comment_Attribute comment]<br><br />
</td><br />
<td valign="top">Miscellaneous information about the data.</td><br />
<td valign="top">metadata/documentation<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:supplementalInformation<br><br />
</td><br />
<td></td><br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_created_Attribute date_created]</td><br />
<td valign="top">The date on which the data was created.<br><br />
</td><br />
<td valign="top">metadata/date[@type="created"]</td> <br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date (M)<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="creation"</br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_name_Attribute creator_name]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist. <br><br />
</td><br />
<td valign="top">metadata/creator/name<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
CI_RoleCode="originator" (O)</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_url_Attribute creator_url]<br><br />
</td> <br />
<td valign="top">metadata/creator/contact@url<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_email_Attribute creator_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/creator/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#institution_Attribute institution]<br><br />
</td><br />
<td valign="top">metadata/creator/name</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#project_Attribute project]<br><br />
</td><br />
<td valign="top">The scientific project that produced the data.<br><br />
</td><br />
<td valign="top">metadata/project<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:title/gco:CharacterString<br>DS_AssociationTypeCode="largerWorkCitation" and DS_InitiativeTypeCode="project"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="project"<br />
</td><br />
<td></td><br />
<td>Responsible Party</td> <br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#processing_level_Attribute processing_level]</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="processing_level"]</td><br />
<td></td><td></td><td></td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#acknowledgement_Attribute acknowledgement]</td><td valign="top">A place to acknowledge various type of support for the project that produced this data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="funding"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:credit/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">geospatial_bounds</td><br />
<td>Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the [http://en.wikipedia.org/wiki/Well-known_text Well-Known Text] (WKT) format.</td><br />
<td></td><br />
<td></td><br />
<td>BoundingPolygon</td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_min_Attribute geospatial_lat_min]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.<br/>The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.<br/>For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/start<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_max_Attribute geospatial_lat_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_min_Attribute geospatial_lon_min]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/start</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td> <br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_max_Attribute geospatial_lon_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_min_Attribute geospatial_vertical_min]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].</td><br />
<td valign="top">metadata/geospatialCoverage/updown/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:minimumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_max_Attribute geospatial_vertical_max]</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/size</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:maximumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_start_Attribute time_coverage_start]</td><br />
<td rowspan="4" colspan="1" valign="top">Describes the temporal coverage of the data as a time range.</td><br />
<td valign="top">metadata/timeCoverage/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_end_Attribute time_coverage_end]</td><br />
<td valign="top">metadata/timeCoverage/end</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:endPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_duration_Attribute time_coverage_duration]</td><br />
<td valign="top">metadata/timeCoverage/duration</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition provides an ISO8601 compliant description of the time period covered by the dataset. This standard supports descriptions of [http://en.wikipedia.org/wiki/ISO_8601#Durations durations].</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_resolution_Attribute time_coverage_resolution]</td><br />
<td valign="top">metadata/timeCoverage/resolution</td><br />
<td></td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute standard_name_vocabulary]<br><br />
</td><br />
<td valign="top">The name of the controlled vocabulary from which variable standard names are taken.<br><br />
</td><br />
<td valign="top">metadata/variables@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br></td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#license_Attribute license]</td><br />
<td valign="top">Describe the restrictions to data access and distribution. </td><br />
<td valign="top">metadata/documentation[@type="rights"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString<br></td><br />
<td></td><td></td><br />
</tr><br />
</table><br />
<br />
=Suggested=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_name_Attribute contributor_name]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The name and role of any individuals or institutions that contributed to the creation of this data.<br><br />
</td><br />
<td valign="top">metadata/contributor<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_role_Attribute contributor_role]<br><br />
</td><br />
<br />
<td valign="top">metadata/contributor@role</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode<br><br />
="principalInvestigator" | "author"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_name_Attribute publisher_name]<br><br />
</td><br />
<td rowspan="3" colspan="1" valign="top">The data publisher's name, URL, and email. The publisher may be an individual or an institution.</td><br />
<td valign="top">metadata/publisher/name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br>CI_RoleCode="publisher"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="dataCenter"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_url_Attribute publisher_url]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@url<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_email_Attribute publisher_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_modified_Attribute date_modified]<br><br />
</td><br />
<td valign="top">The date on which this data was last modified.<br><br />
</td><br />
<td valign="top">metadata/date[@type="modified"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="revision"</td><br />
<td>Modified</td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_issued_Attribute date_issued]<br><br />
</td><br />
<td valign="top">The date on which this data was formally issued.<br><br />
</td><br />
<td valign="top">metadata/date[@type="issued"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="publication"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_units_Attribute geospatial_lat_units]<br><br />
</td><br />
<td rowspan="7" colspan="1" valign="top">Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.<br><br />
<br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_resolution_Attribute geospatial_lat_resolution]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_units_Attribute geospatial_lon_units]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_resolution_Attribute geospatial_lon_resolution]</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_units_Attribute geospatial_vertical_units]<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/updown/units</td><br />
<td valign="top" rowspan="3">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:verticalCRS</td><br />
<td></td> <td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_resolution_Attribute geospatial_vertical_resolution]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/resolution<br><br />
</td> <br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_positive_Attribute geospatial_vertical_positive]<br><br />
</td><br />
<br />
<td valign="top">metadata/geospatialCoverage@zpositive<br><br />
</td><br />
<td></td><td>Extent</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#long_name_Attribute long_name]</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary).</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
<td rowspan="2" valign="top">At present the ISO 19115-2 Standard supports only one name for a variable. Standard names can be provided as keywords with the appropriate thesaurus.</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_Attribute standard_name]<br></td><br />
<td valign="top">A long descriptive name for the variable taken from a controlled vocabulary of variable names.</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#units_Attribute units]</td><br />
<td valign="top">The units of the variables data values. This attributes value should be a valid udunits string.</td><br />
<td valign="top">metadata/variables/variable@units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:contentInfo/gmi:MI_CoverageDescription/gmd:dimension/gmd:MD_Band/gmd:units</td><br />
</tr><br />
<tr><br />
<td valign="top">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data.</td><br />
<td valign="top"></td><br />
<td valign="top">The valid values in the MD_CoverageContentTypeCode list are image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, coordinate</td><br />
</tr><br />
</table><br />
<br />
=Conformance Test=<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
=Examples=<br />
==Attribute Names==<br />
This sample includes the attribute names as the values. It can be used to test transforms.<br />
<pre><br />
<?xml version='1.0' encoding='UTF-8'?><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="UnidataDataDiscoveryAttributes"/><br />
<attribute name="naming_authority" value="naming_authority"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="title"/><br />
<attribute name="summary" value="summary"/><br />
<attribute name="keywords" value="keywords"/><br />
<attribute name="keywords_vocabulary" value="keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="standard_name_vocabulary"/><br />
<attribute name="history" value="history"/><br />
<attribute name="comment" value="comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-89.999 " type="float"/><br />
<attribute name="geospatial_lat_max" value="89.999 " type="float"/><br />
<attribute name="geospatial_lon_min" value="-99.999 " type="float"/><br />
<attribute name="geospatial_lon_max" value="99.999 " type="float"/><br />
<attribute name="geospatial_vertical_min" value="-99.99 " type="float"/><br />
<attribute name="geospatial_vertical_max" value="99.99 " type="float"/><br />
<attribute name="time_coverage_start" value="1888-08-08T08:08:08Z"/><br />
<attribute name="time_coverage_end" value="1777-07-07T07:07:07Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="8.888" type="float"/><br />
<attribute name="geospatial_lon_units" value="geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="9.999" type="float"/><br />
<attribute name="geospatial_vertical_units" value="geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="999.0" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="P2Y2M2D"/><br />
<attribute name="time_coverage_resolution" value="P1Y1M1D"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="acknowledgment"/><br />
<attribute name="creator_email" value="creator_email"/><br />
<attribute name="creator_name" value="creator_name"/><br />
<attribute name="creator_url" value="creator_url"/><br />
<attribute name="date_created" value="1666-06-06T06:06:06Z"/><br />
<attribute name="date_modified" value="1999-09-09T09:09:09Z"/><br />
<attribute name="date_issued" value="2111-01-01T01:01:01Z"/><br />
<attribute name="institution" value="institution"/><br />
<attribute name="project" value="project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="contributor_name"/><br />
<attribute name="contributor_role" value="contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="publisher_name"/><br />
<attribute name="publisher_url" value="publisher_url"/><br />
<attribute name="publisher_email" value="publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="processing_level"/><br />
<attribute name="license" value="license"/><br />
<attribute name="cdm_data_type" value="cdm_data_type"/><br />
<variable name="tv" type="float" shape="depdp"><br />
<attribute name="units" value="units"/><br />
<attribute name="name" value="testVariable"/><br />
<attribute name="long_name" value="Test Variable - long name"/><br />
<attribute name="standard_name" value="test_variable_standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==XPaths==<br />
Sometimes an example with XPaths is useful. Note that this example includes service endpoints in the Service Endpoints section that are added by the ncISO capability in the THREDDS Data Server. ''These are not typically included in the netCDF file'':<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="netcdf/attribute/@name=id"/><br />
<attribute name="naming_authority" value="netcdf/attribute/@name=naming_authority"/><br />
<attribute name="Metadata_Conventions" value="netcdf/attribute/@name=Metadata_Conventions"/><br />
<attribute name="Metadata_Link" value="netcdf/attribute/@name=Metadata_Link"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="netcdf/attribute/@name=thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="netcdf/attribute/@name=thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="netcdf/attribute/@name=thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="netcdf/attribute/@name=thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="netcdf/attribute/@name=title"/><br />
<attribute name="summary" value="netcdf/attribute/@name=summary"/><br />
<attribute name="keywords" value="netcdf/attribute/@name=keywords"/><br />
<attribute name="keywords_vocabulary" value="netcdf/attribute/@name=keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="netcdf/attribute/@name=standard_name_vocabulary"/><br />
<attribute name="history" value="netcdf/attribute/@name=history"/><br />
<attribute name="comment" value="netcdf/attribute/@name=comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="netcdf/attribute/@name=geospatial_lat_min" type="float"/><br />
<attribute name="geospatial_lat_max" value="netcdf/attribute/@name=geospatial_lat_max" type="float"/><br />
<attribute name="geospatial_lon_min" value="netcdf/attribute/@name=geospatial_lon_min" type="float"/><br />
<attribute name="geospatial_lon_max" value="netcdf/attribute/@name=geospatial_lon_max " type="float"/><br />
<attribute name="geospatial_vertical_min" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="geospatial_vertical_max" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="time_coverage_start" value="netcdf/attribute/@name=time_coverage_start"/><br />
<attribute name="time_coverage_end" value="netcdf/attribute/@name=time_coverage_end"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="netcdf/attribute/@name=geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="netcdf/attribute/@name=geospatial_lat_resolution" type="float"/><br />
<attribute name="geospatial_lon_units" value="netcdf/attribute/@name=geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="netcdf/attribute/@name=geospatial_lon_resolution" type="float"/><br />
<attribute name="geospatial_vertical_units" value="netcdf/attribute/@name=geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="netcdf/attribute/@name=geospatial_vertical_resolution" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="netcdf/attribute/@name=geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="netcdf/attribute/@name=time_coverage_duration"/><br />
<attribute name="time_coverage_resolution" value="netcdf/attribute/@name=time_coverage_resolution"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="netcdf/attribute/@name=acknowledgment"/><br />
<attribute name="creator_email" value="netcdf/attribute/@name=creator_email"/><br />
<attribute name="creator_name" value="netcdf/attribute/@name=creator_name"/><br />
<attribute name="creator_url" value="netcdf/attribute/@name=creator_url"/><br />
<attribute name="date_created" value="netcdf/attribute/@name=date_created"/><br />
<attribute name="date_modified" value="netcdf/attribute/@name=date_modified"/><br />
<attribute name="date_issued" value="netcdf/attribute/@name=date_issued"/><br />
<attribute name="institution" value="netcdf/attribute/@name=institution"/><br />
<attribute name="project" value="netcdf/attribute/@name=project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="netcdf/attribute/@name=contributor_name"/><br />
<attribute name="contributor_role" value="netcdf/attribute/@name=contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="netcdf/attribute/@name=publisher_name"/><br />
<attribute name="publisher_url" value="netcdf/attribute/@name=publisher_url"/><br />
<attribute name="publisher_email" value="netcdf/attribute/@name=publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="netcdf/attribute/@name=processing_level"/><br />
<attribute name="license" value="netcdf/attribute/@name=license"/><br />
<attribute name="cdm_data_type" value="netcdf/attribute/@name=cdm_data_type"/><br />
<variable name="netcdf/variable/@name" type="netcdf/variable/@type" shape="netcdf/variable/@shape"><br />
<attribute name="units" value="netcdf/variable/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable/attribute/@name=standard_name"/><br />
</variable><br />
<variable name="netcdf/variable2/@name" type="netcdf/variable2/@type" shape="netcdf/variable2/@shape"><br />
<attribute name="units" value="netcdf/variable2/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable2/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable2/attribute/@name=standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==Real-World Example==<br />
This NcML, taken from a very well documented CoastWatch file, includes real-world examples for all of the recommended attributes:<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="LMHchlaS8day_20100129000000"/><br />
<attribute name="naming_authority" value="gov.noaa.pfel.coastwatch"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Text Search --><br />
<attribute name="title" value="Chlorophyll-a, Aqua MODIS, NPP, 0.05 degrees, Global, Science Quality"/><br />
<attribute name="summary"<br />
value="NOAA CoastWatch distributes chlorophyll-a concentration data from NASA&apos;s Aqua Spacecraft. <br />
Measurements are gathered by the Moderate Resolution Imaging Spectroradiometer (MODIS) carried aboard the spacecraft.<br />
This is Science Quality data."/><br />
<attribute name="keywords" value="EARTH SCIENCE &gt; Oceans &gt; Ocean Chemistry &gt; Chlorophyll"/><br />
<attribute name="keywords_vocabulary" value="GCMD Science Keywords"/><br />
<attribute name="standard_name_vocabulary" value="CF-1.0"/><br />
<attribute name="history" value="NASA GSFC (G. Feldman): 2010-02-22T22:48:46Z NOAA CoastWatch (West Coast Node) and NOAA SFSC ERD"/><br />
<attribute name="comment" value="Text comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-90.0 " type="double"/><br />
<attribute name="geospatial_lat_max" value="90.0 " type="double"/><br />
<attribute name="geospatial_lon_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_lon_max" value="360.0 " type="double"/><br />
<attribute name="geospatial_vertical_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_max" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_positive" value="up"/><br />
<attribute name="time_coverage_end" value="2010-02-02T00:00:00Z"/><br />
<attribute name="time_coverage_start" value="2010-01-25T00:00:00Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="degrees_north"/><br />
<attribute name="geospatial_lat_resolution" value="0.041676313961565174" type="double"/><br />
<attribute name="geospatial_lon_units" value="degrees_east"/><br />
<attribute name="geospatial_lon_resolution" value="0.04167148975575877" type="double"/><br />
<attribute name="geospatial_vertical_units" value="m"/><br />
<attribute name="geospatial_vertical_resolution" value="1.0" type="double"/><br />
<attribute name="time_coverage_duration" value="P1D"/><br />
<attribute name="time_coverage_resolution" value="PT1M"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="NOAA NESDIS COASTWATCH, NOAA SWFSC ERD"/><br />
<attribute name="creator_email" value="dave.foley@noaa.gov"/><br />
<attribute name="creator_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="creator_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<attribute name="date_created" value="2010-02-22Z"/><br />
<attribute name="date_modified" value="2010-03-22Z"/><br />
<attribute name="date_issued" value="2010-02-22Z"/><br />
<attribute name="institution" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="project" value="CoastWatch (http://coastwatch.noaa.gov/)"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="NASA GSFC (G. Feldman)"/><br />
<attribute name="contributor_role" value="Source of level 2 data."/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_email" value="dave.foley@noaa.gov"/><br />
<attribute name="publisher_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="publisher_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="3"/><br />
<attribute name="license"<br />
value="The data may be used and redistributed for free but is not intended for legal use, since it may contain inaccuracies. Neither the data Contributor, CoastWatch, NOAA, nor the United States Government, nor any of their employees or contractors, makes any warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, or assumes any legal liability for the accuracy, completeness, or usefulness, of this information."/><br />
<attribute name="cdm_data_type" value="Grid"/><br />
</netcdf><br />
</pre><br />
=NetCDF Climate and Forecast (CF) Metadata Conventions=<br />
The [http://cf-pcmdi.llnl.gov/ NetCDF Climate and Forecast (CF) Metadata Conventions] are designed to promote the interoperable processing and sharing of data from netCDF files. They are focused on data ''use'' while the NetCDF Attribute Conventions are focused on data ''discovery''. Many of the discovery attributes that are related to extents can be calculated from the CF information:<br/><br />
geospatial_lat_min, geospatial_lat_max, geospatial_lat_units, geospatial_lat_res<br/><br />
geospatial_lon_min, geospatial_lon_max, geospatial_lon_units, geospatial_lon_res<br/><br />
geospatial_vertical_min, geospatial_vertical_max, geospatial_vertical_units, geospatial_vertical_res, geospatial_vertical_pos<br/><br />
time_coverage_start, time_coverage_end, time_coverage_units, time_coverage_duration, time_coverage_res<br/><br />
<br />
'''Note: We recommend explicitly listing these attributes in the file even though they can be calculated from the CF information in order to facilitate direct access to this information by tools that do not understand the CF Conventions.'''<br />
=Open Geospatial Consortium Catalog Service for the Web (CSW)=<br />
The [http://www.opengeospatial.org/standards/cat OGC CSW Service] includes ten core queryable elements that must be supported in all instances. CSW Profiles map these queryables to elements in various standards. The ISO Mappings are described in Section 7.2.3.1,Table 6 of OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile ([http://portal.opengeospatial.org/files/?artifact_id=21460 OGC 07-045]). The core queryables mapping is included in the Table above. An additional "any text" queryable covers all text in a record. Two core queryables are not covered by the NetCDF Attribute Convention for Dataset Discovery: Format and CRS.<br />
<br />
=ISO Translation Notes=<br />
The translation between the Attribute Conventions for Data Discovery is subject to a number of assumptions or conventions described here.<br />
==People==<br />
The ACDD includes several types of people:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td></tr><br />
<tr><br />
<td>creator_name, creator_email, creator_url, institution</td><br />
<td>citation/citedResponsibleParty role=originator, point of contact, and metadata contact</td><br />
<tr><br />
<tr><br />
<td>contributor_name, contributor_role</td><br />
<td>citation/citedResponsibleParty role=originator (may need adjustment)</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword, aggregation information (initiative type = project)</td><br />
</tr><br />
<br />
</table><br />
==Keywords==<br />
The ACDD includes several attributes that make sense as keywords in ISO:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td><br />
</tr><br />
<tr><br />
<td>keywords</td><br />
<td>theme keywords with thesaurus given by the keywords_vocabulary attribute</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword with unknown thesaurus and aggregation information (initiative type = project)</td><br />
</tr><br />
<tr><br />
<td>publisher_name</td><br />
<td>Data Center keyword with unknown thesaurus</td><br />
</tr><br />
<tr><br />
<td>standard_names for parameters</td><br />
<td>theme keywords with thesaurus = standard_name_vocabulary</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
=Translation Revisions=<br />
Several changes were introduced into [http://www.ngdc.noaa.gov/metadata/published/xsl/UnidataDD2MI.xsl Version 2.0.2] of the stylesheet for transforming NcML to ISO in order to improve the rubric score for the resulting ISO metadata. The changes included:<br />
#Including netcdf/@location in transform as distribution onlineResource<br />
#Added tagname to writeResponsibleParty so that responsibleParties with <br />
different UML roles could be supported (i.e. contact vs. distributor)<br />
#Added urlName and urlDescription to writeResponsibleParty to add <br />
content to the onlineResource<br />
#Moved publisher from citation to distributor and included publisher_name as a dataCenter keyword.<br />
#Added project as a keyword with type=project<br />
#Added distributionInfo section to ISO if publisher or location exist.<br />
<br />
=Determining an Order of Precedence=<br />
There can be conflicting information available from different sources within the THREDDS and CDM data models.<br />
The diagram below seeks to determine an order of precedence for what is recorded in the ncISO metadata when those attributes conflict.<br />
[[Image:Metadataprecedence.png]]<br />
<br />
A key part of this discussion is the ability to see identify potentially conflicting metdata between the differenc sources within THREDDS and NetCDF. Below we propose using groups to identify in the NCML what sources contain the relevant metadata that will be used in the ISO translation. <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<netcdf xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2 ../XSD/ncml-2.2.xsd"<br />
xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"<br />
location="http://localhost:8080/thredds/dodsC/test/crm_v1.nc"><br />
<br />
<!-- Metadata from the netCDF or NCML file global attributes --> <br />
<attribute name="Conventions" value="CF-1.4" /><br />
<attribute name="title" value="crm_v1.grd" /><br />
<attribute name="history" value="xyz2grd -R-80/-64/40/48 -I3c -Gcrm_v1.grd" /><br />
<attribute name="GMT_version" value="4.5.1 [64-bit]" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="geospatial_lon_units" value="degrees_east" /><br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_min" type="float" value="-80.0" /><br />
<attribute name="geospatial_lon_max" type="float" value="-64.0" /> <br />
<attribute name="geospatial_lat_max" type="float" value="48.0" /><br />
<attribute name="geospatial_lat_min" type="float" value="40.0" /><br />
<attribute name="geospatial_lon_resolution" type="double" value="8.33E-4" /><br />
<attribute name="geospatial_lat_resolution" type="double" value="8.33E-4" /><br />
<br />
<!-- Metadata calculated from the netCDF file axes based on CF conventions --><br />
<group name="CFMetadata"><br />
<attribute name="geospatial_lon_min" value="-80.0" type="float" /><br />
<attribute name="geospatial_lat_min" value="40.0" type="float" /><br />
<attribute name="geospatial_lon_max" value="-64.0" type="float" /><br />
<attribute name="geospatial_lat_max" value="48.0" type="float" /><br />
<attribute name="geospatial_lon_units" value="degrees_east" /> <br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_resolution" value="8.332899328159992E-4" /><br />
<attribute name="geospatial_lat_resolution" value="8.332465368190813E-4" /><br />
</group><br />
<br />
<!-- Metadata from the THREDDS catalog dataset --><br />
<group name="THREDDSMetadata"><br />
<attribute name="id" value="crm_v1" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="data_distribution" value="http://localhost:8080/thredds/dodsC/test/crm_v1.nc" /><br />
<attribute name="wms_service" value="http://localhost:8080//thredds/wms/crm/crm_vol9.nc" /><br />
<attribute name="wcs_service" value="http://localhost:8080//thredds/wcs/crm/crm_vol9.nc" /><br />
</group> <br />
<br />
<!-- Metadata from the ncISO service --><br />
<group name="NCISOMetadata"><br />
<attribute name="metadata_creation" value="2011-04-19" /><br />
</group><br />
<br />
<dimension name="x" length="19201" /><br />
<dimension name="y" length="9601" /><br />
<br />
<variable name="z" shape="y x" type="float"><br />
<attribute name="long_name" value="z" /><br />
<br />
<attribute name="_FillValue" type="float" value="NaN" /><br />
<attribute name="actual_range" type="double" value="-2754.39990234375 1903.0" /><br />
<attribute name="units" value="meters" /><br />
<attribute name="positive" value="up" /><br />
</variable><br />
<variable name="x" shape="x" type="double"><br />
<attribute name="long_name" value="x" /><br />
<attribute name="actual_range" type="double" value="-80.0 -64.0" /><br />
<attribute name="units" value="degrees_east" /><br />
<br />
<attribute name="_CoordinateAxisType" value="Lon" /><br />
</variable><br />
<variable name="y" shape="y" type="double"><br />
<attribute name="long_name" value="y" /><br />
<attribute name="actual_range" type="double" value="40.0 48.0" /><br />
<attribute name="units" value="degrees_north" /><br />
<attribute name="_CoordinateAxisType" value="Lat" /><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-1&diff=48979Attribute Convention for Data Discovery 1-12015-02-19T18:31:51Z<p>Graybeal: /* Version and Status */ updated to reflect this is no longer the current version</p>
<hr />
<div>== Version and Status ==<br />
<br />
This version is designated as Version 1.1. As of January 1 2015 it is no longer the current version; see [Attribute_Convention_for_Data_Discovery] for the current version.<br />
<br />
See the [[http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page]] for information on the history of this convention.<br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained at [[Attribute_Convention_for_Data_Discovery_(ACDD)_Working]].<br />
<br />
----<br />
<br />
The netCDF Group at Unidata has [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html recommended] netCDF attributes for data discovery. Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
==Metadata Link==<br />
The netCDF metadata model is focused on providing "use metadata" for the data included in the file (or granule). Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "Metadata_Link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
=Highly Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#title_Attribute title]<br><br />
</td><br />
<td valign="top">A short description of the dataset.<br><br />
</td><br />
<td valign="top">dataset@name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString (M)<br><br />
</td><br />
<td>Title</td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#summary_Attribute summary]<br><br />
</td><br />
<td valign="top">A paragraph describing the dataset.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="summary"]<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract/gco:CharacterString (M)<br><br />
</td><br />
<td>Abstract</td> <br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_Attribute keywords]<br><br />
</td><br />
<td valign="top">A comma separated list of key words and phrases.<br><br />
</td><br />
<td valign="top">metadata/keyword<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br><br />
</td><br />
<td>Subject</td><br />
<td>Text Search</td><br />
</tr><br />
</table><br />
<br />
=Recommended=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#id_Attribute id]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The<br />
combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.<br><br />
</td><br />
<td rowspan="2" valign="top">dataset@id<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString (O)<br><br />
</td><br />
<td rowspan="2">Identifier</td><br />
<td rowspan="2">Identifier</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#naming_authority_Attribute naming_authority]<br><br />
</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#keywords_vocabulary_Attribute keywords_vocabulary]<br><br />
</td><br />
<td valign="top">If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.<br><br />
</td><br />
<td valign="top">metadata/keyword@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br><br />
</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#cdm_data_type_Attribute cdm_data_type]<br><br />
</td><br />
<td valign="top">The [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS data type] appropriate for this dataset.</td><br />
<td valign="top">metadata/dataType</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode<br> May need some extensions to this codelist. Current values: vector, grid, textTable, tin, stereoModel, video.<br />
</td><br />
<td></td><br />
<td>Other</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#history_Attribute history]<br></td><br />
<td valign="top">Provides an audit trail for modifications to the original data.</td><br />
<td valign="top">metadata/documentation[@type="history"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement/gco:CharacterString (O)</td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#comment_Attribute comment]<br><br />
</td><br />
<td valign="top">Miscellaneous information about the data.</td><br />
<td valign="top">metadata/documentation<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:supplementalInformation<br><br />
</td><br />
<td></td><br />
<td>Text Search</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_created_Attribute date_created]</td><br />
<td valign="top">The date on which the data was created.<br><br />
</td><br />
<td valign="top">metadata/date[@type="created"]</td> <br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date (M)<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="creation"</br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_name_Attribute creator_name]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist. <br><br />
</td><br />
<td valign="top">metadata/creator/name<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
CI_RoleCode="originator" (O)</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_url_Attribute creator_url]<br><br />
</td> <br />
<td valign="top">metadata/creator/contact@url<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br></td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#creator_email_Attribute creator_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/creator/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#institution_Attribute institution]<br><br />
</td><br />
<td valign="top">metadata/creator/name</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#project_Attribute project]<br><br />
</td><br />
<td valign="top">The scientific project that produced the data.<br><br />
</td><br />
<td valign="top">metadata/project<br></td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:title/gco:CharacterString<br>DS_AssociationTypeCode="largerWorkCitation" and DS_InitiativeTypeCode="project"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="project"<br />
</td><br />
<td></td><br />
<td>Responsible Party</td> <br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#processing_level_Attribute processing_level]</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="processing_level"]</td><br />
<td></td><td></td><td></td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#acknowledgement_Attribute acknowledgement]</td><td valign="top">A place to acknowledge various type of support for the project that produced this data.<br><br />
</td><br />
<td valign="top">metadata/documentation[@type="funding"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:credit/gco:CharacterString</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">geospatial_bounds</td><br />
<td>Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the [http://en.wikipedia.org/wiki/Well-known_text Well-Known Text] (WKT) format.</td><br />
<td></td><br />
<td></td><br />
<td>BoundingPolygon</td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_min_Attribute geospatial_lat_min]<br><br />
</td><br />
<td rowspan="4" colspan="1" valign="top">Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.<br/>The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.<br/>For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/start<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_max_Attribute geospatial_lat_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLatitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_min_Attribute geospatial_lon_min]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/start</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td> <br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_max_Attribute geospatial_lon_max]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/eastwest/size</td><br />
<br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal<br><br />
</td><br />
<td>BoundingBox</td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_min_Attribute geospatial_vertical_min]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#suggested_geospatial suggested geospatial attributes].</td><br />
<td valign="top">metadata/geospatialCoverage/updown/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:minimumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_max_Attribute geospatial_vertical_max]</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/size</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:maximumValue/gco:Real</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_start_Attribute time_coverage_start]</td><br />
<td rowspan="4" colspan="1" valign="top">Describes the temporal coverage of the data as a time range.</td><br />
<td valign="top">metadata/timeCoverage/start</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_end_Attribute time_coverage_end]</td><br />
<td valign="top">metadata/timeCoverage/end</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:endPosition</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_duration_Attribute time_coverage_duration]</td><br />
<td valign="top">metadata/timeCoverage/duration</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod/gml:beginPosition provides an ISO8601 compliant description of the time period covered by the dataset. This standard supports descriptions of [http://en.wikipedia.org/wiki/ISO_8601#Durations durations].</td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#time_coverage_resolution_Attribute time_coverage_resolution]</td><br />
<td valign="top">metadata/timeCoverage/resolution</td><br />
<td></td><br />
<td></td><br />
<td>Extent</td> <br />
</tr><tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute standard_name_vocabulary]<br><br />
</td><br />
<td valign="top">The name of the controlled vocabulary from which variable standard names are taken.<br><br />
</td><br />
<td valign="top">metadata/variables@vocabulary</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString <br></td><br />
<td></td><br />
<td>Text Search</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#license_Attribute license]</td><br />
<td valign="top">Describe the restrictions to data access and distribution. </td><br />
<td valign="top">metadata/documentation[@type="rights"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString<br></td><br />
<td></td><td></td><br />
</tr><br />
</table><br />
<br />
=Suggested=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
<th valign="top">OGC CSW</th><br />
<th valign="top">Rubric Category</th><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_name_Attribute contributor_name]<br><br />
</td><br />
<td rowspan="2" colspan="1" valign="top">The name and role of any individuals or institutions that contributed to the creation of this data.<br><br />
</td><br />
<td valign="top">metadata/contributor<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br><br />
</td><br />
<td></td><br />
<td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#contributor_role_Attribute contributor_role]<br><br />
</td><br />
<br />
<td valign="top">metadata/contributor@role</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode<br><br />
="principalInvestigator" | "author"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_name_Attribute publisher_name]<br><br />
</td><br />
<td rowspan="3" colspan="1" valign="top">The data publisher's name, URL, and email. The publisher may be an individual or an institution.</td><br />
<td valign="top">metadata/publisher/name<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString<br>CI_RoleCode="publisher"<br/>and/or<br/><br />
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/gco:CharacterString with gmd:MD_KeywordTypeCode="dataCenter"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_url_Attribute publisher_url]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@url<br><br />
</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#publisher_email_Attribute publisher_email]<br><br />
</td><br />
<br />
<td valign="top">metadata/publisher/contact@email</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br/>and/or<br/>/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress/gco:CharacterString<br><br />
CI_RoleCode="publisher"</td><br />
<td></td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_modified_Attribute date_modified]<br><br />
</td><br />
<td valign="top">The date on which this data was last modified.<br><br />
</td><br />
<td valign="top">metadata/date[@type="modified"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="revision"</td><br />
<td>Modified</td><td>Responsible Party</td><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#date_issued_Attribute date_issued]<br><br />
</td><br />
<td valign="top">The date on which this data was formally issued.<br><br />
</td><br />
<td valign="top">metadata/date[@type="issued"]</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:Date<br><br />
/gmd:dateType/gmd:CI_DateTypeCode="publication"</td><br />
<td></td><td>Responsible Party</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_units_Attribute geospatial_lat_units]<br><br />
</td><br />
<td rowspan="7" colspan="1" valign="top">Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.<br><br />
<br />
</td><br />
<td valign="top">metadata/geospatialCoverage/northsouth/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lat_resolution_Attribute geospatial_lat_resolution]</td><br />
<br />
<td valign="top">metadata/geospatialCoverage/northsouth/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_units_Attribute geospatial_lon_units]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure/@uom</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_lon_resolution_Attribute geospatial_lon_resolution]</td> <br />
<td valign="top">metadata/geospatialCoverage/eastwest/resolution</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:spatialRepresentationInfo/gmd:MD_Georectified/gmd:axisDimensionProperties/gmd:MD_Dimension/gmd:resolution/gco:Measure</td><br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_units_Attribute geospatial_vertical_units]<br><br />
</td><br />
<td valign="top">metadata/geospatialCoverage/updown/units</td><br />
<td valign="top" rowspan="3">/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:verticalElement/gmd:EX_VerticalExtent/gmd:verticalCRS</td><br />
<td></td> <td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_resolution_Attribute geospatial_vertical_resolution]<br><br />
</td> <br />
<td valign="top">metadata/geospatialCoverage/updown/resolution<br><br />
</td> <br />
<td></td><td>Extent</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#geospatial_vertical_positive_Attribute geospatial_vertical_positive]<br><br />
</td><br />
<br />
<td valign="top">metadata/geospatialCoverage@zpositive<br><br />
</td><br />
<td></td><td>Extent</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top">Attribute</th><br />
<th valign="top">Description</th><br />
<th valign="top">THREDDS</th><br />
<th valign="top">ISO 19115-2</th><br />
</tr> <br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#long_name_Attribute long_name]</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary).</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
<td rowspan="2" valign="top">At present the ISO 19115-2 Standard supports only one name for a variable. Standard names can be provided as keywords with the appropriate thesaurus.</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_Attribute standard_name]<br></td><br />
<td valign="top">A long descriptive name for the variable taken from a controlled vocabulary of variable names.</td><br />
<td valign="top">metadata/variables/variable@vocabulary_name</td><br />
</tr><br />
<tr><br />
<td valign="top">[http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#units_Attribute units]</td><br />
<td valign="top">The units of the variables data values. This attributes value should be a valid udunits string.</td><br />
<td valign="top">metadata/variables/variable@units</td><br />
<td valign="top">/gmi:MI_Metadata/gmd:contentInfo/gmi:MI_CoverageDescription/gmd:dimension/gmd:MD_Band/gmd:units</td><br />
</tr><br />
<tr><br />
<td valign="top">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data.</td><br />
<td valign="top"></td><br />
<td valign="top">The valid values in the MD_CoverageContentTypeCode list are image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, coordinate</td><br />
</tr><br />
</table><br />
<br />
=Conformance Test=<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
=Examples=<br />
==Attribute Names==<br />
This sample includes the attribute names as the values. It can be used to test transforms.<br />
<pre><br />
<?xml version='1.0' encoding='UTF-8'?><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="UnidataDataDiscoveryAttributes"/><br />
<attribute name="naming_authority" value="naming_authority"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="title"/><br />
<attribute name="summary" value="summary"/><br />
<attribute name="keywords" value="keywords"/><br />
<attribute name="keywords_vocabulary" value="keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="standard_name_vocabulary"/><br />
<attribute name="history" value="history"/><br />
<attribute name="comment" value="comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-89.999 " type="float"/><br />
<attribute name="geospatial_lat_max" value="89.999 " type="float"/><br />
<attribute name="geospatial_lon_min" value="-99.999 " type="float"/><br />
<attribute name="geospatial_lon_max" value="99.999 " type="float"/><br />
<attribute name="geospatial_vertical_min" value="-99.99 " type="float"/><br />
<attribute name="geospatial_vertical_max" value="99.99 " type="float"/><br />
<attribute name="time_coverage_start" value="1888-08-08T08:08:08Z"/><br />
<attribute name="time_coverage_end" value="1777-07-07T07:07:07Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="8.888" type="float"/><br />
<attribute name="geospatial_lon_units" value="geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="9.999" type="float"/><br />
<attribute name="geospatial_vertical_units" value="geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="999.0" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="P2Y2M2D"/><br />
<attribute name="time_coverage_resolution" value="P1Y1M1D"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="acknowledgment"/><br />
<attribute name="creator_email" value="creator_email"/><br />
<attribute name="creator_name" value="creator_name"/><br />
<attribute name="creator_url" value="creator_url"/><br />
<attribute name="date_created" value="1666-06-06T06:06:06Z"/><br />
<attribute name="date_modified" value="1999-09-09T09:09:09Z"/><br />
<attribute name="date_issued" value="2111-01-01T01:01:01Z"/><br />
<attribute name="institution" value="institution"/><br />
<attribute name="project" value="project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="contributor_name"/><br />
<attribute name="contributor_role" value="contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="publisher_name"/><br />
<attribute name="publisher_url" value="publisher_url"/><br />
<attribute name="publisher_email" value="publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="processing_level"/><br />
<attribute name="license" value="license"/><br />
<attribute name="cdm_data_type" value="cdm_data_type"/><br />
<variable name="tv" type="float" shape="depdp"><br />
<attribute name="units" value="units"/><br />
<attribute name="name" value="testVariable"/><br />
<attribute name="long_name" value="Test Variable - long name"/><br />
<attribute name="standard_name" value="test_variable_standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==XPaths==<br />
Sometimes an example with XPaths is useful. Note that this example includes service endpoints in the Service Endpoints section that are added by the ncISO capability in the THREDDS Data Server. ''These are not typically included in the netCDF file'':<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="netcdf/attribute/@name=id"/><br />
<attribute name="naming_authority" value="netcdf/attribute/@name=naming_authority"/><br />
<attribute name="Metadata_Conventions" value="netcdf/attribute/@name=Metadata_Conventions"/><br />
<attribute name="Metadata_Link" value="netcdf/attribute/@name=Metadata_Link"/><br />
<!-- Service Endpoints --><br />
<attribute name="thredds_netcdfsubset_service" value="netcdf/attribute/@name=thredds_netcdfsubset_service" /><br />
<attribute name="thredds_opendap_service" value="netcdf/attribute/@name=thredds_opendap_service" /><br />
<attribute name="thredds_wms_service" value="netcdf/attribute/@name=thredds_wms_service"/><br />
<attribute name="thredds_wcs_service" value="netcdf/attribute/@name=thredds_wcs_service"/><br />
<!-- Text Search --><br />
<attribute name="title" value="netcdf/attribute/@name=title"/><br />
<attribute name="summary" value="netcdf/attribute/@name=summary"/><br />
<attribute name="keywords" value="netcdf/attribute/@name=keywords"/><br />
<attribute name="keywords_vocabulary" value="netcdf/attribute/@name=keyword_vocabulary"/><br />
<attribute name="standard_name_vocabulary" value="netcdf/attribute/@name=standard_name_vocabulary"/><br />
<attribute name="history" value="netcdf/attribute/@name=history"/><br />
<attribute name="comment" value="netcdf/attribute/@name=comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="netcdf/attribute/@name=geospatial_lat_min" type="float"/><br />
<attribute name="geospatial_lat_max" value="netcdf/attribute/@name=geospatial_lat_max" type="float"/><br />
<attribute name="geospatial_lon_min" value="netcdf/attribute/@name=geospatial_lon_min" type="float"/><br />
<attribute name="geospatial_lon_max" value="netcdf/attribute/@name=geospatial_lon_max " type="float"/><br />
<attribute name="geospatial_vertical_min" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="geospatial_vertical_max" value="netcdf/attribute/@name=geospatial_vertical_min" type="float"/><br />
<attribute name="time_coverage_start" value="netcdf/attribute/@name=time_coverage_start"/><br />
<attribute name="time_coverage_end" value="netcdf/attribute/@name=time_coverage_end"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="netcdf/attribute/@name=geospatial_lat_units"/><br />
<attribute name="geospatial_lat_resolution" value="netcdf/attribute/@name=geospatial_lat_resolution" type="float"/><br />
<attribute name="geospatial_lon_units" value="netcdf/attribute/@name=geospatial_lon_units"/><br />
<attribute name="geospatial_lon_resolution" value="netcdf/attribute/@name=geospatial_lon_resolution" type="float"/><br />
<attribute name="geospatial_vertical_units" value="netcdf/attribute/@name=geospatial_vertical_units"/><br />
<attribute name="geospatial_vertical_resolution" value="netcdf/attribute/@name=geospatial_vertical_resolution" type="float"/><br />
<attribute name="geospatial_vertical_positive" value="netcdf/attribute/@name=geospatial_vertical_positive"/><br />
<attribute name="time_coverage_duration" value="netcdf/attribute/@name=time_coverage_duration"/><br />
<attribute name="time_coverage_resolution" value="netcdf/attribute/@name=time_coverage_resolution"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="netcdf/attribute/@name=acknowledgment"/><br />
<attribute name="creator_email" value="netcdf/attribute/@name=creator_email"/><br />
<attribute name="creator_name" value="netcdf/attribute/@name=creator_name"/><br />
<attribute name="creator_url" value="netcdf/attribute/@name=creator_url"/><br />
<attribute name="date_created" value="netcdf/attribute/@name=date_created"/><br />
<attribute name="date_modified" value="netcdf/attribute/@name=date_modified"/><br />
<attribute name="date_issued" value="netcdf/attribute/@name=date_issued"/><br />
<attribute name="institution" value="netcdf/attribute/@name=institution"/><br />
<attribute name="project" value="netcdf/attribute/@name=project"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="netcdf/attribute/@name=contributor_name"/><br />
<attribute name="contributor_role" value="netcdf/attribute/@name=contributor_role"/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_name" value="netcdf/attribute/@name=publisher_name"/><br />
<attribute name="publisher_url" value="netcdf/attribute/@name=publisher_url"/><br />
<attribute name="publisher_email" value="netcdf/attribute/@name=publisher_email"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="netcdf/attribute/@name=processing_level"/><br />
<attribute name="license" value="netcdf/attribute/@name=license"/><br />
<attribute name="cdm_data_type" value="netcdf/attribute/@name=cdm_data_type"/><br />
<variable name="netcdf/variable/@name" type="netcdf/variable/@type" shape="netcdf/variable/@shape"><br />
<attribute name="units" value="netcdf/variable/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable/attribute/@name=standard_name"/><br />
</variable><br />
<variable name="netcdf/variable2/@name" type="netcdf/variable2/@type" shape="netcdf/variable2/@shape"><br />
<attribute name="units" value="netcdf/variable2/attribute/@name=units"/><br />
<attribute name="long_name" value="netcdf/variable2/attribute/@name=long_name"/><br />
<attribute name="standard_name" value="netcdf/variable2/attribute/@name=standard_name"/><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
==Real-World Example==<br />
This NcML, taken from a very well documented CoastWatch file, includes real-world examples for all of the recommended attributes:<br />
<pre><br />
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"><br />
<!-- Identifier / Metadata Reference --><br />
<attribute name="id" value="LMHchlaS8day_20100129000000"/><br />
<attribute name="naming_authority" value="gov.noaa.pfel.coastwatch"/><br />
<attribute name="Metadata_Conventions" value="Unidata Dataset Discovery v1.0"/><br />
<attribute name="Metadata_Link" value="URL for full metadata record"/><br />
<!-- Text Search --><br />
<attribute name="title" value="Chlorophyll-a, Aqua MODIS, NPP, 0.05 degrees, Global, Science Quality"/><br />
<attribute name="summary"<br />
value="NOAA CoastWatch distributes chlorophyll-a concentration data from NASA&apos;s Aqua Spacecraft. <br />
Measurements are gathered by the Moderate Resolution Imaging Spectroradiometer (MODIS) carried aboard the spacecraft.<br />
This is Science Quality data."/><br />
<attribute name="keywords" value="EARTH SCIENCE &gt; Oceans &gt; Ocean Chemistry &gt; Chlorophyll"/><br />
<attribute name="keywords_vocabulary" value="GCMD Science Keywords"/><br />
<attribute name="standard_name_vocabulary" value="CF-1.0"/><br />
<attribute name="history" value="NASA GSFC (G. Feldman): 2010-02-22T22:48:46Z NOAA CoastWatch (West Coast Node) and NOAA SFSC ERD"/><br />
<attribute name="comment" value="Text comment"/><br />
<!-- Extent Search --><br />
<attribute name="geospatial_lat_min" value="-90.0 " type="double"/><br />
<attribute name="geospatial_lat_max" value="90.0 " type="double"/><br />
<attribute name="geospatial_lon_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_lon_max" value="360.0 " type="double"/><br />
<attribute name="geospatial_vertical_min" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_max" value="0.0 " type="double"/><br />
<attribute name="geospatial_vertical_positive" value="up"/><br />
<attribute name="time_coverage_end" value="2010-02-02T00:00:00Z"/><br />
<attribute name="time_coverage_start" value="2010-01-25T00:00:00Z"/><br />
<!-- Other Extent Information --><br />
<attribute name="geospatial_lat_units" value="degrees_north"/><br />
<attribute name="geospatial_lat_resolution" value="0.041676313961565174" type="double"/><br />
<attribute name="geospatial_lon_units" value="degrees_east"/><br />
<attribute name="geospatial_lon_resolution" value="0.04167148975575877" type="double"/><br />
<attribute name="geospatial_vertical_units" value="m"/><br />
<attribute name="geospatial_vertical_resolution" value="1.0" type="double"/><br />
<attribute name="time_coverage_duration" value="P1D"/><br />
<attribute name="time_coverage_resolution" value="PT1M"/><br />
<!-- Creator Search --><br />
<attribute name="acknowledgment" value="NOAA NESDIS COASTWATCH, NOAA SWFSC ERD"/><br />
<attribute name="creator_email" value="dave.foley@noaa.gov"/><br />
<attribute name="creator_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="creator_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<attribute name="date_created" value="2010-02-22Z"/><br />
<attribute name="date_modified" value="2010-03-22Z"/><br />
<attribute name="date_issued" value="2010-02-22Z"/><br />
<attribute name="institution" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="project" value="CoastWatch (http://coastwatch.noaa.gov/)"/><br />
<!-- Contributor Search --><br />
<attribute name="contributor_name" value="NASA GSFC (G. Feldman)"/><br />
<attribute name="contributor_role" value="Source of level 2 data."/><br />
<!-- Publisher Search --><br />
<attribute name="publisher_email" value="dave.foley@noaa.gov"/><br />
<attribute name="publisher_name" value="NOAA CoastWatch, West Coast Node"/><br />
<attribute name="publisher_url" value="http://coastwatch.pfel.noaa.gov"/><br />
<!-- Other Attributes --><br />
<attribute name="processing_level" value="3"/><br />
<attribute name="license"<br />
value="The data may be used and redistributed for free but is not intended for legal use, since it may contain inaccuracies. Neither the data Contributor, CoastWatch, NOAA, nor the United States Government, nor any of their employees or contractors, makes any warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, or assumes any legal liability for the accuracy, completeness, or usefulness, of this information."/><br />
<attribute name="cdm_data_type" value="Grid"/><br />
</netcdf><br />
</pre><br />
=NetCDF Climate and Forecast (CF) Metadata Conventions=<br />
The [http://cf-pcmdi.llnl.gov/ NetCDF Climate and Forecast (CF) Metadata Conventions] are designed to promote the interoperable processing and sharing of data from netCDF files. They are focused on data ''use'' while the NetCDF Attribute Conventions are focused on data ''discovery''. Many of the discovery attributes that are related to extents can be calculated from the CF information:<br/><br />
geospatial_lat_min, geospatial_lat_max, geospatial_lat_units, geospatial_lat_res<br/><br />
geospatial_lon_min, geospatial_lon_max, geospatial_lon_units, geospatial_lon_res<br/><br />
geospatial_vertical_min, geospatial_vertical_max, geospatial_vertical_units, geospatial_vertical_res, geospatial_vertical_pos<br/><br />
time_coverage_start, time_coverage_end, time_coverage_units, time_coverage_duration, time_coverage_res<br/><br />
<br />
'''Note: We recommend explicitly listing these attributes in the file even though they can be calculated from the CF information in order to facilitate direct access to this information by tools that do not understand the CF Conventions.'''<br />
=Open Geospatial Consortium Catalog Service for the Web (CSW)=<br />
The [http://www.opengeospatial.org/standards/cat OGC CSW Service] includes ten core queryable elements that must be supported in all instances. CSW Profiles map these queryables to elements in various standards. The ISO Mappings are described in Section 7.2.3.1,Table 6 of OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile ([http://portal.opengeospatial.org/files/?artifact_id=21460 OGC 07-045]). The core queryables mapping is included in the Table above. An additional "any text" queryable covers all text in a record. Two core queryables are not covered by the NetCDF Attribute Convention for Dataset Discovery: Format and CRS.<br />
<br />
=ISO Translation Notes=<br />
The translation between the Attribute Conventions for Data Discovery is subject to a number of assumptions or conventions described here.<br />
==People==<br />
The ACDD includes several types of people:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td></tr><br />
<tr><br />
<td>creator_name, creator_email, creator_url, institution</td><br />
<td>citation/citedResponsibleParty role=originator, point of contact, and metadata contact</td><br />
<tr><br />
<tr><br />
<td>contributor_name, contributor_role</td><br />
<td>citation/citedResponsibleParty role=originator (may need adjustment)</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword, aggregation information (initiative type = project)</td><br />
</tr><br />
<br />
</table><br />
==Keywords==<br />
The ACDD includes several attributes that make sense as keywords in ISO:<br />
<table border="1" cellpadding="3"><br />
<tr><br />
<td>'''ACDD Attributes'''</td><br />
<td>'''ISO Locations'''</td><br />
</tr><br />
<tr><br />
<td>keywords</td><br />
<td>theme keywords with thesaurus given by the keywords_vocabulary attribute</td><br />
</tr><br />
<tr><br />
<td>project</td><br />
<td>Project keyword with unknown thesaurus and aggregation information (initiative type = project)</td><br />
</tr><br />
<tr><br />
<td>publisher_name</td><br />
<td>Data Center keyword with unknown thesaurus</td><br />
</tr><br />
<tr><br />
<td>standard_names for parameters</td><br />
<td>theme keywords with thesaurus = standard_name_vocabulary</td><br />
</tr><br />
<tr><br />
<td>publisher_name, publisher_email, publisher_url</td><br />
<td>distributor and Data Center keyword</td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
=Translation Revisions=<br />
Several changes were introduced into [http://www.ngdc.noaa.gov/metadata/published/xsl/UnidataDD2MI.xsl Version 2.0.2] of the stylesheet for transforming NcML to ISO in order to improve the rubric score for the resulting ISO metadata. The changes included:<br />
#Including netcdf/@location in transform as distribution onlineResource<br />
#Added tagname to writeResponsibleParty so that responsibleParties with <br />
different UML roles could be supported (i.e. contact vs. distributor)<br />
#Added urlName and urlDescription to writeResponsibleParty to add <br />
content to the onlineResource<br />
#Moved publisher from citation to distributor and included publisher_name as a dataCenter keyword.<br />
#Added project as a keyword with type=project<br />
#Added distributionInfo section to ISO if publisher or location exist.<br />
<br />
=Determining an Order of Precedence=<br />
There can be conflicting information available from different sources within the THREDDS and CDM data models.<br />
The diagram below seeks to determine an order of precedence for what is recorded in the ncISO metadata when those attributes conflict.<br />
[[Image:Metadataprecedence.png]]<br />
<br />
A key part of this discussion is the ability to see identify potentially conflicting metdata between the differenc sources within THREDDS and NetCDF. Below we propose using groups to identify in the NCML what sources contain the relevant metadata that will be used in the ISO translation. <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<netcdf xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2 ../XSD/ncml-2.2.xsd"<br />
xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"<br />
location="http://localhost:8080/thredds/dodsC/test/crm_v1.nc"><br />
<br />
<!-- Metadata from the netCDF or NCML file global attributes --> <br />
<attribute name="Conventions" value="CF-1.4" /><br />
<attribute name="title" value="crm_v1.grd" /><br />
<attribute name="history" value="xyz2grd -R-80/-64/40/48 -I3c -Gcrm_v1.grd" /><br />
<attribute name="GMT_version" value="4.5.1 [64-bit]" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="geospatial_lon_units" value="degrees_east" /><br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_min" type="float" value="-80.0" /><br />
<attribute name="geospatial_lon_max" type="float" value="-64.0" /> <br />
<attribute name="geospatial_lat_max" type="float" value="48.0" /><br />
<attribute name="geospatial_lat_min" type="float" value="40.0" /><br />
<attribute name="geospatial_lon_resolution" type="double" value="8.33E-4" /><br />
<attribute name="geospatial_lat_resolution" type="double" value="8.33E-4" /><br />
<br />
<!-- Metadata calculated from the netCDF file axes based on CF conventions --><br />
<group name="CFMetadata"><br />
<attribute name="geospatial_lon_min" value="-80.0" type="float" /><br />
<attribute name="geospatial_lat_min" value="40.0" type="float" /><br />
<attribute name="geospatial_lon_max" value="-64.0" type="float" /><br />
<attribute name="geospatial_lat_max" value="48.0" type="float" /><br />
<attribute name="geospatial_lon_units" value="degrees_east" /> <br />
<attribute name="geospatial_lat_units" value="degrees_north" /><br />
<attribute name="geospatial_lon_resolution" value="8.332899328159992E-4" /><br />
<attribute name="geospatial_lat_resolution" value="8.332465368190813E-4" /><br />
</group><br />
<br />
<!-- Metadata from the THREDDS catalog dataset --><br />
<group name="THREDDSMetadata"><br />
<attribute name="id" value="crm_v1" /><br />
<attribute name="creator_name" value="David Neufeld"/><br />
<attribute name="creator_email" value="David.Neufeld@noaa.gov"/> <br />
<attribute name="data_distribution" value="http://localhost:8080/thredds/dodsC/test/crm_v1.nc" /><br />
<attribute name="wms_service" value="http://localhost:8080//thredds/wms/crm/crm_vol9.nc" /><br />
<attribute name="wcs_service" value="http://localhost:8080//thredds/wcs/crm/crm_vol9.nc" /><br />
</group> <br />
<br />
<!-- Metadata from the ncISO service --><br />
<group name="NCISOMetadata"><br />
<attribute name="metadata_creation" value="2011-04-19" /><br />
</group><br />
<br />
<dimension name="x" length="19201" /><br />
<dimension name="y" length="9601" /><br />
<br />
<variable name="z" shape="y x" type="float"><br />
<attribute name="long_name" value="z" /><br />
<br />
<attribute name="_FillValue" type="float" value="NaN" /><br />
<attribute name="actual_range" type="double" value="-2754.39990234375 1903.0" /><br />
<attribute name="units" value="meters" /><br />
<attribute name="positive" value="up" /><br />
</variable><br />
<variable name="x" shape="x" type="double"><br />
<attribute name="long_name" value="x" /><br />
<attribute name="actual_range" type="double" value="-80.0 -64.0" /><br />
<attribute name="units" value="degrees_east" /><br />
<br />
<attribute name="_CoordinateAxisType" value="Lon" /><br />
</variable><br />
<variable name="y" shape="y" type="double"><br />
<attribute name="long_name" value="y" /><br />
<attribute name="actual_range" type="double" value="40.0 48.0" /><br />
<attribute name="units" value="degrees_north" /><br />
<attribute name="_CoordinateAxisType" value="Lat" /><br />
</variable><br />
</netcdf><br />
</pre><br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Category:Attribute_Conventions_Dataset_Discovery&diff=48595Category:Attribute Conventions Dataset Discovery2015-01-09T00:56:38Z<p>Graybeal: /* History */ added link to change summary</p>
<hr />
<div><br />
=Background=<br />
This page summarizes information related to the Attribute Convention for Dataset Discovery. (The page is a 'category' on the ESIP wiki, and provides a landing page for information on the convention and its versions.)<br />
<br />
The Attribute Convention for Dataset Discovery identify and define a list of NetCDF global attributes recommended for describing a NetCDF dataset to discovery systems such as Digital Libraries. Software tools will use these attributes for extracting metadata from datasets, and exporting to Dublin Core, DIF, ADN, FGDC, ISO 19115 etc. metadata formats.<br />
<br />
=Current Release=<br />
The currently released ACDD document is always the one recommended for public use. <br />
<br />
Since mid-2013, the current release is always referenced by [[Attribute Convention for Data Discovery|this link]]:<br />
http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery<br />
<br />
=History =<br />
<br />
The currently released version of the ACDD is always found at [[Attribute Convention for Data Discovery]]. <br />
<br />
The latest working document, including new concepts and terms under consideration, can be found at [[Attribute Convention for Data Discovery Working]]. <br />
<br />
NOTE: Occasionally the acronym UDDC (Unidata Dataset Discovery Conventions) has been used in the community to refer to this same convention. ACDD is now the preferred acronym, and Attribute Convention for Data Discovery the preferred name.<br />
<br />
The following table describes the history of this document, including some interim versions which were not released. (In particular, the 1.2.x versions of ACDD were all unreleased working versions.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! style="width:130px" | Version/Link !! Released? || Description !! Date Updated<br />
|-<br />
| [http://www.unidata.ucar.edu/software/thredds/v4.3/netcdf-java/formats/DataDiscoveryAttConvention.html 1.0 Original] || Yes || Original version published by Ethan Davis on the Unidata website. <br>(Locally saved [[ArchivalCopyOfVersion1]].) || 2005-09-28<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-1|1.1 Previous Release]] || Yes || Attribute Convention for Data Discovery 1-1: This was the previous release of the ACDD, until updated on 1/1/2015 by version 1.3. <br>''History'': The Unidata vocabulary was migrated to the [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery NOAA Environmental Data Management wiki] on or around 2010-01-20. The discussion and developments on that page focused on mapping the ACDD elements to corresponding ISO elements. These mappings became the basis for software tools to translate from netCDF to ISO19115/19115-2/19119 (e.g. [https://geo-ide.noaa.gov/wiki/index.php?title=NcISO ncISO] and [http://trac.osgeo.org/geonetwork/wiki/ISO19119impl Geonetwork]. <br>''Status'': The Current Release on this site is a copy of the NOAA page, with minor modifications in the introductory text. || 2013-04-29 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2|1.2 ''early beta'' ]] || No || Attribute Convention for Data Discovery 1-2: A working draft of the 'next version' of ACDD, created 2013-04-26 and updated intermittently thereafter to follow the modifications in [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || 2014-02-07 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || No || Attribute Convention for Data Discovery 1-2 Working: This working page was maintained as a long modification section. The Discussion page of this document contained considerable history, distilled from emails. <br>''Also'': Implemented new hierarchy of pages. Now there are permanent target pages (e.g., [[Attribute Convention for Data Discovery]]) which redirect to the Current Release ([[Attribute Convention for Data Discovery 1-1]] and current working pages. || 2014-09-08<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-3|1.3 <font color="green">Current Release</font>]] || Yes || Attribute Convention for Data Discovery 1-3: This is the latest approved release of the ACDD.<br>''Change Summary'': A summary of changes and references can be found at http://commons.esipfed.org/acdd_1-3_references. || 2015-01-01<br />
|-<br />
|}<br />
<br />
== Future Directions ==<br />
<br />
At the moment, there is no working document per se. Instead, the [[Attribute Convention for Data Discovery Working]] link redirects to the [[Attribute Convention for Data Discovery Future Directions]], which describes anticipated work on an object oriented '2.0' version, and also references [[ACDD 1-3 Follow-on Discussions|the document used to capture issues about version 1.3]].<br />
<br />
=Objectives and Goals=<br />
The ACDD is intended<br />
#To allow efficient dataset discovery <br />
#To allow users to use data efficiently<br />
#To facilitate mapping between dataset metadata (notably netCDF) and ISO 19115.<br />
<br />
=Governance=<br />
The ACDD Steering Committee formalizes changes and additions to ACDD.<br />
<br />
The discussion for changes to ACDD is carried out via this wiki and the [http://lists.esipfed.org/mailman/roster/esip-documentation ESIP Documentation Cluster mailing list]. To sign up for edit privileges for this wiki you must first [http://commons.esipfed.org/user/register register at the ESIP Commons]. This registration also grants access to other community resources supported by ESIP. Both the mailing list and this wiki are open and anyone in the community. ACDD will evolve based on the discussions on this list and as documented on these wiki pages. Occasionally, the discussion may need to be moderated or a decision must be made. In these cases the steering committee will vote and adopt a solution as described below. <br />
<br />
==Steering Committee==<br />
ACDD will evolve based on the direction of the steering committee, which is comprised of the following members:<br />
<br />
*Anna Milan (Co-chair) NGDC<br />
*John Graybeal (Co-chair) Graybeal.SKI Consulting<br />
*Dave Blodgett USGS<br />
*Nan Galbraith WHOI<br />
*Ted Habermann The HDF Group<br />
*Steve Hankin PMEL<br />
*Marcos Hermida Unidata<br />
*Aleksandar Jelenak The HDF Group<br />
*Anna Milan NGDC<br />
*Dave Neufeld CIRES<br />
*Rich Signell USGS<br />
*Bob Simons NMFS<br />
*Derrick Snowden IOOS<br />
*Ed Armstrong JPL<br />
<br />
==Decision Making Process==<br />
<br />
Vote 70% majority of voting members; members may decline to vote on some issues<br />
<br />
If a vote is taken or a decision is reached, that decision should be broadcast to those who could not be present. Discussion of the decision takes place for some period of time (or till the next meeting?) If there is disagreement or ongoing discussion, the decision is not finalized. If there is no discussion or disagreement, the topic is final and will not be revisited later.<br />
<br />
<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=ACDD_1-3_Follow-on_Discussions&diff=48585ACDD 1-3 Follow-on Discussions2015-01-06T04:30:26Z<p>Graybeal: </p>
<hr />
<div>This page has been created to capture suggestions and concerns about the released ACDD 1-3 specification.<br />
<br />
As noted in [[Attribute Convention for Data Discovery Future Directions]], given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. <br />
<br />
Therefore, while this document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path. <br />
<br />
== Suggestions and Concerns ==<br />
<br />
It is suggested that each topic follow the following template. You might want to append '(minor fix)' to the topic name if you think this is worth an update to 1.3, as opposed to consideration in version 2. <br />
<br />
----<br />
=== Template Topic ===<br />
<br />
Text description of the issues or suggested changes.<br />
<br />
[[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 13:01, 5 January 2015 (MST) (your signature & date, inserted via 4 ~ characters)<br />
<br />
==== Discussion ====<br />
<br />
(Comments from others go here.)<br />
<br />
----</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Category:Attribute_Conventions_Dataset_Discovery&diff=48584Category:Attribute Conventions Dataset Discovery2015-01-06T04:19:02Z<p>Graybeal: /* History */ updated to reference future work</p>
<hr />
<div><br />
=Background=<br />
This page summarizes information related to the Attribute Convention for Dataset Discovery. (The page is a 'category' on the ESIP wiki, and provides a landing page for information on the convention and its versions.)<br />
<br />
The Attribute Convention for Dataset Discovery identify and define a list of NetCDF global attributes recommended for describing a NetCDF dataset to discovery systems such as Digital Libraries. Software tools will use these attributes for extracting metadata from datasets, and exporting to Dublin Core, DIF, ADN, FGDC, ISO 19115 etc. metadata formats.<br />
<br />
=Current Release=<br />
The currently released ACDD document is always the one recommended for public use. <br />
<br />
Since mid-2013, the current release is always referenced by [[Attribute Convention for Data Discovery|this link]]:<br />
http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery<br />
<br />
=History =<br />
<br />
The currently released version of the ACDD is always found at [[Attribute Convention for Data Discovery]]. <br />
<br />
The latest working document, including new concepts and terms under consideration, can be found at [[Attribute Convention for Data Discovery Working]]. <br />
<br />
NOTE: Occasionally the acronym UDDC (Unidata Dataset Discovery Conventions) has been used in the community to refer to this same convention. ACDD is now the preferred acronym, and Attribute Convention for Data Discovery the preferred name.<br />
<br />
The following table describes the history of this document, including some interim versions which were not released. (In particular, the 1.2.x versions of ACDD were all unreleased working versions.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! style="width:130px" | Version/Link !! Released? || Description !! Date Updated<br />
|-<br />
| [http://www.unidata.ucar.edu/software/thredds/v4.3/netcdf-java/formats/DataDiscoveryAttConvention.html 1.0 Original] || Yes || Original version published by Ethan Davis on the Unidata website. <br>(Locally saved [[ArchivalCopyOfVersion1]].) || 2005-09-28<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-1|1.1 Previous Release]] || Yes || Attribute Convention for Data Discovery 1-1: This was the previous release of the ACDD, until updated on 1/1/2015 by version 1.3. <br>''History'': The Unidata vocabulary was migrated to the [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery NOAA Environmental Data Management wiki] on or around 2010-01-20. The discussion and developments on that page focused on mapping the ACDD elements to corresponding ISO elements. These mappings became the basis for software tools to translate from netCDF to ISO19115/19115-2/19119 (e.g. [https://geo-ide.noaa.gov/wiki/index.php?title=NcISO ncISO] and [http://trac.osgeo.org/geonetwork/wiki/ISO19119impl Geonetwork]. <br>''Status'': The Current Release on this site is a copy of the NOAA page, with minor modifications in the introductory text. || 2013-04-29 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2|1.2 ''early beta'' ]] || No || Attribute Convention for Data Discovery 1-2: A working draft of the 'next version' of ACDD, created 2013-04-26 and updated intermittently thereafter to follow the modifications in [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || 2014-02-07 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || No || Attribute Convention for Data Discovery 1-2 Working: This working page was maintained as a long modification section. The Discussion page of this document contained considerable history, distilled from emails. <br>''Also'': Implemented new hierarchy of pages. Now there are permanent target pages (e.g., [[Attribute Convention for Data Discovery]]) which redirect to the Current Release ([[Attribute Convention for Data Discovery 1-1]] and current working pages. || 2014-09-08<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-3|1.3 <font color="green">Current Release</font>]] || Yes || Attribute Convention for Data Discovery 1-3: This is the latest approved release of the ACDD. || 2015-01-01<br />
|-<br />
|}<br />
<br />
== Future Directions ==<br />
<br />
At the moment, there is no working document per se. Instead, the [[Attribute Convention for Data Discovery Working]] link redirects to the [[Attribute Convention for Data Discovery Future Directions]], which describes anticipated work on an object oriented '2.0' version, and also references [[ACDD 1-3 Follow-on Discussions|the document used to capture issues about version 1.3]].<br />
<br />
=Objectives and Goals=<br />
The ACDD is intended<br />
#To allow efficient dataset discovery <br />
#To allow users to use data efficiently<br />
#To facilitate mapping between dataset metadata (notably netCDF) and ISO 19115.<br />
<br />
=Governance=<br />
The ACDD Steering Committee formalizes changes and additions to ACDD.<br />
<br />
The discussion for changes to ACDD is carried out via this wiki and the [http://lists.esipfed.org/mailman/roster/esip-documentation ESIP Documentation Cluster mailing list]. To sign up for edit privileges for this wiki you must first [http://commons.esipfed.org/user/register register at the ESIP Commons]. This registration also grants access to other community resources supported by ESIP. Both the mailing list and this wiki are open and anyone in the community. ACDD will evolve based on the discussions on this list and as documented on these wiki pages. Occasionally, the discussion may need to be moderated or a decision must be made. In these cases the steering committee will vote and adopt a solution as described below. <br />
<br />
==Steering Committee==<br />
ACDD will evolve based on the direction of the steering committee, which is comprised of the following members:<br />
<br />
*Anna Milan (Co-chair) NGDC<br />
*John Graybeal (Co-chair) Graybeal.SKI Consulting<br />
*Dave Blodgett USGS<br />
*Nan Galbraith WHOI<br />
*Ted Habermann The HDF Group<br />
*Steve Hankin PMEL<br />
*Marcos Hermida Unidata<br />
*Aleksandar Jelenak The HDF Group<br />
*Anna Milan NGDC<br />
*Dave Neufeld CIRES<br />
*Rich Signell USGS<br />
*Bob Simons NMFS<br />
*Derrick Snowden IOOS<br />
*Ed Armstrong JPL<br />
<br />
==Decision Making Process==<br />
<br />
Vote 70% majority of voting members; members may decline to vote on some issues<br />
<br />
If a vote is taken or a decision is reached, that decision should be broadcast to those who could not be present. Discussion of the decision takes place for some period of time (or till the next meeting?) If there is disagreement or ongoing discussion, the decision is not finalized. If there is no discussion or disagreement, the topic is final and will not be revisited later.<br />
<br />
<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Category:Attribute_Conventions_Dataset_Discovery&diff=48583Category:Attribute Conventions Dataset Discovery2015-01-06T04:08:18Z<p>Graybeal: /* Current Release */ changed persistent link to remove the ' (ACDD)' part</p>
<hr />
<div><br />
=Background=<br />
This page summarizes information related to the Attribute Convention for Dataset Discovery. (The page is a 'category' on the ESIP wiki, and provides a landing page for information on the convention and its versions.)<br />
<br />
The Attribute Convention for Dataset Discovery identify and define a list of NetCDF global attributes recommended for describing a NetCDF dataset to discovery systems such as Digital Libraries. Software tools will use these attributes for extracting metadata from datasets, and exporting to Dublin Core, DIF, ADN, FGDC, ISO 19115 etc. metadata formats.<br />
<br />
=Current Release=<br />
The currently released ACDD document is always the one recommended for public use. <br />
<br />
Since mid-2013, the current release is always referenced by [[Attribute Convention for Data Discovery|this link]]:<br />
http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery<br />
<br />
=History =<br />
<br />
The currently released version of the ACDD is always found at [[Attribute Convention for Data Discovery]]. <br />
<br />
The latest working document, including new concepts and terms under consideration, can be found at [[Attribute Convention for Data Discovery Working]].<br />
<br />
NOTE: Occasionally the acronym UDDC (Unidata Dataset Discovery Conventions) has been used in the community to refer to this same convention. ACDD is now the preferred acronym, and Attribute Convention for Data Discovery the preferred name.<br />
<br />
The following table describes the history of this document, including some interim versions which were not released. (In particular, the 1.2.x versions of ACDD were all unreleased working versions.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! style="width:130px" | Version/Link !! Released? || Description !! Date Updated<br />
|-<br />
| [http://www.unidata.ucar.edu/software/thredds/v4.3/netcdf-java/formats/DataDiscoveryAttConvention.html 1.0 Original] || Yes || Original version published by Ethan Davis on the Unidata website. <br>(Locally saved [[ArchivalCopyOfVersion1]].) || 2005-09-28<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-1|1.1 Previous Release]] || Yes || Attribute Convention for Data Discovery 1-1: This was the previous release of the ACDD, until updated on 1/1/2015 by version 1.3. <br>''History'': The Unidata vocabulary was migrated to the [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery NOAA Environmental Data Management wiki] on or around 2010-01-20. The discussion and developments on that page focused on mapping the ACDD elements to corresponding ISO elements. These mappings became the basis for software tools to translate from netCDF to ISO19115/19115-2/19119 (e.g. [https://geo-ide.noaa.gov/wiki/index.php?title=NcISO ncISO] and [http://trac.osgeo.org/geonetwork/wiki/ISO19119impl Geonetwork]. <br>''Status'': The Current Release on this site is a copy of the NOAA page, with minor modifications in the introductory text. || 2013-04-29 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2|1.2 ''early beta'' ]] || No || Attribute Convention for Data Discovery 1-2: A working draft of the 'next version' of ACDD, created 2013-04-26 and updated intermittently thereafter to follow the modifications in [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || 2014-02-07 <br />
|-<br />
| [[Attribute Convention for Data Discovery 1-2 Working|1.2.3 ''working'']] || No || Attribute Convention for Data Discovery 1-2 Working: This working page was maintained as a long modification section. The Discussion page of this document contained considerable history, distilled from emails. <br>''Also'': Implemented new hierarchy of pages. Now there are permanent target pages (e.g., [[Attribute Convention for Data Discovery]]) which redirect to the Current Release ([[Attribute Convention for Data Discovery 1-1]] and current working pages. || 2014-09-08<br />
|-<br />
| [[Attribute Convention for Data Discovery 1-3|1.3 <font color="green">Current Release</font>]] || Yes || Attribute Convention for Data Discovery 1-3: This is the latest approved release of the ACDD. || 2015-01-01<br />
|-<br />
|}<br />
<br />
=Objectives and Goals=<br />
The ACDD is intended<br />
#To allow efficient dataset discovery <br />
#To allow users to use data efficiently<br />
#To facilitate mapping between dataset metadata (notably netCDF) and ISO 19115.<br />
<br />
=Governance=<br />
The ACDD Steering Committee formalizes changes and additions to ACDD.<br />
<br />
The discussion for changes to ACDD is carried out via this wiki and the [http://lists.esipfed.org/mailman/roster/esip-documentation ESIP Documentation Cluster mailing list]. To sign up for edit privileges for this wiki you must first [http://commons.esipfed.org/user/register register at the ESIP Commons]. This registration also grants access to other community resources supported by ESIP. Both the mailing list and this wiki are open and anyone in the community. ACDD will evolve based on the discussions on this list and as documented on these wiki pages. Occasionally, the discussion may need to be moderated or a decision must be made. In these cases the steering committee will vote and adopt a solution as described below. <br />
<br />
==Steering Committee==<br />
ACDD will evolve based on the direction of the steering committee, which is comprised of the following members:<br />
<br />
*Anna Milan (Co-chair) NGDC<br />
*John Graybeal (Co-chair) Graybeal.SKI Consulting<br />
*Dave Blodgett USGS<br />
*Nan Galbraith WHOI<br />
*Ted Habermann The HDF Group<br />
*Steve Hankin PMEL<br />
*Marcos Hermida Unidata<br />
*Aleksandar Jelenak The HDF Group<br />
*Anna Milan NGDC<br />
*Dave Neufeld CIRES<br />
*Rich Signell USGS<br />
*Bob Simons NMFS<br />
*Derrick Snowden IOOS<br />
*Ed Armstrong JPL<br />
<br />
==Decision Making Process==<br />
<br />
Vote 70% majority of voting members; members may decline to vote on some issues<br />
<br />
If a vote is taken or a decision is reached, that decision should be broadcast to those who could not be present. Discussion of the decision takes place for some period of time (or till the next meeting?) If there is disagreement or ongoing discussion, the decision is not finalized. If there is no discussion or disagreement, the topic is final and will not be revisited later.<br />
<br />
<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-3&diff=48582Attribute Convention for Data Discovery 1-32015-01-05T20:10:25Z<p>Graybeal: /* Version and Status */ changed the master URL link to remove the ' (ACDD)', since that's a hard URL to use</p>
<hr />
<div>[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]<br />
= Context =<br />
<br />
== Document ==<br />
<br />
This is the Attribute Convention for Data Discovery (ACDD).<br />
<br />
== Version and Status ==<br />
<br />
This version is designated as Version 1.3; it is the latest released version.<br />
<br />
The page [[Attribute Convention for Data Discovery]] always points to the current released version of the Convention. The version number at the top of the resulting page will show the current version.<br />
<br />
See the [http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery ACDD category page] for information on the history and maintenance of this convention.<br />
<br />
=== Development ===<br />
<br />
For development versions of the ACDD, please see the page [[Attribute Convention for Data Discovery Working]].<br />
<br />
Questions about this specification may be addressed to the [http://www.lists.esipfed.org/mailman/listinfo/esip-documentation ESIP Documentation Cluster mailing list].<br />
<br />
= Overview =<br />
This document describes attributes recommended for describing a NetCDF dataset to discovery systems such as Digital Libraries. THREDDS and other tools can use these attributes to extract metadata from datasets, and exporting to Dublin Core, DIF, ADN, FGDC, ISO 19115 and other metadata formats. This will help systems and users locate and use data efficiently.<br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cfconventions.org/ (CF)] provides more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines three, title, history, and Conventions. CF specifies more: institution, source, references, comment, and featureType. ACDD 1.3 adopts all CF 1.6 global attributes. In a change from ACDD 1.2, we adopt the NUG recommendation to supply all conventions in the single Conventions attribute.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so similar terms exist in many metadata standards. This [[Attribute_Convention_for_Data_Discovery_(ACDD)_Mappings]] page includes a crosswalk to THREDDS, OGC CSW, ISO 19115-2 and Rubric Categories.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
Documents using other metadata specifications (e.g., ISO 19115) can provide additional information about the dataset. If additional metadata exists, you can make users aware of it by adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata.<br />
<br />
== Definitions: Data and Metadata ==<br />
<br />
In several ACDD attribute names or definitions, the terms 'data' and 'metadata' are used. In the context of NetCDF files, these refer specifically to the values within the file, and the attributes of the file, respectively.<br />
<br />
== Maintenance of Metadata ==<br />
<br />
ACDD attributes characterize the data they are associated with. Any processing that alters these characteristics is responsible for updating the relevant attributes.<br />
<br />
NetCDF file creators and software developers should ensure that the attributes of output data accurately represent that data, and specifically should not "pass through" any source attribute in unaltered form, unless it is known to remain accurate. NetCDF data users should verify critical attribute values, to be confident the source metadata is appropriate.<br />
<br />
The ACDD geospatiotemporal attributes present a special case, as this information is already fully defined by the CF coordinate variables. These attributes are recommended, despite being redundant, because they greatly simplify data discovery and access.<br />
<br />
The risk of inconsistency between these attributes and the actual data is highest after aggregation or subsetting; checking them against the data can serve as a useful test of the metadata's validity.<br />
<br />
== Attribute Content Guidance ==<br />
<br />
=== Date and Time: ISO 8601 Recommended Formats ===<br />
<br />
The ACDD specifies [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601:2004] date and time formats for its temporal attributes. ACDD strongly encourages the use of the 'extended' format date-time, in the form <br />
<tt>YYYY-MM-DDThh:mm:ss<zone></tt><br />
(although ss, mm, and hh can be omitted, and <zone> can be Z, ±hh:mm, or ±hh). Per the standard, the shortened or basic format, which omits the - and : separators, "should be avoided in plain text."<br />
<br />
For duration attributes, again the extended form is strongly encouraged for readability:<br />
<tt>P[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]</tt><br />
<br />
If for some reason the strongly encouraged formats can not be used, other ISO 8601-compatible formats are acceptable, but may not be handled by some processing software.<br />
<br />
=== Comma-Separated Lists ===<br />
<br />
Several attributes explicitly allow the entry of multiple entities as comma-separated values. Any entities within such lists which contain a comma must be enclosed in straight double quotation marks ("), which will not be considered part of the entity.<br />
<br />
Spaces (ASCII character 32) between the entities are recommended for readability, but not required. Example: 'John Doe, Jane Lee, "L J Smith, Jr." '<br />
<br />
The same protocol may be used within free-text attributes, but is only recommended in cases where the attribute is being populated with structured data (rather than unconstrained text).<br />
<br />
=== Free Text Formatting: Structured Text Considerations ===<br />
<br />
In some attributes, it may be desirable to use structured text to support computer parsing of human-readable content. Because netCDF files are often translated between binary and text-based encodings like ncML (e.g., by the netCDF command line tools ''nco''), such structures should tolerate changes in white space, including end-of-line characters, that may occur during translation.<br />
<br />
= Global Attributes = <br />
== Highly Recommended ==<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="title">title</td><br />
<td valign="top">A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names. This attribute is also recommended by the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NetCDF Users Guide] and the [http://cfconventions.org/ CF conventions]. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="summary">summary</td><br />
<td valign="top">A paragraph describing the dataset, analogous to an abstract for a paper.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="keywords">keywords</td><br />
<td valign="top">A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary ([http://gcmd.gsfc.nasa.gov/learn/keywords.html GCMD] is often used), or URIs for terms from a controlled vocabulary (see also "keywords_vocabulary" attribute).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="Conventions">Conventions</td><br />
<td valign="top">A comma-separated list of the conventions that are followed by the dataset. For files that follow this version of ACDD, include the string 'ACDD-1.3'. (This attribute is described in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Conventions NetCDF Users Guide].)</td><br />
</tr><br />
</table><br />
<br />
==Recommended== <br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="id">id</td><br />
<td valign="top">An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include white space characters. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="naming_authority">naming_authority</td><br />
<td valign="top"> The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute. We recommend using reverse-DNS naming for the naming authority; URIs are also acceptable. Example: 'edu.ucar.unidata'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="history">history</td><br />
<td valign="top">Provides an audit trail for modifications to the original data. This attribute is also in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NetCDF Users Guide]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append a reference to an ISO Lineage entity; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="source">source</td><br />
<td valign="top">The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is defined in the CF Conventions. Examples: 'temperature from CTD #1234'; 'world model v.0.1'. <br />
</tr><br />
<tr><br />
<td valign="top" id="processing_level">processing_level</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="comment">comment</td><br />
<td valign="top"> Miscellaneous information about the data, not captured elsewhere. This attribute is defined in the [http://cfconventions.org/ CF Conventions].</td><br />
</tr><br />
<tr><br />
<td valign="top" id="acknowledgement">acknowledgement</td><br />
<td valign="top">A place to acknowledge various types of support for the project that produced this data. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="license">license</td><br />
<td valign="top">Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="standard_name_vocabulary">standard_name_vocabulary</td><br />
<td valign="top"> The name and version of the controlled vocabulary from which variable standard names are taken. (Values for any standard_name attribute must come from the CF Standard Names vocabulary for the data file or product to comply with CF.) Example: 'CF Standard Name Table v27'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_created">date_created</td><br />
<td valign="top">The date on which this version of the data was created. (Modification of values implies a new version, hence this would be assigned the date of the most recent values modification.) Metadata changes are not considered when assigning the date_created. The ISO 8601:2004 extended date format is recommended, as described in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_name">creator_name</td><br />
<td valign="top">The name of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_email">creator_email</td><br />
<td valign="top">The email address of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_url">creator_url</td><br />
<td valign="top">The URL of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="institution">institution</td><br />
<td valign="top">The name of the institution principally responsible for originating this data. This attribute is recommended by the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="project">project</td><br />
<td valign="top">The name of the project(s) principally responsible for originating this data. Multiple projects can be separated by commas, as described under Attribute Content Guidelines. Examples: 'PATMOS-X', 'Extended Continental Shelf Project'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_name">publisher_name</td><br />
<td valign="top">The name of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_email">publisher_email</td><br />
<td valign="top">The email address of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_url">publisher_url</td><br />
<td valign="top">The URL of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds">geospatial_bounds</td><br />
<td>Describes the data's 2D or 3D geospatial extent in OGC's Well-Known Text (WKT) Geometry format (reference the OGC Simple Feature Access (SFA) specification). The meaning and order of values for each point's coordinates depends on the coordinate reference system (CRS). The ACDD default is 2D geometry in the EPSG:4326 coordinate reference system. The default may be overridden with geospatial_bounds_crs and geospatial_bounds_vertical_crs (see those attributes). EPSG:4326 coordinate values are latitude (decimal degrees_north) and longitude (decimal degrees_east), in that order. Longitude values in the default case are limited to the [-180, 180) range. Example: 'POLYGON ((40.26 -111.29, 41.26 -111.29, 41.26 -110.29, 40.26 -110.29, 40.26 -111.29))'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds_crs">geospatial_bounds_crs</td><br />
<td>The coordinate reference system (CRS) of the point coordinates in the geospatial_bounds attribute. This CRS may be 2-dimensional or 3-dimensional, but together with geospatial_bounds_vertical_crs, if that attribute is supplied, must match the dimensionality, order, and meaning of point coordinate values in the geospatial_bounds attribute. If geospatial_bounds_vertical_crs is also present then this attribute must only specify a 2D CRS. EPSG CRSs are strongly recommended. If this attribute is not specified, the CRS is assumed to be EPSG:4326. Examples: 'EPSG:4979' (the 3D WGS84 CRS), 'EPSG:4047'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds_vertical_crs">geospatial_bounds_vertical_crs</td><br />
<td>The vertical coordinate reference system (CRS) for the Z axis of the point coordinates in the geospatial_bounds attribute. This attribute cannot be used if the CRS in geospatial_bounds_crs is 3-dimensional; to use this attribute, geospatial_bounds_crs must exist and specify a 2D CRS. EPSG CRSs are strongly recommended. There is no default for this attribute when not specified. Examples: 'EPSG:5829' (instantaneous height above sea level), "EPSG:5831" (instantaneous depth below sea level), or 'EPSG:5703' (NAVD88 height).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_min">geospatial_lat_min</td><br />
<td valign="top">Describes a simple lower latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_max">geospatial_lat_max</td><br />
<td valign="top">Describes a simple upper latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_min">geospatial_lon_min</td><br />
<td valign="top">Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_min specifies the westernmost longitude covered by the dataset. See also geospatial_lon_max.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_max">geospatial_lon_max</td><br />
<td valign="top">Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min; for example, geospatial_lon_min=170 and geospatial_lon_max=-175 incorporates 15 degrees of longitude (ranges 170 to 180 and -180 to -175).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_min">geospatial_vertical_min</td><br />
<td valign="top">Describes the numerically smaller vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_max">geospatial_vertical_max</td><br />
<td valign="top">Describes the numerically larger vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_positive">geospatial_vertical_positive</td><br />
<td valign="top">One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum. Note that if geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the data's vertical location furthest from the earth's center, and the geospatial_vertical_max attribute specifies the location closest to the earth's center.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_start">time_coverage_start</td><br />
<td valign="top">Describes the time of the first data point in the data set. Use the ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_end">time_coverage_end</td><br />
<td valign="top">Describes the time of the last data point in the data set. Use ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_duration">time_coverage_duration</td><br />
<td valign="top">Describes the duration of the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_resolution">time_coverage_resolution</td><br />
<td valign="top">Describes the targeted time period between each value in the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
</table><br />
<br />
==Suggested==<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_type">creator_type</td><br />
<td valign="top">Specifies type of creator with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the creator is assumed to be a person.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_institution">creator_institution</td><br />
<td valign="top">The institution of the creator; should uniquely identify the creator's institution. This attribute's value should be specified even if it matches the value of publisher_institution, or if creator_type is institution.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_type">publisher_type</td><br />
<td valign="top">Specifies type of publisher with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the publisher is assumed to be a person.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_institution">publisher_institution</td><br />
<td valign="top">The institution that presented the data file or equivalent product to users; should uniquely identify the institution. If publisher_type is institution, this should have the same value as publisher_name.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="program">program</td><br />
<td valign="top">The overarching program(s) of which the dataset is a part. A program consists of a set (or portfolio) of related and possibly interdependent projects that meet an overarching objective. Examples: 'GHRSST', 'NOAA CDR', 'NASA EOS', 'JPSS', 'GOES-R'.<br />
</td><br />
</tr><br />
<tr><br />
<td valign="top" id="contributor_name">contributor_name</td><br />
<td valign="top">The name of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="contributor_role">contributor_role</td><br />
<td valign="top">The role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters). Multiple roles should be presented in the same order and number as the names in contributor_names.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_units">geospatial_lat_units</td><br />
<td valign="top">Units for the latitude axis described in "geospatial_lat_min" and "geospatial_lat_max" attributes. These are presumed to be "degree_north"; other options from udunits may be specified instead.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_resolution">geospatial_lat_resolution</td><br />
<td valign="top">Information about the targeted spacing of points in latitude. Recommend describing resolution as a number value followed by the units. Examples: '100 meters', '0.1 degree'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_units">geospatial_lon_units</td><br />
<td valign="top">Units for the longitude axis described in "geospatial_lon_min" and "geospatial_lon_max" attributes. These are presumed to be "degree_east"; other options from udunits may be specified instead.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_resolution">geospatial_lon_resolution</td><br />
<td valign="top">Information about the targeted spacing of points in longitude. Recommend describing resolution as a number value followed by units. Examples: '100 meters', '0.1 degree'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_units">geospatial_vertical_units</td><br />
<td valign="top">Units for the vertical axis described in "geospatial_vertical_min" and "geospatial_vertical_max" attributes. The default is EPSG:4979 (height above the ellipsoid, in meters); other vertical coordinate reference systems may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar. Examples: 'EPSG:5829' (instantaneous height above sea level), 'EPSG:5831' (instantaneous depth below sea level).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_resolution">geospatial_vertical_resolution</td><br />
<td valign="top">Information about the targeted vertical spacing of points. Example: '25 meters'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_modified">date_modified</td><br />
<td valign="top">The date on which the data was last modified. Note that this applies just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_issued">date_issued</td><br />
<td valign="top">The date on which this data (including all modifications) was formally issued (i.e., made available to a wider audience). Note that these apply just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_metadata_modified">date_metadata_modified</td><br />
<td valign="top">The date on which the metadata was last modified. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="product_version">product_version</td><br />
<td valign="top">Version identifier of the data file or product as assigned by the data creator. For example, a new algorithm or methodology could result in a new product_version.</td><br />
<tr><br />
<td valign="top" id="keywords_vocabulary">keywords_vocabulary</td><br />
<td valign="top">If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key. Example: 'GCMD:GCMD Keywords, CF:NetCDF COARDS Climate and Forecast Standard Names'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="platform">platform</td><br />
<td valign="top">Name of the platform(s) that supported the sensor data used to create this data set or product. Platforms can be of any type, including satellite, ship, station, aircraft or other. Indicate controlled vocabulary used in platform_vocabulary.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="platform_vocabulary">platform_vocabulary</td><br />
<td valign="top">Controlled vocabulary for the names used in the "platform" attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="instrument">instrument</td><br />
<td valign="top">Name of the contributing instrument(s) or sensor(s) used to create this data set or product. Indicate controlled vocabulary used in instrument_vocabulary.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="instrument_vocabulary">instrument_vocabulary</td><br />
<td valign="top">Controlled vocabulary for the names used in the "instrument" attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="cdm_data_type">cdm_data_type</td><br />
<td>The data type, as derived from Unidata's Common Data Model Scientific Data types and understood by THREDDS. (This is a THREDDS "dataType", and is different from the CF NetCDF attribute 'featureType', which indicates a Discrete Sampling Geometry file in CF.)</td><br />
</tr><br />
<tr><br />
<td valign="top" id="metadata_link">metadata_link</td><br />
<td valign="top">A URL that gives the location of more complete metadata. A persistent URL is recommended for this attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="references">references</td><br />
<td valign="top">Published or web-based references that describe the data or methods used to produce it. Recommend URIs (such as a URL or DOI) for papers or other references. This attribute is defined in the CF conventions.</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="long_name">long_name</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary). This attribute is recommended by the NetCDF Users Guide, the COARDS convention, and the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="standard_name">standard_name</td><br />
<td>A long descriptive name for the variable taken from a controlled vocabulary of variable names. We recommend using the CF convention and the variable names from the CF standard name table. This attribute is recommended by the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="units">units</td><br />
<td valign="top">The units of the variable's data values. This attribute value should be a valid udunits string. The "units" attribute is recommended by the NetCDF Users Guide, the COARDS convention, and the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="coverage_content_type">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data (image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, or coordinate).</td><br />
</tr><br />
</table><br />
<br />
=Deprecated Attribute=<br />
The following term and definition is still recognized, but is no longer recommended for use by ACDD.<br />
<br />
: Metadata_Convention: removed in favor of 'Conventions'<br />
<br />
= Index by Attribute Name =<br />
<table><br />
<tr><br />
<td valign="top"><br />
<ul><br />
<li>[[#acknowledgement|acknowledgement]] (Recommended)</li><br />
<li>[[#cdm_data_type|cdm_data_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#comment|comment]] (Recommended)</li><br />
<li>[[#contributor_name|contributor_name]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#contributor_role|contributor_role]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#Conventions|Conventions]] ('''Highly Recommended''')</li><br />
<li>[[#coverage_content_type|coverage_content_type]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#creator_email|creator_email]] (Recommended)</li><br />
<li>[[#creator_institution|creator_institution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#creator_name|creator_name]] (Recommended)</li><br />
<li>[[#creator_type|creator_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#creator_url|creator_url]] (Recommended)</li><br />
<li>[[#date_created|date_created]] (Recommended)</li><br />
<li>[[#date_issued|date_issued]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#date_metadata_modified|date_metadata_modified]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#date_modified|date_modified]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_bounds|geospatial_bounds]] (Recommended)</li><br />
<li>[[#geospatial_bounds_crs|geospatial_bounds_crs]] (Recommended)</li><br />
<li>[[#geospatial_bounds_vertical_crs|geospatial_bounds_vertical_crs]] (Recommended)</li><br />
<li>[[#geospatial_lat_max|geospatial_lat_max]] (Recommended)</li><br />
<li>[[#geospatial_lat_min|geospatial_lat_min]] (Recommended)</li><br />
<li>[[#geospatial_lat_resolution|geospatial_lat_resolution]] (<font color="gray">Suggested</font>)</li><br />
</ul><br />
</td><br />
<td valign="top"><br />
<ul> <br />
<li>[[#geospatial_lat_units|geospatial_lat_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_lon_max|geospatial_lon_max]] (Recommended)</li><br />
<li>[[#geospatial_lon_min|geospatial_lon_min]] (Recommended)</li><br />
<li>[[#geospatial_lon_resolution|geospatial_lon_resolution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_lon_units|geospatial_lon_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_vertical_max|geospatial_vertical_max]] (Recommended)</li><br />
<li>[[#geospatial_vertical_min|geospatial_vertical_min]] (Recommended)</li><br />
<li>[[#geospatial_vertical_positive|geospatial_vertical_positive]] (Recommended)</li><br />
<li>[[#geospatial_vertical_resolution|geospatial_vertical_resolution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_vertical_units|geospatial_vertical_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#history|history]] (Recommended)</li><br />
<li>[[#id|id]] (Recommended)</li><br />
<li>[[#institution|institution]] (Recommended)</li><br />
<li>[[#instrument|instrument]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#instrument_vocabulary|instrument_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#keywords|keywords]] ('''Highly Recommended''')</li><br />
<li>[[#keywords_vocabulary|keywords_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#license|license]] (Recommended)</li><br />
<li>[[#long_name|long_name]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#metadata_link|metadata_link]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#naming_authority|naming_authority]] (Recommended)</li><br />
<li>[[#platform|platform]] (<font color="gray">Suggested</font>)</li><br />
</ul><br />
</td><br />
<td valign="top"><br />
<ul><br />
<li>[[#platform_vocabulary|platform_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#processing_level|processing_level]] (Recommended)</li><br />
<li>[[#product_version|product_version]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#program|program]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#project|project]] (Recommended)</li><br />
<li>[[#publisher_email|publisher_email]] (Recommended)</li><br />
<li>[[#publisher_institution|publisher_institution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#publisher_name|publisher_name]] (Recommended)</li><br />
<li>[[#publisher_type|publisher_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#publisher_url|publisher_url]] (Recommended)</li><br />
<li>[[#references|references]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#source|source]] (Recommended)</li><br />
<li>[[#standard_name|standard_name]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#standard_name_vocabulary|standard_name_vocabulary]] (Recommended)</li><br />
<li>[[#summary|summary]] ('''Highly Recommended''')</li><br />
<li>[[#time_coverage_duration|time_coverage_duration]] (Recommended)</li><br />
<li>[[#time_coverage_end|time_coverage_end]] (Recommended)</li><br />
<li>[[#time_coverage_resolution|time_coverage_resolution]] (Recommended)</li><br />
<li>[[#time_coverage_start|time_coverage_start]] (Recommended)</li><br />
<li>[[#title|title]] ('''Highly Recommended''')</li><br />
<li>[[#units|units]] ('''Highly Recommended''') [Variable]</li><br />
</ul><br />
</td><br />
</tr><br />
</table><br />
<br />
= Conformance Test =<br />
Conformance tests are available for verson 1.1. A conformance test for this version will be linked from this page when it is available.<br />
<br />
= Additional Materials =<br />
These materials are not normative and may not be in alignment with this version of ACDD. <br />
* Mappings ACDD to other metadata dialects<br />
**[[Attribute Convention for Data Discovery (ACDD) Mappings]]-<br />
* Recommended Order of Precedence<br />
**[[Attribute Convention for Data Discovery (ACDD) Precedence]]<br />
* Future Directions: Object Conventions for Data Discovery<br />
** [[Attribute Convention for Data Discovery (ACDD) Object Conventions]]<br />
* ISO Translation Notes<br />
** http://wiki.esipfed.org/index.php?title=Attribute_Convention_for_Data_Discovery_(ACDD)_ISO_TranslationNotes</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Future_Directions&diff=48581Attribute Convention for Data Discovery Future Directions2015-01-05T20:07:54Z<p>Graybeal: </p>
<hr />
<div>With the approval of version 1-3 of the ACDD, there are two paths for possible changes.<br />
<br />
A major revision has been proposed, to "version 2" of the ACDD. This revision is envisioned as an 'object oriented' organization, likely taking advantage of NetCDF 4's group capabilities.<br />
<br />
Further revisions might also be proposed to the 1.3 release. However, given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. Therefore, while the following document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path.<br />
* [[ACDD 1-3 Follow-on Discussions]]<br />
<br />
[[Category: Documentation Cluster]]<br />
[[Category: Attribute Conventions Dataset Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Future_Directions&diff=48580Attribute Convention for Data Discovery Future Directions2015-01-05T20:06:38Z<p>Graybeal: </p>
<hr />
<div>With the approval of version 1-3 of the ACDD, there are two paths for possible changes.<br />
<br />
A major revision has been proposed, to "version 2" of the ACDD. This revision is envisioned as an 'object oriented' organization, likely taking advantage of NetCDF 4's group capabilities.<br />
<br />
Further revisions might also be proposed to the 1.3 release. However, given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. Therefore, while the following document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path.<br />
* [[ACDD 1-3 Follow-on Discussions]]<br />
<br />
[[Category: Documentation Cluster]]<br />
[[Category: Attribute Conventions Data Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Future_Directions&diff=48579Attribute Convention for Data Discovery Future Directions2015-01-05T20:05:39Z<p>Graybeal: </p>
<hr />
<div>With the approval of version 1-3 of the ACDD, there are two paths for possible changes.<br />
<br />
A major revision has been proposed, to "version 2" of the ACDD. This revision is envisioned as an 'object oriented' organization, likely taking advantage of NetCDF 4's group capabilities.<br />
<br />
Further revisions might also be proposed to the 1.3 release. However, given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. Therefore, while the following document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path.<br />
* [[ACDD 1-3 Follow-on Discussions]]<br />
<br />
[[Category: Documentation Cluster]]<br />
[[Category: Attribute Conventions for Data Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery&diff=48578Attribute Convention for Data Discovery2015-01-05T20:04:01Z<p>Graybeal: </p>
<hr />
<div>#REDIRECT [[Attribute Convention for Data Discovery 1-3]]<br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category:Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-2_Working&diff=48577Attribute Convention for Data Discovery 1-2 Working2015-01-05T20:02:26Z<p>Graybeal: removed Documentation Cluster category</p>
<hr />
<div>[[Category: Attribute Conventions Dataset Discovery]]<br />
<br />
__TOC__<br />
<br />
== Version and Status ==<br />
<br />
This is an older working document for updates to the ACDD convention, leading to version 1.2 of that convention. This page is no longer under development, but is maintained for historical reasons. It contains extensive (but not complete) documentation of discussions during the development of version 1.3.<br />
<br />
Note this document is not a full replacement of the original 1.1; that full replacement will be built upon approval of this content.<br />
<br />
The version of this ''working'' document is designated as version 1.2.3.<br />
<br />
= Introduction =<br />
<br />
This page consolidates ongoing work seeking to improve the definitions in the [[Attribute Convention for Data Discovery (ACDD)]].<br />
<br />
The first 3 sections represent the terms in the corresponding sections of the ACDD.<br />
<br />
Modifications relative to the original text may be seen with the history mechanism of this wiki. The original definitions are marked in that history with the Summary keyword Original Definitions.<br />
<br />
== Process ==<br />
<br />
The edits have been made in this page by anyone in the community who wishes to contribute, and discussed in greater depth in the Discussion page, if necessary.<br />
<br />
Once there is consensus about these definitions, they will be migrated to a new version of the [[Attribute Convention for Data Discovery|primary document]].<br />
<br />
== Status ==<br />
<br />
This summarizes the status of the terms as of 2014.02.03. All major issues have been resolved in the document, pending review by the ACDD team.<br />
<br />
Details may be reviewed below the [http://wiki.esipfed.org/index.php/Talk:Attribute_Convention_for_Data_Discovery_Working#List_of_Open_Issues open issues] in the Discussion page.<br />
<br />
= Suggested Changes to introductory words =<br />
<br />
The following (between § marks) is proposed to replace the top text on the [[Attribute Convention for Data Discovery 1-1]] page, until just before the Highly Recommended section.<br />
<br />
§<br />
== Version and Status ==<br />
<br />
This is version 1.2 of the ACDD convention.<br />
<br />
The target page [[Attribute Convention for Data Discovery]] will always point to the current version of this convention. As the convention is updated, the version number at the top of the page and in the URL will be updated, and the target page will redirect to the most recent version.<br />
<br />
See the [[http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page]] for an overview of this convention and history about its development. <br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained can be found at [[Attribute_Convention_for_Data_Discovery_Working]], which redirects to the current working document, if any.<br />
<br />
= Overview =<br />
The NetCDF Group at Unidata has recommended [http://www.unidata.ucar.edu/software/thredds/v4.3/netcdf-java/formats/DataDiscoveryAttConvention.html attributes for data discovery] . The Attribute Convention for Data Discovery (ACDD) addresses that need, providing definitions for NetCDF global attributes that will help data to be located efficiently. <br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cf-pcmdi.llnl.gov/documents/cf-conventions/latest-cf-conventions-document-1/ (CF)] provides more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines two, title and history; CF specifies many more. ACDD 1.2 adopts all CF 1.6 global attributes with the exception of 'institution'; we specify 'creator_institution' and 'publisher_institution', to provide more provenance information. We also modify the syntax of the 'Conventions' attribute; we adopt the NUG recommendation to supply all conventions in a single attribute. This change has been approved by the CF Conventions Committee and will be part of CF 1.7, which is not yet published.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] page includes also includes a crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
<br />
Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. If additional metadata exists, you can make users aware of it by adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata.<br />
<br />
== Conformance Test ==<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
== Maintenance of Metadata ==<br />
<br />
ACDD attributes, like all NetCDF attributes, characterize their containing (parent) granules. As NetCDF data are processed (e.g., through subsetting or other algorithms), these characteristics can be altered. The software or user processor is responsible to update these attributes as part of the processing, but some software processes and user practices leave them unchanged. This affects both consumers and producers of these files, which comprises three roles: <br />
* developers of software tools that process NetCDF files; <br />
* users that create new NetCDF files from existing ones; and <br />
* end users of NetCDF files.<br />
<br />
NetCDF file ''creators'' (the first two roles) should ensure that the attributes of output files accurately represent those files, and specifically should not "pass through" any source attribute in unaltered form, unless it is known to remain accurate. NetCDF file ''users'' (all three roles) should verify critical attribute values, and understand how the source data and metadata were generated, to be confident the source metadata is current. <br />
<br />
The ACDD geospatiotemporal attributes present a special case, as this information is already fully defined by the CF coordinate variables (the redundant attributes are recommended to simplify access). Errors in these attributes will create an inconsistency between the metadata and data of the granule or file. The risk of these 'inconsistency errors' is highest for files that are aggregated into longer or larger products, or subset into shorter or smaller products, such as files from numerical forecast models and gridded satellite observations. For this reason, some providers of those data types may choose to omit the ACDD geospatiotemporal attributes from their files. If the ACDD geospatiotemporal attributes are present, checking them against the CF coordinate variables can serve as a partial test of the metadata's validity.<br />
<br />
''{(Not for inclusion in final draft) As a working tool, the page [[NetCDF Utilities Metadata Handling]] has been created to identify the state of play for how tools handle metadata attributes when processing files.}''<br />
<br />
= Global Attributes = <br />
''(reformat Highly Recommended, Recommended, etc. as 2nd-level headings)''<br />
<br />
§<br />
<br />
== Highly Recommended ==<br />
<br />
; title : A short phrase or sentence describing the dataset; this is a NetCDF Users Guide ([http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]) attribute. <br />
; summary : A paragraph describing the dataset, analogous to an abstract for a paper.<br />
; keywords : A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also keywords_vocabulary attribute).<br />
; Conventions : A list of the conventions followed by the dataset; blank space separated is recommended but commas should be used if any convention name contains blanks. For files that comply with this version of ACDD, include the term ACDD-1.2. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
<br />
== Recommended ==<br />
<br />
; id : An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include blanks.<br />
; naming_authority : The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute.<br />
; cdm_data_type : The organization of the data, as derived from the Common Data Model's Scientific Data layer and understood by THREDDS (this is a [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS "dataType"]). One of point, profile, section, station, station_profile, trajectory, grid, image, or swath. Please note that this is different from the CF NetCDF attribute 'featureType' that indicates a Discrete Sampling Geometry file - for guidance on those terms, please see [http://www.nodc.noaa.gov/data/formats/netcdf/ this NODC guidance].<br />
; history : Describes the processes/transformations used to create this data; can serve as an audit trail. This attribute is defined in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append an ISO Lineage reference; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. <br />
; source : The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; comment : Miscellaneous information about the data, not captured elsewhere. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; date_content_modified : The date on which any of the provided content, including data, metadata, and presented format, was last created or changed (ISO 8601 format)<br />
; date_values_modified: The date on which the provided data values were last created or changed; excludes metadata and formatting changes (ISO 8601 format)<br />
; creator : The name of the person principally responsible for originating this data. <br />
; creator_email : The email address of the person principally responsible for originating this data.<br />
; publisher : The person responsible for the data file or product, with its current metadata and format. <br />
; publisher_email : The email address of the person responsible for the data file or product.<br />
; processing_level : A textual description of the processing (or quality control) level of the data.<br />
; acknowledgement : A place to acknowledge various type of support for the project that produced this data.<br />
; geospatial_bounds : Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the Well-Known Text (WKT) format.<br />
; geospatial_lat_min : Describes a simple lower latitude limit; may be part of a bounding box or cube. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.<br />
; geospatial_lat_max : Describes a simple upper latitude limit; may be part of a bounding box or cube. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.<br />
; geospatial_lon_min : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_min specifies the westernmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_lon_max : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_vertical_min : Describes a numerically smaller vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset.<br />
; geospatial_vertical_max : Describes a numerically larger vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset.<br />
; geospatial_vertical_positive : One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum.<br />
; time_coverage_start : Describes the time of the first data point in the data set. ISO8601 format recommended.<br />
; time_coverage_end : Describes the time of the last data point in the data set. ISO8601 format recommended.<br />
; time_coverage_duration : Describes the duration of the data set. ISO8601 duration format recommended.<br />
; time_coverage_resolution : Describes the targeted time period between each value in the data set. ISO8601 duration format recommended.<br />
; license : Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.<br />
<br />
== Suggested ==<br />
<br />
The following terms and definitions are offered in case they address your situation.<br />
<br />
; contributor_info : The name and role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; date_product_generated : The date on which this data file or product was produced/distributed (ISO 8601 format). While this date is like a file timestamp, the date_content_modified and date_values_modified should be used to assess the age of the contents of the file or product.<br />
; geospatial_lat_units : Units for the latitude axis. These are presumed to be "degree_north"; other options from udunits may be specified instead.<br />
; geospatial_lat_resolution : Information about the targeted spacing of points in latitude. (Format is not prescribed.)<br />
; geospatial_lon_units : Units for the longitude axis. These are presumed to be "degree_east"; other options from udunits may be specified instead.<br />
; geospatial_lon_resolution : Information about the targeted spacing of points in longitude. (Format is not prescribed.)<br />
; geospatial_vertical_units : Units for the vertical axis. These are presumed to be "meter" (of depth); other options from udunits may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar.<br />
; geospatial_vertical_resolution : Information about the targeted vertical spacing of points. <br />
; creator_uri : The unique identifier of the person principally responsible for originating this data. <br />
; creator_institution : The institution that originated this data; should uniquely identify the institution. <br />
; creator_institution_info : Additional free text information for the institution that originated this data.<br />
; creator_project : The scientific project that originated this data; should uniquely identify the project. <br />
; creator_project_info : Additional free text information for the institution that originated this data.<br />
; publisher_uri : The unique identifier of the person responsible for providing the data file or product. <br />
; publisher_institution : The institution that provided the data file or equivalent product; should uniquely identify the institution. <br />
; publisher_institution_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; publisher_project : The scientific project that provided the data file or equivalent product; should uniquely identify the project. <br />
; publisher_project_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; keywords_vocabulary : If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix (e.g., "CF:NetCDF COARDS Climate and Forecast Standard Names") and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key.<br />
; metadata_link : A URI that gives the location of more complete metadata; a URL is recommended.<br />
<br />
== Deprecated ==<br />
<br />
The following terms and definitions are still in the specification, but are no longer recommended for use.<br />
<br />
: Metadata_Convention : (deprecated, supported for backward compatibility with current usage) Reference to the particular metadata convention(s) used for the described data file; recommended practice is to add the metadata convention(s) to the comma-delimited conventions list in the 'Conventions' attribute, per NetCDF Best Practices.<br />
: date_created :deleted in favor of date_product_generated (which used to be date_issued); we did not have a use case for knowing the date a stream or product was _first_ generated, once it has been updated<br />
: date_issued : changed name to date_product_generated<br />
: date_modified : changed name to date_content_modified<br />
<br />
----<br />
<br />
= Additional Materials =<br />
== Mappings ACDD to other metadata dialects ==<br />
[[Attribute Convention for Data Discovery (ACDD) Mappings]]<br />
<br />
== Recommended Order of Precedence ==<br />
[[Attribute Convention for Data Discovery (ACDD) Precedence]]<br />
<br />
== Future Directions: Object Conventions for Data Discovery ==<br />
[[Attribute Convention for Data Discovery (ACDD) Object Conventions]]<br />
<br />
== ISO Translation Notes ==<br />
http://wiki.esipfed.org/index.php?title=Attribute_Convention_for_Data_Discovery_(ACDD)_ISO_TranslationNotes</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=ACDD_1-3_Follow-on_Discussions&diff=48576ACDD 1-3 Follow-on Discussions2015-01-05T20:01:22Z<p>Graybeal: Created page with "This page has been created to capture suggestions and concerns about the released ACDD 1-3 specification. As noted in [[Attribute Convention for Data Discovery Future Directi..."</p>
<hr />
<div>This page has been created to capture suggestions and concerns about the released ACDD 1-3 specification.<br />
<br />
As noted in [[Attribute Convention for Data Discovery Future Directions]], given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. <br />
<br />
Therefore, while this document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path. <br />
<br />
It is suggested that each topic follow the following format. You might want to append '(minor fix)' to the topic name if you think this is worth an update to 1.3, as opposed to consideration in version 2. <br />
<br />
----<br />
== Topic ==<br />
<br />
Text description of the issues or suggested changes.<br />
<br />
[[User:Graybeal|Graybeal]] ([[User talk:Graybeal|talk]]) 13:01, 5 January 2015 (MST) (your signature)<br />
<br />
----</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-2&diff=48575Attribute Convention for Data Discovery 1-22015-01-05T19:55:43Z<p>Graybeal: </p>
<hr />
<div>[[Category: Attribute Conventions Dataset Discovery]]<br />
<br />
<font color="red">''(This page is in development, is not the 1-2 standard, and should not be used for review.)''</font><br />
<br />
__TOC__<br />
<br />
<br />
== Version and Status ==<br />
<br />
This is version 1.2 of the ACDD convention.<br />
<br />
The target page [[Attribute Convention for Data Discovery]] will always point to the current version of this convention. As the convention is updated, the version number at the top of the page and in the URL will be updated, and the target page will redirect to the most recent version.<br />
<br />
See the [[http://wikiCategory:Attribute_Conventions_Dataset_Discovery category page]] for an overview of this convention and history about its development. <br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained can be found at [[Attribute_Convention_for_Data_Discovery_Working]], which redirects to the current working document, if any.<br />
<br />
= Overview =<br />
The NetCDF Group at Unidata has recommended [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html attributes for data discovery] . The Attribute Convention for Data Discovery (ACDD) addresses that need, providing definitions for NetCDF global attributes that will help data to be located efficiently. <br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cf-pcmdi.llnl.gov/documents/cf-conventions/latest-cf-conventions-document-1/ (CF)] provide more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines two, title and history; CF specifies many more. ACDD adopts all CF global attributes, with the exception of institution; we specify creator_institution and publisher_institution to allow more information about the data to be included.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
<br />
Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
== Conformance Test ==<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
= Global Attributes = <br />
<br />
== Highly Recommended ==<br />
<br />
; title : A short phrase or sentence describing the dataset; this is a NetCDF Users Guide ([http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]) attribute. <br />
; summary : A paragraph describing the dataset, analogous to an abstract for a paper.<br />
; keywords : A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also keywords_vocabulary attribute).<br />
; Conventions : A list of the conventions followed by the dataset; blank space separated is recommended but commas should be used if any convention name contains blanks. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
<br />
== Recommended ==<br />
<br />
; id : An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include blanks.<br />
; naming_authority : The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute.<br />
; cdm_data_type : The organization of the data, as derived from the Common Data Model's Scientific Data layer and understood by THREDDS (this is a [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS "dataType"]). One of point, profile, section, station, station_profile, trajectory, grid, image, or swath. Please note that this is different from the CF NetCDF attribute 'featureType' that indicates a Discrete Sampling Geometry file - for guidance on those terms, please see [http://www.nodc.noaa.gov/data/formats/netcdf/ this NODC guidance].<br />
; history : Describes the processes/transformations used to create this data; can serve as an audit trail. Per the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append an ISO Lineage reference; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
; source : The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; comment : Miscellaneous information about the data, not captured elsewhere. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; date_content_modified : The date on which any of the provided content, including data, metadata, and presented format, was last changed (ISO 8601 format)<br />
; date_values_modified: The date on which the provided data values were last changed; excludes metadata and formatting changes (ISO 8601 format)<br />
; creator : The name of the person principally responsible for originating this data. <br />
; creator_email : The email address of the person principally responsible for originating this data.<br />
; publisher : The person responsible for the data file or product, with its current metadata and format. <br />
; publisher_email : The email address of the person responsible for the data file or product.<br />
; processing_level : A textual description of the processing (or quality control) level of the data.<br />
; acknowledgement : A place to acknowledge various type of support for the project that produced this data.<br />
; geospatial_bounds : Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the Well-Known Text (WKT) format.<br />
; geospatial_lat_min : Describes a simple lower latitude limit; may be part of a bounding box or cube. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.<br />
; geospatial_lat_max : Describes a simple upper latitude limit; may be part of a bounding box or cube. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.<br />
; geospatial_lon_min : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_min specifies the westernmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_lon_max : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_vertical_min : Describes a numerically smaller vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset.<br />
; geospatial_vertical_max : Describes a numerically larger vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset.<br />
; geospatial_vertical_positive : One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum.<br />
; time_coverage_start : Describes the time of the first data point in the data set. ISO8601 format recommended.<br />
; time_coverage_end : Describes the time of the last data point in the data set. ISO8601 format recommended.<br />
; time_coverage_duration : Describes the duration of the data set. ISO8601 duration format recommended.<br />
; time_coverage_resolution : Describes the targeted time period between each value in the data set. ISO8601 duration format recommended.<br />
; license : Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.<br />
<br />
== Suggested ==<br />
<br />
The following terms and definitions are offered in case they address your situation.<br />
<br />
; contributor_info : The name and role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; date_product_generated : The date on which this data file or product was produced/distributed (ISO 8601 format). While this date is like a file timestamp, the date_content_modified and date_values_modified should be used to assess the age of the contents of the file or product.<br />
; geospatial_lat_units : Units for the latitude axis. These are presumed to be "degree_north"; other options from udunits may be specified instead.<br />
; geospatial_lat_resolution : Information about the targeted spacing of points in latitude. (Format is not prescribed.)<br />
; geospatial_lon_units : Units for the longitude axis. These are presumed to be "degree_east"; other options from udunits may be specified instead.<br />
; geospatial_lon_resolution : Information about the targeted spacing of points in longitude. (Format is not prescribed.)<br />
; geospatial_vertical_units : Units for the vertical axis. These are presumed to be "meter" (of depth); other options from udunits may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar.<br />
; geospatial_vertical_resolution : Information about the targeted vertical spacing of points. <br />
; creator_uri : The unique identifier of the person principally responsible for originating this data. <br />
; creator_institution : The institution that originated this data; should uniquely identify the institution. <br />
; creator_institution_info : Additional free text information for the institution that originated this data.<br />
; creator_project : The scientific project that originated this data; should uniquely identify the project. <br />
; creator_project_info : Additional free text information for the institution that originated this data.<br />
; publisher_uri : The unique identifier of the person responsible for providing the data file or product. <br />
; publisher_institution : The institution that provided the data file or equivalent product; should uniquely identify the institution. <br />
; publisher_institution_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; publisher_project : The scientific project that provided the data file or equivalent product; should uniquely identify the project. <br />
; publisher_project_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; keywords_vocabulary : If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix (e.g., "CF:NetCDF COARDS Climate and Forecast Standard Names") and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key.<br />
; metadata_link : A URI that gives the location of more complete metadata; a URL is recommended.<br />
<br />
== Deprecated ==<br />
<br />
The following terms and definitions are still in the specification, but are no longer recommended for use.<br />
<br />
; Metadata_Convention : (deprecated, supported for backward compatibility with current usage) Reference to the particular metadata convention(s) used for the described data file; recommended practice is to add the metadata convention(s) to the comma-delimited conventions list in the 'Conventions' attribute, per NetCDF Best Practices.<br />
<br />
----<br />
<br />
= Additional Materials =<br />
<br />
== Mappings of ACDD attributes to other metadata dialects ==<br />
[[Attribute Convention for Data Discovery Mappings]]<br />
<br />
== Recommended Order of Precedence ==<br />
[[Attribute Convention for Data Discovery Precedence]]<br />
<br />
== Future Directions: Object Conventions for Data Discovery ==<br />
[[Attribute Convention for Data Discovery Object Conventions]]<br />
<br />
== ISO Translation Notes ==<br />
[[Attribute Convention for Data Discovery ISO Translation Notes]]<br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Future_Directions&diff=48574Attribute Convention for Data Discovery Future Directions2015-01-05T19:54:37Z<p>Graybeal: created page</p>
<hr />
<div>With the approval of version 1-3 of the ACDD, there are two paths for possible changes.<br />
<br />
A major revision has been proposed, to "version 2" of the ACDD. This revision is envisioned as an 'object oriented' organization, likely taking advantage of NetCDF 4's group capabilities.<br />
<br />
Further revisions might also be proposed to the 1.3 release. However, given the anticipated transition to an object-oriented version 2, significant changes to 1.3 may well be deferred in favor of the version 2 work. Therefore, while the following document has been created to collect comments and changes for 1.3, its name and introduction reflect the likely development path.<br />
* [[ACDD 1-3 Follow-on Discussions]]<br />
<br />
[[Category: Documentation Cluster]]<br />
[[Category: Attribute Convention for Data Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-3&diff=48573Attribute Convention for Data Discovery 1-32015-01-05T19:36:45Z<p>Graybeal: moved category entries to top</p>
<hr />
<div>[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]<br />
= Context =<br />
<br />
== Document ==<br />
<br />
This is the Attribute Convention for Data Discovery (ACDD).<br />
<br />
== Version and Status ==<br />
<br />
This version is designated as Version 1.3; it is the latest released version.<br />
<br />
The page [[Attribute Convention for Data Discovery (ACDD)]] always points to the current released version of the Convention. The version number at the top of the resulting page will show the current version.<br />
<br />
See the [http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery ACDD category page] for information on the history and maintenance of this convention.<br />
<br />
=== Development ===<br />
<br />
For development versions of the ACDD, please see the page [[Attribute Convention for Data Discovery Working]].<br />
<br />
Questions about this specification may be addressed to the [http://www.lists.esipfed.org/mailman/listinfo/esip-documentation ESIP Documentation Cluster mailing list].<br />
<br />
= Overview =<br />
This document describes attributes recommended for describing a NetCDF dataset to discovery systems such as Digital Libraries. THREDDS and other tools can use these attributes to extract metadata from datasets, and exporting to Dublin Core, DIF, ADN, FGDC, ISO 19115 and other metadata formats. This will help systems and users locate and use data efficiently.<br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cfconventions.org/ (CF)] provides more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines three, title, history, and Conventions. CF specifies more: institution, source, references, comment, and featureType. ACDD 1.3 adopts all CF 1.6 global attributes. In a change from ACDD 1.2, we adopt the NUG recommendation to supply all conventions in the single Conventions attribute.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so similar terms exist in many metadata standards. This [[Attribute_Convention_for_Data_Discovery_(ACDD)_Mappings]] page includes a crosswalk to THREDDS, OGC CSW, ISO 19115-2 and Rubric Categories.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
Documents using other metadata specifications (e.g., ISO 19115) can provide additional information about the dataset. If additional metadata exists, you can make users aware of it by adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata.<br />
<br />
== Definitions: Data and Metadata ==<br />
<br />
In several ACDD attribute names or definitions, the terms 'data' and 'metadata' are used. In the context of NetCDF files, these refer specifically to the values within the file, and the attributes of the file, respectively.<br />
<br />
== Maintenance of Metadata ==<br />
<br />
ACDD attributes characterize the data they are associated with. Any processing that alters these characteristics is responsible for updating the relevant attributes.<br />
<br />
NetCDF file creators and software developers should ensure that the attributes of output data accurately represent that data, and specifically should not "pass through" any source attribute in unaltered form, unless it is known to remain accurate. NetCDF data users should verify critical attribute values, to be confident the source metadata is appropriate.<br />
<br />
The ACDD geospatiotemporal attributes present a special case, as this information is already fully defined by the CF coordinate variables. These attributes are recommended, despite being redundant, because they greatly simplify data discovery and access.<br />
<br />
The risk of inconsistency between these attributes and the actual data is highest after aggregation or subsetting; checking them against the data can serve as a useful test of the metadata's validity.<br />
<br />
== Attribute Content Guidance ==<br />
<br />
=== Date and Time: ISO 8601 Recommended Formats ===<br />
<br />
The ACDD specifies [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601:2004] date and time formats for its temporal attributes. ACDD strongly encourages the use of the 'extended' format date-time, in the form <br />
<tt>YYYY-MM-DDThh:mm:ss<zone></tt><br />
(although ss, mm, and hh can be omitted, and <zone> can be Z, ±hh:mm, or ±hh). Per the standard, the shortened or basic format, which omits the - and : separators, "should be avoided in plain text."<br />
<br />
For duration attributes, again the extended form is strongly encouraged for readability:<br />
<tt>P[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]</tt><br />
<br />
If for some reason the strongly encouraged formats can not be used, other ISO 8601-compatible formats are acceptable, but may not be handled by some processing software.<br />
<br />
=== Comma-Separated Lists ===<br />
<br />
Several attributes explicitly allow the entry of multiple entities as comma-separated values. Any entities within such lists which contain a comma must be enclosed in straight double quotation marks ("), which will not be considered part of the entity.<br />
<br />
Spaces (ASCII character 32) between the entities are recommended for readability, but not required. Example: 'John Doe, Jane Lee, "L J Smith, Jr." '<br />
<br />
The same protocol may be used within free-text attributes, but is only recommended in cases where the attribute is being populated with structured data (rather than unconstrained text).<br />
<br />
=== Free Text Formatting: Structured Text Considerations ===<br />
<br />
In some attributes, it may be desirable to use structured text to support computer parsing of human-readable content. Because netCDF files are often translated between binary and text-based encodings like ncML (e.g., by the netCDF command line tools ''nco''), such structures should tolerate changes in white space, including end-of-line characters, that may occur during translation.<br />
<br />
= Global Attributes = <br />
== Highly Recommended ==<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="title">title</td><br />
<td valign="top">A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names. This attribute is also recommended by the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NetCDF Users Guide] and the [http://cfconventions.org/ CF conventions]. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="summary">summary</td><br />
<td valign="top">A paragraph describing the dataset, analogous to an abstract for a paper.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="keywords">keywords</td><br />
<td valign="top">A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary ([http://gcmd.gsfc.nasa.gov/learn/keywords.html GCMD] is often used), or URIs for terms from a controlled vocabulary (see also "keywords_vocabulary" attribute).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="Conventions">Conventions</td><br />
<td valign="top">A comma-separated list of the conventions that are followed by the dataset. For files that follow this version of ACDD, include the string 'ACDD-1.3'. (This attribute is described in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Conventions NetCDF Users Guide].)</td><br />
</tr><br />
</table><br />
<br />
==Recommended== <br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="id">id</td><br />
<td valign="top">An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include white space characters. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="naming_authority">naming_authority</td><br />
<td valign="top"> The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute. We recommend using reverse-DNS naming for the naming authority; URIs are also acceptable. Example: 'edu.ucar.unidata'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="history">history</td><br />
<td valign="top">Provides an audit trail for modifications to the original data. This attribute is also in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NetCDF Users Guide]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append a reference to an ISO Lineage entity; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="source">source</td><br />
<td valign="top">The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is defined in the CF Conventions. Examples: 'temperature from CTD #1234'; 'world model v.0.1'. <br />
</tr><br />
<tr><br />
<td valign="top" id="processing_level">processing_level</td><br />
<td valign="top">A textual description of the processing (or quality control) level of the data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="comment">comment</td><br />
<td valign="top"> Miscellaneous information about the data, not captured elsewhere. This attribute is defined in the [http://cfconventions.org/ CF Conventions].</td><br />
</tr><br />
<tr><br />
<td valign="top" id="acknowledgement">acknowledgement</td><br />
<td valign="top">A place to acknowledge various types of support for the project that produced this data. </td><br />
</tr><br />
<tr><br />
<td valign="top" id="license">license</td><br />
<td valign="top">Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="standard_name_vocabulary">standard_name_vocabulary</td><br />
<td valign="top"> The name and version of the controlled vocabulary from which variable standard names are taken. (Values for any standard_name attribute must come from the CF Standard Names vocabulary for the data file or product to comply with CF.) Example: 'CF Standard Name Table v27'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_created">date_created</td><br />
<td valign="top">The date on which this version of the data was created. (Modification of values implies a new version, hence this would be assigned the date of the most recent values modification.) Metadata changes are not considered when assigning the date_created. The ISO 8601:2004 extended date format is recommended, as described in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_name">creator_name</td><br />
<td valign="top">The name of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_email">creator_email</td><br />
<td valign="top">The email address of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_url">creator_url</td><br />
<td valign="top">The URL of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="institution">institution</td><br />
<td valign="top">The name of the institution principally responsible for originating this data. This attribute is recommended by the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="project">project</td><br />
<td valign="top">The name of the project(s) principally responsible for originating this data. Multiple projects can be separated by commas, as described under Attribute Content Guidelines. Examples: 'PATMOS-X', 'Extended Continental Shelf Project'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_name">publisher_name</td><br />
<td valign="top">The name of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_email">publisher_email</td><br />
<td valign="top">The email address of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_url">publisher_url</td><br />
<td valign="top">The URL of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds">geospatial_bounds</td><br />
<td>Describes the data's 2D or 3D geospatial extent in OGC's Well-Known Text (WKT) Geometry format (reference the OGC Simple Feature Access (SFA) specification). The meaning and order of values for each point's coordinates depends on the coordinate reference system (CRS). The ACDD default is 2D geometry in the EPSG:4326 coordinate reference system. The default may be overridden with geospatial_bounds_crs and geospatial_bounds_vertical_crs (see those attributes). EPSG:4326 coordinate values are latitude (decimal degrees_north) and longitude (decimal degrees_east), in that order. Longitude values in the default case are limited to the [-180, 180) range. Example: 'POLYGON ((40.26 -111.29, 41.26 -111.29, 41.26 -110.29, 40.26 -110.29, 40.26 -111.29))'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds_crs">geospatial_bounds_crs</td><br />
<td>The coordinate reference system (CRS) of the point coordinates in the geospatial_bounds attribute. This CRS may be 2-dimensional or 3-dimensional, but together with geospatial_bounds_vertical_crs, if that attribute is supplied, must match the dimensionality, order, and meaning of point coordinate values in the geospatial_bounds attribute. If geospatial_bounds_vertical_crs is also present then this attribute must only specify a 2D CRS. EPSG CRSs are strongly recommended. If this attribute is not specified, the CRS is assumed to be EPSG:4326. Examples: 'EPSG:4979' (the 3D WGS84 CRS), 'EPSG:4047'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_bounds_vertical_crs">geospatial_bounds_vertical_crs</td><br />
<td>The vertical coordinate reference system (CRS) for the Z axis of the point coordinates in the geospatial_bounds attribute. This attribute cannot be used if the CRS in geospatial_bounds_crs is 3-dimensional; to use this attribute, geospatial_bounds_crs must exist and specify a 2D CRS. EPSG CRSs are strongly recommended. There is no default for this attribute when not specified. Examples: 'EPSG:5829' (instantaneous height above sea level), "EPSG:5831" (instantaneous depth below sea level), or 'EPSG:5703' (NAVD88 height).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_min">geospatial_lat_min</td><br />
<td valign="top">Describes a simple lower latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_max">geospatial_lat_max</td><br />
<td valign="top">Describes a simple upper latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_min">geospatial_lon_min</td><br />
<td valign="top">Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_min specifies the westernmost longitude covered by the dataset. See also geospatial_lon_max.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_max">geospatial_lon_max</td><br />
<td valign="top">Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min; for example, geospatial_lon_min=170 and geospatial_lon_max=-175 incorporates 15 degrees of longitude (ranges 170 to 180 and -180 to -175).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_min">geospatial_vertical_min</td><br />
<td valign="top">Describes the numerically smaller vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_max">geospatial_vertical_max</td><br />
<td valign="top">Describes the numerically larger vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_positive">geospatial_vertical_positive</td><br />
<td valign="top">One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum. Note that if geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the data's vertical location furthest from the earth's center, and the geospatial_vertical_max attribute specifies the location closest to the earth's center.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_start">time_coverage_start</td><br />
<td valign="top">Describes the time of the first data point in the data set. Use the ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_end">time_coverage_end</td><br />
<td valign="top">Describes the time of the last data point in the data set. Use ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_duration">time_coverage_duration</td><br />
<td valign="top">Describes the duration of the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="time_coverage_resolution">time_coverage_resolution</td><br />
<td valign="top">Describes the targeted time period between each value in the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.</td><br />
</tr><br />
</table><br />
<br />
==Suggested==<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_type">creator_type</td><br />
<td valign="top">Specifies type of creator with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the creator is assumed to be a person.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="creator_institution">creator_institution</td><br />
<td valign="top">The institution of the creator; should uniquely identify the creator's institution. This attribute's value should be specified even if it matches the value of publisher_institution, or if creator_type is institution.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_type">publisher_type</td><br />
<td valign="top">Specifies type of publisher with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the publisher is assumed to be a person.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="publisher_institution">publisher_institution</td><br />
<td valign="top">The institution that presented the data file or equivalent product to users; should uniquely identify the institution. If publisher_type is institution, this should have the same value as publisher_name.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="program">program</td><br />
<td valign="top">The overarching program(s) of which the dataset is a part. A program consists of a set (or portfolio) of related and possibly interdependent projects that meet an overarching objective. Examples: 'GHRSST', 'NOAA CDR', 'NASA EOS', 'JPSS', 'GOES-R'.<br />
</td><br />
</tr><br />
<tr><br />
<td valign="top" id="contributor_name">contributor_name</td><br />
<td valign="top">The name of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="contributor_role">contributor_role</td><br />
<td valign="top">The role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters). Multiple roles should be presented in the same order and number as the names in contributor_names.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_units">geospatial_lat_units</td><br />
<td valign="top">Units for the latitude axis described in "geospatial_lat_min" and "geospatial_lat_max" attributes. These are presumed to be "degree_north"; other options from udunits may be specified instead.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lat_resolution">geospatial_lat_resolution</td><br />
<td valign="top">Information about the targeted spacing of points in latitude. Recommend describing resolution as a number value followed by the units. Examples: '100 meters', '0.1 degree'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_units">geospatial_lon_units</td><br />
<td valign="top">Units for the longitude axis described in "geospatial_lon_min" and "geospatial_lon_max" attributes. These are presumed to be "degree_east"; other options from udunits may be specified instead.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_lon_resolution">geospatial_lon_resolution</td><br />
<td valign="top">Information about the targeted spacing of points in longitude. Recommend describing resolution as a number value followed by units. Examples: '100 meters', '0.1 degree'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_units">geospatial_vertical_units</td><br />
<td valign="top">Units for the vertical axis described in "geospatial_vertical_min" and "geospatial_vertical_max" attributes. The default is EPSG:4979 (height above the ellipsoid, in meters); other vertical coordinate reference systems may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar. Examples: 'EPSG:5829' (instantaneous height above sea level), 'EPSG:5831' (instantaneous depth below sea level).</td><br />
</tr><br />
<tr><br />
<td valign="top" id="geospatial_vertical_resolution">geospatial_vertical_resolution</td><br />
<td valign="top">Information about the targeted vertical spacing of points. Example: '25 meters'</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_modified">date_modified</td><br />
<td valign="top">The date on which the data was last modified. Note that this applies just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_issued">date_issued</td><br />
<td valign="top">The date on which this data (including all modifications) was formally issued (i.e., made available to a wider audience). Note that these apply just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="date_metadata_modified">date_metadata_modified</td><br />
<td valign="top">The date on which the metadata was last modified. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="product_version">product_version</td><br />
<td valign="top">Version identifier of the data file or product as assigned by the data creator. For example, a new algorithm or methodology could result in a new product_version.</td><br />
<tr><br />
<td valign="top" id="keywords_vocabulary">keywords_vocabulary</td><br />
<td valign="top">If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key. Example: 'GCMD:GCMD Keywords, CF:NetCDF COARDS Climate and Forecast Standard Names'.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="platform">platform</td><br />
<td valign="top">Name of the platform(s) that supported the sensor data used to create this data set or product. Platforms can be of any type, including satellite, ship, station, aircraft or other. Indicate controlled vocabulary used in platform_vocabulary.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="platform_vocabulary">platform_vocabulary</td><br />
<td valign="top">Controlled vocabulary for the names used in the "platform" attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="instrument">instrument</td><br />
<td valign="top">Name of the contributing instrument(s) or sensor(s) used to create this data set or product. Indicate controlled vocabulary used in instrument_vocabulary.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="instrument_vocabulary">instrument_vocabulary</td><br />
<td valign="top">Controlled vocabulary for the names used in the "instrument" attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="cdm_data_type">cdm_data_type</td><br />
<td>The data type, as derived from Unidata's Common Data Model Scientific Data types and understood by THREDDS. (This is a THREDDS "dataType", and is different from the CF NetCDF attribute 'featureType', which indicates a Discrete Sampling Geometry file in CF.)</td><br />
</tr><br />
<tr><br />
<td valign="top" id="metadata_link">metadata_link</td><br />
<td valign="top">A URL that gives the location of more complete metadata. A persistent URL is recommended for this attribute.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="references">references</td><br />
<td valign="top">Published or web-based references that describe the data or methods used to produce it. Recommend URIs (such as a URL or DOI) for papers or other references. This attribute is defined in the CF conventions.</td><br />
</tr><br />
</table><br />
<br />
=Highly Recommended Variable Attributes=<br />
<table width="95%" border="1" cellpadding="2" cellspacing="2"><br />
<tr><br />
<th valign="top" width="200px">Attribute</th><br />
<th valign="top">Description</th><br />
</tr><br />
<tr><br />
<td valign="top" id="long_name">long_name</td><br />
<td valign="top">A long descriptive name for the variable (not necessarily from a controlled vocabulary). This attribute is recommended by the NetCDF Users Guide, the COARDS convention, and the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="standard_name">standard_name</td><br />
<td>A long descriptive name for the variable taken from a controlled vocabulary of variable names. We recommend using the CF convention and the variable names from the CF standard name table. This attribute is recommended by the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="units">units</td><br />
<td valign="top">The units of the variable's data values. This attribute value should be a valid udunits string. The "units" attribute is recommended by the NetCDF Users Guide, the COARDS convention, and the CF convention.</td><br />
</tr><br />
<tr><br />
<td valign="top" id="coverage_content_type">coverage_content_type</td><br />
<td valign="top">An ISO 19115-1 code to indicate the source of the data (image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, or coordinate).</td><br />
</tr><br />
</table><br />
<br />
=Deprecated Attribute=<br />
The following term and definition is still recognized, but is no longer recommended for use by ACDD.<br />
<br />
: Metadata_Convention: removed in favor of 'Conventions'<br />
<br />
= Index by Attribute Name =<br />
<table><br />
<tr><br />
<td valign="top"><br />
<ul><br />
<li>[[#acknowledgement|acknowledgement]] (Recommended)</li><br />
<li>[[#cdm_data_type|cdm_data_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#comment|comment]] (Recommended)</li><br />
<li>[[#contributor_name|contributor_name]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#contributor_role|contributor_role]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#Conventions|Conventions]] ('''Highly Recommended''')</li><br />
<li>[[#coverage_content_type|coverage_content_type]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#creator_email|creator_email]] (Recommended)</li><br />
<li>[[#creator_institution|creator_institution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#creator_name|creator_name]] (Recommended)</li><br />
<li>[[#creator_type|creator_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#creator_url|creator_url]] (Recommended)</li><br />
<li>[[#date_created|date_created]] (Recommended)</li><br />
<li>[[#date_issued|date_issued]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#date_metadata_modified|date_metadata_modified]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#date_modified|date_modified]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_bounds|geospatial_bounds]] (Recommended)</li><br />
<li>[[#geospatial_bounds_crs|geospatial_bounds_crs]] (Recommended)</li><br />
<li>[[#geospatial_bounds_vertical_crs|geospatial_bounds_vertical_crs]] (Recommended)</li><br />
<li>[[#geospatial_lat_max|geospatial_lat_max]] (Recommended)</li><br />
<li>[[#geospatial_lat_min|geospatial_lat_min]] (Recommended)</li><br />
<li>[[#geospatial_lat_resolution|geospatial_lat_resolution]] (<font color="gray">Suggested</font>)</li><br />
</ul><br />
</td><br />
<td valign="top"><br />
<ul> <br />
<li>[[#geospatial_lat_units|geospatial_lat_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_lon_max|geospatial_lon_max]] (Recommended)</li><br />
<li>[[#geospatial_lon_min|geospatial_lon_min]] (Recommended)</li><br />
<li>[[#geospatial_lon_resolution|geospatial_lon_resolution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_lon_units|geospatial_lon_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_vertical_max|geospatial_vertical_max]] (Recommended)</li><br />
<li>[[#geospatial_vertical_min|geospatial_vertical_min]] (Recommended)</li><br />
<li>[[#geospatial_vertical_positive|geospatial_vertical_positive]] (Recommended)</li><br />
<li>[[#geospatial_vertical_resolution|geospatial_vertical_resolution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#geospatial_vertical_units|geospatial_vertical_units]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#history|history]] (Recommended)</li><br />
<li>[[#id|id]] (Recommended)</li><br />
<li>[[#institution|institution]] (Recommended)</li><br />
<li>[[#instrument|instrument]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#instrument_vocabulary|instrument_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#keywords|keywords]] ('''Highly Recommended''')</li><br />
<li>[[#keywords_vocabulary|keywords_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#license|license]] (Recommended)</li><br />
<li>[[#long_name|long_name]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#metadata_link|metadata_link]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#naming_authority|naming_authority]] (Recommended)</li><br />
<li>[[#platform|platform]] (<font color="gray">Suggested</font>)</li><br />
</ul><br />
</td><br />
<td valign="top"><br />
<ul><br />
<li>[[#platform_vocabulary|platform_vocabulary]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#processing_level|processing_level]] (Recommended)</li><br />
<li>[[#product_version|product_version]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#program|program]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#project|project]] (Recommended)</li><br />
<li>[[#publisher_email|publisher_email]] (Recommended)</li><br />
<li>[[#publisher_institution|publisher_institution]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#publisher_name|publisher_name]] (Recommended)</li><br />
<li>[[#publisher_type|publisher_type]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#publisher_url|publisher_url]] (Recommended)</li><br />
<li>[[#references|references]] (<font color="gray">Suggested</font>)</li><br />
<li>[[#source|source]] (Recommended)</li><br />
<li>[[#standard_name|standard_name]] ('''Highly Recommended''') [Variable]</li><br />
<li>[[#standard_name_vocabulary|standard_name_vocabulary]] (Recommended)</li><br />
<li>[[#summary|summary]] ('''Highly Recommended''')</li><br />
<li>[[#time_coverage_duration|time_coverage_duration]] (Recommended)</li><br />
<li>[[#time_coverage_end|time_coverage_end]] (Recommended)</li><br />
<li>[[#time_coverage_resolution|time_coverage_resolution]] (Recommended)</li><br />
<li>[[#time_coverage_start|time_coverage_start]] (Recommended)</li><br />
<li>[[#title|title]] ('''Highly Recommended''')</li><br />
<li>[[#units|units]] ('''Highly Recommended''') [Variable]</li><br />
</ul><br />
</td><br />
</tr><br />
</table><br />
<br />
= Conformance Test =<br />
Conformance tests are available for verson 1.1. A conformance test for this version will be linked from this page when it is available.<br />
<br />
= Additional Materials =<br />
These materials are not normative and may not be in alignment with this version of ACDD. <br />
* Mappings ACDD to other metadata dialects<br />
**[[Attribute Convention for Data Discovery (ACDD) Mappings]]-<br />
* Recommended Order of Precedence<br />
**[[Attribute Convention for Data Discovery (ACDD) Precedence]]<br />
* Future Directions: Object Conventions for Data Discovery<br />
** [[Attribute Convention for Data Discovery (ACDD) Object Conventions]]<br />
* ISO Translation Notes<br />
** http://wiki.esipfed.org/index.php?title=Attribute_Convention_for_Data_Discovery_(ACDD)_ISO_TranslationNotes</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-2_Working&diff=48572Attribute Convention for Data Discovery 1-2 Working2015-01-05T19:34:47Z<p>Graybeal: </p>
<hr />
<div>[[Category: Attribute Conventions Dataset Discovery]]<br />
<br />
__TOC__<br />
<br />
== Version and Status ==<br />
<br />
This is an older working document for updates to the ACDD convention, leading to version 1.2 of that convention. This page is no longer under development, but is maintained for historical reasons. It contains extensive (but not complete) documentation of discussions during the development of version 1.3.<br />
<br />
Note this document is not a full replacement of the original 1.1; that full replacement will be built upon approval of this content.<br />
<br />
The version of this ''working'' document is designated as version 1.2.3.<br />
<br />
= Introduction =<br />
<br />
This page consolidates ongoing work seeking to improve the definitions in the [[Attribute Convention for Data Discovery (ACDD)]].<br />
<br />
The first 3 sections represent the terms in the corresponding sections of the ACDD.<br />
<br />
Modifications relative to the original text may be seen with the history mechanism of this wiki. The original definitions are marked in that history with the Summary keyword Original Definitions.<br />
<br />
== Process ==<br />
<br />
The edits have been made in this page by anyone in the community who wishes to contribute, and discussed in greater depth in the Discussion page, if necessary.<br />
<br />
Once there is consensus about these definitions, they will be migrated to a new version of the [[Attribute Convention for Data Discovery|primary document]].<br />
<br />
== Status ==<br />
<br />
This summarizes the status of the terms as of 2014.02.03. All major issues have been resolved in the document, pending review by the ACDD team.<br />
<br />
Details may be reviewed below the [http://wiki.esipfed.org/index.php/Talk:Attribute_Convention_for_Data_Discovery_Working#List_of_Open_Issues open issues] in the Discussion page.<br />
<br />
= Suggested Changes to introductory words =<br />
<br />
The following (between § marks) is proposed to replace the top text on the [[Attribute Convention for Data Discovery 1-1]] page, until just before the Highly Recommended section.<br />
<br />
§<br />
== Version and Status ==<br />
<br />
This is version 1.2 of the ACDD convention.<br />
<br />
The target page [[Attribute Convention for Data Discovery]] will always point to the current version of this convention. As the convention is updated, the version number at the top of the page and in the URL will be updated, and the target page will redirect to the most recent version.<br />
<br />
See the [[http://wiki.esipfed.org/index.php/Category:Attribute_Conventions_Dataset_Discovery category page]] for an overview of this convention and history about its development. <br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained can be found at [[Attribute_Convention_for_Data_Discovery_Working]], which redirects to the current working document, if any.<br />
<br />
= Overview =<br />
The NetCDF Group at Unidata has recommended [http://www.unidata.ucar.edu/software/thredds/v4.3/netcdf-java/formats/DataDiscoveryAttConvention.html attributes for data discovery] . The Attribute Convention for Data Discovery (ACDD) addresses that need, providing definitions for NetCDF global attributes that will help data to be located efficiently. <br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cf-pcmdi.llnl.gov/documents/cf-conventions/latest-cf-conventions-document-1/ (CF)] provides more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines two, title and history; CF specifies many more. ACDD 1.2 adopts all CF 1.6 global attributes with the exception of 'institution'; we specify 'creator_institution' and 'publisher_institution', to provide more provenance information. We also modify the syntax of the 'Conventions' attribute; we adopt the NUG recommendation to supply all conventions in a single attribute. This change has been approved by the CF Conventions Committee and will be part of CF 1.7, which is not yet published.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] page includes also includes a crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
<br />
Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. If additional metadata exists, you can make users aware of it by adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata.<br />
<br />
== Conformance Test ==<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
== Maintenance of Metadata ==<br />
<br />
ACDD attributes, like all NetCDF attributes, characterize their containing (parent) granules. As NetCDF data are processed (e.g., through subsetting or other algorithms), these characteristics can be altered. The software or user processor is responsible to update these attributes as part of the processing, but some software processes and user practices leave them unchanged. This affects both consumers and producers of these files, which comprises three roles: <br />
* developers of software tools that process NetCDF files; <br />
* users that create new NetCDF files from existing ones; and <br />
* end users of NetCDF files.<br />
<br />
NetCDF file ''creators'' (the first two roles) should ensure that the attributes of output files accurately represent those files, and specifically should not "pass through" any source attribute in unaltered form, unless it is known to remain accurate. NetCDF file ''users'' (all three roles) should verify critical attribute values, and understand how the source data and metadata were generated, to be confident the source metadata is current. <br />
<br />
The ACDD geospatiotemporal attributes present a special case, as this information is already fully defined by the CF coordinate variables (the redundant attributes are recommended to simplify access). Errors in these attributes will create an inconsistency between the metadata and data of the granule or file. The risk of these 'inconsistency errors' is highest for files that are aggregated into longer or larger products, or subset into shorter or smaller products, such as files from numerical forecast models and gridded satellite observations. For this reason, some providers of those data types may choose to omit the ACDD geospatiotemporal attributes from their files. If the ACDD geospatiotemporal attributes are present, checking them against the CF coordinate variables can serve as a partial test of the metadata's validity.<br />
<br />
''{(Not for inclusion in final draft) As a working tool, the page [[NetCDF Utilities Metadata Handling]] has been created to identify the state of play for how tools handle metadata attributes when processing files.}''<br />
<br />
= Global Attributes = <br />
''(reformat Highly Recommended, Recommended, etc. as 2nd-level headings)''<br />
<br />
§<br />
<br />
== Highly Recommended ==<br />
<br />
; title : A short phrase or sentence describing the dataset; this is a NetCDF Users Guide ([http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]) attribute. <br />
; summary : A paragraph describing the dataset, analogous to an abstract for a paper.<br />
; keywords : A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also keywords_vocabulary attribute).<br />
; Conventions : A list of the conventions followed by the dataset; blank space separated is recommended but commas should be used if any convention name contains blanks. For files that comply with this version of ACDD, include the term ACDD-1.2. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
<br />
== Recommended ==<br />
<br />
; id : An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include blanks.<br />
; naming_authority : The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute.<br />
; cdm_data_type : The organization of the data, as derived from the Common Data Model's Scientific Data layer and understood by THREDDS (this is a [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS "dataType"]). One of point, profile, section, station, station_profile, trajectory, grid, image, or swath. Please note that this is different from the CF NetCDF attribute 'featureType' that indicates a Discrete Sampling Geometry file - for guidance on those terms, please see [http://www.nodc.noaa.gov/data/formats/netcdf/ this NODC guidance].<br />
; history : Describes the processes/transformations used to create this data; can serve as an audit trail. This attribute is defined in the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append an ISO Lineage reference; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. <br />
; source : The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; comment : Miscellaneous information about the data, not captured elsewhere. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; date_content_modified : The date on which any of the provided content, including data, metadata, and presented format, was last created or changed (ISO 8601 format)<br />
; date_values_modified: The date on which the provided data values were last created or changed; excludes metadata and formatting changes (ISO 8601 format)<br />
; creator : The name of the person principally responsible for originating this data. <br />
; creator_email : The email address of the person principally responsible for originating this data.<br />
; publisher : The person responsible for the data file or product, with its current metadata and format. <br />
; publisher_email : The email address of the person responsible for the data file or product.<br />
; processing_level : A textual description of the processing (or quality control) level of the data.<br />
; acknowledgement : A place to acknowledge various type of support for the project that produced this data.<br />
; geospatial_bounds : Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the Well-Known Text (WKT) format.<br />
; geospatial_lat_min : Describes a simple lower latitude limit; may be part of a bounding box or cube. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.<br />
; geospatial_lat_max : Describes a simple upper latitude limit; may be part of a bounding box or cube. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.<br />
; geospatial_lon_min : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_min specifies the westernmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_lon_max : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_vertical_min : Describes a numerically smaller vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset.<br />
; geospatial_vertical_max : Describes a numerically larger vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset.<br />
; geospatial_vertical_positive : One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum.<br />
; time_coverage_start : Describes the time of the first data point in the data set. ISO8601 format recommended.<br />
; time_coverage_end : Describes the time of the last data point in the data set. ISO8601 format recommended.<br />
; time_coverage_duration : Describes the duration of the data set. ISO8601 duration format recommended.<br />
; time_coverage_resolution : Describes the targeted time period between each value in the data set. ISO8601 duration format recommended.<br />
; license : Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.<br />
<br />
== Suggested ==<br />
<br />
The following terms and definitions are offered in case they address your situation.<br />
<br />
; contributor_info : The name and role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; date_product_generated : The date on which this data file or product was produced/distributed (ISO 8601 format). While this date is like a file timestamp, the date_content_modified and date_values_modified should be used to assess the age of the contents of the file or product.<br />
; geospatial_lat_units : Units for the latitude axis. These are presumed to be "degree_north"; other options from udunits may be specified instead.<br />
; geospatial_lat_resolution : Information about the targeted spacing of points in latitude. (Format is not prescribed.)<br />
; geospatial_lon_units : Units for the longitude axis. These are presumed to be "degree_east"; other options from udunits may be specified instead.<br />
; geospatial_lon_resolution : Information about the targeted spacing of points in longitude. (Format is not prescribed.)<br />
; geospatial_vertical_units : Units for the vertical axis. These are presumed to be "meter" (of depth); other options from udunits may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar.<br />
; geospatial_vertical_resolution : Information about the targeted vertical spacing of points. <br />
; creator_uri : The unique identifier of the person principally responsible for originating this data. <br />
; creator_institution : The institution that originated this data; should uniquely identify the institution. <br />
; creator_institution_info : Additional free text information for the institution that originated this data.<br />
; creator_project : The scientific project that originated this data; should uniquely identify the project. <br />
; creator_project_info : Additional free text information for the institution that originated this data.<br />
; publisher_uri : The unique identifier of the person responsible for providing the data file or product. <br />
; publisher_institution : The institution that provided the data file or equivalent product; should uniquely identify the institution. <br />
; publisher_institution_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; publisher_project : The scientific project that provided the data file or equivalent product; should uniquely identify the project. <br />
; publisher_project_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; keywords_vocabulary : If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix (e.g., "CF:NetCDF COARDS Climate and Forecast Standard Names") and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key.<br />
; metadata_link : A URI that gives the location of more complete metadata; a URL is recommended.<br />
<br />
== Deprecated ==<br />
<br />
The following terms and definitions are still in the specification, but are no longer recommended for use.<br />
<br />
: Metadata_Convention : (deprecated, supported for backward compatibility with current usage) Reference to the particular metadata convention(s) used for the described data file; recommended practice is to add the metadata convention(s) to the comma-delimited conventions list in the 'Conventions' attribute, per NetCDF Best Practices.<br />
: date_created :deleted in favor of date_product_generated (which used to be date_issued); we did not have a use case for knowing the date a stream or product was _first_ generated, once it has been updated<br />
: date_issued : changed name to date_product_generated<br />
: date_modified : changed name to date_content_modified<br />
<br />
----<br />
<br />
= Additional Materials =<br />
== Mappings ACDD to other metadata dialects ==<br />
[[Attribute Convention for Data Discovery (ACDD) Mappings]]<br />
<br />
== Recommended Order of Precedence ==<br />
[[Attribute Convention for Data Discovery (ACDD) Precedence]]<br />
<br />
== Future Directions: Object Conventions for Data Discovery ==<br />
[[Attribute Convention for Data Discovery (ACDD) Object Conventions]]<br />
<br />
== ISO Translation Notes ==<br />
http://wiki.esipfed.org/index.php?title=Attribute_Convention_for_Data_Discovery_(ACDD)_ISO_TranslationNotes<br />
[[Category:Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_1-2&diff=48571Attribute Convention for Data Discovery 1-22015-01-05T19:32:02Z<p>Graybeal: removed documentation cluster category</p>
<hr />
<div>[[Category: Attribute Conventions Dataset Discovery]]<br />
[[Category: Documentation Cluster]]<br />
<br />
<font color="red">''(This page is in development, is not the 1-2 standard, and should not be used for review.)''</font><br />
<br />
__TOC__<br />
<br />
<br />
== Version and Status ==<br />
<br />
This is version 1.2 of the ACDD convention.<br />
<br />
The target page [[Attribute Convention for Data Discovery]] will always point to the current version of this convention. As the convention is updated, the version number at the top of the page and in the URL will be updated, and the target page will redirect to the most recent version.<br />
<br />
See the [[http://wikiCategory:Attribute_Conventions_Dataset_Discovery category page]] for an overview of this convention and history about its development. <br />
<br />
=== Development ===<br />
<br />
Any development version of the ACDD definitions is maintained can be found at [[Attribute_Convention_for_Data_Discovery_Working]], which redirects to the current working document, if any.<br />
<br />
= Overview =<br />
The NetCDF Group at Unidata has recommended [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html attributes for data discovery] . The Attribute Convention for Data Discovery (ACDD) addresses that need, providing definitions for NetCDF global attributes that will help data to be located efficiently. <br />
<br />
== Alignment with NetCDF and CF Conventions ==<br />
The NetCDF User Guide [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html (NUG)] provides basic recommendations for creating NetCDF files; the NetCDF Climate and Forecast Metadata Conventions [http://cf-pcmdi.llnl.gov/documents/cf-conventions/latest-cf-conventions-document-1/ (CF)] provide more specific guidance. The ACDD builds upon and is compatible with these conventions; it may refine the definition of some terms in those conventions, but does not preclude the use of any attributes defined by the NUG or CF. <br />
<br />
The NUG does not require any global attributes, though it recommends and defines two, title and history; CF specifies many more. ACDD adopts all CF global attributes, with the exception of institution; we specify creator_institution and publisher_institution to allow more information about the data to be included.<br />
<br />
== Attribute Crosswalks == <br />
Many of these attributes correspond to general discovery metadata content, so they are available in many metadata standards. This page includes the [http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html Unidata crosswalk to THREDDS] and adds the crosswalk to ISO 19115-2. Note that the attribute names link to the Unidata definitions. Many of these elements are included in the [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_Core_Elements ISO 19115 Core] specification. They are indicated in this Table by an M, O, or C in parentheses. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions.<br />
<br />
== Additional Metadata: metadata_link attribute ==<br />
<br />
Other metadata dialects (i.e. ISO 19115) can provide information about collections and more details about the dataset. In order to make users aware of that additional metadata we recommend adding a global attribute named "metadata_link" to the netCDF file. The value of this attribute is a URL that gives the location of the more complete metadata. This element is not included in the current version of the NetCDF Attribute Convention for Dataset Discovery.<br />
<br />
== Conformance Test ==<br />
<br />
A [https://geo-ide.noaa.gov/wiki/index.php?title=NetCDF_Attribute_Convention_for_Dataset_Discovery_Conformance_Test Conformance Test] is available for this convention.<br />
<br />
= Global Attributes = <br />
<br />
== Highly Recommended ==<br />
<br />
; title : A short phrase or sentence describing the dataset; this is a NetCDF Users Guide ([http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]) attribute. <br />
; summary : A paragraph describing the dataset, analogous to an abstract for a paper.<br />
; keywords : A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also keywords_vocabulary attribute).<br />
; Conventions : A list of the conventions followed by the dataset; blank space separated is recommended but commas should be used if any convention name contains blanks. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
<br />
== Recommended ==<br />
<br />
; id : An identifier for the data set, provided by and unique within its naming authority. The combination of the "naming authority" and the "id" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include blanks.<br />
; naming_authority : The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute.<br />
; cdm_data_type : The organization of the data, as derived from the Common Data Model's Scientific Data layer and understood by THREDDS (this is a [http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#dataType THREDDS "dataType"]). One of point, profile, section, station, station_profile, trajectory, grid, image, or swath. Please note that this is different from the CF NetCDF attribute 'featureType' that indicates a Discrete Sampling Geometry file - for guidance on those terms, please see [http://www.nodc.noaa.gov/data/formats/netcdf/ this NODC guidance].<br />
; history : Describes the processes/transformations used to create this data; can serve as an audit trail. Per the [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions NUG]: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append an ISO Lineage reference; see [https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Lineage NOAA EDM ISO Lineage guidance]. This attribute is [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-Conventions defined in NUG].<br />
; source : The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; comment : Miscellaneous information about the data, not captured elsewhere. This attribute is [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#description-of-file-contents defined in CF].<br />
; date_content_modified : The date on which any of the provided content, including data, metadata, and presented format, was last changed (ISO 8601 format)<br />
; date_values_modified: The date on which the provided data values were last changed; excludes metadata and formatting changes (ISO 8601 format)<br />
; creator : The name of the person principally responsible for originating this data. <br />
; creator_email : The email address of the person principally responsible for originating this data.<br />
; publisher : The person responsible for the data file or product, with its current metadata and format. <br />
; publisher_email : The email address of the person responsible for the data file or product.<br />
; processing_level : A textual description of the processing (or quality control) level of the data.<br />
; acknowledgement : A place to acknowledge various type of support for the project that produced this data.<br />
; geospatial_bounds : Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the Well-Known Text (WKT) format.<br />
; geospatial_lat_min : Describes a simple lower latitude limit; may be part of a bounding box or cube. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.<br />
; geospatial_lat_max : Describes a simple upper latitude limit; may be part of a bounding box or cube. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.<br />
; geospatial_lon_min : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_min specifies the westernmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_lon_max : Describes a simple longitude limit; may be part of a bounding box or cube. Geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min.<br />
; geospatial_vertical_min : Describes a numerically smaller vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset.<br />
; geospatial_vertical_max : Describes a numerically larger vertical limit; may be part of a bounding box or cube. If geospatial_vertical_positive is up ('altitude' orientation), the geospatial_vertical_min attribute specifies the location furthest from the earth's center covered by the dataset. If geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the location closest to the earth's center covered by the dataset.<br />
; geospatial_vertical_positive : One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum.<br />
; time_coverage_start : Describes the time of the first data point in the data set. ISO8601 format recommended.<br />
; time_coverage_end : Describes the time of the last data point in the data set. ISO8601 format recommended.<br />
; time_coverage_duration : Describes the duration of the data set. ISO8601 duration format recommended.<br />
; time_coverage_resolution : Describes the targeted time period between each value in the data set. ISO8601 duration format recommended.<br />
; license : Provide the URL to a standard or specific license, enter "Freely Distributed" or "None", or describe any restrictions to data access and distribution in free text.<br />
<br />
== Suggested ==<br />
<br />
The following terms and definitions are offered in case they address your situation.<br />
<br />
; contributor_info : The name and role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; date_product_generated : The date on which this data file or product was produced/distributed (ISO 8601 format). While this date is like a file timestamp, the date_content_modified and date_values_modified should be used to assess the age of the contents of the file or product.<br />
; geospatial_lat_units : Units for the latitude axis. These are presumed to be "degree_north"; other options from udunits may be specified instead.<br />
; geospatial_lat_resolution : Information about the targeted spacing of points in latitude. (Format is not prescribed.)<br />
; geospatial_lon_units : Units for the longitude axis. These are presumed to be "degree_east"; other options from udunits may be specified instead.<br />
; geospatial_lon_resolution : Information about the targeted spacing of points in longitude. (Format is not prescribed.)<br />
; geospatial_vertical_units : Units for the vertical axis. These are presumed to be "meter" (of depth); other options from udunits may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar.<br />
; geospatial_vertical_resolution : Information about the targeted vertical spacing of points. <br />
; creator_uri : The unique identifier of the person principally responsible for originating this data. <br />
; creator_institution : The institution that originated this data; should uniquely identify the institution. <br />
; creator_institution_info : Additional free text information for the institution that originated this data.<br />
; creator_project : The scientific project that originated this data; should uniquely identify the project. <br />
; creator_project_info : Additional free text information for the institution that originated this data.<br />
; publisher_uri : The unique identifier of the person responsible for providing the data file or product. <br />
; publisher_institution : The institution that provided the data file or equivalent product; should uniquely identify the institution. <br />
; publisher_institution_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; publisher_project : The scientific project that provided the data file or equivalent product; should uniquely identify the project. <br />
; publisher_project_info : Additional information for the institution that provided the data file or equivalent product; can include any information as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to whitespace).<br />
; keywords_vocabulary : If you are using a controlled vocabulary for the words/phrases in your "keywords" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix (e.g., "CF:NetCDF COARDS Climate and Forecast Standard Names") and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key.<br />
; metadata_link : A URI that gives the location of more complete metadata; a URL is recommended.<br />
<br />
== Deprecated ==<br />
<br />
The following terms and definitions are still in the specification, but are no longer recommended for use.<br />
<br />
; Metadata_Convention : (deprecated, supported for backward compatibility with current usage) Reference to the particular metadata convention(s) used for the described data file; recommended practice is to add the metadata convention(s) to the comma-delimited conventions list in the 'Conventions' attribute, per NetCDF Best Practices.<br />
<br />
----<br />
<br />
= Additional Materials =<br />
<br />
== Mappings of ACDD attributes to other metadata dialects ==<br />
[[Attribute Convention for Data Discovery Mappings]]<br />
<br />
== Recommended Order of Precedence ==<br />
[[Attribute Convention for Data Discovery Precedence]]<br />
<br />
== Future Directions: Object Conventions for Data Discovery ==<br />
[[Attribute Convention for Data Discovery Object Conventions]]<br />
<br />
== ISO Translation Notes ==<br />
[[Attribute Convention for Data Discovery ISO Translation Notes]]<br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_Working&diff=48570Attribute Convention for Data Discovery Working2015-01-05T19:27:42Z<p>Graybeal: updated per 1-3 release</p>
<hr />
<div>#REDIRECT [[Attribute Convention for Data Discovery Future Directions]]<br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]</div>Graybealhttps://wiki.esipfed.org/w/index.php?title=Attribute_Convention_for_Data_Discovery_(ACDD)&diff=48569Attribute Convention for Data Discovery (ACDD)2015-01-05T19:25:32Z<p>Graybeal: updated for latest approved version 1-3</p>
<hr />
<div>#REDIRECT [[Attribute Convention for Data Discovery 1-3]]<br />
<br />
[[Category:Attribute Conventions Dataset Discovery]]</div>Graybeal