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

ROGUE OSS

ROGUE OSS

Slides for talk at Tampa Bay Mil-OSS meeting on April 14th, 2014

04d90c67e5e6ea922342a8c761f739c2?s=128

Scott Clark

April 14, 2014
Tweet

Transcript

  1. ROGUE  OSS Sco+  Clark  –  Project  Manager  

  2. About  ROGUE Challenges in the HADR problem set: •  Supporting

    a wide range of partners, including military, inter-agency, national partners, and NGOs •  Common situational awareness is needed by all partners •  Responding organizations both need, and can provide a great deal of information •  Partners are distributed and sometimes disconnected Ø  Partners must have direct access to the technology itself In short, ROGUE allows organizations to collaboratively develop and share geospatial data with traditional and non-traditional partners Joint  Capability  Technology  Demonstrations  (JCTDs)  introduce  new   operational  concepts  to  maturing  technologies  to  solve  complex   problems
  3. Open  Source  Software  Components Community Components •  GeoNode: Geospatial portal

    •  GeoServer: Web access to geospatial data sources •  GeoWebCache: Caching & serving tiles •  PostGIS: Stores geospatial data in a relational database •  GeoGit: Distributed & versioned editing Custom Components •  ROGUE-GeoNode: A custom build that adds GeoGit and MapLoom •  Arbiter: Mobile app for data collection •  MapLoom: Custom OL3 web map used in GeoNode
  4. None
  5. •  Most feature data in ROGUE is stored in GeoGit

    databases •  Multi-user / Multi-organizational collaboration •  Lets you o  Import geospatial data: Shapefile, PostGIS, OpenStreetMap, SQLite… o  Branch and merge data o  Manage merge conflicts o  Clone a repository o  View history for a repository, featuretype (layer) or feature o  Tag a version o  Export, Sync, and more http://geogit.org GeoGit
  6. Collaboration  from  a  GeoNerd  POV

  7. An  Analyst’s  Worst  Nightmare

  8. ROGUE  Applied  in  Honduras

  9. Honduran  Independence  Day  09/15/13 http://copeco.gob.hn/n/node/2326

  10. •  ARC/GFDRR Yolanda GeoNode o  Combined team collected all geospatial

    data that was technically & legally open o  72 layers of geospatial data imported o  Sources included EU Joint Research Centre, UNOSAT, NGA, Humanitarian OSM team o  Hundreds of situation reports & PDFs from ARC and OCHA o  ROGUE & GFDRR developers provided remote support to ARC personnel on the ground •  Humanitarian OpenStreetMap Team o  Deployed task on HOT Tasking Manager o  OSM community made over 4.5 million edits from 1600 mappers working from 82 countries Yolanda  GeoNode h+p://yolandadata.org
  11. •  Deployment Support & Bug Fixes o  Imported and curated

    data sources o  Fixed deployment issues o  Helped maintain health of server •  OpenStreetMap Imports o  ARC needed to be able to combine OSM damage information with other layers o  Required ability to import updates & maintain history o  Import set up to extract building damage polygons daily o  http://boundlessgeo.com/2014/03/geogit-and- openstreetmap-for-yolanda/ ROGUE  Support
  12. None
  13. Who’s  who US Southern Command CoCom Sponsor US SOUTHCOM S&T

    Operational Manager USACE ERDC Technical Manager Dept of State HIU Deputy Transition Manager OSD DASD (RFO) Oversight Executive Pacific Disaster Center Transition Manager Boundless & Community Open Source Transition MapStory Foundation Technical Partner MARCIMS (USMC) Transition Partner COPECO Honduras Transition Point NGA Technical Partner
  14. None
  15. What  if? Taking  inspiration  from  GitHub  we  could  track  issues

     on  geospatial   data  as  well!
  16. None
  17. h+p://rogue.lmnsolutions.com More  information  at: