Show filters Hide filters

Refine your search

Publication Year
1-36 out of 72 results
Change view
  • Sort by:
25:41 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

istSOS: latest developments and first steps into the OSGeo incubation process

istSOS (http://istsos.org) is an OGC SOS server implementation entirely written in Python. istSOS allows for managing and dispatching observations from monitoring sensors according to the Sensor Observation Service standard. istSOS is released under the GPL License, and should run on all major platforms (Windows, Linux, Mac OS X). The presentation will go through the details of all the new features that will be packed in the next release. In particular the presenters will introduce enhancements that include the Advanced Procedures Status Page and the istSOS Alerts & Web Notification Service. The istSOS Advanced Procedures Status Page is a new section of the Web graphical user Interface, offering at a glance a graphically representation of the Sensor Network health. Administrators can easily figure out common issues related with sensor data acquisition and transmission errors. The istSOS Alert & Web Notification Service are the result of the Google Summer of Code 2014 outputs. This service is a REST implementation that take inspiration from the OGC Web Notification Service (OGC, 2003; OGC, 2006a) and the Sensor Alert Service (OGC, 2006b) which currently are OpenGIS Best Practices. Alerts are triggered by customized conditions on sensor observations and can be dispatched through emails or social networks. This year istSOS is entering into the OSGeo incubation process, this new challenge will permit to enhance the software quality and consolidate the project management procedures. The presenters will present the incubation status and discuss about the next steps.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:56 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Analyzing Fire Department Response with PostGIS

Local government fire departments always face scrutiny of their performance and efficiency. They are continuously asked to do a better job with fewer resources. In this highly technical session we will show how PostGIS is being used to analyze and measure performance throughout the city and plan for future resource requirements. Every city we work with is unique in some way. Some fire departments act as the local ambulance service while other cities contract with private ambulance companies. Emergency “911” response centers are often managed by police/law enforcement departments but not always! Many cities also have “mutual aid” agreements with neighboring cities to assist them when needed. For our customers PostGIS stores and manages the geo-located events (fires, hazardous spills, etc.) and provides details about the departments and individual emergency vehicle performance. It is most interestingly used to create statistical reports about things such as “Effecive Response Force” and “Resource Drawdown”, which are used to measure the efficiency and effectiveness of the department. Please come to learn how PostGIS is used to analyze things such as primary response areas and fire hazard severity zones, allowing our customers to ask more advanced, geographically based questions.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
20:49 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Semantic assessment and monitoring of crowdsourced geographic information

Whilst opensource software allows for the transparent collection of crowdsourced geographic information, in order for this material to be of value it is crucial that it be trusted. A semantic assessment of a feature’s attributes against ontologies representative of features likely to reside in this location provides an indication of how likely it is that the information submitted actually represents what is on the ground. This trust rating can then be incorporated into provenance information to provide users of the dataset an indication of each feature’s likely accuracy. Further to this, querying of provenance information can identify the features with the highest/lowest trust rating at a point in time. This presentation uses crowdsourced data detailing the location of fruit trees as a case study to demonstrate these concepts. Submissions of such crowdsourced information – by way of, say, an OpenLayers frontend – allow for the collection of both coordinate and attribute data. The location data indicates the relevant ontologies – able to be developed in Protégé – that describe the fruit trees likely to be encountered. If the fruit name associate with a submitted feature is not found in this area (e.g. a coconut tree in Alaska) then, by way of this model, the feature is determined to be inaccurate and given a low trust rating. Note that the model does not deem the information wrong or erase it, simply unlikely to be correct and deemed to be of questionable trust. The process continues by comparing submitted attribute data with the information describing the type of fruit tree – such as height – that is contained in the relevant ontologies. After this assessment of how well the submitted feature “fits” with its location the assigned trust rating is added to the feature’s provenance information via a semantic provenance model (akin to the W3C’s OPM). Use of such semantic web technologies then allows for querying to identify lower quality (less trustworthy) features and the reasons for their uncertainty (whether it be an issue with collection – such as not enough attribute data being recorded; time since collection – given degradation of data quality over time, i.e. older features are likely less accurate than newer ones; or because of a major event that could physically alter/remove the actual element, like a storm or earthquake). The tendency for crowdsourced datasets to be continually updated and amended means they are effectively dynamic when compared to more traditional datasets that are generally fixed to a set period/point in time. This requires them to be easily updated; however, it is important that efforts are directed at identifying and strengthening the features which represent the weakest links in the dataset. This is achievable through the use of opensource software and methods detailed in this presentation.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
26:00 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Image Geocoding as a Service

Driven by the ambition of a global geocoding solution, in this paper we present the architecture of an image geocoding service. It takes advantage of the ubiquity of cameras, that are present in almost all smartphones. It is an inexpensive sensor yet powerful, that can be used to provide precise location and orientation. This geocoding service provides an API similar to existing ones for place names and addresses, like Google Geocoding API. Instead of a text based query, images can be submitted to estimate the location and orientation of the user. Developers can use this new API, keeping almost all the existing code already used for other geocoding APIs. Behind the scenes, image features are extracted from the submitted photograph, and compared against a huge database of georeferenced models. These models were constructed using structure from motion (SFM) techniques, and heavily reduced to a representative set of all information using Synthetic Views. Our preliminary results shows that the pose estimation of the majority of the images submitted to our geocoding was successfully computed (more than 60%) with the mean positional error around 2 meters. With this service, an inexpensive outdoor/indoor location service can be provided, for example, for urban environments, where GPS fails.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
32:29 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Magical PostGIS in three brief movements

Everyone knows you can query a bounding box or even spatially join tables in PostGIS, but what about more advanced magic? This short symphony of PostGIS examples will look at using advanced features of PostGIS and PostgreSQL to accomplish surprising results: * Using full text search to build a spatially interactive web form. * Using raster functionality to look into the future. * Using standard PostgreSQL features to track and visualize versioning in data. PostGIS is a powerful tool on it's own, but combined with the features of PostgreSQL, it is almost magical.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
25:33 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Intelligent SDIs with MapMint 2.0

This conference aims at presenting the status of the MapMint open source project and its upcoming 2.0 version. The upgrade to newer versions of its core open source components will first be explained. The extensive use of OGC standards through ZOO-Project 1.5, GDAL 1.11 and MapServer 7 is indeed making MapMint an even more stable and efficient foundation to build an open source and standard-compliant spatial data infrastructure. The new metadata related functionalities being developed in interaction with PyCSW and CKAN will also be presented along with the assets of the CSW standard support. The new MapMint responsive user interfaces based on OpenLayers 3 and Bootstrap will also be presented. Both code and documentation improvements will also be detailed. The newly added functionalities in MapMint 2.0 will finally be explained from the developer and user point of views, based on case studies and live examples.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:45 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Building and integrating a Continuous-Integration system within your open source project

So you have an open source project or you want to create a new one. Maybe you have worked on a development project in the past that didn’t have quite the amount of rigor you would have liked. You know you want a build system for your project that is easy to administer, cheap, and powerful, but where do you start? Here is how we implemented our own process using free open source tools. We learned from experience that developers are more focused on solving problems than perceived “housekeeping” tasks. We needed tools that would automate the mundane, repeatable, mechanical, or human-difficult tasks so that developers could focus on what they are good at. We needed a single-sign on through Github to lower any barriers to tool usage that might exist. We needed a dead-simple way to determine if our commits broke functionality anywhere else in code. We needed to track how much of our code was covered by unit tests. Finally, we needed to be able to quickly and easily review each-other’s code and provide feedback. We decided on TravisCI to handle build duties in Maven with a nested project structure and also for its integration with Coveralls. For bug tracking, release scheduling, and task management, we chose WaffleIO for its tight integration with Github issues. One additional feature we desired was static analysis so that simple errors that lie outside of a linter could be caught and reported. This was handled by a combination of Coverity scans and a static analysis tool for Eclipse called Findbugs. Due to our platform support and third-party library (GDAL) requirement, the Github Wiki was the perfect place to keep all setup documents and other helpful articles for end-users and project new-comers. This system for software development worked quite well in most cases. Builds were automated, moderately tested (~40-60% coverage), and complaining to the team loudly via email when things broke. We had a new problem though: build breakages in the master branch and the inability to share code that was not yet fully functional. To alleviate this, we started using the branching and merging functionality that makes Git so valuable. Now, no direct commits occur to the master branch unless in very special circumstances. A developer will see the TravisCI build results before the merge ever occurs, allowing them to adjust code or test cases *before* they cause failures. As a side effect, the merge request workflow allows the team to perform code reviews quickly and easily. Finally, any CI system is not without challenges. Building a continuous integration system has upfront costs that should not be ignored. The payoff from those costs, however, is code/product quality and the avoidance of technical debt. Lastly, some of these CI tools lack support for private repositories.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
31:05 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

OSGeo and LocationTech Comparison

We have two great organizations supporting our Free and Open Source Software for Geospatial: The Open Source Geospatial Foundation and LocationTech. Putting on events like FOSS4G is primary responsibility of these software foundations - supporting our great open source software is! This talk will introduce OSGeo and LocationTech, and balance the tricky topic of comparison for those interested in what each organisation offers. We will also look at areas where these organizations are collaboration and explore possibilities for future work. Each of these software foundations support for their existing projects, ranging from "release parties" such as OSGeo Live or the Eclipse Annual Release. We are also interested in the ��incubation�� process each provides to onboard new projects. Review of the incubation provides an insight into an organization's priorities. This talks draws the incubation experience of: * GeoServer (OSGeo), GeoTools (OSGeo), * GeoGig (LocationTech), uDig (LocationTech) If you are an open source developer interested in joining a foundation we will cover some of the resource, marking and infrastructure benefits that may be a factor for consideration. We will also looking into some of the long term benefits a software foundation provides both you and importantly users of your software. If you are a team members faced with the difficult choice of selecting open source technologies this talk can help. We can learn a lot about the risks associated with open source based on how each foundation seeks to protect you. The factors a software foundation considers for its projects provide useful criteria you can use to evaluate any projects.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:10 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Raster Data In GeoServer And GeoTools: Achievements, Issues And Future Developments

The purpose of this presentation is, on a side, to dissect the developments performed during last year as far as raster data support in GeoTools and GeoServer is concerned, while on the other side to introduce and discuss the future development directions. Advancements and improvements for the management of multidimensional raster data (NetCDF, GRIB, HDF) and mosaic thereof will be introduced, as well as the available ways to manage sliding windows of data via the REST API and importer. Extensive details will be provided on the latest updates for the management of multidimensional raster data used in the Remote Sensing and MetOc fields, including support for WCS EO and WMS EO, and some considerations on the WCS MetOc extensions. The presentation will also introduce and provide updates on jai-ext, imageio-ext, and JAITools. jai-ext provides extended JAI operators that correctly handle NODATA and regione of interests (masks), JAITools provides a number of new raster data analysis operators, including powerful and fast raster algebra support, while ImageIO-Ext bridges the gap across the Java world and native raster data access libraries providing high performance access to GDAL, Kakadu and other libraries. The presentation will wrap up providing an overview of unresolved issues and challenges that still need to be addressed, suggesting tips and workarounds allowing to leverage the full potential of the systems.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:15 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Using the latest ISO standard for geographic information (ISO19115-1:2014)

Release in April 2014, this talk will introduce the major changes of the new standard for metadata on geographic information and what are the benefits for the data managers. It will be illustrated by its implementation in the latest GeoNetwork 3 version and with examples on how the Wallonia Region in Belgium migrated to it.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:13 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Geodata for Everyone - Model-driven development and an example of INSPIRE WFS service

In denmark the public authorities register various core information about individuals, businesses, real properties, buildings, addresses, ect.. This information is re-used throughout the public sector. It is a challenge for public authorities to re-use data from different providers to perform their tasks properly and efficiently across units, administrations and sectors. Therefore all the authoritative basic data should be defined and standardized according to the same methods. Danish Geodata agency as Denmark's central public source of geographic data has established a set of guidelines for future modelling of spatial data for distributing them as open geographic data. Based on the guidelines a model-driven process has also been established. It starts from the data modelling in UML to the end where data are distributed through WFS services and download services. One INSPIRE WFS service will be used as a concrete example.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
16:51 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Revolutionizing map use in Norwegian newspapers

Norway represents one of the countries with most newspapers and media outlets per person. One topic that has an everlasting interest is land registration data - or more commonly: Who bought which properties and what was the price. Land registration data has always been a public data set. Every citizen can request specific information on who has rights to which properties. Up until 1. January 2014 the digital version of this data set was monopolized by law to one vendor - obviously inhibiting innovation. Starting in 2014 - land registration data has been opened and is now accessible to everyone. Webatlas seized this opportunity and hired two summer interns. The task was fairly easy: "Revolutionize the way land registration data is used in local newspapers." After two hard-working months the resulting web application was used by a local newspaper with great results. The newspaper could finally showcase an interactive leaflet map displaying all real estate transactions in the area of interest. Behind the scenes the interns experienced a steep learning curve using PostGIS, GeoServer, Leaflet and a range of excellent plugins. Some of the more stable parts made it to the general use with an Open Source license on GitHub. Today. The solution is used in the majority of Norways newspapers - now showcasing more maps than ever! All made possible by two excellent interns, open data sets and well proven Open Source software components.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
24:48 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Sensor up your connected applications with OGC SensorThings API

This introduction will give an introduction and live demonstration of the OGC SensorThings API. The OGC SensorThings API provides an open and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. The OGC SensorThings API is a new OGC standard candidate. Unlike many existing OGC standards, SensorThings API is very simple and efficient. At the same time, it is also comprehensive and designed to handle complex use cases. It builds on a rich set of proven-working and widely-adopted open standards, such as the OGC Sensor Web Enablement (SWE) standards, including the ISO/OGC Observation and Measurement (O&M) and Sensor Observation Services (SOS). The main difference between the SensorThings API and the OGC SOS is that the SensorThings API is designed specifically for the resource-constrained IoT devices and the Web developer community. As a result, the SensorThings API follows the REST principles, the use of an efficient JSON encoding, and the use of the flexible OASIS OData protocol and URL conventions. In addition to introduce the specification, this talk will also demonstrate an end-to-end IoT application based on the SensorUp IoT platform, an open source implementation of the SensorThings API, including a server, javascript library, web dashboard and a Arduino library.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
20:29 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Opening Address Data around the World

With over 110 million points, OpenAddresses.io has grown to be the largest open database of address data in the world. Governments, developers and businesses are realizing that address data belongs in a commons where it can be easily maintained, used by all, and drive economic growth. These early efforts are now powering some of the world's best commercial geocoding systems, as well as crucial infrastructure like emergency responders. But there's more work to do. We need to reform outdated laws, expand coverage to new cultural contexts, untangle shortsighted licenses, and invent new modes of collaboration between the public and government. We'll cover how OpenAddresses started, how it can be used today, and how we expect it to grow into a definitive global resource.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:57 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Route Planning in your Database with pgRouting

pgRouting extends the PostGIS / PostgreSQL geospatial database to provide shortest path search and other network analysis functionality. This presentation will show the inside and current state of the pgRouting development, from its wide range of shortest path search algorithms to driving distance calculation or Traveling Sales Person (TSP) optimization. Additionally we will give a brief outlook and introduction of upcoming new features like the Vehicle Routing Problem (VRP) solver, and what we have in mind for future releases. We will explain the shortest path search in real road networks and how the data structure is important to get better routing results. Furthermore we will show how you can improve the quality of the search with dynamic costs and make the result look closer to the reality. You will also learn about difficulties and limitations of the library, and when pgRouting might not be not the right tool to solve your routing problem.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
31:40 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Mapping in GeoServer with SLD and CSS

Various software can style maps and generate a proper SLD document for OGC compliant WMS like GeoServer to use. However, in most occasions, the styling allowed by the graphical tools is pretty limited and not good enough to achieve good looking, readable and efficient cartographic output. For those that like to write their own styles CSS also represents a nice alternatives thanks to its compact-ness and expressiveness. Several topics will be covered, providing examples in both SLD and CSS for each, including: mastering multi-scale styling, using GeoServer extensions to build common hatch patterns, line styling beyond the basics, such as cased lines, controlling symbols along a line and the way they repeat, leveraging TTF symbol fonts and SVGs to generate good looking point thematic maps, using the full power of GeoServer label lay-outing tools to build pleasant, informative maps on both point, polygon and line layers, including adding road plates around labels, leverage the labelling subsystem conflict resolution engine to avoid overlaps in stand alone point symbology, blending charts into a map, dynamically transform data during rendering to get more explicative maps without the need to pre-process a large amount of views. The presentation aims to provide the attendees with enough information to master SLD/CSS documents and most of GeoServer extensions to generate appealing, informative, readable maps that can be quickly rendered on screen.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
28:12 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

A spatial view in the culture heritage domain

Culture heritage institutions are hosting digital historic map collection and the collections more and more allow spatial-temporal searching and georeferencing of its maps. At the Saxon State and University Library Dresden (SLUB) this lead to the development of the Virtual Map Forum 2.0, which is a spatial data infrastructure (SDI) for searching, visualization and georeferencing plane survey sheets. This SDI mainly relies on OpenLayers 3, Mapserver, GeoNetwork and GDAL. Beside that, tools for automatic georeferencing based on image recognition software have been developed and compared with the use of crowdsourcing tools for georeferencing. A further topic, on which culture heritage institutions are focusing is enrichment, transformation and merging of existing heterogeneous metadata sets. The goal is to allow better searching and utilization approaches for digital and analog objects. In the SLUB this lead to the development of the open source ETL-tool d:swarm, which supports the transformation and enrichment of metadata records. This opens possibilities for adding spatial identifier to large amounts of library objects, like pictures, newspaper articles or books and through this allows for a greater consideration of the spatial dimension in discovery systems. Another big topic is long term preservation, which becomes even more important with the growing number of digital native publications and datasets. Libraries and archives as experts of long term preservation and spatial data infrastructure provider, which are confronted with tasks and questions regarding the preservation of content. They therefor can benefit from an exchange of knowledge and work between each other. The presentation will give an insight into the world of culture heritage institutions. It will present topics, where FOSS4G and libraries can benefit from each other. Therefore it discusses different issues from within the SLUB where FOSS4G is used or could be used and spatial issues are affected. The main topics are spatial-temporal searching and visualization, georeferencing, metadata enrichment and long-term preservation.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:10 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

GIS-modelling of long-term consequences after a nuclear accident.

In order to evaluate consequences of deposited radioactive cesium (and other radioactive substances) in natural systems a GIS based model called Stratos has been developed. This model incorporates information regarding deposition, transfer to vegetation and animals, intervention levels and geographical distribution of animals. The presentation will use a case study which describes the possible environmental consequences for Norway due to a hypothetical accident at the Sellafield complex in the UK. The scenario considered involves an explosion and fire at the B215 facility resulting in a 1 % release of the total HAL 1 inventory of radioactive waste with a subsequent air transport and deposition in Norway. Air transport modeling is based on real meteorological data from October 2008 with wind direction towards Norway and heavy precipitation. This weather is considered to be quite representative as typical seasonal weather. Based on this weather scenario, the estimated fallout in Norway will be ~17 PBq of cesium-137 which is 7 times higher than fallout after the Chernobyl accident. The modeled radioactive contamination is linked with data on transfer to the food chain and statistics on production and hunting to assess the consequences for foodstuffs. The investigation has been limited to the terrestrial environment, focusing on wild berries, fungi, and animals grazing unimproved pastures (i.e. various types of game, reindeer, sheep and goats). The results of a model-run are maps for the chosen products, with categorized colors - giving the degree of consequences. A linked text file gives relevant numeric values for each color. The Stratos model is written in python which calls GRASS-functions and uses as gui for model setup. The model has been used for two reports at the Norwegian Radiation Protection Authority, and is currently being used and developed further in the "Centre for Environmental Radioactivity" (CERAD), cerad.nmbu.no.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
25:21 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

OGC GeoPackage in practice: Implementing a new OGC specification with open-source tools

GeoPackage is a new encoding standard created by the Open Geospatial Consortium as a modern alternative to formats like SDTS and Shapefile. Using SQLite, the single-file relational database can hold raster imagery, vector features and metadata. GeoPackage is an ideal data container for mobile devices such as smartphones, IoT devices, wearables, and even automobiles. We have created a few open-source tools to manipulate this exciting technology in a way that is useful to the geospatial community. Our goal with the GeoPackage specification implementations is simple: Create GeoPackages quickly and reliably while maintaining standard conformance. The single biggest issue we have faced is the speed in which large amounts of imagery can be disseminated to the end user. Data standards reliability was also a concern because we found many vendors interpreted the specification differently or to suite their own needs. Finally, the main problem GeoPackage was created was to solve was interoperability. We set out to create an implementation that would guide other parties towards making a data product that would function as well on one platform as it would on a completely different platform. Our initial implementation of the GeoPackage specification was created using Python 2.7.x. The software design was intended for command line use only in a script-friendly environment where tiling speed was paramount. The Gdal2tiles.py script was improved upon by harnessing the Python multiprocessing library so that multiple tile jobs could run simultaneously. The other piece of the workflow, creating GeoPackages, would be a separate development effort from scratch called tiles2gpkg parallel.py. In tiles2gpkg parallel.py, we implemented multiprocessing by writing to separate SQLite databases in parallel and then merging the tiled data sets into one compact database. This implementation worked well and increased the performance of producing these data sets; however, the command line design means that all but the most technically adept users would struggle to use the tools. With the initial Python implementation getting early-adopters a preview of GeoPackage in the short term, our team set out to make a production-quality GeoPackage API that could satisfy all user needs. Named Software to Aggregate Geospatial Data or SWAGD, we created a robust library for tiling raster data, packaging raster data stores into GeoPackages, and viewing either the raw tiles OR the finished GeoPackage products within a map viewer. Additionally, a Geopackage verification tool was created to foster community adoption. For more information, see our Github site here: https://github.com/GitHubRGI/swagd. Many open-source tools are being leveraged on the SWAGD project, including many common build and continuous integration tools including Github, TravisCI, WaffleIO, and Coverity. Using proven software development mechanisms like unit testing and code reviews we now have a consistent, reproducible, and inclusive GeoPackage implementation. We have an aggressive list of future capability that we would like to develop including ad-hoc routing on a mobile device, vector tile data sets, and even 3D support.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
19:36 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

On simulation and GIS, coupling and hydrology

This presentation shows how to better integrate simulation codes and Geographical Information Systems, and takes the example of Hydrological modelling integration into QGIS. Scientific modelling and simulations are present in a large number of areas. A significant proportion of simulation codes are applied spatially, at different levels, from a neighborhood scale up to worldwide areas. These simulation codes take spatial information as input data, and output results which are related to space too. But most of the time, they do not directly handle GIS data. Data types and data formats are different, and there is therefore a lot of effort to put into pre-processing and post-processing of the data to get it from GIS to the simulation codes and back. For example, determining the diffusion of a pollutant leak into underground water necessitates to get a DEM, location of the leak, geological data and more from the GIS, and transform it to simulation code input format. Then launch a simulation (on finite volumes e.g.), and convert the output into GIS files so that to be able to visualize spatial repartition of the pollutant according to time. The topic of this presentation is therefore to show how to better interact between simulation and GIS. We present the prevalent types of data for simulation, how they differ from GIS, and how we usually transfer from one type to another. Then we show how we worked towards better integration. Polygonal meshes are the most common way of representing 2D geometries for simulation purposes. Integrating simulation to a GIS requires storing georeferenced meshes in a databases (or using standard GIS file formats), and being able to use simulation values interpolated over the elements as a map layer. We show how to modify simulation codes to read directly a mesh from a GIS and write the results into a GIS. We implemented a new type of layer for QGIS, a mesh layer, which enables to display simulation results with high performances. This takes into account the temporal dimension. We also demonstrate how to integrate a simulation code into QGIS Processing so that it can be managed directly from within the desktop application. We illustrate these concepts with a demonstration of a full integration of a Hydrological simulation tool inside QGIS, with simulation management, custom user interface and strong integration of data between the simulation code and GIS data. In this sense the FREEWAT project started mid-2015, which aims at integrating multiple Hydrological codes into QGIS is also a good example of simulation and GIS integration. We end up with the perspectives for more global integration of simulation tools and GIS, and the work still to be done to bridge the gap between those two worlds.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:59 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

ZOO-Project 1.5.0: News about the Open WPS Platform

ZOO-Project is an Open Source Implementation of the OGC Web Processing Service (WPS) available under a MIT/X-11 style license and currently in incubation at OSGeo. ZOO-Project provides a WPS compliant developer-friendly framework to easily create and chain WPS Web services.This talk give a brief overview of the platform and summarize new capabilities and enhancement available in the 1.5.0 release. A brief introduction to WPS and a summary of the Open Source project history with its direct link with FOSS4G will be presented. An overview of the ZOO-Project will then serve to introduce new functionalities and concepts available in the 1.5.0 release and highlight their interests for applications developers and users. Evolutions and enhancements of the ZOO-Project WPS server (ZOO-Kernel) will first be detailed especially regarding compliancy (WPS 1.0.0 and 2.0), performance and scalability. The ZOO-Project optional support for Orfeo Toolbox and SAGA GIS will then be introduced, with details on the numerous new WPS Services (ZOO-Services) they provide. Use and connexion with other reliable open source libraries such as GDAL, GEOS, MapServer, GRASS GIS, CGAL will also be reviewed. Examples of concrete applications will finally be shown in order to illustrate how ZOO-Project components (ZOO-Kernel, ZOO-Services, ZOO-API and ZOO-Client) can be used together as a platform to build standard compliant advanced geospatial applications. Along with the new 1.5 release, this talk will also present how ZOO-Project is being developed, extended and maintained in the context of the EU funded PublicaMundi research project.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
24:29 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Leaflet vs. OpenLayers: which is best for our indoor maps?

Leaflet and OpenLayers are two well-known javascript libraries for embedding interactive maps in a web page, and each of them comes with pros and cons which are not obvious. Having worked with both libraries for indoor applications, we will in this presentation offer insight on which of them is more suited to a variety of situations and requirements, and which challenges they should overcome in the future.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:44 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Building OpenLayers Applications with QGIS

OpenLayers 3 is a powerful mapping library that can be used to create interactive mapping applications. Although it has a simple, intuitive and well-documented API, it requires knowledge of JavaScript to use, and no tools exist to leverage its functionality for more general GIS users. This presentation introduces an open-source QGIS plugin that creates web applications based on OL3, without the need of writing code manually. Elements of the web app are defined using a simple GUI, and QGIS GUI elements are used as well to define its characteristics (for instance, for defining the styling of layers or the extent of the view). The plugin can create different types of web apps, from simple maps used to browse data layers, to rich ones with GIS-like functionality, as well as others such as narrative maps. Apart from being an interface for writing OL3 code in a graphical way, it automates data deployment, and can import data into a PostGIS database or upload layers to a GeoServer instance. Altogether, these capabilities, along with QGIS data management functionality, allow to create a web app from QGIS in a very short time, as well as modifying or improving it later.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:12 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

MapCache: Fast and Featureful tile serving from the MapServer project

MapCache is a tiling server component designed to be efficient while still comprising all the features expected from a modern tiling solution. This presentation will give a brief presentation of the MapCache tiling solution, along with the recent developments that were added to reply to the needs of large scale installations (cache replication, load balancing, failsafe/fallback operations, large cache management, etc...)
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
19:50 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

WPS Benchmarking Session

The yearly Web Processing Service (WPS) benchmark. Variuos WPS implementations will be tested regarding their capabilities, compliancy to the standard and performance. Traditionally, each participating project designates individuals from their community to participate in this talk to introduce their project and summarize its key features. The focus this year will be on compliancy and interoperability. We will present the test set-up, participating WPS projects and the results of the benchmark.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:50 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Push it through the wire! Push it more, if it's wireless!

Today's web browsers, their rendering engines and JavaScript interpreters are able to display relatively big amounts of vector data. Moving from DOM rendering (as it was implemented with help of SVG in for examples OpenLayers 2) to Canvas (and further to WebGL -- as we are now having in OpenLayers 3 or Leaflet) enables us to display thousands of complex vector features, with complicated on-client vector data styling. With this possibility, we are facing now new types problems: how to send such amount of data through limited internet connection? If we have closer look at the problem, we can see clearly, that old database paradigm has raised one more time: we can not have all three attributes of data in one pot, but only 2 of them: speed of the delivered data or amount of delivered data or their topicality. If we take this limits into account and decide to deal with big amounts of data in fast way, topicality must be sacrificed. In the talk, we will demonstrate some possible solutions for this problem, using tiled vectors, generalization, aggregation of vector data. Also advantages, disadvantages of various new and popular vector formats, such as GeoJSON, TopoJSON or MapBox will be discussed. Geometric data do not have be rendered all the time in all scales and over whole area of interest, but only necessary portion of them. If displayed in smaller scales, aggregation and generalisation can take place on the server side. That implies, that using vector caching mechanism could be considered as well. But if we need direct interaction of the server input with cached vector data, mechanism for this must be defined as well. Also attribute data have to be transfered separately, if all the optimisation was put in the vector geometries. Also possible steps between cached data and real-time data will be discussed.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
24:22 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Jsonix: Talking to OGC Web Services in JSON

Can you talk to OGC Web Services in JSON instead of XML? You can - with Jsonix, a powerful JavaScript tool for XML - JSON conversion. JSON has probably already replaced XML as a "lingua franca". JSON is much lighter and easier to use than XML, especially in JavaScript-based web apps. In the context of GIS, web mapping is dominated by JavaScript libraries like OpenLayers and Leaflet, which speak JSON natively. But what about the standards? Open Geospatial Consortium defines more than 50 specifications with more than 100 individual versions. Technically almost all of them are XML-based and defined by XML schemas. These are de jure and de facto standards, widely used and well supported. So you still need XML processing in JS web mapping apps. Processing XML is no rocket science, but it's seldom a pleasure to implement. The OL3 KML parser is about 2.5KLoc of dense XML parsing. Even a very simple WMS GetCapabilities format is almost 1 KLOC. From this code around 90% is pure XML parsing and only 10% is the processing of the payload. Would not it be nice if we could talk to the OGC Web Services directly in JSON? So that the developers could focus on the 10%, the payload processing, and cut off the 90% (XML handling) of the effort. Jsonix is an open source library for XML - JS conversion which makes it just possible. With Jsonix you can take an XML Schema and generate XML - JS mappings. These mappings allow you to parse XML in the original schema and get your data in pretty JSON. It also works in the opposite direction: you can serialize JSON in XML, which would correspond to the original XML Schema. What makes Jsonix unique is that it is type and structure-safe. On the JSON side, you will get types and structures exactly as they are defined in the original XML Schema. For instance, xs:decimal is converted into a number in number in JSON, repeatable elements are represented by arrays etc. You just need the corresponding mapping. You can generate Jsonix mappings on your own or use one of the pre-generated mappings. The (unofficial) OGC Schemas Project compiles and provides mappings for many of the popular OGC schemas (OWS, WMS, WFS, CSW, SLD and many more). This presentation gives an overview of Jsonix demonstrates its usage by a number of examples.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
23:26 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Big data analysis with Tile Reduce and Turf.js

Tile Reduce is a new open source map reduce frame work for analyzing massive geo data. Tile reduce is a tile analysis framework built on the javascript GIS library Turf.js. It runs on your local computer or in the AWS cloud and scales to run thousands of processors in parallel. At Mapbox we use Tile Reduce to detect issues in global street vector data like OpenStreetMap, data comparison and data conflation. This talk will walk through the architecture of Tile Reduce, highlight advantages, limitations and future developments.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
24:31 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Dynamic dashboards with D3.js and CartoDB

NextGIS has been busy working on a new stack of geospatial software for the past few years and we're finally ready to present what we've accomplished. Our stack consists of 4 major components: web (NextGIS Web), mobile (NextGIS Mobile), desktop (NextGIS QGIS) and data management (NextGIS Manager). Three of those components are brand new, developed by NextGIS alone and were released just recently. For the fourth component, we participate in QGIS development since 2008 and use its codebase for our desktop component. The main focus of the stack is tight integration, ease of use and modularity. New stack features unique features, to name just the few: plugable renderers for NextGIS Web, multi-layer support for NextGIS Mobile, super-fast rendering and great formats support for NextGIS Manager and all-around integration with NextGIS QGIS. The presentation will provide an overview and will look at general architecture, use cases and plans for future development.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
1:03:54 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

FOSS4G Seoul 2015 - panel discussion

  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
25:41 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Don't Copy Data! Instead, Share it at Web-Scale

Since its start in 2006, Amazon Web Services has grown to over 40 different services. Amazon Simple Storage Service (S3), our object store, and one of our first services, is now home to trillions of objects and core to many enterprise applications. S3 is used to store many kinds of data, including geo, genomic, and video data and facilitates parallel access to big data. Netflix considers S3 the source of truth for all its data warehousing.The goal of this presentation is to illustrate best practice for open or shared geo-data in the cloud. To do so, it showcases a simple map tiling architecture, running on top of data stored in S3 and uses CloudFront (CDN), Elastic Beanstalk (Application Management), and EC2 (Compute) in combination with FOSS4G tools. The demo uses the USDA��s NAIP dataset (48TB), plus other higher resolution city data, to show how you can build global mapping services without pre-rendering tiles. Because the GeoTIFFs are stored in a requester-pays S3 bucket, anyone with an AWS account has immediate access to the source GeoTIFFs at the infrastructure level, allowing for parallel access by other systems and if necessary, bulk export. However, I will show that the cloud, because it supports both highly available and flexible compute, makes it unnecessary to move data, pointing to a new paradigm, made possible by cloud computing, where one set of GeoTIFFs can act as an authoritative source for any number of users.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:00 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

GeoPackage and how open source is changing the way governments think about standards

Government is a great sector in which to use geospatial technology to solve problems at scale. This geospatial technology typically has varying degrees of quality and cost as you would expect in any market. Combine the two with the fact that the ecosystem of systems, large and small, is very diverse, creating varying challenges. With this in mind, governments are now realizing how their decisions impact their future capabilities. In this talk, we will discuss GeoPackage, an OGC encoding standard and the challenges it was created to solve. We were encountering a problem with how data was being created, disseminated, and used. With the rise of mobile computing devices raster images in various native formats were being disseminated to a wider audience to use and visualize information. These raster images were typically enormous and uncompressed in some cases and compressed but painfully slow in other cases. Computing resource availability varied across computing environments. Some end users were converting these large raster images to more friendly or optimized formats to do their daily jobs. This leads to massive data reprocessing efforts across many different areas, all of which are mostly avoidable if the source would simply produce relevant, fast-performing data in a format that satisfies the broadest audience. Many vendors have tried to solve this problem with their own custom or proprietary solutions. Full stack vendor solutions come with hefty price tags in the form of licenses, support contracts, or sometimes both. These solutions can and often do solve the immediate problem however they have side effects that reach far beyond the immediate. Vendor-specific technology islands therefore appear, beholden to a certain proprietary implementation simply because it would be too expensive or too involved to do otherwise. Proprietary data created for one system did not necessarily work in another system. Tools needed to be created, re-created, or modified to handle formats that did not work on their target platform. Data interoperability between geospatial groups is the first casualty. Glue code is then created to bridge the gap between the offending incompatible data and the desired data format of the new end-user. Government entities are quickly realizing that this makes no sense. Extra processing causes bottlenecks in downstream workflows and can quickly cause untenable requirements in areas like disaster recovery. Incompatibility in data makes it even harder to share crucial information between government organizations and non-government organizations alike. It is with these types of open standards that governments can maintain the control of their data creation and management. GeoPackage was created to free data from the constrictions of proprietary formats and is already paying dividends to government groups. Current GeoPackage development tools will be discussed as well as how early adopters are leveraging this new data specification and subsequent tools to push geospatial products to the end user.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
19:41 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

DigitalGlobe and Open Source

Adding some important and pertinent information to this abstract with respect to the recent tragic events in Nepal. DigitalGlobe, in responding to the devastating earthquake in Nepal, has openly licensed both pre-event and post-event imagery, as well as openly licensed the results of our Tomnod campaign, which has crowdsourced information from nearly 50,000 volunteer contributors to assess damage and displaced people in Nepal. DigitalGlobe is working with first responders, aid relief and NGOs including Kathmandu Living Labs, Humanitarian OpenStreetMap Team, the UN, IFRC and American Red Cross. We are providing important information to disperse relief to the growing number of displaced people. The work we have done has been featured by CNN, CCTV, Mashable, the Atlantic and many more. Please reference links below. This is a poignant example of how Geospatial data, provided in the open can benefit millions of people who need help. http://www.cnn.com/videos/business/2015/05/01/wbt-intv-lake-bullock-nepal-digitalglobe.cnn http://www.theatlantic.com/technology/archive/2015/05/the-mapmakers-helping-nepal/392228/ http://www.citylab.com/tech/2015/04/how-amateur-mappers-are-helping-recovery-efforts-in-nepal/391703/ http://mashable.com/2015/05/06/landslide-nepal-photos-before-after/#:eyJzIjoidCIsImkiOiJfdTVjdzgyb2M5aGRnMnZ1bCJ9 Original abstract: DigitalGlobe operates a constellation of high resolution, high accuracy satellites. Imagery from DigitalGlobe can be seen in Mapbox Satellite, CartoDB, Google Maps, HERE Maps, Bing Maps, Apple Maps and is often used for the purposes of contributing, editing and validating for OpenStreetMap. Over the years, DigitalGlobe has provided both imagery and software processing tools with an Open Source license. This includes post-event imagery for Typhoon Haiyan in the Philippines and the Japanese Tsunami. Recently, we open sourced a software toolkit called "Mr Geo" http://defensesystems.com/articles/2015/01/14/nga-open-sources-geospatial-analysis-tool.aspx This presentation will give an overview of DigitalGlobe, our geospatial technology and our services we are providing to the Open Source community.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
20:07 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

ngeo: a companion library for OpenLayers 3

ngeo is an open-source JavaScript library that aims to ease the development of web GIS applications based on AngularJS and OpenLayers 3. More specifically, ngeo provides Angular components, namely "services" and "directives", that can be combined together in different ways, based on the need of the application. This talk is a general presentation of ngeo. We will present some of the features provided by the library, through concrete examples. We will also present the design choices we have made, and why we have made this design choices. AngularJS, as a very popular framework, has received (severe) criticism lately. We will report on our experience with AngularJS, discuss its "good parts", and how we mitigate its "bad parts". With ngeo we define ? what we think ? is a good way to use AngularJS. ngeo, for example, includes guidelines for application developers, which have turned out to be key for the development of robust and high-performance applications. This talk is for anyone interested in AngularJS and OpenLayers 3. Come to this talk if you're interested to know how we use ngeo to develop applications combining AngularJS and OpenLayers 3.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
19:14 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Cadasta: Securing Property Rights with Open-Source

Much of the world currently does not have secure property and land tenure rights. Communities and individuals need low-cost tools to enable them to advocate for themselves. The Cadasta Foundation is building an open-source platform to securely enable these groups to document their land rights. This talk will review the design decisions taken into account, the technology underlying Cadasta, and the future road map. Individuals interested in land rights management and/or the challenges in implementing technology in difficult environments will be especially interested in this presentation.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:30 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

OL3-Cesium: 3D for OpenLayers maps

OL3-Cesium is a new Open Source JavaScript library for adding a Cesium 3D globe to applications based on OpenLayers 3. Concretely, OL3-Cesium creates and automatically synchronizes the 3D globe by reading the raster and vector layers from the 2D map. Additionally, the view parameters (center, resolution, rotation) are bidirectionally synchronized allowing shared 2D/3D interactions. This talk is a general presentation of OL3-Cesium. We will present practical cases of map enhancement with 3D, show code and explain what happens under the hood. We will discuss current status and work in progress. Our main interests will be: - easy kick-start of a side-by-side or stacked views application; - handling of different raster and vector projections; - positioning vectors on terrain or at absolute 3D coordinates; - editing and picking Points Of Interest in a unified 2D/3D manner; - streaming and displaying vector data; - streaming and displaying buildings. OL3-Cesium was started by three companies from the OpenLayers community; we will discuss the benefits of the community, notably in terms of simplicity, speed of development, ease of maintenance, and sharing of complex code. This talk is for anyone interested in adding 3D to OpenLayers 3. Come to this talk to discover new ways of displaying and interacting with your map.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
out of 2 pages
Loading...
Feedback

Timings

  117 ms - page object
   94 ms - search
    4 ms - highlighting
    1 ms - highlighting/32099
    1 ms - highlighting/32085
    2 ms - highlighting/32062
    2 ms - highlighting/32166
    0 ms - highlighting/32160
    2 ms - highlighting/32159
    2 ms - highlighting/32098
    3 ms - highlighting/32029
    1 ms - highlighting/32168
    2 ms - highlighting/32126
    1 ms - highlighting/32138
    1 ms - highlighting/32124
    2 ms - highlighting/32132
    2 ms - highlighting/32134
    2 ms - highlighting/32152
    2 ms - highlighting/32162
    2 ms - highlighting/32145
    1 ms - highlighting/32055
    1 ms - highlighting/32051
    1 ms - highlighting/32040
    0 ms - highlighting/32158
    1 ms - highlighting/32102
    1 ms - highlighting/32164
    1 ms - highlighting/32125
    1 ms - highlighting/32103
    1 ms - highlighting/32135
    1 ms - highlighting/32101
    2 ms - highlighting/32061
    1 ms - highlighting/32056
    1 ms - highlighting/32069
    1 ms - highlighting/32060
    0 ms - highlighting/32054
    1 ms - highlighting/32161
    2 ms - highlighting/32156
    0 ms - highlighting/32083
    1 ms - highlighting/32095

Version

AV-Portal 3.7.0 (943df4b4639bec127ddc6b93adb0c7d8d995f77c)