1 / 40

Community Building and Collaborative Georeferencing using GEOLocate

Community Building and Collaborative Georeferencing using GEOLocate. Nelson E. Rios & Henry L. Bart Jr. Tulane University Museum of Natural History. What is Georeferencing.

callie
Download Presentation

Community Building and Collaborative Georeferencing using GEOLocate

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. Community Building and Collaborative Georeferencing using GEOLocate Nelson E. Rios & Henry L. Bart Jr. Tulane University Museum of Natural History

  2. What is Georeferencing • As applied to natural history collection data it is the process of assigning geographic coordinates to a textually described collecting event • Traditional approaches laborious and time consuming • Automated and collaborative processes have proven to improve efficiency

  3. GEOLocate Overview Desktop application for automated georeferencing of natural history collections data Initial release in 2002 Locality description analysis, coordinate generation, batch processing, geographic visualization, data correction and error determination

  4. Overview: Locality Visualization & Adjustment Computed coordinates are displayed on digital maps Manual verification of each record Drag and drop correction of records

  5. Overview:Multiple Result Handling Caused by duplicate names, multiple names & multiple displacements Results are ranked and most “accurate” result is recorded and used as primary result All results are recorded and displayed as red arrows Working on using specimen data to limit spread of results

  6. Overview:Estimating Error User-defined maximum extent described as a polygon that a given locality description can represent Recorded as a comma delimited array of vertices using latitude and longitude

  7. Current Lines of Development • “Taxonomic Footprints” • Collaborative georeferencing • Global expansion • Multilingual georeferencing with user-defined locality grammar

  8. Taxonomic Footprint Validation Uses point occurrence data from distributed museum databases to validate georeferenced data Taxa collected for a given locality Species A Species B

  9. Lepomis macrochirus Lepomiscyanellus Cottus carolinae Hypentelium etowanum Notropis chrosomus Micropterus coosae Notropis volucellus Etheostoma ramseyi Footprint for specimens collected at Little Schultz Creek, off Co. Rd. 26 (Schultz Spring Road), approx. 5 mi N of Centreville; Bibb County; White circles indicate results from automated georeferencing. Black circle indicates actual collection locality based on GPS. This sample was conducted using data from UAIC & TUMNH

  10. Collaborative Georeferencing • Distributed community effort increases efficiency • Web based portal used to manage each community • DiGIR used for data input (alternatives in development) • Similar records from various institutions can be flagged and georeferenced at once • Data returned to individual institutions via portal download as a comma delimited file

  11. Collaborative Georeferencing

  12. Global Georeferencing • Typically 1:1,000,000 • Will work with users to improve resolution (examples: Australia250K & Spain200K) • Advanced features such as waterbody matching bridge crossing detection possible but requires extensive data compilation (example: Spain)

  13. Multilingual Georeferencing • Extensible architecture for adding languages via language libraries • Language libraries are text files that define various locality types in a given language • Current support for: • Spanish • Basque • Catalan • Galician • May also be used to define custom locality types in English

  14. Future Directions • Collaboration with foreign participants to improve datasets and language libraries • Cross platform Java client • More web services integration • Integration of WFS & WMS for mapping • Alternatives to DiGIR

  15. Final Thoughts • Approximately 20% of DiGIR providers (excluding fish collections) tested have problems of stability and/or data quality resulting in the inability to cache records. • Typical data quality issues: • Malformed data (common in “datelastmodified”) • Catalog numbers missing and/or duplicated • Resolution requires dedicated infrastructure for data providers or alternative means of serving data.

  16. Acknowledgements Djihbrihou Abibou Andy Bentley Shwetha Belame Paul Flemons Demin Hu Sophie Hung John Johanson David Draper Munt Dave Vieglais Ed Wiley National Science Foundation

More Related