SlideShare a Scribd company logo
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 the DOD/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
The CAPRA Program Central America Probabilistic Risk Assessment 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.
Multiple Natural Hazards EARTHQUAKE HURRICANE INTENSE RAIN VOLCANO TSUNAMI GROUND SHAKING / LIQUEFACTION LANDSLIDES -  GROUND SHAKING - HURRICANE RAINFALL - OTHER RAINFALL STRONG WINDS STORM SURGE HURRICANE RAINFALL FLOODS - HURRICANE RAINFALL - OTHER RAINFALL ASH FALLS BALLISTIC EJECTIONS PYROCLASTIC FLOWS LAVA FLOWS
Probabilistic Risk Modeling Risk (i.e. probable loss) Hazard (i.e. earthquake) Exposure (i.e. houses) Vulnerability (of house to quake) INFRASTRUCTURE ENVIRONMENTAL ECONOMIC SOCIAL -  Disaster Impact Analysis - Scenario or Stochastic
SDIs and Collaborative Mapping Risk (i.e. probable loss) Hazard (i.e. earthquake) Exposure (i.e. houses) Vulnerability (of house to quake) 1)  Locate the data that already exists 2)  Access and share that data 3)  Create the data that is not in existence
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 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.
GeoNode = Web Portals + Web 2.0 User at the Center Compelling and relevant User Responsibility  Reduce Barriers of Entry
GeoNode Principle Concepts Collaboration Distribution Cartography Data collection
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 integration Focus 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,  [email_address] Chris Holmes,  [email_address] Ken Bossung,  [email_address] Alyssa Wright,  [email_address]

More Related Content

Advancing open source geospatial software for the do d ic edward pickle opengeo 20100802a

  • 1. Advancing Open Source Geospatial Software for the DoD/IC MILITARY OPEN SOURCE SOFTWARE (Mil-OSS) August 3, 2010
  • 2. 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
  • 3. 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
  • 4. 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
  • 5. 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
  • 6. 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
  • 7. 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
  • 8. OpenGeo Suite Options Community Edition – free Enterprise Editions – four levels of support Basic Professional Platform Strategic
  • 9. Who Uses OpenGeo Software?
  • 10. 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)
  • 11. Helping the DOD/IC Easily create, visualize and publish data for situational awareness with the OpenGeo Suite
  • 12.  
  • 14. 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
  • 15. A New Approach to Developing SDI
  • 16. The CAPRA Program Central America Probabilistic Risk Assessment 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.
  • 17. Multiple Natural Hazards EARTHQUAKE HURRICANE INTENSE RAIN VOLCANO TSUNAMI GROUND SHAKING / LIQUEFACTION LANDSLIDES - GROUND SHAKING - HURRICANE RAINFALL - OTHER RAINFALL STRONG WINDS STORM SURGE HURRICANE RAINFALL FLOODS - HURRICANE RAINFALL - OTHER RAINFALL ASH FALLS BALLISTIC EJECTIONS PYROCLASTIC FLOWS LAVA FLOWS
  • 18. Probabilistic Risk Modeling Risk (i.e. probable loss) Hazard (i.e. earthquake) Exposure (i.e. houses) Vulnerability (of house to quake) INFRASTRUCTURE ENVIRONMENTAL ECONOMIC SOCIAL - Disaster Impact Analysis - Scenario or Stochastic
  • 19. SDIs and Collaborative Mapping Risk (i.e. probable loss) Hazard (i.e. earthquake) Exposure (i.e. houses) Vulnerability (of house to quake) 1) Locate the data that already exists 2) Access and share that data 3) Create the data that is not in existence
  • 20. 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
  • 21. The theory of SDI developed before we learned what was possible with the Internet…
  • 22. Successful Internet projects have a vitality that encourages participation.
  • 23. 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)
  • 24. – Tim O’Reilly “ Architectures of Participation” 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.
  • 25. GeoNode = Web Portals + Web 2.0 User at the Center Compelling and relevant User Responsibility Reduce Barriers of Entry
  • 26. GeoNode Principle Concepts Collaboration Distribution Cartography Data collection
  • 27. 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…
  • 28. Usage Statistics Add Context…
  • 29. Ratings Inform Search Results…
  • 31. Simple installation and distribution Automatic metadata creation Versioned metadata Searchable via catalogs and also Google GeoNode is About Distribution…
  • 32. User Profiles as Sources of Metadata
  • 33. User Profiles as Sources of Metadata
  • 34. GeoNode is About Cartography…
  • 35. ...that will entice people to upload and use their data on GeoNode Give Users Web GIS Tools…
  • 38. Tools and workflows for data integration Focus on exposure data for disaster reduction GeoNode is about Data Collection
  • 39. OpenStreetMap Focus on exposure data for disaster reduction Data Collection Platform
  • 41. For the metadata catalog Fully integrated with upcoming 1.0 release
  • 42. JavaScript library for rich web GIS applications Same library as used in MapFish user interface
  • 43. Web application framework The glue between the other pieces Foundation for social features and cartographic ecosystem
  • 44. GeoNode Status: Progress, Challenges and Promise
  • 45. 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
  • 46. 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
  • 47. 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
  • 48. 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
  • 49. Most robust ones are in lighter-weight scripting languages Geospatial applications require higher-performance languages Challenge: Which Web Framework?
  • 50. 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?
  • 51. 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
  • 52. 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
  • 53. GeoNode encourages Open Data Some institutions love this Others are concerned about data quality, misuse of data, etc. Challenge: Open Data
  • 54. Solution: Give Users Control
  • 55. Solution: Group Endorsement
  • 56. Peru and Guatemala have started their own open source SDI initiatives Quick progress, but no unified community Challenge: CAPRA & Other OS SDIs
  • 57. Encourage common use of GeoNode as open source SDI throughout Latin America Involve others in the developer community Solution: Build Developer Community
  • 58. Haiti Data Dissemination Portal Global Earthquake Model ITHACA / WFP Caribbean Community Climate Change Center And more... User Community
  • 59. 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
  • 61. Questions & Discussion Contacts: Eddie Pickle, [email_address] Chris Holmes, [email_address] Ken Bossung, [email_address] Alyssa Wright, [email_address]

Editor's Notes

  1. The OpenGeo Suite enables scalable solutions to combine enterprise data with Google's mapping infrastructure. The OpenGeo Suite excels at Google Maps and Earth integration, connecting directly to existing databases, no matter how large.
  2. 04/26/10
  3. 04/26/10
  4. 04/26/10
  5. 04/26/10
  6. For example, we want usage statistics to add context ala YouTube
  7. 04/26/10
  8. 04/26/10
  9. 04/26/10
  10. 04/26/10
  11. 04/26/10
  12. 04/26/10
  13. 04/26/10
  14. 04/26/10
  15. 04/26/10
  16. 04/26/10
  17. 04/26/10
  18. 04/26/10
  19. 04/26/10