OSGeo Planet

GeoServer Team: GeoServer 2.13-beta released

OSGeo Planet - 7 hours 57 min ago

We are happy to announce the release of GeoServer 2.13-beta. Downloads are available (zipwar, and exe) along with docs and extensions.

This is a beta release of GeoServer made in conjunction with GeoTools 19-beta.

We want to encourage people to test the release thoroughly and report back any issue found. With no further delay, let’s see what’s new, that is, what is there to test!

Isolated Workspaces

The concept of an “Isolated Workspaces” has been added to GeoServer, to allow for reusing a namespace among multiple workspaces. In particular, an isolated workspace allows reuse of a namespace already used by another workspace, but its resources (layers, styles, etc …) can only be retrieved when using that workspace’s virtual services and will only show up in those virtual service capabilities documents.

When reusing a namespace among workspaces, exactly one of those must be non-isolated, and the rest must be isolated; i.e. isolated workspaces have no restrictions in namespaces usage but the existing restrictions still apply for non isolated workspaces.

For more details, refer to the original proposal.

GeoWebCache REST API

Two new endpoints have been added to the GeoWebCache REST API:

  • /gwc/rest/blobstores:
    • GET /gwc/rest/blobstores for a list of the blobstores
    • GET /gwc/rest/blobstores/{blobStoreName} for details about a single blobstore
    • PUT /gwc/rest/blobstores/{blobStoreName} to create or update a blobstore
    • DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
  • /gwc/rest/gridsets:
    • GET /gwc/rest/gridsets for a list of the gridsets
    • GET /gwc/rest/gridsets/{gridSetName} for details about a single gridset
    • PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
    • DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset

API docs for these endpoints will be added to the GeoServer documentation shortly. Until then, the request body syntax for PUT requests closely matched the equivalent structures in geowebcache.xml: BlobStores and GridSets.

The ArcGISCache backed layers are now also configurable via the REST API.

This release sees a major reworking of the configuration system in GeoWebCache that will allow for plugging in alternate configuration persistence mechanisms in future. While these changes should be largely invisible to users, it is a huge update that impacts all of GeoWebCache. However, due to these changes, we ask that you please test the embedded GeoWebCache.

UI Improvements

Entering in URLs for data files has been improved with autocomplete – now GeoServer will scan the path that has already been typed, and suggest existing files within that path.

In addition, autocomplete support has been added to a number of dropdowns which contain a long list of values, such as stores or layers. You can now start typing the name of an option, and the visible options will be filtered to match.

Removed OS X installers

Due to lack of resources and interest, the OS X dmg installers are no longer being built. OS X users can still use the system-independent binary.

New community modules

The 2.13 series comes with a few new community modules, in particular:

  • Do you want to generate GHRSST compliant outputs from GHRSST inputs? Try out the new GHRSST NetCDF output community module.
  • There is also a new community module introducing NSG profiles for the WFS and WMTS services.

Not that community modules are not part of the release; instead you can find them in the nightly builds.

Other assorted improvements

There are many bug fixes and improvements to look at in the release notes, cherry picking a few here:

  • Autocomplete support for dropdowns with long lists of values
  • Upgrade JDom library
  • REST API CORS support
  • REST improvements to list all layers in a workspace, and include the workspace prefix in layer listings
  • Style POST does not support non-SLD styles
  • Add WMTS RESTful API
  • Installing the XSLT plugin may cause random REST endpoints to report lists with transforms/transform
  • WCS 1.0.0 does not handle FORMAT parameter properly
  • Cache small amount of features in memory to avoid repeated data scans in GetFeature requests
  • Allow requesting both OL3 and OL2 from the client side
  • Simple feature GML 3.2.1 output schema-invalid as geometries lack mandatory gml:id
  • GeoPackage generated via WPS has y coordinates starting from bottom left
  • Numerous WFS 2.0 bugfixes
  • Submitting a seed/truncate request for a tile layer results in a “406, not acceptable”
  • GWC Seed Form returns “Chunk [] is not a valid entry” message error when seeding a layer.
  • Demo Page does not send password
Test, test, test!

Now that you know about all the goodies, please go, download and test your favourite ones. Let us know how it went!

About GeoServer 2.12

GeoServer 2.13 is scheduled for March 2018 release.

Categories: OSGeo Planet

Free and Open Source GIS Ramblings: Resources for QGIS3

OSGeo Planet - Wed, 2018-02-21 19:43

The release of 3.0 is really close now. If you want to know what’s new or are just looking for interesting ways to pass the time until the packages land, check out the following QGIS3 resources.

For users

For developers

There’s still time to get the PyQGIS 3 Programmer’s Guide at discount before QGIS 3.0 is released! See: https://t.co/xJ7LLaX5UU #qgis #qgis3 #pyqgis #python pic.twitter.com/9k3FUmNFkH

— Locate Press (@locatepress) February 13, 2018

Migrating your plugin to #qgis 3, you can use First Aid plugin to help you debugging issues. To learn more about First Aid:https://t.co/5k7RXUDfGD

— Lutra Consulting (@lutraconsulting) February 1, 2018

If you have further reading recommendations, please post them in the comments below.

 

Categories: OSGeo Planet

GeoTools Team: GeoTools 19-beta Released

OSGeo Planet - Wed, 2018-02-21 18:08
The GeoTools team is pleased to announce the release of GeoTools 19-beta:This release is also available from our Maven repository.This release is made in conjunction with GeoServer 2.13-beta.
This release includes a two major changes, both related to Java 9 compatibility, and a significant set of new features and improvements.FactorRegistry RefactoringIn JDK 9 javax.imageio.spi.ServiceRegistry verifies that it is extended by JDK-classes only. For GeoTools' org.geotools.factory.FactoryRegistry that means that an exception is thrown, thus crashing GeoTools. To fix this, it was necessary to reimplement the ServiceRegistry functionality that is needed by GeoTools in FactoryRegistry.

For most users, this should not require any changes to make your project compatible. However, if you are accessing the FactorRegistry directly, there are some API changes that you will need to handle. For more details, refer to the FactoryRegistry Refactoring for Java 9 Compatibility proposal.


Java 9 CompatibilityMore generally, GeoTools as a whole has been updated to be able to run on Java 9.If your project depends on GeoTools 19.x, and you want to use it with Java 9, you will need to add the following flags to your JVM runtime arguments:--add-modules=java.xml.bind --add-modules=java.activation
This adds the JAXB and Activation modules to the Java Runtime (They are not included by default in Java 9). Strictly speaking, this is only required if your project depends upon certain GeoTools modules, such as gt-imagemosaic.Note that these arguments are not supported under Java 8. If you wish to retain compatibility with Java 8, also include:-XX:+IgnoreUnrecognizedVMOptions
This tells the JVM to ignore options it doesn’t recognize, so Java 8 won’t throw an error.
Also note that running GeoTools on Java 9 will introduce a few functional changes:
  • XML pretty-print behaviour has changed, so that CDATA tags will now be on their own lines. These changes are only cosmetic - there are no functional changes to the XML. 
  • Certain math functions are more precise on Java 9. This can result differences in the last digit of double values between Java 8 and Java 9. In particular, this has been observed when dealing with reprojected coordinates.
  • Small changes in horizontal offset have been observed in labels following lines. This may be OS-specific.
GeoPackage performance improvementsGeoPackage reading and rendering performance improved significantly, up to two times faster on large datasets full extractions and 50% faster on small bounding box searches, bringing GeoPackage on par with PostGIS. We also have a Google spreadsheet with more details.

Shapefile remains king of full dataset extractions and the fastest data source for pure spatial driven queries.

Support for more PostGIS data types

The PostGIS data store now has simple support for HStore and JSON columns. HStore is returned as a Map, while JSON is read as a String. In both cases no special query support has been added for those types (but we'd be very happy if someone would work, or sponsor, that functionality too).

Better label position control in map rendering

When setting maxDisplacement on point/polygons the renderer used to search in a circular area around the designated label point.
The new displacementMode vendor option allows to control the positioning by specifying the preferred cardinal positions, as a comma separated list.


Shapefile now supporting all Java object types on write

Shapefile used to throw exceptions if unrecognized object types were fed to it (basically, anything but geometries, strings, numbers and dates). From now on it will write unrecognized objects as strings instead.
Assorted improvementsHighlights from our issue tracker release-notes:
  • Upgrade JDom to version 2.0.6
  • Upgrade to EJML 0.32
  • Upgrade Apache Solar Java client to is last stable release
  • Expose GDAL ASRP/USRP format
  • GML 3.2 encoding misses mandatory gml:id on geometry elements - fast path
  • Cannot export to GeoPackage when GeoServer feature type has Boolean attribute
  • MongoDB support optional milliseconds in ISO8601 date/time string
  • Geometries used in expressions should be cloned during rendering to preserve their original coordinates
  • Improved NoData support in mosaics of NetCDF files
  • JDBCDataStore recognize the "in" function family (including in2, ..., in10) and encode those as native SQL whenever possible. Also, all Instant objects will now be encoded in SQL (before only the Date family was encoded properly).
There is also a large set of bug fixes. For more information see the 19-beta release notes.
Please test test test!!
Java 9 (and the soon-to-be-released Java 10) introduce significant changes, so please test GeoTools on Java 9 if you are able. 
Please also test GeoPackage and all the new features introduced in this release.
Categories: OSGeo Planet

gvSIG Team: gvSIG Desktop 2.4 is already available

OSGeo Planet - Wed, 2018-02-21 17:11

gvSIG Desktop 2.4, the new version of the open source Geographic Information System, is now available. You can access both the gvSIG Desktop 2.4 installable and portable versions from the download section of the project website, with distributions available for Windows, Linux and Mac OS X.

Downloads: http://www.gvsig.com/es/productos/gvsig-desktop/descargas

This new gvSIG version is released with a lot of new features and improvements. The most outstanding ones can be found here:

Table of contents: Integrated catalog

SA new tab has been integrated in the ‘Table of Contents’ of the Views which contains the previous ‘Catalog’ plugin functionality, considerably improved. It allows you to add layers from the catalog browser to the View, open files as a Table, save to Favourites, change a layer name in Favourites, etc.

Table of contents: hiding legends and behaviour improvements

The behaviour of the TOC has been improved in terms of layer order and selection of layers.

A functionality has been added to hide the legends of the layers that are not visible in the ‘Table of Contents’ automatically. Besides having more space in the TOC, the gvSIG speed is optimized, since in case of web services (such as WMS) it avoids making requests to the server if the layer is not visible.

This option can be disabled from the ‘Preferences’ of the application

Symbology: Heat map legend

The heat map legend, also known as Hot Spot, has been added. This type of legends are used to identify the gathering of a certain element. More information.

Symbology: Marker clustering legend

New type of legend available and especially useful when we want to visualize a certain phenomenon whose quantity can’t be determined only visually. To do this, this legend also represents the element by means of a symbol, the number of times that the phenomenon exists in a certain area and that the user can adjust. More information.

Tools: 4D, temporary data support

Tools to support temporary data in gvSIG Desktop, known as 4D, have been developed. With this new tools we can assign the temporary parameter to a layer (even if it does not have a date field) and consult the data in a specific moment or time range. It also has tools to generate animations in the View, allowing to see a temporary evolution of the information. More information.

Tools: quick information

This tool allows us to show information about vector entities on a label when we move the mouse over it. We can define what information we want to display. More information.

Tools: Cadastre GML

In the European Union, the exchange format defined for Cadastre is GML with a specific scheme. The gvSIG Desktop functionality has been updated to support the latest changes made at GML format. In the case of Spain, it has been verified that the data generated with gvSIG Desktop complies with the cadastral validation.

Databases: H2GIS

In this version we have included H2GIS database support, the H2 spatial engine. One of the main advantages is the access to the H2 administration tools from gvSIG Desktop, with which using the SQL language we can perform any of the many operations that H2GIS allows and, therefore, adding all the GIS functionalities of H2GIS (they are a lot!) to gvSIG Desktop. Among others: management of 2D and 3D geometries, support of spatial indexes (improving the speed when loading layers), importers of different formats, geoprocessing, triangulation, surveying, network analysis, OSM data download… More information.

Databases: Oracle

The Oracle database driver has been updated and optimized, allowing to work with this extended database.

Databases: SQL Server

In gvSIG Desktop 2.4 there is support for SQL Server database. SQL Server is a database management system of the relational model, developed by Microsoft. SQL Server is one of the most used databases. More information.

Databases: SpatiaLite

In gvSIG Desktop 2.4 the support for SpatiaLite database has been added. SpatiaLite is a SQLite database engine where spatial functions have been added. This improvement will also allows easy data exchange between gvSIG Mobile and gvSIG Desktop, since the mobile application of the gvSIG Suite works with SpatiaLite. More information.

Data: New OSM map services

The OpenStreetMap cartography is one of the most widely used cartographic base worldwide. In gvSIG Desktop 2.4 we have added new OSM map services that provide both new ways of representing cartography and thematic services. The new map services available are: Open Sea Map, Open Railway Map, Carto Dark, Carto Light and HOT (Humanitarian OSM Team). More information.

Data: OSM data direct download

One of the H2GIS functions allows the direct OpenStreetMap data download. We would be able to run that sentence from the H2GIS console, but because of its usefulness (and to make it easier for users) we have decided to add it as an independent tool. It allows to download the OSM cartography of the frame that we have in our View at that moment. More information.

3D: World Wind update and safety improvements

The NASA World Wind Library, the 3D engine used by gvSIG Desktop, has been updated. This new World Wind version includes improvements in safety protocols.

Geoprocessing: Geocoding

Through this geoprocess we can convert a table with addresses to point layers. The table, apart from addresses, could contain characteristic elements such as museums, monuments, sports facilities …, that is, any place that we can search in Google Maps, OpenStreetMap …, since they are the search engines used for geocoding.. More information.

Geoprocessing: Point disperse

This geoprocess allows us to disperse the points that are overlapped around a central point in a layer. From a point layer, a match distance and a scatter radius, this algorithm acts on the input layer looking for groups of points whose distance is less than or equal to the match distance. It scatters them, according to the scatter radius, around the centre of that group, creating a new point layer with the results. More information.

Geoprocessing: Rossmo

Geoprocess that implements Rossmo’s mathematical model for serial killers detection. It allows to calculate the probability that each point of a map is the usual place of a serial killer. More information.

Geoprocessing: Demonstration attendees calculator, population by area calculator

This geoprocess was developed to calculate how many people there are really in a demonstration. It allows to calculate population in a specific area. More information.

Interface: Icon theme configurator

This set of tools will allow us to create new icon themes so that we can customize the appearance of our gvSIG Desktop. If you are tired of the current icon set … with this add-on you will be able to change it and design your own icons. More information.

Interface: 16×16 and 22×22 TreCC icon set

Icon set to change the appearance of gvSIG Desktop completely, available in 16×16 and 22×22 size. More information.

Usability: project preview

When opening a project in a concrete location, this new functionality allows you to see an image of the available projects of gvSIG Desktop, which many times can help us to identify the one we want to open. This image is updated every time we save changes in a project. More information.

Usability: toolbars

To facilitate the daily work of users in gvSIG Desktop 2.4, the usability of the application has been improved by placing the toolbars in the following logical order: Project actions, adding layers, zooms, attribute table, information tools, selection tools, editing tools… More information.

Usability: Maximized view

When opening gvSIG Desktop 2.4 a new maximized view is created automatically, the first action that a user always does. In addition, the option has been added in the ‘Preferences’ of the application, so that the user can define whether or not he wants this behaviour in gvSIG or not.

Usability: CRS of the View same as the layer

When adding a new layer we will see a new button ‘CRS View’ in the window, which allows to apply the reference system of the layer to the View automatically.

Help access from gvSIG Desktop

Two new tools have been added in the “Help” menu that will surely be very useful. Sometimes the simplest things can be the most useful. One of them allows to access to all the contents of the gvSIG Desktop user manual and the other one allows to search for the appropriate documentation for a specific query. More information.

Safety symbol library (ISO-7010)

A symbol library with the standard to represent the different safety pictograms can be useful for certain jobs. From now they are available in gvSIG Desktop. More information.

Emoji symbol library

This is a set of symbols very popular and recognizable by most users, and that they are now available in gvSIG Desktop to be able to represent your data in new ways. It contains activities, nature, flags, food and drink or objects symbols, the well-known smiley, frequently used symbols (numbers, letters, …), and places / trips (which includes means of transport symbols). More information.

Urban and Territorial Planning of the Valencian Community symbol library

Through this symbol library all the official symbols related to urban and territorial planning in the Valencian Community (Spain) are available. And, of course, they can be used by all those who need this symbology.

Development: Greater functionality using gvPy

gvPy is a library that facilitates the running of geoprocesses from scripting. Among other things it allows us to run scripts from the toolbox. For gvSIG Desktop 2.4, new improvements have been added too, that allow get objects from scripting, such as charts, that were not possible to get previously. More information.

Portable versions: Improvement in preferences

Portable versions have preferences within it by default. For certain organizations that use the portable, the option to use the user’s home for preferences has been enabled; in this case if any of the preferences (scripts, symbols, …) are not in the user’s home, gvSIG will copy them there before starting. In this way the option to keep the user preferences when updating portable version distributions is enabled.

Application: Opening projects with corrupt layers

The opening of projects with layers containing errors has been improved. With gvSIG Desktop 2.4, if there is a corrupt entity, the project is opened completely, indicating the layer with errors to the user, and allowing to load that layer again.

Application: Quick start

The gvSIG boot has been optimized, minimizing the opening time. Loading of the EPSG database is also carried out in the background, which implies that its query is immediate.

Application: Windows 10 support

The distribution for Windows 10 to 64bits has been optimized, which presented some problems in the installation in previous versions.

Application: new built-in browser

A new web browser has been incorporated. It optimizes the visualization of web pages where it is necessary to load them, such as in hyperlinks to web pages or in Google Street View tool.

Application: Quick scripts loading

Improvements that allow quick loading of scripts have been incorporated. These improvements are especially useful since gvSIG Desktop is increasing the number of tools developed from scripting considerably.

Application: optimized distributions size

Secondary plugins have been removed from the distributions, decreasing their size at this way. In this way, the user who wants to increase the functionality of his gvSIG Desktop can do so from the ‘Add-ons Manager’ through the URL option.

And there is still more, but we don’t want to launch all the novelties at once! In gvSIG Desktop 2.4, from the next week there will be three new plugins available, that will increase the functionalities of gvSIG Desktop greatly: Horton Machine, gvSIG Mobile and Epanet.

Horton Machine

Horton Machine, known as Jgrass previously, brings us a new toolbox with hundreds of geoprocesses of all kinds that are added to the more than 350 existing ones in gvSIG Desktop. With Horton Machine you will have access to tools for geomorphological analysis, for HECRAS, for LiDAR, etc. More information.

gvSIG Mobile

gvSIG Mobile is an app for data gathering in the field available in the available in the Google Play Store. Through this new plugin we can generate the base cartography for gvSIG Mobile from a gvSIG Desktop View. In addition, we will be able to upload a project made in gvSIG Mobile directly to gvSIG Desktop, including that created with a custom form, images, etc.

Epanet

This is a plugin to connect with the software called “Epanet”, that allows the analysis of drinking water distribution systems. The program is public and it’s developed by the United States Environmental Protection Agency (EPA). More information here and here.

We can only thank the work and support to all the people and organizations that have made this new version possible. All this work wouldn’t see the light without people who collaborate in testing, development, spreading… , and the organizations that bet on the gvSIG Association as a support organization for their ‘geo’ needs. Thank you.

As a final note we would like to comment that in recent months the gvSIG Desktop team hasn’t been working only on gvSIG Desktop 2.4. In parallel they have been working on the next gvSIG Desktop version intensely and it will be called 3.0 probably because of all the changes that it includes!!! … but we’ll talk about it later.

Categories: OSGeo Planet

gvSIG Team: gvSIG Desktop 2.4 ya disponible

OSGeo Planet - Wed, 2018-02-21 16:30

gvSIG Desktop 2.4, la nueva versión del Sistema de Información Geográfica libre, ya está disponible. Podéis acceder tanto a las versiones instalables como portables de gvSIG Desktop 2.4 en el apartado de descargas del proyecto, con distribuciones disponibles para Windows, Linux y Mac OS X

Descargas: http://www.gvsig.com/es/productos/gvsig-desktop/descargas

Esta nueva versión de gvSIG viene cargada de novedades y mejoras. Las más destacadas las podéis encontrar a continuación:

Tabla de contenidos: Catálogo incorporado

Se ha incorporado una nueva pestaña en la ‘Tabla de Contenidos’ de las Vistas que contiene la funcionalidad del anterior plugin de ‘Catalog’, considerablemente mejorada. Permite añadir capas desde el navegador del catálogo a la Vista, abrir como Tabla, guardar en Favoritos, cambiar nombre de una capa en Favoritos, etc.

Tabla de contenidos: ocultar leyendas y mejoras de comportamiento

Se ha mejorado el comportamiento del TOC en cuanto a cambio de orden de capas y selección de las mismas.

Se ha añadido una funcionalidad que oculta automáticamente en la ‘Tabla de Contenidos’ las leyendas de las capas que no estén visibles. Además de la ganancia de ‘espacio’ en el TOC, optimiza la velocidad de gvSIG, ya que en caso de servicios web (como por ejemplo WMS) evita hacer peticiones al servidor si la capa no está visible.

Está opción puede deshabilitarse desde las ‘Preferencias’ de la aplicación.

Simbología: Leyenda de mapa de calor

Se ha añadido el tipo de leyenda de mapa de calor, también conocida como Hot Spot. Este tipo de leyendas son utilizadas para identificar la concentración de un determinado fenómeno. Más info.

Simbología: Leyenda de marcadores agrupados

Nuevo tipo de leyenda disponible y especialmente útil cuando queremos visualizar un determinado fenómeno cuya cantidad no podemos determinar únicamente de forma visual. Para ello esta leyenda representa además del elemento mediante un símbolo, la cantidad de veces que sucede en un área determinada y que puede ajustar el usuario. Más info.

Herramientas: 4D, soporte a datos temporales

Se han desarrollado herramientas para disponer de soporte a datos temporales en gvSIG Desktop, el conocido como 4D. Mediante esta nuevas herramientas podemos asignar la capacidad temporal a una capa (incluso si no tiene campo fecha) y consultar los datos en un instante o rango temporal determinado. También dispone de herramientas para generar animaciones en la propia Vista, permitiendo ver una evolución temporal de la información. Más info.

Herramientas: información rápida

Esta herramienta permite mostrar información de las entidades vectoriales en forma de etiqueta cuando pasemos el ratón por encima y definir qué información queremos que se muestre. Más info.

Herramientas: GML Catastro

En la Unión Europea el formato de intercambio definido para Catastro es el GML con un esquema determinado. Se ha actualizado la funcionalidad de gvSIG Desktop para soportar los últimos cambios realizados sobre dicho GML. En el caso de España se ha comprobado que los datos generados con gvSIG Desktop son conformes a la validación catastral.

Bases de datos: H2GIS

En esta versión se ha incluido el soporte a base de datos H2GIS, el motor espacial de H2. Entre sus ventajas se encuentra el acceso a las propias herramientas de administración de H2 desde gvSIG Desktop, con lo que utilizando el lenguaje SQL podemos realizar cualquier operación de las muchas que permite H2GIS y, por tanto, añadiendo toda la funcionalidad de procesos SIG de H2GIS (¡que es mucha!) a gvSIG Desktop. Entre otras: Tratamiento de geometrías 2D y 3D, soporte de índices espaciales (mejorando la velocidad de carga de capas), importadores de diversos formatos, geoprocesamiento, triangulación, topografía, análisis de redes, descarga de datos OSM,…

Más info: aquí y aquí.

Bases de datos: Oracle

Se ha actualizado y optimizado el drive de base de datos de Oracle, permitiendo de este modo el trabajo con esta extendida base de datos.

Bases de datos: SQL Server

En gvSIG Desktop 2.4 se dispone de soporte a la base de datos SQL Server. SQL Server es un sistema de manejo de bases de datos del modelo relacional, desarrollado por la empresa Microsoft. SQL Server es una de las bases de datos más utilizadas. Más info.

Bases de datos: SpatiaLite

En gvSIG Desktop 2.4 se ha añadido el soporte a la base de datos SpatiaLite. SpatiaLite es un motor de base de datos SQLite al que se le han agregado funciones espaciales. Esta mejora además va a permitir intercambiar fácilmente datos entre gvSIG Mobile y gvSIG Desktop, ya que la aplicación móvil de la Suite gvSIG trabaja con SpatiaLite. Más info.

Datos: Nuevos servicios de mapas de OSM

La cartografía de OpenStreetMap es una de las bases cartográficas que más se utilizan a nivel mundial. En gvSIG Desktop 2.4 hemos añadido nuevos servicios de mapas de OSM que aportan tanto nuevas formas de representar la cartografía como servicios temáticos. Los nuevos servicios de mapas disponibles son: Open Sea Map, Open Railway Map, Carto Dark, Carto Light y HOT (Humanitarian OSM Team). Más info.

Datos: Descarga directa de datos de OSM

Una de las funciones de H2GIS permite la descarga directa de datos de OpenStreetMap. Esa sentencia la podríamos ejecutar desde la consola de H2GIS, pero por su utilidad (y para facilitar la vida a los usuarios) hemos optado por añadirla como una herramienta. Permite descargar la cartografía de OSM del encuadre que en ese momento tengamos en la Vista. Más info.

3D: Actualización de World Wind y mejoras en seguridad

Se ha actualizado la librería de World Wind de la NASA, el motor 3D de gvSIG Desktop. Esta nueva versión de World Wind incluye mejoras en protocolos de seguridad.

Geoproceso: Geocodificación

Mediante este geoproceso podemos convertir a capas de puntos una tabla con direcciones. La tabla, aparte de direcciones, también podría contener elementos característicos como museos, monumentos, instalaciones deportivas…, es decir, todo lugar que podríamos encontrar en buscadores como Google Maps, OpenStreetMap…, ya que emplea dichos motores de búsqueda para crear la geocodificación. Más info.

Geoproceso: Dispersión de puntos

Este geoproceso permite dispersar los puntos de una capa que se superponen alrededor de un punto central. Dada una capa de puntos, una distancia de concordancia y un radio de dispersión, este algoritmo recorre la capa de origen buscando grupos de puntos cuya distancia sea menor o igual a la distancia de concordancia y los dispersa, según el radio de dispersión, alrededor del centro de dicho grupo, generando una nueva capa de puntos con el resultado. Más info.

Geoproceso: Rossmo

Geoproceso que implementa el modelo matemático de Rossmo para detección de asesinos en serie. Permite calcular la probabilidad de que cada punto de un mapa sea el lugar habitual de un homicida serial. Más info.

Geoproceso: Calculador de población por área; manifestantes por unidad de superficie

Este geoproceso se realizó para calcular la cifra de asistentes a una manifestación. En definitiva permite calcular la población en una determinada área. Más info.

Interfaz: Configurador de tema de iconos

Este conjunto de herramientas nos permitirán crear nuevos temas de iconos de forma que podamos personalizar el aspecto de nuestro gvSIG Desktop. Si estás cansado del actual juego de iconos…con este complemento vas a poder cambiarlo y diseñarte tus propios iconos. Más info.

Interfaz: Juego de iconos TreCC de 16×16 y 22×22

Juego de iconos para cambiar totalmente el aspecto de gvSIG Desktop disponible en tamaños de 16×16 y 22×22. Más info.

Usabilidad: previsualización de proyectos

Al ir a abrir un proyecto en una determinada ubicación, esta nueva funcionalidad permite ver una imagen de los proyectos disponibles de gvSIG Desktop, lo que muchas veces nos puede ayudar a identificar aquel que queremos abrir. Esta imagen se actualiza cada vez que guardamos cambios en un proyecto. Más info.

Usabilidad: barras de herramientas

Para facilitar el trabajo diario de los usuarios en gvSIG Deskop 2.4 se ha mejorado la usabilidad de la aplicación situando las barras de herramientas en el siguiente orden lógico: Acciones sobre el proyecto, añadir capas, zooms, tabla de atributos, herramientas de información, herramientas de selección, herramientas de edición… Más info.

Usabilidad: Vista maximizada

Al abrir gvSIG Desktop 2.4 de forma automática se crea una Vista nueva maximizada, primeras acciones que siempre suele hacer un usuario. Además se ha añadido la opción en las ‘Preferencias’ de la aplicación, para que el usuario defina si quiere o no que gvSIG se comporte así.

Usabilidad: CRS de la Vista igual al de la capa

Al añadir una nueva capa veremos un nuevo botón, ‘CRS View’ en la imagen, que permite aplicar automáticamente la proyección de la capa a la Vista.

Acceso a la ayuda desde gvSIG Desktop

Se han añadido un par de opciones en el menú “Ayuda” que seguro que van a ser muy utilizadas. A veces las cosas más sencillas pueden ser las más útiles. Permiten por un lado acceder a todos los contenidos del manual de usuario de gvSIG Desktop y por otro buscar la documentación adecuada a una determinada consulta. Más info.

Biblioteca de símbolos: Seguridad (ISO-7010)

Disponer de una biblioteca de símbolos que contenga el estándar para representar los distintos pictogramas de seguridad puede ser útil para determinados trabajos. A partir de ahora ya los tienes disponibles en gvSIG Desktop. Más info.

Biblioteca de símbolos: Emojis

Un conjunto de símbolos muy popular y reconocible por la mayoría de usuarios, y que ahora tenéis disponible en gvSIG Desktop para poder representar vuestros datos de nuevas formas. Contiene símolos de actividades, naturaleza, banderas, comida y bebida, objetos, los conocidos smileys, símbolos de uso frecuente (números, letras,…), y lugares/viajes (que incluye simbología de medios de transporte). Más info.

Biblioteca de símbolos: Planificación Urbanística y Territorial de la Comunidad Valenciana

Mediante esta biblioteca se tienen disponibles todos los símbolos oficiales relacionados con planificación urbanística y territorial en la Comunidad Valenciana. Y, por supuesto, pueden ser utilizados por todos aquellos que requieran de esta simbología. Más info.

Desarrollo: Mayor funcionalidad utilizando gvPy

gvPy es una librería que facilita la ejecución de georocesos desde scripting. Entre otras cosas nos permite ejecutar scripts desde la caja de herramientas. Para gvSIG Desktop 2.4 se han añadido mejoras que permitan capturar objetos que antes no era posible capturar desde scripting, como por ejemplo gráficas. Más info.

Portables: Mejora en preferencias

Las versiones portables por defecto tienen las preferencias dentro de ella. Para ciertas organizaciones que utilizan la portable se ha habilitado la opción de poder usar el home del usuario para las preferencias; en este caso si alguna de las preferencias (scripts, símbolos,…) no están en el home del usuario, gvSIG se encarga de copiarlas allí antes de arrancar. De este modo se habilita la opción de que con la actualización de versiones de distribuciones portables se mantengan las preferencias del usuario.

Aplicación: Apertura de proyectos con capas defectuosas

Se ha mejorado la apertura de proyectos con capas que contienen errores. Con gvSIG Desktop 2.4, en caso de haber alguna entidad corrupta, el proyecto se abre completamente, indicando al usuario la capa que ha dado error y permitiendo cargarla de nuevo.

Aplicación: Arranque rápido

Se ha optimizado el arranque de gvSIG, minimizando el tiempo de apertura. También se realiza la carga de la base de datos de EPSG en segundo plano lo que implica que la consulta a la misma es inmediata.

Aplicación: soporte Windows 10

Se ha optimizado la distribución para Windows 10 a 64bits, que en versiones anteriores presentaba en algunos equipos problemas en la instalación.

Aplicación: nuevo navegador incorporado

Se ha incorporado un nuevo navegador web que optimiza la visualización de páginas web allí dónde es necesario, como por ejemplo en los hiperenlaces a páginas web o en la herramienta de Google Street View.

Aplicación: Carga rápida de scripts

Se han incorporado mejoras que permiten la carga rápida de scripts. Estas mejoras son especialmente útiles ya que gvSIG Desktop está aumentando considerablemente el número de herramientas desarrollas desde scripting.

Aplicación: tamaño optimizado de las distribuciones

Se han eliminado plugins secundarios de las distribuciones, disminuyendo así su tamaño. De este modo el usuario que quiera aumentar la funcionalidad de su gvSIG Desktop puede hacerlo desde el ‘Administrador de complementos’ por la opción de URL.

Y todavía hay más, pero no queremos lanzar todas las novedades de golpe!!. En gvSIG Desktop 2.4 van a estar disponibles a partir de la próxima semana tres nuevos plugins que multiplican considerablemente la funcionalidad de gvSIG Desktop: Horton Machine, gvSIG Mobile y Epanet.

Horton Machine

Horton Machine, anteriormente conocido como Jgrass, nos trae una nueva caja de herramientas con cientos de geoprocesos de todo tipo y que se suman a los más de 350 geoprocesos ya existentes en gvSIG Desktop. Con Horton Machine se tendrá acceso a herramientas para análisis geomorfológico, para HECRAS, para LiDAR, etc. Más info.

gvSIG Mobile

gvSIG Mobile es una app para la toma de datos en campo disponible en la Play Store de Google. Mediante este plugin podemos generar la base cartográfica para gvSIG Mobile desde Vistas de gvSIG Deskop. Y, por otro lado, podemos cargar directamente en gvSIG Desktop un proyecto realizado en gvSIG Mobile, incluyendo los creados con un formulario personalizado, imágenes, etc.

Epanet

Plugin para conectar con el software denominado “Epanet” y que permite el análisis de sistemas de distribución de agua potable. El programa es de dominio público y lo desarrolla la Agencia de Protección Ambiental de Estados Unidos (Environmental Protection Agency; más conocida por las siglas EPA). Más info: aquí y aquí.

Sólo nos queda agradecer el trabajo y apoyo a todas las personas y organizaciones que han hecho posible esta nueva versión. Sin las personas que colaboran en testeo, desarrollo, difusión…, sin las organizaciones que apuestan por la Asociación gvSIG como organización de soporte para sus necesidades ‘geo’, todo este trabajo no vería la luz. Gracias.

Como nota final nos gustaría comentar que estos últimos meses el equipo de gvSIG Desktop no sólo ha estado trabajando en gvSIG Desktop 2.4. En paralelo se ha estado trabajando intensamente en la próxima versión de gvSIG Desktop y que probablemente se denominará 3.0 por todos los cambios que trae!!!…pero de esto ya hablaremos en otra ocasión.

Categories: OSGeo Planet

Jackie Ng: Announcing: mapguide-react-layout 0.11

OSGeo Planet - Tue, 2018-02-20 17:10
Here's a long overdue release of mapguide-react-layout with a ton of new features.

GIFs and screenshots galore below. Brace yourselves!

Adding external WMS layers

A new component is available to easily add external WMS layers to your map.



As previously mentioned, you can access this component through a InvokeURL command that uses a component://AddManageLayers URI instead of a normal URL.

Partial Application State now encoded in URL

Through the use of react-url-query, we now have the ability to transfer part of our internal application state into the URL, allowing us to reload the browser window and be able to resume from where we left off.


The following bits of application state are now encoded into the URL:
  • Current view (x/y/scale)
  • Current active map (for multiple map configurations)
  • Shown/Hidden layer and group names
  • Current session id
Share Link to View

A new component is available to easily share this newly stateful URLs to other users.


Once again, you can access this new feature through an InvokeURL that has a component://ShareLinkToView URI instead of a normal URL. The session id is omitted by default, but you can tick Include Session ID to include your session id

Measure Segment Display

This was a feature missing from the equivalent Fusion widget that has finally been ported over. The measure tool properly displays individual measured segments.


Segments are only displayed for geodesic measurements. 

Drawing/Digitization improvements

Digitization now supports easily undoing the most recently drawn point by pressing the 'U' key.


This key and the key for cancelling the digitization (ESC) can be bound to different keys through new viewer mount options.

Template Improvements

The ajax-viewer template has been tweaked to look more like the original

This is possible because of the use of react-splitter-layout that gives us resizable panels.

The slate, maroon, limegold and turquoiseyellow templates also use this new component to finally give us resizable sidebars.


HTML property values in Selection Panel

Through new mount options, you can specify property values that are HTML to be presented as actual HTML, meaning property values that used to look like this:


Now looks like this:


This feature is disabled by default and you must opt into it (through new mount options). If the HTML content you're presenting is potentially un-trusted you can provide a sanitization function to clean the provided content (for example, with DOMPurify) to guard against possible cross-site scripting attacks.

Other Changes
  • Updated React to 16.2
  • Updated Blueprint to 1.35.5
  • Updated OpenLayers to 4.6.4
  • Updated TypeScript to 2.7.2
  • Debug viewer bundle (viewer-debug.js) now included
  • Added support for CenterSelection fusion widget. This marks the end of the Fusion widget porting work. No further Fusion widgets will be ported across. The list of Fusion widgets that will not be ported across can be found here.
  • Added support for extra extension properties in Redline and SelectPolygon widgets
  • Flyouts are now mutually exclusive, behaving more like their Fusion counterparts
  • Broke/404 toolbar/menu icons now gracefully show error icon as a placeholder.
  • Added support for manual feature tooltip toggling. This replaces click-based map selection if active and can be controlled through the Viewer Options UI.
  • Fix: Initial view of the map not using full viewport.
  • Fix: Commands now fall back to running in modal dialog if Task Pane is not present.
  • AJAX map frame viewer API is now fully emulated.

Project Home Page
Download
mapguide-react-layout on npm
Categories: OSGeo Planet

GeoServer Team: GeoServer 2.11.5 released

OSGeo Planet - Tue, 2018-02-20 17:02

We are happy to announce the release of GeoServer 2.11.5. Downloads are available (zipwar, and exe) along with documentation and extensions (OSX installer is currently missing as we’re unable to generate a signed installed version due to security/infrastructure issues being discussed on geoserver-devel).

GeoServer 2.11.5 is the last maintenance release of the GeoServer 2.11.x series, so we recommend users to plan an upgrade to 2.12.x or to the upcoming 2.13.x series. This release is made in conjunction with GeoTools 17.5.

Highlights of this release are featured below, for more information please see the release notes (2.11.5 | 2.11.4 | 2.11.3 |  2.11.22.11.12.11.0 | 2.11-RC1 | 2.11-beta ).

Bug Fixes
  • Fixed GetFeatureInfo on rasters setup with “reproject to declared” SRS policy
  • Assorted fixes on demo request page (password was not being sent
  • Allow importer to handle multi-coverage files on import (NetCDF)
  • GetLegendGraphic fixes for cut symbols on rescale (happened with large symbols and odd sized legends)
  • WMS fixes on rendering rasters whose native CRS is a polar stereographic
  • And several more, check the release notes for full details
About GeoServer 2.11

Articles, docs, blog posts and presentations:

  • OAuth2 for GeoServer (GeoSolutions)
  • YSLD has graduated and is now available for download as a supported extension
  • Vector tiles has graduate and is now available for download as an extension
  • The rendering engine continues to improve with underlying labels now available as a vendor option
  • A new “opaque container” layer group mode can be used to publish a basemap while completely restricting access to the individual layers.
  • Layer group security restrictions are now available
  • Latest in performance optimizations in GeoServer (GeoSolutions)
  • Improved lookup of EPSG codes allows GeoServer to automatically match EPSG codes making shapefiles easier to import into a database (or publish individually).
Categories: OSGeo Planet

Jackie Ng: React-ing to the need for a modern MapGuide viewer (Part 20): It doesn't have to *specifically* be a URL

OSGeo Planet - Tue, 2018-02-20 15:51
Wow! It's been 5 months since the last post related to mapguide-react-layout.

No I haven't stopped development. There's still plenty of things I want to achieve with this project before I consider it "done". It just had to take a back seat to other things that needed some attention:
Now that things have calmed down a bit, before I talk about the new release of mapguide-react-layout that will drop real soon, I want to talk about a capability of mapguide-react-layout that has been present for some time now, but I want to dedicate this entire post to because understanding this capability is the key in knowing how we can add new features to mapguide-react-layout yet retain the ability to use our existing Web Layout and Application Definitions to reference such new features.

I'm sure most of you should already be familiar with InvokeURL commands. You can define these commands in both a Web Layout and an Application Definition. They get represented in the AJAX/Fusion viewer as toolbar or menu items. When you click them, they invoke the specified URL into a given target (the Task Pane, a new window or a specific frame). InvokeURL commands is the basic gateway to custom MapGuide viewer functionality.

InvokeURL commands are also supported in mapguide-react-layout, except we can do extra things with such commands in mapguide-react-layout by leveraging the fact that a URL is merely a type of URI (Uniform Resource Identifier) and a URI ... does not necessarily have to start with http://. MapGuide resource identifiers (eg. Library://Foo/Bar.MapDefinition) are basically like URIs so this shouldn't be too much of a foreign concept.

So what does mapguide-react-layout do with this fact?

To demonstrate, here's a new feature that will be in the next release of mapguide-react-layout: A component to easily add external WMS layers


How can you access this new feature? Through an InvokeURL command.

Except, you don't invoke a URL you invoke a URI ... of our own custom creation.


As you can see from the above screenshot, we've invented our own component:// URI scheme to easily tap into new features in mapguide-react-layout without any structural changes required in the Web Layout or Application Definition schemas. We just leverage the existing InvokeURL command support and leverage the fact that whatever we're invoking in mapguide-react-layout ... doesn't necessarily have to be a URL. component URIs are structured as follows:

component://[component name][?query]
A component name refers to any component that's registered in the component registry. If a component can take parameters, you can pass them through the query string. Several components are available in the standard viewer bundle. The list of accessible components is available here.
If you use the npm module to roll your own custom viewer bundle, we provide APIs to allow you to easily create your own custom components. This is demonstrated in this example project.
The list of components available is small so far, that will grow over time as we add new features in future releases of mapguide-react-layout and the best thing about this is that to take advantage of such features, no changes to any authoring tools is required. You just have to enter a different kind of URI instead of a URL.
    Categories: OSGeo Planet

    GeoTools Team: GeoTools 17.5 released

    OSGeo Planet - Mon, 2018-02-19 15:11
    The GeoTools team is pleased to announce the release of GeoTools 17.5:
    This release, which is also available from the GeoTools Maven repository, is made in conjunction with GeoServer 2.11.5.

    GeoTools 17.5 is the last maintenance release of the 17.x series, time to consider upgrading!
    The release mainly fixes bugs but also includes some enhancements: 
    • Allow group extraction in image mosaic regular expression based property collector
    • Allow overriding LabelCache in renderer
    • Allow MetaBufferEstimator to work against a specific feature (to calculate sizes based on attribute values)
    For more information please see the release notes (17.517.4 | 17.3 | 17.2 | 17.1 | 17.0 | 17-RC1 | 17-beta).
    About GeoTools 17
    • The wfs-ng module has now replaced gt-wfs.
    • The NetCDF module now uses NetCDF-Java 4.6.6.
    • Image processing provided by JAI-EXT 1.0.15.
    • YLSD module providing a plain-text representation of styling.
    Upgrading
    • The AbstractDataStore has finally been removed. Please transition any custom DataStore implementations to ContentDataStore (tutorial available).
    Categories: OSGeo Planet

    gvSIG Team: GIS applied to Municipality Management: Module 13 ‘Layouts’

    OSGeo Planet - Mon, 2018-02-19 10:49

    The video of the thirteenth module is now available, in which we will show how to create maps with the geographic information that we have in our views.

    The layout will be the document that we can print, or export to PDF or PostScript, and in which we will insert the views that we have created in our project.

    On the layout we can insert all type of elements, such as texts, north arrow, scale, legend, images or logos, charts, rectangles, lines…

    The cartography to follow this video can be downloaded from this link.

    Here you have the videotutorial of this new module:

    Related posts:

    Categories: OSGeo Planet

    Just van den Broecke: Emit #3 – Things are Moving

    OSGeo Planet - Fri, 2018-02-16 23:03

    This is Emit #3, in a series of blog-posts around the Smart Emission Platform, an Open Source software component framework that facilitates the acquisition, processing and (OGC web-API) unlocking of spatiotemporal sensor-data, mainly for Air Quality. In Emit #1, the big picture of the platform was sketched. Subsequent Emits will detail technical aspects of the SE Platform. “Follow the data” will be the main trail loosely adhered to.

    Three weeks ago since Emit #2. A lot of Things have been happening since:

    A lot to expand on. Will try to briefly summarize on The Things Conference, LoRA and LoRaWAN and save the other tech for later Emits.

    LoRA and LoRaWAN may sound like a sidestep, but are very much related to for example building a network of Air Quality and other environmental sensors. When deploying such sensors two issues always arise:

    • power: need continuous electricity to keep sensors and their computing boards powered
    • transmission: need cabled Internet, WIFI or cellular data to transmit sensor-data

    In short, LoRa/LoRaWAN (LoRa=Long Range) is basically a wireless RF technology for long-range, low-power and low-throughput communications. You may find many references on the web like from the LoRa Alliance and SemTech. There is lots of buzz around LoRa. But just like the, Wireless Leiden project , who built a public WIFI network around the city, The ThingsNetwork has embraced LoRa technology to build a world-wide open, community-driven, “overlay network”:

    “The Things Network is building a network for the Internet of Things by creating abundant data connectivity, so applications and businesses can flourish. The technology we use is called LoRaWAN and it allows for things to talk to the internet without 3G or WiFi. So no WiFi codes and no mobile subscriptions. It features low battery usage, long range and low bandwidth. Perfect for the internet of things.”

    You may want to explore the worldwide map of TTN gateways below.

    And The ThingsNetwork (TTN) was established in Amsterdam, The Netherlands. As an individual you can extend The Things Network by deploying a Gateway. Via the TTN KickStarter project, I was one of the first backers, already in 2015. The interest was overwhelming, even leading to (Gateway) delivery problems. But a LoRa Gateway to extend TTN is almost a commodity now. You can even build one yourself. TTN is very much tied to the whole “DIY makers movement”. All TTN designs and code (on GitHub) are open. Below a global architecture picture from their site.

     So TTN organized their first conference, off course in Amsterdam. For three days: it was an amazing success, more than 500 enthousiasts.

    The conf was very hands-on with lots of free workshops (with free takeaway hardware). Followed several workshops, which were intense (hardware+software hacking) but always rewarding (blinking green lights!). One to mention in particular (as a Python programmer) was on LoPy a sort of Arduino board, very low cost (around $30), programmable with MicroPython that connects directly to TTN. Within an hour the board was happily sending meteo-data to the TTN.

    All in all this conference made me eager to explore more of LoRA with TTN, in particular to explore possibilities for citizen-based sensor-networks for environmental, in particular air quality, data. I am aware that “IoT” has some bad connotations when it comes to security, especially from closed technologies. But IoT is a movement we cannot stop. With and end-to-end open technology like the TTN there is at least the possibility to avoid the “black box”-part and take Things in our own hand.

     

     

     

    Categories: OSGeo Planet

    gvSIG Team: Recording of webinar on “gvSIG Suite: open source software for geographic information management in agriculture” is now available

    OSGeo Planet - Fri, 2018-02-16 09:33

    If you weren’t be able to follow the webinar on “gvSIG Suite: open source software for geographic information management in agriculture”, organized by GODAN and gvSIG Association, you can watch the recording now at the gvSIG Youtube channel:

    The webinar was oriented to show the gvSIG Suite, a complete catalog of open source software solutions, applied to agriculture.

    The gvSIG Suite is composed of ‘horizontal’ products:

    • gvSIG Desktop: Geographic Information System for editing, 3D analysis, geoprocessing, maps, etc
    • gvSIG Online: Integrated platform for Spatial Data Infrastructure (SDI) implementation.
    • gvSIG Mobile: Mobile application for Android to take field data.

    and sector products:

    • gvSIG Roads: Platform to manage roads inventory and conservation.
    • gvSIG Educa: gvSIG adapted to geography learning in pre-university education.
    • gvSIG Crime: Geographic Information System for Criminology management.

    At the webinar we also showed several successful case studies in agriculture and forestry. You also can consult another case studies at gvSIG Outreach website in this sector and other related sectors (they are in their original language but there’s a translator at the left side):

    The presentation is available at this link.

    If you want to download gvSIG Desktop you can do it from the gvSIG website, gvSIG Mobile is available from the Play Store, and if you are interested in implementing gvSIG Online in your organization you can contact us by e-mail: info@gvsig.com.

    If you have any doubt or problem with the application you can use the mailing lists.

    And here you have several links about training on gvSIG, with free courses:

    Categories: OSGeo Planet

    gvSIG Team: GIS applied to Municipality Management: Module 12 ‘Geoprocessing’

    OSGeo Planet - Thu, 2018-02-15 08:52

    The video of the twelfth module is now available, in which we will see the geoprocessing tools in gvSIG.

    gvSIG has more than 350 geoprocesses, both for raster and vector layers, which allow us to perform different types of analysis, for example to obtain the optimal areas to locate a specific type of infrastructure.

    Using the geoprocesses that are available in gvSIG we can create buffers for example, to calculate, among other things, the roads or railways rights of way. Then an intersection can be applied with a layer of parcels to obtain which part of each parcel should be expropriated. We can also make hydrological analysis, merge layers…

    The cartography to follow this video can be downloaded from this link.

    Here you have the videotutorial of this new module:

    Related posts:

    Categories: OSGeo Planet

    GeoSolutions: Latest on GeoNode: Local Monitoring Dashboard

    OSGeo Planet - Wed, 2018-02-14 16:51

    monitoring-geonode-featured

    Dear All,

    in this post we would like to introduce a plugin which we have developed for GeoNode and released it as Open Source (full documentation available here) in order to give users the ability to to keep under control hardware load as well as software load on a GeoNode installation. This plugin is called Monitoring, it is available as an Open Source contrib module for GeoNode, documentation on how to enable it and configure it, can be found here.

    Overview of the monitoring capabilities

    We are now going to provide an overview of the functionalities provided by this plugin; it is worth to point out that given the sensitive nature of the information to show, it is accessible only to GeoNode users that have the administrator role.

    The plugin allows administrators to keep under control the hardware and software load on a GeoNode instance by collecting, aggregating, storing and indexing a large number of informations that we normally keep hidden and spread in various logs which are difficult to find when troubleshooting, like GeoNode's own log, GeoServer log and audit log and so on; in addition, we collect also information about hardware load on memory and cpu (disk could be added easily) which are important to collect in live instances.

    Possibility to create alerts that can control certain conditions and then send a notification email to preconfigured email addresses is also available (more on this here).

    It is also possible to look at OGC Service statistics on a per service and per layer basis. Eventually, a simple country-based map that shows where requests are coming from is available.

    Overview of the available analytics

    Let us now dive a little into the functionalities provided by this plugin. Here below you can see the initial homepage of the plugin.

    [caption id="attachment_3878" align="alignnone" width="1024"]Monitoring Plugin Homepage Monitoring Plugin Homepage[/caption] We tried to put on the homepage a summary of the available information so that a user can quickly understand what is going on. The first row provides a series of visual controls that give an overview of the instance's health at different aggregation time ranges (from 10 mins to 1 Week):
    • Health Check - tells us if there are any alerts or erros that would require the attention of the administrator. Colors range from Red (at least an Error has happened in the selected time range) to Yellow (no Errors but at least an Alert has triggered within the selected time range)  and finally to Green (no Alerts or Errors).
    • Uptime - shows GeoNode system uptime.
    • Alerts -  shows number of notifications from defined checks. When clicked, Alerts box will show detailed information . See Notifications description for details.
    • Errors - shows how many errors were captured during request processing. When clicked, Errors box will show detailed list of captured errors.
    The Software Performance section is responsible for showing analytics about the overall performance of both GeoNode itself as well as the OGC back-end. [caption id="attachment_3892" align="alignnone" width="400"]dashboard-sw-performance Software Performance Summary Dashboard[/caption]

    If we click on the upper right corner icon, the detailed view will be shown, as illustrated below. Additional detailed information over the selected time period will be shown for both GeoNode, OGC Services and then for individual layers and resources.

    [caption id="attachment_3906" align="alignnone" width="1024"]Software Performance Detailed Dashboard - 1 Software Performance Detailed Dashboard - 1[/caption] [caption id="attachment_3907" align="alignnone" width="1024"]Software Performance Detailed Dashboard - 2 Software Performance Detailed Dashboard - 2[/caption]

    The Hardware Performance section is responsible for showing analytics about CPU and Memory usage of the machine where GeoNode runs as well as of the machine where GeoServer runs (in case it runs on a separate machine); see figure below.

    [caption id="attachment_3901" align="alignnone" width="1024"]Hardware Performance Detail Section Hardware Performance Detail Section[/caption]

    Interesting points and next steps

    The plugin provides additional functionalities which are described in detail in the GeoNode documentation (see this page); as mentioned above we can inspect errors in the logs directly from the plugin, we can set alerts that would send notifications email when they trigger. Moreover, the plugin provides a few additional endpoints that make it easier to monitor a GeoNode instance from the GeoHealthCheck Open Source project (as explained here).

    [caption id="attachment_3912" align="alignnone" width="1024"]Inspecting the error log Inspecting the error log[/caption]

    Last but not least, we would want to thank the GFDRR group at the World Bank which provided most of the funding for this work.

    If you are interested in learning about how we can help you achieving your goals with open source products like GeoServerMapStoreGeoNode and GeoNetwork through our Enterprise Support Services and GeoServer Deployment Warranty offerings, feel free to contact us!

    The GeoSolutions team,
    Categories: OSGeo Planet

    CARTO Inside Blog: CARTO Core Team and 5x

    OSGeo Planet - Wed, 2018-02-14 10:00

    CARTO is open source, and is built on core open source components, but historically most of the code we have written has been in the “CARTO” parts, and we have used the core components “as is” from the open source community.

    While this has worked well in the past, we want to increase the velocity at which we improve our core infrastructure, and that means getting intimate with the core projects: PostGIS, Mapnik, PostgreSQL, Leaflet, MapBox GL and others.

    Our new core technology team is charged with being the in-house experts on the key components, and the first problem they have tackled is squeezing more performance out of the core technology for our key use cases. We called the project “5x” as an aspirational goal – can we get multiples of performance improvement from our stack? We knew “5x” was going to be a challenge, but by trying to get some percentage improvement from each step along the way, we hoped to at least get a respectable improvement in global performance.

    Our Time Budget

    A typical CARTO visualization might consist of a map and a couple widget elements.

    The map will be composed of perhaps 12 (visible) tiles, which the browser will download in parallel, 3 or 4 at a time. In order to get a completed visualization delivered in under 2 seconds, that implies the tiles need to be delivered in under 0.5s and the widgets in no more than 1s.

    Ideally, everything should be faster, so that more load can be stacked onto the servers without affecting overall performance.

    The time budget for a tile can be broken down even further:

    • database retrieval time,
    • data transit to map renderer,
    • map render time,
    • map image compression, and
    • image transit to browser.

    The time budget for a widget is basically all on the database:

    • database query execution, and
    • data transit to JavaScript widget.

    The project goal was to add incremental improvements to as many slices as possible, which would hopefully together add up to a meaningful difference.

    Measure Twice, Cut Once

    In order to continuously improve the core components, we needed to monitor how changes affected the overall system, against both a long-term baseline (for project-level measurements) and short-term baselines (for patch-level measurements).

    To get those measurements, we:

    • Enhanced the metrics support in Mapnik, so we could measure the amount of time spent in retrieving data, rendering data, and compressing output.
    • Built an internal performance harness, so we can measure the cost of various workloads end-to-end.
    • Carried out micro-benchmarks of particular workloads at the component level. For PostGIS, that meant running particular SQL against sample data. For Mapnik that meant running particular kinds of data (large collections of points, or lines, or polygons) through the renderer with various stylings.

    Using the measurements as a guide, we then attacked the performance problem.

    Low Hanging Fruit

    Profiling and running performance tests, and doing a little bit of research showed up three major opportunities for performance improvements:

    • PostgreSQL parallelism was the biggest potential win. With version 10 coming out shortly, we had an opportunity get “free” improvements “just” by ensuring all the code in CARTO was parallel safe and marked as such. Reviewing all the code for parallel safety also surfaced a number of other potential efficiency improvements.
    • Mapnik turned out to have a couple areas where performance could be improved, through caching features rather than re-querying, and in improving the algorithms used for rendering large collections of points.
    • PostGIS had some small bottlenecks in the critical path for CARTO rendering, including some inefficient memory handling in TWKB that impacted point encoding performance.

    Most importantly, during our work on core code improvements, we brought all the core software into the CARTO build and deployment chain, so these and future improvements can be quickly deployed to production without manual intervention.

    We want to bring our improvements back to the community versions, and at the same time have early access to them in the CARTO infrastructure, so we follow a policy of contributing improvements to the community development versions while back-patching them into our own local branches (PostGIS, Mapnik, PostgreSQL).

    And In the End

    Did we get to “5x”? No, in our end-to-end benchmarks, we notched a range of different improvements, ranging from a new percent to a few times, depending on the use cases. We also found our integration benchmarks were sensitive to pressure from other load on our testing servers, so relied mostly on micro-benchmarks of different components to confirm local performance improvements.

    While the performance improvements have been gratifying, some of the biggest wins have been the little improvements we made along the way:

    We made a lot of performance improvements across all the major projects in which CARTO is based upon: you may have already noticed those improvements. We’ve also shown that optimizations can only get you that so far – sometimes taking a whole new approach is a better plan. A good example of this is the vector and raster data aggregations work we have been doing, reducing the amount of data transfered with clever summarization and advanced styling.

    More changes from our team are still rolling out, and you can expect further platform improvements as time goes on. Keep on mapping!

    Categories: OSGeo Planet

    GeoNode: GeoNode Summit 2018

    OSGeo Planet - Wed, 2018-02-14 00:00
    GeoNode Summit 2018 Join the awesome GeoNode community for the Summit 2018 from 26 to 28 March 2018 in the elegant city of Turin, Italy!

    Summit Website


    This Website is licensed CC by SA 2012. - GeoNode Contributors. Designed by Spatial Dev

    Categories: OSGeo Planet

    OSGeo.nl: Verslag: OSGeo.nl en OpenStreetMap NL Nieuwjaarsborrel 2018

    OSGeo Planet - Tue, 2018-02-13 22:33

    Op zondag 14 januari 2018 werd de traditionele OSGeo.nl en OpenStreetMap NL nieuwjaarsborrel, in de inmiddels geheel gerenoveerde bovenzaal van Cafe Dudok in Hilversum, weer goed bezocht. Een van de weinige events waar deze twee communities tezamen komen (dat moeten we vaker doen!).

    Ieder jaar weer blijkt dat er bij deze communities weer interesses en raakvlakken zijn: niet alleen op gebied van de open data rond De Basis Registraties (BAG, BGT, BRK, Top10NL etc) en projecten die zich daar mee bezig houden zoals NLExtract, maar ook op het gebied van bijvoorbeeld Missing Maps en QGIS. Dit smaakt ook naar meer events in 2018 om gezamenlijk Open Source en Open Data voor geo-informatie in Nederland te versterken.

    Onder de aanwezigen was duidelijk veel kennis en vooral het enthousiasme deze kennis te delen. Naast dat de bitterballen en speciaal-bieren weer goed smaakten waren er weer een aantal presentaties, aankondigingen en plannen. Meer hieronder, met links naar de slides:

    1. OSGeo.nl: Terugblik 2017, plannen 2018 – Just van den Broecke – Slides PDF
    Gert-Jan van der Weijden nam na 5 jaar uitmuntend OSGeo.nl voorzitterschap afscheid. Het huidige OSGeo.nl bestuur bestaat nu uit Just van den Broecke (voorzitter), Paulo van Breugel (secretaris), Barend Köbben (penningmeester). Maar bovenal was 2017 het jaar waarin de eerste FOSS4G NL plaatsvond in Groningen. Door de inzet van een geweldig team met o.a. Erik Meerburg, Leon van der Meulen, Willy Bakker en vele vrijwilligers van de Rijks Universiteit Groningen, werd dit event een enorm succes. Meer (vervolg) daarover later. En vooruitkijkend: welke ambities hebben we in 2018: teveel om op te noemen: vooral een FOSS4G NL 2018, maar ook gezien bijvoorbeeld een overweldigend aantal inschrijvingen op onze GRASS Crash Course, willen we in 2018 meer inzetten op kleinschalige, gerichte, hands-on events. Laat ons weten, als je daarvoor ideeën hebt.

    2. Raymond Nijssen – 510.global data team Rode Kruis – Slides PDF

    Raymond nam ons mee naar Sint Maarten in zijn, vaak aangrijpende, persoonlijke verhaal als vrijwilliger voor het 510.global data team van het Rode Kruis, waarvoor hij zich had aangemeld  kort na de orkaan Irma. Met de beperkte middelen en connectiviteit aldaar, wisten Raymond en het team, gebruikmakend van het ecosysteem van OpenStreetMap en tools als QGIS effectief overzichtskaarten voor hulpverleners te fabriceren. Hulde Raymond, je bent een voorbeeld!

    3. Rob van Loon, Ordina – Beheer GeoServer configuratie met Python scripts – Slides PDF


    GeoServer wordt op zeer veel plekken in Nederland ingezet. De bijbehorendeGeoServer Web UI om lagen en styling in te regelen is handig. Maar in veel situaties is het geautomatiseerd configureren van GeoServer veel effectiever: denk aan OTAP straten, meerdere, soms 100-en bijna identieke, lagen. Veel herhaalde, handmatige handelingen. Er bestaat al jaren een niet heel bekende REST-API om GeoServer op afstand te configureren. Deze is in de laatste versies van GeoServer steeds stabieler en krachtiger. Rob heeft daarvoor een toolkit ontwikkeld, binnenkort onder https://github.com/borrob.

    4. Willem Hofmans (JW van Aalst) – Witte Plekken en Zwarte Gaten in de BGT


    Willem en bij afwezigheid, Jan-Willem van Aalst, presenteerde een ontdekkingsreis in de krochten en details van de BGT. Daarbij viel nog veel te ontdekken: Witte Plekken, waar BGT nog niet volledig is, presenteert Jan-Willem regelmatig via zijn website. Zwarte Gaten, waar Willem met name op inging, zijn ook spannend: zitten er fouten in de BGT, of in de tools die, de vaak over-gecompliceerde, GML van BGT inlezen zoals NLExtract? Grensgebieden tussen rechthoeken en curves, het werd een reis vol verassingen. Navolging binnen NLExtract is er al.

    Verdere aankondigingen:

    Erik Meerburg (met Hans van der Kwast): de eerste QGIS Gebruikersdag op 31 jan 2018 bij IHE in Delft. Heeft inmiddels plaatsgevonden: een overweldigend success: over de 100 deelnemers. Er komt een QGIS NL Gebruikersgroep. Meer daarover binnenkort, blijf ons hier volgen!

    Erik Meerburg: de FOSS4G NL 2018: er waren op dat moment gesprekken met meerdere universiteiten/HBOs, want iedereen wil dit event graag binnenhalen. Inmiddels vergaande vorderingen: save the date: woensdag 11 juli 2018 bij Aeres Hogeschool in Almere. Meer nieuws volgt!

    Edward Mac Gillavry: na eerder discussies op deze dag rond basisregistraties met name BGT en NLExtract en het streven van OSGeo.nl op kleinere, gerichte events/workshops/hackethons/code sprints te organiseren, biedt WebMapper, ook sponsor voor de OSGeo.nl Meetup, aan om in 2018 een NLExtract Dag te organiseren. Vorm, plaats, tijd, nog te bepalen, ook meer hierover hier en via de OSGeo.nl kanalen.

    Al met al weer een mooie middag, waarbij het overgrote deel van de aanwezigen ook nog aanschoof bij het gezamenlijke diner in Cafe Dudok.

     

     

    Categories: OSGeo Planet

    Gary Sherman: Quick Guide to Getting Started with PyQGIS 3 on Windows

    OSGeo Planet - Tue, 2018-02-13 09:00

    Getting started with Python and QGIS 3 can be a bit overwhelming. In this post we give you a quick start to get you up and running and maybe make your PyQGIS life a little easier.

    There are likely many ways to setup a working PyQGIS development environment---this one works pretty well.

    Contents

    Requirements
    • OSGeo4W Advanced Install of QGIS
    • pip (for installing/managing Python packages)
    • pb_tool (cross-platform tool for compiling/deploying/distributing QGIS plugin)
    • A customized startup script to set the environment (pyqgis.cmd)
    • IDE (optional)
    • Emacs (just kidding)
    • Vim (just kidding)

    We'll start with the installs.

    Installing

    Almost everything we need can be installed using the OSGeo4W installer available on the QGIS website.

    OSGeo4W

    From the QGIS website, download the appropriate network installer (32 or 64 bit) for QGIS 3.

    • Run the installer and choose the Advanced Install option
    • Install from Internet
    • Choose a directory for the install---I prefer a path without spaces such as C:\OSGeo4W
    • Accept default for local package directory and Start menu name
    • Tweak network connection option if needed on the Select Your Internet Connection screen
    • Accept default download site location
    • From the Select packages screen, select: Desktop -> qgis: QGIS Desktop

    When you click Next a bunch of additional packages will be suggested---just accept them and continue the install.

    Once complete you will have a functioning QGIS install along with the other parts we need. If you want to work with the nightly build of QGIS, choose Desktop -> qgis-dev instead.

    If you installed QGIS using the standalone installer, the easiest option is to remove it and install from OSGeo4W. You can run both the standalone and OSGeo4W versions on the same machine, but you need to be extra careful not to mix up the environment.

    Setting the Environment

    To continue with the setup, we need to set the environment by creating a .cmd script. The following is adapted from several sources, and trimmed down to the minimum. Copy and paste it into a file named pyqgis.cmd and save it to a convenient location (like your HOME directory).

    @echo off SET OSGEO4W_ROOT=C:\OSGeo4W3 call "%OSGEO4W_ROOT%"\bin\o4w_env.bat call "%OSGEO4W_ROOT%"\apps\grass\grass-7.4.0\etc\env.bat @echo off path %PATH%;%OSGEO4W_ROOT%\apps\qgis-dev\bin path %PATH%;%OSGEO4W_ROOT%\apps\grass\grass-7.4.0\lib path %PATH%;C:\OSGeo4W3\apps\Qt5\bin path %PATH%;C:\OSGeo4W3\apps\Python36\Scripts set PYTHONPATH=%PYTHONPATH%;%OSGEO4W_ROOT%\apps\qgis-dev\python set PYTHONHOME=%OSGEO4W_ROOT%\apps\Python36 set PATH=C:\Program Files\Git\bin;%PATH% cmd.exe

    You should customize the set PATH statement to add any paths you want available when working from the command line. I added paths to my git install.

    The last line starts a cmd shell with the settings specified above it. We'll see an example of starting an IDE in a bit.

    You can test to make sure all is well by double-clicking on our pyqgis.cmd script, then starting Python and attempting to import one of the QGIS modules:

    C:\Users\gsherman>python3 Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 07:18:10) [MSC v.1900 32 bit (In tel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import qgis.core >>> import PyQt5.QtCore

    If you don't get any complaints on import, things are looking good.

    Installing pb_tool

    Open your customized shell (double-click on pyqgis.cmd to start it) to install pb_tool:

    python3 -m pip install pb_tool

    Check to see if pb_tool is installed correctly:

    C:\Users\gsherman>pb_tool Usage: pb_tool [OPTIONS] COMMAND [ARGS]... Simple Python tool to compile and deploy a QGIS plugin. For help on a command use --help after the command: pb_tool deploy --help. pb_tool requires a configuration file (default: pb_tool.cfg) that declares the files and resources used in your plugin. Plugin Builder 2.6.0 creates a config file when you generate a new plugin template. See http://g-sherman.github.io/plugin_build_tool for for an example config file. You can also use the create command to generate a best-guess config file for an existing project, then tweak as needed. Bugs and enhancement requests, see: https://github.com/g-sherman/plugin_build_tool Options: --help Show this message and exit. Commands: clean Remove compiled resource and ui files clean_docs Remove the built HTML help files from the... compile Compile the resource and ui files config Create a config file based on source files in... create Create a new plugin in the current directory... dclean Remove the deployed plugin from the... deploy Deploy the plugin to QGIS plugin directory... doc Build HTML version of the help files using... help Open the pb_tools web page in your default... list List the contents of the configuration file translate Build translations using lrelease. update Check for update to pb_tool validate Check the pb_tool.cfg file for mandatory... version Return the version of pb_tool and exit zip Package the plugin into a zip file suitable...

    If you get an error, make sure C:\OSGeo4W3\apps\Python36\Scripts is in your PATH.

    More information on using pb_tool is available on the project website.

    Working on the Command Line

    Just double-click on your pyqgis.cmd script from the Explorer or a desktop shortcut to start a cmd shell. From here you can use Python interactively and also use pb_tool to compile and deploy your plugin for testing.

    IDE Example

    By adding one line to our pyqgis.cmd script, we can start our IDE with the proper settings to recognize the QGIS libraries:

    start "PyCharm aware of Quantum GIS" /B "C:\Program Files (x86)\JetBrains\PyCharm 3.4.1\bin\pycharm.exe" %*

    We added the start statement with the path to the IDE (in this case PyCharm). If you save this to something like pycharm.cmd, you can double-click on it to start PyCharm. The same method works for other IDEs, such as PyDev.

    Within your IDE settings, point it to use the Python interpreter included with OSGeo4W---typically at: %OSGEO4W_ROOT%\bin\python3.exe. This will make it pick up all the QGIS goodies needed for development, completion, and debugging. In my case OSGEO4W_ROOT is C:\OSGeo4W3, so in the IDE, the path to the correct Python interpreter would be: C:\OSGeo4W3\bin\python3.exe.

    Make sure you adjust the paths in your .cmd scripts to match your system and software locations.

    Workflow

    Here is an example of a workflow you can use once you're setup for development.

    Creating a New Plugin
    1. Use the Plugin Builder plugin to create a starting point [1]
    2. Start your pyqgis.cmd shell
    3. Use pb_tool to compile and deploy the plugin (pb_tool deploy will do it all in one pass)
    4. Activate it in QGIS and test it out
    5. Add code, deploy, test, repeat

    Working with Existing Plugin Code

    The steps are basically the same was creating a new plugin, except we start by using pb_tool to create a new config file:

    1. Start your pyqgis.cmd shell
    2. Change to the directory containing your plugin code
    3. Use pb_tool create to create a config file
    4. Edit pb_tool.cfg to adjust/add things create may have missed
    5. Start at step 3 in Creating a New Plugin and press on

    Troubleshooting

    Assuming you have things properly installed, trouble usually stems from an incorrect environment.

    • Make sure QGIS runs and the Python console is available and working
    • Check all the paths in your pygis.cmd or your custom IDE cmd script
    • Make sure your IDE is using the Python interpreter that comes with OSGeo4W

    [1] Plugin Builder 3.x generates a pb_tool config file

    Categories: OSGeo Planet

    Blog 2 Engenheiros: Como organizar seus mapas no ArcGIS e QGIS?

    OSGeo Planet - Tue, 2018-02-13 07:07

    Nem todas as pessoas são organizadas, e não é diferente para aquelas pessoas que passaram 5+ anos numa graduação.

    Se eu te solicita-se material das aulas de Química Orgânica do seu curso de graduação, você teria condições de me entregar eles? Ou eles estariam perdidos, em uma pasta muito remota, que nem mesmo o Windows conseguiria achar.

    Se você tem problemas de organização e trabalha com geoprocessamento, iremos dar dicas para você se organizar e não perder os arquivos do seu SIG.

    Como é a sua área trabalho? Organizada ou uma bagunça?Como é a sua área trabalho? Organizada ou uma bagunça? Fonte: ATRL. Vantagens da Organização

    Ao tornar-se uma pessoa organizada, você notará benefícios como passar menos tempo procurando seus arquivos e corrigindo erros. Logo, se você não perde tempo com isso, terá mais tempo para realizar atividades produtivas.

    Não pense que as boas práticas de arquivamento de documentos se foram pois não utilizamos mais papeis.

    Aaron Lynn, no site Asian Efficiency, apresenta algumas regras que devem ser seguidas para deixar seu computador organizado. São elas:

    • Não salve documentos na Área de Trabalho;
    • Limite a criação de novas pastas;
    • Acostume-se a pensar em hierarquias;
    • Crie uma pasta para projetos concluídos (arquivo morto).

    Dentre essas regras, a ideia de hierarquia é a mais importante. Pois você deverá classificar seus documentos, por exemplo, como Pessoal ou Trabalho; dentro da pasta Trabalho, você pode ainda ter outras classes, tais como Projetos em Andamento, Projetos Concluídos e Documentos Administrativos.

    Exemplo de organização usando hierarquia para uma pasta de trabalho.Exemplo de organização usando hierarquia para uma pasta de trabalho.

    Parece complicado? Se você se acostumar a ser organizado, as coisas começarão a fluir facilmente. Ainda parece difícil? Segue alguns sites que podem te auxiliar a ser mais organizado:

    Organização no SIG

    Agora vamos aplicar um pouco dessas ideias para gerenciar nossos arquivos do nosso Sistema de Informações Geográficas. Assista nosso vídeo e descubra.

    Siga nossas dicas e você será mais organizado. Organização é uma habilidade que desenvolvemos com o tempo, portanto, não desista.

    E caso você tenha alguma sugestão de organização, deixa ela nos comentários.

    Categories: OSGeo Planet

    Free and Open Source GIS Ramblings: TimeManager 2.5 published

    OSGeo Planet - Mon, 2018-02-12 21:39

    TimeManager 2.5 is quite likely going to be the final TimeManager release for the QGIS 2 series. It comes with a couple of bug fixes and enhancements:

    • Fixed #245: updated help.htm
    • Fixed #240: now hiding unmanageable WFS layers
    • Fixed #220: fixed issues with label size
    • Fixed #194: now exposing additional functions: animation_time_frame_size, animation_time_frame_type, animation_start_datetime, animation_end_datetime

    Besides updating the help, I also decided to display it more prominently in the settings dialog (similarly to how the help is displayed in the field calculator or in Processing):

    So far, I haven’t started porting to QGIS 3 yet. If you are interested in TimeManager and want to help, please get in touch.

    On this note, let me leave you with a couple of animation inspirations from the Twitterverse:

    Here's my attempt, Thanks @tjukanov for the inspiration and @dig_geo_com for the Tutorial. Distances traveled in 2,5,7,9,11,13,15 minutes in Cluj-Napoca, Romania. Made with @QGIS#TimeManager,@openstreetmap, data from @here pic.twitter.com/tEhXfy6CAs

    — vincze istvan (@spincev) February 3, 2018

    More typographic experiments with Danish ship data.
    – 24 hours of ship traffic
    – Size of ship name defined by a combination of vessel size and speed
    – Direction of the name is defined by vessel's course pic.twitter.com/2p16Qo1Kuf

    — Topi Tjukanov (@tjukanov) January 11, 2018

    How the City of #Zurich has grown since 1875.

    Made with @QGIS#TimeManager.
    Thx to @underdarkGIS and @tjukanov for the inspiration.#geogiffery #DataViz #Map #cartography pic.twitter.com/TY2flppsVA

    — Marco Sieber (@DonGoginho) January 17, 2018

    Categories: OSGeo Planet
    Syndicate content