Planet Georezo » Planet OSGeo

Un Planet est un site Web dynamique qui agrÃ¨ge le plus souvent sur une seule page, le contenu de notes, d'articles ou de billets publiÃ©s sur des blogs ou sites Web afin d'accentuer leur visibilitÃ© et de faire ressortir des contenus pertinents aux multiples formats (texte, audio, vidÃ©o, Podcast). C'est un agrÃ©gateur de flux RSS. Il s'apparente Ã un portail web.
Vous pouvez lire le billet sur le blog La Minute pour plus d'informations sur les RSS !

Canaux

7244 éléments (0 non lus) dans 116 canaux

Dans la presse

Du cÃ´tÃ© des Ã©diteurs

Toile gÃ©omatique francophone

GÃ©omatique anglophone

Blogs GeoRezo.net

Autres planets

Planet OSGeo

Abonnez vous à cette page (RSS) !

Planet OSGeo

Sauter à la page: 1 2 3 ... 13

18 March 2019
11:30
Fernando Quadro: Introdução ao Leaflet – Basemaps e Overlays
sur Planet OSGeo
Hoje vamos adicionar alguns mapas base e alguns controles ao nosso mapa. Até agora temos usado o OpenStreetMap como o nosso basemap. Iremos adicionar 2 novas camadas base e também adicionaremos uma atribuição ao mapa para que possamos dar crédito, além de uma barra de escala.

1. Adicionando Basemaps

Os mapas base e seus URLs que queremos adicionar são:

Mapa Nacional topo: [https:]

Open Topop Map: [https:]

Primeiro criamos as duas camadas de blocos:
```
var basetopo = L.tileLayer('https://basemap.nationalmap.gov/arcgis/rest/services/USGSTopo/MapServer/WMTS/tile/1.0.0/USGSTopo/default/default028mm/{z}/{y}/{x}.png', {});
var baserelief = L.tileLayer('https://tile.opentopomap.org/{z}/{x}/{y}.png', {});
```
Poderíamos adicioná-los ao mapa como estão, mas queremos controlar a visibilidade de cada um, permitindo que o usuário escolha qual deles é exibido. Para fazer isso, crie um objeto para manter a descrição e a camada:
```
var baselayers = {
    'Shaded Relief': baserelief,
    'National Map topo': basetopo
};
```
2. Adicionando Controle de Camada

O controle de camada nos permite escolher o que é exibido no mapa. Para criá-lo, passamos o mapa base e as camadas de sobreposição. Isso exige que criemos um objeto para manter a(s) sobreposições e, em seguida, podemos criar o controle:
```
var overlays = {
    'The Trail': thetrail
};
L.control.layers(baselayers, overlays).addTo(map);
```
Adicionamos apenas um dos mapas base ao mapa antes de criar o controle. O mapa agora tem um controle de camada com um mapa base ativo e outro disponível no controle:

Nós vamos adicionar sobreposições adicionais em posts futuros.

3. O Scalebar

Adicionar uma barra de escala é fácil:
```
  var scale = L.control.scale()
  scale.addTo(map)
```
4. Adicionando Atribuição

Para dar crédito às fontes de dados, adicione a atribuição:
```
map.attributionControl.addAttribution('National Map Topo');
map.attributionControl.addAttribution('OpenTopoMap');
```
Isso acrescenta atribuição a qualquer existente, que no início é apenas “Leaflet”.

Isso completa nosso mapa para hoje. Podemos alternar entre camadas base usando o controle e ter a atribuição adequada e uma barra de escala.

5. Código Javascript
```
var map = L.map(document.getElementById('mapDIV'), {
    center: [62.7, -144.0],
    zoom: 6
});

// Base maps
var basetopo = L.tileLayer('https://basemap.nationalmap.gov/arcgis/rest/services/USGSTopo/MapServer/WMTS/tile/1.0.0/USGSTopo/default/default028mm/{z}/{y}/{x}.png', {});
var baserelief = L.tileLayer('https://tile.opentopomap.org/{z}/{x}/{y}.png', {});

basetopo.addTo(map);

// The trail
var thetrail = L.geoJSON(trail, {
    color: '#800000',
    weight: 3,
    dashArray: '12 8 12',
});

thetrail.bindTooltip('The Valdez-Eagle Trail')
thetrail.addTo(map);

var baselayers = {
    'Shaded Relief': baserelief,
    'National Map topo': basetopo
};
var overlays = {
    'The Trail': thetrail
};
L.control.layers(baselayers, overlays).addTo(map);

// Add scalebar

var scale = L.control.scale()
scale.addTo(map)

// Add attribution
map.attributionControl.addAttribution('National Map Topo');
map.attributionControl.addAttribution('OpenTopoMap');
```
8:00
CARTO Blog: Optimize Data Workflows with Insider Tools
sur Planet OSGeo

CARTO’s Support and Solutions teams often create CARTO.js and CARTO VL examples for our clients, so we’re in the same situation as many of you: we need to build apps effici...
15 March 2019
12:48
gvSIG Team: 4th gvSIG festival: Free registration is now open
sur Planet OSGeo

Free registration period for the 4th gvSIG Festival is now open. The gvSIG Festival is an online conference about gvSIG that will be held in March 27th and 28th.

This year we made a special appeal to the group of women who are part of the gvSIG Community, and it has been reflected at the program, where almost all the presentations will be given by women. You can check the full program of the gvSIG Festival on the event website, where there will be presentations in Spanish, English and Portuguese.

The webinar platform allows to connect to the webinars from any operating system, and in case you canâ€™t see some of the webinars, you will be able to watch them at the gvSIG Youtube channel later like in the previous year.

Registration for each webinar can be done from the program page of the gvSIG Festival website.

Donâ€™t miss it!
12:34
gvSIG Team: 4Âº gvSIG Festival: Abiertas las inscripciones gratuitas
sur Planet OSGeo

Ya estÃ¡n abiertas las inscripciones gratuitas para el 4Âº gvSIG Festival, lasÂ jornadas virtuales de gvSIG que se celebrarÃ¡n los dÃas 27 y 28 de marzo.

Este aÃ±o hemos hecho un llamamiento especial al colectivo de mujeres que forman parte de la Comunidad gvSIG, y cuenta de ello es que prÃ¡cticamente todas las ponencias van a ser impartidas por mujeres. PodÃ©is consultar el programa completo del gvSIG Festival en la pÃ¡gina web del evento, en el que habrÃ¡ ponencias en InglÃ©s, EspaÃ±ol y PortuguÃ©s.

La plataforma de webinar permite conectarse desde cualquier sistema operativo, y en caso de no poder seguirlos en directo podrÃ©is verlos a posteriori, ya que se publicarÃ¡n en el canal de Youtube del proyecto al igual que en aÃ±os anteriores.

La inscripciÃ³n a cada uno de los webinars puede realizarse desde el propio programa en la web del evento.
14 March 2019
17:15
Jackie Ng: Announcing: vscode-map-preview 0.4.6
sur Planet OSGeo
A kind user alerted me to the fact that my Map Preview extension for Visual Studio CodeÂ was using APIs that have long been deprecated and could be removed any moment in a future release, breaking this extension in the process.

Although I haven't touched this code in a while (not intentional btw. One person can only tend to so many different open source projects), getting back into VSCode extension development was a very comfortable affair:
- Update a few packages here and there.Â
- Update TypeScript.Â
- Read up on the new Webview API, which is what our extension should be using now.
- Replace usages of vscode.previewHtml with the new Webview API.
- Verify the extension still works
- Get re-acquainted with how to publish VSCode extensions
And ... voila! A new version of the Map Preview extension is available for your VSCode installation to auto-update to.

In terms of changes, beyond some updates to OpenLayers and a small bug fix or two, there isn't really much to write home about, it should still be the same extension as before. This release was driven primarily by the need to move away from their oldÂ vscode.previewHtmlÂ API over to their new Webview API.

Once things have settled down on my other projects, I'd like to give this project some more attention. There's still some cool ideas I want to explore with this extension. I don't know if I still want to go down the Cesium route as previously hinted as there have been many more data viz players that have arrived on the scene since then and I also sort of do not want to detract from the original goal and purpose of this extension: An easy way to preview on a MapÂ textual contentÂ that you are already editing or viewing in VSCode.
17:02
gvSIG Team: Loading GPX files on gvSIG Desktop and gvSIG Mobile
sur Planet OSGeo

Sometimes we need to visualize GPX files obtained with GPS devices. These files can be used to describe waypoints, tracks and routes.

Both with gvSIG Desktop (on Windows, Linux and Mac) and with gvSIG Mobile (on Android) you can load this type of files, and overlap them with another type of cartography, both raster and vector layers, with local files and layers available through remote services.

In gvSIG Desktop we can load the GPX files from the â€œOGCâ€ tab of the â€œAdd layerâ€ window. Once the file is selected by entering the â€œâ€¦â€ button, we must press â€œOpenâ€, and then the information to be loaded has to be selected (â€œtracksâ€, â€œtrack_pointsâ€ â€¦). The layer will be reprojected to the reference system of the View.

In gvSIG Mobile we can load the GPX files from the â€œImportâ€ menu available at the main menu.

In these videos you can see how it works in a better way:
gvSIG Desktop:
gvSIG Mobile:
17:02
gvSIG Team: Carga de ficheros GPX en gvSIG Desktop y gvSIG Mobile
sur Planet OSGeo

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:
12:50
Marco Bernasocchi: QField RC5 â€“ Last call for testing
sur Planet OSGeo
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
Search functionality
List of improvements since RC3
- New Custom file selector (#476)
- Favorite directories in file selector (#507)
- Recent projects in file selector (#499)
- Ripple effect in file selector (#505)
- Smart unobtrusive â€œrate this appâ€ dialog (#510)
- clear value in date/time if invalid when losing focus (#464)
- fix crash when switching layer (#498)
- Respect DPI in multiline fontsize
- Value Map compatibility with QGIS 2 and lazy loading for performance improvements
- Use external valuemap model
- allow to copy text from clipboard in search bar
- respect keep scale option in locator
- optimize scale when searching points (#472)
- add frame to search results
- Update to Qt 5.12.1 (for android 6+)
You can easily install QField using the Playstore (https://qfield.org/get), find out more on the documentation site (https://qfield.org), watch some demo videos on our channel ( [https:]] ) and report problems to our issues tracking system (https://qfield.org/issues). Please note that the Playstore update can take some hours to roll out and if you had installed a version directly from GitHub, you might have to uninstall it to get the latest playstore update.

QField, like QGIS, is an open source project. Everyone is welcome to contribute making the product even better â€“ whether it is with financial support, enthusiastic programming, translation and documentation work or visionary ideas.

If you want to help us build a better QField or QGIS, or need any services related to the whole QGIS stack donâ€™t hesitate to contact us.
6:30
gvSIG Team: Towards gvSIG 2.5: New geoprocess, Aoristic Clock by grid
sur Planet OSGeo

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.

Â
6:20
gvSIG Team: Camino a gvSIG 2.5: Nuevo geoproceso, Reloj AorÃstico por rejilla
sur Planet OSGeo

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.
13 March 2019
17:19
gvSIG Team: Towards gvSIG 2.5: New geoprocess, Aoristic Clock
sur Planet OSGeo
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.
12 March 2019
15:49
gvSIG Team: Camino a gvSIG 2.5: Nuevo geoproceso, Reloj AorÃstico
sur Planet OSGeo
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.

Â

Â
2:33
Cameron Shorter: Google Season of Docs Announced
sur Planet OSGeo

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?
11 March 2019
1:00
PostGIS Development: PostGIS 2.5.2, 2.4.7, 2.3.9 Released
sur Planet OSGeo
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).
- source download
- NEWS
- PDF docs en de
- html doc download
- html online en de ja
- epub doc download
- Changelog
2.4.7 This release supports PostgreSQL 9.3-10.
- source download
- NEWS
- PDF docs en
- html doc download
- html online en
- epub doc download
- Changelog
2.3.9

This release supports PostgreSQL 9.2-10.
- source download
- NEWS
- PDF docs en
- html doc download
- html online en
- epub doc download
- Changelog
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.
10 March 2019
19:09
QGIS Blog: A CoruÃ±a contributors meeting: another step forward for the QGIS.ORG project!
sur Planet OSGeo

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
09 March 2019
9:13
QGIS Blog: End of life notice: QGIS 2.18 LTR
sur Planet OSGeo
QGIS 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.
07 March 2019
10:26
gvSIG Team: Coordinate capture tool utilities in gvSIG
sur Planet OSGeo
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:
06 March 2019
21:08
FOSS4G 2019 Bucharest: Launch of the Travel Grant Program FOSS4G 2019 Bucharest!
sur Planet OSGeo

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.
19:06
gvSIG Team: Utilidades del nuevo capturador de coordenadas en gvSIG
sur Planet OSGeo
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:
11:00
CARTO Blog: Exporting Maps for Printing in the Digital Maps Era
sur Planet OSGeo

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 ...
05 March 2019
10:41
gvSIG Team: 11as Jornadas Latinoamericanas e do Caribe de gvSIG: â€œGeoteconologias, contribuindo para a soluÃ§Ã£o de problemas do territÃ³rioâ€
sur Planet OSGeo

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.
10:35
GeoSolutions: MapStore Release 2019.01.00: Timeline, Styler and more
sur Planet OSGeo
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[/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[/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[/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[/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[/caption] Â [caption id="" align="aligncenter" width="1143"] 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Â GeoServer,Â Mapstore, GeoNodeÂ and GeoNetworkÂ through our Enterprise Support ServicesÂ and GeoServer Deployment Warranty offerings, feel free to contact us!
The GeoSolutions team,
8:00
GIS for Thought: Every Person in Great Britain Mapped
sur Planet OSGeo

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 Survey,Â Open 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.
04 March 2019
18:57
Martin Davis: Fast Geometry Distance in JTS
sur Planet OSGeo
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(n²) (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(n²) 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 size Target
Data size Time
Indexed Time
Brute-Force Improvement
1 polygon
(19,487 vertices) 244 polygons
(366,951 vertices) 164 ms 136 s x 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 size Target
Data size Time Time
Brute-Force Improvement
1 polygon
(7,316 vertices) 100,000 polygons
(500,000 vertices) 53 ms 10.03 s x 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.
16:21
gvSIG Team: 11as Jornadas de LatinoamÃ©rica y Caribe de gvSIG: â€œGeotecnologÃas, contribuyendo a la soluciÃ³n de problemas del territorioâ€
sur Planet OSGeo

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.
11:00
CARTO Blog: Mapping Segregation - MIT's Atlas of Inequality
sur Planet OSGeo

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...
03 March 2019
21:03
Free and Open Source GIS Ramblings: Stand-alone PyQGIS scripts with OSGeo4W
sur Planet OSGeo
PyQGIS scripts are great to automate spatial processing workflows. Itâ€™s easy to run these scripts inside QGIS but it can be even more convenient to run PyQGIS scripts without even having to launch QGIS. To create a so-called â€œstand-aloneâ€ PyQGIS script, there are a few things that need to be taken care of. The following steps show how to set up PyCharm for stand-alone PyQGIS development on Windows10 with OSGeo4W.

An essential first step is to ensure that all environment variables are set correctly. The most reliable approach is to go to C:\OSGeo4W64\bin (or wherever OSGeo4W is installed on your machine), make a copy of qgis-dev-g7.bat (or any other QGIS version that you have installed) and rename it to pycharm.bat:

Instead of launching QGIS, we want that pycharm.bat launches PyCharm. Therefore, we edit the final line in the .bat file to start pycharm64.exe:

In PyCharm itself, the main task to finish our setup is configuring the project interpreter:

First, we add a new â€œsystem interpreterâ€ for Python 3.7 using the corresponding OSGeo4W Python installation.

To finish the interpreter config, we need to add two additional paths pointing to QGIS\python and QGIS\python\plugins:

Thatâ€™s it! Now we can start developing our stand-alone PyQGIS script.

The following example shows the necessary steps, particularly:
1. Initializing QGIS
2. Initializing Processing
3. Running a Processing algorithm
```
import sys

from qgis.core import QgsApplication, QgsProcessingFeedback
from qgis.analysis import QgsNativeAlgorithms

QgsApplication.setPrefixPath(r'C:\OSGeo4W64\apps\qgis-dev', True)
qgs = QgsApplication([], False)
qgs.initQgis()

# Add the path to processing so we can import it next
sys.path.append(r'C:\OSGeo4W64\apps\qgis-dev\python\plugins')
# Imports usually should be at the top of a script but this unconventional 
# order is necessary here because QGIS has to be initialized first
import processing
from processing.core.Processing import Processing

Processing.initialize()
QgsApplication.processingRegistry().addProvider(QgsNativeAlgorithms())
feedback = QgsProcessingFeedback()

rivers = r'D:\Documents\Geodata\NaturalEarthData\Natural_Earth_quick_start\10m_physical\ne_10m_rivers_lake_centerlines.shp'
output = r'D:\Documents\Geodata\temp\danube3.shp'
expression = "name LIKE '%Danube%'"

danube = processing.run(
    'native:extractbyexpression',
    {'INPUT': rivers, 'EXPRESSION': expression, 'OUTPUT': output},
    feedback=feedback
    )['OUTPUT']

print(danube)
```
18:29
GeoTools Team: GeoTools 21.0 Released
sur Planet OSGeo

The GeoTools is pleased to announce the release of GeoTools 21.0 our first release with both Java 11 and Java 8 compatibility: geotools-21.0-bin.zip geotools-21.0-doc.zip geotools-21.0-userguide.zip geotools-21.0-project.zip maven repository This is a stable release of GeoTools made in conjunction with GeoServer 2.15 and GeoWebCache 1.15. Release highlights: Works with both Java 11 and Java
1:04
Cameron Shorter: Starting build cycle for OSGeoLive 13.0
sur Planet OSGeo

Are you interested in joining our Open Source GIS experience? The build cycle for the next OSGeoLive release 13.0, is going to start. The final version is planned to be ready on 30th July 2019 in time for FOSS4G 2019Â in Bucharest. Have a look at our schedule for the detailed steps.
Till then we have many challenges - from simple to challenging, to help describe and train people in the value of Open Source GIS.
For this release, we hope to help OSGeo Community projects join OSGeoLive, and work out how we can keep within our size constraints.
We'd love to build a cloud version of OSGeoLive for this release. It would make OSGeoLive, and OSGeo software much more accessible. It seems elusively achievable, but we haven't worked it out yet. If you think you could help, we'd love to hear from you.
Get involvedAre you a programmer or packager with experience in one of the Open Source GIS applications. Are you a technical writer interested in making FOSS4G accessible to all? Are you interested in helping updateÂ translations to latest documents on Transifex.
Contact usIf you would like to add a new project, help us to get in the cloud or have another goal you would like to work on and get involved you are very welcome.

Please join the OSGeoLive mailing listÂ or meet us on IRC at ourÂ weekly meeting.
About OSGeoLiveOSGeoLiveÂ is a â€‹Lubuntu based distribution of Geospatial Open Source Software, available via a Live DVD, Virtual Machine and USB. You can use OSGeoLive to try a wide variety of open source geospatial software without installing anything.
02 March 2019
14:22
Free and Open Source GIS Ramblings: Easy Processing scripts comeback in QGIS 3.6
sur Planet OSGeo
When QGIS 3.0 was release, I published a Processing script template for QGIS3. While the script template is nicely pythonic, itâ€™s also pretty long and daunting for non-programmers. This fact didnâ€™t go unnoticed and Nathan Woodrow in particular started to work on a QGIS enhancement proposal to improve the situation and make writing Processing scripts easier, while â€“ at the same time â€“ keeping in line with common Python styles.

While the previous template had 57 lines of code, the new template only has 26 lines â€“ 50% less code, same functionality! (Actually, this template provides more functionality since it also tracks progress and ensures that the algorithm can be cancelled.)
```
from qgis.processing import alg
from qgis.core import QgsFeature, QgsFeatureSink

@alg(name="split_lines_new_style", label=alg.tr("Alg name"), group="examplescripts", group_label=alg.tr("Example Scripts"))
@alg.input(type=alg.SOURCE, name="INPUT", label="Input layer")
@alg.input(type=alg.SINK, name="OUTPUT", label="Output layer")
def testalg(instance, parameters, context, feedback, inputs):
    """
    Description goes here. (Don't delete this! Removing this comment will cause errors.)
    """
    source = instance.parameterAsSource(parameters, "INPUT", context)

    (sink, dest_id) = instance.parameterAsSink(
        parameters, "OUTPUT", context,
        source.fields(), source.wkbType(), source.sourceCrs())

    total = 100.0 / source.featureCount() if source.featureCount() else 0
    features = source.getFeatures()
    for current, feature in enumerate(features):
        if feedback.isCanceled():
            break
        out_feature = QgsFeature(feature)
        sink.addFeature(out_feature, QgsFeatureSink.FastInsert)
        feedback.setProgress(int(current * total))

    return {"OUTPUT": dest_id}
```
The key improvement are the new decorators that turn an ordinary function (such as testalg in the template) into a Processing algorithm. Decorators start with @ and are written above a function definition. The @alg decorator declares that the following function is a Processing algorithm, defines its name and assigns it to an algorithm group. The @alg.input decorator creates an input parameter for the algorithm. Similarly, there is a @alg.output decorator for output parameters.

For a longer example script, check out the original QGIS enhancement proposal thread!

For now, this new way of writing Processing scripts is only supported by QGIS 3.6 but there are plans to back-port this improvement to 3.4 once it is more mature. So give it a try and report back!
11:16
GeoServer Team: GeoServer 2.15.0 Released
sur Planet OSGeo
The GeoServer team is happy to announce the GeoServer 2.15.0Â release with downloads (zip|war|exe), documentation (html|pdf) and extensions.

This release is production ready and is ready to work with your Java 8 or Java 11 operational environment. This release is made in conjunction with GeoWebCache 1.15.0 and GeoTools 21.0.

The ability to work with Java 11 is the result a dedicated code sprint. Thanks to organizations participating in the code sprint (Boundless, GeoSolutions, GeoCat,Â Astun Technology,Â CCRi) along with sprint sponsors (Gaia3D,Â atol, osgeo:uk, Astun Technology).
Layer Service Settings
To start things off an often requested capability, the ability to control which services are enabled on a layer-by layer basis.

To try it our yourself see Service Settings in our user manual.
GeoFence Internal Server Extension
Originally a standalone service offering fine grain control over GeoServer security this functionality has been packaged up and embedded into a GeoServer extension for easier deployment.
- GeoFence rules provided greater control over security allowing layer by layer service restrictions
- GeoFence rules can provide access to data overriding layer details including CQL filter to limit contents returned and default style used for rendering
- GeoFence rules can limit access to a geographic extent
For more details see GeoFence Internal Server in our user manual.
Style Editor SLD Auto-Complete
To help make editing easier the Style Editor can provide auto-complete suggestions for SLD 1.0. To try it out yourself use control-space for context aware suggestions.

Generate Classified Thematics maps
SLDService is now an official extension, with a number of improvements. SLDService can now be used for the
- classification of raster data too
- equal area classification
- standard deviation filtering
The SLD REST Service extension is used to generate thematic styles based on attribute data:
```
curl -v -u admin:geoserver -XGET
  [localhost:8080]   ?attribute=PERSONS
  &ramp=CUSTOM
  &method=quantile
  &intervals=3
  &startColor=0xFF0000
  &endColor=0x0000FF
  &open=true
```
For more information see SLD Rest Service in our user manual.

WPS GetExecutionStatus and Dismiss Operations
WPS â€œGetExecutionsâ€ vendor operation allows each user to get the list of running processes:
- Users can review all their running processes
- Administrators can see all processes
The Dismiss vendor operation can be used to cancel the execution of one of the listed processes.

For more information see Dismiss in our user guide.
Java 11 Support
The provided binary download works with either Java 8 or Java 11. Tomcat 9 or newer is required for the WAR install.Â The user guide compatibility listÂ will continue to be updated based on your feedback.

The java ecosystem is now being led by the open source OpenJDK project, with long term support available from a range of organizations notably RedHat OpenJDK Â and Adopt OpenJDK. TheÂ GeoTools user guide provides an overview of Java 8 and Java 11 distributions.

The net effect of these changes:
- If you have been using Oracle JDK please review your options
- Java 8 will continue to be available
- The Java ecosystem is now led by the open-source Open JDK project
Java 11 no longer supports the Java 2 extension mechanism used for native JAI and native ImageIO libraries. Â We recommend the use of the pure Java JAI-EXT operations which have been made the default (see the next section).
JAI-EXT operations on by default
The use of the JAI-EXT operations have long been a recommendation, with this release we are making them the default for GeoServer. Â The JAI-EXT library offers a pure java implementation enhanced for geospatial functionality supporting NODATA pixels and support for vector footprints.

GeoServer Codebase
In addition to Java 11 support this release includes:
- Add JSON as a Legend Output format (GISP 173)
- Printing plugin upgrade version of JTS
- Upgrade NetCDF dependencies
- Improvements for vector tile production, both in terms of output correctness and production performance
Thanks to Andrea Aime for steady work on the codebase quality:
- PMD source code analysis, high priority checks, will fail the build in case of issues
- Error Prone byte code analysis, same as above
- Many small bugs fixed
For more details developers are invited to review Automated Quality Assurance checks in our developers manual. Also, work in ongoing on the master (dev) branch to extend the reach of static code checks using SpotBugs and CheckStyle too.
About GeoServer 2.15 Series
Additional information on the GeoServer 2.15 series:
- Release Notes (2.15.0|2.15-RC|2.15-M0)
- Running on Java 11 (User Manual)
28 February 2019
17:06
gvSIG Team: Camino a gvSIG 2.5: EnumeraciÃ³n de capas en la Tabla de Contenidos
sur Planet OSGeo

Una de las componentes mÃ¡s utilizadas en un SIG es su Tabla de Contenidos, tambiÃ©n conocida como TOC por sus siglas en inglÃ©s.

En la Tabla de Contenidos se enumeran todas las capas de una Vista y se muestra la leyenda con la que se representan las entidades de cada capa. TambiÃ©n ayuda a administrar el orden de visualizaciÃ³n de las capas en la Vista, a definir las capas que son visibles, las que estÃ¡n seleccionadas, permite el acceso rÃ¡pido a distintas herramientas, etc.

Ya en gvSIG Desktop 2.4 iniciamos las mejoras en el TOC con la existencia de un catÃ¡logo, que permite la carga rÃ¡pida de capas y la gestiÃ³n de favoritos. En la nueva versiÃ³n, gvSIG 2.5, encontrarÃ©is un nuevo plugin â€œTabbed TOCâ€ con el que continuamos estas mejoras.

Mediante este nuevo plugin aÃ±adimos a la Tabla de Contenidos una serie de nuevas opciones para enumerar o agrupar las capas de nuestra Vista.

AdemÃ¡s de la enumeraciÃ³n principal podremos listar las capas segÃºn la fuente, si son o no visibles y si tienen o no elementos seleccionados. El procedimiento es muy sencillo, hacer clic en el icono de la parte superior del TOC que permite acceder a alguno de los mÃ©todos de agrupaciÃ³n.

Para ver cÃ³mo instalar este nuevo plugin y su funcionamiento, os dejamos con este vÃdeo:
16:57
gvSIG Team: Towards gvSIG 2.5: Listing layers at the Table of Contents
sur Planet OSGeo

One of the most used components in a GIS is the Table of Contents, also known as TOC.

All the layers of a View are listed at the Table of Contents, and the legend with which the entities of each layer are represented is shown too. It also helps to manage the display order of the layers in the View, to define the layers that are visible, which layers are selected, it allows quick access to different tools, etc.

In gvSIG Desktop 2.4, we started improvements in the TOC with a catalog, which allows to load layers quickly and manage the favourite ones. In the new version, gvSIG 2.5, you will find a new plugin called â€œTabbed TOCâ€ with which we are continuing these improvements.

Through this new plugin we add a series of new options to the Table of Contents to list or group the layers of our View.

Besides the main list, now we can list the layers according to the source, if they are visible or not, and if they have selected elements or not. The procedure is very simple, you have to click on the icon on the top of the TOC and it allows to access to any of the grouping methods.

Here you have a video about how to install this new plugin and how it works:

Â

Source Data size	Target Data size	Time Indexed	Time Brute-Force	Improvement
1 polygon (19,487 vertices)	244 polygons (366,951 vertices)	164 ms	136 s	x 830

Source Data size	Target Data size	Time	Time Brute-Force	Improvement
1 polygon (7,316 vertices)	100,000 polygons (500,000 vertices)	53 ms	10.03 s	x 19

13:25

Fernando Quadro: IntroduÃ§Ã£o ao Leaflet â€“ Trilhas com GeoJSON

sur Planet OSGeo

Para adicionar uma trilha ao nosso mapa, vamos convertÃª-lo de um shapefile para GeoJSON. HÃ¡ mais de uma maneira de fazer isso â€“ vocÃª poderia usar ogr2ogr, mas optamos por usar o QGIS, pois ele nÃ£o apenas o converteria, mas tambÃ©m transformaria o sistema de coordenadas ao mesmo tempo.

1. Convertendo para GeoJSON

Com o shapefile carregado no QGIS, podemos clicar com o botÃ£o direito na camada e escolher a opÃ§Ã£o â€œExport -> Save Features Asâ€¦â€

Escolhemos o sistema de coordenadas apropriado ( EPSG:4326 â€“ WGS 84) para uso com o Leaflet e o QGIS faz a conversÃ£o enquanto salva no GeoJSON. Isso torna nossa trilha pronta para uso no Leaflet.

2. Adicionando o arquivo

O arquivo GeoJSON precisa ser adicionado ao nosso arquivo HTML como um script, mas primeiro precisamos modificÃ¡-lo adicionando um nome de variÃ¡vel:

var trail = {
"type": "FeatureCollection",
"name": "rails",
"crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:EPSG::3857" } },
"features": [
...

Adicionando o var trail ao inÃcio do arquivo nos permitirÃ¡ fazer referÃªncia a ele no Leaflet.

Em seguida, adicionamos o script e agora podemos adicionÃ¡-lo ao mapa:

  var trail = L.geoJSON(trail);
  trail.addTo(map);

3. Estilizando a trilha

Podemos mudar a aparÃªncia da trilha adicionando opÃ§Ãµes Ã declaraÃ§Ã£o L.geoJSON:

Â Â varÂ thetrailÂ =Â L.geoJSON(trail,Â {
Â Â Â Â Â Â color:Â '#800000',
Â Â Â Â Â Â weight:Â 3,
Â Â Â Â Â Â dashArray:Â '12Â 8Â 12',
Â Â });

Isso transforma a trilha em vermelho escuro, aumentando sua largura para 3 pixels e criando uma linha tracejada.

4. Adicionando rÃ³tulo

Ao adicionar este rÃ³tulo quando se passa o mouse sobre a trilha o mesmo Ã© apresentado na tela:

thetrail.bindTooltip('Trilha de Brumadinho')

5. Resultado

ApÃ³s nossas mudanÃ§as o resultado do nosso mapa agora Ã© esse:

6. CÃ³digo

ApÃ³s as alteraÃ§Ãµes realizadas acima, o nosso cÃ³digo ficou da seguinte forma:

<!DOCTYPEÂ html>
<head>
Â Â <linkÂ rel="stylesheet"Â href="https://unpkg.com/leaflet@1.4.0/dist/leaflet.css"
Â Â integrity="sha512-puBpdR0798OZvTTbP4A8Ix/l+A4dHDD0DGqYW6RQ+9jxkRFclaxxQb/SJAWZfWAkuyeQUytO7+7N4QKrDh+drA=="
Â Â crossorigin=""/>Â Â 
Â Â <scriptÂ src="https://unpkg.com/leaflet@1.4.0/dist/leaflet.js"
Â Â integrity="sha512-QVftwZFqvtRNi0ZyCtsznlKSWOStnDORoefr1enyq5mVL4tmKB3S/EnC3rRJcxCPavG10IcrVGSmPh6Qw5lwrg=="
Â Â crossorigin=""></script>
Â Â <scriptÂ src="rails.geojson"></script>
<style>
Â Â Â Â #mapDIV{
Â Â Â Â Â Â Â Â height:Â 700px;
Â Â Â Â Â Â Â Â width:Â 700px;
Â Â Â Â Â Â Â Â border:Â solidÂ 1pxÂ black;
Â Â Â Â }
</style>
</head>
<body>
Â Â Â Â <divÂ id='mapDIV'></div>
<script>
Â Â Â Â varÂ mapÂ =Â L.map(document.getElementById('mapDIV'),Â {
Â Â Â Â center:Â [-20.1438,Â -44.1301],
Â Â Â Â zoom:Â 15
Â Â Â Â });
Â Â Â Â varÂ basemapÂ =Â L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png',Â {
Â Â Â Â Â Â Â Â });

Â Â Â Â basemap.addTo(map);
	
Â Â Â Â varÂ earthquakeMarkerÂ =Â L.marker([-20.1438,Â -44.1301],
Â Â Â Â Â Â Â Â Â {title:Â 'JaneiroÂ 25,Â 2019Â DesastreÂ deÂ Brumadinho'});
		Â 
Â Â Â Â earthquakeMarker.bindPopup(
Â Â Â Â Â Â Â Â Â "JaneiroÂ 25,Â 2019<br>Â DesastreÂ deÂ Brumadinho");
		Â 
Â Â Â Â earthquakeMarker.addTo(map);
Â 
Â Â Â Â varÂ thetrailÂ =Â L.geoJSON(trail,Â {
Â Â Â Â Â Â Â Â color:Â '#800000',
Â Â Â Â Â Â Â Â weight:Â 3,
Â Â Â Â Â Â Â Â dashArray:Â '12Â 8Â 12',
Â Â Â Â });
	
Â Â Â Â thetrail.bindTooltip('TrilhaÂ deÂ Brumadinho');
Â Â Â Â thetrail.addTo(map);
</script>
</body>
</html>

10:48
gvSIG Team: Towards gvSIG 2.5: New OSM map servers
sur Planet OSGeo
Surely most of you know the OpenStreetMap (OSM) cartography, and almost certainly you have used it in some of your projects with gvSIG Desktop. Now we have added three new servers to the great number of OSM servers that were already available in gvSIG, that we think that will be interesting for certain uses:
- OSM France. Oriented to show the OSM data with the toponymy in French and the most representative symbols of French culture (for example, bakeries are represented with the symbol of a baguette). Surely it will be useful for the growing French-speaking gvSIG Desktop users community.
- Hillshading. It shows the relief of the ground through a representation using grey tones.
- OSM B&W. In this case it shows the OSM cartography, as represented by Mapnik, but without using colours, only using grey tones.
Here you have a video where you can see these three new OSM servers:

And if you donâ€™t want to wait for the new gvSIG Desktop version to use them, you can add them manually filling in these parameters at the â€œOSMâ€ tab of the â€œAdd layerâ€ window:
- OSM France
  - Name: OSM France
  - URL: [a.tile.openstreetmap.fr]
  - Levels: 18
  - Format: png
- Hillshading
  - Name: Hillshading
  - URL: [c.tiles.wmflabs.org]
  - Levels: 18
  - Format: png
- OSM B&W
  - Name: OSM Black & White
  - URL: [tiles.wmflabs.org]
  - Levels: 18
  - Format: png
27 February 2019
18:56
GIScussions: Citymapper â€“ Londonâ€™s Uber?
sur Planet OSGeo

Travel Puzzle
Last week Citymapper (one of the poster children of the UKâ€™s OpenData movement) announced the launch of their CityMapper PASS card.

Citymapper started out with a travel app based on the early releases of transport open data by UK public providers, they then launched a hopper bus service for a short while and this morphed into their shared taxi service â€œRideâ€œ. Along the way they raised an enormous amount of funding for a relatively small startup â€“ according to Crunchbase they had a $10m Series A in 2014 and a $40m Series B in 2016 with some pretty serious investors coming on board. Now they have launched their PASS which potentially can save users upwards of Â£4 per week on the cost of an Oyster Card (London Transportâ€™s contactless card). The Guardian explained the basic finances here

â€œWhile the pass will bring in revenue, it will also result in the company losing money, at least in the short term. Technically, it operates as a simple pre-paid debit card, with Citymapper paying TfL for each journey its users take until they hit the standard weekly price cap.
That means that every user who reaches the daily Tube price cap (Â£7.00 for zones one and two) at least five days in seven will result in Citymapper losing money on them that week. The companyâ€™s explicit plan to counter that loss is to expand the pass by bundling in ever more private offerings, where it has more power to negotiate prices, until it offers a bundle that covers everything from dockless bikes, through rental cars, to ridesharing services.â€
https://www.theguardian.com/uk-news/2019/feb/27/citymapper-pass-launch-london-travel-card-with-cheaper-rate-than-tfl

If PASS is going to reach a critical mass (is that 10,000, 100,000 or more users?) they could be losing Â£15-20 per user per month at which point they will burn through their cash resources pretty quickly. The last accounts that Citymapper filed are for 2017 they show cash balances of Â£12.5m after an in year loss of Â£6.3m. It looks as if Citymapper will need another investment round to support an aggressive launch of PASS and the costs of acquiring users until they find ways to make the service profitable.

Does this matter? Just after the launch was announced JA Early said

It's not ever really been clear how Citymapper was supposed to make money. So, I assume, it's been funded by people who understand the immense value of data derived from sitting at the centre of a large network that tracks the travel times and habits of millions of urbanites.
â€” J A Earley (@AlbyEarley) February 21, 2019

The only way Citymapper can make serious money is through wielding the political power it will accrue from its dominant position in the marketplace.

It will eventually turn on the consumer, regulators and the public realm to carve out a lucrative niche.
â€” J A Earley (@AlbyEarley) February 21, 2019

Or as the Guardian concluded

â€œBut the launch of the service has prompted concerns from some that the companyâ€™s end goal is to try and burn its funding to establish a large base of users that it can then wield in political battles with city authorities to gain better terms for itself. That model has brought success for companies like Uber and Airbnb, which have reshaped regulations around their needs in cities including San Francisco, New York and Paris.â€
https://www.theguardian.com/uk-news/2019/feb/27/citymapper-pass-launch-london-travel-card-with-cheaper-rate-than-tfl

Time will tell whether this pivot will work for Citymapper and their backers, Iâ€™m doubtful whether there is enough demand for this all inclusive multimodal public transport payment system. Of course Uber have shown how you can disrupt a market by throwing enough investorsâ€™ money at undercutting existing players, whether that is good in the long term for users of these services remains to be seen.
15:42
gvSIG Team: Camino a gvSIG 2.5: Nuevos servicios de mapas de OSM
sur Planet OSGeo
Seguro que la gran mayorÃa de vosotros conocÃ©is la cartografÃa de OpenStreetMap (OSM), y con casi toda seguridad la habrÃ©is utilizado en alguno de vuestros proyectos con gvSIG Desktop. Al buen nÃºmero de servidores de OSM que ya estaban disponibles en gvSIG hemos aÃ±adido tres nuevos que consideramos que pueden ser interesantes para determinados usos:
- OSM France. Orientado a mostrar los datos de OSM con la toponimia en francÃ©s y simbologÃa mÃ¡s representativa de la cultura francesa (por ejemplo las panaderÃas ser representan con el sÃmbolo de una baguette). Seguramente serÃ¡ de utilidad para la cada vez mayor comunidad francÃ³fona de usuarios de gvSIG Desktop.
- Hillshading. Muestra el relieve del terreno mediante una representaciÃ³n del mismo utilizando tonos de gris.
- OSM B&W. En este caso muestra la cartografÃa de OSM, tal y como la representa Mapnik, pero sin uso del color, utilizando unicamente tonos de grises.
PodÃ©is ver un vÃdeo en el que se muestran estos 3 nuevos servicios de OSM:

Y si no querÃ©is esperar a la nueva versiÃ³n de gvSIG Desktop para utilizarlos, los podÃ©is aÃ±adir manualmente introduciendo estos parÃ¡metros en la pestaÃ±a de OSM de la ventana de â€œAÃ±adir capaâ€:
- OSM France
  - Nombre: OSM France
  - URL: [a.tile.openstreetmap.fr]
  - Levels: 18
  - Format: png
- Hillshading
  - Nombre: Hillshading
  - URL: [c.tiles.wmflabs.org]
  - Levels: 18
  - Format: png
- OSM B&W
  - Nombre: OSM Black & White
  - URL: [tiles.wmflabs.org]
  - Levels: 18
  - Format: png
12:24
gvSIG Team: Towards gvSIG 2.5: New geoprocess, Grid by point density
sur Planet OSGeo
In the previous post we talked about a series of geoprocesses related to criminology made together with Jaume I University (UJI). These geoprocesses can be used in different fields, not exclusively in criminology.

Now we are going to show the â€œGrid by point densityâ€ geoprocess. The main objective of this geoprocess is to perform a fast and efficient count of points contained in a grid, that also is created by the geoprocess. Here it has been raised for crimes, but it can be applied to many other things. It allows to visualize how events are distributed when there is a layer with a large accumulation of them in the same areas quickly.

Crimes in New York (150.000 features)

The input parameters are a point layer and an expression (optional) that would be a filter to run the geoprocess. For example, we could apply a filter by type of crime.

The options make reference to:
- Grid distance: At the distance from the side of each square or hexagon. In relation to the measurements of the View.
- Grid type: It can be squared or hexagonal. And in hexagonal type there are two types: Vertical or horizontal.
- Add empty grids: It doesnâ€™t add grid in areas where there are no specific elements, that is, where their count is zero.
Itâ€™s important to select the grid extension in the Analysis Region tab correctly.

The results of the geoprocess on the starting image layer returns a grid with an attribute table, where we will be able to apply a legend by intervals of values.

Here you can see the results on the complete crime layer with a shorter distance and vertical grid type.

And here applying a filter on a district.

In the attribute table you can see the total count of points within each grid, the total points involved in the initial calculation before filtering, and the percentage of those points in relation to the total.

In addition, we have taken advantage of this during the development of this geoprocess to improve and debug gvSIG to support layers with a larger number of records. One of these tests for this geoprocess was done with a layer with more than 6.7 million records and more than 10 fields.

You can now download and test the new Grid by point density geoprocess in the new distribution candidate to final version. You can download it from Tools -> Add-ons Manager, and search the â€œGeoprocess: Point density gridâ€ geoprocess. Once installed and after restarting gvSIG, it will appear at the toolbox in the â€œScripting â€“ Data Analysis â€“ Grid by density of pointsâ€ section.

If you find any error or you have any recommendation, we encourage you to write to the gvSIG mailing lists.
11:30
Fernando Quadro: IntroduÃ§Ã£o ao Leaflet â€“ Adicionando Marcador
sur Planet OSGeo
Estou começando devagar, então hoje vamos adicionar um marcador com alguns recursos extras. Já que o mapa de ontem já está centralizado no Desastre de Brumadinho, vamos adicionar um marcador lá.

1. Adicionando um Marcador

Para criar um marcador, o Leaflet usa a classe L.marker:
```
var earthquakeMarker = L.marker([-20.1438, -44.1301]);
```
Isso cria o marcador, porém precisa ser adicionado ao mapa:
```
earthquakeMarker.addTo(map);
```
E o nosso mapa fica assim:

Bom até agora, mas olhando para o mapa não nos diz nada sobre o marcador. Vamos mudar isso adicionando um título:
```
var earthquakeMarker = L.marker([-20.1438, -44.1301], 
    {title: 'Janeiro 25, 2019 Desastre de Brumadinho'});
```
Agora, quando passamos o marcador, recebemos um título:

Agora, vamos adicionar um pop-up ao marcador para exibir mais informações no evento do click. Fazemos isso vinculando um pop-up ao nosso marcador existente:
```
var earthquakeMarker = L.marker([-20.1438, -44.1301], 
    {title: 'Janeiro 25, 2019 Desastre de Brumadinho'});
earthquakeMarker.bindPopup("Janeiro 25, 2019
Desastre de Brumadinho");
earthquakeMarker.addTo(map);	
```
Quando clicamos no marcador, o pop-up é exibido.
26 February 2019
18:01
gvSIG Team: Camino a gvSIG 2.5: Nuevo geoproceso, Rejilla por densidad de puntos
sur Planet OSGeo
Hablamos en el post anterior 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 Rejilla por densidad de puntos. El objetivo principal de este geoproceso es el de realizar de una forma rÃ¡pida y eficiente un conteo de puntos contenidos en una rejilla que tambiÃ©n crea el geoproceso. En el caso planteado, delitos, pero se puede aplicar a muchas otra cosas. Esto permite visualizar de forma rÃ¡pida cÃ³mo se distribuyen los eventos cuandoÂ hay una capa con una gran acumulaciÃ³n de ellos en unas mismas zonas.

Delitos en Nueva York (150.000 entidades)

Los parÃ¡metros de entrada son una capa de puntos y una expresiÃ³n (opcional) que servirÃa de filtrado para ejecutar el geoproceso. Por ejemplo, podrÃamos aplicar un filtro por tipologÃa de delito.

Las opciones hacen referencia a:
- Distancia de rejilla: A la distancia del lado de cada cuadrado o hexÃ¡gono. En relaciÃ³n con las medidas de la Vista.
- Tipo de rejilla: PuedeÂ ser cuadricular o hexagonal. Y en hexagonal dos tipos: Vertical o horizontal.
- AÃ±adir rejillas vacÃas: No aÃ±adir rejilla en las zonas donde no hay elementos puntuales, o sea, donde su conteo es cero.
Es importante seleccionar correctamente en la pestaÃ±a de RegiÃ³n de anÃ¡lisis cual va a ser la extensiÃ³n de la rejilla.

El resultado del geoproceso sobre la capa de la imagen inicial devuelve una rejilla con una tabla de atributos a la que podemos aplicarle una leyenda por intervalo de valores.

AquÃ un resultado sobre toda la capa de delitos con otra distancia mÃ¡s pequeÃ±a y de tipo rejilla vertical.

AquÃ aplicando un filtro sobre un distrito.

En la tabla de atributos se puede ver el conteo total de puntos dentro de cada rejilla, el total de puntos implicados en el cÃ¡lculo inicial antes del filtrado, y el porcentaje de esos puntos respecto al total.

AdemÃ¡s, hemos aprovechado durante el desarrollo de este geoproceso en hacer mejoras y depurar gvSIG para soportar capas con mayor nÃºmero de registros. Una de estas pruebas para este geoproceso se realizo con una capa con mÃ¡s de 6.7millones de registros y mÃ¡s de 10 campos.

Ya puedes descargarte y probar el nuevo geoproceso de Rejilla por densidad de puntosÂ en la nueva candidata a versiÃ³n final . Puedes descargarlos de Herramientas -> Administrador de complementos y buscar por el geoproceso â€œGeoprocess: Point density gridâ€. Una vez instalado, aparecerÃ¡ junto a los geoprocesos dentro del apartado de â€œScripting â€“ AnÃ¡lisis de datos â€“ Rejilla por densidad de puntosâ€.

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

11:30

Fernando Quadro: IntroduÃ§Ã£o ao Leaflet â€“ Parte 1

sur Planet OSGeo

Prezados leitores,

Os prÃ³ximos 13 posts, serÃ£o dedicados a uma introduÃ§Ã£o ao framework Leaflet. Estarei comeÃ§ando do zero e cada postagem no blog serÃ¡ adicionado um pouco mais ao projeto. As postagens provavelmente nÃ£o serÃ£o publicadas todos os dias.

Parte 1 â€“ Configurando um Mapa Simples

Para comeÃ§ar, vamos criar um modelo, copiado diretamente dos documentos do Leaflet:

<!DOCTYPEÂ html>
<head>
Â Â <linkÂ rel="stylesheet"Â href="https://unpkg.com/leaflet@1.4.0/dist/leaflet.css"
Â Â crossorigin=""/>Â Â 
Â Â <scriptÂ src="https://unpkg.com/leaflet@1.4.0/dist/leaflet.js"
Â Â crossorigin=""></script>
Â Â <style>
Â Â Â Â Â Â #mapDIV{
Â Â Â Â Â Â Â Â Â Â height:Â 700px;
Â Â Â Â Â Â Â Â Â Â width:Â 700px;
Â Â Â Â Â Â Â Â Â Â border:Â solidÂ 1pxÂ black;
Â Â Â Â Â Â }
</style>
</head>
<body>
Â Â Â Â <divÂ id='mapDIV'>i</div>
</body>
</html>

TambÃ©m criamos um div para manter o id do mapa (mapDIV) na seÃ§Ã£o head, e adicionamos um estilo para definir o tamanho do mapa quando exibido no navegador. Este HTML irÃ¡ â€œcarregarâ€ o Leaflet, mas vocÃª nÃ£o verÃ¡ nada. Precisamos adicionar um script que crie o mapa.

<script>
Â Â Â Â Â Â varÂ mapÂ =Â L.map(document.getElementById('mapDIV'),Â {
Â Â Â Â Â Â center:Â [-20.1438,Â -44.1301],
Â Â Â Â Â Â zoom:Â 15
Â Â Â Â Â Â });
Â Â Â Â Â Â varÂ basemapÂ =Â L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png',Â {
Â Â Â Â Â Â Â Â Â Â });
Â Â Â Â Â Â Â Â Â Â basemap.addTo(map);
</script>

Este pequeno script, colocado depois da mapDiv, faz o seguinte:

Adiciona um objeto de mapa
Centraliza em uma latitude/longitude
Define o nÃvel de zoom
Adiciona o mapa base do OpenStreetMap

Se nÃ³s carregarmos o arquivo em nosso navegador, nÃ³s veremos isto:

Este mapa Ã© centrado na localizaÃ§Ã£o do desastre de Brumadinho que ocorreu no dia 25 de janeiro de 2019. Vamos movÃª-lo em um post posterior.

Esse Ã© o nosso primeiro post. A atribuiÃ§Ã£o Ã© importante e vamos adicionÃ¡-la ao mapa, junto com outras novidades no prÃ³ximo post.

Aqui estÃ¡ o arquivo HTML completo:

<!DOCTYPEÂ html>
<head>
Â Â <linkÂ rel="stylesheet"Â href="https://unpkg.com/leaflet@1.4.0/dist/leaflet.css"
Â Â crossorigin=""/>Â Â 
Â Â <scriptÂ src="https://unpkg.com/leaflet@1.4.0/dist/leaflet.js"
Â Â crossorigin=""></script>
Â Â <style>
Â Â Â Â Â Â #mapDIV{
Â Â Â Â Â Â Â Â Â Â height:Â 700px;
Â Â Â Â Â Â Â Â Â Â width:Â 700px;
Â Â Â Â Â Â Â Â Â Â border:Â solidÂ 1pxÂ black;
Â Â Â Â Â Â }
</style>
</head>
<body>
Â Â Â Â <divÂ id='mapDIV'>i</div>
<script>
Â Â Â Â Â Â varÂ mapÂ =Â L.map(document.getElementById('mapDIV'),Â {
Â Â Â Â Â Â center:Â [-20.1438,Â -44.1301],
Â Â Â Â Â Â zoom:Â 15
Â Â Â Â Â Â });
Â Â Â Â Â Â varÂ basemapÂ =Â L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png',Â {
Â Â Â Â Â Â Â Â Â Â });
Â Â Â Â Â Â Â Â Â Â basemap.addTo(map);
</script>
</body>
</html>

1:28
Martin Davis: Better/Faster ST_PointOnSurface for PostGIS
sur Planet OSGeo

And now for the final chapter in the saga of improving InteriorPoint / PointOnSurface.Â For those who missed the first two episodes, the series beganÂ with a new approach for the venerable JTS Geometry.interiorPoint() for polygons algorithm.Â Episode 2 travelled deep into the wilds of C++ with a port to GEOS.Â The series finale shows how this results in greatly improved performance of PostGIS ST_PointOnSurface.

The BC Voting Area dataset is a convenient test case, since it has lots of large polygons (shown here with interior points computed).
The query is about as simple as it gets:

Â Â select ST_PointOnSurface(geom) from ebc.voting_area;

Here's the query timings comparison, using the improved GEOS code and the previous implementation:

Data size Time Time
OLD Improvement Time
ST_Centroid
5,658 polygons
(2,171,676 vertices) 341 ms 4,613 ms x 13 369 ms

As expected, there is a dramatic improvement in performance.Â The improved ST_PointOnSurface runs 13 times faster than the old code.Â And it's now as fast as ST_Centroid.Â It's also more robust and tolerant of invalid input (although this test doesn't show it).

This should show up in PostGIS in the fall release (PostGIS 3 / GEOS 3.8).

On to the next improvement... (and also gotta update the docs and the tutorial!)
25 February 2019
17:05
Fernando Quadro: Usando tiles do OpenStreetMap para Machine Learning
sur Planet OSGeo
O OpenStreetMap Ã© uma fonte de dados incrÃvel. O esforÃ§o coletivo de milhares de voluntÃ¡rios criou um rico conjunto de informaÃ§Ãµes que abrange quase todos os locais do planeta.

HÃ¡ um grande nÃºmero de problemas em que as informaÃ§Ãµes do mapa podem ser Ãºteis:
- Urbanismo
- Infraestrutura de transporte pÃºblico
- Campanhas de marketing
- Pontos crÃticos de crimes e trÃ¡fego
No entanto, para cada problema individual, hÃ¡ uma quantidade significativa de pensamento que precisa ser decidida sobre como transformar os dados usados â€‹â€‹para criar o mapa em recursos Ãºteis para a tarefa em questÃ£o. Para cada tarefa, Ã© preciso entender os recursos disponÃveis e escrever cÃ³digo para extrair esses recursos do banco de dados do OpenStreetMap.

Uma alternativa a essa abordagem manual de engenharia de recursos seria usar redes convolucionais nos tiles renderizados do mapa.

1. Como as redes convolucionais poderiam ser usadas?

Se houver um relacionamento forte o suficiente entre as imagens do mapa (tiles) e a variÃ¡vel de resposta, uma rede convolucional poderÃ¡ aprender os componentes visuais do mapa que sÃ£o Ãºteis para cada problema. Os designers do OpenStreetMap fizeram um Ã³timo trabalho ao garantir que a renderizaÃ§Ã£o do mapa expusesse tanta informaÃ§Ã£o quanto o sistema visual pudesse compreender. E as redes de convoluÃ§Ã£o provaram ser muito capazes de imitar o desempenho do sistema visual â€“ por isso, Ã© viÃ¡vel uma rede convolucional poder aprender quais recursos extrair das imagens â€“ algo que seria demorado programar para cada domÃnio de problema especÃfico.

2. Testando a hipÃ³tese

Para testar se redes convolucionais podem aprender recursos Ãºteis do mapa, foi escolhido um problema simples: Estimar a populaÃ§Ã£o de um determinado bloco do mapa. O censo dos EUA fornece dados sobre o nÃºmero da populaÃ§Ã£o no nÃvel do setor censitÃ¡rio, e Ã© possÃvel usar a informaÃ§Ã£o de populaÃ§Ã£o dos setores para aproximar com as informaÃ§Ãµes de populaÃ§Ã£o do mapa.

As etapas envolvidas:
- FaÃ§a o download dos dados da populaÃ§Ã£o no nÃvel do setor censitÃ¡rio do Census Bureau.
- Para um determinado nÃvel de zoom, identifique os tiles do OpenStreetMap que se cruzam com 1 ou mais setores censitÃ¡rios.
- FaÃ§a o download dos tiles de uma instÃ¢ncia local do OpenMapTiles.
- Soma a populaÃ§Ã£o dos tratos dentro de cada tile, e adicione as populaÃ§Ãµes fracionÃ¡rias para trechos que se cruzam com o tile.
Visualizando os setores censitÃ¡rios que se sobrepÃµem aos 3 tiles de exemplo

Isso nos dÃ¡:
- Entrada X : uma representaÃ§Ã£o de bitmap (RGB) do tile do OpenStreetMap
- Meta Y : uma populaÃ§Ã£o estimada do tile
Para reiterar, as Ãºnicas informaÃ§Ãµes usadas pela rede para prever a populaÃ§Ã£o sÃ£o os valores RGB dos tiles do OpenStreetMap.

Para este experimento, gerou um conjunto de dados da CalifÃ³rnia, mas o mesmo processo pode ser feito para todos os estados dos EUA.

3. Resumo

Desempenho da rede ao prever a populaÃ§Ã£o de um determinado ladrilho

No exemplo de estimativa da populaÃ§Ã£o, hÃ¡ informaÃ§Ãµes suficientes nos tiles do OpenStreetMap para superar significativamente um estimador ingÃªnuo de populaÃ§Ã£o.
Para problemas com um sinal forte o suficiente, os tiles do OpenStreetMap podem ser usados â€‹â€‹como uma fonte de dados sem a necessidade de engenharia manual de recursos.

Este post foi traduzido e adaptado do original escrito por Robert Kyle do site Towards Data Science.
11:00
CARTO Blog: Introducing the new CARTO dashboard ðŸŽ‰
sur Planet OSGeo

The dashboard is one of the core pieces of CARTO. Itâ€™s what users see right after they login to their CARTO accounts. From here, users can manage their datasets, create map...
9:18
gvSIG Team: Towards gvSIG 2.5: Fields importer
sur Planet OSGeo

We continue with a new feature of the next gvSIG Desktop version. In this post we will show you how the new tool to import fields works. Thanks to it you can import the fields that you want from one table to another, through a field that allows to establish a relationship.

This tool allows you to optimize this type of tasks, which otherwise would have to be done by establishing a series of steps: creating a link, exporting to new layer, editing the table if we want to make changes in the configuration of fields â€¦ With the fields importer all these actions are reduced to the use of a single tool, where you can define the fields to be imported and even define how to name them once imported. This is another extremely useful novelty.

Here you have a video where how to install the plugin and how it works is shown:
24 February 2019
9:04
gvSIG Team: Camino a gvSIG 2.5: Importador de campos
sur Planet OSGeo

Seguimos con las numerosas novedades de la prÃ³xima versiÃ³n de gvSIG Desktop. En este post vamos a mostrar como funciona la nueva herramienta de importar campos. Gracias a ella podemos importar los campos que deseemos de una tabla a otra, mediante un campo que permita establecer una relaciÃ³n.

Esta herramienta permite optimizar este tipo de tareas, que de otro modo se tendrÃan que hacer estableciendo una serie de pasos: crear un enlace, exportar a nueva capa, editar la tabla si queremos realizar cambios en la configuraciÃ³n de camposâ€¦

Con el importador de campos todas estas acciones se reducen al uso de una Ãºnica herramienta, donde podemos definir los campos a importar e incluso definir el nombre con el que queremos que aparezcan una vez importados. Otra novedad extremadamente Ãºtil.

Os dejamos un vÃdeo que muestra cÃ³mo instalar el plugin y su funcionamiento:
22 February 2019
15:13
gvSIG Team: Towards gvSIG 2.5: New geoprocess, Ring map
sur Planet OSGeo

In the last gvSIG Conferences we talked about a series of geoprocess created for criminology developed with Universidad Jaume I (UJI). You can see the video here (in spanish, if you have any question you can write directly to us and we will help you). This geoprocess can be used in different fields, not only in criminology.

The first geoprocess that we are going to present is the Ring Map. The objective of this geoprocess is to make easy to visualize info that is inside the layer. For example, it will show info in multipleÂ fields in a single map.

In this example, we are going to see a layer with the population on each block for different range of ages. The result of the ring map will be like in the image. Now with this graph, with a quick look, we can analyse quickly how the population is distributed in each block and in different age ranges.

This geoprocess generate a series of rings and sectors. Each ring is a reference for the same field, and each sector is for the same geometry, that is pointed with an arrow. It creates three new layers with the rings, labels and arrows. Each of them can be modified as a normal shapefile. It creates an automatic legend that can also be modified as we need them.

The parameters that we need to execute this geoprocess is, at least one layer, (with any type of geometry) that it has a field with unique values for each geometry. It needed a opened table. If you are going to use layers,Â be sure that you open previously the attributes table, if not, thisÂ table will not appear as an option. If it doesnâ€™t have an unique field, you can create it using the Field Calculator. This option has been createdÂ becouse it is posible to create diferent representations (differents table) to show them over the same vectorial layer.

The fields should be written in the order that we want them to appear. Also, we have multiple options for change the visualization of the rings. We can change sectors, gaps, size, labels..

This is a similar result from the initial image.

As always, you can see more information about this process pressing the help button.

You can test the Ring Map geoprocessÂ at the newÂ distribution candidateÂ to final version. Just go to Tools -> Addons Manager and Search for â€œGeoprocess: Ring Mapâ€.

If you find any error we encourage you to write about it at the users mailing list. It will help us to fix them.
14:45
gvSIG Team: Camino a gvSIG 2.5: Nuevo Geoproceso, Mapa de anillos
sur Planet OSGeo

Ya comentamos en las Ãºltimas jornadas de gvSIG una serie de geoprocesos relacionados con criminologÃa junto a la Universidad Jaume I (UJI). Puedes ver el video de la ponencia aquÃ. Estos geoprocesos pueden utilizarse en diferentes campos, no ligado en exclusiva a la criminologÃa.

El primer geoprocesoÂ que vamos a presentar es el de Mapa de anillos. El objetivo es el de facilitar la visualizaciÃ³n de una capa que dispone de informaciÃ³n en diferentes campos y necesitamos mejorar la visualizaciÃ³n de todos ellos para presentarlos en un mapa.

En el siguiente ejemplo, vamos a ver una capa que contiene la poblaciÃ³n en diferentes campos de la tabla de atributos, para visualizarlo generaremos un mapa de anillos que darÃ¡ como resultado algo similar a la imagen de a continuaciÃ³n. De esta forma podemos ver de un vistazo rÃ¡pido como se distribuye la poblaciÃ³n en diferentes franjas de edades sobre una zona del mapa.

El geoproceso genera una serie de anillos y sectores. Cada anillo hace referencia a un mismo campo y cada sector hace referencia a una misma entidad o geometrÃa, con una flecha que seÃ±ala la geometrÃa de la cual extrae los valores. Vemos que genera una serie de capas sobre la vista que podemos tratarlas como cualquier otra capa de gvSIG. Dispone de una leyenda que se genera de forma automÃ¡tica y de una serie de capas de puntos que sirven para colocar las etiquetas. Todas ellas son modificables para adaptarseÂ a las necesidades que tengamos.

Los parÃ¡metros necesarios para ejecutar este geoproceso es mÃnimo una capa (puede ser de cualquier tipo de geometrÃa) que tenga de forma obligatoria un campo con un valor Ãºnico que identifique cada geometrÃa. Tiene que haber una tabla abierta (si usas solo capas vectoriales asegÃºrate de abrir la tabla de atributos con antelaciÃ³n para poderla seleccionar sino no aparecerÃ¡ en el listado de tablas disponibles). Si no lo tuviera podrÃamos crearle uno desde la calculadora de campos. Este campo Ãºnico tiene el uso de que sobre una misma capa vectorial, podrÃamos tener diferentes resultados a mostrar en diferentes tablas cuyos valores podrÃan ser calculados en otros programas. El geoproceso relacionarÃ¡ esos valores por su valor Ãºnico y los mostrarÃ¡.

Los campos a mostrar deberÃ¡n ser escritos por orden en que queremos que se muestren. TambiÃ©n disponemos de muchas opciones de configuraciÃ³n para la creaciÃ³n de los anillos. Desde posiciÃ³n de los sectores, espacio entre ellos, tamaÃ±o del circulo interior, del grosor de cada sector, creaciÃ³n de etiquetas..

AquÃ puedes ver otra representaciÃ³n similar a la de la imagen inicial.

Siempre puedes ver con mÃ¡s detalle la informaciÃ³n del geoproceso presionando el botÃ³n de ayuda.

Ya puedes descargarte y probar el nuevo geoproceso de mapa de anillos en laÂ nueva candidata a versiÃ³n final . Puedes descargarlos de Herramientas -> Administrador de complementos y buscar por el geoproceso â€œGeoprocess: Ring Mapâ€

Si encuentras cualquier fallo o recomendaciÃ³n te animamos a escribirnos a las Listas de correo de gvSIG.
14:00
Paul Ramsey: Proj6 in PostGIS
sur Planet OSGeo
Map projection is a core feature of any spatial database, taking coordinates from one coordinate system and converting them to another, and PostGIS has depended on the Proj library for coordinate reprojection support for many years.

For most of those years, the Proj library has been extremely slow moving. New projection systems might be added from time to time, and some bugs fixed, but in general it was easy to ignore. How slow was development? So slow that the version number migrated into the name, and everyone just called it â€œProj4â€.

No more.

Starting a couple years ago, new developers started migrating into the project, and the pace of development picked up. Proj 5 in 2018 dramatically improved the plumbing in the difficult area of geodetic transformation, and promised to begin changing the API. Only a year later, here is Proj 6, with yet more huge infrastructural improvements, and the new API.

Some of this new work was funded via the GDALBarn project, so thanks go out to those sponsors who invested in this incredibly foundational library and GDAL maintainer Even Roualt.

For PostGIS that means we have to accomodate ourselves to the new API. Doing so not only makes it easier to track future releases, but gains us access to the fancy new plumbing in Proj.

For example, Proj 6 provides:

Late-binding coordinate operation capabilities, that takes metadata such as area of use and accuracy into accountâ€¦ This can avoid in a number of situations the past requirement of using WGS84 as a pivot system, which could cause unneeded accuracy loss.

Or, put another way: more accurate results for reprojections that involve datum shifts.

Hereâ€™s a simple example, converting from an old NAD27/NGVD29 3D coordinate with height in feet, to a new NAD83/NAVD88 coordinate with height in metres.
```
SELECT ST_Astext(
         ST_Transform(
           ST_SetSRID(geometry('POINT(-100 40 100)'),7406), 
           5500));
```
Note that the height in NGVD29 is 100 feet, if converted directly to meters, it would be 30.48 metres. The transformed point is:
```
POINT Z (-100.0004058 40.000005894 30.748549546)
```
Hey look! The elevation is slightly higher! Thatâ€™s because in addition to being run through a horizontal NAD27/NAD83 grid shift, the point has also been run through a vertical shift grid as well. The result is a more correct interpretation of the old height measurement in the new vertical system.

Astute PostGIS users will have long noted that PostGIS contains three sources of truth for coordinate references systems (CRS).

Within the spatial_ref_sys table there are columns:
- The authname, authsrid that can be used, if you have an authority database, to lookup an authsrid and get a CRS. Well, Proj 6 now ships with such a database. So thereâ€™s one source of truth.
- The srtext, a string representation of a CRS, in a standard ISO format. Thatâ€™s two sources.
- The proj4text, the old Proj string for the CRS. Until Proj 6, this was the only form of definition that the Proj library could consume, and hence the only source of truth that mattered to PostGIS. Now, itâ€™s a third source of truth.
Knowing this, when you ask PostGIS to transform to an SRID, what will it do?
- If there are non-NULL values in authname and authsrid ask Proj to return a CRS based on those entries.
- If Proj fails, and there is a non-NULL srtext ask Proj to build a CRS using that text.
- If Proj still fails, and there is a non-NULL proj4text ask Proj to build a CRS using that text.
In general, the best transforms will come by having Proj look-up the CRS in its own database, because then it can apply all the power of â€œlate bindingâ€ to ensure the best transformation for each geometry. Hence we bias in favour of Proj lookups, then the quite detailed WKT format, and finally the old Proj format.
8:13
Cameron Shorter: Inspiring techies to become great writers
sur Planet OSGeo
How to attract writers into Open Source communities, have them amplify developers' written impact, reduce tech ramp-up, facilitate growth,Â while having fun improving the world.

Reading time: 8 minutesPresented at Write The Docs - Sydney [slides]
My story starts at the international conference for Free and Open Source Software for Geospatial when it was held here in Sydney, ten years ago. We wanted to build a distribution of the software to hand out to conference attendees. Back then when software was expensive to download, it was a useful handout, and it provided an attractive marketing pipeline for these free software projects.To build the first version of OSGeoLive we followed install instructions, configured applications, resolved dependencies and conflicts, asked questions on email lists, and finally, after much hard work, produced our first release. This was a very important first step as it showed that we had the commitment to follow through and deliver.
However, it also highlighted many of our failings. We had followed a fully manual install process, so when the next software releases came out, we had to start the installation process again, from scratch. It was completely unsustainable. We needed to automate the install process, and we needed projects to show us how.
But our first calls for help were embarrassingly underwhelming. You see, the perceived learning curve for packaging was considered unacceptably high and volunteers were not stepping up.
To fix this, we wrote an example install script along with clear, step-by-step instructions. We then went back to developers with the message of "if you can spend a couple of hours writing a short install script which looks like this, then we will market your application though our OSGeoLive distribution". Small effort / High Value. And it worked! 28 projects packaged their applications for our version 2 release.In following releases, we applied the same process to documentation. Our first docs were written by developers and as such were quite ... variable.Â So we created skeleton outlines for Project Overviews and Quickstarts, along with clear writing instructions. We then asked projects to write documentation in line with theses outlines. We followed up with reviews, and a publishing pipeline, to produce consistent, quality material. So by applying an outline / write / review / publish process, we were able to achieve significant efficiencies by allowing experts to focus only on the bits they do best and thus reduce contribution effort.
Translators later adopted the same formula to create multiple language variants.
Unpacking the storyOk, letâ€™s unpack this story from the perspective of technical writers. Firstly, we should acknowledge the significant efficiencies software enables. Four out of the ten richest people in the world are self made software entrepreneurs.
However, while proprietary businesses centralise captured wealth, open source software, like other creative commons works, is given away for free. This act of sharing has far reaching consequences. Tools and knowledge created can be used and built upon by everyone. This democratises knowledge, wealth and power.
So if you want to positively improve our world, supporting Open Source projects is a good place to start.
The ResearchSo what makes a successful Open Source project; one which is sustained in the long term? Research provides some answers,Â Â An analysis of over 170,000 Open Source projects to identify success factors, and a study of the success factors of episodic volunteering in Open SourceÂ both highlight the importance of:
- Clear utility,
- Lean governance,
- Clear vision and goals,
- Marketing and a quality website,
- Good user and developer documentation,
- Digestible information,
- Guided introductions,
- Simple workspaces,
- Taskâ€“finding dashboards,
- Financial backing,
- Fine scaled task granularity, making it easier for people to contribute.
And on the social side:
- Leaders who lead by doing, by putting in the hard work,
- A virtuous and supportive community,
- Attracting external contributors,
- Advocating broadly, by all involved,
- A sense of collective ownership,
- Hosting of meetups,
- Recognising all forms of contribution,
- Personal invitations for help,
- Showing appreciation.
Notice the prevalence of communication within these characteristics?Communicators Needed
Where Iâ€™m heading here is that while the Open Source story usually focuses on software developers, equally important are communicators and community builders. So for you folks who are technical writers, Open Source communities need you! Your involvement can significantly amplify a projectâ€™s impact, and by extension, your help will be:
- Making the world more egalitarian,Â
- Reducing wealth inequality,Â
- And democratising knowledge and power.Â
Bridging the tech gapIâ€™d like to touch on inflection points. As a projectâ€™s technology and user base matures, community success factors move. An early inflection point with Open Source projects happens when a project attracts external contributors. These contributors increase the size of the workforce and adds extra skills, but they lack the deep domain expertise of the core team.Â To attract contributors, projects should to reduce ramp up time; and good documentation is key. Poetically however, the documenters who are most qualified to help are typically the least technical, and face the greatest ramp up time.To help explain this problem, Iâ€™d like to introduce you to Johanna Botman. She started her working career as an english teacher, then moved into IT, website design, and is now a geospatial officer in local council. I met her at a spatial conferenceâ€™s community day when she joined other volunteers in updating our OSGeoLive documentation. It was a humbling experience for me. I saw such an accomplished person, with oodles of commitment, struggling to use our documentation tools.Johanna reviewed an early draft of this presentation and observed that ...
Some of the issues relating to getting started is about bridging the gap between developers and writers.Â Developers write code in coding tools. They collaborate, they are used to versioning and are at home with unformatted raw text and automation tools. Writers? They work on Windows machines in Word â€“ maybe in Google Docs if they are lucky. They donâ€™t know about running build scripts, running Linux variants, Github, chat programs, HTML, RST, Wikis and the variants of markup languages.
Itâ€™s one thing to work with the Open Source software, another to write about it, and a third thing to work out how to write it so that it fits in with the project. It seems as if the developers have created the writing system in a way that they are used to working, not necessarily in a way that works for writers.
And I think Johanna is right. Iâ€™ve found many users and writers who are keen to help, but feel overwhelmed, donâ€™t know where to start, donâ€™t want to burden the existing community, and so are shy to ask questions.Writers need to be sought out, welcomed, encouraged, supported and publicly appreciated if projects are to attract good documenters to help them grow.In turn, Iâ€™d encourage writers to proactively reach out to development communities. Iâ€™d expect youâ€™ll find them very welcoming and appreciative, especially if you are volunteering to tackle key documentation pain points.And together we need to help bridge the gap between writers and developers.Documentation StrategySo what should writers expect to see when joining a project. Typically, emerging projects have patchy documentation, in various stages of currency, completion, relevance, verbosity, and quality. The challenge is to consolidate it so that it becomes concise, intuitive, accurate, minimises learning and ramp up time, and sustainably maintained to match continually evolving software releases. This is non-trivial and requires good writing skills, planning, leadership, commitment and follow through to do it well.The problems are that:
- Software is complex. Itâ€™s hard to understand, and harder to explain.
- Software continually evolves, meaning documentation needs to be continually maintained.
- Projects have a range of audiences, with differing information needs, technical backgrounds, and attention spans.
It helps toÂ define the characteristics of your different communication mediums.
Raw imageÂ (inÂ draw.ioÂ format)
Your front web page and elevator pitch should be concise, highly polished and target first time visitors, while community forums are good for once off questions and can be rough around the edges.For each medium you should define your:
- Target audience,
- Document structure,
- Technical depth,
- Quality requirements, and
- Maintenance strategy.
Then aim to:
- Write timeless material to minimise maintenance.
- Only write as much as your team has capacity to maintain.
- Help techies become great writers. Provide skeleton docs and writing instructions, then review, mentor and publish.
- Work within a release cycle, which ideally synchronises with the project.Â
Itâ€™s worth noting that most of what Iâ€™m talking about here is relevant to all sorts of technical writing - not just for Open Source communities.
Getting Started?Okay, so maybe youâ€™d like to get involved and are wondering where to start? Iâ€™d suggest:
Image source
- Focus on one project instead of many, as your ramp-up time will likely be high.Â
- Acknowledge the value you bring. Use it as motivation because youâ€™ll have many challenges and the inner motivation will really help.
- Demonstrate commitment. Itâ€™s contagious.
- Ask for help, you will need it, and youâ€™ll likely be surprised how supportive people will be.
- Donâ€™t be daunted by your lack of domain knowledge. Itâ€™s actually an asset when writing to a broad audience.
- Help developers become great writers. Great impact comes from amplifying the effectiveness others.Â
- Be part of the team; help paint the vision; be inspirational.
- And most of all, have fun while you are doing it. Because believe you me, it is hugely rewarding to share the team camaraderie involved in building something that is much bigger and more impactful than you could possibly create by yourself.
21 February 2019
20:52
Martin Davis: Better/Faster Interior Point for Polygons - now in GEOS
sur Planet OSGeo
As a gentle introduction to GEOS development I took on the task of porting the recent improvements to the JTS InteriorPointArea algorithm.Â Â This is a fairly small chunk o'code, but it touches most of the aspects of GEOS development process: build chain, debugging, unit tests, and infra (source control and build farm).Â It also has the advantage that the JTS code was still hot off the keyboard and (almost) unreleased, so it was a chance to see if any cross-fertilization would blossom from working on the two projects jointly.

Skipping lightly over the details of my (somewhat painful)Â GEOS learning curve, I'm delighted to say that the code has landed in master and is basking in the green glow from the build bot badges.

And now the whole point of the exercise: how much better is the new code in GEOS?Â

It exhibits the expected improvement in robustness, since a GEOS test which actually depended on a thrownÂ TopologyExceptionÂ (due to the now-removed call toÂ Geometry::intersection()Â ) had to be modified to handle a successful return.

Most importantly, there is a dramatic improvement in performance.Â Here's some numbers from running the GEOS InteriorPointArea performance test:

Data size Time Time
OLD Improvement Time
Centroid
100 .8 ms 86 ms x 100 1 ms
1000 6 ms 144 ms x 24 12 ms
10,000 55 ms 672 ms x 12 107 ms
100,000 508 ms 6,714 ms x 13 961 ms
1,000,000 5,143 ms 73,737 ms x 14 11,162 ms

Some observations:
- The performance test uses synthetic data (sine stars).Â Real-world datasets are likely to show significantly better times ( 80x better in some cases, based on JTS timings)
- The largest improvement is for small geometries, which is nice since these are more common
- InteriorPoint is now actually faster than the Centroid computation.Â This is also good news, since users were often tempted to try and use centroids instead of interior points, despite the known issues.
Future Work
Running the identical performance test in JTS is still faster, by roughly 5x.Â This may be due to the advantages of JIT compilation and memory management.Â It may also indicate there is room for improvement by making GEOS smarter about data handling.
14:00
gvSIG Team: Towards gvSIG 2.5: Improvements at geoprocessing framework
sur Planet OSGeo

The gvSIG Desktop 2.5 version, that you can test with the new distribution candidate to final version, includes a series of improvements in the geoprocess framework that we explain below.Â
Visual improvements
Now when opening the geoprocessing toolbox, you can see that extra information about the layers and fields appears at the interface.

At layer type parameters, you will be able to see the layer name, the name of the View in which it is, if it has an active selection and how many entities are selected. An icon will also appear indicating the type of geometry of the layer, or if it has a selection (with a background yellow circle).

At field type parameters, you can also see information about the type of field. and in the future you will be able to see an icon identifying that field.

Integration with the new plugin to capture coordinates
Last year we released a new extension to capture coordinates more effectively in the View. At the new version, the integration with the geoprocess framework has been completed, so that the points captured with that tool will appear at the selection of the Point type parameter.

New Filter type parameter
As we have told about and as we will explain in the next posts in detail, gvSIG has a new expression generator. In the geoprocessing framework this functionality has been added, so that new geoprocesses can have a new type of parameter that is expression type.

This parameter can greatly improve the execution of a geoprocess by a filter and it is also much more optimal to use than a selection done with the â€˜Selection by attributeâ€™ tool. It can greatly improve the processing of some geoprocesses.

This parameter, according to the geoprocess, could be used for values calculation tasks, filtering, etc.

The expression type parameter is associated to each layer or table type parameter, so that several of these parameters may exist in the same geoprocess. Each time we run the expression generator we will see that this window is associated with the corresponding initial parameter. Now you can start to test all these improvements at the new distribution candidate to final version and if you find any error we encourage you to write about it at the users mailing list. It will help us to fix them.

Â
20 February 2019
14:38
gvSIG Team: Camino a gvSIG 2.5: Mejoras en el marco de geoprocesos
sur Planet OSGeo

La versiÃ³n de gvSIG Desktop 2.5, que ya puedes testear con la nueva candidata a versiÃ³n final, trae una serie de mejoras en el marco de geoprocesos que explicamos a continuaciÃ³n.
Mejoras visuales
Ahora al abrir los geoprocesos, podremos notar que en la interfaz nos aparece informaciÃ³n extra sobre las capas y los campos que antes no tenÃamos.

En los parÃ¡metros de tipo capa, podremos ver rÃ¡pidamente el nombre de la capa, el nombre de la Vista en la que se encuentra, si tiene una selecciÃ³n activa y de cuantas entidades es esa selecciÃ³n. TambiÃ©n aparecerÃ¡ un icono que nos indica el tipo de geometrÃa de la capa o si tiene una selecciÃ³n (con un circulo amarillo de fondo).

En los parÃ¡metros de tipo campo, tambiÃ©n podremos ver informaciÃ³n sobre el tipo de campo que es y a futuro veremos un icono identificativo de dicho campo.

IntegraciÃ³n con el nuevo capturador de coordenadas
El aÃ±o pasado sacamos una nueva extensiÃ³n para capturar coordenadas de manera mÃ¡s efectiva en la Vista. Con la nueva versiÃ³n, se ha completado la integraciÃ³n con el marco de geoprocesos, por lo que los puntos capturados en la herramienta, aparecerÃ¡n en la selecciÃ³n del parÃ¡metro de tipo Punto.

Nuevo parÃ¡metro de tipo Filtro
Como hemos comentado y explicaremos en prÃ³ximos post con mÃ¡s detenimiento, gvSIG tiene un nuevo generador de expresiones. En el marco de geoprocesos hemos aÃ±adido esta funcionalidad para que nuevos geoprocesos puedan tener un nuevo tipo de parÃ¡metro que sea de tipo expresiÃ³n.

Este parÃ¡metro puede agilizar enormemente la ejecuciÃ³n de un geoproceso por un filtro y ademÃ¡s es mucho mÃ¡s optimo de utilizar que una selecciÃ³n realizada con el SelecciÃ³n por atributos, lo que puede mejorar enormemente la velocidad de algunos geoprocesos.

Este parÃ¡metro, segÃºn el geoproceso, podrÃa utilizarse para tareas de cÃ¡lculo de valores, de filtrado, etc.

El parÃ¡metro de tipo expresiÃ³n, va asociado a cada parÃ¡metro de tipo capa o tabla, por lo que en un mismo geoproceso pueden existir varios de estos parÃ¡metros. Cada vez que le demos al generador de expresiones veremos que esa ventana estÃ¡ asociada al parÃ¡metro inicial que corresponde.

Ya puedes comenzar a probar todas estas mejoras en laÂ nueva candidata a versiÃ³n final y si encuentras cualquier fallo o recomendaciÃ³n te animamos a escribirnos a las Listas de correo de gvSIG.

Â
19 February 2019
17:23
Just van den Broecke: Emit #6 â€“ AirSensEUR Calibration
sur Planet OSGeo
This is Emit #6, in a series of blog-posts around the Smart Emission Platform,Â an Open Source software component framework that facilitates the acquisition, processing and (OGC web-API) unlocking of spatiotemporal sensor-data, mainly for Air Quality and other environmental sensor-data like noise.

In Emit #5 â€“ Assembling and Deploying 5 AirSensEURsâ€¦, I described how , with the great help of Jan Vonk from RIVM, we placed five AirSensEURÂ (ASE) air quality stations at the RIVM reference site near the A2 Highway at Breukelen. For about 2.5 months raw data was gathered there while the RIVM station was gathering its data to be used as reference for calibration.

Now â€œcalibrationâ€ is a huge and increasingly important topic when using inexpensive sensors for measuring Air Quality. Within the Smart Emission project we have been applying Artificial Neural Networks to calibrate the gas-sensors within the Josene stations. See also the SE documentation. These sensors were so called metaloxide (MICS) sensors from SGX Sensortech Limited.

The AirSensEURs contain electrochemical sensors from AlphaSense. Several sources like RIVM, state that these sensors are more accurate (than metaloxide sensors), but at the same time need per-sensor calibration.

Within the ASE boxes the following four gas-sensors were applied:
- NO2 (Nitrogen Dioxide): the NO2-B43F, see datasheet.
- NO (Nitric Oxide): the NO-B4, see datasheet.
- O3 (Ozone): the OX_A431, see datasheet.
- CO (Carbon Monoxide): theÂ CO-A4, see datasheet.
The Gang of Four Sensors

The calibration to be applied is based on Regression Analysis. This and other calibration-methods have been investigated and evaluated for many types/brands of sensors by the EC-JRC team. Read all in thisÂ landmark articleÂ and other references there.Â

The complete timeline was as follows. Each phase will be expanded below.
1. Aug 1, 2018 â€“ Okt 9, 2018
  Raw ASE and RIVM reference data collection (Breukelen site)
2. Okt 10, 2018 â€“ Nov 2, 2018
  All ASEs deployed at their target locations
3. Nov/dec 2018
  Calibration performed by Michel Gerboles at the EC-JRC labÂ
4. Jan 2019
  Calibration formulas implemented in Smart Emission (SE) platform
5. Feb 2019
  All ASE calibrated gas-data continuously available via SE viewers/APIs
6. Feb 2019
  Analysis of the calibration (SE Python Stetl) implementation results
ad 1) The five ASE Boxes were mounted on a horizontal pole and connected to WIFI and current. As end-result all boxes were publishing their raw data to the SE InfluxDB Data Collector and were visible in the SE Grafana raw data viewer.

Configured for InfluxDB Data Push visualized via Grafana

Reference values for the gases NO,NO2 and O3 were already continuously available from the RIVM reference station via e.g. the RIVM SOS API. A CO-sensor was added to the station by RIVM. CO-data was collected manually.

ad 2) The picture below shows ASE_NL_01 (left above) through _05 clockwise at their deployment sites. ASE_03 and 04 (right below) were at a single location.

ASE_NL 01 was deployed at an RIVM site in Nijmegen. This allowed us to verify its calibration with different reference data as with which it was calibrated! See below.

ad 3)Â The calibration was performed by EC-JRC (M. Gerboles) using R and ShinyR webapp. All sources can be found in this EC-JRC GitHub repo. This process is quite intricate and a bit hard to explain in the context of a blog-post paragraph. Iâ€™ll try a summary:

Sensor values are digital readings (0..65535). This is effected by the electrical circuitry within each ASE, for optimal gain. To calculate back to mV and nA a per-sensor (brand+type) calculation is required first before applying any regression formula. A bit is explained in the image below.

The second outcome is a per-individual-sensor regression formula. This is for most sensors a linear equation. For O3 (OX_A431) the formula is polynomial, as O3 readings are influenced by NO2 concentration. Below is an example as later implemented in Python using SE Stetl ETL (see below).

The main three outcomes of the calibration are:
- the parameters for digital to nA calculation (per sensor brand+type)
- the linear (polynomial) equations for nA to concentration (ug/m3)
- the per-individual-sensor parameters (a0-a3)
Above some scatterplots made for ASE Box 3 NO2 and O3.

ad 4). Knowing all equations and their parameters from step 3 above, I attempted to integrate this in the continuous ETL within the Smart Emission Platform. Up to now the platform supported only a single sensor station type: the Intemo Jose(ne). As the platform is fed by harvesting raw data from a set of remote APIs provided by Data Collectors, it was relatively easy to add sensor(-station)-metadata and extend the Refiner ETL to apply calibration algorithms driven by that metadata.Â

So for Josene stations the existing ANN calibration would still be applied, while for ASE stations per-sensor linear equations would be performed. All parameterization was already configurable using the Device, DeviceDefs, DeviceFuncs abstractions in the SE Stetl implementation. Recently, to allow stations that already send calibrated values, I introduced the Vanilla Device starting with harvesting Luftdaten.info stations (more in a later post).

The formulaâ€™s as applied in Python SE Stetl are as follows:
```
STEP 1a - Digital to Voltage (V)
V = (Ref - RefAD) + (Digital+1) /2^16 x 2 x RefAD
```
```
STEP 1b - Voltage (V) to Ampere (I) as Ri
I = 10^9 V/(Gain x Rload)
```
```
STEP 2 - Ampere (I) to concentration (ug/m3) - Example 
I=a0+a1*NO2+a2*T
```
```
  ==> NO2Â = (I - a0 - a2 * T) / a1
a0-a2 has specific values for each NO2-B43F sensor.
```
Now that these formulas and their parameters were implemented, near-realtime values could be made visible in all SE apps (viewers) and APIs such as the SmartAppÂ and the Heron Viewer.

Within the Heron Viewer we can compare for example NO2, not only with Josene measurements, but also with official RIVM values.

Also the data is available through all SE OGC APIs, for example the SensorThings API.

ad 6) The moment of truth! How well does the SE-based SE Stetl Python calibration results fit with the original RIVM values? One of the advantages of Data Harvesting (opposed to data push) is that we can switch back in time, i.e. restart harvesting from a given date. Harvesting and continuous calibration was restarted from august 1, 2018, the start of the calibration period at the RIVM station. Using a Grafana panel that displays both RIVM and SE-calculated values we can graphically see how well the data aligns.

What we can see from the above image, is that visually the data aligns very well, here for NO2. The purple graph is the official RIVM measurement. Only station ASE NL 02 is not completely aligned.

To also have some numeric proof and a more objective comparison, I dived in scatterplot and numerical analysis in Python. Apart from scatterplots that show calculated (Y) agains RIVM ref values (X) I calculated the â€œR-squaredâ€ and â€œslopeâ€ for fitting indicator values. This was also my first serious use of Python libs like Scipy, Pandas, Seaborn and Numpy (youâ€™re never too old to become a data-scientist!).

As all SE calibrated data is also stored in InfluxDB with RIVM refdata harvested from their SOS, it was easy to fetch values for the plots/calculations..

Objectivity could be effected since station ASE NL 01 was finally deployed (okt 2018) in Nijmegen, also next to an RIVM station. So the calibration calculations from RIVM refdata in Breukelen could be compared to â€œNijmegenâ€. The implementation for making these scatterplots can be found here. Lets look at some results, mainly for NO2, as I consider this one of the most important AQ indicator gasses.

I like this image a lot as it shows an almost ideal alignment with an R2 of 0.976 and slope of almost 1. Mind: calibration was thus done at a very different site (about 80 km west) and AQ condition (highway) as the deployment (city street).Â

Above are plots for the other gasses as well. First row in Breukelen (no ref CO available in RIVM SOS), front row in Nijmegen. Only NO in Nijmegen is a bit problematic.

To close off: this last image above shows NO2 fit at the Breukelen station for all five ASE boxes. Also quite good.

What to conclude? First of all AirSensEUR is a major step forward in affordable accurate AQ sensing. We hope to expand the community.

AlphaSense NO2 electrochemical sensors appear quite accurate, but calibration requires quite some effort, plus calibration formulas apply per individual sensor. Would automatic per-sensor ANN be less time-consuming and still accurate? Something I would like to investigate.

The Smart Emission project and platform is still going strong, running within a Kubernetes Cloud maintained by Dutch Kadaster.

Next emit will discuss how I integrated data from the amazing Luftdaten.info project for the municipality of Nijmegen.
14:13
gvSIG Team: gvSIG 2.5 RC1 disponible, primera distribuciÃ³n candidata a final
sur Planet OSGeo
Ya estÃ¡ disponible para descargar la primera distribuciÃ³n candidata a final (RC1) de la nueva versiÃ³n gvSIG 2.5.

Esta versiÃ³n puede descargarse desde el apartado de versiones en desarrollo de la web del proyecto.

Las novedades que incluye esta versiÃ³n son mÃºltiples, desde nuevas funcionalidades hasta mejoras en rendimiento y estabilidad. Muchas de ellas pueden ser consultadas ya en los diferentes post que se estÃ¡n publicando en el blog, como pueden ser:
Seguiremos publicando mÃ¡s posts sobre el resto de novedades durante las prÃ³ximas semanas.

Con la publicaciÃ³n de esta primera RC, pretendemos que la Comunidad gvSIG comience a probarla de forma masiva y que nos vayÃ¡is comunicando los errores que detectÃ©is a travÃ©s de las listas de usuarios para corregirlos.

TambiÃ©n estamos preparando en paralelo la versiÃ³n para MAC OS X, cuya versiÃ³n portable, asÃ como las versiones portables de Windows y Linux, esperamos tenerlas en los prÃ³ximos dÃas.
14:12
gvSIG Team: gvSIG 2.5 RC1 available, first release candidate to final version
sur Planet OSGeo
The first release candidate (RC1) of the new gvSIG 2.5 version is now available to download.

This version can be downloaded from the development versions section of the project website.

The novelties included in this version are multiple, from new functionalities to performance and stability improvements. Many of them can be consulted already in the different posts that are being published on the blog, such as:
We will continue publishing more posts about the rest of the novelties during the next weeks.

Publishing this first RC, we intend that the gvSIG Community start to test it in a massive way and that you send us the errors that you detect through the user mailing lists to be fixed.

We are also preparing the version for MAC OS X in parallel, and its portable version, as well as the portable versions for Windows and Linux, will be available in the coming days.
18 February 2019
12:33
gvSIG Team: Towards the new gvSIG 2.5 version: Calling for translators
sur Planet OSGeo

The stabilization phase of the new gvSIG 2.5 version has started, and in order to have the final version with as many languages as possible the update of the translations of the interface are being carried out too.Currently gvSIG has been translated to more than 25 languages, thank to the participation of the Community.

There are two ways of collaboration: updating any of the existing languages, as well as translating gvSIG interface to a new language in which gvSIG is not translated currently.

If you are interested in translating gvSIG interface you can contact the gvSIG Project [info@gvsig.com] and we would send the instructions to do it.

Translations that arenâ€™t finished when the final version is released will be published as a package to be loaded from the gvSIG Add-ons manager. We will inform about these updates at the gvSIG blog.

We expect your collaboration!
12:22
gvSIG Team: Hacia la nueva versiÃ³n gvSIG 2.5: Llamamiento a traductores
sur Planet OSGeo

La nueva versiÃ³n 2.5 de gvSIG Desktop ya se encuentra en fase de estabilizaciÃ³n, para lo cual se ha comenzado tambiÃ©n con la actualizaciÃ³n de las traducciones de la interfaz. El objetivo es el de tener la versiÃ³n final disponible en el mayor nÃºmero de idiomas posible.Actualmente gvSIG se encuentra traducido a mÃ¡s de 25 idiomas, gracias a la participaciÃ³n de la Comunidad.

Existen dos formas de colaboraciÃ³n, bien actualizar cualquiera de los idiomas ya existentes en versiones anteriores, o bien traducir a algÃºn idioma en el que no se encuentre traducido gvSIG actualmente.

Si estÃ¡is interesad@s en traducir la interfaz de gvSIG podÃ©is poneros en contacto con el proyecto [info@gvsig.com], y os indicaremos las instrucciones.

Las traducciones que no estÃ©n finalizadas en el momento de la publicaciÃ³n de la versiÃ³n final se publicarÃ¡n como paquetes que podrÃ¡n ser cargados directamente desde el Administrador de complementos de gvSIG. Iremos informando sobre estas actualizaciones en el blog de gvSIG.

Â¡Esperamos vuestra colaboraciÃ³n!
15 February 2019
12:25
gvSIG Team: Towards gvSIG 2.5: Report by point
sur Planet OSGeo

We are going to show you another novelty of the next version of gvSIG Desktop, that is called report by point. It is a configurable multilayer information button, and it is very useful to consult the information of different layers on a concrete location and visualize it in a simultaneous way.

The operation is very simple, you only have to click on a specific point on the View and a report will be shown in a new window on that point with all the attributes of all visible layers. In that report you can select and copy data to the clipboard, being able to paste them in other applications.

In addition, a new tab has been added to the layer â€œPropertiesâ€, that allows to define which fields you want to see in the report, and even you can modify the field name to be shown.

In the following video you can see how it works. Simple and extremely useful.
11:01
gvSIG Team: Camino a gvSIG 2.5: Informe por punto
sur Planet OSGeo

La novedad que os traemos hoy de la prÃ³xima versiÃ³n de gvSIG Desktop la hemos denominado informe por punto. Viene a ser un botÃ³n de informaciÃ³n multicapa y configurable. Â¡Muy Ãºtil para consultar la informaciÃ³n en un punto de distintas capas y visualizarla de forma simultanea!

El funcionamiento es muy sencillo, pulsamos en un punto determinado de la Vista y se nos mostrarÃ¡ en una nueva ventana un informe sobre ese punto con todos los atributos de todas las capas visibles. En este informe podemos seleccionar y copiar los datos al portapapeles, pudiendo asÃ luego pegarlos en otras aplicaciones.

AdemÃ¡s se ha aÃ±adido una nueva pestaÃ±a a las â€œPropiedadesâ€ de la capa que permite definir que campos queremos que se visualicen en el informe, e incluso modificar el nombre con que aparece el campo.

En el siguiente vÃdeo podÃ©is ver su funcionamiento. Sencillo y extremadamente Ãºtil.
14 February 2019
15:19
gvSIG Team: Free course about Geographic Information Systems applied to archaeology: Certification and links to the complete course
sur Planet OSGeo
The certification of the course about Geographic Information Systems applied to archaeology is now available (this course is also available in Spanish).

This certification starts after publishing the seven modules that form the course, but it will continue open continuously, so that any user can get it at any moment when the modules are finished.

To take the course, that is free of charge, itâ€™s not necessary any registration. You only have to follow the videos of the different modules induicated at the end of this post.

In addition, if you want to get the certification of the course, that is optional, a complete exercise must be completed, which includes some of the contents shown during the course. Likewise, you must have at least 6 of the 9 existing activities correctly, which will validate the knowledge acquired during the course and will be evaluated by a tutor.

Apart from the delivery and passing exercise successfully, the certification will have a minimum cost, necessary to cover the expenses related to the evaluation and certification. This cost will be â‚¬ 25.

The certification will be issued by the gvSIG Association, and will include the Course completion certificate.

The exercise and the cartography to be used at this practical exercise can be downloaded from the following links:
- Practical exercise.
- Cartography.
In the first section of the practical exercise the steps to follow to send it are explained in detail, as well as how to make the payment.

The course is composed of the following modules:
15:11
gvSIG Team: Curso gratuito de Sistemas de InformaciÃ³n GeogrÃ¡fica aplicados a arqueologÃa: CertificaciÃ³n y enlaces al curso completo
sur Planet OSGeo
Ya estÃ¡ disponible la certificaciÃ³n del curso de Sistemas de InformaciÃ³n GeogrÃ¡fica aplicados a arqueologÃa (este curso tambiÃ©n estÃ¡ disponible en inglÃ©s).

Esta certificaciÃ³n se abre tras la publicaciÃ³n de los siete mÃ³dulos que componen el curso, pero seguirÃ¡ abierta de forma continua, por lo que cualquier usuario podrÃ¡ obtenerla en el momento en que finalice los distintos mÃ³dulos.

Para poder realizar el curso, que es gratuito, no es necesario registrarse en ningÃºn portal, solo se deben seguir los vÃdeos de los mÃ³dulos que lo forman, indicados al final de este post.

Por otro lado, si se desea obtener la certificaciÃ³n del curso, que es opcional, se deberÃ¡ completar un completo ejercicio, que incluye algunos de los contenidos impartidos durante el curso. AsÃ mismo, se deberÃ¡ tener correctamente al menos 6 de las 9 actividades existentes en dicho ejercicio, que validarÃ¡ los conocimientos adquiridos durante el curso y serÃ¡ evaluado por un tutor.

Aparte de la entrega y aprobaciÃ³n del ejercicio, la certificaciÃ³n llevarÃ¡ un coste mÃnimo, necesario para cubrir los gastos relativos a la evaluaciÃ³n y certificaciÃ³n. Este coste serÃ¡ de 25 â‚¬.

La certificaciÃ³n serÃ¡ emitida por la AsociaciÃ³n gvSIG, e incluirÃ¡ el Certificado de aprovechamiento del curso.

El ejercicio y la cartografÃa a utilizar en el mismo pueden descargarse desde los siguientes enlaces:
- Ejercicio prÃ¡ctico
- CartografÃa
En el primer apartado del ejercicio prÃ¡ctico se explica con detalle los pasos a seguir para enviar la prÃ¡ctica, asÃ como para la realizaciÃ³n del pago para poder obtener el certificado.

El curso se compone de los siguientes mÃ³dulos:
13 February 2019
14:24
gvSIG Team: Towards gvSIG 2.5: â€œIndigenous mappingâ€ symbol library
sur Planet OSGeo

Not all the novelties of the next gvSIG Desktop version are new functionalities. We added a new symbol library called â€œIndigenous mappingâ€ that contains an interesting set of point symbols developed by â€œThe Ethnographic Mapping Labâ€ of the University of Victoria and designed by the graphic artist James Gray.

The objective of these icons is to represent the set of activities, resources and locations commonly associated with indigenous mapping projects. We hope that they are useful for you.

Its installation and use is very simple, as you can see in the following video:
14:24
gvSIG Team: Camino a gvSIG 2.5: Biblioteca de sÃmbolos â€œIndigenous mappingâ€
sur Planet OSGeo

No todas las novedades de la prÃ³xima versiÃ³n de gvSIG Desktop son nuevas funcionalidades. AÃ±adimos una nueva biblioteca de sÃmbolos denominada â€œ Indigenous mappingâ€ que contiene un interesante conjunto de sÃmbolos puntuales desarrollados por â€œThe Ethnographic Mapping Labâ€ de la Universidad de Victoria y diseÃ±ados por el artista grÃ¡fico James Gray.

El objetivo de estos iconos es representar el conjunto de actividades, recursos y localizaciones comÃºnmente asociadas a los proyectos de mapeo indÃgena. Esperamos que os resulten de utilidad.

Su instalaciÃ³n y uso es muy sencilla, como podrÃ©is comprobar en el siguiente vÃdeo:
12:28
Fernando Quadro: GeoCast Live: OpenStreetMap no apoio ao desastre de Brumadinho
sur Planet OSGeo

No dia 14/02 as 19h acontecerÃ¡ uma live promovida pelo Canal GeoCast (YouTube). Nesta live serÃ¡ possÃvel entender como se deu o esforÃ§o colaborativo de mapeamento da comunidade OpenStreetMap (OSM) na montagem de um mapa base prÃ© e pÃ³s desastre da barragem de rejeitos de minÃ©rio de ferro, da mineradora Vale em Brumadinho-MG, com o intuito de auxiliar no planejamento das buscas e do resgate das vÃtimas, bem como na recuperaÃ§Ã£o a longo prazo da cidade de Brumadinho.

Se vocÃª tem interesse de participar, tirar dÃºvidas, ou simplesmente entender como se deu esse esforÃ§o colaborativo, segue abaixo o link para a live:
8:28
gvSIG Team: Camino a gvSIG 2.5: Guardar y cargar un etiquetado
sur Planet OSGeo

Seguimos con mÃ¡s novedades. En este caso os traemos una pequeÃ±a funcionalidad pero muy Ãºtil. Se trata de la posibilidad de guardar una configuraciÃ³n de etiquetado y poder recuperarla para aplicarla posteriormente.

Cualquier usuario de un SIG sabe que en ocasiones puede conllevar un tiempo considerable definir las caracterÃsticas de un etiquetado; una configuraciÃ³n de etiquetado que no es recuperable para otros proyectos. Y tambiÃ©n puede ocurrir que en un mismo proyecto, a una misma capa, nos pueda interesar aplicarle distintos tipos de etiquetado.

Este tipo de necesidades se cubren con esta nueva funcionalidad que permite guardar la configuraciÃ³n del etiquetado y recuperarla siempre que lo necesitemos.

Os dejamos con una pequeÃ±o demo de su funcionamiento:
8:25
gvSIG Team: Towards gvSIG 2.5: Saving and loading labelling
sur Planet OSGeo

We continue with more novelties. In this case it is a simple functionality, but very useful. This new tool allows to save a labelling configuration, being able to recover it later to apply it.

Any GIS user knows that sometimes it can take a considerable time to define the characteristics of a labelling; a labelling configuration that canâ€™t be recovered for other projects. And sometimes we may be interested in applying different types of labelling in a same project to the same layer.

This type of needs are covered with this new functionality that allows to save labelling configuration and recovering it whenever we need it.

Here you have a short demo of this functionality:

Â
12 February 2019
22:03
Martin Davis: Better and Faster Interior Point for Polygons in JTS/GEOS
sur Planet OSGeo
A humble workhorse of geospatial processing is the ability to compute a point which is guaranteed to lie in the interior of a polygon.Â In the OGC Simple Features for SQL specification (and hence in PostGIS) this is known as ST_PointOnSurface.Â In JTS/GEOS it is called getInteriorPoint, for historical reasons [1].

Interior points for country boundaries
There are some important use cases for this capability:
- Constructing a "proxy point" for a polygon to use in drill-down spatial query.Â This has all kinds of applications:
- Cartographic rendering including:
There is a variety of ways that have been proposed to compute interior points: triangulation, sampling via random or grid points, medial axis transform, etc.Â These all involve trade-offs between location quality and performance [2].Â JTS uses an approach which optimizes performance, by using a simple scan-line algorithm:

JTS Scan-Line Interior Point Algorithm
1. Determine a Y-ordinate which is distinct to every polygon vertex Y-ordinate and close to the centre of the vertical extent
2. Draw a scan line across the polygon and determine the segments of intersection
3. Choose the interior point as the midpoint of the widest intersection segment
Locating a polygon interior point along a scan-line
The current code has been in the JTS codebase since the release of the very first version back in 2001.Â It is elegantly simple, but is quite non-optimal, since it uses the overlay intersection algorithm.Â This is overkill for the computation of the scan-line intersection segments.Â It also has a couple of serious drawbacks: slow performance, and the requirement that the input polygon be valid.Â These are not just theoretical concerns.Â They have been noticed in the user community, and have caused client projects to have to resort to awkward workarounds.Â It's even documented as a known limitation in PostGIS.
Thanks toÂ Crunchy DataÂ recognizing theÂ importance of geospatial,Â we've been able to look into fixing this.Â It turns out that a relatively simple change makes a big improvement.Â The scan-line intersections can be computed via a linear-time scan of the polygon edges.Â This works even for invalid input (except for a few pathological situations).
Interior points of invalid polygons(LH invalid polygon shows suboptimal point placement)
Best of all, it's much faster - providing performance comparable to the (less useful) centroid computation.Â The performance results speak for themselves:

Dataset # polys # points Time Prev
time Improvement
World countries 244 366,951 25 ms 686 ms x 27
Land Cover 64,090 366,951 78 ms 6.35 s x 81

This has been committed to JTS.Â It will be ported to GEOS soon, and from there should show up in PostGIS (and other downstream projects like QGIS, Shapely, GDAL, etc etc).

More Ideas

Some further improvements that could be investigated:
- Use the centroid to provide the Y-ordinate.Â This is probably better in some situations, and worse in others.Â But perhaps there's a fast way to choose the best one?
- Use multiple scan-lines (both vertical and horizontal)
- Provide better handling of short/zero-width scan-line intersections
- Support clipping the interior point to a rectangle.Â This would provide better results for cartographic labelling
[1] JTS was based on the original OGC SFS specification (version 1.1).Â The spec actually does include a method Surface.pointOnSurface.Â The reason for the different choice of name is lost to time, but possibly the reasoning was that the JTS function is more general, since it handles all types of geometry.Â (One of the design principles of JTS is Geometric Uniformity, AKA No Surprises.Â Wherever possible spatial operations are generalized to apply to all geometric types. There is almost always a sensible generalization that can be defined, and it's often quite useful.)

[1a] Also, the acronym IPA is much better than the one for PointOnSurface.

[2] Apparently Oracle has decided to provide blazingly fast performance by simply returningÂ a point on the boundary of the polygon.Â Thus proving the maxim that for every problem there is an solution which is simple, fast, and dead wrong.
12:11
gvSIG Team: Towards gvSIG 2.5: Topology
sur Planet OSGeo

Another important novelty of the next version of gvSIG Desktop is the incorporation of a topology framework.

The topology term refers to the spatial relationships between the different entities of a GIS. These special relationships turn into a set of rules (topological rules) that we can apply to our data. The topological rules that can be applied depend mainly on the types of data that we have. There are rules that are applied to polygon layers, point layers, line layers, to the relationship between a polygon layer and a point layer, etc.

gvSIG Desktop 2.5 will have a topology framework where we have already implemented a first set of rules, but it is prepared to grow unlimitedly, allowing as many new rules to be developed as necessary.

With this topology framework, gvSIG Desktop possibilities to edit and manage cartographic information are greatly increased.

At this video you can see its interface and how it works:

Â
11:54
gvSIG Team: Camino a gvSIG 2.5: TopologÃa
sur Planet OSGeo

Otra de las mÃ¡s importantes novedades de la prÃ³xima versiÃ³n de gvSIG Desktop es la incorporaciÃ³n de un marco de topologÃa.

El tÃ©rmino topologÃa se refiere a las relaciones espaciales entre las distintas entidades de un SIG. Estas relaciones especiales se traducen en un conjunto de reglas (reglas topolÃ³gicas) que podremos aplicar sobre nuestros datos. La reglas topolÃ³gicas que se pueden aplicar dependen principalmente de los tipos de datos que dispongamos. Hay reglas que se aplican a capas de polÃgonos, otras a capas de puntos, otras a capas de lÃneas, otras a la relaciÃ³n entre una capa de polÃgonos y otra de puntos, etc.

gvSIG Desktop 2.5 traerÃ¡ un marco de topologÃa al que ya le hemos implementado un primer conjunto de reglas, pero que estÃ¡ preparado para crecer ilimitadamente, permitiendo que se desarrollen tantas nuevas reglas como sea necesario.

Con la incorporaciÃ³n de este marco de topologÃa se amplÃan enormemente las capacidades de gvSIG Desktop para editar y gestionar la informaciÃ³n cartogrÃ¡fica.

Para que veÃ¡is su interfaz y funcionamiento os dejamos con este vÃdeo:
0:49
Gary Sherman: Leaflet Day 14 - Image Overlay and Wrap-up
sur Planet OSGeo

We end our series with a somewhat trivial, though interesting addition to our map and a special offer. Leaflet allows you to add an image that spans a specified region on the map. Here we add a picture of a little lost moose to the map. In this instance, it serves no purpose other than to show we can do it. The JavaScript code needed is: var imageUrl = "/images/calf_moose.png"; bounds = thetrail.
11 February 2019
11:52
gvSIG Team: Towards gvSIG 2.5: Virtual fields
sur Planet OSGeo

We advance one of the (many) novelties that the next gvSIG Desktop version includes and we think that it will be very useful. This new feature is the virtual fields support (also known as calculated or generated fields).

This fields contain values â€‹â€‹that are calculated when executing a certain formula that the user has defined. And, therefore, their values â€‹â€‹are automatically updated each time there is a change that affects that formula.

For example, in the next video, we can see how a virtual field with population density based on the values â€‹â€‹of two other fields (area and population) can be calculated. When changing any of those two values â€‹â€‹- in the video we can see how the population value is modified â€“ we see how the density is calculated automatically again and it shows the new values.

Another example where the usefulness of these fields is shown is when we create a virtual field that calculates the area of â€‹â€‹the geometries. Each time we modify a geometry graphicallyâ€¦ the polygon area will be updated.

In addition, with the new and powerful formula generator that has been implemented in gvSIG Desktop 2.5 (and which we will discuss in the next post), the possibilities are practically unlimited.
10:29
gvSIG Team: Camino a gvSIG 2.5: Campos virtuales
sur Planet OSGeo

Os adelantamos una de las (muchas) novedades que trae la prÃ³xima versiÃ³n de gvSIG Desktop y que pensamos que va a resultar de muchÃsima utilidad. Se trata del soporte a campos virtuales (tambiÃ©n conocidos como campos calculados o generados).

Este tipo de campos contienen valores que se calculan al ejecutarse una determinada fÃ³rmula que hayamos definido. Y, por tanto, sus valores se actualizan automÃ¡ticamente cada vez que hay algÃºn cambio que afecta a esa fÃ³rmula.

Por ejemplo, en el siguiente vÃdeo, vemos como creamos un campo virtual que calcula la densidad de poblaciÃ³n en funciÃ³n de los valores de otros dos campos: Ã¡rea y poblaciÃ³n. Al cambiar cualquiera de esos dos valores â€“ en el vÃdeo vemos como modificamos la poblaciÃ³n â€“ observamos como de forma automÃ¡tica se calcula de nuevo la densidad y nos muestra los nuevos valores.

Otro ejemplo que os puede permitir ver la utilidad de estos campos: crear un campo virtual que calcule el Ã¡rea de las geometrÃas. Cada vez que modifiquemos grÃ¡ficamente una geometrÃaâ€¦su Ã¡rea estarÃ¡ actualizada.

AdemÃ¡s, con el nuevo y potente generador de fÃ³rmulas que se ha implementado en gvSIG Desktop 2.5 (y del que hablaremos en prÃ³ximos post), las posibilidades son prÃ¡cticamente ilimitadas.
10 February 2019
22:59
Gary Sherman: Leaflet Day 13 - Styling with a Plugin
sur Planet OSGeo

Today weâ€™ll take a look at another pluginâ€”one that allows us to interactively change they style of features on our map: Leaflet.StyleEditor. This illustrates how we can customize our map by changing styles on the fly and also serves as a starting point for even more customization. Installing and Referencing the Plugin The web page for the plugin provides information on installing it. This requires getting the css, js, and image files in the proper location, then referencing them in our HTML file:
22:00
Stefano Costa: Reproducible science per archeologi
sur Planet OSGeo
Il 20 febbraio 2019, a Padova, tengo un workshop su Reproducible science per archeologi dentro il convegno FOSS4G-IT 2019. Avete tempo fino a mercoledÃ¬ 13 febbraio per iscrivervi.
Cosa facciamo
Questo workshop guida i partecipanti nella creazione di una analisi di dati archeologici, secondo i canoni della reproducible science sempre piÃ¹ diffusi a livello internazionale e trasversale.

Utilizzando software di elaborazione ben noti come il linguaggio R e lâ€™ambiente di programmazione RStudio, partiremo da alcuni dataset e affronteremo i vari passaggi analitici che vengono trasposti sotto forma di codice: Ã¨ una procedura pensata per rendere esplicito il processo di ricerca con i suoi meccanismi di tentativi ed errori, secondo il principio della ripetibilitÃ sperimentale.

I partecipanti potranno intervenire attivamente con me nella definizione del percorso e del prodotto finale del workshop, esplorando le pratiche piÃ¹ attuali della open science archeologica diffuse a livello internazionale.

Ci colleghiamo ad altri workshop svolti negli anni scorsi negli USA da Ben Marwick e Matt Harris.
Come iscriversi
Vi potete registrare fino al 13 febbraio 2019 su questa pagina [foss4g-it2019.gfoss.it]

Per lâ€™iscrizione Ã¨ richiesto un pagamento di 10 â‚¬ che vanno a coprire i costi organizzativi dellâ€™evento â€“ non serve a pagare il sottoscritto.
Letture e riferimenti

Per partecipare servirÃ avere installato R, RStudio e se possibile anche Git:
Di seguito qualche link a letture utili per prepararsi al workshop:
09 February 2019
22:39
GIScussions: Never Lost Again
sur Planet OSGeo

Thanks to Ed Freyfogle, I have just finished reading Never Lost Again by Bill Kilday. If you enjoy books about the history of tech and the rollercoaster of a startup in the early part of this century, this is a great read. For me it was a compulsive page turner, partly because I thought that I knew the story and of course I didnâ€™t.

Kilday was the VP Marketing at Keyhole from just about the beginning and he remained with the company after they were acquired by Google and was the marketing lead for both Google Earth and Google Maps through the first part of their explosive growth. This a good chronology of the key events in the creation of Googleâ€™s massive geo-business and also provides some intriguing insights into the the backstory, personalities and the rivalries.

Itâ€™s quite amazing to remember that Google Maps is just 14 years old (launched on 8th Feb 2005). From a team of 30 odd people it has grown to over 5,000, there are over 1 billion users of Google maps each month.

Unless you are as old as me it is difficult to remember how clunky, slow and limited web mapping was before Google and of course the subsequent intersection with â€œsmartâ€ phones started by the iPhone. If you want a peak at what mapping was like before Google you can scroll through my Brief History of Web Mapping talk which I prepared for a post graduate class at Nottingham University.

Today there are only really 3 players left in the game â€“ Google, the collective of businesses delivering services on top of OpenStreetMap (MapBox, Carto et al) and of course Esri â€“ I discounted Apple because I donâ€™t believe their heart is in it for the long term.

For the consumer who wants to find their way to a meeting, a restaurant, a hotel in almost any city in the world or wants to take a peek at a store front on StreetView, there is one solution that they are most likely to turn to â€“ Google Maps. I wonder what the next 10 years will bring?
18:08
Gary Sherman: Leaflet Day 12 - Create a Leaflet Map from QGIS
sur Planet OSGeo

Today weâ€™ll use the qgis2web plugin to export from QGIS to Leaflet. The QGIS project, a location map for the third (in progress) Life on the Alaska Frontier novel, looks like this: Installing qgis2web The qgis2web plugin is installed like any other. Click on the Plugins->Manage and Install Plugins... menu item, click Not installed, and then find qgis2web in the list. Click the Install plugin button to complete the install.
08 February 2019
15:37
Gary Sherman: Leaflet Day 11 - Plugins
sur Planet OSGeo

At its core, Leaflet is designed to be lightweight. That being said, there are hundreds of third-party plugins available to extend and enhance the functionality of your web maps. Today weâ€™ll illustrate adding a plugin to our map from Day 6. The L.Control.ZoomBar plugin adds a custom zoom control that allows us to draw a box around the area we want to zoom to, as well as adding a Home button to return to the initial map view.
07 February 2019
8:02
gvSIG Team: Camino a gvSIG 2.5. Nuevo visor de imÃ¡genes mejorado
sur Planet OSGeo

Entre las numerosas novedades que trae la prÃ³xima versiÃ³n de gvSIG Desktop, hay algunas que sin tener el impacto funcional de otras como el diseÃ±ador de informes o el marco de topologÃa, aportan una mejora funcional considerable. Es el caso del nuevo visor de imÃ¡genes, que podrÃ¡ ser utilizado desde cualquier herramienta que lo requiera, como por ejemplo el hiperenlace a imÃ¡genes.

El anterior visor simplemente mostraba la imagen enlazada a su tamaÃ±o real. Con este nuevo visor podemos visualizar la imagen escalada al tamaÃ±o de la ventana, agrandarla o reducirla e incluso girarla.

Se trata de un visor que ademÃ¡s se ha implementado de forma que puedan aÃ±adirse nuevas herramientas si fuera necesario.

Os dejamos con un pequeÃ±o vÃdeo que muestra el considerable cambio respecto al anterior visor. PequeÃ±as mejoras que hacen mÃ¡s grande a gvSIG Desktop.
8:00
gvSIG Team: Towards gvSIG 2.5. New improved image viewer
sur Planet OSGeo

Among the many novelties that the next gvSIG Desktop version brings, there are some of them that, without having the functional impact of others such as the report designer or the topology framework, provide a considerable functional improvement. This is the case of the new image viewer, which can be used from any tool that requires it, such as the hyperlink to images.

The previous viewer simply showed the image in its original size. With this new viewer users will be able to see the image scaled to the size of the window, enlarge or reduce it and even rotate it.

This viewer has been implemented so that new tools can be added if necessary.

Here you have a short video where this considerable change is shown. Little improvements that make gvSIG Desktop greater.
06 February 2019
17:21
Gary Sherman: Leaflet Day 10 - Adding a Link to a Popup
sur Planet OSGeo

In this post weâ€™ll add a link to the towns popup that will display the satellite view on Google Maps. The API for working with Google Maps URLs can be found here: [https:] To add a link to the town name in the popup, we modify the JavaScript code that creates the towns layer: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 var towns = L.
17:03
EOX' blog: Sentinel-2 cloudless 2018
sur Planet OSGeo

Good news everyone, there is an updated version of the Sentinel-2 cloudless map available! After being first in having processed the whole Sentinel-2 archive to create a cloudless mosaic for 2016 it was time to use our experience and improve [â€¦]
11:30
Fernando Quadro: Dados do IPHAN disponibilizados com o GeoServer
sur Planet OSGeo

O Instituto do PatrimÃ´nio HistÃ³rico e ArtÃstico Nacional (IPHAN) Ã© uma autarquia federal do Governo do Brasil, criada em 1937, vinculada ao MinistÃ©rio da Cidadania, responsÃ¡vel pela preservaÃ§Ã£o e divulgaÃ§Ã£o do patrimÃ´nio material e imaterial do paÃs.

Tem a funÃ§Ã£o de defender e favorecer os bens culturais do paÃs proporcionando sua existÃªncia e usufruto para as geraÃ§Ãµes presentes e tambÃ©m futuras. Buscando a preservaÃ§Ã£o dos tesouros da cultura nacional.

O IPHAN anunciou que disponibilizou seu acervo de dados geogrÃ¡ficos nos formatos WMS e WFS. Os dados foram publicados utilizando o servidor de mapas Geoserver.

Se vocÃª precisa utilizar dados do IPHAN, independente do propÃ³sito, sabia que agora ficou mais fÃ¡cil, basta consumir os serviÃ§os em:

[portal.iphan.gov.br]
11:00
CARTO Inside Blog: State of the Art Styling in CARTO VL
sur Planet OSGeo

CARTO Inside Blog: State of the Art Styling in CARTO VL
7:25
gvSIG Team: Camino a gvSIG 2.5. Plugin para convertir una capa vectorial 2D a 3D a partir de un MDT
sur Planet OSGeo

Se ha publicado un nuevo plugin para instalar en gvSIG que permite convertir una capa vectorial (formato SHP) 2D a 3D a partir de un MDT que ocupe la misma zona.

El plugin estarÃ¡ disponible para la versiÃ³n 2.5 final, pero ya puede descargarse sobre la Ãºltima versiÃ³n final (gvSIG 2.4).

Esta nueva funcionalidad, disponiendo de una capa vectorial en formato .SHP (ya sea de puntos, lÃneas o polÃgonos) en 2D, y de un Modelo Digital de Terreno de la misma zona, convierte la capa vectorial 2D en una capa 3D, tomando las coordenadas Z de dicho rÃ¡ster, y asignÃ¡ndolas como coordenada Z a los elementos de la capa vectorial.

Para instalar este plugin, se debe entrar en el menÃº Herramientas -> Administrador de complementos, y seleccionar la opciÃ³n â€œInstalaciÃ³n por URLâ€. Conectando a la URL por defecto se debe seleccionar la categorÃa â€œGeoprocessâ€ donde habrÃ¡ que marcar el paquete â€œSet Z from rasterâ€œ. InstalÃ¡ndolo y reiniciando gvSIG aparecerÃ¡ el geoproceso en la Caja de herramientas (menÃº Herramientas->Geoprocesamiento), en el apartado Scripting->TransformaciÃ³n.

Para ejecutar este nuevo geoproceso solo se necesita insertar como parÃ¡metros la capa vectorial 2D y la capa rÃ¡ster.
7:21
gvSIG Team: Towards gvSIG 2.5. Plugin to convert a 2D vector layer to 3D from a DEM
sur Planet OSGeo

A new plugin that allows to convert a 2D vector layer (SHP format) to 3D from a DEM located at the same area has been released to be installed on gvSIG.

The plugin will be available for the final gvSIG 2.5 version, but it can be downloaded now to be used on the latest final version (gvSIG 2.4).

This new functionality allows to convert a 2D vector layer into a 3D layer, taking Z coordinates from a Digital Terrain Model on the same area, and assigning them as Z coordinate to the elements of the vector layer. The vector layer has to be a shapefile (it works on points, lines and polygons).

To install this plugin, you must access to Tools -> Add-ons Manager menu, and select the â€œInstall from URLâ€ option. Connecting to the default URL, you must select the â€œGeoprocessâ€ category, and you will have to mark â€œSet Z from rasterâ€ package. After installing it and restarting gvSIG, the geoprocess will appear in the Toolbox (Tools->Geoprocessing menu), in the Scripting->Transform section.

To run this new geoprocess you only need to insert the 2D vector layer and the raster layer as parameters.
05 February 2019
19:22
QGIS Blog: User question of the Month â€“ Febâ€™19 & answers from Jan
sur Planet OSGeo

In January, we wanted to learn more about if and how QGIS users contribute back to the project. We received 299 responses from all over the world:

55% of responders have contributed to the project in the past:

Responders who stated that they had contributed to QGIS were asked to specify what kind of contributions they had provided. This question was multiple-choice. Time contributions are generally more common than financial contributions. 30% of responders helped by creating reproducible bug reports and 24% implemented improvements themselves. The most common financial contribution are personal donations to QGIS.ORG at 17%.

Membership in user groups, contracting developers / documentation writers / translators, or having a support contract with a QGIS support provider are less common amongst responders:

Responders who stated that they had not contributed to QGIS most commonly stated that they didnâ€™t know how to contribute (26%), while lacking financial resources were only raised by 10% of responders:

New question
This month, weâ€™d like to know which plugins you think should be advertised as â€œfeaturedâ€ on the official QGIS plugin repository.

The survey is available in English, Spanish, Portuguese, French, Italian, Ukrainian, Danish, and Japanese. If you want to help us translate user questions in more languages, please get in touch!
15:15
Fernando Quadro: Habilitar camada por serviÃ§o no GeoServer
sur Planet OSGeo

VocÃª sabia que a partir da versÃ£o 2.15 do GeoServer vocÃª pode selecionar em quais serviÃ§os vocÃª deseja que sua camada seja publicada?

E vocÃª faz isso na tela de configuraÃ§Ã£o de camadas, conforme demonstra a figura abaixo:

Fonte: Twitter do Andrea Aime
13:19
GIScussions: #geomob BCN is born
sur Planet OSGeo

Last week I hopped on a plane to Barcelona to hang out with my pal Ed Freyfogle, strategise about the development of his OpenCage Geocoder business (where I am an advisor) and to support him at the launch of geomob in Barcelona.

Barcelona is an awesome city with great food, wonderful walks, beautiful buildings and of course the beach, but I think it is fair to say that the tech scene in general and the geo scene in particular are not as well developed as they are in London. So we were uncertain as to how many people would turn up for the first geomob BCN, in fact before we left for the venue we were â€œmanaging expectationsâ€ â€“ 20/25 would be good for a first meeting â€“ no worries expectations were blown out of the water.

Weâ€™re setting up for #geomobBCN â€“ reminder weâ€™re on the first floor of @Coworkidea pic.twitter.com/ffKb5C12AK
â€” geomob (@geomob) January 30, 2019

At 6pm the room looked pretty large and setting out chairs for about 35-40 people seems optimistic, by 6.30 the room was pretty full and a few minutes late we were off and running. I got my 15 seconds of fame early on as one of the sponsors of the event via my Maps in the Wild project, unfortunately my exquisitely crafted slides had not made it into the final version of the decks that Ed had on his laptop so I had to improvise.

Comencem la #geomobBCN, un nou event de la comunitat GEO de Barcelona. #map @geoinquiets @geomob pic.twitter.com/u4pPnO6OCc
â€” Marc Torres (@marc_torres_) January 30, 2019

Next up was Ed talking about OpenCage and how they supported OSM. If you need a meta-geocoder that is based on open data and uses multiple sources to deliver the best results in reverse and forward geocoding, you should have a look at OpenCage. There were no good pics of Ed speaking so here is one I took the morning after when we were walking and plotting future geomob events and activities.

When you've just plotted global domination for #geomob LDN, BCN, BLN â€¦? pic.twitter.com/GOMPhl08p1
â€” (((Steven Feldman))) (@StevenFeldman) February 5, 2019

Next up was Alexis Battle of Avuxi, whoâ€™s Top Places service is having a big impact on travel booking web sites. I met Alexis and his team a couple of years ago when I was in Barcelona and it is impressive to see how far their business has developed and the range of customers they now serve. They are making headway in analysing sentiment in social media feeds and linking this to location, you will hear more about these guys.

Some of the many travel brands working with @AVUXI #geomobBCN pic.twitter.com/kaoBUOu5ZI
â€” geomob (@geomob) January 30, 2019

Third up was Carla Coll of gotakimaps â€“ I donâ€™t know whether it was a language thing (all the speakers spoke in English which mainly wasnâ€™t their first language) but I didnâ€™t really understand what these guys were doing. Here is what their Crunchbase entry says:

Gotaki Maps is building a decentralized map solution in the Ethereum block chain. Map solutions such as Google Maps and Mapbox are expensive for companies, collect data from users and are centralized. Through state-of-the-art technologies such as Plasma and delegated Proof-of-Stake, the Gotaki Maps network will provide more effective maps for businesses and applications. Network users can contribute to the network and offset their map costs.

Got to admire their ambition!

Next up was Xavi Ruiz, founder of SmartMonkey. They focus on optimising logistics for the last mile of deliveries (local couriers and distributors) using some AI (of course!) to learn from failed deliveries and preferences to ensure the maximum number of completed deliveries. I had some concerns about the privacy risks of this service but perhaps I misunderstood what they were doing with personal data.

Data is good, but whereâ€™s the money? @enedebe of @smartmonkey_io at #geomobBCN pic.twitter.com/RZvLmquSGt
â€” geomob (@geomob) January 30, 2019
I like a slide that asks â€œWhereâ€™s the money?â€

Last up was David Santos, an engineer at Badi who are a star of the Barcelona tech scene and have a neat offer for flat share searchers and renters, sort of long term AirBnB. David talked about the challenges they had with geocoding, why they had gone with Google and why they had then moved to OpenCage. The moment that was greeted with gasps and laughs was when David showed the impact of Googleâ€™s price changes on their business model.

.@dsantosmerino what happened when google raised geocoding pricing #geomobBCN pic.twitter.com/gK3s2Ok3ZU
â€” geomob (@geomob) January 30, 2019

They switched pretty rapidly to using OpenCage after that!

And so the serious part of geomob was over, we finished with about 50 people crammed into the room and it was literally standing room only. Then it was time for the traditional geomob drinks at a local hostelry, the staff struggled a bit with the concept of running a tab but it didnâ€™t stop us drinking plenty of beer, chatting maps and stuff, meeting new people and generally having a good time.

More #geobeers at #geomobBCN pic.twitter.com/WXSmGidfDF
â€” geomob (@geomob) January 30, 2019

#geobeers at #geomobBCN pic.twitter.com/9BgClLLN9p
â€” geomob (@geomob) January 30, 2019

The first geomob BCN was a great success. There are already four speakers lined up for the next event in April, if you want to speak at a geomob BCN or a geomob LDN send a message to Ed.

Oh, you remember that global domination tweet above? Look out for some new activity from geomob over the next few months.
11:02
gvSIG Team: Jornada de presentaciÃ³n MOLAB, el laboratorio de software libre en la AdministraciÃ³n local
sur Planet OSGeo

El prÃ³ximo 7 de febrero a las 10 horas tendrÃ¡ lugar en la sede de MediaLab Prado en Madrid la jornada de presentaciÃ³n de Molab, el laboratorio de software libre en la AdministraciÃ³n local, un evento organizado por el Ayuntamiento de Rivas Vaciamadrid en el que colaboran la Red Innolabs (red de laboratorios de innovaciÃ³n iberoamericanos liderada por NovaGob.Lab y apoyada por el programa CYTED) y MediaLab Prado. La AsociaciÃ³n gvSIG ha sido invitada a participar en sesiÃ³n â€œDe la teorÃa a la prÃ¡ctica: experiencias de usoâ€ donde hablaremos de nuestra experiencia tanto como proyecto tecnolÃ³gico, como de puesta en marcha de un nuevo modelo productivo. Y, por supuesto, de como la Suite gvSIG es un catÃ¡logo de tecnologÃas libres que permite de forma eficiente gestionar toda la informaciÃ³n geogrÃ¡fica de una administraciÃ³n local.

El laboratorio de software libre en la AdministraciÃ³n local es una iniciativa dirigida a Administraciones pÃºblicas, especialmente del Ã¡mbito local, universidades, sociedad civil y sector privado para colaborar en el diseÃ±o de servicios digitales innovadores de alto valor pÃºblico.

AsÃ, la Jornada se presenta como una gran oportunidad para dar a conocer el proyecto, debatir y atraer mÃ¡s participantes a esta comunidad abierta.

La web de la jornada, donde podÃ©is consultar el programa e inscribiros, es:

[https:]]
04 February 2019
18:02
Gary Sherman: Leaflet Day 9 - Calculating Distance with Turf.js
sur Planet OSGeo

Today weâ€™re going to use Turf.js to calculate the distance between any two points along the trail. Turf.js is billed as providing â€œAdvanced geospatial analysis for browsers and Node.js.â€ The distance calculated is a straight line (â€œas the crow fliesâ€) distance rather than actual trail miles. Including Turf.js To calculate the distance we need to include Turf.js. Rather than install it locally, just add this line to the head of your HTML:
17:26
gvSIG Team: The 4th gvSIG Festival is coming
sur Planet OSGeo

For the fourth year running we launch the 4th gvSIG Festival, the online conference in which anyone in the world with an Internet connection can attend or participate as a speaker. The event will be held in March 27^th and 28^th 2019.

This year we want to make a special appeal to the group of women who are part of the gvSIG Community. We would like that a large percentage of the presentations of this 4th Festival are given by you, so we encourage you to present your proposals.

In the gvSIG project we have always wanted to work and contribute our bit in the fight against gender discrimination. In internal debates we have always taken into account that within a movement such as open source software, and the values associated to it, the obvious absence of women should be worrying. And maybe itâ€™s the biggest problem. That should be worrying and it is not.

The sector of open source geomatics, and gvSIG, do not escape these dynamics either. Even significant progress, thereâ€™s an obvious absence of women in our collective. And the worst thing, we not only find that there are only a few initiatives that allow to create spaces to favour their integration, but it seems that it is not necessary.

And even if itâ€™s only a little that we can contribute, we would like to start working on this small step to help to reverse this situation.

gvSIG festivals are open to any presentation related to the project, from anywhere in the world and in any language. From now on, we start the path to the next â€˜4th gvSIG Festivalâ€™.

The information about the proposals submission can be found on the event website: www.gvsig.com/festival
17:15
gvSIG Team: Llega el 4Âº gvSIG Festival
sur Planet OSGeo

Por cuarto aÃ±o consecutivo lanzamos el 4Âº gvSIG Festival, las jornadas on-line en las que cualquier persona del mundo con conexiÃ³n a internet puede asistir o participar como ponente. La fecha, 27 y 28 de marzo de 2019.

Este aÃ±o queremos hacer un llamamiento especial al colectivo de mujeres que forman parte de la Comunidad gvSIG. Nos gustarÃa que un gran porcentaje de las ponencias de este 4Âº Festival fuera impartido por vosotras, por lo que os animamos a presentar vuestras propuestas.

En el proyecto gvSIG siempre hemos querido trabajar y aportar nuestro granito de arena en la lucha contra la discriminaciÃ³n de gÃ©nero. En debates internos siempre hemos considerado que dentro de un movimiento como el del software libre, y los valores que a Ã©l asociamos, la ausencia manifiesta de mujeres deberÃa resultarnos preocupante. Y quizÃ¡ ese es el mayor de los problemas. Que deberÃa ser preocupante y no lo es.

El sector de la geomÃ¡tica libre, y gvSIG, tampoco escapan a estas dinÃ¡micas. AÃºn con significativos avances, hay una ausencia preocupante de mujeres en nuestro colectivo. Y lo que es peor, no sÃ³lo encontramos que casi no existen iniciativas que sirvan para crear espacios que favorezcan su integraciÃ³n, sino que no se ve necesario.

Y aunque sÃ³lo sea un poco lo que podamos aportar, nos gustarÃa comenzar a trabajar dando este pequeÃ±o paso para ayudar a revertir esta situaciÃ³n.

Los Festivales gvSIG estÃ¡n abiertos a cualquier ponencia relacionada con el proyecto, desde cualquier parte del mundo y en cualquier idioma. Desde ya, damos por iniciado el camino al prÃ³ximo â€˜4Âº gvSIG Festivalâ€™.

La informaciÃ³n para el envÃo de propuestas la podÃ©is encontrar en la web del evento: www.gvsig.com/festival
15:05
Markus Neteler: Happy birthday OSGeo!
sur Planet OSGeo

On February 4, 2006 OSGeo held its first meeting in Chicago, with 25 participants representing 18 groups and over 20 different Open Source GIS projects, and 39 others participating via Internet Relay Chat. During the meeting, participants made important decisions in the formation and organization of the foundation, including the name, structure and purpose. The consensus reached in Chicago opened the way for the establishment of a productive and representative foundation.

Today we are happy to announce that the we have meanwhile over 32,800 unique subscribers in the huge list of over 290 OSGeo mailing lists!

And: check out the web site of the OSGeo foundation.
1. More to come this year!

â€¦ see here for the growing list of events

The post Happy birthday OSGeo! appeared first on GFOSS Blog | GRASS GIS and OSGeo News.
15:00
gvSIG Team: Graphical output of an archaeological project: Layouts. GIS applied to Archeology
sur Planet OSGeo

We have reached the end of the course about GIS for Archaeologists, where you are going to learn to create a Layout with the different cartographic elements such as scale, north, legend â€¦ For this you will start from a View of our GIS with archaeological sites cartography.

For all those who finish the course and want to get a certificate, we will publish a post with the instructions for it soon. Stay alert!

We remind you that the data to follow the course can be downloaded in a compressed .zip file from this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find whenÂ carrying out the course, you can use the gvSIG users mailing list.

We hope that this course is useful for you and that allows you to become a regular gvSIG Desktop user. From our part we will continue working to improve this great collaborative project that allows us to have hundreds of thousands of users in more than 160 countries.
Module 7. Graphical output of an archaeological project: Layouts
Previous modules:
Module 1: Preparation of an archaeological project

Module 2: Digitalizing prospection areas

Module 3: Analysis of prospection results: Vector geoprocessing

Module 4: Working with historical maps: Georeferencing images

Module 5: Territorial analysis of archaeological sites: Raster geoprocessing and Digital Elevation Models

Module 6: Hydrological analysis to locate archaeological material or sites
14:00
Paul Ramsey: Dr. JTS comes to Crunchy
sur Planet OSGeo

Todayâ€™s an exciting day in the Victoria office of Crunchy Data â€“ our local staff count goes from one to two, as Martin Davis joins the company!

This is kind of a big deal, because this year Martin and I will be spending much or our time on the core computational geometry library that powers PostGIS, the GEOS library, and the JTS library from which it derives its structure.

Why is that a big deal? Because GEOS, JTS and other language ports provide the computational geometry algorithms underneath most of the open source geospatial ecosystem â€“ so improvements in our core libraries ripple out to help a huge swathe of other software.

JTS came first, initially as a project of the British Columbia government. GEOS is a C++ port of JTS. There are also Javascript and .Net ports (JSTS and NTS).

Each of those libraries has developed a rich downline of other libraries and projects that depend on them. On the desktop, on the web, in the middleware, JTS and GEOS power all of it.

So we know that work on JTS and GEOS on our side is going to benefit far more than just PostGIS.

Iâ€™ve already spent a decent amount of time on bringing the GEOS library up to date with the changes in JTS over the past few months, and trying to fulfill the â€œmaintainerâ€ role, merging pull requests and closing some outstanding tickets.

As Martin starts adding to JTS, I now feel more confident in my ability to bring those changes into the C++ world of GEOS as they land.

Without pre-judging what will get first priority, topics of overlay robustness, predicate performance, and geometry cleaning are near the top of our list.

Our spatial customers at Crunchy process a lot of geometry, so ensuring that PostGIS (GEOS) operations are robust and high performance is a big win for PostgreSQL and for our customers as well.
11:36
Fernando Quadro: Curso de GeoServer â€“ Turma 15
sur Planet OSGeo

Caros leitores,

Quero convidÃ¡-los a participarem do Curso Online de GeoServer que estarei ministrando pela GEOCURSOS. O objetivo do curso Ã© que vocÃª aprenda a disponibilizar, compartilhar e editar dados geogrÃ¡ficos na internet com o GeoServer.

No curso serÃ£o abordados tÃ³picos como: configuraÃ§Ã£o de dados, criaÃ§Ã£o de estilo com SLD, padrÃµes OGC, interface administrativa (web), visualizaÃ§Ã£o cartogrÃ¡fica com OpenLayers, REST API, SeguranÃ§a, entre outros.

O curso ocorrerÃ¡ entre os dias 19 e 28 de marÃ§o (terÃ§as, quartas e quintas) das 20:00 as 22:00 (horÃ¡rio de BrasÃlia).

Aqueles que poderem divulgar para seus contatos, agradeÃ§o. Quem quiser saber mais informaÃ§Ãµes sobre o curso, pode obtÃª-las no site do curso ( [www.geocursos.com.br] ), twitter ( [twitter.com] ) e pelo facebook ( [www.facebook.com] ).
10:23
gvSIG Team: Salida grÃ¡fica de un proyecto arqueolÃ³gico: Mapas. SIG aplicados a ArqueologÃa
sur Planet OSGeo

Llegamos al final del curso de SIG aplicado a arqueologÃa, donde aprenderemos a crear un Mapa con los distintos elementos cartogrÃ¡ficos como escala, norte, leyendaâ€¦Para ello partiremos de una Vista de nuestro SIG con cartografÃa de yacimientos.

Para todos los que acabÃ©is el curso y querÃ¡is obtener un certificado, en breve publicaremos un post con las instrucciones para ello. Â¡Estad atentos!

Os recordamos que los datos para poder seguir el curso los podÃ©is descargar comprimidos en un fichero .zip en este enlace.

Para dudas en el manejo del software, realizaciÃ³n de los ejercicios y problemas que puedan surgir en la realizaciÃ³n del curso, siempre podÃ©is utilizar la lista de usuarios de gvSIG.

Esperamos que hayÃ¡is encontrado Ãºtil este curso y os permita convertiros en unos usuarios habituales de gvSIG Desktop. Por nuestra parte seguiremos trabajando para continuar mejorando este gran proyecto colaborativo que permite que tengamos ya cientos de miles de usuarios en mÃ¡s de 160 paÃses.
Tema 7. AnÃ¡lisis hidrolÃ³gico para localizar materiales o yacimientos arqueolÃ³gicos
Temas anteriores
Tema 1: PreparaciÃ³n de un proyecto arqueolÃ³gico: vistas, capas y tablas

Tema 2: Digitalizar zonas de prospecciones

Tema 3: AnÃ¡lisis de resultados de prospecciones: Geoprocesos vectoriales

Tema 4: Trabajando con mapas antiguos: GeorreferenciaciÃ³n de imÃ¡genes

Tema 5: AnÃ¡lisis territorial de yacimientos: Geoprocesos rÃ¡ster y Modelos Digitales de Terreno

Tema 6: AnÃ¡lisis hidrolÃ³gico para localizar materiales o yacimientos arqueolÃ³gicos
02 February 2019
20:28
Martin Davis: Joining Crunchy Data to work on PostGIS
sur Planet OSGeo
I'm happy to announce that I am taking a position with Crunchy Data as a Senior Geospatial Engineer.Â I'm working alongside fellow Victorian geospatial maven extraordinaire Paul Ramsey, as the core of a proposed Geospatial Data Centre of Excellence.

Our mission statement is simple:Â make PostGIS bigger, better, faster!
- Bigger - more spatial algorithms and functions
- Better - enhance existing functionality to make it easier to use, more powerful, and more robust
- Faster - keep looking for algorithmic optimizations and ways to use the power of Postgres to make spatial processing faster
A lot of this work will involve enhancements to the core GEOS geometry library.Â Part of the goal is to keep JTS and GEOS aligned, so this should produce a nice boost to JTS as well.
Having been lurking in the background for many years now, I'm stoked to be (finally) able to work directly on PostGIS.Â And I'm excited to be part of the Crunchy team. They have some of the leading Postgres experts in-house, so I'm expecting that it will be a great learning experience.Â And their client list promises to expose us to some fascinating large-scale use cases for spatial data processing, which can only be good for the power and robustness of PostGIS.
I'm also looking forward to re-engaging with the geospatial open source community, and learning more about the (even bigger) open source Postgres community.Â Great things lie ahead!
14:57
Free and Open Source GIS Ramblings: Movement data in GIS #20: Trajectools v1 released!
sur Planet OSGeo
In previous posts, I already wrote about Trajectools and some of the functionality it provides to QGIS Processing including:
There are also tools to compute heading and speed which I only talked about on Twitter.

Trajectools is now available from the QGIS plugin repository.

The plugin includes sample data from MarineCadastre downloads and the Geolife project.

Under the hood, TrajectoolsÂ depends on GeoPandas!

If you are on Windows, hereâ€™s how to install GeoPandas for OSGeo4W:
1. OSGeo4W installer: install python3-pip
2. Environment variables: add GDAL_VERSION = 2.3.2 (or whichever version your OSGeo4W installation currently includes)
3. OSGeo4W shell: call C:\OSGeo4W64\bin\py3_env.bat
4. OSGeo4W shell: pip3 install geopandas (this will error at fiona)
5. FromÂ [https:]] : download Fiona-1.7.13-cp37-cp37m-win_amd64.whl
6. OSGeo4W shell: pip3 install path-to-download\Fiona-1.7.13-cp37-cp37m-win_amd64.whl
7. OSGeo4W shell: pip3 install geopandas
8. (optionally) FromÂ [https:]] : download Rtree-0.8.3-cp37-cp37m-win_amd64.whl and pip3 install it
If you want to use this functionality outside of QGIS, head over to my movingpandas project!

Data size	Time	Time OLD	Improvement	Time ST_Centroid
5,658 polygons (2,171,676 vertices)	341 ms	4,613 ms	x 13	369 ms

Data size	Time	Time OLD	Improvement	Time Centroid
100	.8 ms	86 ms	x 100	1 ms
1000	6 ms	144 ms	x 24	12 ms
10,000	55 ms	672 ms	x 12	107 ms
100,000	508 ms	6,714 ms	x 13	961 ms
1,000,000	5,143 ms	73,737 ms	x 14	11,162 ms

Dataset	# polys	# points	Time	Prev time	Improvement
World countries	244	366,951	25 ms	686 ms	x 27
Land Cover	64,090	366,951	78 ms	6.35 s	x 81

Sauter à la page: 1 2 3 ... 13

Communauté	Ressources	L'emploi	Le marché	L'association	Fils RSS
Forum Blogs Wiki Planet Carte des membres Sites amis	Annuaire Agenda Biblio Netvibes Fiches AMO-CNIG Paris PCGIS Téléchargements	Offres d'emploi Banque de CV Carte des CV Formations Démarche Métiers	Geo-Entreprises Geo-Communiqué Appels d'offres	L'association Qui sommes-nous ? Nous aider Bienfaiteurs Partenaires Historique Statuts	Tout le site Job Géomatique Services GeoBlogs ...	Faire un don Mentions légales

Le portail francophone de la géomatique

Canaux

Planet OSGeo