View
1.677
Download
4
Category
Preview:
DESCRIPTION
Advancing Open Source Geospatial Software for the DoD/IC Eddie Pickle, OpenGeo
Citation preview
Advancing Open Source Geospatial Software for
the DoD/IC
MILITARY OPEN SOURCE SOFTWARE (Mil-OSS)
August 3, 2010
Summary
• Many DoD/Intel organizations deploy geo web services based on OS software
• Increasingly organizations turn to OpenGeo– To deploy with greater ease and lower risk
– To develop advanced features
• OpenGeo is extending the OpenGeo Suite for collaboration and Web 2.0 functionality
OpenGeo Background
• Founded 2003. HQ New York City
• Enterprise support for a complete, open-source web mapping platform– Certified, stable releases with one easy install– Professional support and service– Training– Advanced development & feature enhancements
OpenGeo Suite Bundles Five Open Source Projects For Enterprise Use
• Storage: PostGIS PostgreSQL spatial database
• Application server: GeoServer map/feature server
• Application cache: GeoWebCache tile cache
• User interface framework: GeoExt / ExtJS
• User interface map component: OpenLayers
Strong OGC Standards Support
• WFS Reference Implementation• WFS, WFS-T 1.0• WFS, WFS-T and WFS Xlink 1.1• WCS 1.0 compliant and 1.1 Reference Implementation• WMS 1.1.1 and full SLD• SLD is native style format• KML with Super Overlays• GeoRSS, GeoJSON, Shapefile, PDF, WMS-C, CSV, XLS
KML Super Overlays
• Problem: Display large data sets on Google Earth
• Generated KML is simply too big• Features for display have a clear hierarchy• Zoomed out, you want to display only the most
important ones– Less important ones should appear progressively, as you
zoom in, while leaving the important ones visible– Everything should happen in the most fluid way
KML Super Overlays
• Solution– Create a pyramid like structure– Have Google Earth regions drive what is visible at each
scale– Use a tile cache to maximize delivery speed
OpenGeo Suite Options
• Community Edition – free
• Enterprise Editions – four levels of support– Basic– Professional– Platform– Strategic
Who Uses OpenGeo Software?
OpenGeo Clients
• NGA• World Bank• MassGIS• Google• City of New York• Portland TriMet• Palantir Technologies
• DISA
• Austrian Fed. Railways• Finnish Ministry of Agric.• Grontmij-Calbro (Den.)• Landgate (Australia)• Rijkswaterstaat (Neth.)• SWECO (Sweden)
Helping theDOD/IC
Easily create, visualize and publish data for situational awareness with the
OpenGeo Suite
GeoServer
OpenGeo Suite – Key Features
• Greater scalability & app control in combining enterprise data with Google's infrastructure
• Additional geospatial capabilities to the Oracle platform
• Seamless integration with ESRI, plus developer-friendly JavaScript components
• Instant, wide access to data stores on Bing
A New Approach to Developing SDI
CAPRA is an ongoing initiative to develop and enhance a set of free and open source tools to understand, communicate and support decisions to reduce disaster risk within Central America.
The CAPRA ProgramCentral America Probabilistic Risk Assessment
EARTHQUAKE HURRICANE INTENSE RAIN VOLCANO
TSUNAMI
GROUND SHAKING / LIQUEFACTION
LANDSLIDESLANDSLIDES
- - GROUND SHAKINGGROUND SHAKING- HURRICANE RAINFALL- HURRICANE RAINFALL
- OTHER RAINFALL- OTHER RAINFALL
STRONG WINDS
STORM SURGE
HURRICANE RAINFALL
FLOODSFLOODS
- HURRICANE RAINFALL- HURRICANE RAINFALL- OTHER RAINFALL- OTHER RAINFALL
ASH FALLS
BALLISTIC EJECTIONS
PYROCLASTIC FLOWS
LAVA FLOWS
Multiple Natural Hazards
Risk(i.e. probable loss)
Hazard(i.e. earthquake)
Exposure(i.e. houses)
Vulnerability(of house to quake)
INFRASTRUCTURE ENVIRONMENTALECONOMIC SOCIAL
- Disaster Impact Analysis- Scenario or Stochastic
Probabilistic Risk Modeling
Risk(i.e. probable loss)
Hazard(i.e. earthquake)
Exposure(i.e. houses)
Vulnerability(of house to quake)
1) Locate the data that already exists2) Access and share that data3) Create the data that is not in existence
SDIs and Collaborative Mapping
Meeting CAPRA Requirements
Need more participatory SDI building Must improve/augment existing SDI platforms Meet these requirements through developing and
distributing open source, Web-based GeoNodes
The theory of SDI developed before we learned what was possible with the Internet…
Successful Internet projects have a vitality that encourages participation.
Align incentives to create a sustainable Spatial Data Infrastructure
Necessary, but not sufficient to just have policies, requirements & mandates
Necessary, but not sufficient to just have best-of-breed software
Spatial Data Infrastructure (SDI)
–Tim O’Reilly
“Architectures of Participation”
An “Architecture of Participation” is bothsocial 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.
User at the Center
Compelling and relevant
User Responsibility
Reduce Barriers of Entry
GeoNode = Web Portals + Web 2.0
Collaboration
Distribution
Cartography
Data collection
GeoNode Principle Concepts
Very simple to share data Provide user statistics Comments, ratings, tags Collaborative Filtering Rankings of best ‘views’ and data sets contributed Highest rated, most viewed, most shared
GeoNode is About Collaboration…
Usage Statistics Add Context…
Ratings Inform Search Results…
Comments improve collaboration...
Simple installation and distribution
Automatic metadata creation
Versioned metadata Searchable via
catalogs and also Google
GeoNode is About Distribution…
User Profiles as Sources of Metadata
User Profiles as Sources of Metadata
GeoNode is About Cartography…
...that will entice people to upload and use their data on GeoNode
Give Users Web GIS Tools…
Styling
Editing
Tools and workflows for data integrationFocus on exposure data for disaster reduction
GeoNode is about Data Collection
OpenStreetMap
Focus on exposure data for disaster reduction
Data Collection Platform
GeoNode Components
For the metadata catalog Fully integrated with upcoming 1.0 release
JavaScript library for rich web GIS applications Same library as used in MapFish user interface
Web application framework The glue between the other pieces Foundation for social features
and cartographic ecosystem
GeoNode Status: Progress, Challenges and Promise
June 2009 – Began prototype development September 2009 – Completed prototype
development October 2009 – Began 1.0 development August 2010 – 1.0 beta release September 2010 – 1.0 release (planned) 2011 – Pilot deployment in Piura, Peru
GeoNode Project Timeline
SDI-building institutions have high standards for metadata (ISO)
Social features of GeoNode depend on social metadata (ratings, # of views, comments, etc.)
Challenge: Integrating Social Metadata
How to put social metadata into the metadata catalog?
Using & modifying GeoNetwork Building a custom XML schema that extends ISO19139
with social metadata fields
Challenge: Integrating Social Metadata
GeoNode requirements: Open source Focus on the user (rich profiles, content management,
and social metadata, etc.) Standard open source geospatial web tools lack
this focus Need a modern web application framework
Challenge: Focus on Users
Most robust ones are in lighter-weight scripting languages
Geospatial applications require higher-performance languages
Challenge: Which Web Framework?
Chose Django: mature & lighter-weight Presents challenging build and deployment issues But gained a strong community and great capabilities for
building user features
Challenge: Which Web Framework?
Work on the API's of GeoNode components Improved styling widget library for GeoExt Improved GeoServer REST API gsconfig.py, a library for working with the GeoServer REST
API Patches to OWSLib
Solution: Contributions to Open Source
Integrating existing tools & building new application code
Adding to the libraries and API's at the joints Maximize potential for reuse
Contributions to Open Source
GeoNode encourages Open Data Some institutions love this Others are concerned about data quality, misuse of
data, etc.
Challenge: Open Data
Solution: Give Users Control
Solution: Group Endorsement
Peru and Guatemala have started their own open source SDI initiatives
Quick progress, but no unified community
Challenge: CAPRA & Other OS SDIs
Encourage common use of GeoNode as open source SDI throughout Latin America
Involve others in the developer community
Solution: Build Developer Community
• Haiti Data Dissemination Portal• Global Earthquake Model • ITHACA / WFP • Caribbean Community Climate Change Center • And more...
User Community
Other Initiatives
• OpenAerialMap– What's needed is a bright shiny core, well documented
for others to work from.– OSM got that through the monk-like devotion, over a
period of months/years, by the OSM founders – OAM is getting that from... nobody (post C. Schmidt)– OpenGeo pursuing partners and funders to revive OAM
as a repository for contributions of raster data
Questions & Discussion
Questions & Discussion
• Contacts:– Eddie Pickle, epickle@opengeo.org– Chris Holmes, cholmes@opengeo.org– Ken Bossung, kbossung@opengeo.org– Alyssa Wright, awright@opengeo.org
Recommended