1 / 16

GIS to EML Workshop

GIS to EML Workshop. Andrews Experimental Forest November 9-10, 2010. Documenting GIS Data using ArcCatalog (9.3). Andrews Experimental Forest LTER: Spatial Metadata Guide Additional considerations based on best practices of EML

lilah
Download Presentation

GIS to EML Workshop

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GIS to EML Workshop Andrews Experimental Forest November 9-10, 2010

  2. Documenting GIS Data using ArcCatalog (9.3) • Andrews Experimental Forest LTER: Spatial Metadata Guide • Additional considerations based on best practices of EML • (1) Personnel names: Last name, first name (i.e., use a comma to separate last name and first name) and for multiple names and contact elements (phone, fax, e‐mail), use repeating fields. • (2) Attribute definition: Every attribute value needs a corresponding value definition. If the value definition is not available, record the value definition as “unknown”, “none”, or null”.

  3. Working with Data that started as Coverages • Coverage to shapefile or geodatabase • Metadata can contain additional attribute tables • .tic, .prj, .aat, (that you don’t want in your EML file. • Need to check for these and delete

  4. If you add a field or delete a field in your data, it may not be added or deleted in your metadata (need to check)

  5. EML Review • EML Best Practices • ESRI2EML stylesheet • Biological Data Profile EML Crosswalk • Differences between ESRI and FGDC standards • Customizing the ESRI2EML to your site

  6. Documenting Study Site Locations as Part of a Study Database (page 22) • geographicCoverage • The <geographicCoverage> element is used to describe geographic locations of research sites and areas related to the dataset. It is recommended to use the element at different levels for different types of information.

  7. At the dataset level (eml:eml/dataset/coverage) one <geographicCoverage> element should be included, whose <boundingCoordinates> describe the extent of the data. As a default, the bounding box could describe the entire LTER site as stored in SiteDB. However, it is strongly recommended that a more accurate extent of observations be provided, i.e., the maximum extent of the data, for each of east, west, north and south. Additional <geographicCoverage> elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box, For example, cross site studies where a bounding box would represent North American or more should have two bounding boxes, one for each site. • Use eml:eml/dataset/methods/sampling/spatialSamplingUnits/coverage, to give more specific information if necessary, e.g. to describe the specific geographic areas sampled as a list of individual areas or single points. In the case of a study in which the measurements from several disbursed point‐collection devices are aggregated, then the sampling unit would be the area of that aggregation. More information about sampling sites can be found under <methods>,

  8. There are alternative methods for including location information with EML, especially when it is intended for use in an external application. These include GIS shapefiles, Keyhole Markup Language (KML or KMZ), or EML spatial modules. For more information, see Section III, Recommendations for Compatibility with External Applications. • Latitudes and longitudes should be in the same commonly used datum (i.e., all values in WGS84 or NAD83) and expressed to at least six decimal places (the EML2.1 schema enforces decimal content). International convention dictates that longitudes east of the prime meridian and latitudes north of the equator be prefixed with a plus sign (+), or by the absence of a minus sign (‐), and that west longitudes and south latitudes be prefixed with minus sign (‐).

  9. Examples • EML best practices • Completed ESRI metadata • EML • Examples from CAP

  10. EML Best Practices

  11. Version 10 of ArcGIS Called Description (not metadata) in tab Need to convert FGDC metadata to ESRI metadata Nice editor, but bombs sometimes Need to change default settings. Tasks: Import, edit We need a new stylesheet as the tags have changed.

  12. Recommendations to EML on Spatial Data

  13. LTER GIS Standards Recommendations 1. Results of survey *Suzanne 2. LTERmapS plans 3. Create “Documenting GIS to EML standard for LTER sites” guide

  14. Breakout Sessions: 1. LTERmapS subgroup working session 2. Continue working on Documentation of Site Data 3. Develop “Documenting GIS to EML standard for LTER sites” guide 4. Other

  15. LTERmapS ESRI group

  16. Group Summaries (if needed) Next Steps Assignments Documents on-line Check out

More Related