Topic type
|
|
Target Type
|
Case Studies: Relate your experiences.
Benchmarks: Comparisons between packages.
|
|
People new to open source geospatial
Manager
End User
Technical / Developer
|
Additional Presenters
|
Name
|
Lluis VICENS FRANQUESA
|
Organisation
|
SIGTE-Universitat de Girona
|
Email
|
lluis@sigte.udg.edu
|
|
|
Name
|
Toni HERNANDEZ VALLƒS
|
Organisation
|
SIGTE-Universitat de Girona
|
Email
|
toni@sigte.udg.edu
|
Name
|
Sebastian Goerke
|
Organisation
|
lat/lon GmbH
|
Email
|
goerke@lat-lon.de
|
Paper Title
|
Tiles and more - deegree freshly implements WMTS
|
I can give a practical demo
|
yes
|
Paper Abstract (short)
|
In 2013, a new service type joined the deegree family - the deegree Web Map Tile Service. This deegree service implements the OGC WMTS 1.0.0 specification and is going to be the OGC reference implementation for this specification. Both, the OGC WMTS test suite and deegree's candidate reference implementation have been developed within the OGC OWS-9 initiative.
|
Paper Abstract (long)
|
In 2013, a new service type joined the deegree family - the deegree Web Map Tile Service. This deegree service implements the OGC WMTS 1.0.0 specification and is going to be the OGC reference implementation for this specification. Both, the OGC WMTS test suite and deegree's candidate reference implementation have been developed within the OGC OWS-9 initiative. The intention for implementing WMTS was that deegree had no clear strategy to handle big raster data. As a result, one of the advantages of deegree WMTS is the performant handling of big raster data - such as aerial images - and providing it through a standard-compliant interface. Additionally there is advanced support for using other web services based on OGC WMS and WMTS such as GeoServer, GeoWebCache and Mapserver as datasource for deegree's tiling API, which is the underlying data access layer of the WMTS. As a key feature deegree is capable of proxying FeatureInfo output from those remote services. The presentation will give an overview about deegree WMTS and all its capabilities, especially regarding the interfaces with other OSGeo components.
|
Topic type
|
|
Target Type
|
Visualization: effective presentation of information.
Development: new developments in products.
Collaboration: data collection, data sharing, open standards.
|
|
Manager
End User
Technical / Developer
|
Name
|
Petr Pridal
|
Organisation
|
Klokan Technologies GmbH
|
Email
|
petr.pridal@klokantech.com
|
Paper Title
|
TileServer: hosting map tiles and MBTiles
|
I can give a practical demo
|
yes
|
Paper Abstract (short)
|
Extremely fast, free and open-source OGC WMTS server for pre-rendered tiles running on any web server
|
Paper Abstract (long)
|
OpenGIS Web Map Tiling Service (WMTS) is becoming the standard used for distributing raster maps to the web and mobile applications, cell-phones, tablets as well as desktop software. Practically all popular desktop GIS products now support this standard as well, including ESRI ArcGIS for Desktop, open-source Quantum GIS (qgis) and uDig, etc. The TileServer, a new open-source software project, is going to be demonstrated. It is able to serve maps from an ordinary web-hosting and provide an efficient OGC WMTS compliant map tile service for maps pre-rendered with MapTiler, MapTiler Cluster, GDAL2Tiles, TileMill or available in MBTiles format. The presentation will demonstrate compatibility with ArcGIS client and other desktop GIS software, with popular web APIs (such as Google Maps, MapBox, OpenLayers, Leaflet) and with mobile SDKs. We will show a complete workflow from a GeoTIFF file (Ordnance Survey OpenData) with custom spatial reference coordinate system (OSGB / EPSG:27700) to the online service (OGC WMTS) provided from an ordinary web-hosting. The software has been originally developed by Klokan Technologies GmbH (Switzerland) in cooperation with NOAA (The National Oceanic and Atmospheric Administration, USA) and it has been successfully used to expose detailed aerial photos during disaster relief actions, for example on the crisis response for Hurricane Sandy and Hurricane Isaac in 2012. The software was able to handle large demand from an ordinary in-house web server without any issues. The geodata were displayed in a web application for general public and provided to GIS clients for professional use - thanks to compatibility with ArcIMS. It can be easily used for serving base maps, aerial photos or any other raster geodata. It very easy to apply - just copy the project files to a PHP-enabled directory along with your map data containing metadata.json file. The online service can be easily protected with password or burned-in watermarks made during the geodata rendering. Tiles are served directly by Apache web server with mod_rewrite rules as static files and therefore are very fast and with correct HTTP caching headers. The web interface and XML metadata are delivered via PHP, because it allows deployment on large number of existing web servers including variety of free web hosting providers. There is no need to install any additional software on the webserver. The mapping data can be easily served in the standardized form from in-house web servers, or from practically any standard web-hosting provider (the cheap unlimited tariffs are applicable too), and from a private cloud. The same principle can be applied on an external content distribution network (Amazon S3 / CloudFront) to serve the geodata with higher speed and reliability by automatically caching it geographically closer to your online visitors, while still paying only a few cents per transferred gigabyte.
|
Topic type
|
|
Target Type
|
Business Cases: building the economic case.
Development: new developments in products.
Hacks and Mashes: novel solutions to our problems.
|
|
People new to open source geospatial
Manager
End User
Technical / Developer
|
Name
|
Peter Baumann
|
Organisation
|
Jacobs Universit
|
Email
|
p.baumann@jacobs-university.de
|
Paper Title
|
Towards Big Earth Data Analytics: The EarthServer Approach
|
I can give a practical demo
|
yes
|
Paper Abstract (short)
|
EarthServer introduces distributed real-time analytics on Big Earth Data
|
Paper Abstract (long)
|
Big Data in the Earth sciences, the Tera- to Exabyte archives, mostly are made up from coverage data whereby the term "coverage", according to ISO and OGC, is defined as the digital representation of some space-time varying phenomenon. Common examples include 1-D sensor timeseries, 2-D remote sensing imagery, 3D x/y/t image timeseries and x/y/z geology data, and 4-D x/y/z/t atmosphere and ocean data. Analytics on such data requires on-demand processing of sometimes significant complexity, such as getting the Fourier transform of satellite images. As network bandwidth limits prohibit transfer of such Big Data it is indispensable to devise protocols allowing clients to task flexible and fast processing on the server. The EarthServer initiative, funded by EU FP7 eInfrastructures, unites 11 partners from computer and earth sciences to establish Big Earth Data Analytics. One key ingredient is flexibility for users to ask what they want, not impeded and complicated by system internals. The EarthServer answer to this is to use high-level query languages; these have proven tremendously successful on tabular and XML data, and we extend them with a central geo data structure, multi-dimensional arrays. A second key ingredient is scalability. Without any doubt, scalability ultimately can only be achieved through parallelization. In the past, parallelizing code has been done at compile time and usually with manual intervention. The EarthServer approach is to perform a semantic-based dynamic distribution of queries fragments based on networks optimization and further criteria. The EarthServer platform is comprised by rasdaman, an Array DBMS enabling efficient storage and retrieval of any-size, any-type multi-dimensional raster data. In the project, rasdaman is being extended with several functionality and scalability features, including: support for irregular grids and general meshes; in-situ retrieval (evaluation of database queries on existing archive structures, avoiding data import and, hence, duplication); the aforementioned distributed query processing. Additionally, Web clients for multi-dimensional data visualization are being established. Client/server interfaces are strictly based on OGC and W3C standards, in particular the Web Coverage Processing Service (WCPS) which defines a high-level raster query language. We present the EarthServer project with its vision and approaches, relate it to the current state of standardization, and demonstrate it by way of large-scale data centers and their services using rasdaman.
|
Topic type
|
|
Target Type
|
Case Studies: Relate your experiences.
Visualization: effective presentation of information.
Development: new developments in products.
Hacks and Mashes: novel solutions to our problems.
Collaboration: data collection, data sharing, open standards.
New data: handling new data models, for example 3D & temporal data, or big data.
|
|
People new to open source geospatial
Manager
End User
Technical / Developer
|
Name
|
CŽdric Moullet
|
Organisation
|
swisstopo
|
Email
|
cedric.moullet@gmail.com
|
Paper Title
|
User centered design for map.geo.admin.ch or how to create an usable geoportal.
|
I can give a practical demo
|
yes
|
Paper Abstract (short)
|
This presentation will describe the way to make a geoportal used and useful.
|
Paper Abstract (long)
|
ÒFast, intuitive, informative, fastÓ, according to Brian Timoney [1], these requirements are the secret of good web mapping applications. Ok, great, but how to handle 200 layers, permalinks, tooltips, address search, feature search, catalogs, layer trees, KML, GPX, measurements, profile, print, help, feedback, copyrights, contextual menu etc, etc.. ? This presentation will try to provide an answer based on the experiences made by the map.geo.admin.ch geoportal. ÒUser centered designÓ is probably the most important process in order to propose an usable geoportal. This process implies to identify the personas (or the user types) and to identify the use cases accomplished by these users. For map.geo.admin.ch, several methods have been used: contextual inquiry, user survey, analysis of user feedbacks and user tests. This talk will present these various methods and discuss their key findings: - A geoportal is not a GIS application. The UI has to be as simple as simple with only the strictly required features. - The pareto rule Ò80% of the effects come from 20% of the causeÓ applies perfectly for the features of a geoportal. The majority of features are ÒonlyÓ expert features. - Search has to be fast, efficient, fast, efficient, fast, efficient etc... The majority of users are used to work with Google search. The geoportal has to offer equivalent possibilities. - Thematic geoportals are easier to use. The diversity of layers is a killer for a geoportal. Layers need to be contextualized and grouped. - No need to have an ÒiÓ button is order to get attributive information. If the users wants an information about a feature, he has simply to click on this feature. - ÒSettingsÓ are forbidden (because never used) - Users are able to navigate in the map with the mouse... and this is the first thing users do after starting the application. - The switch between mobile and desktop worlds has to be possible without losing information. Internet users expect to work with a geoportal like with other web applications. The same design patterns have to be used in order to simplify the access to the geoinformation and to make your geoportal used and useful. LetÕs see if this dream can be a reality ! [1] http://mapbrief.com/2013/02/11/the-tyranny-of-requirements-why-map-portals-dont-work-part-iii/
|
Topic type
|
|
Target Type
|
Case Studies: Relate your experiences.
Business Cases: building the economic case.
Visualization: effective presentation of information.
Hacks and Mashes: novel solutions to our problems.
|
|
Manager
End User
Technical / Developer
|
Name
|
Adriˆ Mercader
|
Organisation
|
Open Knowledge Foundation
|
Email
|
adria.mercader@okfn.org
|
Paper Title
|
Using CKAN as a catalog for geospatial data
|
I can give a practical demo
|
yes
|
Paper Abstract (short)
|
CKAN is the most widely used open source data portal software across the world, built on open standards to make data easily discoverable and reusable for end users, manageable by publishers and easily customisable and expandable for developers. This presentation will explore what features already allow several organizations to publish their geospatial metadata with CKAN and how this provides an alternative to traditional geospatial catalogs.
|
Paper Abstract (long)
|
CKAN is an open source data management software maintained by the Open Knowledge Foundation, a UK-based non-profit organization pioneering tools for the promotion and sharing of open information. CKAN makes data accessible by providing tools to streamline publishing, sharing, finding and using data. CKAN is used around the world to power numerous Open Data catalogs [1], including official portals like the Open Data Hub of the European Union [2], the UK Government [3] one, and community driven ones like the DataHub or PublicData.eu. The upcoming new version of the US government Open Data portal will be also based on CKAN, merging general and geographic data, now spread across different sites. CKAN is a mature project, with a vibrant community around it and regularly welcomes contributions from external developers. On many of these portals geographic data plays a crucial role and a significant part of recent CKAN developments have focused on enhancing its geospatial capabilities, making it compatible with the standards used by the geospatial community. This process was started during the development of Data.gov.uk, which acts as the INSPIRE node for the UK, and has carried on through the development of the next version of geo.data.gov for the US Government. Our presentation will include an overview of the main features available in CKAN, from a polished user-centered UI down to the APIs that give full control over its functionality, allowing developers to extend it and customize it. Special efforts are made to make data easy to find and share, with a powerful full text search with faceting and spatial filtering available. Another aspect that has seen significant improvements are data visualizations that allow users to explore the datasets listed on the catalogue. For tabular data, CKAN integrates Recline [4], another open source library from the OKF that provides advanced visualizations such as tables, graphs and maps. Other viewers for geospatial standards like WMS and KML have also been developed. Using its harvesting and spatial extensions [5], CKAN allows importing geospatial metadata from other catalogs, supporting formats like ISO 19139 or FGDC and protocols like CSW or Web Accessible Folders. Other harvesters for other data sources like ArcGIS REST APIs can be also developed. Apart from its own API, metadata stored in CKAN can be exposed via a CSW interface, which is done integrating pycsw. CKAN is built on top of an open source stack, with the main code base written in Python and Javascript, Postgres as database server and Apache Solr as the search platform. The spatial extensions use well known open source geospatial projects and libraries, from PostGIS, pycsw or shapely on the backend to Leaflet or OpenLayers on the frontend. More information on CKAN and the main source code repository can be found on the following links: * http://ckan.org * https://github.com/okfn/ckan [1] http://ckan.org/instances [2] http://open-data.europa.eu/open-data/ [3] http://data.gov.uk [4] http://reclinejs.com/ [5] https://github.com/okfn/ckanext-spatial
|
Dostları ilə paylaş: |
