Welcome to Planet OSGeo

September 18, 2020

This is a brief update about the issue described in this previous post https://fromgistors.blogspot.com/2020/08/minor-update-semi-automatic.html , related to the Semi-Automatic Classification Plugin (SCP) dependency SciPy.

I'm glad to inform you that the issue is solved in the latest QGIS version 3.14.16.
Therefore, I invite you to update QGIS to the latest version. All the SCP tools should work normally.
Many thanks to the QGIS developers for their fantastic work.

For any comment or question, join the Facebook group about the Semi-Automatic Classification Plugin.

by Luca Congedo (noreply@blogger.com) at September 18, 2020 06:28 PM

En cualquier método de producción sea del ámbito que sea, son necesarios los controles de calidad ya que garantizan que el producto presente unas determinadas características preestablecidas, cumpliendo además con el fin al que está destinado. Esta idea anterior muy generalista se aplica al campo del desarrollo software, y más concretamente al desarrollo del software libre gvSIG Desktop, siendo esos controles de calidad los planes de prueba.

Un plan de prueba es un documento escrito que aúna los casos de prueba necesarios para evaluar cualquier desarrollo software. Un caso de prueba no es más que un breve documento que describe de manera detallada el comportamiento de parte o la totalidad de una herramienta del software al realizar una determinada acción concreta.

Para llevar a cabo un caso de prueba se tiene que describir una simulación útil, fijando las condiciones al igual que los datos utilizados, de modo que solo se teste el “motor” o algoritmo que trata dichos datos bajo dichas condiciones. De lo anterior se puede deducir que la función principal de un caso de prueba es poder detectar errores de manera fácil y sin apenas consumir tiempo/esfuerzo cada vez que se realizan cambios en el código del software.

Además, como es lógico, si un desarrollo pasa todos los casos de prueba y por tanto el plan sin fallos o errores, este sería correcto.

Las partes de un caso de prueba son:

  1. Título. Este compuesto por un identificador único más una breve frase de describe que se va a probar.
  2. Enlace de petición existente con ese caso. Enlace a la web de control de errores de gvSIG con el identificador único de forma que se puede comprobar si ya hay algún reporte de error asociado al caso en cuestión.
  3. Descripción. Breve texto que resume la acción a realizar, así como el tipo de resultados obtenidos. La descripción debe identificar sin ningún tipo de duda el comportamiento a testear.
  4. Prerrequisitos. Lista con los datos y configuración necesarios para la correcta ejecución del caso práctico.
  5. Pasos. Secuencia de acciones a realizar que proporcionan una serie de resultados tanto intermedios como finales. Esta es la parte más importante del documento ya que en ella se detallan todos los aspectos a probar y la forma de hacerlo.
  6. Resultados esperados. Texto en el que se indican tanto los resultados intermedios si son necesarios, como los resultados finales del caso. Puede presentarse como un párrafo o en forma de lista si los resultados son varios o así se mejora la comprensión.
  7. Reportar fallo. Parte del documento en el que se facilita la comunicación de errores detectados tras realizar el caso de prueba. Se compone de dos enlaces, un primer enlace que te dirige a la página web de control de errores de gvSIG y un segundo enlace, que previo a identificación te permite reportar en la página anterior una petición de corrección de error de dicho caso mediante su identificador único y titulo de manera automática.

Una vez definidos y detallada su estructura se muestran una serie de recomendaciones a tener en cuenta para la correcta elaboración de un caso de prueba.

  • Cuidar la ortografía en todo el documento.
  • Garantizar la comprensión de todo el texto. Prestar especial atención a la descripción ya que esta debe describir inequívocamente lo que se va a realizar.
  • El Título debe estar compuesto por el identificador único y un breve resumen de la descripción.
  • El apartado Pasos debe de detallar sin ningún tipo de dudas la acción a realizar por simple que sea.
  • En el apartado Pasos no se debe obviar ningún paso intermedio por simple que sea.
  • En el apartado de Resultados esperados se puede detallar el resultado en un párrafo o en forma de lista si hay resultados intermedios. La elección del formato depende de que caso hace más comprensible el resultado final.
  • Se permite el uso de imágenes en los apartados Pasos y Resultados esperados, pero si se puede describir en texto mejor.

En conclusión, los casos de prueba son elemento necesario en un ambiente de desarrollo software ya que garantizan que los productos presenten resultados correctos, cumpliendo una serie de requisitos. Siendo la implantación de estos una forma de aportar más calidad y profesionalidad al software.

 Referencias:

Protocolo para la elaboración de casos de prueba.

Artículo escrito por José Olivas Carriquí

by jolicar at September 18, 2020 08:20 AM

September 17, 2020

Jo Cook and Jared Morgan have been presented with awards for Google's Open Source Peer Bonus Program. The award is a recognition and thank you to people who go above and beyond in their contributions to open source. It also includes a token financial contribution - enough to take the family out for dinner at a nice restaurant.

Well done Jo and Jared, you really deserve it:

Jared Morgan, Write the Docs podcast host

Jared Morgan

Jared is a core contributor and community builder within The Good Docs Project. As an experienced technical writer, he has contributed to many of our initial set of writing templates and then helped absorb feedback from our community. He is well respected and well connected within the technical writing community, helping to inspire other thought leading technical writers to come and join us.

This year, 2020, he has signed up as a Season of Docs mentor for The Good Docs Project.

In a related activity, he has also helped spread knowledge within the technical writing community, by co-hosting the Write the Docs podcast.

Jo Cook, explaining docs at DevRel conference

Jo Cook

Jo is an enabler of open source communities. She commits large chunks of her volunteer time to working on the hard problems that others don't tackle. She is someone you can rely upon when needed, and she steps back when her skill-sets are more valuable elsewhere.

A few highlights of her volunteer activities over the last couple of decades include:
  • Help set up The Good Docs Project, doing much of the grunt work in setting up open source processes.
  • Mentoring a Season of Docs tech writer and other community contributors for the GeoNetwork project.
  • Presenting at numerous conferences on topics of open source, documentation, and geospatial.
  • Playing lead roles in setting up conferences for the Open Source Geospatial foundation.
  • Building the Portable GIS distribution of Open Source Geospatial software.
  • Serving on the board of the international Open Source Geospatial foundation (OSGeo).
  • and more ...

by Cameron Shorter (noreply@blogger.com) at September 17, 2020 08:47 PM

Tal y como se describe en el post de 04/11/2019 titulado Proyecto GSoC 2019: Nuevas reglas para el Marco de Topología (1) en sus primeros párrafos, existe una necesidad de automatizar procesos iterativos o rutinarios con el fin de centrar toda la capacidad del ser humano en la creación y diseño de nuevas fórmulas de trabajo. En otras palabras, dejar el trabajo tedioso a las máquinas y el desarrollo de nuevas soluciones al ser humano.

El proyecto titulado “Nuevas reglas para el Marco de Topología de gvSIG Desktop” realizado durante el programa Google Summer of Code 2020 mediante la organización OSGeo (Open Source Geospatial Foundation) y la Asociación gvSIG no es más que un ejemplo de lo descrito en el párrafo anterior. Una forma de encauzar a las personas en la creación de estrategias, resolución de estas y análisis de resultados de tipo topológico, dejando el trabajo repetitivo a los computadores.

Dicho proyecto al igual que el elaborado con el mismo título durante el GSOC 2019 consiste en la creación de nuevas reglas topológicas y elementos asociados, haciendo así más rico el ecosistema de topología del software. Además, también corrige y mejora algunas de las ya existentes mejorando ya no solo la cantidad sino también la calidad.

Las reglas topológicas tratadas durante dicho proyecto son:

  • Debe estar correctamente dentro (Must be properly inside). Esta es una regla topología cuyo primer dataset es de tipo punto, el cual se evalúa frente a un segundo dataset de tipo polígono. Los puntos cumplirán la regla si estos se encuentran en el interior de los polígonos, no en el exterior o en el borde de estos. Los puntos que no cumplan la regla serán reportados mediante entrada en el reporte de errores.
  • Contiene puntos (Contains Point). Esta regla topológica tiene como capa primaria una capa de polígonos, mientras que la capa secundaria es de puntos. En esta regla se evalúa si los polígonos tienen en su interior puntos, no en su exterior o extremos. Un polígono cumple la regla si en su interior se situa al menos un punto. Los polígonos que no cumplan la regla serán reportados mediante entrada en el reporte de errores.
  • Contiene un punto (Contains one point). Dicha regla topológica utiliza como dataset primario una capa de polígonos y como dataset secundario una capa de puntos. La regla presenta gran similitud con la anterior con la diferencia que solo los polígonos con un punto en su interior harán cierta la regla. Al igual que la anterior el punto tiene que estar en su interior, no en el exterior o extremo de los polígonos. Los polígonos que no cumplan la regla serán reportados mediante entrada en el reporte de errores.
  • Deben cubrirse unos a otros (Must Cover Each Other). Esta regla topología trabaja con dos capas de polígonos. De modo que todos los polígonos de una capa tienen que cubrirse por los polígonos de la restante y viceversa. En el caso que una capa presente polígonos o secciones de polígonos no cubiertos, estos elementos serán reportados en el reporte de errores.
  • UDR (User Defined Rule). Una regla topológica experimental atípica que permite al usuario especificar la expresión condicional de la regla, así como acción de corrección a aplicar en los casos que no la cumplan. De modo que, conociendo la expresión necesaria, esta regla puede implementar todas las reglas ya existentes o no en el software. Hay que especificar que tanto las expresiones condicionales como las que indican la acción de corrección se realizan con el lenguaje propio de gvSIG llamado COSA. Además de la codificación inherente a la creación de la regla en cuestión fue necesario crear nuevas funcionalidades y opciones en el motor topológico de gvSIG Desktop que entre otras cosas permite añadir parámetros auxiliares a las reglas topológicas, abriéndose así nuevas posibilidades en futuros desarrollos.

Paralelo al desarrollo de las reglas en el proyecto en cuestión se implementan varias acciones correctoras, las cuales tratan las geometrías incluidas en el reporte de errores. Aclarar que cada regla topología presenta un tipo de acción correctora adaptada para la regla en cuestión.

Las acciones correctoras desarrolladas en el proyecto son:

  • Eliminar (Delete). Esta acción correctora como su propio nombre indica elimina la geometría o elemento calificado como error. La acción correctora eliminar es común a todas las reglas topológicas en el Proyecto GSoC 2020: Nuevas reglas para el Marco de Topología (1).
  • Crear elemento (Create feature). La acción en cuestión crea un elemento o elementos en los casos que la geometría que presenta el error sea errónea por falta de estos. Dicha acción se utiliza en las reglas topológicas Contiene puntos (Contains Point), Contiene un punto (Contains one point) y Deben cubrirse unos a otros (Must Cover Each Other).
  • Acción correctiva definida por el usuario (User corrective expresión). Esta acción correctiva es peculiar ya que puede ser cualquiera, siempre que el usuario la defina de manera correcta mediante el lenguaje de creación de expresiones propio de gvSIG. Como es lógico esta acción solo esta implementado en la regla UDR (User Defined Rule).

Como componentes finales para las reglas topológicas del proyecto se genera documentación de dichas reglas y acciones así como un plan de pruebas constituido por números casos de prueba que permitan garantizar el correcto funcionamiento de las reglas desarrolladas. El proceso de creación de planes de prueba se abordará en una de las siguientes entradas del gvSIG blog.

En conclusión, como resultado del Proyecto GSoC 2020: Nuevas reglas para el Marco de Topología (1) el marco de topología de gvSIG Desktop aumenta su número de reglas así como la calidad de estas haciendo cada día más un software más competitivo y lo que es más importante, útil para la comunidad.

Referencias:

Wiki con toda la información del proyecto anterior en idioma inglés. (Proyecto elaborado por José Olivas Carriquí).

Este año también se ha llevado a cabo un proyecto con igual nombre y temática realizado por Mauro Carlevaro el cual se detalla en próximos posts.

Artículo escrito por: José Olivas Carriquí

by jolicar at September 17, 2020 12:00 PM

September 16, 2020

Dentro de los acuerdos que la Asociación gvSIG mantiene con diversas universidades, se encuentra el fomento de prácticas de los alumnos alrededor de la Suite gvSIG. En la actualidad, varios alumnos y alumnas de la UAEMEX (Universidad Autónoma del Estado de México) se encuentran iniciando este tipo de actividades tutorizadas por el equipo de gvSIG.

Una de las alumnas, Rosario García Ramírez, está desarrollando un trabajo relacionado con la aplicación de la Suite gvSIG (gvSIG Desktop y gvSIG Online) al área de la criminología, gestión del delito y convivencia ciudadana. Como primer paso, durante sus primeros días de prácticas ha realizado un tutorial titulado “Feminicidios en México: Los datos son más que visibles“, mediante el cual muestra de forma sencilla, los pasos seguidos para analizar los datos de feminicidios con arma blanca cometidos en México en 2019 y parte de 2020.

Un tutorial muy interesante, que puede servir de guía para otros análisis geoespaciales que se quieran realizar, y que permite obtener con pocos pasos unos resultados notables. Por este motivo, lo compartimos. El tutorial comienza con esta introducción:

«En México se vive una crisis de violencia en feminicidios que es urgente resolver. Diariamente, cientos de niñas y mujeres son agredidas, violadas, asesinadas y revictimizadas por individuos e instituciones que nos violentan tanto en lo social como en lo político y económico. Las cifras son de horror y sin embargo poco sabemos de la magnitud real del fenómeno» (Sánchez et al.2020).

El objetivo del presente ejercicio es identificar en México, el estado más afectado en feminicidios con arma blanca en el periodo 2019 y parte del 2020 realizando una comparación de años identificado un posible aumento o disminución de registros. Para ello se trabajará con una base de datos del Secretariado Ejecutivo del Sistema Nacional de Seguridad Pública, analizando los datos y cartografiando para una:
– Utilización de la plataforma gvSIG
– Identificación de los primeros 3 estados más conflictivos
– Obtención de mapas cuantitativos
– Comparación de feminicidios en el periodo 2019-2020

Podéis descargar el tutorial aquí

by Alvaro at September 16, 2020 06:48 AM

September 15, 2020

La certification du cours des Systèmes d’information géographiques appliqués à l’archéologie est maintenant disponible (ce cours est également disponible en anglais et en espagnol).

Cette certification s’ouvre avec la publication des 7 modules qui composent le cours, mais elle continuera d’être ouverte de façon continue, pour que tout utilisateur puisse l’obtenir au moment où il termine les modules.

Pour pouvoir effectuer le cours (gratuit), il n’est pas nécessaire de s’inscrire sur quelconque portail, mais il suffit de suivre les vidéos des modules qui le composent (liens à la fin de ce post).

Si vous souhaitez obtenir la certification du cours, qui est optionnelle, il vous faudra compléter un exercice complet, qui inclut l’ensemble des thèmes abordés durant le cours. Il est nécessaire de réaliser correctement au moins 6 exercices sur 9 pour valider les connaissances aquises lors du cours. L’évaluation sera effectuée par un tuteur.

Outre la livraison et l’approbation de l’exercice, la certification a un coût, nécessaire pour couvrir les dépenses relatives à l’évaluation et à la certification. Ce coût sera de 25 euros.

La certification sera émise par gvSIG Asociacion, et incluera un Certificat de réussite du cours.

L’exercice et la cartographie à utiliser sont à télécharger depuis les liens suivants :

Dans la première partie de l’exercice pratique, vous trouverez les explications en détail sur les étapes à suivre pour envoyer l’exercice, ainsi que pour effectuer le paiement pour obtenir le certificat.

Le cours est composé des modules suivants :

Thème 1 : Préparation d’un projet archéologique : vues, couches et tables

Thème 2 : Digitalisation de zones de prospection

Thème 3 : Analyse de résultats de prospections : Géotraitements vectoriels

Thème 4 : Travail avec des cartes anciennes : géoréférencement d’images

Thème 5 : Analyse territoriale de sites archéologiques : Géotraitements raster et Modèles Numériques de Terrain

Thème 6 : Analyse hydrologique pour localiser du matériel ou des sites archéologiques

Thème 7 : Création de cartes pour un projet archéologique

by mateoboudon at September 15, 2020 02:01 PM

September 14, 2020

We have recently been working for the French Space Agency ( CNES ) who needed to store and visualize satellite rasters in a cloud platform. They want to access the image raw data, with no transformation, in order to fullfill deep analysis like instrument calibration. Using classic cartographic server standard like WMS or TMS is not an option because those services transform datasets in already rendered tiles.

We chose to use a quite recent format managed by GDAL, the COG (Cloud Optimize Geotiff) and target OVH cloud platform for it provides OpenStack, a open source cloud computing platform.

How it works

A COG file is a GEOTiff file which inner structure is tiled, meaning that the whole picture is divided in fixed size tile (256 x 256 pixels for instance) so you can efficiently retrieve parts of the raster. In addition to the HTTP/1.1 standard feature range request, it is possible to get specific tiles of an image through the network without downloading the entire raster.

We used a service provided by OpenStack, called Object Storage to serve the COG imagery. Object storage allows to store and retrieve file as objects using HTTP GET/POST requests.

Why not WCS ?

Web Coverage Service standard could have been an option. A WCS server can serve raw data according to a given geographic extent. It’s completely possible to deploy a container or a VPS (Virtual Private Server) running a WCS Server in a cloud plateform. The main advantages of the COG solution over WCS Server is that you don’t have to deal with the burden of deploying a server, like giving it ressources, configuring load balancing, handle updates, etc…

The beauty of COG solution is its simplicity. It is only HTTP requests, and everything else (rendering for instance) is done on the client side.

Step by step

Here are the different steps you’d have to go through if you’re willing to navigate in a big raster image directly from the cloud.

First, let’s generate a COG file

gdal_translate inputfile.tif cogfile.tif -co TILED=YES -co COPY_SRC_OVERVIEWS=YES -co COMPRESS=DEFLATE

Install your openstack-client, it can be achieved easily with Python pip install command line

$ pip install python-openstackclient

Next, configure your openstack client in order to generate an athentification token. To do so you need to download your project specific openrc file to setup your environment)

$ source myproject-openrc.sh
Please enter your OpenStack Password for project myproject as user myuser:
**********
$ openstack token issue                                 
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field      | Value                                                                                                                                                                                   |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| expires    | 2020-07-21T08:15:12+0000                                                                                                                                                                |
| id         | xxxx_my_token_xxxx
| project_id | 97e2e750f1904b41b76f80a50dabde0a                                                                                                                                                        |
| user_id    | 18f7ccaf1a2d4344a4e35f0d84eb065e                                                                                                                                                        |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

You are now good to push you COG file to the cloud instance

openstack object create MyContainer cogfile.tif --name cogfile.tif

Before starting QGIS, 2 environment variables need to be set.  (replace xxxx_my_token_xxxx with the token you’d just come to generate)

$ export SWIFT_AUTH_TOKEN=xxxx_my_token_xxxx
$ export SWIFT_STORAGE_URL=https://storage.sbg.cloud.ovh.net/v1/AUTH_$OS_PROJECT_ID

It can also be done directly from the QGIS Python console by setting those variable using the os.environ.

Finally, add a cloud raster data source in in QGIS

You can now navigating into your image directly reading it from the cloud

© CNES 2018, Distribution Airbus DS

Performances

While panning in the map, QGIS will download only few tiles from the image in order to cover the view extent. The display latency that you could see in the video depends essentially on:

  • The number of band of your image
  • The pixel size
  • Your internet connection (mine, the one use for the video, is not an awesome one)

Note that the white flickering that you could see when you move in the map and the raster is refreshed should be removed in next version of QGIS according to this QEP.

What’s next ?

Thanks so much to the GDAL and QGIS contributors for adding such a nice feature ! It brings lots of possibilities for organizations that have to deal with great number of big raster and just want to explore part of it.

We are already thinking about further improvments (ease authentification, better integration with processing…), so if you’re willing to fund them or just want to know more about QGIS, feel free to contact us at infos+data@oslandia.com. And please have a look at our support offering for QGIS.

by Julien Cabieces at September 14, 2020 11:20 AM

September 13, 2020

I'm continuing the development of the new version 7 of the Semi-Automatic Classification Plugin (SCP) for QGIS.

In this post I'll briefly describe the download and processing of Sentinel-1 GRD images in SCP.

Synthetic Aperture Radar (SAR) is a technique of active remote sensing that is the sensor platform emits microwaves in order to acquire images of the ground (ESA, 2020). In fact, the sensor platform emits the radiation (at a specific wavelength) and measures the magnitude and the phase of radiation that bounces back from the ground to the sensor.

Sentinel-1 is a Copernicus mission of satellites that operate at C-band to provide SAR imagery at medium resolution (about 10m).

The Sentinel-1 constellation provides high revisit time (about 5 days), a wide swath (250 km), and acquires images in different operational modes. 
Ground Range Detected (GRD, Level-1 data with multi-looked intensity only) is a product systematically delivered by Copernicus. Sentinel-1 supports dual polarization, which are horizontal (H) or vertical (V); VV and VH polarimetric channels are available to classify and analyse land cover such as built-up areas or vegetation.

SCP will include the search and download of Sentinel-1 GRD images, in the same interface that allows for the download of other satellite images, such as Sentinel-2 and Landsat and more.

Sentinel-1 download

Read more »

by Luca Congedo (noreply@blogger.com) at September 13, 2020 06:17 PM

September 12, 2020

On Thursday, I was awarded the 2020 Sol Katz award for Free and Open Source Software for Geospatial. I feel very honored to have been selected for this award and I’d like to take this opportunity to share a few words of thanks:

As people working in open source projects, we are constantly reminded that we are all standing on the shoulders of giants. However, particularly this year, we also see just how important small personal connections are. For me, my involvement with open source communities really took off when I joined the QGIS hackfest in Vienna in 2009 and I felt that my participation was really appreciated and welcome. I couldn’t imagine being without these connections anymore.

Thank you to the whole QGIS community, particularly my fellow PSC members both current and former: Tim, Andreas, Jürgen, Richard, Paolo, Otto, Marco Hugentobler, Alessandro, our new chair Marco Bernasocchi, and of course QGIS founder Gary Sherman for starting this awesome project and for still being around and actively promoting geospatial open source by publishing so many great books covering multiple different OSGeo projects.

I’d also like to thank my partner and my family for being incredibly understanding whenever I’m spend my time geeking out over a new programming project, data analysis, forum question, or conference talk.

Thank you also to my friends, colleagues and fellow members of the larger OSGeo community for sharing ideas, providing valuable feedback, and spreading the word about all the great work that’s going on all around us.

I’m constantly amazed by all the innovation happening to nourish and grow our community. And I’m looking forward to continue being a part of these efforts.

Thank you!

 

by underdark at September 12, 2020 11:38 AM

September 11, 2020

La date limite pour soumettre des propositions de communication pour la 16ème conférence internationale gvSIG  (évènement en ligne cette année) a été étendue. La nouvelle date limite est le 6 Octobre.

Etant un évènement virtuel, toute personne ou organisation pourra présenter son projet sur gvSIG de partout dans le monde, ne nécessitant qu’une connection internet. Toutes les informations sur la façon d’envoyer les propositions sont indiquées dans la section Communications du site de l’évènement. Les propositions en anglais, espagnol et français sont acceptées.

Les inscriptions seront gratuites et pourront être faites une fois que le programme est publié.

Nous attendons votre participation !

by mateoboudon at September 11, 2020 10:44 AM

September 10, 2020

September 09, 2020

gvSIG has two distributions: portable and installable. In the installable version we must follow the installation wizard, and a shortcut is automatically created on our Desktop and at Home menu. On the other hand, in the portable version we must unzip the downloaded .zip file and we can run gvSIG directly, without installing anything on our computer and even having it on a removable disk, such as a pen-drive.

In the case of portable versions, this shortcut is not created, but we can do it. Depending on the operating system we will do it in the following way:

Windows:

If we want to start a portable version of gvSIG, we will access to the folder where we have that version (once the zip has been unzipped), and we will double-click on the gvsig-desktop.exe file.

If we want to create a shortcut to start the application, we will click with the right mouse button on that .exe file, and then we will select the option “Send to -> Desktop (create shortcut)”. In this way it will create the shortcut on the Desktop, and we just have to double-click on it to open gvSIG.

If we click on the shortcut created with the right mouse button we can change the icon, being able to select, for example, the”gvsig-icon48x48.png” file that we have in the portable version folder.

If we download a new portable version we will have to create a new shortcut on the new exe file, or we can change the properties of the previously shortcut created on the Desktop, indicating the path to the new file.

Linux:

In case we have Linux, once the zip file of the portable version has been unzipped, we can run the application by double-clicking on the gvSIG.sh file that we have in the unzipped folder (on some computers it may not work, depending on the characteristics of the operating system), or we can also do it by opening a Terminal, accessing to the path where we have the portable version, and running the gvSIG.sh file with the command: “./gvSIG.sh”.

If we want to create a shortcut on our Desktop, it can be done by creating a .desktop file and configuring it to call the gvSIG.sh file. If you are not used to working with Linux, we have created some instructions that will make this work easy. For this we have created a boot file, which you can download from:

http://downloads.gvsig.org/download/gvsig-desktop/runtimes/portable_version_shortcut/gvSIG%20desktop%202.5.1_3033_ENG.desktop

You must download it on the Desktop. Then you open the text editor that you have (such as ‘gedit’ or ‘Kate’), then go to Open file, and open the file that you have downloaded. In that file you have to change the name (for your gvSIG version) and write the full path to the gvSIG.sh file and the gvSIG icon. They are these 3 lines:

Name=gvSIG desktop 2.5.1_3033
Exec=path to the gvSIG.sh file in the portable version folder.
Icon=path to the gvsig-icon48x48.png file in the portable version folder.

(Check that you do not have spaces at the end of the paths).

You should have something like this:

Name=gvSIG desktop 2.5.0 final
Exec=/home/test/gvSIG-desktop-2.5.0-2930-final-lin_ubuntu_14.04-x86/gvSIG.sh
Icon=/home/test/gvSIG-desktop-2.5.0-2930-final-lin_ubuntu_14.04-x86/gvsig-icon48x48.png

Once the file is saved, you can start gvSIG by double-clicking on it.

If we download a new portable version we must follow the same steps, or we can edit that file again and indicate the path to the new boot file and the new icon.

by Mario at September 09, 2020 08:54 AM

gvSIG dispone de dos distribuciones, una portable y una instalable. En la instalable debemos seguir el asistente de instalación, y automáticamente se crea un acceso directo en nuestro Escritorio y en el menú Inicio. En cambio, en la versión portable debemos descomprimir el fichero .zip descargado y ya podemos ejecutar gvSIG directamente, sin instalar nada en nuestro equipo y pudiendo incluso tenerla en un disco extraíble, como un pen-drive.

En el caso de las versiones portables no se crea ese acceso directo, pero podemos crearlo nosotros. Según el sistema operativo lo haremos de la siguiente forma:

Windows:

Si queremos arrancar una versión portable de gvSIG iremos a la carpeta donde tenemos dicha versión (una vez descomprimido el zip), y pulsaremos doble click sobre el fichero gvsig-desktop.exe.

Si lo que queremos es crear un acceso directo para arrancar la aplicación, con el botón secundario del ratón sobre dicho fichero .exe seleccionaremos la opción “Enviar a->Escritorio (acceso directo)”. De esa forma nos creará el enlace directo en el Escritorio, y ya solo debemos hacer doble-click sobre él para abrir gvSIG.

Si pinchamos sobre el acceso creado con el botón secundario del ratón podremos cambiarle el icono, pudiendo seleccionar por ejemplo el fichero “gvsig-icon48x48.png” que tenemos en la carpeta de la portable.

Si descargamos una nueva versión portable deberemos crear un nuevo acceso directo sobre el nuevo fichero de arranque, o bien podemos cambiar las propiedades del acceso creado anteriormente en el Escritorio, indicando la ruta al nuevo fichero.

Linux:

En caso de que tengamos Linux, una vez descomprimido el zip de la portable, podremos arrancar la aplicación con doble click sobre el fichero gvSIG.sh que tenemos en la carpeta descomprimida (en algunos equipos puede no funcionar, según las características del sistema operativo), o también podremos hacerlo abriendo un Terminal, yendo a la ruta donde tenemos la portable, y ejecutando el fichero gvSIG.sh con el comando: “./gvSIG.sh”.

Si queremos crear un acceso directo en nuestro Escritorio, se puede hacer creando un fichero .desktop y configurándolo para que llame al fichero gvSIG.sh. Si no estás acostumbrado a trabajar con Linux, hemos creado unas instrucciones que te facilitará este trabajo. Para ello hemos creado un fichero de arranque de la portable, que puedes descargar desde:

http://downloads.gvsig.org/download/gvsig-desktop/runtimes/portable_version_shortcut/gvSIG%20desktop%202.5.1_3033.desktop

Lo debes dejar en el Escritorio. Luego abres el editor de texto que tengas (como por ejemplo ‘gedit’ o ‘Kate’), vas a Abrir fichero, y abres el fichero que has descargado. En él cambias el nombre (por el de tu versión de gvSIG) y pones la ruta completa al gvSIG.sh de tu portable y al icono de gvSIG. Son estas 3 líneas:

Name=gvSIG desktop 2.5.1_3033
Exec=ruta al gvSIG.sh de la portable
Icon=ruta al fichero gvsig-icon48x48.png de la carpeta de la portable.

(revisa que no tengas espacios al final de las rutas).

Deberá quedarte algo como:

Name=gvSIG desktop 2.5.0 final
Exec=/home/test/gvSIG-desktop-2.5.0-2930-final-lin_ubuntu_14.04-x86/gvSIG.sh
Icon=/home/test/gvSIG-desktop-2.5.0-2930-final-lin_ubuntu_14.04-x86/gvsig-icon48x48.png

Una vez guardado el fichero podrás arrancar gvSIG con doble-click sobre él.

Si descargamos una nueva versión portable deberemos seguir los mismos pasos, o bien podemos editar de nuevo ese fichero e indicar la ruta al nuevo fichero de arranque y al nuevo icono.

by Mario at September 09, 2020 08:54 AM

September 08, 2020

The GeoServer community is pleased to share the availability of GeoServer 2.18-RC Release Candidate for testing. Downloads are available (zip and war) along with documentation and more than 40 extensions.

This is a GeoServer release candidate made in conjunction with GeoTools 24-RC and GeoWebCache 1.18-RC.

  • Release candidates are a community building exercise and are not intended for production use.
  • We ask the community (everyone: individuals, organizations, service providers) to download and thoroughly test this release candidate and report back.
  • Participating in testing release candidates is a key expectation of our open source social contract. We make an effort to thank each person who tests in our release announcement and project presentations!

We would like to thank everyone who contributed to this release. Jody Garnett (GeoCat) for this release candidate downloads and setting up the 2.18.x branch.

Release Candidate Testing Priorities

We would like to ask for your assistance testing the following:

  • The number one testing priority is to try out GeoServer with your data! Mass market open source thrives on having many people to review. Data driven open source like GeoServer thrives on exposure to many datasets.
  • The rest of this blog post highlights new features for GeoServer 2.17, please try out these features, read the documentation links, and ask questions.

Thanks to Jukka Rahkonen and Brad Hards for initial testing. To add your name to the list for the 2.18 release announcement: download the release candidate, try it out, and let us know (on the user list, twitter, or LinkedIn).

Black Lives Matter

The casual use of the word “slave” in computer software is an unnecessary reference to a painful human experience that continue to impact society.

  • Change to the use of primary / replica in description of GeoServer clustering (although new diagrams would be welcome)
  • Change to use of allow-list / deny-list
  • Changed to use of keystore password
  • Changing our repository to a “main” branch will be scheduled when both the git command line tool and GitHub repository infrastructure roll out planned improvements for a seamless transition.

David Blasby (GeoCat) worked on this issue as part of the OSGeo Bolsena 2020 Work-from-home code-sprint.

User interface creature comforts

A couple small but important changes to the GeoServer user interface make a significant difference to how you interact with the application and how easy it is to publish your data.

Andrea Aime (GeoSolutions) has taken the time to add an “Apply” functionality to most page, and ensure each screen has consistent buttons:

  • Apply (new): used to apply your setting change the running application so you can try them out, leaving the page open so you can experiment with applying different settings to see the effect.
  • Save: saves your setting change, returning to the initial welcome page.
  • Cancel: returns to the welcome page, abandoning and setting changes made.
Consistent Save, Apply, Cancel buttons for pages

Some configuration activities, such as WPS security, use nested pages to fine tune configuration options. These pages now consistently use OK and Cancel to return from a nested page.

Consistent OK, Cancel buttons for nested pages

Finally Michel Gabriël (GeoCat) arranged for these buttons to float to remain visible when scrolling through long pages.

The combination of consistent button names, in a consistent location, with an Apply button provide an improved experience when configuring GeoServer.

Jiffle scripts now supporting multi-band outputs

The Jiffle scripting language is used to run raster algebra against one or more input raster layers. In this release we added the ability to generate multi-band outputs, whilst previous versions of Jiffle could generate only single-banded outputs.

Here is an interesting example of how this can be useful. Let’s take an image mosaic with time dimension, and configure its generation mode to “stack”. This will make the mosaic use each image matching the request as an output band. Then, let’s make a WMS request with two times, thus, generating an image with two bands, allowing for a before/after comparison, and use the following style, reporting in output the before, the after, and the difference, using Jiffle as a rendering transformation:

<?xml version="1.0" encoding="UTF-8"?>
<StyledLayerDescriptor xmlns="http://www.opengis.net/sld"
 xmlns:ogc="http://www.opengis.net/ogc"
 xmlns:xlink="http://www.w3.org/1999/xlink"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd"
 version="1.0.0">
  <NamedLayer>
    <Name>InputLayer</Name>
    <UserStyle>
      <Title>Time comparison</Title>
      <FeatureTypeStyle>
        <Transformation>
          <ogc:Function name="ras:Jiffle">
            <ogc:Function name="parameter">
              <ogc:Literal>coverage</ogc:Literal>
            </ogc:Function>
            <ogc:Function name="parameter">
              <ogc:Literal>script</ogc:Literal>
              <ogc:Literal>
                before = src[0];
                after = src[1];
                dest[0] = before;
                dest[1] = after;
                dest[2] = after - before;
              </ogc:Literal>
            </ogc:Function>
            <ogc:Function name="parameter">
              <ogc:Literal>bandNames</ogc:Literal>
              <ogc:Literal>before,after,difference</ogc:Literal>
            </ogc:Function>
          </ogc:Function>
        </Transformation>
        <Rule>
          <RasterSymbolizer>
            <Opacity>1.0</Opacity>
            <ChannelSelection>
              <GrayChannel>
                <SourceChannelName>3</SourceChannelName>
              </GrayChannel>
            </ChannelSelection>
            <ColorMap>
              <ColorMapEntry color="#800000" quantity="-1"/>
              <ColorMapEntry color="#008000" quantity="1"/>
            </ColorMap>
          </RasterSymbolizer>
        </Rule>
      </FeatureTypeStyle>
    </UserStyle>
  </NamedLayer>
</StyledLayerDescriptor>

The result is a color code map showing red when the change is negative, green where it’s positive. As a bonus, running a GetFeatureInfo on the map would return all 3 values, before, after, and difference.

Source maps are also available for reference:

Map projections news

This release comes with support for Goode’s interrupted Homolosine, including both the projection itself, and the advanced projection handling machinery to handle on the fly source data slicing.

This means one can use a common map, like Natural Earth or OSM land masses and seas, and use it without any preparation, obtaining the following:

Still in the projections support department, we can cite:

  • Support for the Polyconic spherical case
  • Improvements in the Azimuthal Equidistant support, with better handling of source slicing when the CRS has false origins.

The following map is a polar Azimuthal Equidistant, with false origins, generated from data originally in web mercator (hence the hole in Antarctica):

Vector tiles improvements

The vector tiles extension can now work hand-in-hand with the pre-generalized data store, significantly speeding up the generation of MVTs out of a large dataset. A typical example of this case is generating vector tiles out of a OpenStreetMap import performed via imposm3, along with generalized tables.

Map-box GL styles language support improved

MBStyle support continues to improve with support for the dynamic expressions allowing a both feature attributes and “camera” information such as zoom level to be included.

{ "version": 8,
  "name": "landmarks",
  "layers": [
      {   "id": "Expression example",
          "type": "circle",
          "paint": {
              "circle-color": "#dd9933",
              "circle-radius": ["/",["get","LAND"],15],
          }
      }
  ]
}
Mapbox Style Expression example

GeoServer continues to support the earlier “function stop” approach for compatibility with the vast majority of examples online.

Community Modules

The GeoServer project devotes space to community research and development activities.

  • The GeoPackage community module is having a breakout of creativity with a host of fascinating functionality being added by Andrea Amie (GeoSolutions).
    • Dumping a GeoPackage with WPS or WFS output formats is now significantly faster, thanks to insert batching and improved selection of settings/pragma while creating the SQLite database.
    • GeoPackage WPS output can now inline linked metadata and add OWS Contexts for request and data, providing full provenance information.
    • GeoPackage WPS output can now include styles, based on an experimental style extension along with semantic annotations linking styles to data.
    • Activity is ongoing to add a generalized tables extension, similar to the pre-generalized store, but built into the GeoPackage itself.
  • A new module looking at attribute labeling has been started by Fernando Miño.
  • Fixed an issue with JMS plugin replicating SLD styles
  • JDBCStore speed improvement with automatic caching of select directories
  • The WPS download module can now preserve the original resolutions when working against heterogeneous CRS mosaic, for the granules that are matching the requested output CRS.
  • The GRS module has been made available, adding ArcGIS REST compatibility API.
  • The JSON-LD community module has been extended to support custom JSON output too, and renamed to wfs-template.

If you are interested in seeing any of this work included on the GeoServer roadmap contact the developer to learn how to participate or fund the activity.

And more

Other fixes and improvements include:

  • LayerGroups now list a default style in the capabilities document for greater client compatibility
  • CSW module performance fix when paging output
  • Josh Fix introduced a proposal to help determine GridCoverageReader object types to help work with Cloud Optimized GeoTIFF images.
  • Importer has been improved with better logging and error messages
  • REST API allows changing name and workspace of a data store
  • The latest JTS 1.17.1 release
  • MetadataLinkInfo allows more metadata types to be edited, including optional about field
  • GetFeatureInfo templates can now call static methods, such as Math functions, providing additional control.
  • Styled editor now provides a choose image dialog for setting legend image
  • PDF output can now include WMS decorations

Find out more in the release notes.

About GeoServer 2.18

Additional information on GeoServer 2.18 series:

by jgarnett at September 08, 2020 10:38 PM

The deadline for submitting communication proposals for 16th International gvSIG Conference (online event this year), has been extended. The new deadline is October 6th.

Being a virtual event, any person or organization will be able to present their project about gvSIG from anywhere in the world, just needing internet connection. All the information about proposals sending is indicated at Communications section of the event website. English and Spanish proposals are accepted.

Registrations will be free of cost and they will be able to be done once the program is published.

We expect your participation!

by Mario at September 08, 2020 02:12 PM

El plazo de envío de resúmenes para las 16as Jornadas Internacionales gvSIG, que este año serán de forma online del 4 al 6 de noviembre, ha sido ampliado unos días, siendo la nueva fecha límite el día 6 de octubre.

Al ser unas jornadas virtuales cualquier persona u organización puede presentar su proyecto sobre gvSIG desde cualquier parte del mundo, necesitando únicamente una conexión a internet, con lo que os animamos a presentar vuestras propuestas. Toda la información sobre el envío de comunicaciones podéis encontrarla en la web del evento. Se pueden enviar propuestas en español e inglés.

La inscripción a las jornadas será gratuita, y podrá realizarse una vez publicado el programa de las mismas.

¡Esperamos vuestra participación!

by Mario at September 08, 2020 02:12 PM

September 07, 2020

September 06, 2020

I am glad to announce that I'm working on the development of the new version 7 of the Semi-Automatic Classification Plugin (SCP) for QGIS.

The main improvement will be the conversion of several functions, such as the Preprocessing, the Classification and Band calc tools, from single-threading to multi-threading. This is a very big change that will allow to speedup the processing and reduce the computation time, exploiting the multi-core processors available in the system. In fact, with multi-threading the process is distributed among multiple threads (i.e. each thread performs a part of the calculation) and the result is computed very rapidly (if compared to single thread).

Other relevant changes will be:
  • improving the Band calc tool to perform iterations of raster calculation and filter Band sets using the acquisition date information; this will allow to perform calculation on time series of images;
  • the download and processing of Sentinel-1 images through the integration with ESA SNAP;
  • add the Random Forest classification through the integration with ESA SNAP; this will allow to use ROIs and Band sets defined in SCP and perform the Random Forest classification;
  • improving the Batch tool to initiate QGIS Processing tools from SCP; this will allow to extend the possibilities of calculation and use the QGIS Processing output with SCP tools in a script;
  • new raster tools.

Of course, the interface will be revamped. Following an image of the new interface with a tree menu and a filter that will allow to rapidly navigate through all the SCP functions.

The new interface of SCP


Hopefully, I'll complete the development of the new SCP 7 in a few weeks.
I am going to post other news on this blog to illustrate the progress of SCP development.

For any comment or question, join the Facebook group about the Semi-Automatic Classification Plugin.

by Luca Congedo (noreply@blogger.com) at September 06, 2020 08:00 AM

September 04, 2020

September 02, 2020

September 01, 2020

August 31, 2020

💥ÚLTIMOS DIAS PARA REALIZAR SUA MATRÍCULA!💥

👉CURSO ONLINE EXCLUSIVO NO MERCADO – GEOSERVER – EAD AO VIVO:

Faça sua inscrição e garanta sua vaga até o dia 06/09!

O GeoServer é um servidor de Web Map Service (WMS), Web Coverage Service (WCS) e de Web Feature Service-Transaction (WFS-T) completamente funcional que segue as especificações da Open Geospatial Consortium (OGC).

Aprenda a trabalhar com um software livre, que permite o desenvolvimento de soluções de mapas, integrando diversos repositórios de dados geográficos com simplicidade e alta performance.

Aproveite, oportunidade única para você aprimorar seus conhecimentos!

Se interessou? Entre em contato agora mesmo:
SITE: https://geocursos.com.br/geoserver
E-mail: contato@geocursos.com.br

by Fernando Quadro at August 31, 2020 03:17 PM

We are pleased to announce the release of GeoServer 2.16.5 with downloads (war|zip), documentation and extensions.

This release is made in conjunction with GeoTools 22.5. This is the final planned maintenance release and we highly recommend users to switch to the 2.17 branch for production systems.

Thanks to everyone who contributed, and Ian Turton (Astun Technology) for making this release.

Improvements and Fixes

[GEOS-6467] – UI bug in disabling tile caching for layers
[GEOS-8569] – JSON encoding on NaN values fails
[GEOS-9266] – Geopackage raster table with dots in the name cannot be added
[GEOS-9482] – Nearest Match NPE if source database table is empty
[GEOS-9539] – URLKvpParser encodes urls also when not needed
[GEOS-9622] – NullPointerException when using WMS vendor parameter “CLIP” on an ImageMosaic based layer
[GEOS-9629] – Legend Graphic fails on first visit to publish tab on a new layer publish
[GEOS-9638] – Duplicate SRS in Native SRS List selection on WFS 2.0.0 layer
[GEOS-9639] – Add OGC URN syntax support for Native SRS selection
[GEOS-9649] – NullPointerException for geoJSON output format with ComplexFeatures if some feature misses geometry value
[GEOS-9654] – Layer preview layer count and paging off base when secured layers are not visible
[GEOS-9655] – WMTS layer configuration page doesn’t show all the native srs in getCapabilties document
[GEOS-9668] – UniqueProcess call against a JDBC store does not result in a “select distinct” anymore
[GEOS-9678] – SldService numberFormatException if percentages true with customClasses
[GEOS-9680] – WMTS othersSrs always add EPSG:4326 and shows wrong CRS code
[GEOS-9682] – GetFeatureInfo on raster layers ignores rendering transformations

About GeoServer 2.16

Features, presentations and reference material on the 2.16 series:

by iant at August 31, 2020 10:13 AM

August 28, 2020

It took a while for our last blogpost to come to light. At the beginning, it was because we badly needed to disconnect and recover. Then, life stormed in through the breaches of our schedules, with all the unattended tasks and assignments, responsibilities and engagements. And then time just sneaked by. Days turned into weeks, weeks into months, months into the year. We continued to work, at a slower pace, to wrap up everything, sending the last invoices, calculating budgets, extracting statistics, collecting slides and workshop materials for upload on the conference website and tying up other loose ends.

But something happened. Today our generation is facing its biggest challenge yet, a pandemic of dreadful proportions unfolding as a black cloak covering the world as we have come to know it. We are far from even beginning to grasp the consequences, but it is no secret to anyone that our world will emerge changed, hopefully for the better.

In the midst of all the Covid-19 news alerts, recommendations and interdictions, we invite you to pause for a second and join us for one last trip back in time, to FOSS4G 2019 Bucharest, Romania. Here is what happened last summer.

But until we warmly welcomed you in the wonderful National Theatre Bucharest on the 28th of August 2019, a lot had already happened. Events were already kicking off the weekend before the conference, as the 23rd – 25th of August 2019 was reserved for the QGIS contributors meeting, held in the University of Bucharest.

Starting with the 26th of August, the geospatial community was already prepared to take Bucharest by storm. The FOSS4G 2019 workshops sessions were beginning. The Workshop Committee had a challenging task in selecting just 42 workshops out of the almost 80 received and the resulting schedule was, as expected, wonderful. From cartographic tips and tricks, to mobile geospatial data collection, from Earth Observation data processing and visualizations to plain old geospatial development, we had it all.

And then… the conference started!

We cannot put into words the feelings we experienced as more and more participants were finally crowding into the plenary of the National Theatre of Bucharest. All that work, all those milestones and challenges to overcome, all those meetings and discussions, all of it had finally matured into the FOSS4G 2019 Bucharest.

After an exciting opening plenary spiced up with 3 awesome keynotes from María Arias de Reyna – OSGeo, Kyoung-Soo Eom – United Nations and Steven Ramage – Group on Earth Observations, the FOSS4G 2019 Bucharest conference accelerated, full speed ahead.

At 11 o’clock, 11 parallel tracks steamed away in the conference halls of the Intercontinental Hotel – our 5 stars conference venue.

Needless to say, that after that first momentum, for us, things just went on fast forward. Yet, I believe that we experienced during the FOSS4G 2019 Bucharest week more than others do in a year. Running from one place to another, answering tens of calls, making on-spot decisions, happily using our professional walkie talkie stations and, basically, doing everything in our power so that FOSS4G 2019 unfolds as smoothly as possible for every participant.

The first day of conference continued with the traditional birds of-a-feather flocking together for discussions on: OSGeo charter membership, Open Science and New Technologies forum at IPSRS 2020 Congress, GeoForAll, Mapserver, Catalog, GRASS GIS new website, OpenMapTiles, GeoServer and GeoServer Demos and, of course, a thorough informing BoF for all Travel Grant Program.

In another part of the FOSS4G 2019 venue, another important side event was taking place. In an orderly and fashionable manner, 63 participants were initiating the B2B meetings arranged in the elegant Modigliani Restaurant at the ground floor of the Intercontinental Hotel. As expected, we did not keep track of any concrete results, yet the evolution of the open source geospatial ecosystem of the last decade stands proof of the robust business aspect of it.

The first day of FOSS4G 2019 ended with the icebreaker. And what an icebreaker that was! The setting: Bragadiru Palace. An imposing eclectic building erected following the plans of the Austrian architect Anton Shucker in 1894. It’s main scope was to be a recreational center for the brewery of one the most respected and rich business Romanians at the end of the XIX century. Yes, you read that correctly, it was intended as a recreation center for a brewery. A century later, we can truly admit it wonderfully fulfilled its purpose.

Day 2 started in force with the long-awaited FOSS4G morning run around the famous House of Parliament! Or it should have… Out of the 67 registered runners, less than 20 carried the torch of a #healthylife for the FOSS4G 2019.

We can only express our admiration and a hint of envy for the power of their will.

The second day of the FOSS4G 2019 Bucharest started vigorously with 4 keynotes from… Oh, wait. No. The second day of the FOSS4G 2019 Bucharest started vigorously with 3 keynotes. (Yes, the icebreaker was one to remember, but we won’t give any more details!). Julia Wagemann from ECMWF, Aaron Williams from OmniSci and Jody Garnett from GeoCat snapped everyone back into the conference mood. And, just like that at 11 o’clock sharp, 11 parallel tracks were underway.

After a full day of talks, the closing came in the shape of the productive and relaxed Birds-of-a-feather: OSGeo members’ talk, Open Source Cartography and Mapping, Women in Geospatial – What skills will matter in FOSS4G?, Mapillary Q&A Session, FOSS4G-Europe 2020, Google Code-in, Deep Learning for Earth Observation, GeoTIFF (.js). Yet, of course, we are still far away from the end of the day for the FOSS4G 2019 participants…

The FOSS4G 2019 gala dinner was held in the People’s House also known as the Palace of the Parliament. The heaviest building in the world, third by size, with heating and electricity requirements as a medium-sized city, it was ordered by the Romanian dictator, Nicolae Ceaușescu and built in just 13 years. Truth be told, this would have not been our choice if not for public demand. But yes, the building is a symbol of a long-gone Romania, just like the Berlin wall is for Germany, and we can easily understand the fascination it holds.

Ever wondered what the coordinates on your FOSS4G 2019 T-shirt point to? They point to the KM 0 of Democracy, a place of great value for us, Romanians, because here, in the University square, people gave their lives for freedom in the 1989 Revolution. Because of their sacrifice, our generation is building a new Romania. The one you got to see, and enjoy we hope, at FOSS4G 2019 in Bucharest. KM 0 of Democracy was right in front of the National Theater of Bucharest – our main impressive venue. Coincidence? I would say not.

The gala dinner was.. memorable, to say the least!

During preparations for the FOSS4G 2019, we were keen in keeping prices as low as possible for a high quality event – a 5 starts venue, delicious food, plentiful coffee breaks, 11 fully equipped conference rooms – so succeeding in including the gala dinner in the price of the conference ticket was a huge hit for us. The global FOSS4G has been the hotspot for the open source geospatial people for more than a decade now. Of course, listening to them talk about their research and outcomes and having the ability to interact on the spot are priceless, yet if there is one thing we have learned over the years is that continuing that discussion in an informal environment is what makes this community healthy and powerful. And the Gala Dinner at FOSS4G 2019 Bucharest is just another proof in that exact direction.


Credit @adamsteer


Credit @AnaLeticiaGIS


Credit @ticheler

And the last day of FOSS4G 2019 Bucharest is here. Yes, it is a warm Friday, the 30th of August 2019. The parallel sessions started at the fierce 9:00 o’clock and strongly continued up to 16:00 pm when the Closing Plenary took over and awards time had come! We had 3 award categories, all of which proved once again, although there is no need anymore, how diverse, powerful and productive our community is.

1. FOSS4G Earth Observation Data Challenge. This competition was initiated given the overarching theme of our event – DATA and by extension – Earth Observation data. We challenged startups, developers, students and researchers to come up with useful, valuable or interesting open source applications using large volumes of EO data (and their evolution in time) and state-of-the art technologies (AI/ML, HMC, STAC, data cube, COG), together with other sources of open data (e.g. OpenStreetMap, Copernicus Services – Land, Atmosphere, Climate). We also gave the participants the possibility of working with mentors that guided their work to evolve into a mature idea and a demo.

2. Sol Katz award. There is no need for any introduction to the Sol Katz award, the most prestigious award within the FOSS4G community – a symbol, a token of the highest appreciation to those that brought outstanding contributions to the geospatial open source domain and that have relentlessly proven to be leaders within the community, constantly driving and supporting its advancement. The 2019 Sol Katz award winner is such a person. Do you use… GDAL?

We had some fabulous closing keynotes to say our official goodby: Francesco Barbato from the European Commission talking about the most ambitions human-made program to monitor our home planet – Copernicus, then Matthew Hanson from Element64 sharing his journey through open source for geospatial and Iván Sánchez Ortega, who gave us a stirring lesson on.. the semantics of love and free! Not to worry, Ivan’s talk fitted perfectly as a keynote for a global FOSS4G! But this was not all, we had one more ace down our sleeve! Every event organizer will tell you with the strongest confidence that her/his biggest dream is a clockwork unfolding event. All must be known and prepared in advance so no random incident can downgrade the participants’ experience. However, an open mind with just a little bit of a spur-of-the-moment attitude can go a long way. As it did for FOSS4G 2019! We were lucky enough to have the wordsmith of the famous quote “You are awesome, your software is awesome, (but) your software is useless, …without data” attending the conference, but even more delighted we were when he accepted our spur-of-the-moment invitation to give a short keynote on Friday. And yes, it was awesome! Curious who he was and what he talked about? Take a look!

We are now reaching the very last oficial moments of FOSS4G 2019 Bucharest. 2 years of hard work, constant planning and calculating, running after sponsors and negotiating with every supplier time and time again, answering hundreds of emails – ticket questions, program questions, hotel questions, TGP questions, poster session questions, T-shirts questions, visa questions, workshop questions, weather questions (?!), code sprint questions, conference rooms questions, video questions, booth questions, EO data challenge questions, gala dinner questions, BoFs questions and so many more – all boiled down to these fabulous days that rushed by so fast! The conference chair is walking up the stage, he is exhausted beyond repair but he’s happy. The FOSS4G Bucharest participants are smiling and he survived! We all did, together! He starts his final speech, his last slides for FOSS4G 2019, so many people to thank, many memories are cluttering his mind. Here we go… THANK YOU!

We don’t know if it was obvious, but this was a truly emotional moment for all of us. We were on the other side of time. It was all done. And well! We have come through, we kept our word and we gave our 101% for our community, our colleagues, our friends. You trusted us enough to come to our country, to our city, stroll the streets we walk every day, drink in the bars we meet and where we planned this very conference. A lot has happened that will remain forever with us, tense moments, funny stories, peculiar situations. Should we also write about that Tuesday night before the opening plenary? That time when a group of organizers together with geospatial friends waited in the Intercontinental hotel, with the C3Voc team for their gear to arrive from Germany until 4 am?

Our FOSS4G 2019 final blog post is a heartfelt THANK YOU to all, volunteers, sponsors, supporters, partners, participants, speakers, workshop instructors and of course, our dear PCO, Andreea. We are a quirky bunch of people, a little bit nerdy and truth be told, not always the most easy to communicate with, especially in times of great pressure. Andreea made the effort of getting to know us, coming to our geo-spatial.org seminars around the country to see us “in our natural environment”. She did an outstanding PCO job and that was possible only because she cared.

All of you have greatly contributed to the success of this event and you have honored us with your unreserved trust that we, geo-spatial.org – the Romanian OSGeo Local Chapter – can organize the 14th edition of the international Free and Open Source for Geospatial in Bucharest.


Credit @ticheler

And because we all love numbers, here are some. Enjoy!

  • ● Bucharest Local Organizing Committee + Conference Committees: 60;
  • ● Keynotes: 9 + a special message;
  • ● Presentations: 286;
  • ● Hours of recordings: 100+;
  • ● Workshops: 42;
  • ● Labs: 5;
  • ● BoFs: 17;
  • ● Code sprint participants: 34;
  • ● QGIS contributors meeting participants: 33;
  • ● 2 B2B participants with 63 participants;
  • ● FOSS4G 2019 participants: 1020+;
  • ● Countries represented: 80;
  • ● FOSS4G 2019 ambassadors: 23;
  • ● Travel Grant supported participants: 28;
  • ● EO Open Data Challenge prizes: 10;
  • ● EO Open Data Challenge total EUR prizes: 20000;
  • ● Sponsors: 37 (5 categories);
  • ● Partners:
    • ○ Strategic: 1;
    • ○ Conference: 20;
    • ○ FOSS4G EO Data Challenge: 35;
    • ○ Academic: 6;
    • ○ Media: 21;
    • ○ Knowledge: 2;
    • ○ Mobility: 1;
    • ○ Safety: 1;
    • ○ Taste: 9;
    • ○ Community: 4;
  • ● Bucharest guided tours: 3;
  • ● Guides: 3 (thank you Olimpia, Georgiana and Andi!);
  • ● Participants enjoying the Bucharest guided tours: 270 (day 1 – 108, day 2 – 141, day 3 – 21);
  • ● Social events: survived 2 x 7 hours long social events with an open bar! Not to neglect all the other evenings of informal networking at the FOSS4G pubs;
  • ● FOSS4G 2019 pubs: 6;
  • ● Volunteers:
    • ○ Rooms: 11;
    • ○ Conference: 20;
    • ○ Video: 44 + 6 C3Voc wonderful team members;
  • ● Social media stats:
    • ○ Twitter: 256 tweets (from the official account);
    • ○ Blogpost entries: 22.

Today, the world is paying attention to the terrible challenge we have to face. In face of adversity, it is important to remember what unites us, what makes us a community and what helps us find the resources to remain kind and gentle, responsive and helpful, reasonable and hopeful.

by Vasile Crăciunescu at August 28, 2020 02:56 PM

August 27, 2020

August 26, 2020

QWAT est une application open source de gestion des réseaux d’eau potable émanant des collectivités de Pully, le SIGE à Vevey, Morges et Lausanne.
QGEP est son homologue dédiée à la gestion des eaux usées et pluviales, initiée par le groupe utilisateur QGIS Suisse.

L’échange de données entre institutions est une pierre angulaire des politiques de l’eau. Ces échanges se basent sur des formats d’échanges standardisés. Ainsi les Cantons de Fribourg (format aquaFRI) ou de Vaud (format SIRE) conditionnent certaines subventions publiques à la transmission des données selon des formats pré-définis et permettent à ces échelons administratifs d’avoir une vision globale des réseaux humides.

Dans le cadre d’une expérimentation des outils QWAT (eau potable) et QGEP (eaux usées), Charentes Eaux a souhaité mettre en œuvre des extensions dédiées au standard d’échange de données sur les réseaux d’eau Français, le Géostandard Réseaux d’adduction d’eau potable et d’assainissement (RAEPA) défini par la Commission de validation des données pour l’information spatialisée (COVADIS).

Oslandia a été mandaté pour mettre en œuvre des instances de QWAT et QGEP, réaliser les extensions RAEPA pour chacun de ces outils, et aider Charente Eaux à charger les données des collectivités membres de ce syndicat mixte.

https://charente-eaux.fr/le-syndicat/qui-sommes-nous/

Le travail a été publié pour QWAT sous forme d’une extension standardisée dans le dépôt l’organisation QWAT https://github.com/qwat/extension_fr_raepa/

Pour QGEP, il n’existe pas encore de fonctionnalité pour gérer d’extension, le dépôt https://gitlab.com/Oslandia/qgep_extension_raepa/ contient donc les définitions de données et de vues à rajouter manuellement au modèle de données.

La compatibilité des modèles de données a été évaluée et le choix a été fait de ne faire que des vues dédiées à l’export de données. Il est techniquement possible de faire des vues éditables pour permettre le chargement de données via ces vues depuis des fichiers suivant le gabarit de données RAEPA. Le niveau de simplification et d’agrégation des listes de valeurs rend ce travail peu générique dans l’état actuel du géostandard (v1.1), il est donc plus pertinent à ce stade de réaliser des scripts de chargement sans passer par ce pivot dans le cas de Charente-Eaux

by Régis Haubourg at August 26, 2020 10:07 AM

August 25, 2020

Imagens de satélites são utilizadas por vários profissionais. Engenheiros, geógrafos, oceanógrafos e muitos outros fazem uso delas para planejar atividades de campo, quantificar o impacto em matas nativas e avaliar mudanças no solo.

Softwares como QGIS e ArcGIS apresentam recursos para mostrar imagens de satélite online, seja por meio do QuickMapService ou pelo Base Map, respectivamente.

Porém, em algumas situações, esses recursos podem não estar disponíveis. Um bom exemplo disso é o site do SIG SDS de Santa Catarina, o qual permite visualizar os dados por meio de WMS, mas que eventualmente, fica fora do ar, sendo necessário baixar as imagens manualmente.

Portanto, ter as imagens no seu computador pode evitar algumas dores de cabeça na execução de estudos ambientais.

Há vários sites que possibilitam baixar imagens de satélites, tais como Earth Explorer e Copernicus Open Access Hub. Mas para dar continuidade nas postagens sobre o Google Earth Explorer com Python, vamos mostrar como baixar imagens de satélite para que você possa analisar as imagens que você esta trabalhando e seus resultados e permitir que você crie mapas com elas no QGIS (ou outro software de geoprocessamento de preferência).

Imagem obtida no GEE (visualização prévia com modificações).Imagem obtida no GEE (visualização prévia com modificações).

Autenticação no Google Earth Engine (GEE)

Como comentamos na postagem anterior sobre GEE, é necessário realizar a sua autenticação e inicializar a biblioteca ee. Você pode realizar esse procedimento a partir do código abaixo, que irá redirecionar você para uma nova página, solicitando a sua conta Google (gmail) e você receberá um código para colar no campo aberto.

import ee
ee.Authenticate()
ee.Initialize()

Caso você já tenha executado o código uma vez, você pode deixar a função ee.Authenticate() como comentário.

Recortando e Selecionando Bandas Específicas

Agora que já autenticamos nosso acesso. Vamos criar uma variável com os limites da nossa área de estudo e outra para guardar a nossa imagem de satélite. Neste tutorial, vamos salvar uma imagem LANDSAT 8, porém, você pode consultar as imagens disponíveis no Google Earth Engine visitando a página dos conjuntos de imagens disponíveis.

Além disso, usaremos o LANDSAT Acquisition Tool para identificar os números da rota e trajeto do satélite na nossa área de estudo, e o Earth Explorer para saber o dia que ele passou (embora você possa usar o segundo para os dois).

Depois disso tudo, iremos selecionar as bandas 2 (Azul), 3 (Verde) e 4 (Vermelho) e em seguida, recortar a imagem usando a função clip().

area_estudo = ee.Geometry.Rectangle([-49.7, -28.3, -49.3, -28.7])
img_landsat = ee.Image('LANDSAT/LC08/C01/T1/LC08_220080_20200420')\
    .select(['B2','B3','B4']).clip(area_estudo)

Agora que salvamos nossa área de estudo, vamos ver alguns comandos para visualizá-la.

Na nossa primeira postagem, mostramos uma função para retornar as datas disponíveis em um período de tempo considerando como variável uma coleção de imagens. Você pode conferir ela clicando aqui.

Visualização prévia com getThumbURL()

Antes de olharmos a função getThumbURL(), que nos fornece um endereço online para visualizarmos nossa imagem, vamos olhar um pouco sobre redutores (ee.Reducer).

As funções de redução servem para calcular estatísticas de uma região, tais como média (mean), mediana (median), desvio padrão (stdDev) e valores mínimos e máximos (minMax). No nosso caso, vamos usar ee.Reducer.minMax() para conhecermos os valores extremos da nossa imagem e configurar a visualização dela.

Após esse procedimento, usamos a função getThumbURL() para obter o endereço da nossa imagem. Lembrando que essa função é utilizada para ter a imagem para ser usada em apresentações (não sendo ainda a imagem para ser usada no SIG).

print(img_landsat.reduceRegion(reducer = ee.Reducer.minMax()).getInfo())

print(img_landsat.getThumbURL({'min':5000, 'max': 23000}))

Os resultados irão aparecer no terminal python. Basta então copiar e colar o link no navegador para ver a imagem. Caso você esteja obtendo uma imagem totalmente branca, verifique se os valores mínimos e máximos na função getThumbURL abrangem todos os valores mostrados pela função de redução.

Além disso, caso sua área seja grande demais, poderá haver problemas, visto que o Earth Engine, para priorizar desempenho, não executa a função Reducer com muitos pixels.

Exportando para o Google Drive

Uma forma de obter as suas imagens de interesse é salvá-las diretamente no seu Google Drive. Para realizar esse procedimento, vamos usar a função ee.batch.Export.image.toDrive().

Essa função precisa de alguns dados de entrada para fazer seu trabalho. Precisamos indicar qual imagem queremos salvar, o nome do arquivo quando salvo, a pasta, a resolução (neste caso, no GEE, chamada de scale), e a região que gostaríamos de salvar.

O código abaixo mostra como realizar esse procedimento.

task = ee.batch.Export.image.toDrive(**{
    'image': img_landsat,
    'description': 'img_B2E',
    'folder': 'EE_Output',
    'scale': 30,
    'region': area_estudo.getInfo()['coordinates']
    })
task.start()

import time
while task.active():
    print('Salvando a imagem (id: {}).'.format(task.id))
    time.sleep(5)

Note que salvamos a nossa função dentro da variável task. Para que o GEE entenda que a exportação deve iniciar, temos que usar start(). Em seguida, usamos a função sleep() da biblioteca time para nos dar o andamento do processo a cada 5 segundos.

Caso tudo ocorra corretamente, você terá no seu Google Drive, uma pasta chamada EE_Output com o tif da sua imagem.

Obtendo endereço da imagem para download

Outra forma ainda de conseguirmos baixar uma imagem no GEE é por meio da função getDownloadURL().

download_url = img_landsat.getDownloadURL({
    'image': img_landsat,
    'region': area_estudo,
    'name': 'img_B2E_down',
})

print(download_url)

Ao rodar esse código, será salvo uma variável do tipo string (texto), contendo a URL para download. A diferença desse método, para o anterior, é que você irá baixar um arquivo compactado com cada uma das bandas em arquivos separados.

Agora você aprendeu alguns métodos para realizar o download das suas imagens, possibilitando avaliar elas e apresentar seus resultados em artigos e projetos.

Você pode consultar o código completo no meu GitHub. Estarei disponibilizando os códigos que apresentamos aqui no blog e, alguns poucos, irei alimentar com alguns códigos que uso em alguns estudos ambientais.

Caso você tenha alguma dúvida, fique a vontade para usar os comentários que estaremos respondendo assim que possível.

The post Como baixar imagens de satélite com Google Earth Engine usando Python? first appeared on Blog 2 Engenheiros.

by Fernando BS at August 25, 2020 06:16 AM

August 24, 2020

Prezados leitores,

Na última sexta-feira, dia 21 de agosto, participei do evento ConFLOSS 2020 (Conferência de Free/Libre e Open Source Software) palestrando sobre o uso de software livre para interoperabilidade de dados espaciais.

Assim que o vídeo for disponibilizado no YouTube eu vou adicionar nesse post, por enquanto você pode conferir os slides da apresentação que já estão disponíveis no Speaker Deck:



by Fernando Quadro at August 24, 2020 11:00 AM

We are delighted to announce that in collaboration with North Road and Hobu, we are running a crowdfunding campaign to implement native support for point cloud data in QGIS.

point cloud support in QGIS

With the proposed changes, you will be able to load, style and visualise your point cloud data in QGIS in 2D and 3D map views.

The work will be carried out by the trusted and highly skilled developers across PDAL and QGIS community (Lutra Consulting, North Road and Hobu) who have been at the forefront of some of the exciting features in Open Source projects.

If you or your organisation are point cloud data users, this is your chance to bring native support for your data in QGIS. With this work, you will be able to overlay your point cloud data to your other data (vector/raster). The addition of native support for point cloud data in QGIS will pave the way to support analytical tools for point cloud data in future.

The target amount is 49,000 € and the campaign will be active until 15 October 2020.

Please have a look at the dedicated page point cloud data support in QGIS for further details and help us spread the word!

August 24, 2020 06:00 AM

August 23, 2020

Rendering large sets of trajectory lines gets messy fast. Different aggregation approaches have been developed to address this issue. However, most approaches, such as mobility graphs or generalized flow maps, cannot handle large input datasets. Building on M³ prototypes, the following approach can be used in distributed computing environments to extracts flows from large datasets. 

This is part 3 of “Exploring massive movement datasets”.

This flow extraction is based on a two-step process, conceptually similar to Andrienko flow maps: first, we extract M³ prototypes from the movement data. In the second step, we determine flows between these prototypes, including information about: distribution of travel speeds and number of observed transitions. The resulting flows can be visualized, for example, to explore the popularity of different paths of movement:

After the prototypes have been computed, the flow algorithm computes transitions between pairs of prototypes. An object moving from prototype A to prototype B triggers an update of the corresponding flow. To allow for distributed processing, each node in the distributed computing environment needs a copy of the previously computed prototypes. Additionally, the raw movement data records need to be converted into trajectories. Afterwards, each trajectory is processed independently, going through its records in chronological order:

  1. Find the best matching prototype for the current record
  2. Ensure that the distance to the match is below the distance threshold and that the matched prototype is different from the previous prototype
  3. Get or create the flow between the two prototypes
  4. Ensure that the prototype and flow directions are a good match for the current record’s direction
  5. Update the flow properties: travel speed and number of transitions, as well as the previous prototype reference

This approach scales to large datasets since only the prototypes, the (intermediate) flow results, and the trajectory currently being worked on have to be kept in memory for each iteration. However, this algorithm does not allow for continuous updates. Flows would have to be recomputed (at least locally) whenever prototypes changed. Therefore, the algorithm does not support exploration of continuous data streams. However, it can be used to explore large historical datasets:

Flow example: passenger vessel speed patterns showing mean flow speeds (line color: darker colors equal higher speeds) and speed variation (line width)

If you want to dive deeper, here’s the full paper:

[1] Graser, A., Widhalm, P., & Dragaschnig, M. (2020). Extracting Patterns from Large Movement Datasets. GI_Forum – Journal of Geographic Information Science, 1-2020, 153-163. doi:10.1553/giscience2020_01_s153.


This post is part of a series. Read more about movement data in GIS.

by underdark at August 23, 2020 05:34 PM

August 21, 2020

Dear Community,

2020, as we all know, has been an unusual year. In addition to all the other issues we have all faced, we also had to cancel our beloved hackfests. Since we first started holding bi-annual hackfests in 2009, this will be the first year without an in-person event where our friendly community can meet. 

First hackfest in Hannover 2009 (https://www.umwelt.uni-hannover.de/qgis.html)

That can’t be! We are a modern and thriving community based on exchange, discussion and collaboration and should foster this even when physical meetings are not possible.

I’m super excited to announce that after some very motivating discussions on the HackFest telegram channel and in the PSC, starting from next week on every last Friday of each month we will hold an informal online virtual meeting to hack around, document, discuss and in general meet the awesome QGIS community. 

First QGIS User Conference in Nødebo 2015 (https://qgis2015.wordpress.com)

There will normally be no formal agenda, no fixed schedule nor moderators, simply join the QHackFriday (pronounced KwakFriday) jitsi room and say hi! 

I added a page to the wiki, so if you have topics that you like to discuss/present you can put them there and others might join you. 

Stay safe and see you next Friday!

by mbernasocchi at August 21, 2020 06:14 PM

August 20, 2020

Hello everybody!
This post is about a minor update for the Semi-Automatic Classification Plugin (SCP) for QGIS, version 6.4.7.
This fixes a QGIS crash on installing or uninstalling the plugin on Windows OS, which is related to this QGIS issue https://github.com/qgis/QGIS/issues/38372.

Unfortunately the SCP dependency SciPy is broken in recent versions of QGIS, therefore the functions requiring SciPy won't work.
In order to use all the tools of SCP, until QGIS developers fix the SciPy issue, you should install the QGIS version 3.10.8 or previous versions.

In case QGIS crashes during plugin installation, you can manually remove the SCP directory in the QGIS plugin folder (usually C:\Users\USERNAME\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins) and then install the plugin.

For any comment or question, join the Facebook group about the Semi-Automatic Classification Plugin.

by Luca Congedo (noreply@blogger.com) at August 20, 2020 12:16 PM

Today we released SMASH 1.4.0 to the Apple and Google stores.

This release brings some bugfixes and two main features.

1) SLD support

When it comes to styling data many have expressed their hate towards the OGC standard SLD. Coming from the uDig/Geotools world, where SLD has always been used, I find it quite nice to use. Well,  I use it for very simple styling, so that might be the reason behind it. Well, it seemed to be the perfect format. There are several editors and GIS that support SLD, so people will be able to create their styles for the survey. And now SMASH is one of them, even if it right now supports a subset of SLD features.

Lets' have a look. Assume to be in the region of the Resia Lake in northern Italy:

Now let's play around with some geopackage data: lake polygons, river lines and geoname points.

Sliding the polygon layer to the right allows to enter the style properties:

It is rather intuitive what needs to be done to have a lake styled. But remember to save using the floating action bottom at the bottom. This will write the style to the database table.

Et voila'. The same goes for lines:

and points. Points are the only layer types that allow labeling at the moment.

These have been very very simple styles. For those that talk SLD, these examples only had a FeatureTypeStyle and one Rule. 

SMASH supports one type of theming: by unique values. In this case a FeatureTypeStyle is populated with several rules that obey to a filter that supports matching of unique values from the attributes table.

The properties page has buttons to change rules and modify them. The following is an example that features 2 FeatureTypeStyles, one with just a Rule containing a textsymbolizer:

 
and a second one with all the Rules with filter:
 

If only one FeatureTypeStyle or Rule are present, the header titles can vary:

The result then looks like:

We decided to give also GPX files these kind of powers. If you change the style properties of a GPX layer, an SLD sidecar file is created and ensures style persistence. 

Style can be defined for lines and points. If waypoints have the name tag, it can be used for labeling.


 2) GPS log enhancements

The log stats have been extended and now contain time, length, up and down delta (mind this is GPS elevation, so it is usually bad), number of points contained in the log.

In the previous version of SMASH a Kalman filter had been added to filter GPS logs and both log types are kept in the database. It is now possible to decide to use the filtered logs in certain sections of SMASH as for example in the logs list. Just enter the GPS settings and enable the option:

If you head back to the logs list, the stats length value might be changed:

In this case the difference is around 8Km. This is due to the fact that in tunnels the GPS often goes crazy and jumps around, generating additional distance to the log. The filtered version is more realistic. But you can choose based on your usecase.


From the log list a new tool is available when sliding to the right: the Profile View

The profile view allows to analyze the profile and navigate it:

Thanks for the OwnWeb guys for this nice plugin.


Well, that is it for SMASH 1.4.0. Enjoy!





by moovida (noreply@blogger.com) at August 20, 2020 06:54 AM

August 19, 2020