Skip to content
This repository has been archived by the owner on Apr 15, 2020. It is now read-only.

Latest commit

 

History

History
60 lines (50 loc) · 4.11 KB

01.md

File metadata and controls

60 lines (50 loc) · 4.11 KB
Raw

GIS Interest Group: Meeting 01

January 27, 2015 10:00AM - 11:00AM Pacific (01:00PM - 02:00PM Eastern, 02:00PM - 03:00PM Atlantic)

Agenda

  1. Introductions
  • James Griffin (Lafayette College Libraries)
  1. Proposed Solutions
  1. Institutional User Stories/Use Cases
  • To be captured

Attendees

  • James Griffin (Lafayette College Libraries)
    • Donald Moses (UPEI)
    • Lingling Jiang (USTC)
    • Kim Pham (USTC)
    • Marcel Fortin (USTC)
    • Melissa Anez (Islandora Foundation)

Notes

  • Lafayette is working on two projects using Geospatial metadata.
    • One documents the change in food manufcaturing over the US, using dot maps from ESRI files
    • Would like ultimately to render a js timeline widget within an Islandora site
    • Other project maps history of eastern PE residents of Lebanese extractions
  • James created a slideshow to highlight the basic points of concern for Lafayette's projects.
  • Concerns with discovery, indexing. Should they should MODS or DC?
  • Chose MODS because DC has globalization problem. Using geohydra tools, coming fro the Hydra community to generate MODS documents from standards compliant geospatical metadata.
  • Most using common datasets, such as esri, can generate metadata with this toolkit.
  • Resources from last Open Repos conferences.
  • Raster data sets
    • Images bearing data fields referencing GIS data
    • For access/discovery, it's limited to what can be extracted by tika and FITS. Beyond that you can't parse the data in any intelligent manner.
    • Managing vector data sets is also challenging. Geometric primitives related to geospacial coordinates, produced with ArcGIS at Lafayette.
    • Challenges: Individual features cannot be identified within a shapefile unless the shapefile is processed or parsed by some third party service. Islandora alone cannot handle this.
    • Began exploring/scoping java application to handle this. Using open source java service geoserver. Will be able to take assets in Islandora, integrate with geoserver, and interact with points within an shapefile. Developing RESTful API client for geoserver with Islandora. Basic CRUD operations are working.
    • Two aproaches:
    • stream Islandora data into js map visualization
    • take datastream content, upload and manage in geoserver, and pull up to OpenLayers. Geoserver has good caching utlities and this takes the load off of fedora.
    • Geoserver is used by the Cartaro project in the Drupal community. Also popular with DH and Omeka. Works well with PostGIS too.
    • Works with OpenLayers.
  • Ultimately, does data needs to be stored in two places: Fedora, and somewhere that can handle and serve the data, such as geoserver?
  • UPEI is using Varnish for caching. Using externally referenced urls as part of the content type for serving videos on Islandora sites.
  • Use Islandora/Fedora to store the package. Use something else to present the data on the fly.
  • Preference for GeoJSON extracted from esri shapefiles, over the shapefiles themselves, because of the potential in TopoJSON.
    • Can also be imported into a wider variety of desktop GIS applications
  • Looking for more use cases so the work can be generalized for the community
  • There is interest from USTC for putting Islandora results on a map.
  • UPEI does extractions of place names on works, builds a KML file. Managed datastream. Example

Other Business