Organisation terrestris GmbH & Co kg

Topic type		Target Type
Case Studies: Relate your experiences. Development: new developments in products. Collaboration: data collection, data sharing, open standards.		People new to open source geospatial Manager End User

ID Number

259

Name	Pirmin Kalberer
Organisation	Sourcepole
Email	[e-mail]

Paper Title	GeoPackage, the shapefile of the future
I can give a practical demo	no

Paper Abstract (short)

GeoPackage is a OGC candidate standard combining vector data and raster tiles in a single database file

Paper Abstract (long)

OGC has published GeoPackage as a candidate standard in January 2013. An SQLite container combines simple feature vector data (SpatiaLite) and JPEG/PNG raster tiles in a single file. The SQL interface makes it immediately usable for mobile, web or desktop applications. An embedded XML capabilities manifest makes a typical OGC standard out of it, provoking also critical comments. But an official standard for an interchange format built on widespread technology could finally end the good old shapefile era.

Topic type		Target Type
Development: new developments in products.		Manager End User Technical / Developer

ID Number

63

Name	Dorian Ginane
Organisation	Geomatys
Email	[e-mail]

Paper Title	Geoportal in action
I can give a practical demo	yes

Paper Abstract (short)

Nowadays, influenced by the OpenData movement or by legislation, lots of organization want to share their geospatial data using geoportal. However, the management, the maintenance and the evolution of such platforms are often expensive and time consuming. To overcome this gap, Geomatys built a geoportal solution based on homogenous technical solutions and where User eXperiences drive the software conception. To facilitate the maintainability, the solution is based on Java JEE portlets, allowing to do evolve each application parts without impacting the entire portal. To ensure user platform appropriation functionalities and interfaces benefit of a real ergonomic work.

Paper Abstract (long)

Due to OpenData movement or because of legislation such as the European INSPIRE directive, more and more organisations wish or have to share geospatial data using web platforms. Most of these structures are not historical data producers such as national cartographic institutes or such as marine charts editors, but they acquire geospatial data as a side effect to their core activities. Also these structures do not have always a specific team to manage the platform and an important budget dedicated to the maintain and to do evolve the platform. Also geoportals must be easily maintained and easily updated. Moreover the geoportal will be used by non-expert users and must be easily taken in hand. However the geoportals often handle a lot of different functionalities such as a classical web content management system and a geospatial data viewer in a same application. Consequently, they are often an aggregation of several different softwares each one dedicated to a specific function. One of the risk of these multi OpenSources software approach is to penalize the user experience by providing an heterogeneous visual aspect and by providing several different ergonomic approach in the same application. A second risk, is to have several different technologies for a same application and so to make difficult the solution maintenance. To avoid the first risk, the key idea is to be able to design the functionalities focusing on the user experience and not led by the pre-existing interfaces and by the pre-existing workflows of the softwares integrated. Also the portal solution presented is built on a technical homogenous OpenSource toolkit from which specific interfaces are designed based on an ergonomic work. To avoid the second risk, Geomatys uses an architecture based on Java JEE portlet and geospatial interoperability standards to design its portals. Indeed the portlets allow to integrate various applications on a same portlets container, this giving a very homogenous aspect to the solution. Moreover portlets ensure easy portal evolution. Each portlet can evolve independently because portlets communicate with each other using a communication standard (JSR 286). The interoperability allows building new clients portlets easily and to easily add third-party applications to the geoportal. Used together, portlets and interoperability standards are able to provide a very modular solution. The combined approach of a modular architecture and of an ergonomic interface design allow to build portal able to respond to organisations needs for sharing geospatial data.

Topic type		Target Type
Case Studies: Relate your experiences. Collaboration: data collection, data sharing, open standards.		End User

ID Number

330

Name	Simone Giannecchini
Organisation	GeoSolutions s.a.s.
Email	[e-mail]

Paper Title	GeoServer on steroids
I can give a practical demo	no

Paper Abstract (short)

Setting up a GeoServer can sometimes be deceptively simple. However, going from proof of concept to production requires a number of steps to be taken in order to optimize the server in terms of availability, performance and scalability. The presentation will show how to get from a basic setup to a battle ready, rock solid installation.

Paper Abstract (long)

Setting up a GeoServer can sometimes be deceptively simple. However, going from proof of concept to production requires a number of steps to be taken in order to optimize the server in terms of availability, performance and scalability. The presentation will show how to get from a basic setup to a battle ready, rock solid installation by showing the ropes an advanced user already mastered. The topics that will be covered in details include: - Optimize vector and raster data for the deep multi-resolution displays typical of web GIS - Optimize styling to provide a good balance between map navigability and performance, identifying common performance pitfalls in the styling options - Setting up caching with GWC for the background layers, identify layers and situations that are not suitable for caching - Defend against peak hour load by setting service limits and using the control-flow extension - Using the monitoring extension to control the server in production and identify sources of trouble (long request, clients making too many/too heavy requests, layers and services used the most that could use more tuning attention) - Solutions for clustering GeoServer 2.3.0 and GeoWebCache 1.4.0 - Challenges in scaling beyond the few hundreds concurrent requests, and solutions to get there The presentation will end with real world examples of enterprise deployments of GeoServer implemented by the author as well as its colleagues at GeoSolutions during the years.

Topic type		Target Type
Case Studies: Relate your experiences. Development: new developments in products. Hacks and Mashes: novel solutions to our problems.		People new to open source geospatial Manager End User Technical / Developer

Additional Presenters
Name	Andrea Aime
Organisation	GeoSolutions s.a.s.
Email	[e-mail]
Name	Alessio Fabiani
Organisation	GeoSolutions s.a.s.
Email	[e-mail]

ID Number

5

Name	Alessio Fabiani
Organisation	GeoSolutions s.a.s.
Email	[e-mail]

Paper Title	GeoServer, an introduction for beginners
I can give a practical demo	yes

Paper Abstract (short)

This presentation will provide an introduction to the GeoServer project and its abilities to publish data with a mix of well known OGC protocols and other pupolar protocol and data formats.

Paper Abstract (long)

This presentation will provide an introduction to the GeoServer project and its abilities to publish data with a mix of well known OGC protocols and other pupolar protocol and data formats. This presentation will provide an introduction to the GeoServer project and its abilities to publish data with a mix of well known OGC protocols and other pupolar protocol and data formats, including: - Setting up vector and raster data from the GeoServer administration control - Publishing data via WMS, WFS and WCS - Styling layers using desktop tools, with a carousel of GeoServer mapping abilities - Tile caching with WMTS - Moving to data processing with WPS - Brief introduction to security The attendees will be provided with the basic information to be able to get started with using GeoServer proficiently on their own.

Topic type		Target Type
Case Studies: Relate your experiences. Hacks and Mashes: novel solutions to our problems.		People new to open source geospatial Manager End User

Additional Presenters
Name	Andrea Aime
Organisation	GeoSolutions s.a.s.
Email	[e-mail]

ID Number

46

Name	Christopher Helm
Organisation	Esri
Email	[e-mail]

Paper Title	Geospatial Github
I can give a practical demo	yes

Paper Abstract (short)

A whimsical exploration of the best geospatial code repos on Github

Paper Abstract (long)

Github has lots of code, lots! Finding code is aslo actually pretty easy but there are a lot of repos that are directly related to the geospatial industry that can be hard to find. This talk will take you on exciting journey through several of the best & seldom known Github repos. I'll give my top ten repos, and also walk through demos of why these repos are great and why you should know about them.

Topic type		Target Type
Case Studies: Relate your experiences. Benchmarks: Comparisons between packages. Development: new developments in products. Collaboration: data collection, data sharing, open standards.		People new to open source geospatial Manager End User Technical / Developer

ID Number

136

Name	Luca Morandini
Organisation	University of Melbourne
Email	[e-mail]

Paper Title	Getting the best performance for GeoJSON map visualizations: PostGIS vs CouchDB backend.
I can give a practical demo	no

Paper Abstract (short)

Rich user experiences call for JSON data, but what combination of DBMS, compression, generalization, etc. can deliver the best performance on the client ? During the course of this presentation we will present our findings, showing how we collected test data and built statistical models to gauge the contribution of each factor (DBMS, compression, etc.) to the overall performance

Paper Abstract (long)

In order to deliver rich user experience to user, features (attribute data and geometries) have to be sent to the client for mouse-over visual effects, synchronization between charts, tables and maps, and on-the-fly classifications. GeoJSON is one of the most popular encodings for the transfer of features for client-side map visualization. The performance of client visualizations depends on a number of factors: message size, client memory allocation, bandwidth, and the speed of the database back-end amongst the main ones. Large GeoJSON-encoded datasets can substantially slow down loading and stylization times, and also crash the browser when too many geometries are requested. A combination of techniques can be used to reduce the size of the data (polygon generalization, compression, etc). The choice of an open-source DBMS for geo-spatial applications used to be easy: PostGIS is powerful, well-supported, robust and fast RDBMS ? On the other hand, unstructured data, such as (Geo)JSON, may be better served by document-oriented DBMS such as Apache CouchDB. The performance of PostGIS and CouchDB in producing GeoJSON polygons with different combination of factors that are known to affect performance was tested: compression of GeoJSON (zip) to reduce transmission times, different levels of geometry generalization (reducing the number of vertices in transferred geometries), precision reduction (the reduction of numbers of decimal digits encoding coordinates), and the use of a topological JSON encoding of geometries (TopoJSON) to avoid redundancy of edges transferred. We present the results of a benchmark exercise testing the performance of an OpenLayers interface backed by a persistence layer implemented using PostGIS and CouchD. Test data were collected using an automated test application based on Selenium, which allowed to gather repeated observations for every combination of factors and build statistical models of performance. These statistical models help to pick the best combination of techniques and DBMS, and to gauge the relative contribution of every technique to the overall performance.