GeoNode Summit 2014


JCTDs introduce new operational concepts to maturing technologies to solve complex problems.

Challenges in the HA/DR problem set:

  • Supporting a wide range of partners, including military, inter-agency, and NGOs
  • Common situational awareness must be provided to all partners
  • Responding organizations both need, and can provide a great deal of information
  • Partners should have direct access to the technology itself
  • Partners are distributed and sometimes disconnected

In short, ROGUE allows organizations to collaboratively develop and analyze geospatial data with traditional and non-traditional partners

ROGUE Components

Community components:

  • GeoNode: The user interface
  • Geoserver: Web access to GIS data sources
  • GeoWebCache: Caching and serving tiles
  • PostGIS: Stores geospatial data in a relational database

Custom components:

  • ROGUE-GeoNode: A lightweight GeoNode-project that overrides a handful of GeoNode templates and adds additional views.
  • Arbiter: Native Android mobile application
  • GeoGIT: Distributed and versioned editing
  • MapLoom: Custom OL3 web mapping client used in GeoNode


  • Follows the GeoNode-project construct
  • Overrides 20 GeoNode templates
  • Adds 2 extra views

View on Github


  • Native Android App that supports data collection
  • User can create and edit feature geometry and attributes
  • Users can link media to features which get uploaded as documents in GeoNode *
  • Cache basemap tiles
  • Supports disconnected editing

View on Github
Syncing operation in Arbiter


  • Most feature data in ROGUE is stored in GeoGit datastores
  • Multi-user/Multi-organizational collaboration
  • Supports Low bandwidth and disconnected editing
  • Client side functionality interacts with geogit datastores via a restful service endpoint
  • Supported Git commands: add, apply, blame, branch, checkout, cherry-pick, clean, clone, commit, config, conflicts, diff, fetch, format-patch, geojson, help, init, log, ls, merge, oracle, osm, pg, pull, push, rebase, remote, reset, revert, rm, show, shp, sl, sqlserver, squash, status, tag, version

View on Github


  • Development started in October 2013
  • Custom client-side mapping application
  • Angular, Bootstrap 3, OpenLayers 3
  • Provides a high-level interface for performing GeoGit operations including: Commit, Merge, Sync, Conflict resolution, Log
  • Export commit history to a CSV file
  • Static files and template tags packaged in a python module (django-maploom) which is updated on every commit to Maploom.

View on Github
Conflict resolution in MapLoom.

2014 GeoNode Wishlist

    Core Enhancements

    • Group Permissions: Implement group permissions*
    • Abstract the GXP map configuration classes to make swapping out the mapping library easier.
    • Formal GeoNode API
    • External Layers: Model external layers and services as first-class citizens in GeoNode*
    •                     {"source": {"ptype": "gxp_olsource"},
                          "visibility": True,
                              "HIU Tacloban Post Event",

2014 GeoNode Wishlist (cont.)

    Core Enhancements (cont.)

    • Allow external resources to be saved as documents.
    • Client-side testing suite and larger test coverage.
    • Support more filetypes during upload including FGDB, and GeoJSON*

    GeoNode plugins

    • Geospatial Issue Tracking: Github-like issues with spatial bounds that are related to a map or layer in GeoNode*

JCTD Partners

  • Boundless & Community: Open Source Transition
  • COPECO Honduras: Transition Point
  • Dept. of State HIU: Deputy Transition Manager
  • MapStory Foundation: Technical Partner
  • MARCIMS (USMC): Transition Partner
  • NGA: Technical Partner
  • OSD DASD (RFO): Oversight Executive
  • Pacific Disaster Center: Transition Manager
  • USACE ERDC: Technical Manager
  • US Southern Command: CoCom Sponsor
  • US SOUTHCOM S&T: Operational Manager

Thank you!

GeoNode Summit 2014