Georeferencing Workshop

1. Georeferencing Workshop University of the Western CapeCape Town, South Africa 04-08 Feb 2011

2. GEOLocate – Automated Georeferencing Initially funded in 2002 Software & services for georeferencing of natural history collections data locality description analysis coordinate generation data correction kml export multilingual batch processing interoperable soap & rest api geographic visualization error determination google, bing, openstreet, wms collaborative georeferencing

4. Basic Georeferencing Process • Data Input • Data Correction • Manual or file based data entry • Coordinate Generation • Locality description parsing and analysis • Coordinate Adjustment • Fine tuning the results on a visual map display • Error Determination • Assigning a maximum possible extent for a given locality description

5. Coordinate Generation Pipeline Standardize Locality String Highway Name and Water body Name Query & Analysis TRS Query & Analysis Navigable Waterway Query & Analysis Placenames Query & Analysis Water Body Query & Snapping

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

7. 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

8. Example

9. When a point just isn’t good enough… Eagle Lake, Warren County,Mississippi, USA

10. Polygons within GEOLocate User-defined maximum extent described as a polygon that a given locality description can represent Represented as a comma delimited array of vertices using latitude and longitude Next release will support auto-detection and generation of polygons

11. Multilingual Georeferencing • 3 millas al norte de Madrid • 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 (example- adding alternative unit representations)

12. 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

13. 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 www.museum.tulane.edu/taxonfootprint

14. www.museum.tulane.edu/taxonfootprint

15. Barbus paludinosus Mesobola brevianalis -27.02033 32.302492

16. Collaborative Georeferencing • Distributed community effort increases efficiency. • CoGe is a web-based portal/client for managing multiple georeferencing communities each with multiple members. • DiGIR / .CSV used for data input (other alternatives in development). • Similar records from various institutions can be matched and georeferenced simultaneously. • Georeferenced data can be returned to providers via portal (download as a comma delimited file). • CoGe is entirely web-service based; can be plugged into any digitization workflow (e.g., TCN data management systems).

17. DiGIR Service Remote Data Source Cache Update Web Service • CoGe Web Portal Application Data Retrieval Web Service Data Store • CoGe Client Application (Desktop or Web) Record Processor Insert Correction Web Service Georeferencing Web Service Collaborative Georeferencing

18. Users register for access with options for different levels of authority and privacy.

19. View Existing Communities

20. Create New Communities

21. Manage Community Data Sources Shows data sources within Nelson’s test community, number of records and pace of correction of records.

22. Add new data sources via DiGIR or .CSV files Four Steps (Step 1) Enter URL of DiGIR provider then click “Probe”.

23. Add new data source (Step 2) Select data source you would like to add then click “add”

24. Add new data source (Step 3) Resolve conflicts in data schema. Map them to default schema before source data added.

25. Add new data source (Step 4) Verify new concept mapping and approve it.

26. Update cache

27. Complete update Sync records Alert data provider of data inconsistencies 1 possible duplicate record was skipped and emailed to data provider. Option to keep or drop records from cache.

28. Save updated cache

29. A Locality records automatically georeferenced as they enter the data store. System monitors progress of result verification/correction. Collaborative aspect and record similarity matching maximizes efficiency of correction process.

30. View cache

31. Invite New Users to Join Community

32. Invite Sent

33. Invite Received

34. Adjust Community Users Permissions

35. Manage Community Georeferencing assignments Assign all records from Kenya to experts on East African regions

36. Viewcorrections

42. Interoperability:

50. Questions? University of the Western CapeCape Town, South Africa 04-08 Feb 2011