Download to read offline
Uploaded byJody Garnett
State of GeoGig
The document outlines the development updates and performance enhancements for GeoGig, including the release of version 1.0 and subsequent updates like 1.1 and 1.1.1, which focus on optimizations and smaller memory footprints. Key improvements include spatial-with-attributes indexing, rendering performance enhancements, and collaboration features aimed at user experience in geo-data management. Future goals involve further enhancing user collaboration and ease of use, with a call to engage with the community for feedback and collaboration opportunities.
More Related Content
State of GeoGig
- 1.
- 2. David Blasby ErikMerkle Gabriel RoldanHannah Bristol Johnathan Garrett Prominent Edge The Main GeoGig Team
- 3. 1.0 - Firstofficial LocationTech release! Core functionality complete. 1.1 - Optimization for direct GeoGig Querying. Spatial-with-attributes index. 1.1.1 - More optimization for GeoGig inside GeoServer GeoServer Clustering Support 2016 Q4 2017 Q2 2017 Q3 GeoGig Releases
- 4.
- 5.
- 6. 1.1.x Series PostgreSQL GeoServer GeoGig Network Encoding •1.1 - twice as small as 1.0 • 1.1.1 - another 25% smaller Almost 3* smaller!
- 7. 1.1.x Series PostgreSQL GeoServer GeoGig Cache In-MemoryCache • lots of performance improvements! • easy to configure • view usage statistics
- 8. 1.1.x Series PostgreSQL GeoServer GeoGig Rendering PerformanceImprovements • took a deep look at the rendering process • made many optimizations
- 9. 1.1.x Series PostgreSQL GeoServer GeoGig Clustered GeoServerDeployments • made sure GeoGig functioned with GeoServer’s Resource API • watch out for the size of the memory cache
- 10. 1.1.x Series PostgreSQL GeoServer GeoGig Spatial-With-Attributes Index •Biggest task in 1.1.x • Huge performance improvements
- 11. Spatial-with-Attributes Index GeoGig holdsmost of its information in two places • A revision-sharing hash (Merkle) index tree • Actual feature data Revision BRevision A Sharable Sub-Trees Actual Feature Data Changed Feature
- 12. Spatial-with-Attributes Index When youwant to Query features in a revision; a) Scan through the tree b) Request the features Revision BRevision A Sharable Sub-Trees Actual Feature Data
- 13. Includes sub-tree bounds Includesfeature bounds Quad-Tree Features in Same Quad
- 14. Spatial-with-Attributes Index What aboutattribute Queries? • Just draw Highways from a roads dataset • Just draw a time-slice of data from a time-enabled layer Revision BRevision A
- 15. Revision BRevision A Spatial-with-AttributesIndex We add some of the feature’s attribute data to the leaf nodes HUGE performance boost Include feature bounds and some attribute values
- 16. Spatial-with-Attributes Index Optimize queriesand retrieval Revision BRevision A Include feature bounds and some attribute values
- 17.
- 18. 1.1.x - Whereare we? 1.0 - Core Functionality, LocationTech Graduation 1.1.1 - Performance meeting/beating expectations
- 19. Where are wegoing? 1.2 - Changes required for GeoServer 2.12 release (REST) - Improving performance of clone/push/pull/fetch
- 20. Where do weneed to go next?
- 21. Where do weneed to go next? We really really want people to actually collaborate.
- 22. Where do weneed to go next? Need to make things easy to use!
- 23. Making Things Easier Concentratingon User Experience
- 24. Making Things Easier FundamentalGeoGig Ops High-level Primitives Workflows
- 25. Making Things Easier GeoGigCollaboration Engine GeoGig GeoServer QGIS
- 26. Enabling Collaboration We wantto hear how you could use GeoGig geogig-dev@locationtech.org
- 27. Discover, Learn, Collaborate,and Share connect.boundlessgeo.com With GIS Professionals Check out our booth #103
- 28. David Blasby JohnathanGarrett Prominent Edge Q&A Please come talk to us during the conference or on-line at geogig.org - geogig-dev@locationtech.org