Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Distributed Versioned Editing in Action

Scott Clark
September 12, 2014

Distributed Versioned Editing in Action

Talk for FOSS4G 2014 about how we applied versioned editing with GeoSHAPE for the ROGUE JCTD

Scott Clark

September 12, 2014

More Decks by Scott Clark

Other Decks in Technology


  1. A project called ROGUE !   Joint Capability Technology Demonstration

    (JCTD) !   Two Year effort (Aug 2012 – Aug 2014) !   JCTDs introduce new concepts to solve operational problems !   ROGUE focused on supporting Humanitarian Assistance & Disaster Response
  2. The Challenge !   Supporting a wide range of partners,

    including military, inter- agency, national partners, & NGOs !   Common situational awareness is needed by all partners !   Responding organizations both need, & can provide a great deal of information !   Partners are distributed & sometimes disconnected !   Partners should have direct access to the technology itself The goal is to deliver dynamic, collaborative maps
  3. Our Building Blocks Community & OpenGeo Suite Components !  

    GeoNode: Spatial data portal !   GeoServer: Web access to geospatial data sources !   GeoWebCache: Caching & serving tiles !   PostGIS: Stores geospatial data in a relational database
  4. Additional Components !   ROGUE-GeoNode: A lightweight GeoNode project that

    overrides a handful of GeoNode templates and adds additional views !   Arbiter: Mobile app for data collection ! GeoGig: Distributed versioned editing !   MapLoom: OL3 web map embedded in GeoNode
  5. !   Distributed Versioned Editing !   Multi-user / Multi-organizational

    collaboration !   Provenance !   Synchronization & Conflict Resolution !   Lets you !   Import geospatial data: Shapefile, PostGIS, OpenStreetMap, SQLite… !   Branch and merge data !   Clone a repository !   View history for a repository, FeatureType (layer) or feature !   Tag a version !   Export & more GeoGig
  6. Web map for editing feature data & interacting with GeoGig

    !   Built using OpenLayers 3, Bootstrap, & Angular !   View history of layers & features in GeoGig !   Conflict resolution !   Export commit history to a .csv file MapLoom
  7. Native Android App for data collection !   Observations from

    the field !   Create & edit point, line, polygon features !   Link photos to a feature !   Cache basemap tiles & layers !   Work disconnected !   Sync over 3G or WiFi Arbiter
  8. !   Follows the GeoNode project construct !   View

    for GeoGig layer history !   MapLoom as main web map !   Import into GeoGig repos !   A lot of other worked pushed to mainline GeoNode ROGUE-GeoNode
  9. What worked well !   Development team & relationships with

    existing projects !   Open Source Community !   Continuous Integration, GitHub & Dev Ops !   Government team – USACE ERDC & SOUTHCOM S&T !   Transition team – Pacific Disaster Center, Department of State Humanitarian Information Unit !   Translation support
  10. Remaining Technical Challenges !   Documentation translation !   Better

    integration using Sphinx !   Schema accessibility in GeoServer !   Provisioning between servers !   Data, Styles, Schemas !   Better workflows (UI implementation) for branching & merging !   Easy install on top of existing OpenGeo Suite install !   Current process is manual !   Using SLD with KML & GeoServices REST
  11. Questions? !   MapLoom: A new web client with versioned

    editing (GeoGit) integration !   Friday at 13:00 – Track 3