Welcome to Planet OSGeo

November 26, 2015

gvSIG Team

gvSIG se gradúa como proyecto OSGeo


gvSIG se ha graduado como proyecto OSGeo (the Open Source Geospatial Foundation), cumpliendo todos los requisitos de calidad exigidos por OSGeo para obtener esta calificación.

Desde la Asociación gvSIG queremos agradecer el esfuerzo de todos los que han participado en este proceso de incubación, tanto desde el equipo gvSIG como desde OSGeo, y especialmente a nuestro mentor Dimitris Kotzinos.

Por otro lado esperamos aportar no solo un buen software, sino también la experiencia de poner en marcha un nuevo modelo de negocio y de sostenibilidad basado en el conocimiento compartido, la solidaridad y la colaboración de pequeñas y medianas empresas a lo largo del planeta. Demostrando que es posible un modelo de negocio basado en tecnologías con licencias como la GPL, adoptada por gvSIG o gvNIX, y que dan las máximas libertades al usuario, es decir, las máximas garantías a los clientes.

Os dejamos con la nota oficial emitida por OSGeo:

OSGeo is pleased to announce that the gvSIG project has graduated from incubation and is now a full fledged OSGeo project. Manuel Madrid, a long time member of the gvSIG Project Steering Committee (PSC), has been appointed as project officer.

gvSIG is an Open Source desktop application designed for capturing, storing, handling, analyzing and deploying any kind of referenced geographic information in order to solve complex management and planning problems. gvSIG is known for having a user-friendly interface, being able to access the most common formats, both vector and raster ones. It features a wide range of tools for working with geographic-like information (query tools, layout creation, geoprocessing, networks, etc.), which turns gvSIG into the ideal tool for users working in the land realm.

Graduating incubation includes fulfilling requirements for open community operation, a responsible project governance model, code provenance, and general good project operation. Graduation is the OSGeo seal of approval for a project and gives potential users and the community at large an added confidence in the viability and safety of the project.

The project steering committee says, “The gvSIG team is thrilled to be recognized as a full OSGeo project. There have been strong ties between the two communities with common objectives to spread open source for geomatics, and develop a business model based on collaboration and shared knowledge. We are very happy to be included as part of OSGeo and a member of such an esteemed group of projects”.

OSGeo would also like to thank Dimitris Kotzinos, Jeroen Ticheler and Jorge Sanz for their assistance during this Incubation process.

Congratulations to the gvSIG community!

Filed under: community, gvSIG Desktop, opinion, press office, spanish Tagged: graduación, incubación, osgeo

by Alvaro at November 26, 2015 06:36 PM

GeoSpatial Camptocamp

14ème Rencontre Développeurs de QGIS aux Îles Canaries

Camptocamp était présent au 14ème Hackfest de QGIS qui s'est déroulé à l'Université de Las Palmas, aux Îles Canaries du 5 au 8 Novembre 2015.

Cet article 14ème Rencontre Développeurs de QGIS aux Îles Canaries est apparu en premier sur Camptocamp.

by Yves Jacolin at November 26, 2015 03:58 PM


20 minutes of #AISHub TCP #AIS flow around #Majorca #Spain provides 1 msg/min/ship

20 minutos de conexión a AISHub alrededor de Palma de Mallorca. Un mensaje por minuto y buque:

by jldominguez at November 26, 2015 03:54 PM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (VI y final)

Una vez visto en post anteriores como crear rutas, calibrarlas, y generar la segmentación dinámica, en este último post de la serie veremos como mostrar y limpiar medidas.

Mostrar medidas

Esta herramienta permitirá la representación gráfica de la coordenada M. Para que la herramienta esté habilitada, la capa activa de la Vista debe ser una capa de lineas compuestas por puntos con coordenadas M. Dicha capa debe tener algún elemento seleccionado.

Al activar la herramienta, se muestra un cuadro de diálogo que permite introducir la distancia a la que deben mostrarse los puntos kilométricos.


Tras aceptarlo, gvSIG mostrará puntos en la ruta a las distancias definidas y una etiqueta con la coordenada M de dicho punto. El formato de dicha etiqueta será “# + ###”. Así, el punto kilométrico 2,350 se etiquetará como “2 + 350”.


Esta herramienta muestra los resultados en la vista sin alterar en modo alguno los datos de las rutas involucradas.

Limpiar medidas

Esta herramienta sirve para borrar de la Vista las medidas que previamente se hayan mostrado con la herramienta anterior.

El usuario puede haber ejecutado la herramienta de mostrar medidas cuantas veces y sobre cuantas rutas quiera, quedando esas medidas en la Vista e imposibilitando, tal vez, la correcta interpretación de los datos. Al activar esta herramienta se limpia la Vista de dichas medidas.

Post relacionados:

Filed under: gvSIG Desktop, spanish Tagged: carreteras, gvSIG 2.3, Segmentación dinámica, Sistema de referencia lineal

by Alvaro at November 26, 2015 11:50 AM

November 25, 2015

Free and Open Source GIS Ramblings

How to create connectivity-based line caps

It’s been a while since my last blog post mostly because I’ve been busy with some more long form writing. Most notably, I’ve been writing a paper on the QGIS Projcessing framework in the open access ISPRS International Journal of Geo-Information together with Victor Olaya and I’m still in the process of writing a new book titled “QGIS Map Design” together with Gretchen Peterson which is scheduled for early 2016.

Today’s post has been on my todo list for a while now. It’s inspired by a talk at a recent cartography conference I attended:

(For a summary of the whole event, check the storify I compiled.)

The idea of this slide and several more was to show all the attention to detail which goes into designing a good road map. One aspect seemed particularly interesting to me since I had never considered it before: what do we communicate by our choice of line caps? The speaker argued that we need different caps for different situations, such as closed square caps at the end of a road and open flat caps when a road turns into a narrower path.

I’ve been playing with this idea to see how to reproduce the effect in QGIS …

So first of all, I created a small test dataset with different types of road classes. The dataset is pretty simple but the key to recreating the style is in the attributes for the road’s end node degree values (degree_fro and degree_to), the link’s road class as well as the class of the adjacent roads (class_to and class_from). The degree value simply states how many lines connect to a certain network node. So a dead end as a degree of 1, a t-shaped intersection has a degree of 3, and so on. The adjacent class columns are only filled if the a neighbor is of class minor since I don’t have a use for any other values in this example. Filling the degree and adjacent class columns is something that certainly could be automated but I haven’t looked into that yet.



The layer is then styled using rules. There is one rule for each road class value. Rendering order is used to ensure that bridges are drawn on top of all other lines.


Now for the juicy part: the caps are defined using a data-defined expression. The goal of the expression is to detect where a road turns into a narrow path and use a flat cap there. In all other cases, square cap should be used.


Like some of you noted on Twitter after I posted the first preview, there is one issue and that is that we can only set one cap style per line and it will affect both ends of the line in the same way. In practice though, I’m not sure this will actually cause any issues in the majority of cases.

I wonder if it would be possible to automate this style in a way such that it doesn’t require any precomputed attributes but instead uses some custom functions in the data-defined expressions which determine the correct style on the fly. Let me know if you try it!

by underdark at November 25, 2015 06:52 PM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (V)

Una vez visto en post anteriores como crear rutas y calibrarlas, veamos la herramienta disponible para generar la segmentación dinámica.

Esta herramienta permite la generación de nuevas capas de información a partir de una geocodificación referida al sistema de referencia lineal. Por ejemplo, la ubicación de accidentes referidos a una carretera y pk o la representación de aforos o intensidades medias de tráfico en función de tramos kilométricos.

Para la ejecución de esta herramienta es necesario partir de una capa de rutas calibradas y de una tabla con columnas que indiquen puntos kilométricos y columnas con otros valores.

Al activar la herramienta muestra un cuadro de diálogo con los siguientes componentes:

  • Capa de rutas” para seleccionar la capa de rutas calibradas.
  • Identificador de ruta” para seleccionar el campo de la tabla de la capa de rutas calibradas que contiene el identificador de la ruta.
  • Tabla de valores” para seleccionar la tabla con valores.
  • Identificador de ruta en la tabla” para seleccionar el campo de la tabla de valores que contiene el identificador de la ruta. Si no se selecciona, bien porque no existe en la tabla bien porque no se desea, se aplicarán todos los valores a la salida para cualquier ruta seleccionada.
  • pk / pk inicial” para indicar el campo que contendrá los puntos kilométricos iniciales de cada tramo.
  • pk final” para indicar el campo que contendrá los puntos kilométricos finales de cada tramo.
  • valor” para indicar el campo que contendrá los valores que se desean representar.
  • Capa de salida” para introducir la capa en la que se van a guardar los resultados.

Al aceptar este diálogo, se generará una nueva capa con las siguientes características:

  • Si se han seleccionado los dos campos “pk inicial” y pk final”, la capa de salida será una capa de líneas con las rutas de la capa original separadas en los tramos indicados por estos campos.
  • Si solo se ha seleccionado el campo “pk inicial”, la capa de salida será una capa de puntos posicionados en los puntos kilométricos indicados por ese campo.
  • En la tabla asociada a capa de salida se añadirán las siguientes columnas:
    • matrícula” o el nombre de la columna de la tabla de la capa original donde este el identificador de ruta.
    • pk”, si la capa de salida es de puntos, o “pk inicial” si es de lineas.
    • pk final” si la capa de salida es de líneas
    • valor” o el nombre de la columna de la tabla de valores donde esté el valor que se ha querido representar.

Posteriormente ya se podrá aplicar cualquiera de las simbologías de las que dispone gvSIG para las capas de líneas.

Si, previamente a la ejecución de la herramienta, la capa de origen tenía una selección solo se realizará este proceso sobre las rutas seleccionadas.

En la siguiente imagen se puede ver un ejemplo de una capa de lineas generada por segmentación dinámica (usando los atributos de la tabla ID como identificador de rutas, DESDE como pk inicial, HASTA como pk final y VALOR como valor) a la que se le ha aplicado una simbología de valores únicos según el atributo “VALOR”.


Y en la siguiente imagen se puede ver un ejemplo de una capa de puntos generada por segmentación dinámica (usando los atributos de la tabla ID como identificador de rutas, DESDE como pk y VALOR como valor) en la que se le ha aplicado un símbolo único de punto (azul y 8 píxeles de tamaño) y una leyenda que muestra el valor del atributo “VALOR”.


Una vez termine el proceso, que será indicado con un diálogo con una barra de progreso, gvSIG facilitará al usuario la carga de la capa generada en la vista activa.

Post relacionados:

Filed under: gvSIG Desktop, spanish Tagged: carreteras, gvSIG 2.3, Segmentación dinámica, Sistema de referencia lineal

by Alvaro at November 25, 2015 09:34 AM

November 24, 2015

gvSIG Team

On the road to gvSIG 2.3: Dynamic Segmentation / LRS (I)


We are working in the stabilization of the next gvSIG version, which will bring important changes both on developer and user sides. It is time to start a series if posts that let us introduce you all the new features that we are going to find in gvSIG 2.3.

One of the main new features is that so called “Dynamic Segmentation” which is related to the management of network infrastructures (roads, railways, tracks, electricity, water, etc.).

Dynamic Segmentation, also known as Linear Reference System (LRS), is a spatial reference method in which the positions of the elements are referred to measurements along a linear element.

The information related to elements such as roads don’t use coordinates of a reference system (X,Y or Latitude, Longitude) but milestones. A Milestone is one of a series of numbered markers placed along a road or boundary at intervals, usually of one unit (i.e. mile or kilometer).

For instance we may indicate that, in a given road, there is an accident in the milestone 17.300 or a traffic jam between the milestones 6 and 12. The use of this reference system based on milestones is known as dynamic segmentation. The position of an element in this reference system is known as M coordinate.

For example, for the management of roads and all its elements (traffic signs, accidents, capacity, intensity, etc.) it is very important that the GIS software is able to generate dynamic segmentation.

This ability involves a set of tools that let define routes, calibrate each route from the milestones, edit the M coordinate of an element, depict it and generate new layers that support dynamic segmentation.

In short, with these new tools we’ll be able to convert a road layer containing X,Y coordinates in a linear reference system based on milestones or, in other words, to subdivide that road by its milestones. As a result the roads are converted in polylines containing an M coordinate.

Along this post series we’ll let you know the improvements that this new add-on.

These are the tools included in the plug-in:

  • Generate routes
  • Calibrate routes
  • Edit the calibration of a route
  • Generate dynamic segmentation
  • Show measurements
  • Remove measurements

For a proper operation of theses tools a new implementation of the geometries library has been included in gvSIG, which allows to add a measurement to each of the vertexes of a geometry. These tools allow to manage that measurements.

Filed under: english, gvSIG Desktop Tagged: Dynamic Segmentation, gvSIG 2.3, Linear Reference System, LRS, roads

by Alvaro at November 24, 2015 01:57 PM

gvSIG Team

A vueltas con el Cambio de Modelo Productivo


Sectores Estratégicos, las TIC y el Siglo XXI; la Geomática, gvSIG y las infraestructuras de Datos Espaciales; Estándares, Software libre, Compartir y Colaborar; la Neutralidad la Independencia y la Soberanía Tecnológica; y como no, el cambio del Modelo Productivo.

De cuantas cosas oímos hablar. Cuantos conceptos, cuantas etiquetas, cuantas buenas intenciones.

Sobre el papel dudo que nadie vaya a negar la relevancia de las TIC en la actualidad hasta el punto de considerarlas como el sector estratégico del Siglo XXI, y es que hoy en día no podemos imaginar proceso productivo, económico, académico o social donde las TIC no sean parte fundamental del mismo. Pero la duda es. ¿Somos conscientes de lo que esto implica?

Supongo que tampoco encontraremos a mucha gente que dude sobre la relevancia que tiene para cualquier organización; sea una nación, una administración o una empresa, tener el control sobre sus sectores estratégicos. Es decir, tener el control sobre la Tecnología y no que la Tecnología, o mucho peor, sus propietarios, te controlen a ti. Y sigo con la misma duda. ¿Somos conscientes de lo que esto implica?

A poco que conozcamos mínimamente el sector, no creo que nadie dude de la potencialidad de la incorporación de la componente Geo en nuestros Sistemas de Información. En un mundo donde la realidad se manifiesta en el Territorio, herramientas que nos permitan gestionar el territorio, son herramientas que nos permiten gestionar la realidad. Hablamos de la Geomática.

Si le damos ya un poco de rienda suelta a la imaginación, podemos pensar en la tradición de Siglos del Progreso Científico, donde los principales avances se han producido gracias a que los gigantes de la Ciencia han podido avanzar a partir de los estudios y conclusiones de sus homólogos. Hablamos de Compartir el conocimiento. Hablamos de Colaborar para la obtención de soluciones. Compartir y Colaborar, valores intrínsecos al Software Libre. Software Libre como herramienta de progreso tecnológico.

Y vamos, me juego mil licencias de gvSIG a que no hay nadie que esté leyendo esto que no haya oído hablar del Cambio del Modelo Productivo. Tantos años como llevamos hablando de Crisis son años que llevamos hablando de Cambio de Modelo Productivo, de abandonar los sectores burbuja para apostar por el mencionado cambio donde sin lugar a duda las TIC y el I+D+i han de jugar un papel fundamental.

Veamos, umh… Las TIC como Sector Estratégico, subir a hombros de gigantes (colaborar y compartir, valores del Software Libre), la potencialidad de la Geomática y gvSIG, proyecto en torno al cual se ha construido una auténtica referencia internacional en el campo de la Geomática como es la Asociación gvSIG. ¿De aquí podemos sacar conclusiones que nos ayuden a convertir en realidad esto del Cambio del Modelo Productivo? ¿Alguna oportunidad delante de nuestra cara?

Ideas a compartir y debatir en las #11gvSIG, un año más unas jornadas organizadas por la Asociación gvSIG donde todo esto no es un sueño. Es más, no solamente es posible, sino que además, Es real.

Pd. Para los olvidadizos. No es la Neutralidad, Es la Independencia, Sonámbulos

Filed under: opinion, spanish

by Gabi at November 24, 2015 12:06 PM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (IV)

Continuamos con las novedades en gvSIG 2.3 relacionadas con Segmentación dinámica. En este post veremos la herramienta que permite editar la calibración de una ruta.

Esta herramienta permite la edición de coordenada M de una geometría, ya sea mediante la introducción manual de dicha coordenada en cada uno de los puntos, ya sea introduciendo un rango de valores (inicial y final) sin necesidad de tener una capa de calibración de puntos.

La herramienta se habilita cuando la capa activa de la Vista es una capa de líneas con geometrías con coordenada M y está en edición. Al activar esta herramienta se muestra un cuadro de diálogo en el que el usuario debe seleccionar el campo que se corresponde con el identificador de la ruta.


Una vez seleccionado el atributo que contiene los identificadores de las rutas y aceptado el diálogo, se mostrará otra ventana para introducir el resto de los parámetros de la herramienta.


Esta ventana contiene:

  • Una tabla con las columnas:
    • Identificador de ruta”
    • Punto” con el orden del vértice en la ruta
    • X” con la coordenada X del punto
    • Y” con la coordenada Y del punto
    • M” con la coordenada M del punto
  • Id”, para indicar el identificador de la ruta que se va a modificar. Contiene todos los identificadores de las rutas seleccionadas (si no hubiera selección se rellenará con todos los de la capa).
  • Mínimo”, para indicar el valor que tomará el vértice cuyo orden sea 0.
  • Máximo”, para indicar el valor que tomará el vértice cuyo orden sea el máximo.
  • El usuario puede intercambiar los valores de los cuadros de texto “Mínimo” y “Máximo” pulsando el botón “Invertir”.
  • Al pulsar el botón de “Aplicar” se recalcularán los valores de la coordenada M de la tabla según los valores de los cuadros “Mínimo” y “Máximo” introducidos.

Cuando el usuario seleccione un “Id”, se rellenará la tabla con los valores de los puntos de las geometrías de los elementos de la capa cuya “Id” se corresponda. Para ayudar al usuario, al seleccionar un Id concreto, aparecerá la ruta correspondiente dibujada en amarillo en la vista.

El usuario podrá editar manualmente uno o varios de los valores de la M en la tabla. Para ayudar al usuario, cada vez que seleccione una o más filas de la tabla, se dibujará un punto de color rojo en la vista en la posición de las coordenadas correspondientes al vértice que se está editando.


Si en lugar de editar a mano alguno de los puntos preferimos que la herramienta los calcule partiendo de un rango de valores y de los valores antiguos, se puede hacer modificando los valores en los cuadros de texto “Mínimo” y “Máximo”. Cuando se pulse el botón “Aplicar” se recalcularán los valores M de la tabla.

Al aceptar esta ventana, la herramienta hará una comprobación de que los valores de la M forman una secuencia ordenada, si hay valores repetidos o si hay valores negativos. Esto valores pueden ser correctos, pero le da la opción al usuario de poder echarse atrás antes de guardar los cambios.

Al aceptar este diálogo se persistirán los valores de los campos M en los puntos de la ruta, pero no será hasta que salga de edición de la capa aceptando los cambios que se persistan definitivamente en la capa.


Post relacionados:

Filed under: gvSIG Desktop, spanish Tagged: carreteras, Segmentación dinámica, Sistema de referencia lineal

by Alvaro at November 24, 2015 08:59 AM


FOSS4G NA 2016 Call for Proposals and Sponsors

For those who are unaware. Free and Open Source 4 GIS North America (FOSS4G NA 2016) will be happening in Raleigh, NC May 2-5th 2016. We are accepting proprosals now. Early Bird proposal deadline is January 22nd, 2016. Which means if you submit early, you'll get a notification early before the February 8th, 2016 deadline.

Unlike last year where decisions were made entirely by the program committee, we will have users voting for presentations similar to what has been done for many FOSS4G international.

We are also looking for Sponsors, so if you'd like to sponsor the event in some way, please refer to our Sponsor Prospectus page.

by Regina Obe (nospam@example.com) at November 24, 2015 08:07 AM

November 23, 2015

Juergen Weichand

New Geometry Exporter Plugin for QGIS

I’ve just released the new experimental plugin Geometry Exporter for QGIS. The plugin displays the geometry of a selected feature as text. Thanks to GDAL, the following formats are currently supported: WKT, EWKT, GML2, GML3, GeoJSON. Also on-the-fly conversion (e. g. Envelope, Centroid, ConvexHull, Boundary) and transformation (changing Coordinate Reference System) are supported.



by Jürgen Weichand at November 23, 2015 06:58 PM

GIS for Thought

The Great Polish Map of Scotland Revisited

A lot of progress has been made since my last visit: Visiting the Great Polish Map of Scotland

This time I had a bit more time, staying overnight with the very accomodating girlfirend at the Barony Castle Hotel. The steak was excellent, but the sauna was not very hot. Overall a good experience though.




As you can see from the photos restoration works are in full progress.


And dontains can be made to the worthy cause at: MapaScotland.org


For a view of the way up to the map, see my first post on Mapillary:

by Heikki Vesanto at November 23, 2015 11:00 AM

gvSIG Team

#11gvsig: gvSIG applied to town planning (Workshop)


After the successful reception of the “gvSIG applied to town planning” workshop in the gvSIG LAC Conference and gvSIG Perú Conference, we think it would be interesting to offer it in the International gvSIG Conference.

The workshop will take place on Friday 4th December from 12:00am to 14:00pm

The town planning is one of the areas where potentially GIS software is an essential tool. However, we know that its use is not usual, basically because of the unknowledge of these technologies and also, for the high cost of the privatives licences.

The projects related to town planning handle and analyse a high volume of information, the most part of it has a cartographical representation. The correct analysis of this information from a spatial point, it can be the key for the decision making and for the design of projects of town planning.

At the same time, from the design of the new projects, the real impact of them can be analysed.

This workshop will be to introduce you to the possibilities of the Geographic Information Systems in the town planning area. To do that, and through some case studies and thanks to the gvSIG open source software, a simulation of a town planning project will be made in a headquarter of the city Valencia.

Some characteristics will be analysed: population density, noise map, tree density,… as a preliminar study. After that and having a project proposal, a simulation of the changes in the population will be realised.

Through case studies, the most significant tasks of gvSIG will be covered, including edition, creation of thematic maps and some geoprocesses.

There is no need of previous knowledge of gvSIG to attend to this workshop.

Anyone interested in following it with its computer, must have installed the last version of gvSIG (gvSIG 2.2) and downloaded the data to use in the Friday´s morning workshops.

Just remind you that the workshops are free of charge , as all the activities of the Conference. If you are interested, you need to fill the application form for the Conference at:


Filed under: english, events, gvSIG Desktop, training

by mjlobato76 at November 23, 2015 09:56 AM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (III)

En el tercer post sobre el nuevo complemento de segmentación dinámica, vamos a ver el funcionamiento de la herramienta que permite Calibrar Rutas.

Esta herramienta permite asignar la información de puntos kilométricos a una ruta, es decir geocodificar elementos de esa carretera a partir de sus pk’s.

Para realizar la calibración se requieren dos capas de información, la de rutas, obtenida con la herramienta de creación de rutas y una capa de puntos de calibración (pk’s) con el identificador de la ruta y un atributo que indique el valor de la medida.

La herramienta se habilita cuando la Vista activa contiene una capa de líneas con geometrías con coordenada M y una capa de puntos.

Al activarla, se muestra el siguiente cuadro de diálogo en el que el usuario puede introducir los parámetros necesarios para su funcionamiento.


El usuario podrá indicar:

  • Origen, la capa de rutas de entrada. Mostrará la lista de capas de líneas con coordenadas M que estén cargadas en gvSIG
  • Campo de identificadores de ruta, el campo de la tabla de la capa de rutas que contiene el identificador de la ruta. Mostrará la lista de atributos de la tabla correspondiente a la capa seleccionada en “Capa de rutas”.
  • Capa de puntos de calibración, la capa de puntos de calibración de entrada. Mostrará la lista de tablas de puntos que estén cargadas en gvSIG y que tengan algún atributo numérico.
  • Identificador de ruta en la capa de puntos, el campo de la tabla de la capa de puntos de calibración que contiene el identificador de la ruta. Mostrará la lista de atributos de la tabla correspondiente a la capa seleccionada en “Capa de puntos de calibración”.
  • Campo desde o longitud, el campo de la tabla de la capa de puntos de calibración que contiene los valores de las medidas. Mostrará la lista de atributos de la tabla correspondiente a la capa seleccionada en “Capa de puntos de calibración”.
  • Fichero de salida, archivo en el que se desea que se guarden los resultados.
  • Método de cálculo de mediciones. Permite seleccionar entre Distancia (Las mediciones serán recalculadas utilizando la distancia más corta entre los puntos de calibración a través de la ruta a calibrar) y Mediciones (La mediciones serán recalculadas utilizando las mediciones preexistentes entre los puntos de calibración).
  • Radio de búsqueda, la distancia máxima a la que puede estar un punto de calibración de la ruta para que entre a formar parte del cálculo de calibración. El valor por defecto será “0” que indicará que los puntos que no estén sobre la ruta no serán tenidos en cuenta para la calibración de ésta.
  • Interpolar entre puntos de calibración, permite indicar que en los vértices que existan entre los puntos de calibración se interpole para asignar la coordenada M.
  • Extrapolar antes de puntos de calibración, permite indicar que en los vértices que existan antes de los puntos de calibración se extrapole para asignar la coordenada M.
  • Extrapolar después de puntos de calibración, permite indicar que en los vértices que existan después de los puntos de calibración se extrapole para asignar la coordenada M.
  • Ignorar huecos espaciales, permite indicar si no se desea que se tenga en cuenta el tamaño de los huecos que puedan existir entre los tramos de la ruta. Si está seleccionado no tendrá en cuenta la distancia entre el último vértice de un tramo y el primero del siguiente, y si no lo está, la distancia entre ellos repercutirá en el calculo de la coordenada M del primer vértice (y posteriores) del siguiente tramo.
  • Incluir todos los elementos en la capa de salida. Si está seleccionado se incluirán en el archivo de salida aquellas rutas para las que no se haya suministrado puntos de calibración.

El proceso de calibración se puede realizar sobre toda la capa o sobre aquellas rutas que se encuentren seleccionadas.

Post relacionados:

Filed under: gvSIG Desktop, spanish Tagged: carreteras, Segmentación dinámica, sistema referencia lineal

by Alvaro at November 23, 2015 09:41 AM

Le blog de Geomatys

Major release of Open Source Constellation-SDI project,v.Andromeda.

Constellation-SDI Andromeda is the outcome of the research and development efforts made ​​by the community for 7 years. This new geographic server allows users to manage and share their spatial data through many interoperable services.   Constellation-SDI is already used by many public and private agencies in France and abroad. These companies give impetus to […]

by geoadmin at November 23, 2015 09:25 AM

November 22, 2015

Cameron Shorter

Starting build cycle for OSGeo-Live 9.5

We are starting the build cycle for version 9.5 of the OSGeo-Live DVD/USB/VM which will be released in March 2016, ready for several special events, including FOSS4G-NA, FOSSGIS (Salzburg, Austria), among others.

We would like to hear from anyone wishing to add new projects to OSGeo-Live, anyone wishing to extend or add translations, or anyone who has ideas on how we should shape the upcoming release.

Key Milestones

  • 11 Jan 2016 All new applications installed, most old applications updated
  • 01 Feb 2016 Feature Freeze (all apps updated)
  • 15 Feb 2016 User Acceptance Test (all apps installed and working)
  • 21 Mar 2016 Final ISO sent to printers
... full schedule

About OSGeo-Live

OSGeo-live is a Lubuntu based distribution of Geospatial Open Source Software, available via a Live DVD, Virtual Machine and USB. You can use OSGeo-Live to try a wide variety of open source geospatial software without installing anything.

by Cameron Shorter (noreply@blogger.com) at November 22, 2015 07:14 PM

Andrea Antonello

Bye bye uDig, hello gvSIG world!

Bye bye uDig

This post should have been written ages ago. But I have never been ready to do so. And it still is very difficult for me to properly write something about my exit from the uDig community. The Open Source ecosystem is a particular one and people not involved in the same way understand things differently. But I love the Open Source ecosystem, it gives you always a new possibility even if it might seems there is none.

So I will try to stick with the facts, even if being my personal blog some passion could seep through.

We have loved uDig for many years. We have contributed about everything that means raster analysis in uDig and have been in the Project Steering Committee for several years. We fought the trend that was keeping uDig "only" an SDK for developers instead of a desktop GIS for the community. And well, it is time to say that we failed.

My guess is that uDig will never be a widely used desktop GIS, i.e. a standalone GIS. uDig will always be an amazing SDK. Something you use to build great location aware applications.

uDig has always suffered from the fact that there were almost no contributions in the last 5 years. No resources/interest to the fix bugs that were stopping people from using it. uDig didn't evolve much. Resources were really low and at some point I remember always the same 3 developers trying to get uDig up and running, adding stuff, making it work: Jody, Frank and myself.

Then, in this low resources situation we made a huge error. We started the migration into the Locationtech Fundation. Which is not an error per se, but in the conditions the community of developers was in, that has been an irresponsible move. uDig entered a kind of limbo from which I think it still didn't exit. There was no real well working version available and all resources were in the migration process. A process that lasted about 2 years. In the meanwhile we lost possible contributions (at least one big I know of), since it was not clear were to contribute: the old was old, the new was never finished.

In the middle of all this mess, in which Jody and Frank were doing a big big voluntary work and keeping the uDig ecosystem on their shoulders alone (kudos for all that to you guys), I started to retire from uDig. Several long discussions at the Nottingham Foss4G opened my eyes an made me understand that I was in the wrong project.
uDig was on the way to be an only-SDK project (if you disagree with that i will be happy to openly discuss about it) and this was no longer something I would be part of.
Also, the Locationtech environment was not exactly what I expected it to be (I am not saying good or bad, I am just saying not the right thing for me).

So we left... without knowing where to go. For a couple of years we were working without a desktop GIS. Something that had never happened before... and it felt really wrong!

But our clients needed our tools, so we created the standalone version of the spatial toolbox, S.T.A.G.E.
Funny thing is that once the tool was standalone, also QGIS users approached us, because it was handy. They didn't like it in uDig, but if they could use it with QGIS it was ok :-)

Hello gvSIG world!

Well, time passed and it was still unclear to us were we would land. uDig was still blocked somewhere in the migration process... when a company of friends of ours invited us to come to the gvSIG conference in 2014, offering to pay travel and accommodation. They were interested to see our Geopaparazzi digital field mapping tools inside gvSIG to use them in projects in development countries. While I was still emotionally too bound to uDIG to cheat on it, Silvia was very sensitive to the words "development countries", so we decided to accept the offer.

We had a private meeting with the gvSIG Association members and developers to discuss the possibilities to work together and migrate our JGrasstools and Geopaparazzi libraries into gvSIG.
I have to admit they were extremely helpful and we also made a session to quickly get me up and running with gvSIG development.

After the conference we came back to reality... with no funding we could never migrate... the process was simply too big. So time passed and nothing happened. Secretly I hoped the uDig migration nightmare would be over and we could go back to normal life.

A couple of months ago we decided to end the suffering and at least try something. So I contacted Alvaro Anguix from the gvSIG Association and discussed with him the blockers we had (mainly about the projection system) to start using gvSIG. After some discussions, we decided that it would be best for me to spend a week with them at the gvSIG headquarters in Valencia, hacking, coding and discussing the way thing should or should not be.

At the begin of this month I did exactly what that. I tried to prepare myself as much as possible in order to have tons of complex questions for their developers and flew to Valencia.

I had the luck to sit for a week near gvSIG's main architect and talk daily also to other developers, as well as discuss about user needs and features and Open Source philosophy. I found gvSIG to be a nice community, even if until that moment focused heavily on the latin world.

So let me show you what we were able to achieve in the last weeks.

I started with the aim to:
  1. bring the water management module based un Epanet into gvSIG
  2. bring support for geopaparazzi databases to gvSIG

The water management module

Porting that module has been fun. The biggest difficulty has been understanding the styling engine of gvSIG, which is way different from uDig.    

So for now we have a HydroloGIS menu inside which an Epanet menu appears. From there you can do the usual stuff: create new project files, link the layers properly together the Epanet way (filling in the attributes) and style layers:

When you run the module, the usual wizard appears. Now that wizard remembers exactly everything you entered before, which comes in handy when working a lot with simulations.

Results are stored directly into a sqlite database. One file can also contain more simulation runs.

The results can be visualized in two ways:
  1. view the state of the network in one moment (in time) on the whole map. This now looks way better than in uDig, since gvSIG allows for a nice legend to be updated. So in the layerview you will see also the values for each colored pipe or pump or junction.
  2. view the whole timeline of one of the pieces of the pipeline.

If you are interested to know more about it, come to this year's gvSIG conference, Silvia will give a talk about it:

GIS tools for water supply systems: an implementation using JGrassTools and gvSIG

Geopaparazzi support

gvSIG now has direct Geopaparazzi database support. That means that as you add any WMS, shapefile or tiff layer, now also an option for Geopaparazzi appears.

Once you select the database file, some information about the database will appear, as well as the layers it will create on loading:

You have the option to import it to temporary layer, but also to create shapefiles from the database.
The second option gives more features and is the suggested way to go.

Once imported, the layers will be generated with their own default style and labeling:

The media layer can now be queried with an own tool:

So if you select one or more images, they will be opened:

gvSIG now also has the tool to create a tileset (for Geopaparazzi basemaps) from the current view:

If you are interested in this, again, come to this year's gvSIG conference, I will be giving a talk about it. :-)

Digital field mapping with Geopaparazzi and gvSIG

The spatial toolbox: JGrasstools

Since things were going really fast (I was in Valencia and working around 15 hours a day, no partying for me this time :-) ), I decided to also give the spatial toolbox a try.

One thing that helped, was the fact that gvSIG is licensed under GPL license, which is the same one I love and JGrasstools are licensed under. That gave huge advantage during the integration.

This took a bit more work, also after the Valencia days, but it is already usable:

Obviously the layers are taken from the current selected map view and the coordinates (as in the above extract basin module) are set form clicks on the map.

If you are interested in this, again-again come to this year's gvSIG conference, I will be giving a talk about it. :-)

New tools for LiDAR, forestry, river management and hydro-geomorphology in gvSIG

Styling rasters

I am not sure why that happens, but every time I approach a GIS first, rasters is one of the last things to be considered. :-) Also the gvSIG raster system is not the best right now, but I know that there are resources to work on it next year, so I am quite happy about it.

For now, one thing that is really necessary, is the possibility to style rasters properly.

Right now, if I define a colortable for a map, I get 255 color rules.
One good example is the map of aspect. Such a map, that ranges between 0 and 360 degrees, is usually coloured from white to black between 0 and 180, and from black to white between 180 and 360. So all you need would be 3 rules, not 255 which make everything unreadable (apart of being wrong):

If I wanted to customize them, the only way I seemed to have, was selecting and editing each rule. That got odd very quickly.

So it has been better to invest that time to create a small styling tool, which right now is hosted in the HydroloGIS menu, but I really hope it will get into the raster style engine at some point.

An example: One of my favourite base maps is the elevation model with the aspect map overlayed with transparency, which gives that 3D sensation.

Just select the colortable and the transparency. Also the number format pattern in the legend and push apply. That is it:

Some legends are just colors, which will be adapted between the min and max of the raster map. Others, like the map of flowdirections instead, have defined unique values and colours:

One thing I have not been able to, is styling a map with a logarithmic scale. I have tried but failed. That one is for example important for a map like the one of total contributing areas, where the values range from 1 (many many cells) to huge numbers (but few few cells):

well, this should look more like this:

Coordinates Info tool

To exercise myself (and because Silvia forced me to :-) ) I developed a mini-plugin that allows the user to view the clicked coordinates and see them in another projection, but most of all allows to copy them quickly to use them:

Well known text tools

A last small tool that I added is the WKT toolbox. It is a very simple tool, but we find it very useful:

With it you can select a geometry in the layer and extract the WKT representation of the geometry.

The same way, in the lower box, you can write/paste some WKT geometry and it will be inserted as new feature in the currently selected layer, if it is of the same geometry type.

This makes it very easy, for example, to insert points in a layer.


Well, it is strange for me to finish a blog post with a conclusions section, but this one requires it.

I love the open source ecosystem. Once again, even if with much work and some investment, we have been able to find what we needed. HydroloGIS will from now on embrace the gvSIG community and bring its tools (as well as the ones from the universities of Trento and Bolzano) into gvSIG (time and resources permitting).

We have a desktop GIS again. We have a community that focuses on a community GIS again. One that focuses on user needs and tools, on cool selection features, even cooler editing features, on a working printing system (do we want to produce maps or not!??!?!), on 3D, on linear referencing, on table joins, and... and...

Hardhearted I bid farewell to the uDig project. With a small tear in my eyes I say ciao to those great developers with which I shared many nights, code sprints and fun talks. Jody and Frank, it has been a great journey with you and I will see you at the next Foss4g. I know you will bring uDig on top again at some point even without me ;-). Good luck in your quest!  

by andrea antonello (noreply@blogger.com) at November 22, 2015 11:09 AM

November 21, 2015

From GIS to Remote Sensing

Minor Update: Semi-Automatic Classification Plugin v. 4.8.5

This post is about a minor update for the Semi-Automatic Classification Plugin for QGIS, version 4.8.5.

Following the changelog:
- added tab for Sentinel-2 conversion

by Luca Congedo (noreply@blogger.com) at November 21, 2015 10:32 AM

GeoServer Team

GeoServer Code Sprint 2016

The GeoServer web administration console is built on top of the Wicket 1.4.x series, which is pretty old and unmaintaned. The purpose of the sprint is to update it to Wicket 7.x, the current stable version.

Upgrade from Wicket 1.3 to Wicket 7

Due to the large distance between the two releases and the number of backwards incompatible changes accumulated by Wicket in the years this will require the concerted effort of a handful of developers over a few days, including the changes to upgrade the code, and the thorough hand testing of the resulting modified interface.

Victoria British Columbia

The code sprint is planned for the week of January 18th in sunny Victoria British Columbia. Thanks to Boundless for providing a venue (either the boundless offices or Fort Techtoria depending on numbers).

A note on the timing: We were unable to join the Paris Code Sprint 2016 as it is scheduled too close to the GeoServer 2.9 code freeze. This location was selected to reduce travel costs allowing us to run the event with minimal sponsorship.

Participation and Sponsorship

We have the following sponsorship levels available:

  • Gold: $1000
  • Silver: $500
  • Bronze: $250

We are reaching out to international and local sponsors. Contributions will be put towards travel costs for overseas sprinters who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprints.

For more details on participation, sponsorship or budget for the event please see the GeoServer Code Sprint 2016 wiki page.


by jgarnett at November 21, 2015 03:25 AM

November 20, 2015

GeoTools Team

GeoTools 14.1 Released

The GeoTools team is pleased to announce the release of GeoTools 14.1:

This release was made by Ben Caradoc-Davies (Transient) in conjunction with GeoServer 2.8.1.

GeoTools 14.1 is the latest stable release of the 14.x series and is recommended for all new projects.

Fixes and improvements:
  • Fixed paged queries with JDBC post filters
  • Allow mixing of Z-order and compositing in WMS 
  • Support for coverage time dimensions with different names across datasets
  • app-schema support for setting string value for complex type extending anyType
  • Fixed JAI-Ext scalability issue while iterating over ROIs on machines with high number of CPUs
  • Fixed OOM while reading JPEG compressed GeoTIFFs under heavy load
  • Support for removing global and local values in EnvFunction filters
  • Log the full SQL statement when JDBC data store queries fail
  • Many rendering and SLD fixes
  • And more ...
 For more information see the release notes.

About GeoTools 14

GeoTools 14 highlights:
For more information see the 14-M014-M114-beta14-RC1, 14.0, and 14.1 release notes.

by Ben Caradoc-Davies (noreply@blogger.com) at November 20, 2015 06:37 PM

GeoServer Team

GeoServer 2.8.1 Released

The GeoServer team is pleased to announce the release of GeoServer 2.8.1. Download bundles are provided (binwardmg and exe) along with documentation and extensions.

GeoServer 2.8.1 is the latest stable release of GeoServer and is recommended for production deployment. This release is made in conjunction with GeoTools 14.1. Thanks to all contributors. Fixes and new functionality include:

  • Multidimensional GRIB / NetCDF / NetCDF Output modules promoted to extension
  • Fixed query parameters in SLD external graphic
  • Fixed legend preview with SLD external graphic
  • Fixed multiline labels in PDF WMS request with translation
  • Fixed layer preview GML links for app-schema layers
  • Fixed JMS clustering to use qualified names for layers, layer groups, and styles
  • Avoid catalog linear scans in GWC integration listeners
  • Fixed OpenLayers preview with the authkey module enabled
  • For a full list, see the release notes

Thanks to Ben Caradoc-Davies (Transient) for this release.

About GeoServer 2.8

Articles, blog posts and presentations:


by Ben Caradoc-Davies at November 20, 2015 06:33 PM

Markus Neteler

GRASS GIS 7.0.2 released

What’s new in a nutshell

The new GRASS GIS 7.0.2 release provides 190 stability fixes and manual improvements.

About GRASS GIS 7: Its graphical user interface supports the user to make complex GIS operations as simple as possible. The updated Python interface to the C library permits users to create new GRASS GIS-Python modules in a simple way while yet obtaining powerful and fast modules. Furthermore, the libraries were significantly improved for speed and efficiency, along with support for huge files. A lot of effort has been invested to standardize parameter and flag names. Finally, GRASS GIS 7 comes with a series of new modules to analyse raster and vector data, along with a full temporal framework. For a detailed overview, see the list of new features. As a stable release series, 7.0.x enjoys long-term support.

Source code download:

Binaries download:

More details:

See also our detailed announcement:

  http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures (overview of new 7.0 stable release series)First time users may explore the first steps tutorial after installation.


The Geographic Resources Analysis Support System (http://grass.osgeo.org/), commonly referred to as GRASS GIS, is an Open Source Geographic Information System providing powerful raster, vector and geospatial processing capabilities in a single integrated software suite. GRASS GIS includes tools for spatial modeling, visualization of raster and vector data, management and analysis of geospatial data, and the processing of satellite and aerial imagery. It also provides the capability to produce sophisticated presentation graphics and hardcopy maps. GRASS GIS has been translated into about twenty languages and supports a huge array of data formats. It can be used either as a stand-alone application or as backend for other software packages such as QGIS and R geostatistics. It is distributed freely under the terms of the GNU General Public License (GPL). GRASS GIS is a founding member of the Open Source Geospatial Foundation (OSGeo).

The GRASS Development Team, November 2015

The post GRASS GIS 7.0.2 released appeared first on GFOSS Blog | GRASS GIS Courses.

by neteler at November 20, 2015 04:59 PM

gvSIG Team

Libro: Taller gvSIG aplicado a urbanismo

Publicamos el libro “Taller gvSIG aplicado a urbanismo” basado en los diversos talleres que hemos realizados en jornadas gvSIG de este año, y como base para el correspondiente taller en las próximas Jornadas Internacionales de gvSIG.

El objetivo del taller es mostrar mediante una serie de ejercicios prácticos la utilidad que tiene gvSIG en el área del urbanismo.

No se trata de un taller que pretenda tratar el tema de la aplicación de los Sistemas de Información Geográfica al Urbanismo de forma profunda, sino servir de introducción para despertar el interés por gvSIG a los urbanistas.



Filed under: gvSIG Desktop, press office, spanish, training Tagged: arquitectura, documentación, libro, urbanismo

by Alvaro at November 20, 2015 04:33 PM

Paulo van Breugel

GRASS GIS 7.0.2 released

For those who haven’t seen it yet, GRASS GIS 7.0.2 has been released! See here for the announcement and here for a detailed overview of all the changes (over 190 of stability fixes and improvements since GRASS GIS 7.01). For those still using GRASS GIS 6.4, GRASS GIS 7 offers a strongly improved interface, a […]

by pvanb at November 20, 2015 04:29 PM

GeoTools Team

GeoTools 13.4 released

We are pleased to announce the availability of the GeoTools 13.3 release for immediate download:
This release is made in conjunction with GeoServer 2.7.4 and GeoNode 2.4 and is available from our maven repository

Thanks to Alessio Fabiani (from GeoSolutions) for packaging this release.

GeoTools 13.4 contains a 7 small fixes and improvements compared to 13.3, and it's the current maintenance release recommended for production. The changes include:

  • [GEOT-2603] - Encode PropertyIsLike filter 'matchcase' is ignored
  • [GEOT-5212] - DB2 st_dishoint does not work with SELECTIVITY clause
  • [GEOT-5254] - http://download.java.net/maven/2 repository is gone
  • [GEOT-5268] - DB2 plugin does not store z values for coordinates
  • [GEOT-5273] - The encode of LineStringPropertyType in GMLComplexType verify the class of value like a point
  • [GEOT-5274] - Badly structured source images can lead to rendering errors when oversampled
  • [GEOT-5287] - Render fails to ignore empty geometries in some very specific cases

For detailed information about changes please check the release notes.

About GeoTools 13

GeoTools 13 features and improvements:

by afabiani (noreply@blogger.com) at November 20, 2015 03:24 PM

Jackie Ng

Write MapGuide application once. Run MapGuide application anywhere?

MapGuide is a very flexible development platform, allowing you to build your MapGuide applications in either .net, PHP or Java.

Depending on your OS, you currently have the following development/deployment options:
  • Deploy .net or PHP on IIS
  • Deploy PHP or Java (in a Tomcat Servlet container) on Apache HTTPD
But what if we could be even more flexible than that? What if you deploy to any platform regardless of whether your application is .net, Java or PHP.

We now have the components that can make this a possibility.
  • .net is now cross-platform. The canonical recommended deployment strategy of ASP.net 5 applications is done through hosting the application via the Kestrel HTTP server, and reverse-proxying to it from a more industrial-strength HTTP server.
  • The HttpPlatformHandler module for IIS allows it to do process management and request proxying for other http listeners (like Tomcat or Kestrel), making it possible for IIS to "host" Java or .net Core applications.
So regardless of whether you're on .net*, PHP or Java we now have the means to deploy and host it on both Windows and Linux.

* Yes, there's a small caveat in this idealized scenario. It requires:
  1. A CoreCLR-compatible wrapper for the MapGuide API. This is something I'm playing around with at the moment.
  2. Your .net MapGuide application basically has to target the .net Core profile (and not the full .net Framework) in order to take advantage of the cross-platform deployment scenario.
  3. That we can reverse-proxy to Kestrel from Apache HTTPD. The official documentation refer to nginx as the front-facing web server, but if the ability to reverse proxy is the sole requirement, then any web server that has the capability can be the front-facing web server and not just nginx.

by Jackie Ng (noreply@blogger.com) at November 20, 2015 12:34 PM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (II)

Continuamos con las novedades en gvSIG 2.3 relacionadas con Segmentación dinámica. En este post veremos la herramienta de “Crear rutas”.

Esta herramienta sirve para crear rutas a partir de una capa de líneas. Su funcionamiento consiste en la agrupación de las geometrías de la capa de origen en una única entidad lineal mediante un atributo común.

Esta capa debe tener un atributo que sirva para identificar cada una de las rutas que se desean crear.

Al activar la herramienta, gvSIG muestra el siguiente cuadro de diálogo.

El usuario puede indicar:

  • Origen”, la capa de entrada.
  • Campo de identificadores de ruta”, el atributo de la tabla de la capa de lineas “Origen” que contiene el identificador de la ruta.
  • Fichero de salida”, el archivo en el que se desea que se guarden los resultados.
  • Origen de mediciones”, mostrará 3 opciones para seleccionar de donde se van a tomar las medidas para la dimensión M:
    • Longitud, la medición se basará en la longitud gráfica de la linea original
    • Un campo, la capa original deberá tener un campo que indique la longitud de cada uno de los tramos a enrutar y la medición se basará en dicho campo
    • Dos campos, la capa original deberá tener dos campos que indiquen la coordenada M del primer y último vértices de cada tramo y las mediciones se basarán en dichas M mediante interpolaciones.
  • Campo desde o longitud”. Estará habilitado cuando alguna de las opciones “Un campo” o “Dos campos” esté seleccionada en “Origen de mediciones”:
    • con “Un campo” se utilizará éste como medida del tramo
    • con “Dos campos” se utilizará éste como coordenada M del primer vértice del tramo
  • Campo Hasta”, se utilizará como coordenada M del ultimo vértice del tramo. Estará habilitado cuando la opción “Dos campos” esté seleccionada en “Origen de mediciones”.
  • Prioridad de las coordenadas”. Estará habilitado solo cuando “Longitud” o “Un campo” esté seleccionado en “Origen de mediciones”. Este valor servirá para decidir el vértice por el que se empezarán a acumular las mediciones y tendrá cuatro posibles opciones:
    • arriba – izquierda
    • abajo – izquierda
    • arriba – derecha
    • abajo – derecha
  • Factor de medición”, el usuario puede introducir un factor por el que se multiplicarán las mediciones antes de introducirlas en la coordenada M de los vértices. Tiene un valor por defecto de 1.
  • Compensación de medición”, el usuario puede introducir un valor que se sumará a las mediciones antes de introducirlas en la coordenada M de los vértices. Tiene un valor por defecto 0,0.
  • Ignorar huecos espaciales”, decidir si se desea que el tamaño de los huecos entre las geometrías se debe tener en cuenta para el caĺculo de las medidas. Estará habilitado solo cuando “Longitud” o “Un campo” esté seleccionado en el “Origen de mediciones”. Si está seleccionado no tendrá en cuenta la distancia entre el último vértice de un tramo y el primero del siguiente, y si no lo está, la distancia entre ellos repercutirá en el calculo de la coordenada M del primer vértice (y posteriores) del siguiente tramo.

Al aceptar el cuadro de diálogo, gvSIG generará el archivo de la “capa de salida” que contendrá las lineas de la capa original agrupadas en nuevas entidades según el valor de “Identificador de ruta” y el resto de opciones que el usuario haya introducido.

Si, previamente a la ejecución de la herramienta, la capa de origen tenía una selección solo se realizará el proceso sobre los elementos seleccionados.

Post relacionados:

Filed under: gvSIG Desktop, spanish Tagged: carreteras, Segmentación dinámica, Sistema de referencia lineal

by Alvaro at November 20, 2015 09:07 AM

OSGeo News

Boston Awarded Hosting of FOSS4G 2017

by jsanz at November 20, 2015 08:37 AM

November 19, 2015

GeoServer Team

GeoServer 2.7.4 released

The GeoServer team is happy to announce the release of GeoServer 2.7.4. Download bundles are provided (zipwardmg and exe)  along with documentation and extensions.

GeoServer 2.7.3 is a maintenance release of GeoServer recommended for production deployment. Thanks to everyone taking part, submitting fixes and new functionality including:


  • [GEOS-3228] – Empty filter causes IndexOutOfBoundsException
  • [GEOS-3432] – RESTConfig “styles” list does not get generated if a style is missing its associated sld file
  • [GEOS-4986] – Creating SQL Views via RESTConfig as JSON fails
  • [GEOS-6768] – externalGraphic with relative path and query parameters problem
  • [GEOS-7045] – Layer Security – Catalog Mode
  • [GEOS-7243] – Render (or transform) fails on Multipolygon but not on polygon
  • [GEOS-7256] – Maven Cobertura plugin does not work
  • [GEOS-7259] – JMS based cluster should use qualified names for Layers and Layergroups
  • [GEOS-7267] – JMS Clustering should prefix Styles names with workspace
  • [GEOS-7295] – OpenLayers preview does not work if authkey community module is enabled
  • [GEOS-7302] – Using on the fly meta tiling in WMS request may result in rendered images not being disposed of
  • [GEOS-7312] – RawDataPPIO does not close InputStreams it opens
  • [GEOS-7314] – GeoTiffPPIO can return the source file of a processed coverage


  • [GEOS-4762] – WCS should force usage of imageread
  • [GEOS-7150] – Features counted twice for WFS queries with GeoJSON responses

For a full list, see the release notes.

Also, as a heads up for Oracle users, the Oracle store does not ship anymore with the JDBC driver (due to redistribution limitations imposed by Oracle). For details see the updated the oracle installation instructions here.

Thanks to Alessio Fabiani (GeoSolutions) for this release.

This release is made in conjunction with GeoTools 13.4 and GeoNode 2.4.

by Alessio Fabiani at November 19, 2015 05:29 PM

Le blog de Geomatys

(Français) Prenez votre envol avec la librairie Proxy-vole

Sorry, this entry is only available in Français. Alexis Manin1

by Alexis Manin at November 19, 2015 11:20 AM

gvSIG Team

Camino a gvSIG 2.3: Segmentación dinámica (I)


Estamos  trabajando en la estabilización de la próxima versión de gvSIG, que va a traer importantes cambios tanto a nivel de desarrollo como a nivel de usuario. Es momento de comenzar una serie de post que nos permitan presentar todas aquellas novedades que vamos a encontrar en gvSIG 2.3.

Una de las novedades más importantes es la que denominaremos “Segmentación dinámica” que está relacionada con la gestión de infraestructuras de redes (carreteras, vías de ferrocarril, senderos, tendidos eléctricos, corrientes de agua, etc.).

La segmentación dinámica, también conocida como sistema de referencia lineal, es un método de referencia espacial en el que las ubicaciones de los elementos están referidos a través de medidas a lo largo de un elemento lineal.

La información relativa a elementos como las carreteras no utiliza coordenadas de un sistema de referencia (X,Y o Latitud, Longitud) sino hitos kilométricos. Por ejemplo se indica que en una determinada carretera hay un incidente en el kilómetro 17,300 o una congestión desde el kilómetro 6 al 12. El uso de este sistema de referencia basado en puntos kilométricos es lo que se conoce como segmentación dinámica. La posición de un elemento en este sistema de referencia lineal se conoce como coordenada M.

Por ejemplo, para la gestión de las carreteras y de todos los elementos que en ella se ubican (señalización, accidentalidad, aforos o intensidades medias de tráfico, etc.) es fundamental que el software SIG tenga la capacidad de generar la segmentación dinámica de una red de carreteras.

Esta capacidad se traduce en una serie de herramientas que permiten definir las rutas, calibrar cada ruta a partir de los hitos kilométricos, editar la coordenada M de un elemento, representar dicha coordenada M y generar nuevas capas con segmentación dinámica.

En definitiva con estas nuevas herramientas se podrá convertir una capa de carreteras, que tiene unas coordenadas X, Y conocidas, en un Sistema de Referencia Lineal basado en hitos kilométricos, o dicho de otra forma, subdividir esa carretera por sus hitos kilométricos (los denominados pk´s). Esto convierte las capas lineales de carreteras en polilíneas con coordenadas M.

Durante una serie de post os explicaremos que mejoras aporta este nuevo complemento.

Las herramientas que forman parte del plugin son:

  • Crear rutas
  • Calibrar rutas
  • Editar la calibración de una ruta
  • Generar segmentación dinámica
  • Mostrar medidas
  • Limpiar medidas

Para el correcto funcionamiento de estas herramientas, gvSIG ha incorporado recientemente una nueva implementación de la librería de geometrías que permite añadir una medida a cada uno de los vértices de una geometría. Estas medidas son las que estas herramientas permiten gestionar.

Filed under: gvSIG Desktop, opinion, spanish Tagged: coordenada M, gvSIG 2.3, Segmentación dinámica, Sistema de referencia lineal

by Alvaro at November 19, 2015 09:29 AM

gvSIG Team

NASA World Wind, gvSIG Association Honour Member


NASA World Wind has become a Honour Members of the gvSIG Association. The collaboration between the gvSIG and NASA World Wind projects started this year with the integration of both applications in gvSIG 2.2, that allowed to add the 3D component to gvSIG, and at the same time, that World Wind had all the possibilities of a complete Geographic Information System.

This work was recognised with the European Challenge, awarded during the last FOSS4G-EU.

From the gvSIG Association we are glad to recognise the NASA World Wind project work, and we hope to continue with the collaboration between both organizations.

Filed under: community, english, gvSIG Desktop, technical collaborations

by Alvaro at November 19, 2015 08:56 AM

gvSIG Team

NASA World Wind Socio de Honor de la Asociación gvSIG


NASA World Wind ha pasado a formar parte de los Socios de Honor de la Asociación gvSIG. La colaboración entre el proyecto gvSIG y el proyecto World Wind de la NASA comenzó este año con la integración de ambos en gvSIG 2.2, lo que permitió añadir la componente 3D a gvSIG y, a su vez, que World Wind tuviera toda la potencialidad de un completo Sistema de Información Geográfica.

Este trabajo de integración fue reconocido con el European Challenge, otorgado en el pasado FOSS4G-EU.

Desde la Asociación gvSIG estamos encantados de reconocer de este modo la labor del proyecto NASA World Wind y esperamos continuar avanzando en la colaboración entre ambas organizaciones.

Filed under: community, gvSIG Desktop, spanish, technical collaborations

by Alvaro at November 19, 2015 08:46 AM

Stefano Costa

L’etimologia di Genova

Perché Genova si chiama così? Dipende dall’epoca in cui fate questa domanda.

Oggi il calendario segna 2015 quindi lasciamo perdere la (interessante ma ben nota) paretimologia medievale di Ianua e quella molto meno interessante che rimanda al termine greco xenos. Parliamo dell’etimologia “vera” di Genua, attestata per la prima volta in un cippo miliario dell’anno 148 a.C. (CIL I¹ 540 = CIL V 8045).

Il cippo miliario di Spurio Postumio Albino (sanpierdarena.net) Il cippo miliario di Spurio Postumio Albino (Epigraphik-Datenbank  Clauss / Slaby)

L’ipotesi principale è che genua sia un termine indoeuropeo, che significherebbe “bocca” (*genaua), riferito alla foce del fiume ‒ il Bisagno. La tesi è stata formalizzata da Xavier Delamarre che nota nel suo Noms de lieux celtiques de l’Europe ancienne. Dictionnaire (p. 13, nota 5; traduzione mia):

Per limitarsi alla toponomastica, è notevole che l’antico nome di Genova, Genua, porto ligure per antonomasia, abbia una costruzione precisamente simile a quello della gallica Ginevra, Genava, entrambi esito di *Genoṷā, derivazione in -ā di un tema *genu- che indica la bocca in celtico (irlandese gin bocca, gallese gên ‘mascella’), e quindi per estensione ‘l’imboccatura’. Ora, se la derivazione semantica bocca → imboccatura, porto è banale e universale (latino ōsōstium, tedesco MundMündung, finlandese suu ‘bocca’ → (joen)suu, etc), è in celtico e solo in celtico che il tema indoeuropeo *ǵénu- / *ǵonu- che inizialmente indica la mascella o le guance (latino genae, gotico kinnus, sanscrito hanu-, etc.) è passato per metonimia a designare la bocca. Il nome «ligure» del porto di Genua è pertanto costruito su un tema la cui semantica è specificamente celtica.

Tra gli archeologi Delamarre ha trovato un primo forte sostegno da parte di Filippo Maria Gambari. La validità di questa ipotesi è slegata dalla attribuzione della lingua ligure preromana alla famiglia indoeuropea o al substrato pre-indoeuropeo, proprio perché il nome è attestato solo in epoca così tarda, e quindi potrebbe essere una acquisizione linguistica dalla lingua celtica in una situazione ‒ attestata anche archeologicamente ‒ di commistione celto-ligure. Le scoperte archeologiche dell’ultimo decennio nella zona della foce del Bisagno rafforzano questa ipotesi e indeboliscono molto la precedente ipotesi, sempre di ambito indoeuropeo, che indicava una possibile radice *genu– “ginocchio”, riferita ad un altra caratteristica geografica di Genova: l’insenatura del porto.

È interessante come in entrambe le ipotesi sia stata data per acquisita la coincidenza dell’etimologia di Genova con quella di Ginevra (registrata per la prima volta come Genaua nel De Bello Gallico), come indicato ad esempio sul Wikeriadur Brezhoneg (wikizionario bretone). Il bretone (con alcune lingue affini) e il gallese sono di fatto le uniche lingue che permettono di indicare questa parola come celtica, creando quindi un possibile legame etimologico. In effetti nel Catholicon breton (1464), la più antica testimonianza scritta di questo termine è indicata come guenou (mentre nel bretone contemporaneo il lemma è genoù), quindi il termine antico è più difforme dalla forma “celtica” rispetto a quello contemporaneo. In gallese genau indica “mouth, lips; estuary, entrance to a valley, pass, mouth (of sack, cave, bottle, &c.), hole; fig. saying, speech.” (Geiriadur Prifysgol Cymru). Sia il gallese sia il bretone sono considerate lingue celtiche “insulari”, cioè parzialmente distinte dalle lingue celtiche parlate sul continente (a maggior ragione in Liguria) e ora estinte.

L’archeologa Piera Melli, accettando questa ipotesi, sostiene nel suo recente volume Genova dalle origini all’anno Mille che potrebbe anche essere avvenuta una “etruschizzazione” del nome, in cui sarebbe stato sostanzialmente preso a modello il nome di  kainua (Marzabotto) e di altri nomi di città etrusche come mantua e padua. Tuttavia questa forma etrusca del nome di Genova non è attestata, e rimane una suggestione legata alla relativa abbondanza di iscrizioni in alfabeto etrusco rinvenute a Genova.

Genova nacque alla foce del Bisagno, ma era solo l’inizio.

by Stefano Costa at November 19, 2015 07:17 AM


GeoNode 2.4

GeoNode 2.4 Released

The GeoNode dev team is proud to announce the release of GeoNode 2.4 stable!

GeoNode 2.4 ships a lot of new features:

  • New granular permissions system
  • Support for groups and group permissions
  • New search engine based on json REST API with spatial search
  • Support for remote services
  • New responsive templates with brand new look
  • New contrib apps
  • Support to Geoserver 2.7.x
  • Several performance enhancements

Check it out for Ubuntu 14.04.

Don't upgrade before backing up your data!

There are a lot of internal changes from version 2.0 to 2.4, and even from 2.4 pre-release to 2.4 final.

The recommended upgrde path is to set up a new server from scratch and migrate the data to it.

Migration instructions

Installation Instructions

The automatic installer is available for Ubuntu 14.04 Trusty Tahr.

sudo add-apt-repository ppa:geonode/stable
sudo apt-get update
sudo apt-get install geonode

Then set the IP address and create a superuser.

geonode createsuperuser
sudo geonode-updateip

After your GeoNode is set up, don't forget to read the admin docs to personalize it and tweak it for better performance.

Getting support

You can report any issues or feature requests in our Issue Tracker in Github.

And a big thank you to all the developers and contributors for the big effort. See you in our Users mailing list

Posted at - 2015-11-19 16:30:00

November 19, 2015 12:00 AM

November 18, 2015


Publish Image Tooltips with QGIS Cloud

A lot of people are using QGIS Cloud as a service with ready to use QGIS webclient. It’s very easy to publish data and share maps in this way. Publishing of georeferenced images can be done with QGIS Cloud in a few steps as well. But the main problems are:

  • how to upload the images into the cloud database?
  • how to manage them?
  • how to display the results?

QGIS and QGIS Cloud are offering all tools for this task.

Create a new spatialite layer with QGIS:

As the first step we need to create a point layer with some mandatory columns.

  • Open the New Spatialite Layer dialog with Layer -> Create Layer -> New Spatialite Layer
  • Create in minimum three columns :
    • name text
    • filename text
    • image text
  • name the new layer images


Create a new dialog with QtDesigner which looks like in the image below.

For adding and managing the images a customized input GUI is needed.

  • add two QLineEdit Widgets and name them with the corret objectName
  • add two QTextEdit Widgets and name them with the corret objectName
  • add a QToolButton Widget with the corret objectName

  • or download the file attribute.ui


  • Open the layer properties of layer images and open the section fields.
  • Select from “Attribute editor layout”: Provide ui-file
  • To get the custom UI select the path to attribute.ui in “Edit UI” and open the gui.
  • Click OK

Create a Python init function for handling the image data.

When you add a new feature to the layer images, the dialog opens but the tool button is not working. To get it working we need some Python code.

The idea behind that is to run some functionality to convert the binary image to text based base64 encoding. Let’s Python doing that job for us. QGIS offers the ability to define an init function when a custom dialog is opened. This offers a wide range of options.

  • create a new text file and call it encodeimage.py
  • add the following Python code (or download the Python script encodeimage.py):

Import all nesseccary Modules and Classes from PyQt4 and QGIS

from PyQt4.QtCore import *
from PyQt4.QtGui import *
from qgis.core import QgsFeature,  QgsMapLayerRegistry
import base64

Define some global variables

filePathField = None
imageField = None
imagePreview = None
toolButton = None
fileName = None

This is the main function which will be connected with the QGIS layer dialog

def formOpen( dialog, layer, featureid ):

    global filePathField
    global imageField
    global imagePreview
    global toolButton
    filePathField = dialog.findChild(QLineEdit, "filename")
    imageField = dialog.findChild( QTextEdit, "image" )
    imagePreview = dialog.findChild( QTextEdit, "imagePreview" )

Find the QToolButton Object to connect the conversion function.

    toolButton = dialog.findChild( QToolButton, "toolButton" )

When the ToolButton is clicked run the method getFileName()


set the imageField Widget invisible for a nicer GUI. It is not nesseccary to see the data

    imagePreview.setText('<img width="300" src="data:image/jpg;base64,'+imageField.toPlainText()+'"/>')

Open FileDialog and convert the binary image to base64

def getFileName():
    filePath = QFileDialog.getOpenFileName(None,  'Open Image File',  '',  '(Images *.jpg *.png)')

    if len(filePath) > 0:
        encodedImage = ''

Read the image file and proceed the encoding

        encodedImage = base64.b64encode(open(filePath, 'rt').read())

Set the appropriate fields for storing in the QGIS layer


Set HTML img tag around the base64 image

        imagePreview.setText('<img width="300" src="data:image/jpg;base64,'+encodedImage+'"/>')

If you have finished editing, save this file in the same directory where your QGIS project file is stored. As the final step to connect the layer images with the Python module you have to define the Python init function in the layer properties of the layer images. Add encodeimage.formOpen to the Python init function definition. The Fields definition of the layer properties of layer “images” should look like


Now you are able to add images and photos to your spatialite database table. But be careful because the main disadvantage of this approach is the size of the image. The conversion of a 5Mb image produces a huge base64 string. As the result it will be very wise to reduce the size of the images you want to add to the layer. If you like, you can add a check of image size to the Python module.

A nice tool of the QGIS map canvas is the option to add maptips to a layer. When maptips are activated images should be visible when the mouse moves over a feature of the layer images in the map.

Create a maptip with image as content

  • open the layer properties of the layer images and jump to the Display section.
  • tick the HTML radio button.
  • add the HTML code to the Text field as you can see in the figure below:
  • close the dialog with OK
  • activate the maptip tool in QGIS and move over a feature of the layer images. The ame and the image are popped up.


Share your images with QGIS Cloud

What’s about to share the pictures and the geolocation of the pictures with others over the web. For this task QGIS Cloud is the right choice. QGIS Cloud is your personal spatial data infrastructure and offers OGC Web Services and ready preconfigured Web GIS clients.

  • save the project.
  • open the QGIS Cloud plugin (If you don’t have the QGIS Cloud plugin installed, than install it from the official QGIS Plugin Repository)
  • log in your QGIS Cloud account. (If you don’t have a QGIS Cloud account, sign up a new account).
  • upload the local data to your QGIS Cloud database (if you don’t have a QGIS Cloud database, create one from the QGIS Cloud plugin).
  • publish the project via QGIS Cloud plugin.
  • open the map in QGIS Cloud Web Client
  • activate the identify tool and move over a point with image
  • here you are, it works


November 18, 2015 04:00 PM

Jackie Ng

Making the mapagent serve more useful looking JSON

Let's make that SELECTFEATURES mapagent operation a bit more useful!

by Jackie Ng (noreply@blogger.com) at November 18, 2015 02:38 PM

gvSIG Team

Recopilación de proyectos finales del MOOC de Scripting en gvSIG (III)

Hace unos días publicamos varios post ( I, II) con algunos de los mejores proyectos finales realizados durante el MOOC de Scripting. Continuamos con una tercera parte. Esperamos que os gusten y los veáis de utilidad.

  • Script: Enlace espacial a geometrías más cercanas
  • Realizado por: Iñaki Zuazo
  • Resumen: Este script sirve para añadir un nuevo campo a una capa1, de otra capa2, y el valor de ese campo de cada entidad de la capa1 sera el de la entidad más cercana de la capa2.

  • Script: Desplazamiento de puntos seleccionados
  • Realizado por: Ana Cruz Martín
  • Resumen: El script realiza el movimiento de los puntos seleccionados de una capa; si no se seleccionan puntos, mueve todos los puntos de la capa.



  • Script: Transformar tipos de datos y formatos
  • Realizado por: Josep Jané Iniesta
  • Resumen: Duplicar columna con diferente tipo de dato: El objetivo es que teniendo una columna que sea de tipo texto (STRING) pero que contenga números o fechas, podamos transformala a una nueva columna de ese tipo nuevo de dato pero que tenga el mismo nombre que el campo inicial. Esto te obligará a crear una columna intermedia


Recordad que si estáis interesados en aprender a programar así, el MOOC de Scriptinges gratuito y se encuentra siempre en abierto. Está orientado para usuarios sin conocimientos previos en programación (siempre ayuda conocer algo de Python) y contamos con un foro que es una fuente muy valiosa de conocimiento (al cual siempre estoy atento a responder dudas), en el que podrás consultar rápidamente con otros alumnos. Puedes inscribirte e ir al ritmo de aprendizaje que más cómodo te sea.

Lo mismo, si queréis optar al certificado, solo hay que completar el curso y abonar una cantidad de 40€, que van dirigidos a la sostenibilidad del proyecto. Con esto realizaremos una corrección de todos los ejercicios que realicéis y un seguimiento personalizado.

Si has realizado scripts por tu cuenta y quieres subirlos al Outreach de gvSIG, simplemente ponte en contacto con nosotros a través de este email.

¡Más proyectos próximamente!

Filed under: development, gvSIG Desktop, scripting, spanish

by Óscar Martínez at November 18, 2015 12:38 PM

November 17, 2015


Docs For Devs

November 17, 2015 07:26 PM



November 17, 2015 07:26 PM