OSGeo Planet

gvSIG Team: Carga de ficheros GPX en gvSIG Desktop y gvSIG Mobile

OSGeo Planet - Thu, 2019-03-14 16:02

En ocasiones podemos necesitar visualizar ficheros GPX obtenidos con dispositivos GPS. Estos ficheros se pueden usar para describir puntos (waypoints), recorridos (tracks) y rutas (routes).

Tanto con gvSIG Desktop (en Windows, Linux y Mac) como con gvSIG Mobile (en Android) podréis cargar este tipo de ficheros, y superponerlos con otro tipo de cartografía, tanto ráster como vectorial, y tanto capas locales como capas disponibles a través de servicios remotos.

En gvSIG Desktop podemos cargar los ficheros GPX desde la pestaña “OGC” de la ventana de “Añadir capa”. Una vez seleccionado el fichero entrando en el botón “…”, se le debe dar a “Abrir”, y entonces se seleccionará la información a cargar (“tracks”, “track_points”…). La capa se reproyectará al sistema de referencia de la Vista.

En gvSIG Mobile podemos cargar los ficheros GPX desde el menú “Importar” disponible en el menú principal.

En estos vídeos podéis ver mejor su funcionamiento:

gvSIG Desktop:

gvSIG Mobile:

Categories: OSGeo Planet

Marco Bernasocchi: QField RC5 – Last call for testing

OSGeo Planet - Thu, 2019-03-14 11:50

We are really happy to announce the fifth and (hopefully) last 1.0 release candidate in QField’s history! This means that QField 1.0 is closer than ever.

Get it while it’s hot on the Playstore (https://qfield.org/get) or on GitHub

Thanks to all the feedback by the fantastic community we were able to fix plenty of bugs, address performance issues and even add some super cool new features.

New file selector

Among the new features, the most important is the flashy new file selector with favorite directories (long press on a folder to add it to the favorites and longpress on the favorites list to remove it) and an automatic list of the last three opened projects that will save you heaps of time while looking for your projects.

Another lifesaver is the newly added support for pasting text from the clipboard in the search bar. Finally, we added a smart and unobtrusive “rate this app” dialog to make it easier for you to give QField the ★★★★★ you always wanted to give it

Categories: OSGeo Planet

gvSIG Team: Towards gvSIG 2.5: New geoprocess, Aoristic Clock by grid

OSGeo Planet - Thu, 2019-03-14 05:30

In previous posts we spoke (Aoristic clock, Ring map and Grid by point density) about a series of geoprocesses related to criminology made together with Jaume I University (UJI). These geoprocesses can be used in different sectors, not exclusively related to criminology.

Now we are going to show the Aorist Clock by grid geoprocess. The main objective of this geoprocess is to visualize the distribution of the temporal component in a graphical way. Its distribution within the hours of the same day, and within the day of the week will be shown.

Temporal distribution of 150.000 crimes in New York

A square grid will be generated in which the same number of entities on which the analysis has been made will be placed, with the only difference that the geometry has been changed to a point type geometry that will be placed on the grid. The position of this geometry will correspond to the time field, according to the day and the hour in which the event occurred.

When having all the starting elements with all their fields, we will be able to apply other type of symbologies. By default, a dot density symbology will be generated (as seen in the first image), but we could apply any other. A legend by categories or a label could be applied too. Other legends could also be applied, such as grouping points.

Temporal distribution analysis of 16 features by categories.

The geoprocess parameters are a layer that has two fields with time and day (which could be contained in the same field), an optional filter of the input data, and two proportion parameters that will help us to manage the horizontal and vertical size in case you want to modify it.

This geoprocess can be tested with the next Release Candidate version of gvSIG Desktop. You can download it from Tools -> Add-ons manager and search the “Geoprocess: Aoristic clock” geoprocess. Once installed, and after restarting gvSIG, it will appear at the “Scripting – Data Analysis – Aorist Clock” section.

If you have any doubt or you find any error you can send us the information through the mailing lists.

 

Categories: OSGeo Planet

gvSIG Team: Camino a gvSIG 2.5: Nuevo geoproceso, Reloj Aorístico por rejilla

OSGeo Planet - Thu, 2019-03-14 05:20

Hablamos en el post anteriores (Reloj Aorístico, Mapa de anillos y Rejilla por densidad de puntos) sobre una serie de geoprocesos relacionados con la criminología realizados junto a la Universidad Jaume I (UJI). Puedes ver el vídeo de la ponencia aquí. Estos geoprocesos pueden utilizarse en diferentes campos, no ligado en exclusiva a la criminología.

Le toca el turno al geoproceso de Reloj Aorístico de Rejilla. El objetivo principal de este geoproceso es el de visualizar de una forma gráfica la distribución de la componente temporal. Se mostrará su distribución dentro de las horas de un mismo día, y su distribución dentro del día de la semana.

Distribución temporal de 150.000 delitos en Nueva York

Se generará una rejilla cuadrada en la que se situarán el mismo número de entidades sobre las que se le ha hecho el análisis, con la única diferencia, de que la geometría se ha cambiado por una de tipo punto que se situará sobre la rejilla. La posición de esta geometría corresponderá al campo temporal, según el día y la hora en la que se haya producido el evento.

Al disponer de todos los elementos iniciales con todos sus campos, podremos aplicar otros tipos de simbologías. Por defecto se generará una simbología de densidad de puntos (como la vista en la imagen inicial), pero podríamos aplicar cualquier otra. Una leyenda por categorías o se podría aplicar un etiquetado. También se podrían aplicar otras leyendas como la de agrupación de puntos.

Análisis de distribución temporal de 16 elementos por categorías.

Los parámetros del geoproceso son una capa que disponga de dos campos que indiquen la hora y el día (que podrían estar contenidos en el mismo campo), un filtro opcional de los datos de entrada, y dos parámetros de proporción que nos ayudarán a manejar el tamaño horizontal y vertical en caso de querer modificarlo.

Este geoproceso se podrá  probar con la próxima versión Release Candidate de gvSIG Desktop. Lo podrás descargar de Herramientas -> Administrador de complementos y buscar por el geoproceso “Geoprocess: Aoristic clock”. Una vez instalado, aparecerá junto a los geoprocesos dentro del apartado de “Scripting – Análisis de datos – Reloj Aorístico”.

Si encuentras cualquier fallo o recomendación te animamos a escribirnos a las Listas de correo de gvSIG.

Categories: OSGeo Planet

gvSIG Team: Towards gvSIG 2.5: New geoprocess, Aoristic Clock

OSGeo Planet - Wed, 2019-03-13 16:19

In previous posts we spoke (Ring map and Grid by point density) about a series of geoprocesses related to criminology made together with Jaume I University (UJI). These geoprocesses can be used in different sectors, not exclusively related to criminology.

Now we are going to show the Aorist Clock geoprocess. The main objective of this geoprocess is to visualize the distribution of the temporal component in a graphical way. Its distribution within the hours of the same day, and within the day of the week will be shown.

Crimes in New York (150.000 features)

This will generate a set of layers that will create a ring map representing the number of features located in each range of hours and days.

Example about the temporal distribution of the 150.000 crimes of New York

The input parameters are a layer with date fields that include the day of the week and the crime time. A filter could also be applied to analyze only a subset of data. For example, we could filter by type of crime.

The time type field has been generated by a calculated field to which the formula has been applied: TIMESTAMP (CMPLNT_F_1, ‘HH: mm: ss’), that converts a text type field similar to “03:15:00” in a Timestamp type field that supports hours, minutes and seconds values which are used in the geoprocess. This functionality will be explained in the next post about the new expression generator. You can ask any question about it at the mailing lists.

The geoprocess options are:

  • Proportion: It allows you to modify the size of the ring map.
  • Range of hours: It allows you to filter the range of hours to be analyzed. From 0 to 23.
  • Range of days: It allows you to filter the range of days to analyze. From 0 to 6.
  • Starting point: Placement of the ring map on the map.

These ranges can be established by writing the following text for the hours for example: 8-14,19-21,23. This means that it will analyze the hours in the range from 8 hours to 14 hours (from 8:00 to 14:59), from 19 to 21 hours, and also the 23 hours (which would include all events from 23:00 to 0:00)

These ranges allow to limit the temporal analysis. For example, looking at the first graph of all crimes, we see that they are mainly concentrated from midday to midnight, so an analysis of only that time slot will allow us to see their distribution in a better way.

To verify these ranges, we will run the geoprocess with the following parameters.

We will see a graph like this one:

We can see that the graph has only be generated with the selected ranges. In the hour sectors where there is a temporal gap, the algorithm leaves a small blank space indicating that there is a discontinuity in that range.

The geoprocess generates several layers for the labels and for the ring. This allows you to modify everything related to your visualization, both labelling and legends.

In this case we are going to prepare it to appear in the New York area, giving us the possibility to print the map.

With the Coordinate Capture tool we will select a point close to the New York area.

Now we will run the geoprocess on that starting point. The proportion parameter is a function of the type of units of the view projection. In this case we have to reduce its size to a ratio of 0.01 to fit our map.

The results are these ones.

And if we created a map we would be able to have results similar to these ones.In this example we have used a crime layer, but it could be used on any data set where a time field is available.

This geoprocess can be tested with the next Release Candidate version of gvSIG Desktop. You can download it from Tools -> Add-ons manager and search the “Geoprocess: Aoristic clock” geoprocess. Once installed, and after restarting gvSIG, it will appear at the “Scripting – Data Analysis – Aorist Clock” section.

If you have any doubt or you find any error you can send us the information through the mailing lists.

Categories: OSGeo Planet

gvSIG Team: Camino a gvSIG 2.5: Nuevo geoproceso, Reloj Aorístico

OSGeo Planet - Tue, 2019-03-12 14:49

Hablamos en post anteriores (Mapa de anillos y Rejilla por densidad de puntos) sobre una serie de geoprocesos relacionados con la criminología realizados junto a la Universidad Jaume I (UJI). Puedes ver el vídeo de la ponencia aquí. Estos geoprocesos pueden utilizarse en diferentes campos, no ligado en exclusiva a la criminología.

Le toca el turno al geoproceso de Reloj Aorístico. El objetivo principal de este geoproceso es el de visualizar de una forma gráfica la distribución de la componente temporal. Se mostrará su distribución dentro de las horas de un mismo día, y su distribución dentro del día de la semana.

Delitos en Nueva York (150.000 entidades)

Esto generará un conjunto de capas que crearan un mapa de anillos respresentando cantidad de entidades situadas en cada rango de horas y día.

 

Ejemplo sobre la distribución temporal de los 150.000 delitos de Nueva York

Los parámetros de entrada son una capa con los campos de tipo fecha en los que se incluyan el día de la semana y la hora del delito. También se podría aplicar un filtro para realizar en análisis solo de un subconjunto de datos. Por ejemplo, podríamos hacer un filtro por tipología de delito.

El campo de tipo hora se ha generado mediante un campo calculado al que se le ha aplicado la formula: TIMESTAMP( CMPLNT_F_1 , ‘HH:mm:ss’) que convierte un campo de tipo texto similar a “03:15:00” en un campo de tipo Timestamp que soporta valores de horas, minutos y segundos los cuales se usan en el geoproceso. Esta funcionalidad se explicará en próximos post sobre el nuevo generador de expresiones. Cualquier duda nos podéis preguntar.

Las opciones  del geoproceso son:

  • Proporción: Permite modificar el tamaño del mapa de anillos.
  • Rango de horas: Permite realizar un filtrado del rango de horas a analizar. De 0 a 23.
  • Rango de días: permite realizar un filtrado del rango de días a analizar. De 0 a 6.
  • Punto de inicio: Colocación del mapa de anillos en el mapa.

Estos rangos los podemos establecer escribiendo por ejemplo la siguiente cadena para las horas: 8-14,19-21,23. Esto significa que analizará las horas en el rango de 8 horas a 14 horas (desde 8:00 a 14:59) , de 19 a 21 horas, y también las 23 horas (que implicaría todos los eventos de 23 a 0 horas).

Estos rangos permiten acotar los análisis temporales. Por ejemplo, viendo el primer gráfico de todos los delitos vemos que se concentran principalmente a partir del medio día hasta media noche, por lo que realizar un análisis solo de esa franja horaria permitirá ver mejor su distribución.

Para comprobar estos rangos, vamos a ejecutar el geoproceso con los siguientes parámetros.

Veremos que se obtiene una gráfica similar a la siguiente.

Vemos que ha generado la gráfica solo con los rangos seleccionados. En los sectores de las horas donde vemos que hay un hueco temporal, el algoritmo deja un espacio en blanco pequeño indicando que hay una discontinuidad en ese rango.

El geoproceso genera varias capas para las etiquetas y para el anillo. Esto permite modificar todo lo relacionado a su visualización, tanto etiquetados como leyendas.

En este caso vamos a prepararlo para que aparezca en la zona de Nueva York y nos facilite posible impresión del mapa.

Con el Capturador de coordenadas vamos a selecionar un punto cerca de la zona de Nueva York.

Ahora ejecutaremos el geoproceso sobre ese punto inicial. El parámetro de proporción va en función del tipo de unidades de la proyección de la Vista. En este caso tenemos que reducir su tamaño hasta una proporción de 0.01 para que se adecue a nuestro mapa.

Teniendo como resultado.

Y si creásemos un mapa podríamos tener un resultado similar al siguiente.

En este ejemplo hemos usado una capa de delitos, pero podría usarse sobre cualquier conjunto de datos donde se disponga de un campo temporal.

Este geoproceso se podrá  probar con la próxima versión Release Candidate de gvSIG Desktop. Lo podrás descargar de Herramientas -> Administrador de complementos y buscar por el geoproceso “Geoprocess: Aoristic clock”. Una vez instalado, aparecerá junto a los geoprocesos dentro del apartado de “Scripting – Análisis de datos – Reloj Aorístico”.

Si encuentras cualquier fallo o recomendación te animamos a escribirnos a las Listas de correo de gvSIG.

 

 

Categories: OSGeo Planet

Cameron Shorter: Google Season of Docs Announced

OSGeo Planet - Tue, 2019-03-12 01:33
Google has just launched a Season of Docs program, designed to bring open source and technical writer communities together, to the benefit of both. Awesome! I reckon our OSGeo projects should get involved, and I'm personally keen to be part of it. Anyone else want to join me?
Categories: OSGeo Planet

PostGIS Development: PostGIS 2.5.2, 2.4.7, 2.3.9 Released

OSGeo Planet - Mon, 2019-03-11 00:00

The PostGIS development team is pleased to provide bug fix 2.5.2, 2.4.7, and 2.3.9 for the 2.5, 2.4, and 2.3 stable branches.

These are the first versions to be able to compile against Proj 6.0.0, You must upgrade to these if you are using Proj 6.

2.5.2 This release supports PostgreSQL 9.3-11 (will compile against PostgreSQL 12, but not pass tests. Use only for pg_upgrade. You are encouraged to use the PostGIS 3.0 unreleased branch with PostgreSQL 12 , which has features specifically designed to take advantage of features new in PostgreSQL 12).

2.4.7 This release supports PostgreSQL 9.3-10.

2.3.9

This release supports PostgreSQL 9.2-10.

View all closed tickets for 2.5.2, 2.4.7, 2.3.9.

After installing the binaries or after running pg_upgrade, make sure to do:

ALTER EXTENSION postgis UPDATE;

— if you use the other extensions packaged with postgis — make sure to upgrade those as well

ALTER EXTENSION postgis_sfcgal UPDATE; ALTER EXTENSION postgis_topology UPDATE; ALTER EXTENSION postgis_tiger_geocoder UPDATE;

If you use legacy.sql or legacy_minimal.sql, make sure to rerun the version packaged with these releases.

Categories: OSGeo Planet

QGIS Blog: A Coruña contributors meeting: another step forward for the QGIS.ORG project!

OSGeo Planet - Sun, 2019-03-10 18:09
IMG_20190310_101428_486~2

On behalf of QGIS.ORG and the whole community, I’m would like to extend our thanks and congratulations to all the local volunteers who helped to make the event happen, with special thanks to Luigi “Ginetto” Pirelli, who spearheaded the effort. The event, which included a full week of workshops, a user conference, and contributor meeting, marked another milestone in the history of QGIS.

It was possibly the largest meeting we have had to date. It especially gratifying seeing more diversity and new faces. Our inclusive and welcoming community has always been a point of pride and it was amazing seeing how newcomers easily and pleasantly integrating in the community, producing good and tangible results within just a few days.

Many decisions were made, many discussions were fruitfully concluded, many tortillas were eaten, plans were laid out. These events are critical for preparing the way for the future of the QGIS.ORG project.

Our heartfelt thanks to all who donated their time and intellect, and to the many donors and sponsors to make all this possible.

See you in Bucharest next August, for the 23rd QGIS meeting!

QGIS.ORG

Categories: OSGeo Planet

QGIS Blog: End of life notice: QGIS 2.18 LTR

OSGeo Planet - Sat, 2019-03-09 08:13

257901067_158842QGIS 3.4 has recently become our new Long Term Release  (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR  as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

Categories: OSGeo Planet

gvSIG Team: Coordinate capture tool utilities in gvSIG

OSGeo Planet - Thu, 2019-03-07 09:26

In certain gvSIG tools it is necessary to enter coordinates as input parameters. For example in graphical editing, in geoprocessing (Visibility and lighting geoprocesses such as “Visibility” or “Line of sight”, or some tools for hydrological analysis such as “Flow line profile” or “Upslope area from a single point”) or in the field calculator, coordinates are necessary so that they can run. Until version 2.4 this task had to be done manually, being easy to make mistakes when entering the numbers.

From 2.5 version, and thanks to the new plugin that allows to capture coordinates and its integration with the geoprocesses framework or the expression tool, this task has been facilitated.

This plugin is not installed by default in the first builds of gvSIG 2.5, but it will be included in the final version by default. It you don’t have it installed, it must be installed previously from the Add-ons Manager (“Tools” menu). Accessing to “Installation from URL” and connecting to the default URL, in the following window you can search by “coord” text and you will find “Coordinate capture” plugin. You must mark it, and after installing it you have to restart gvSIG. With this you will have the plugin ready to use.

Once gvSIG is restarted, the tool will appear at View-> Query menu. After loading the desired layers, a new window will be opened if the new tool is executed. At that window, you will have two options:

  • Tool to copy the coordinates of a point and paste them in any external document.
  • Tool that allows to capture and memorize the coordinates of several points to be used later at these tools:
      • In graphical editing.
      • At the geoprocesses framework.
      • At the field calculator.
      • At “Selecting by attribute” tool.

Besides when capturing the coordinates we can indicate the reference system for them, to be copied at the clipboard as well as to be memorized at the list of coordinates.

In the following video you can see how to use the coordinate capture tool in different functionalities in detail:

Categories: OSGeo Planet

FOSS4G 2019 Bucharest: Launch of the Travel Grant Program FOSS4G 2019 Bucharest!

OSGeo Planet - Wed, 2019-03-06 20:08

Community is about inclusiveness, cooperation, support, sharing your knowledge and benefiting from knowledge shared by others. FOSS4G is a deeply rooted community event and that is why OSGeo is keen in supporting participation of fellow geospatial enthusiasts for whom attending an international FOSS4G would be a great opportunity, but almost if not completely, inaccessible.

With great joy, we announce that the FOSS4G 2019 Bucharest Travel Grant Program is launched! Check out all the details here.

You are on the other side? Do consider sponsoring TGP, a small amount for you can make a world of difference for another.

Categories: OSGeo Planet

gvSIG Team: Utilidades del nuevo capturador de coordenadas en gvSIG

OSGeo Planet - Wed, 2019-03-06 18:06

En ciertas herramientas de gvSIG es necesario introducir coordenadas como parámetros de entrada. Por ejemplo, en edición, o en ciertos geoprocesos (de Visibilidad e iluminación como el de “Visibilidad” o el de ”Línea de visión”, o algunos para análisis hidrológico como el de “Perfil según línea de flujo” o “Cuenca vertiente a un punto dado”) se necesitan unas coordenadas para que puedan ejecutarse. Hasta la versión 2.4 esta tarea debía realizarse manualmente, siendo fácil equivocarse al introducir los números.

A partir de la versión 2.5, y gracias al nuevo plugin que permite capturar coordenadas, esta tarea se ha facilitado mucho.

Este plugin no va instalado por defecto en los primeros builds de gvSIG 2.5, pero sí que irá en la versión final. Si no lo tenéis instalado se deberá instalar previamente desde el Administrador de complementos (menú “Herramientas”). Accediendo a la “Instalación por URL” y conectando a la URL por defecto, en la siguiente ventana podéis buscar por el texto “coord” y encontraréis el plugin “Coordinate capture”. Debéis marcarlo, y tras instalarlo debéis reiniciar gvSIG. Con ello tendréis el plugin listo para utilizar.

Una vez reiniciado gvSIG aparecerá la herramienta en el menú Vista->Consulta. Tras cargar las capas deseadas, si se ejecuta la nueva herramienta se abrirá una ventana. En ella, tendremos dos opciones:

  • Copiar las coordenadas de un punto para pegarlas en cualquier documento externo.
  • Capturar y memorizar las coordenadas de varios puntos para poder utilizarlas en las siguientes herramientas:
      • En edición gráfica.
      • En el marco de geoprocesos.
      • En la calculadora de campos.
      • En la herramienta de selección por atributo.

Además, en el momento de capturar las coordenadas podemos indicarle en qué sistema de referencia queremos tomarlas, tanto para copiarlas al portapapeles como para memorizarlas en el listado de coordenadas.

En el siguiente vídeo podréis ver en detalle las diferentes utilidades del capturador de coordenadas en gvSIG:

Categories: OSGeo Planet

CARTO Blog: Exporting Maps for Printing in the Digital Maps Era

OSGeo Planet - Wed, 2019-03-06 10:00
You have probably heard about Microsoft’s work this past year, in training a neural network to polygonize satellite imagery into building footprints. This work resulted in ...
Categories: OSGeo Planet

gvSIG Team: 11as Jornadas Latinoamericanas e do Caribe de gvSIG: “Geoteconologias, contribuindo para a solução de problemas do território”

OSGeo Planet - Tue, 2019-03-05 09:41

Nos dias 15 e 16 de agosto de 2019 serão celebradas na Universidade de Guanajuato (México) as 11as Jornadas Latinoamericanas e do Caribe de gvSIG com o tema “Geoteconologias, contribuindo para a solução de problemas do território”.

Esta edição, onde serão realizadas também as 5as Jornadas gvSIG México, serão um ponto de encontro para os usuários e desenvolvedores da Comunidade gvSIG, bem como para todas as pessoas interessadas nas Tecnologias de Informação Geográficas livres.

Para o envio propostas de comunicação, tanto para apresentação como para pôster, deve ser preenchida a planilha disponível na seção de Comunicações na página das jornadas.

As inscrições são gratuitas e poderão ser realizadas a partir do dia 15 de maio de 2019. Também serão realizadas várias oficinas, cuja inscrição será independente das jornadas. Todas as informações podem ser obtidas na página do evento.

Por outro lado, qualquer entidade ou pessoa interessada em patrocinar a conferência ou qualquer outro tipo de colaboração, pode escrever um email para o endereço jornadas.latinoamericanas@gvsig.org.

Categories: OSGeo Planet

GeoSolutions: MapStore Release 2019.01.00: Timeline, Styler and more

OSGeo Planet - Tue, 2019-03-05 09:35

release_2019.01.00

Dear Reader,

We are pleased to announce the release 2019.01.00 of MapStore, our flagship Open Source WebGIS product. The full list of changes for this release can be found here, but the most interesting additions are the following:

  • Timeline: you can manage time-enabled WMS layers, visualize their data through time and create animations, more information are available in the User Guide
  • Style Editor: you can create new styles for your layers or edit an existing one directly in MapStore, more information are available in the User Guide
  • User Guide: the MapStore User Guide is now available here with several sections and improved documentation
  • Various bug fixes and performance improvements
We have also nearly completed the integration in GeoNode, which will be release shortly after this release. [caption id="attachment_4496" align="aligncenter" width="800"]MapStore integration in GeoNode MapStore integration in GeoNode[/caption]

The Timeline

The Timeline is an useful tool for managing WMS layers with a time dimension. It makes it possible to observe the layers evolution over time, to inspect the layer values at a specific time instant (or time range) and to view different layer configurations dynamically through animations.

The Timeline works on top of the GeoServer WMTS-Multidim extension, when you load time layers the Timeline panel becomes automatically visible over the map viewport.

[caption id="attachment_4509" align="aligncenter" width="981"]Timeline tool visible on the map for layers with time dimension Timeline tool visible on the map for layers with time dimension[/caption]   The Timeline panel can be expanded to visualize the timeline histogram that shows the time domain of the involved layers. You can zoom on the histogram, scroll the time axis and drag the current time cursor along it.   [caption id="attachment_4511" align="aligncenter" width="1024"]Timeline histogram Timeline histogram[/caption]   More functionalities and the whole set of the available settings are described in the new User Guide.   [video width="1280" height="720" mp4="https://www.geo-solutions.it/wp-content/uploads/2019/03/timeline_30sec.mp4"][/video]   Style Editor

The style section of the Layer Settings tool has been improved and the L&F reviewed. Now you can select the layer styles from a list of cards and a search tool is also available. New tools have been also included to allow the editing capabilities, they are available in the toolbar to the users with Admin rights. The Style Editor works with the GeoServer REST APIs.

  [caption id="attachment_4512" align="aligncenter" width="1024"]Style settings and new tools for editing Style settings and new tools for editing[/caption]

As a user with administrative rights in GeoServer you can edit an existing style in the list or you can create a new style from scratch, in that case MapStore shows some style templates from which you can start the editing using both SLD or CSS syntax (CSS is available only if the GeoServer CSS Styling plugin is installed in GeoServer).

[caption id="attachment_4513" align="aligncenter" width="744"]Template selection Template selection[/caption]   [caption id="" align="aligncenter" width="1143"]style_editor_edit_style Style editing in SLD format[/caption]   The User Guide

MapStore documentation has been refactored and updated to improve the user experience: both the User Guide and the Developer Guide are now easly accessible and navigable. The User Guide provides now several sections with useful information about the MapStore functionalities: each plugin and component has been described to guide the user to a better experience.  The Developer Guide has been also migrated to the new documentation and it will be furtherly updated this year for next releases.

Ongoing and future work

For the next releases we have plans to work on the following (in sparse order):

  • Integration with GeoNode, during the last year we have also provided a GeoNode plugin that allows to integrate MapStore as GeoNode WebGIS Viewer and it will be released soon during 2019
  • Support for more general map annotations, beyond simple markers
  • Further improvements to charts and dashboards
  • Support for storytelling tools
  • Support for multiple map projections
  • Improvements to the existing tools like Measurement, Search and Catalog
  • Vector Tiles and MapBox Style support
Stay tuned for additional news on the next features!

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

The GeoSolutions team,
Categories: OSGeo Planet

GIS for Thought: Every Person in Great Britain Mapped

OSGeo Planet - Tue, 2019-03-05 07:00

A follow up to my previous post: Every Person in Scotland on the Map. Winner of the 2016 OS OpenData Award for Excellence in the use of OpenData from the British Cartographic Society.

Full size interactive map.

The mapping process is pretty straightforward, and not accurate. I don’t know where you live. But I can make an educated guess.

I simply amalgamate the two sets of census data from the NRS (National Records of Scotland) for Scotland (2011 census) and the ONS (Office of National Statistics) for England and Wales (2010 census).

Postcodes were then created based on the ONS Postcode Directory, filtering for postcodes that were live in 2011 (which is the latest census data). The postcode centroids were turned into polygons using voronoi polygons.

Then we simply select all of the buildings in a postcode from Ordnance SurveyOpen Map product, filtering out most schools and hospitals. Then we put a random point in a random building for each person in that postcode.

I would have loved to include Northern Ireland, but the Ordnance Survey of Northern Ireland do not have an equivalent open building outline dataset, like Open Map from the Ordnance Survey.

Rendered with: QGIS tile writer python script. Processing done 100% in PostGIS.

Categories: OSGeo Planet

Martin Davis: Fast Geometry Distance in JTS

OSGeo Planet - Mon, 2019-03-04 17:57

The second-most important criteria for a spatial algorithm is that it be fast.  (The most important is that it's correct!)  Many spatial algorithms have a simple implementation available, but with performance of O(n2) (or worse).  This is unacceptably slow for production usage, since it results in long runtimes for data of any significant size. In JTS a lot of effort has gone into identifying O(n2) performance hotspots and engineering efficient replacements for them.

One long-standing hotspot is the algorithm for computing Euclidean distance between geometries.  The obvious distance algorithm is a brute-force O(MxN) comparison between the vertices and edges (facets) of the input geometries.  This is simple to implement, but very slow for large inputs.  Surprisingly, there seems to be little in the computational geometry literature about more efficient distance algorithms.  Perhaps because of this, many geometric libraries provide only the slow brute force algorithm - including JTS (until now). 

Happily, it turns out there is a faster approach to distance computation.  It uses data structures and algorithms which are already provided in JTS, so it's relatively easy to implement. The basic idea is to build a spatial index on each of the input geometries, and then use a Branch-and-Bound search algorithm to efficiently traverse the index trees to find for the minimum distance between geometry facets.  This is a generalization of the R-tree Nearest Neighbour algorithm described in the classic paper by Rousssopoulos et al.  [1]. 

JTS has the STRtree R-tree index implementation (a packed R-tree using the Sort-Tile-Recursive algorithm). This has recently been enhanced with several kinds of nearest-neighbour searches.  In particular, it now supports a method to find the nearest neighbours between two different trees.  The IndexedFacetDistance class uses this capability to implement fast distance searching on the facets of two geometries.

Another benefit of this approach is that it allows caching the index of one geometry.  This further increases performance in the common case of repeated distance calculations against a fixed geometry.

The performance improvement is impressive.  Here's the timings for computing the distance from Antarctica to other world countries:

Source
Data sizeTarget
Data sizeTime
IndexedTime
Brute-ForceImprovement1 polygon
(19,487 vertices)244 polygons
(366,951 vertices)164 ms136 sx 830
Branch-and-bound search also speeds up isWithinDistance queries.  Here's a within-distance selection query between another antipodean continent and a large set of small rectangles:

Source
Data sizeTarget
Data sizeTimeTime
Brute-ForceImprovement1 polygon
(7,316 vertices)100,000 polygons
(500,000 vertices)53 ms10.03 sx 19
A small fly in the algorithmic ointment is that Indexed Distance is not always better than the brute-force approach.  For small geometries (such as points or rectangles) a simple scan is actually faster, since it avoids the overhead of building indexes.  It may be possible to determine a tuning parameter that allows automatically choosing the fastest option.  Or the client can choose the faster approach, using knowledge of the use case.
Future Work

A few further ideas to build or investigate:
  • Implement a caching FastDistanceOp using IndexedFacetDistance and indexed Point-In-Polygon.  This can be used to add a fast distance() method to PreparedGeometry 
  • Investigate improving isWithinDistance by using the MINMAXDISTANCE metric for envelopes.  This allows earlier detection of index nodes satisfying the distance constraint.
  • Investigate alternative R-Tree packing algorithms (such as Hilbert packing or sequence packing) to see if they improve performance

[1] Roussopoulos, Nick, Stephen Kelley, and Frédéric Vincent. "Nearest neighbor queries."  ACM SIGMOD record. Vol. 24. No. 2. ACM, 1995.





    Categories: OSGeo Planet

    gvSIG Team: 11as Jornadas de Latinoamérica y Caribe de gvSIG: “Geotecnologías, contribuyendo a la solución de problemas del territorio”

    OSGeo Planet - Mon, 2019-03-04 15:21

    Los días 15 y 16 de agosto de 2019 se celebrarán en la Universidad de Guanajuato (México) las 11as Jornadas de Latinoamérica y Caribe de gvSIG bajo el lema “Geotecnologías, contribuyendo a la solución de problemas del territorio”.

    Esta edición, que serán también las 5as Jornadas gvSIG México, serán un punto de encuentro para los usuarios y desarrolladores de la Comunidad gvSIG, así como de toda aquella persona interesada en las Tecnologías de la Información Geográfica libres.

    Para poder enviar propuestas de comunicación, tanto para presentación como para póster, se debe completar la plantilla disponible en el apartado de Comunicaciones de la web de las jornadas.

    Las inscripciones son gratuitas, y podrán realizarse a partir del día 15 de mayo de 2019. También se realizarán varios talleres gratuitos, cuya inscripción será independiente de la de las jornadas. Toda la información se podrá consultar en la web del evento.

    Por otro lado, cualquier entidad o persona interesada en patrocinar las jornadas o en cualquier otro tipo de colaboración, puede escribir un correo electrónico a la dirección jornadas.latinoamericanas@gvsig.org.

    Categories: OSGeo Planet

    CARTO Blog: Mapping Segregation - MIT's Atlas of Inequality

    OSGeo Planet - Mon, 2019-03-04 10:00
    This week, The Atlas of Inequality, a joint project from MIT Media Lab’s Human Dynamics Group and the Department of Mathematics at Universidad Carlos III de Madrid, was lau...
    Categories: OSGeo Planet
    Syndicate content