fgdc meet the ddi adding geospatial metadata to a numeric data catalog n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
FGDC, Meet the DDI Adding Geospatial Metadata to a Numeric Data Catalog PowerPoint Presentation
Download Presentation
FGDC, Meet the DDI Adding Geospatial Metadata to a Numeric Data Catalog

Loading in 2 Seconds...

play fullscreen
1 / 15

FGDC, Meet the DDI Adding Geospatial Metadata to a Numeric Data Catalog - PowerPoint PPT Presentation


  • 90 Views
  • Uploaded on

FGDC, Meet the DDI Adding Geospatial Metadata to a Numeric Data Catalog. Julie Linden Yale University. Outline. StatCat: numeric data catalog Why add geospatial metadata? FGDC/DDI crosswalk Implementation. StatCat. ssrs.yale.edu/statcat/

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

FGDC, Meet the DDI Adding Geospatial Metadata to a Numeric Data Catalog


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. FGDC, Meet the DDIAdding Geospatial Metadata to a Numeric Data Catalog Julie Linden Yale University

    2. Outline • StatCat: numeric data catalog • Why add geospatial metadata? • FGDC/DDI crosswalk • Implementation Please do not cite or copy without permission.

    3. StatCat • ssrs.yale.edu/statcat/ • Partnership between Social Science Library and Social Science Research Services • Records for Yale’s Social Science Data Archive, CDs, subscription databases, Internet sources • Subset of DDI elements in relational database Please do not cite or copy without permission.

    4. Why add geospatial metadata • Use of GIS increasing at Yale • Current searching for geospatial data is inadequate • GIS and data searches closely tied • Existing GIS metadata could be imported • FGDC standard for geospatial metadata Please do not cite or copy without permission.

    5. Interface goals • Could restrict search to numeric, geospatial, or both types of data • Eventually can link directly from StatCat record to datasets on server Please do not cite or copy without permission.

    6. Data Documentation Initiative • Document description • Study description • Data files description • Variable description • Other study-related materials Please do not cite or copy without permission.

    7. StatCat database design (with DDI element numbers) Please do not cite or copy without permission.

    8. Geospatial metadata standard • Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata: http://www.fgdc.gov/metadata/csdgm/ • ESRI Profile: http://www.esri.com/metadata/esriprof80.html Please do not cite or copy without permission.

    9. FGDC CSGDM • Metadata • Identification Information • Data Quality Information • Spatial Data Organization Information • Spatial Reference Information • Entity and Attribute Information • Distribution Information • Metadata Reference Information • Citation Information • Time Period Information • Contact Information Please do not cite or copy without permission.

    10. FGDC, meet the DDI • Compared FGDC/ESRI elements to our DDI subset to see what obviously mapped • How would FGDC structure map to StatCat database structure? • FGDC doesn’t treat “files” the same way as the DDI or StatCat • “Entity and attribute” information didn’t map to “variables.” Please do not cite or copy without permission.

    11. Brief detour into XML… • XML is good at: • Describing hierarchical data • Exchanging data between independent sites in a highly structured manner • Since both standards are in XML, why not present XML records rather than to select elements from each for inclusion in common database? Please do not cite or copy without permission.

    12. …and back to original plan • Decided to go with database • Amount of time it would take to start from scratch would greatly delay inclusion of geospatial metadata • FGDC and DDI elements did not have to correspond exactly; just needed a minimum set of elements to facilitate data discovery and evaluation. Please do not cite or copy without permission.

    13. Database modifications • Included some FGDC elements that had no DDI equivalent: • bounding coordinates • “type” – to distinguish (and thus search on) geospatial and numeric data • Added “Data Sources” and “Record Information” tables • New database design Please do not cite or copy without permission.

    14. Near-term next steps • Updating database tables • Writing parser to import records • Redesign search interface and results screens Please do not cite or copy without permission.

    15. Long-term next steps • Link study description to live data sets, including documentation and software setups. • Interoperability among catalogs • Spatial queries • Variables table • Geodatabases Please do not cite or copy without permission.