A Suite and a Node:
The two primary initiatives of OpenGeo.org
–Chris Holmes
In the beginning
(The Open Planning Project)
The first project
Towards OpenGeo
QuickTime™
and a of TOPP
• From a side
project
TIFF (Uncompressed) decompressor
are needed to see this picture.
• To sustaining
contract work
• And the push to grow
Grow!
Building a stack
The Client
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
OpenLayers
The Cache
The Database
The Rich Client
The OpenGeo Suite
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
Funding
Building the Open Geospatial Web
• Making Geospatial Information Open and
Accessible
• By bringing Open Source Principles to
Geo
• Working by building OS software that
gets used by all
• In the context of a hybrid organization
OpenGeo.org
Towards a Product
Enterprise
The full solution
OpenGe
oSuite
Enterprise Edition
What’s in the Suite 1.0?
• GeoServer, GeoWebCache, OpenLayers,
GeoExt
• Installers (Windows, Mac, Linux)
• Dashboard
• Importer
• Styler
• GeoExplorer
• Recipes
The Next Suite
• PostGIS Integration
– With installers
– In Dashboard
•
•
•
•
WARs - enable deployments on existing systems
GeoEditor
Tested and certified on a variety of platforms
More Recipes and Bug Fixes
Two flavors
The Suite Roadmap
• Stable, tested, certified releases
every four months
• Integrated GeoExplorer
• Monitoring Tools
• Mobile Data Gathering App Builder
• ArcMap plugin to publish to Suite
• On the cloud
Spatial Data Infrastructure (SDI)
“…the sources, systems, network
linkages, standards, and institutional
issues involved in delivering spatiallyrelated data from many different
sources to the widest possible group of
potential users at affordable costs.”
– Groot & McLaughlin 2000
Principles: Towards the SDI Party
Necessary, but not sufficient to
just have policies, requirements
& mandates
Necessary, but not sufficient to
just have best of breed software
Align incentives to create
a sustainable Spatial Data
Infrastructure
There are many
examples of aligning
incentives using the
internet
“Architectures of
Participation”
– Coined by Tim O’Reilly
An “Architecture of
Participation” is both social
and technical, leveraging the
skills and energy of users as
much as possible
to cooperate in building
something bigger than any
single person or organization
could alone.
contributors not just consumers
No more Aquariums!
People use them
if and when
they have to
not because they want to.
Which means they
don't use them
much at all.
GeoPortals
Portals
Too often portals have:
•
•
•
•
•
No benefit to registering
Few real users
No recognition
No reward for the effort
Uses stick, not carrot
There is little incentive to participate
= GeoPortals +
User at the Center
Compelling and relevant
User Responsibility
Reduce Barriers of Entry
But what is it?
GeoNode
is SDI software
inspired by the best practices
of the open, social web
It will have web GIS tools
...that will entice people to upload and use their data on GeoNode
GeoNode:
Integrated Viewer
QuickTime™ and a
H.264 decompressor
are needed to see this picture.
GeoNode:
Online Styling
QuickTime™ and a
H.264 decompressor
are needed to see this picture.
GeoNode:
Easy upload
Choose File
Upload
Geofile.shp
GeoNode:
Searchable by Google
QuickTime™ and a
H.264 decompressor
are needed to see this picture.
GeoNode:
Editing
QuickTime™ and a
H.264 decompressor
are needed to see this picture.
GeoNode: Mobile
access and editing
http://iol.opengeo.org/
examples/draw.html
On your iphone
QuickTime™ and a
H.264 decompressor
are needed to see this picture.
It will have social features
...that generate metadata to inform search results.
MAGIC!
GeoNode:
The bottom up SDI
• Traditional SDI start with metadata
• Metadata -> Users -> Data
• GeoNodes start with data
• Data -> Users -> Metadata
• Align incentives so everyone gets some
benefit from contributing
• Make it easy and open for anyone to use, not
just specialists
• Build iteratively
What's it made of?
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
...and more!
All implementing open standards and API's
...so it's easy to integrate with other applications and systems
We have a roadmap for the core features
...but the system will be pluggable to
accommodate the specific needs of
users
Taking this seriously.
We make it a priority build new features
as part of core projects
(as opposed to custom application code
on top)
We build new libraries,
which we hope to have general use,
as we go.
We budget for this and schedule
accordingly.
Our clients understand
that this is essential for success.
Who?
The World Bank
CAPRA in particular
They facilitate cooperation between lots of organizations to
do Disaster Risk Management modeling.
They have the data disorganization problem.
Probablistic Risk Modeling
Hazard
Exposure
Vulnerability
Risk
(i.e. earthquake)
(i.e. houses)
(of house to quake)
(i.e probable loss)
Make the best decisions today to
mitigate disaster tomorrow
Building the
regional
SDI from the
bottom up
Placing GeoNodes as
requested in CAPRA
countries
Countries control the data locally
Nodes sync regional information
I see a bright future
where spatial data for
disaster risk management
is managed efficiently
In CAPRA...
In the World Bank...
Across the Whole World...
Expanding GeoNodes
•
•
•
•
•
•
Haiti World Bank GeoNode
Guatemala
Peru
Global Earthquake Model (GEM)
ITHACA / WFP
INSPIRE?
The OpenGeo.org plan
Suite Clients
GeoNode Clients
$$$
GeoNode
Requirements
$$$
Support
GeoNode Team
Support
Features
Suite Team
Towards the ‘dot-org’
• Full Cost Recovery for OpenGeo
• Spin off like Mozilla Corporation
• Reinvest profit in similar ‘dot-orgs’
– Make Capital viral like the GPL
• Require complete transparency
• Business built on Open Source
principles