Show filters Hide filters

Refine your search

Publication Year
1-36 out of 74 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
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
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
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
26:13 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Advanced Security with GeoServer and GeoFence

The presentation will provide an introduction to GeoServer own authentication and authorization subsystems. We’ll cover the supported authentication protocols, such as from basic/digest authentication and CAS support, check through the various identity providers, such as local config files, database tables and LDAP servers, and how it’s possible to combine the various bits in a single comprehensive authentication tool, as well as providing examples of custom authentication plugins for GeoServer, integrating it in a home grown security architecture. We’ll then move on to authorization, describing the GeoServer pluggable authorization mechanism and comparing it with proxy based solution, and check the built in service and data security system, reviewing its benefits and limitations. Finally we’ll explore the advanced authentication provider, GeoFence, explore the levels on integration with GeoSErver, from the simple and seamless direct integration to the more sophisticated external setup, and see how it can provide GeoServer with complex authorization rules over data and OGC services, taking into account the current user, OGC request and requested layers to enforce spatial filters and alphanumeric filters, attribute selection as well as cropping raster data to areas of interest.
  • 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
18:37 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Satellite Snow Cover Products Evaluation and Validation Platform Developed Entirely With Floss Software

The monitoring of snow cover extent is important for the management of natural resource, extreme events prediction such as snowmelt floods, avalanches etc. The current status is that the network of weather stations is too sparse in regions with seasonal snow cover to provide reliable snow monitoring and impact applications. Remote sensing can regularly provide maps of snow cover extent, under limitations imposed by satellite cycles or cloud cover. A number of daily or synthesis snow cover extent products, covering Romania, with different resolutions and specifications, are available for free (e.g. GLOBSNOW, CryoLand, H-SAF, IMS). These products were homogenized and included, along with reference and in-situ data, into an application that make possible for user to inspect, process, analyze and validate the information, using a web based interface. The platform, created by National Meteorological Administration of Romania offers services based on Open Geospatial Consortium standards for data retrieval (WMS, WCS, WFS) and server-side processing (WPS, WCPS). The services were built upon open source solutions such as GeoServer, OpenLayers, GeoExt, PostgreSQL, GDAL, rasdaman. The application is composed of several software modules/services. The modules are split into two categories: server-side modules/services and client side modules - responsible for interaction with the user. A typical usage scenario assumes the following steps: 1. The user is operating the client functionality to select a temporal and spatial slice from a product cube (e.g. 5 months archive of daily CryoLand FSC data); 2. The users select a statistic method to be applied; 3. The request is sent to the server side processing applications wrapped as WPS or WCPS calls; 4. The process will trim/slice the coverage cube, perform the statistic operation for the pixels within the ROI for each day in the selected time interval; 5. The results are sent back encoded in a standard file format; 6. The web client display the results in a relevant form.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:33 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

GeoServer for Spatio-temporal Data Handling With Examples For MetOc And Remote Sensing

This presentation will provide detailed information on how to ingest and configure SpatioTemporal in GeoServer to be served using OGC services, with examples from WMS and WCS services. Topics covered are as follows: * Discussion over existing data formats and how to preprocess them for best serving with GeoServer * Configuring SpatioTemporal raster and vector data in GeoServer * Serving SpatioTemporal raster and vector data with OGC Services Tips and techniques to optimize performance and allow maximum exploitation of the available data The attendees will be provided with the basic knowledge needed to preprocess and ingest the most common spatiotemporal data from the MetOc and Remote Sensing field for serving via GeoServer.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
21:21 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

High-precision open lidar data enable new possibilities for spatial analysis in the canton of Zurich/Switzerland

The department of geoinformation of the canton of Zurich/Switzerland has carried out a high-resolution laser scanning (LIDAR) last year over the entire canton of Zurich. The extensive data (8 pts / m2) have now been evaluated, and a digital surface (DSM) and terrain model (DTM) created (dot grid of 50 cm and horizonal and vertical accuracies of 20 cm, resp. 10 cm. This is the first time high-resolution elevation data is widely available for the entire canton of Zurich. In the past, lidar data have been collected only for small-scale projects. As a novelty, the department has decided to provide the lidar data and its derived products, i.e. DTM and DSM, as open data to the public. With this decision new standards are set not only in terms of accuracy and scope, but also in the usage as open government data. The lidar data can provide valuable support for example in the areas of infrastructure, urban planning, regional planning, natural hazard assessment, forestry, environment, energy, line survey, solar potential analysis, surveying, archeology, agriculture, water or noise. Due to the planned repetition cycle of four years even time series and monitoring projects are possible. Therefore it is not surprising, that since the opening as open data, many interesting applications using this data have been created. The presentation will show the high-resolution data and its possible usage for terrain-visualizations. A selection of the most appealing visualizations will be demonstrated, e.g. an Oculus Rift version enabling the user to navigate through virtual reality. It will further give an insight in the challenge of opening up the LIDAR?data for the public, i.e. setting up an open-data strategy in the cantonal administration of Zurich.
  • 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
23:21 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

GeoCouch: Operating multidimensional data at scale with Couchbase

Couchbase is a distributed document-oriented NoSQL database. You store the data as JSON and then build indexes with simple JavaScript functions. This talk is about the multidimensional index capability of Couchbase. This means you can index not only geographic data (encoded as GeoJSON) but any additional numeric attributes you like. Such a multidimensional query might be used for an application about car sharing. You would e.g. query for all the cars in a certain area, but you're also interested in additional attributes. Let's say you want to display only cars where at least four people fit in. Or you want one with air-conditioning. Such attributes would be the additional dimensions. In this case it would be 4-dimensional query, two for the location and two for additional attributes. Quite often GeoHash is used for implementing a spatial index, which has some limitations. A notable one is that you need to know that maximum range of your data upfront as it's a space partitioning algorithm. It is good enough for purely geospatial data, but as soon as additinal attributes like time are needed, it might become an issue. GeoCouch takes a more traditional approach like PostGIS and uses an R-tree which is data partitioning, hence you don't need to know the extent up-front. Another focus of this talk will be on the operational strengths Couchbase has. One thing is the web interface that makes administrating clusters very easy, even when there's a failure. The other thing is that you can easily restart servers, e.g. when a Linux Kernel upgrade is due, without any downtime on the full cluster. The system stays operational and handles those upgrades gracefully. In the end you will have a good overview on why you really want to use a multidimensional indexing for your remote sensing data or points of interest in your location aware mobile app. GeoCouch is fully integrated into Couchbase, there's no additional setup needed to get started. All source code from Couchbase is licensed under the Apache 2.0 License. Links: - Couchbase: http://www.couchbase.com/ - Source code: https://github.com/couchbase/manifest - GeoCouch: https://github.com/couchbase/geocouch
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
23:44 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

CartoDB Basemaps: a tale of data, tiles, and dark matter sandwiches

CartoDB is an open souce tool and SaaS platform that allows users to make beautiful maps quickly and easily from their own data. To complement our users needs, we launched last year our free-to-use open source OSM based basemaps Positron and Dark Matter (https://github.com/CartoDB/CartoDB-basemaps), designed in collaboration with Stamen to complement data visualization. While architecturing them, we had several compromises in mind: they had to be powered by our existing infrastructure (powered by Mapnik and PostGIS at its core), they had to be scalable, cacheable but frequently updated, customizable, match with data overlays, and, last but not least, they had to be beautiful. This talk is the tale of the development process and tools we used, how we implemented and deployed them and the technology challenges that arose during the process of adapting a dynamic mapping infrastructure as CartoDB to the data scale of OSM, including styling, caching, and scalability, and how (we think) we achieved most of those. I will also talk about the future improvements that we are exploring about mixing the combination of basemap rendering with data from other sources, and how you can replicate and tweak those maps on your own infrastructure.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
22:46 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Use case of a dual open strategy in the canton of Zurich/Switzerland

With a dual 'open'-strategy the department of geoinformation at the canton of Zurich/Switzerland opts for a strategic orientation towards open source and open data: Open in the sense of an open web-mapping- infrastructure based on open source components: Mapfish Appserver was developed as a framework for building web map applications using OGC standards and the Mapfish REST protocol. It is freely available under the new BSD-license (http://mapfish-appserver.github.io/). The Ruby on Rails gem comes with the following out-of-the box features: - Organize maps by topics, categories, organisational units, keywords and more - Combine maps with background and overlay topics with adjustable opacity - Import UMN Mapserver mapfiles to publish new topics within seconds - Fully customizable legends and feature infos - Creation of complex custom searches - Rich digitizing and editing functionality - Role-based access control on topic, layer and attribute level - Access control for WMS and WFS - Rich library of ExtJS 4 based map components - Multiple customizable viewers from minimal mobile viewer to full featured portal - Multi-site support - Built-in administration backend - Self-organized user groups maps.zh.ch, the official geodata-viewer of the canton of Zurich, was developed using Mapfish Appserver. It contains more than 100 thematic maps and is considered an indispensable working tool for everyone working with spatial data in the canton of Z?rich/Switzerland. 'Open' in the sense of Open Government Data: Zurich is the first canton participating in the national open data portal opendata.admin.ch. The portal has the function of a central, national directory of open data from different backgrounds and themes. This makes it easier to find and use appropriate data for further projects. The department of geoinformatics aims to open as many geo-datasets as possible for the public by publishing them on the national OGD-portal. The open geodata is issued in form of web services ? Web Map Services (WMS), WebFeature Services (WFS) and Web Coverage Services (WCS) - and contains a wide range of geodata from the fields of nature conservation, forestry, engineering, infrastructure planning, statistics to high resolution LIDAR-data.
  • 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
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
29:02 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Improving public health delivery in northern Nigeria using open source technologies

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

Case study: A full-fledged cutting-edge FOSS4G map production system

The development and the usage of National Land Survey of Finland's dynamic and high performance map production system is described in this presentation. The system is currently in use and serves map images both to customers and to NLSFI production systems. The data in the map production system are open data and being updated on a weekly basis. When the data get updated, a RSS-feed is generated. Based on the feed, the map products are updated. Data is stored, updated and replicated in PostGIS. Map pictures are rendered in GeoServer. The visualization of the maps is based on SLD-stylesheets. SLD-stylesheets enable the same data to be visualized in several different ways. GeoServer in conjunction with SLD-stylesheets offers a Web Map Service (WMS). Map images are delivered via a high performance MapCache Web Map Tile Service (WMTS) and as image files via NLSFI download service. The system is designed to be expandable and is currently being further developed to enable the pro-duction of on-demand printed maps.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
23:23 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Open Source and Open Standard based decision support system: the example of lake Verbano floods management.

The Locarno area (Switzerland, Canton Ticino) is exposed to lake floods with a return period of about 7-8 years. The risk is of particular concern because the area is located in a floodplain that registered in the last decades a great increase in settlement and values of the real estates. Moreover small differences in lake altitude may produce a significant increase in flooded area due to the very low average slope of the terrain. While fatalities are not generally registered, several important economic costs are associated, e.g.: damages to real estates, interruption of activities, evacuation and relocation and environmental damages. While important events were registered in 1978, 1993, 2000, 2002 and 2014 the local stakeholder invested time and money in the set-up of an up-to-date decision support system that allows for the reduction of risks. Thanks to impressive technological advances the visionary concept of the Digital Earth (Gore 1992, 1998) is being realizing: geospatial coverages and monitoring systems data are increasingly available on the Web, and more importantly, in a standard format. As a result, today is possible to develop innovative decision support systems which mesh-up several information sources and offers special features for risk scenarios evaluation. In agreement with the exposed view, the authors have recently developed a new Web system whose design is based on the Service Oriented Architecture pattern. Open source software (e.g.: Geoserver, PostGIS, OpenLayers) has been used throughout the whole system and geospatial Open Standards (e.g.: SOS, WMS, WFS) are the pillars it rely on. SITGAP 2.0, implemented in collaboration with the Civil protection of Locarno e Vallemaggia, combines a number of data sources such as the Federal Register of Buildings and Dwellings, the Cantonal Register of residents, the Cadastral Surveying, the Cantonal Hydro-meteorological monitoring observations, the Meteoswiss weather forecasts, and others. As a result of this orchestration of data, SITGAP 2.0 serves features that allows, for example, to be informed on active alarms, to visualize lake level forecasts and associated flooding areas, to evaluate and map exposed elements and people, to plan and manage evacuation by searching for people living in particular areas or buildings, by registering evacuation actions and by searching for evacuated people. System architecture and functionalities, and consideration on the integration and accessibility of the beneath information together with the lesson learnt during the usage of the system during the last floods of November 2014, provides interesting discussion points for the identification of current and future needs.
  • 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
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
21:51 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Taking dynamic web mapping to 1:100000 scale

CartoDB is growing to be one of the biggest mapping platform for the masses, being powered by a fully open-source stack, with PostgreSQL, PostGIS, Mapnik and Leaflet at its core. Our aim is to democratize map and geographical data visualization, making it easy for non-GIS people to create simple maps using the CartoDB Editor, but still keeping all the power and flexibility of the underlying components available to advanced users, with a variety of building blocks ranging from the frontend with CartoDB.js and Torque to the backend with the Map, SQL and Import API, parts of what we call the CartoDB Platform. Serving dozens of millions of map tiles daily has its own set of problems, but when they are being created by hundreds of thousands of users (which have their own database and can alter everything from styling, to the data sources and the SQL queries applied) everything turns out to be a big source of challenges, both development and operationally speaking. This talk will go through our general architecture, some of the decisions we’ve had to take, the things we’ve learned and the problems we’ve had to tackle through the way of getting CartoDB to scale at our level of growth, and how we're giving back to the community what we've discovered though the process.
  • 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
24:37 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Gis Server with Golang.

GIS Server architecture with Golang. Find the better way of Golang GIS Server.
  • 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
22:23 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Use case of Disaster Management System by using Geopaparazzi and MapGuide Open Source

In recent years, large-scale disasters have occurred in the countries of Asia including Japan, rapid collection and sharing of disaster information is required in order to provide relief and support speedy restoration of civic services. This presentation discusses the integration and customization of FOSS4G field survey tools and Web GIS server to facilitate aggregation and rapid sharing of disaster related field information. Further, the system also provide realtime interaction between field party and coordination team. A case study of practical use of the system at the Osaka Water General Service (OWGS) Corporation will be demonstrated to present the salient features of the system. The main capability of the system usability is normal as well as disaster situation will be highlighted.
  • 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
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
29:05 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Geopaparazzi, state of the art

Geopaparazzi is an application for fast field surveys. Its simplicity and the possibility to use it on as good as any android smartphone makes it a trusty field companion for engineers and geologists, but also for tourists who wish to keep a geodiary and any user that needs to be aware of his position even in offline mode. In Geopaparazzi it is possible to create text, picture and sketch notes and place them on the map. Notes can also be complex and form based in order to standardize surveys in which many people need to be coordinated. In the last years the support for the visualization of spatialite vector layers and recently also editing possibilities for spatialite poligonal datasets has been added, allowing for some simple-yet-powerfull possibilities on vector data. Desktop tools are supplied to bring datasets from the GIS environment to Geopaparazzi and back. The presentation will focus on the most important features of Geopaparazzi as well as the latest additions to the application in order to give a complete idea of the state of the art of the project.
  • 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
21:08 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Presentation of GNOSIS SDK: High performance 3D visualization SDK and GIS software

An introduction and demonstration of the capabilities of the GNOSIS SDK ( http://ecere.ca/gnosis ), high performance 3D geospatial visualization software built atop our open-source Ecere Software Development Kit ( http://ecere.org ). The GNOSIS SDK offers a cross-platform object-oriented API for visualizing geospatial raster imagery, vector data and elevation models in both 3D and cartographic projections. It also features GNOSIS Cartographer, a GIS software allowing to import, visualize, edit, tile, optimize, style and analyze geospatial data. Vector shapefiles, GeoTIFF imagery and ASCII Grid heightmaps are readily supported, while a plug-in system allows to extend support and functionality through additional programming. Through tiling and resampling all supported types of data (raster, vector and elevation) at multiple scales, GNOSIS can handle large planetary scale data sets (up to 1 mm resolution) with consistent performance. Elevation data models, including high resolution point clouds, can drive the terrain rendering system which performs dynamic mesh optimization based on elevation variation. All types of map data can also be draped on top of the terrain, and styles can be modified in real-time. Styling can be applied with cascading style sheets based on the values of associated data records. GNOSIS also supports geo-referencing and rendering 3D models. GNOSIS also provides a map client / server architecture through its own highly efficient protocol, while it will also support serving and accessing data through widely used protocols such as WFS and WMS. Although the GNOSIS SDK itself is currently not open-source, we hope to be in a position to release it under an open-source license in the future and possibly apply for it to become an OSGeo software project.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
23:46 FOSS4G, Open Source Geospatial Foundation (OSGeo) English 2015

Modifications to Web Processing Service Standard For Client-Side Geoprocessing

Nowadays we see the rapid growth of solutions number for spatial data processing in the Web (i.e. geoprocessing). One of the main trends of Web geotechnologies evolution is the transition from Web map applications to the Web GIS applications, which are supplement the maps delivery with the analytic tools providing to the end user through Web interface. The only general open standard describes implementation rules for Web geoprocessing services. This is the Open Geospatial Consortium Web Processing Service standard (OGC WPS), which is server-oriented standard [Schut at al., 2007]. Moreover, the vast majority of currently used solutions (both open source and proprietary) are server-oriented, i.e. assume the using for computations the server resources only. However, some researchers underline that it is possible way to transmit the executable code to the client for client-side computations and geoprocessing [Keens at al., 2007]. Also, some general Web architecture concepts assumes the effectiveness of client-side computations, e.g. Fog Computing concept [Hong at al., 2013]. Our practical experience also shows that in some cases it is useful to have ability of client-side geoprocessing, which is not opposite but complement technology to the server-side processing technologies. In addition, we believe that it is more useful to have the ability to run the same processing tool by choice on server or client side. We name such double-sided services as Hybrid Geoprocessing Web Services (HGWS) [Panidi, 2014]. We study and discuss the approaches to fill the gap of client-side geoprocessing general schema. For this purpose, we implemented previously the getProcess request as addition to the WPS protocol [Panidi, 2014]. Additionally at the previous steps of our study, we proposed a possible structure of getProcess request and draft XML schema for its response, which describes the list of executable resources and their dependencies [Kazakov at al., 2015]. Currently we working on detailed methodology of processing tools implementation, and prototypes testing in use cases of geospatial data processing for small-scale research projects. We use the Python programming language as primary development tool, because of its applicability to build both server- and client-side processing tools using single core program code. We use Python also for implementation of needed infrastructure components, such as HGWS server that supports the getProcess request/response performing, and client-side runtime environment that provides executable code orchestration on the client. Achieved results need to be discussed widely and carefully. However, main conclusion of our current work is that client-side geoprocessing schema in general could be relatively simple and compatible backward with current standards. The HGWS concept is applicable when implementing client-side geoprocessing Web services in small-scale projects and could be the entering point for study of distributed geoprocessing systems implementation.
  • Published: 2015
  • Publisher: FOSS4G, Open Source Geospatial Foundation (OSGeo)
  • Language: English
out of 3 pages
Loading...
Feedback

Timings

  110 ms - page object
   82 ms - search
    3 ms - highlighting
    0 ms - highlighting/32101
    1 ms - highlighting/32140
    1 ms - highlighting/32059
    1 ms - highlighting/32051
    2 ms - highlighting/32102
    1 ms - highlighting/32055
    0 ms - highlighting/32058
    1 ms - highlighting/32104
    2 ms - highlighting/32040
    2 ms - highlighting/32162
    1 ms - highlighting/32100
    0 ms - highlighting/32081
    1 ms - highlighting/32021
    1 ms - highlighting/32132
    1 ms - highlighting/32082
    2 ms - highlighting/32156
    2 ms - highlighting/32130
    1 ms - highlighting/32061
    1 ms - highlighting/32128
    0 ms - highlighting/32099
    1 ms - highlighting/32152
    1 ms - highlighting/32098
    1 ms - highlighting/32080
    0 ms - highlighting/32103
    0 ms - highlighting/32069
    1 ms - highlighting/32060
    0 ms - highlighting/32107
    0 ms - highlighting/32105
    1 ms - highlighting/32134
    2 ms - highlighting/32135
    2 ms - highlighting/32164
    0 ms - highlighting/32127
    1 ms - highlighting/32112
    1 ms - highlighting/32159
    1 ms - highlighting/32167
    2 ms - highlighting/32126

Version

AV-Portal 3.7.0 (943df4b4639bec127ddc6b93adb0c7d8d995f77c)