1. FGDC Metadata and the Biological Data Profile Anchorage, AK January 25, 2006 Terry Giles IAPWWS @ USGS-FORT terry_giles@usgs.gov (970) 226-9425

2. Metadata Workshop Topics  Metadata: what it is, why you need it, and how to write good metadata.  U.S. Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM) and the Biological Data Profile.  Implementation: decisions, challenges, and resources.  Tools and resources for metadata creation and management.

3. Trainer’s Goals  Everyone learn / meet your goals for the class  Experience that metadata isn’t that scary  Have fun!

4. Introduction: What are Metadata?  Definitions  Examples  Types of information included

5. Introduction: What Are Metadata?  In your own words – what does “metadata mean to you?  Metadata are literally “data about data” - they describe the content, quality, condition, and other characteristics of the data.

6. Metadata in the Real World  What are some everyday examples of “metadata”?  Examples: food product labels, library records, information on a video or DVD, published maps, etc., etc., etc.

7. Working With Data provide  When you provide data to someone else, what types of information would you want to include with the data? receive  When you receive a dataset from an external source, what types of information do you want to know about the data?

8. Metadata describes the Who, What, Where, Why, and How  Who created and maintains the data?  Why were the data created?  What is the content and structure of the data?  When collected? When published?  Where is the geographic location? Storage location?  How were the data produced?

9. Mining Existing Resources  Metadata is not a new or alien concept.  We all have a strong history of documenting methodology, describing appropriate uses of the data, and writing summaries about data completeness and currentness.  What existing documentation (i.e. metadata) materials do you have in your program / office?

10. Examples of existing “data about data” materials:  Methodology documentation  Database help records  BASIS+ project/task entries  Data sharing and licensing agreements  Project agreement, documentation and reports  Data requests – data use guidelines

11. The Key Point: All of us have personal experience with creating metadata.

12. The Value of Metadata  Data developers  Data users  Organizations

13. Value to Data Developers?  Avoid duplication  Share reliable information  Publicize efforts  Reduce workload  Documenting data is critical to preserving its usefulness over time; without proper documentation, no data set is complete

14. Value to Data Users?  Search, retrieve, and evaluate data set information both inside and outside organizations  Finding data - determine which data exist for a geographic location and/or topic  Applicability - determine if a dataset meets your needs  Access and transfer - acquire the dataset you identified, process and use the dataset

15. Value to Organizations?  Organizes and maintains an organization’s investment in data  Documentation of data processing steps, quality control, definitions, data uses and restrictions, etc.  Transcends people and time; offers data permanence and creates institutional memory  Saves time, money, frustration

16. Value to Organizations?  “Advertising”: Provide information about datasets to data catalogs and clearinghouses  External data sharing and data transfer: Provide information that is critical for others to understand and correctly use your data  Helps share data with other agencies, lead to potential partnerships

17. Value to All: Data developers Data users Organizations Metadatahelps…

18. What’s new about metadata (i.e. why are we here today)? Creating and managing metadata standardized in a standardized format using a common set of terms.

19. Why Have a Metadata Standard?

20. Why Have a Standard? Helps you determine:  If a set of data is available and fit for your use  How to access and transfer the data set

21. Why Have a Standard? Helps to create:  Common terms  Common definitions  Common language  Common structure

22. Why Have a Standard?  Establishes names of metadata elements and compound elements  Defines information about values provided for metadata elements  The standard serves as a uniform summary description of the data set  Online systems rely on documentation being predictable in form and content

23. The Key to Using the Standard…  If you’re creating metadata for the first time, it may seem complex - stick with it  Don’t create your own version of the standard - you’ll only confuse people  Find the fields that are pertinent to your data and your organization’s needs  Build a template; use the template  Ask questions!

24. Establishment of U.S. Metadata Standards

25. Executive Order 12906 (1994)  Defines the responsibilities of the Federal Geographic Data Committee (FGDC)  Requires that metadata be available to the public  Requires creation of metadata for data sets from 1995 forward

26. FGDC’s Responsibilities Federal Geographic Data Committee (FGDC) is responsible for coordinating: development of National Spatial Data Infrastructure establishment of National Geospatial Data Clearinghouse development of standards cooperative efforts with State, Local, and tribal governments, and private sector implementation of digital geospatial data framework

27. Executive Order 12906 Federal Agencies responsible for: standardized documentation of all new data collected or produced beginning in January 1995 plans to document data previously collected or produced (legacy data) to the “extent practicable” making metadata and data available to the public utilize Clearinghouse to determine if data has already been collected or cooperative efforts are possible

28. FGDC Profiles and Extensions Extension: extended elements to the standard are elements outside the standard but needed by the data set producer Profile: document that describes the application of the Standard to a specific community Examples: Biological Data Profile, Shoreline Data Profile, Remote Sensing Extensions

29. Biological Data Profile: Defines Additional Elements  Taxonomy  Methodology  Analytical tools

30. Biological Data Profile: Documents three types of data sets  Explicitly biological  Biological and geospatial  Explicitly geospatial

31.  National Research Council recommended in 1994 the establishment of a National Biotic Resource Information System to coordinate distributed databases and disseminate new data and information ~ NBII  NBII established a federation of biological information sources and tools to help users find biological information and to combine information from various sources.  NBII has a biological information focus, on both geospatial and non-geospatial data.

32. International Organization for Standardization (ISO) Metadata Standard  ISO 19115 has been approved - an abstract standard that specifies general content for the metadata, but does not specify the format.  ISO 19139 is under development - XML implementation schema specifying the metadata record format.  The FGDC is developing metadata content for the U.S. National Profile of ISO 19139.

33. International Organization for Standardization (ISO) Metadata Standard  ISO not yet the official U.S. metadata standard (important if need to provide FGDC-compliant metadata!).  Software tools under development.  Metadata created before the release of the ISO standard will not need to be altered.  Updates and more information: http://www.fgdc.gov/metadata/whatsnew/fgdciso.html http://www.fgdc.gov/metadata/whatsnew/fgdciso.html

34. Other Metadata Standards  Ecological Metadata Language (EML) Used for the Long-term Studies Section (LTSS) publicly accessible registry describing scientific data sets on ecology and the environment. http://knb.ecoinformatics.org/software/eml/ http://knb.ecoinformatics.org/knb/style/skins/ltss/index.html  Darwin Core Used for the Global Biodiversity Information Facility (GBIF) portal of collection and observation data. http://darwincore.calacademy.org/ http://www.gbif.org/

35. The FGDC CSDGM Standard and the Biological Data Profile  What the CSDGM Standard and the Biological Data Profile are  Details about the Sections and Terms of the Standard

36. Biological Data Profile Workbook

37. FGDC metadata standard: overview Seven Major Metadata Sections: Section 1 - Identification Information* Section 2 - Data Quality Information Section 3 - Spatial Data Information Section 4 - Spatial Reference Information Section 5 - Entity and Attribute Information Section 6 - Distribution Information Section 7 - Metadata Information* Three Supporting Sections: Section 8 - Citation Information* Section 9 - Time Period Information* Section 10 - Contact Information* * Minimum required metadata

38. FGDC Metadata Standard: All the Details FGDC Metadata Standards: http://www.fgdc.gov/standards/status/textstatus.html Content Standard for Digital Geospatial Metadata (CSDGM) (version 2.0), FGDC-STD-001-1998 http://www.fgdc.gov/metadata/contstan.html Content Standard for Digital Geospatial Metadata, Part 1: Biological Data Profile, FGDC-STD-001.1-1999 (Note: The FGDC biological data profile is sometimes also referred to as the “NBII extension”) http://www.fgdc.gov/standards/status/sub5_2.html

39. FGDC Metadata Workbook & Graphic Representations Primary FGDC digital geospatial metadata standard http://fgdc.gov/metadata/meta_workbook.html http://biology.usgs.gov/fgdc.metadata/version2/ FGDC metadata including the Biological Data Profile http://www.nbii.gov/datainfo/metadata/standards/BDP- workbook.doc http://www.nbii.gov/datainfo/metadata/standards/bdp.html

40. 1.2.1Abstract - a brief narrative summary of the data set. Type: Text Domain: free text FGDC Metadata Element Data ElementDefinition Choice of integer, real, text, date Valid values that can be assigned or “free text”, “free date”, or “free time” Element number

41. FGDC Graphic Representation color symbology A tool to visually describe the structure of the metadata standard; depicting information, organization, reporting requirements, and structure of the standard through the use of color and the relationship of information through the use of symbology. http://biology.usgs.gov/fgdc.metadata/version2/ http://www.nbii.gov/datainfo/metadata/standards/bdp.html

42. Graphical Representation of the Elements Section 10/06/95 Data Elements (raised 3-d boxes) Compound Elements (not raised)

43. How Are Elements Grouped? Compound elements are composed of other compound or data elements. The composition is represented by nested boxes. Compound Element 1 Compound Element 1.1 Data Element 1.1.1 Data Element 1.1.2 Data Element 1.2 10/06/95

44. If an element can be repeated independently from other elements, a label below the element name states how many times the element may be repeated. If there is no label, the element does not repeat independently from other elements. What Can Repeat? How Many Times? Compound Element 1 (can be repeated unlimited times) Compound Element 1.1 Data Element 1.1.1 Data Element 1.1.2 Data Element 1.2 10/06/95

45. What’s Mandatory? What’s Not? Mandatory if applicable: Mandatory if applicable: must be provided if the data set exhibits the defined characteristic Meaning Data Element Compound Element Mandatory: Mandatory: must be provided Optional: Optional: provided at the discretion of the data producer Biological Data Profile yellowgreenbluered outline and text Biological Data Profile elements (yellow, green, or blue with red outline and text).

46. Navigating the FGDC Standard Status Progress Maintenance and Update Frequency 10/06/95 Attribute Accuracy Quantitative Attribute Accuracy Assessment Attribute Accuracy Value Attribute Accuracy Explanation Attribute Accuracy Report Mandatory if Applicable Optional Keywords Theme (can be repeated unlimited times) Theme Keyword Thesaurus Theme Keyword (can be repeated...) Place (can be repeated unlimited times) Place Keyword Thesaurus Place Keyword (can be repeated...)

47. How Do You Write Good Metadata? Rules and Tips for Creating Quality Metadata Files

48. Good Metadata: Steps to Quality Metadata  Organize your information  Write your metadata  Review for accuracy and completeness  Have someone else read your file  Revise it, based on comments from your reviewer  Review it once more before you publish it

49.  Write simply but completely  Document for a general audience  Be consistent in style and terminology Good Metadata: Keep your readers in mind

50. Good Metadata: Think about the long-term effects  Don’t use jargon  Define technical terms and acronyms: CA, LA, GPS, GIS  Clearly state data limitations  Don’t use ALL CAPITAL LETTERS  Use subheadings and/or bulleted lists  Cite examples  Use “none” or “unknown” meaningfully

51. Good Metadata: The Title  Critical in helping readers find your data.  A complete title includes: What, Where, When, Scale, Who  An informative title includes: Topic, Timeliness of the data, Specific information about place and geography

52. Good Metadata: The Title If the data are officially published, in the title include:  Series name  Issue number  Name of publisher  Location of publisher

53. Good Metadata: The Title  Which is better? Rivers Greater Yellowstone Rivers from 1:126,700 Forest Visitor Maps (1961-1983)  Examples of useful titles: Near Real Time Advanced Very High Resolution Radiometer (AVHRR) Data-Satellite Imagery from NOAA CSC Coastal Remote Sensing Division Ace Basin, South Carolina National Estuarine Research Reserve Digital Line Boundary

54. Vague: We checked our work and it looks complete. Specific:We checked our work using 3 separate sets of check plots reviewed by 2 different people. We determined our work to be 95% complete based on these visual inspections. Good Metadata: Be Specific, Quantify when you can

55.  Use unambiguous words  Use descriptive words  Fully qualify geographic locations – where is ‘Portland’? Good Metadata: Select keywords wisely

56.  Don’t use symbols that might be misinterpreted ! @ # % { } | / \ ~  Don’t use characters with dual interpretations  Don’t use tabs or indents  Be careful with the use of carriage returns  Use “none” or “unknown” meaningfully Good Metadata: Remember, a computer will read your metadata

57.  Have someone else read it  If you’re the only reviewer, put it away and read it again later  Check for clarity and omissions  Can a novice understand what you wrote?  Are your data properly documented for posterity? Good Metadata: Review your final product

58.  Does the documentation present all the information needed to use or reuse the data?  Are any pieces missing? Good Metadata: Review your final product

59. Taking a Closer Look: FGDC Metadata – Section by Section

61. Originator 8.1Originator name of an organization / individual that developed data set Publication Date 8.2Publication Date Publication Time 8.3Publication Time Title 8.4Title Edition 8.5Edition Geospatial Presentation Form BDP8.6 Geospatial Presentation Form Supporting Section 8: Citation Information

62. Series Information 8.7Series Information Publication Information 8.8Publication Information Place and Publisher Other Citation Details 8.9Other Citation Details Online Linkage 8.10Online Linkage online resource for the dataset – a URL Larger Work Citation 8.11Larger Work Citation Supporting Section 8: Citation Information

63. Single Date 9.1Single Date OR Multiple Date(s) 9.2Multiple Date(s) OR Range of Date(s) 9.3Range of Date(s) BDP allows use of Geologic Age information for the Time Period Supporting Section 9: Time Period Information

64. Contact Person Primary 10.1Contact Person Primary OR Contact Organization Primary 10.2Contact Organization Primary Contact Position 10.3Contact Position title of individual Contact Address 10.4Contact Address Minimal: type, city, state / province, postal code Contact Voice Telephone 10.5Contact Voice Telephone Supporting Section 10: Contact Information

65. Contact TDD/TTY Telephone 10.6Contact TDD/TTY Telephone Contact Facsimile Telephone 10.7Contact Facsimile Telephone Contact Electronic Mail Address 10.8Contact Electronic Mail Address Hours of Service 10.9Hours of Service Contact Instructions 10.10 Contact Instructions supplemental instructions on how or when to contact the Contact Person or Organization Supporting Section 10: Contact Information

67. Citation 1.1Citation Originator, Publication Date, Title Description 1.2Description Abstract and Purpose Time Period of Content 1.3Time Period of Content Date(s) and Currentness Reference Status 1.4Status Progress and Maintenance Spatial Domain 1.5Spatial Domain Description of Geographic Extent; N, S, E, and W bounds Section 1: Identification Information

68. Keywords 1.6Keywords Theme Thesaurus and Keyword Taxonomy BDP1.7 Taxonomy Thesaurus, Keywords, Classification System, Procedures, Taxonomic Classification: rank and value Access Constraints 1.7Access Constraints restrictions and legal prerequisites for accessing the data; including protection of privacy or intellectual property Use Constraints 1.8Use Constraints restrictions for using the data set after access is granted Point of Contact 1.9Point of Contact Section 1: Identification Information

69. Browse Graphic 1.10Browse Graphic Data Set Credit 1.11 Data Set Credit recognition of those who contributed to the data set Security Information 1.12Security Information Native Data Set Environment 1.13Native Data Set Environment software used to create / analyze / export the dataset Cross Reference 1.14Cross Reference other, related data sets that are likely to be of interest Analytical Tool BDP1.15Analytical Tool tools, models, or statistical procedures

71. Attribute Accuracy 2.1Attribute Accuracy Logical Consistency Report 2.2Logical Consistency Report Completeness Report 2.3Completeness Report Positional Accuracy 2.4Positional Accuracy Horizontal and Vertical Lineage 2.5Lineage Methods used; Sources used; and Process Step Cloud Cover 2.6Cloud Cover Section 2: Data Quality Information

72. Section 2.5 Lineage: Taking a closer look The lineage and process step metadata elements

73. What do these have in common?

74. What do the terms “lineage” and “process step” mean to you?

75. Section 2.5 Lineage: Definition  “Information about the events, parameters, and source data which constructed the data set, and information about the responsible parties.”  What were the ingredients (source data)?  How were they combined (process steps)?  Who did the work (contact)?

76. Mandatory M if Applicable Optional What were the ingredients (source data)?

77. How were they combined (process steps)? Mandatory M if Applicable Optional

78. Who did the work (contact)? Mandatory M if Applicable Optional

79. Section 2.5 Data Lineage and Process  Who would use this type of information?  What is its value?

81. Indirect Spatial Reference 3.1Indirect Spatial Reference Direct Spatial Reference Method 3.2Direct Spatial Reference Method Point and Vector Object Information 3.3Point and Vector Object Information Type, Topology level, Count OR Raster Object Information 3.4Raster Object Information Type, Count Section 3: Spatial Data Organization Information

83. Horizontal Coordinate System Definition 4.1Horizontal Coordinate System Definition Geographic 4.1.1Geographic OR Planar 4.1.2Planar OR 4.1.2.1Map Projection OR 4.1.2.2Grid Coordinate System OR 4.2.2.3Local Planar Local 4.1.3 Local Geodetic Model 4.1.4Geodetic Model Vertical Coordinate System 4.2Vertical Coordinate System 4.2.1Altitude System Definition 4.2.2Depth System Definition Section 4: Spatial Reference Information

85. Detailed Description 5.1Detailed Description 5.1.1 Entity Type label, description & source for dataset features 5.1.2 Attributes label (field name), field definition, definition source (authority ~ USGS, FIPS, etc.), and domain values / valid values AND/OR Section 5: Entity and Attribute Information

86. AND/OR Overview Description 5.2Overview Description 5.2.1Entity and Attribute Overview detailed summary of the information contained in a data set 5.2.2Entity and Attribute Detail Citation reference to the complete description of the entity types, attributes, and attribute values for the data set Section 5: Entity and Attribute Information

87.  Enumerated Domain: list of possible values (conservation status ranks, domain tables)  Range Domain: numeric values between limits (lat / long)  Codeset Domain: values defined by a set of codes (FIPS codes, Quad codes, HUC codes, USESA values)  Unrepresentable Domain: values not in a known predefined set (any text or comment field, common names) Section 5: Attribute Domain Values

89. Distributor 6.1Distributor Contact information for obtaining the data set Resource Description 6.2Resource Description Internal identifier such as a dataset name or code Distribution Liability 6.3Distribution Liability Liability statement regarding the data set Standard Order Process 6.4Standard Order Process general data request process, instructions, and fees Custom Order Process 6.5Custom Order Process Technical Prerequisites 6.6Technical Prerequisites Available Time Period 6.7Available Time Period Section 6: Distribution Information

91. Metadata Date 7.1Metadata Date date metadata created or last reviewed Metadata Review Date 7.2Metadata Review Date Metadata Future Review Date 7.3Metadata Future Review Date Metadata Contact 7.4Metadata Contact person or organization responsible for metadata content Metadata Standard Name 7.5Metadata Standard Name Metadata Standard Version 7.6Metadata Standard Version Section 7: Metadata Information

92. Metadata Time Convention 7.7Metadata Time Convention Metadata Access Constraints 7.8Metadata Access Constraints Metadata Use Constraints 7.9Metadata Use Constraints Metadata Security Information 7.10Metadata Security Information Metadata Extensions 7.11Metadata Extensions Example: Biological Data Profile Section 7: Metadata Information

93. Implementation – Where Do You Go From Here?

94. Implementation Decisions: Overview  Getting support for metadata development?  What is a “data set?” What needs metadata?  When is the best time to collect metadata?  When should you document legacy data?  Who is the metadata being created for? For what purpose? External - Clearinghouse, Projects, Internet Internal - Data Library, Archives  Who should create the metadata? Single individual or team approach  What metadata creation tools?

95. Getting Support: The Value of Metadata is Organization Wide  Saves time, money, frustration  Preserve institutional memory and investment in data; written documentation rather than in one person’s brain  Partnerships and “advertising” data collections, help share reliable information  Efficiency – identify and use existing datasets, avoid duplication of effort  Gives the data set creator(s) credit

96. Funding Metadata Development  Internal funding options?  External - include as project deliverable / scope of work, therefore included in the project budget!

97. Deciding what data sets need metadata?  Dataset definitions: EO 12906, FGDC, NBII  Historical data: NSDI “Guide for Federal Agencies”  Prioritize data sets: Mission critical, High demand, Projects, Web downloadable, Legacy, Others?  Data inventory: Format, Resolution, Contacts, Geographic locations, etc  General rule of thumb: The “what if Joe Scientist gets hit by a bus tomorrow?” test

98. Who contributes to creating a metadata file? Single individual or team approach?  Team Leader / Project Manager  GIS Specialist  Field Personnel  Database Manager  Science Staff  Data Analysis Lead

99. More Metadata Training & Info  FGDC metadata trainer directory  FGDC metadata training calendar http://www.fgdc.gov/metadata/education.html  NBII metadata training program http://www.nbii.gov/datainfo/metadata/training/index.html  Other Training Materials http://www.csc.noaa.gov/metadata/  Email list http://lists.geocomm.com/mailman/listinfo/metadata

100. Metadata Resources on the Web  Federal Geographic Data Committee (FGDC): http://www.fgdc.gov/metadata/metadata.html http://fgdc.gov/metadata/meta_workbook.html http://biology.usgs.gov/fgdc.metadata/version2/  National Biological Information Infrastructure (NBII) / Biological Data Profile: http://www.nbii.gov/datainfo/metadata/ http://www.nbii.gov/datainfo/metadata/standards/BDP-workbook.doc http://www.nbii.gov/datainfo/metadata/standards/bdp.html  USGS metadata resource page (includes factsheets, FAQs, MP validation tool): http://geology.usgs.gov/tools/metadata/

101. Metadata Tools and Resources

102. Metadata Creation Tools Software Name Spatial Capture TemplatesBDPPrice ArcCatalog (ArcGIS 8.x) YESImport existing metadata, Advanced Synchronization tools NOPart of ArcGIS 8.x ArcView 3.x Extensions YESStores as.dbf files; can be reused as a “template” NOExtensions are free MetavistNOStores as XML files; can start with existing metadata to use as a template YESFree SMMSYESYES – creates whole record templates, and citations & contacts YES~ $600 TKMENOStart with existing metadata record to use as a template YESFree

103. Metadata Creation Tools Summary and review of a variety of metadata software tools: http://www.sco.wisc.edu/wisclinc/metatool/index.html http://www.fgdc.gov/metadata/toollist/metatools797.html Check back periodically – these review sites are updated on an ongoing basis!

104. Metadata Validation Tools CNS - “Chew-n-Spit” Pre-parser to prepare for using “MP” (probably not needed if using tool such as ArcCatalog ) http://geology.usgs.gov/tools/metadata/tools/doc/cns.html MP - “Metadata Parser” Validation that metadata are FGDC compliant; critical if posting metadata to an online clearinghouse http://geology.usgs.gov/tools/metadata/tools/doc/mp.html

105. CNS: “Chew-n-Spit” Pre-parser  Metadata formatting tool  Pre-parser for formal metadata to convert records that cannot be parsed by MP into records that can be parsed by MP  Uses ASCII text files from metadata creation tool  Not all ASCII text files require CNS prior to using MP Metadata Tool CNS review to MP

106. MP: Metadata Parser  Metadata quality control and output configuration tool  Compiler to parse formal metadata  Checks the syntax against the FGDC standard (including the Biological Data Profile)  Checks structure and values of elements  Generates output suitable for viewing with a web browser or text editor (can create.html,.sgml,.diff, and.xml files for serving on the clearinghouse or the Internet)  Reads ASCII text, XML, or SGML files

107. MP: Correcting Errors  All errors must be fixed in the original metadata record (and then re-run through MP)  Errors are labeled with numbers - how can you find out where they are? Open a DOS window and edit the file c:\metanbii\cns_out.txt (the edit feature contains line numbers) OR View CNS output “cns_out.txt” in and use “Find” feature of WordPad to locate error

108. Metadata Process Summary Final Output MP Correct Errors Output to MP Metadata Tool Clearinghouse

109. Metadata software – a closer look

110. ArcCatalog (ArcGIS 8.x or 9.x)

111. ArcCatalog: Metadata Options

112. ArcCatalog (ArcGIS 8.x or 9.x)  Advanced tools and customizations (such as specifying which parts of the metadata record to automatically update) can be downloaded from the ESRI ArcObjects website: http://arcobjectsonline.esri.com/  Select “Samples”, “Metadata”, “Tools”, see “Advanced Synchronization” or “Set Synchronized Properties”

113. ArcCatalog: Advanced Synchronization

114. ArcCatalog: Set Synchronized Properties

115. ArcCatalog with NPS NBII Extension

116. ArcView 3.x Extension: Metadata Collector v2.0

117. Metavist 2005 http://ncrs.fs.fed.us/pubs/viewpub.asp?key=2737

118. Metavist 2005 Information Author:David Rugg, USFS Vendor:USDA Forest Service, North Central Research Station Platform needed:Microsoft Windows 2000 or XP, with the Microsoft.Net Framework version 1.1. Metadata stored as:XML files Software license:NOT required Software updates:Software new, not known Cost:FREE Request a copy:http://ncrs.fs.fed.us/pubs/viewpub.asp?key=2737

119. Metavist 2005 Software Features  Creates FGDC compliant metadata, including the Biological Data Profile for the FGDC standard.  Covers all FGDC elements plus Biological Data Profile elements (Taxonomy, Methodology, and Analytical Tools).  Geospatial metadata elements NOT automatically collected from GIS data layers.  Metadata stored / output in XML format.  Import existing metadata file (must be XML file with proper formatting).  Template – create a partial record with template components, import to start a new metadata record.

120. Spatial Metadata Management System (SMMS)

121. TKME “Another editor for formal metadata”

122. Metadata Clearinghouses: Sharing and Discovery

123. Metadata clearinghouses  A metadata clearinghouse is a location — typically accessed through the Internet — to search for spatial data sets  Clearinghouses make metadata records easy to find

124. Clearinghouse examples  FGDC Geospatial Data Clearinghouse http://www.fgdc.gov/clearinghouse/clearinghouse.html  Montana State Library Natural Resource Information System GIS http://nris.state.mt.us/gis/  Nebraska Geospatial Data Clearinghouse http://www.dnr.state.ne.us/databank/geospatial.html  Wisconsin Land Information Clearinghouse http://www.sco.wisc.edu/wisclinc/

125. National Geospatial Data Clearinghouse (NGDC)  Has the people and infrastructure to help you find out who has what geographic information.  Set of information services that use hardware, software, and telecommunications networks to provide searchable access to information.  Includes federal, state, university, and vendor participants in the United States and abroad.  User can search all or part of the community in a single session

128. NBII Clearinghouse http://metadata.nbii.gov/ http://metadata.nbii.gov/