Welcome to Planet OSGeo

July 01, 2015

Andrea Antonello

Geopaparazzi 4.4.0 is out! First RasterLite2 for the brave!

The version 4.4.0 of Geopaparazzi has been pushed to Google Play.


The main news for this release is for sure the first inclusion of RasterLite2, the spatialite raster support, in the release. This makes geopaparazzi 3Mb heavier but it is worth the price.


So to summarize:


1) RasterLite2 support


RasterLite2 is not yet in stable phase, but it is already good to play with. A first stable release should be out by begin of the next year.


For this kudos go to Mark Johnson, that took care of making this possible.


It is also Mark to supply this beatiful map of Berlin in RasterLite2 format:








A RL2 database can contain more than one map, so a review of the tile source tree has been necessary. The RL2 database is represented as folder:







And also the filter-by-type buttons had to be changed because of space issues:



But good thing is, they now remember the last used setting.








2) view the position coordinate when panning



This is a small one, but handy to many. An image explains it all:




3) and last but not least, a better center on GPS button and better GPS status on the map

This has been asked a couple of times in the list, so we thought it might be best to put them together.

Can you tell the difference?



That should be the most important changes for this release!
Enjoy!!






by andrea antonello (noreply@blogger.com) at July 01, 2015 05:31 AM

June 30, 2015

Boundless Blog

Pioneers Get All the Arrows

Early in my career an industry veteran cautioned me from taking on a new initiative for my company. His words of wisdom were, “Pioneers Get all the Arrows.”  I thought long and hard about these words as I embarked upon this initiative, ultimately working on a team that enjoyed much success. But the reason we enjoyed success is we understood and appreciated the risks involved, and we built solid plans to mitigate those risks. From the beginning of time great accomplishments were often preceded by great failures. Given the many years I resided in Chicago, I’m often reminded of how arguably one of the greatest athletes of our time, #23, Michael Jordan, failed to make his high school varsity team over concerns about his height. We all know how that turned out long term for MJ…

Boundless has been on a similar journey from Open Source Geo industry pioneer to Open Source Geo industry leader. The company has evolved from the original small project incubated under a well-established charity to the recognized software and services leader it is today. There have been some failures and much success. But during this journey, Boundless has stayed true to our Open Source roots, furthering the cause for Open Source adoption in the Geospatial community and with specific initiatives for GEOINT.

Open Source has now become a force to be reckoned with in the Geospatial community.  No event in my tenure drove this point home further than to listen to Robert Cardillo’s speech during the just-completed GEOINT 2015 event, sponsored by USGIF in DC last week. As I “walked the show floor,” met with customers, partners, and industry leaders and listened to many of the speeches and presentations from government Seniors, I reflected on just how far the Open Source movement in Geo has come in a few short years. Boundless has been and continues to be on the forefront of this change with OpenGeo Suite, allowing customers and partners greater freedom and flexibility to drive technical solutions in their environments while directly influencing the product roadmaps and innovation. Our customers are building solutions that enable their missions and meet their business requirements while providing a lower cost of ownership.

GEOINT was an awakening for me. It was validation of our strategy, furthering of our partnering strategy, and strengthening of our company overall as we truly listened to customers and partners and work to incorporate this feedback into our product, services offerings, and roadmap.  There is no time like the present for all of the different projects, communities, and companies that work in the OpenGeo ecosystem to capitalize on our unique ability to move the industry forward with true and validated openness.

In this case, being a pioneer continues to be rewarding. There are some scars left over from a few arrows that hit a soft target, but the mission of the company has not changed. Seeing that mission aligned so well to the needs of our customers is the ultimate reward.

 

The post Pioneers Get All the Arrows appeared first on Boundless.

by Ann Johnson at June 30, 2015 08:04 PM

geomati.co

Noves condicions d'ús, ara més senzilles i obertes

Per tal de generar valor afegit a partir de la informació cartogràfica,
geològica i geofísica, l'ICGC ha actualitzat les condicions d'ús de la
informació que produeix o n'és propietari.

Concretament, les noves condicions es basen en la llicència Creative Commons de Reconeixement 4.0 Internacional (CC BY 4.0), que permeten la
reutilització de la informació cartogràfica, geològica i geofísica per a
qualsevol objectiu lícit, especialment la reproducció i divulgació amb
qualsevol mitjà, i la creació de productes o serveis d'informació amb valor
afegit, simplement indicant l'autoria de la font (i aplicant els altres
termes definits en les condicions i en el CC BY 4.0).

Web ICC

Quin gran moment. Després de tants anys, això s'ha de celebrar!!!
Ara ja no hi ha excusa per (re)utilitzar la informació de formes creatives.
:)

Fins dijous!

Oscar Fonts

June 30, 2015 01:49 PM

From GIS to Remote Sensing

Video Tutorial: Your First Land Cover Classification


I have published a new video tutorial bout the use of the Semi-Automatic Classification Plugin (SCP) for the classification of a generic multi-spectral image. It is recommended to read the Brief Introduction to Remote Sensing before this tutorial.


by Luca Congedo (noreply@blogger.com) at June 30, 2015 08:00 AM

gvSIG Team

Reprojecting vector and raster layers in gvSIG 2.x

When we download cartography from a web page we need to know its reference system in order to load it correctly in gvSIG. For that we have to look for it at the same web page, or access to the metadata if they are published.

The reference systems are designed by codes in gvSIG, and EPSG is the most used code (managed by the International Association of Oil & Gas Producers – IAOGP). If we don’t know the EPSG code of our reference system, we can search it in gvSIG by Name or by Area. We also can look for it at the next EPSG codes list.
When we are working on gvSIG we must select the reference system of the View that we are creating. Then, when we add a layer, if it’s at the same reference system than the View we will add it directly, and it will appear on the correct location.

Nevertheless, if it’s in a different reference system, we will act differently for raster or vector layers.

 

Reprojecting vector layers

If our vector layer is in a different reference system than the View one, we must indicate it when loading (we also can select the transformation to be applied in order to adjust the reprojection). As gvSIG detects that it’s a different reference system it will be reprojected on the fly.

reproy-vectorial-en_1

This reprojection will be, as we said, “on the fly”, that means, the layer will be at its original reference system yet.

If we want to have that vector layer at the same reference system than the View, once it’s reprojected on the fly, we must export it to a new file (Layer->Export to menu)

That new file that we have saved on our computer will be on the new reference system, the same system than the View, so if we load it on the same View we won’t have to indicate its reference system, assuming the same than the View. It will be loaded correctly already.

Note: If we make any geoprocess on the ‘reprojected on the fly’ layer, we won’t get the correct results because it’s made on the layer on its original system. For that we must do it on the exported layer.

 

Reprojecting raster layers

If we have a raster layer that is in a different reference system than the View, gvSIG can’t reproject it at the same way than the vector layers.

If we want to reproject a raster layer to the same reference system than the View we will load it on the View directly (it won’t be loaded correctly), and we will use the “Reproject raster layer” tool.

For that we will open the raster tools main menu (we must click on the white triangle that is in the button), and then select the “Geographic transformations” option.

reproj-raster-en1

Once this option is selected, we open the menu at the right side, and we select “Reproject layer”.

reproj-raster-en2

At the new window, we select the source projection of the layer, and the target projection, that will be the same than the View one (selecting the transformation if we know it and we want to adjust the reprojection). We will select the name of the reprojected system and where it will be saved.

When we accept it, we indicate that it has to add the layer to the View, so it will be at the same reference system than the View. We will remove the old layer, and zoom to the new one.

 

How to check which is the reference system of a layer

If we have a layer, and we don’t know its reference system like we told at the beginning, and we don’t have the prj file with that information, we can use reference cartography to check it.

Most of the WMS services offer the layers in several reference systems, in the official ones of the offered area normally, so that we can use them for checking it.

For that we will open a View in gvSIG, that will be in a concrete reference system (one of the systems that we think our layer can be). Then we will load a WMS layer at the same system (it’s recommendable to use some layer that offers lots of details, like cadastral cartography). We will load our layer finally, assuming that it’s in the same reference system than the View, and if it coincides, the layer will be in that reference system.

In case it doesn’t coincide, we’ll do the same operation with another View in other reference system, and loading the WMS layer in that system.


Filed under: english, gvSIG Desktop

by Mario at June 30, 2015 07:50 AM

June 29, 2015

GeoSolutions

Developer’s Corner: Customizable arrow in GeoServer

GeoServer

Dear Reader,
Today we want to share a recent development in  GeoServer: an arrow mark whose proportions can be customized to get the type of arrow you're looking for.
The general syntax for this arrow mark is the following:
<WellKnownName>extshape://arrow?hr=[hrValue]&t=[tValue]&ab=[abValue]</WellKnownName>
All parameters are ratios, and they are all optional. By default the arrow is the usual 1 by 1 mark, whose actual size you can control in SLD via the Mark size attribute. In particular, the parameters and their default values are:
  • t: thickness of the arrow base, between 0 and 1, default is 0.2
  • hr: height over width ratio, a positive number, default is 2
  • ab: arrow head base ratio, between 0 and 1, default is 0.5
The values can be modified to change the proportions of the arrow, for example, varying t between 0 and 1 results in the following arrows:
arrow1
Changing the height to width ratio will generate arrows that are wider or thinner:
arrow2
Finally, changing the arrow head base will move the position where the head of the arrow starts:
arrow3
Playing with all the three parameters will allow you to get the arrow of the desired proportions. Now, what if your desired characteristic is just having a long arrow? Since size is controlled by the mark size attribute, you'll have to make a big arrow whose height ratio makes for a thin one, and maybe push up a bit the arrow base, like in this example:
<?xml version="1.0" encoding="ISO-8859-1"?>
<StyledLayerDescriptor version="1.0.0"
 xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd"
    <Name>ThinArrow</Name>
      <Title>Thin long arrow</Title>
        <Rule>
          <Name>r1</Name>
            <PointSymbolizer>
              <Graphic>
                <Mark>
                  <WellKnownName>extshape://arrow?hr=4&amp;ab=0.8</WellKnownName>
                  <Fill>
                    <CssParameter name="fill">#000000</CssParameter>
                  </Fill>
                </Mark>
              <Size>40</Size>
            </Graphic>
          </PointSymbolizer>
        </Rule>
      </FeatureTypeStyle>
    </UserStyle>
  </NamedLayer>
</StyledLayerDescriptor>
Which will result in the following arrows:
arrow4 We would like to thanks the GEOS Fugro for funding this work under a GeoSolutions Enterprise Services support contract. The GeoSolutions team, http://www.geo-solutions.it

by Andrea Filosa at June 29, 2015 01:04 PM

Blog italiano di gvSIG

gvSIG a FOSS4G India 2015

gvSIGpresentation

gvSIG presentato da KAIINOS al FOSS4G India 2015

Il FOSS4G India 2015 si è tenuto dall’8 al 10 giugno all’istituto Indiano di Telerilevamento a Dehradun. Vi hanno partecipato più di 100 delegati provenienti da tutto il paese e con comunità di studenti che hanno partecipato con tanto entusiasmo. Circa 45 persone hanno presentato il loro lavoro in vari settori: silvicoltura, smart cities, open data e open standard, meteorologia, difesa, geolocalizzazione, etc. La conferenza ha presentato la sempre crescente influenza di FOSS4G nel contesto indiano.

Caso studio in Italia gvSIG al FOSS4G India

Caso studio in Italia gvSIG al FOSS4G India

KAIINOS, come rappresentante dell’Associazione gvSIG, ha avuto l’opportunità di presentare casi studio con gvSIG nella sessione “Use of Open Source Geospatial Tools in Capacity building and in Strategic Applications “. KAIINOS ha messo in evidenza nella sua presentazione i vantaggi tecnici di gvSIG, il suo ambiente di sviluppo flessibile, la facilità d’uso, la compatibilità cross-platform, le potenti librerie di geoprocessing, etc. Ma la vera forza dell’Open Source si trova nella comunità e gvSIG ha una grande comunità di utenti e sviluppatori in circa 100 paesi. Un altro grande punto di forza di gvSIG è la disponibilità di supporto per lo sviluppo di applicazioni personalizzate e altri servizi attraverso l’associazione gvSIG (Associazione di piccole e medie imprese con più di 60 collaboratori e partner). Nella presentazione sono stati messi in evidenza anche  gli sforzi di sensibilizzazione da parte della Associazione nel fornire corsi di formazione, come i MOOC per esempio.

gvSIG, che è molto famoso in Europa e nei paesi del Sud America, è ancora un novizio nella comunità GIS indiana. KAIINOS dopo aver provato le potenzialità di gvSIG è diventato membro dell’Associazione ponendosi due obbiettivi. Il primo incrementare il numero di utenti base di gvSIG nella comunità geospaziale indiana e l’altro è quello di sviluppare soluzioni convenienti che utilizzano la tecnologia gvSIG. Come parte attiva della crescente base di utenti di gvSIG in India, KAIINOS sta mettendo il materiale espositivo gvSIG come poster nelle conferenze tenute in India.

Libera traduzione in italiano del post gvSIG at FOSS4G India 2015  pubblicato su gvSIG blog il  da .


by Maurizio Foderà at June 29, 2015 07:00 AM

June 28, 2015

Free and Open Source GIS Ramblings

Video tutorial: animated heatmaps with QGIS

Do you like the QGIS heatmap functionality? Did you know that QGIS can also create animated heatmaps?

The following video tutorial shows all necessary steps. To reproduce it, you can get the sample data from my Time Manager workshop at #QGIS2015.


by underdark at June 28, 2015 06:14 PM

June 27, 2015

GeoServer Team

GeoServer XEE Vulnerability

GeoServer has encountered an XML External Entity (XEE) vulnerability permitting an unauthenticated read access to server files.

This vulnerability GEOS-7032 is addressed in the following releases and we strongly encourage all users to upgrade:

Thanks to Ben Caradoc-Davies (Transient Software) for the maintenance release along with Jody Garnett (Boundless) and Andrea Aime (GeoSolutions) for the unscheduled patch releases provided above.

If you are running an earlier version of GeoServer and would like to generate a patch release please contact one of our commercial support providers, or join us on geoserver-devel to volunteer.

About XEE

For more information on XEE see owasp articles on XML External Entity Processing and XML External Entity Attack provided to geoserver-devel by Johannes Kröger.

Responsible Disclosure

If you encounter a security vulnerability in GeoServer, or any other open source software, please take care to report the issue in a responsible fashion:

  • Keep exploit details out of issue report (send to developer/PSC privately – just like you would do for sensitive sample data)
  • Be prepared to work with Project Steering Committee (PSC) members on a solution
  • Keep in mind PSC members are volunteers and an extensive fix may require fundraising / resources

If you are not in position to communicate in public (or make use of the issue tracker) please consider commercial support, contacting a PSC member privately or contacting us via the Open Source Geospatial Foundation at info@osgeo.org.

We will be revising the GeoServer Developers Guide to clarify in the coming days.

by jgarnett at June 27, 2015 06:23 AM

June 26, 2015

gvSIG Team

Reproyección de capas ráster y vectoriales en gvSIG 2.x

Cuando descargamos cartografía de una página web debemos saber en qué sistema de referencia está para poder cargarla en gvSIG correctamente. Para ello deberemos buscar en la propia página para ver si lo indican, o si ofrecen los metadatos accederemos a ellos y lo comprobaremos.

Los sistemas de referencia en gvSIG vienen designados por códigos, siendo el sistema más utilizado el EPSG (gestionados por la International Association of Oil & Gas Producers – IAOGP). Si no conocemos el código EPSG de nuestro sistema de referencia podemos realizar una búsqueda en gvSIG por Nombre o por Área. También podemos buscarlo en el siguiente listado de códigos EPSG.

Al trabajar en gvSIG, debemos seleccionar el sistema de referencia de la Vista que creamos, entrando en sus propiedades. Después, cuando insertamos una capa, si está en el mismo sistema de referencia que la Vista la añadiremos directamente, y aparecerá en su sitio.

Si, por el contrario, la capa se encuentra en un sistema de referencia distinto al de la Vista debemos reproyectarla, y dependerá de si es una capa ráster o vectorial lo haremos de una u otra forma.

 

Reproyección de capas vectoriales

Si tenemos una capa vectorial que está en un sistema de referencia distinto al de la Vista, deberemos indicárselo en el momento de cargarla, cambiando sus propiedades (al indicar el sistema de la capa podremos seleccionar también la transformación a aplicar, para ajustar más la reproyección). Al detectar gvSIG que es un sistema distinto la reproyectará al vuelo.

reproy-vectorial-es_1

Esta reproyección será, como hemos dicho, “al vuelo”, es decir, que la capa seguirá estando en su sistema de referencia original.

Si lo que queremos es tener esa capa vectorial en el sistema de la Vista, lo que deberemos hacer es, una vez reproyectada al vuelo, exportarla a nuevo fichero (menú Capa->Exportar a).

Ese nuevo fichero que hemos guardado en disco ya estará en el nuevo sistema de referencia, en el de la Vista, por lo que si lo cargamos ahora en dicha Vista ya no deberemos indicarle su sistema de referencia, asumiendo el de la propia Vista. Se cargará ya correctamente.

Nota: Si realizamos algún geoproceso sobre una capa reproyectada al vuelo, no obtendremos el resultado correcto, ya que lo realiza sobre la capa en su sistema original. Para ello debemos realizarlo sobre la nueva capa que hemos exportado, sobre la que tenemos ya en el sistema de la Vista.

 

Reproyección de capas ráster

Si tenemos una capa ráster que está en un sistema de referencia distinto al de la Vista, gvSIG no la puede reproyectar al vuelo como habíamos hecho con las capas vectoriales.

Si queremos reproyectar dicha capa ráster al sistema de la Vista, lo que haremos será cargarla en la Vista directamente (no se cargará en su sitio), y utilizar la herramienta de “Reproyección de capa ráster”.

Para ello abriremos el menú principal de herramientas ráster (el botón de la izquierda, pinchando sobre el triángulo blanco que hay en él), y seleccionaremos la opción de “Transformaciones geográficas”.

reproy-raster-es1

Una vez seleccionada esta opción, abriremos el menú de la parte derecha, y seleccionaremos “Reproyectar capa”.

reproy-raster-es2

En la nueva ventana que se abre seleccionaremos el sistema de referencia origen de la capa, y el sistema de referencia al que queremos reproyectarla, que en nuestro caso era el de la Vista (seleccionando la transformación a aplicar si la conocemos, y si queremos ajustar más la reproyección). Seleccionaremos el nombre del fichero reproyectado y dónde lo debe guardar.

Cuando aceptamos le indicamos que agregue la capa en la Vista, con lo que ya la tendremos en el sistema de la Vista. Entonces eliminaremos la capa anterior, que no estaba cargada correctamente, y haremos un zoom a la capa nueva.

 

Cómo comprobar en qué sistema de referencia está una capa

Si tenemos una capa, y no nos han facilitado su sistema de referencia como hemos indicado al principio, si no disponemos de ninguna información, como por ejemplo su fichero .prj, podemos utilizar cartografía de referencia para comprobarlo.

La mayoría de los servicios WMS ofrecen las capas en varios sistemas de referencia, normalmente en los oficiales del área ofrecida, por lo que podemos utilizarlos para hacer la comprobación.

Para ello lo que haremos es abrir una Vista en gvSIG en un sistema de referencia concreto (uno de los que nosotros pensamos en que puede estar la capa). Después cargaremos una capa WMS en el mismo sistema (es recomendable cargar alguna capa que ofrezca detalle, tal como cartografía catastral). Finalmente cargaremos la capa, asumiendo que es el mismo sistema de la Vista, y si coincide con la cartografía de referencia será que dicha capa está en ese sistema.

En caso de que no coincida, realizaríamos la misma operación con otra Vista en otro sistema de referencia, y cargando de nuevo la capa WMS en el sistema de dicha Vista.


Filed under: gvSIG Desktop, spanish

by Mario at June 26, 2015 10:44 AM

Bjorn Sandvik

Freelance mapper

I’m going freelance over the summer, after 5 great years at the Norwegian Broadcasting Corporation (NRK). It was not an easy decision, but I have to try. I’ll tell more about my plans later. I’m available for hire if you need help on your mapping project, home or abroad.

Some of the projects I've been working on at NRK:

The flexible mapping stack of NRK.no, allowing journalists and digital storytellers to create advanced maps in minutes. 

"Kartoteket" - our in-house mapping tool built on top of our mapping stack.

Digital storytelling using NRKs mapping stack and Mapbox. 

Digital storytelling using NRKs mapping stack and Mapbox. 

Flood maps using NRKs mapping stack and CartoDB.

Radon affected areas in Norway using NRKs mapping stack.

Our popular photo maps

Video map of the long running TV show Norge Rundt.
Tracking of "Sommerbåten" along the coast of Norway.

Other work.

by Bjørn Sandvik (noreply@blogger.com) at June 26, 2015 07:57 AM

gvSIG Team

Talleres 7as Jornadas gvSIG LAC: gvNIX

Como ya sabréis en las 7as Jornadas gvSIG de Latinoamérica y Caribe hay previsto realizar un buen número de actividades, todas gratuitas, y entre ellas un taller de gvNIX.

Y aquí empezarán vuestras dudas… ¿gvNIX?¿Qué es esto? ¿Me puede interesar asistir a este taller?

gvNIX es el nuevo proyecto que se incorpora al catálogo de la Asociación gvSIG, un software que pensamos viene a cubrir un aspecto hasta ahora no cubierto por la geomática libre. Un proyecto que amplia considerablemente el abanico de usos de la geomática, entrando directamente a formar parte de soluciones informáticas en su sentido más amplio. En definitiva con gvNIX podemos ir un paso más allá de las soluciones IDE/Geoportal al uso y que pasen a estar integradas en soluciones de gestión más complejas y dejen de ser “islas” ajenas al resto de la informática de una organización.

gvNIX es una herramienta de desarrollo rápido de aplicaciones web Java. Es una herramienta de software libre (GNU/GPL v.3), altamente productiva, flexible y que no compromete la calidad de los proyectos. Y, claro, que incluye componente GEO … pero por componente GEO no estamos hablando de que nuestra aplicación muestre un mapa de Google Maps donde geoposicionamos información concreta de la aplicación, estamos hablando que nuestra aplicación permitirá a los usuarios finales, tanto si tienen conocimientos en geomática como si no los tienen:

  • Editar datos de tipo GEO.

  • Cruzar información de múltiples fuentes en un mapa.

  • Filtrar la información visualizada en el mapa.

  • Mostrar en el mapa sólo la información seleccionada.

  • Generar automáticamente listados de capas disponibles.

  • Añadir fácilmente nuevas capas:

    • Datos de entidades

    • Tile Layers

    • WMS Layers

  • Habilitar herramientas de mapas y permitir crear nuevas herramientas: medición, zoom, escala… así como herramientas personalizables.

  • Acceder desde cualquier dispositivo: tableta, móvil, PC … debido a su diseño responsive.

Precisamente en el taller nos centraremos en esta componente GEO.

Llegados a este punto podemos ya comentar que este taller está especialmente orientado a desarrolladores.

Para los que quieran asistir al taller y además quieran ir siguiendo los distintos ejercicios del mismo, los requisitos previos son:

En cuanto a la parte práctica, en el taller veremos como:

  • Crear base de datos POSTGRESQL con extensión POSTGIS (para agilizar el taller se aconseja que los asistentes ya lo tengan configurado)

  • Configurar un proyecto para trabajar con componentes GEO

  • Crear un proyecto gvNIX basado en modelo de entidades con campos GEO

  • Generar capa web (Datatables, Bootstrap, jQuery, etc…)

  • Transformar capa web de campos GEO para guardar datos

  • Demostración de creación, actualización y visualización de entidades con campos GEO

  • Generar mapa vacío

  • Añadir entidades al mapa

  • Añadir nuevas capas al mapa (Tiles y WMS)

  • Añadir nuevas herramientas al mapa (Personalizadas e incluídas en gvNIX)

  • Configuración de capas (filtrable, seleccionable, icono, colores, etc…)

  • Demostración de filtrado y selección utilizando componente Datatables

Al acabar el taller, los asistentes tendrán un Geoportal con el siguiente aspecto:

map_entities_1filter_0

Sin duda este tipo de talleres ya justifican la asistencia a las Jornadas. ¡Que no falte nadie!

Recordar que los talleres son gratuitos, al igual que todas las actividades de las jornadas, y que para asistir necesitáis realizar vuestra inscripción a las jornadas mediante el siguiente enlace:

http://www.gvsig.com/es/eventos/jornadas-lac/2015/inscripcion

Post anteriores sobre talleres:


Filed under: events, gvNIX, spanish, training Tagged: geoportal, LAC, Spring Roo, talleres

by Alvaro at June 26, 2015 07:26 AM

June 25, 2015

OSGeo News

OSGeo-BE is an official local OSGeo chapter

by jsanz at June 25, 2015 05:45 PM

gvSIG Team

gvSIG at FOSS4G India 2015

gvSIG prsented by KAIINOS at FOSS4G India 2015

gvSIG prsented by KAIINOS at FOSS4G India 2015

FOSS4G India 2015 was held at Indian Institute of Remote Sensing, Dehradun. It was attended by more than 100 delegates from all over the country with student community participating with lot of enthusiasm. Close to 45 people presented their work in various domains like forestry, smart cities, open data and open standards, weather, defence applications, localization etc. The conference showcased the ever growing influence of FOSS4G in Indian context.

KAIINOS, as a representative of gvSIG Association, got an opportunity to present gvSIG case studies in the session “Use of Open Source Geospatial Tools in Capacity building and in Strategic Applications “. KAIINOS highlighted the technical advantages of gvSIG, its flexible development environment, ease of use, cross platform compatibility, strong geoprocessing library etc in the presentation. But the actual strength of Open Source lies in the community and gvSIG has a very large user and developer community spread in and around 100 countries. Another unique strength of gvSIG is availability of support for custom application development and other services through gvSIG association (An association of SMEs with more than 60 collaborators and partners). The outreach efforts by the association in delivering trainings such as MOOC was also highlighted in the presentation.

gvSIG at IIIT Booth in FOSS4G India 2015gvSIG, which is very famous in Europe and South American countries, is still a newbie to Indian GIS community. KAIINOS after realizing the strengths of gvSIG became member of the association with a two-point agenda. One to increase user base of gvSIG in the Indian geospatial community and the other is to develop cost effective solutions using the gvSIG technology. As part of increasing user base of gvSIG in India, KAIINOS has been putting up gvSIG exhibition material like posters in the conferences held in India.

 


Filed under: community, english, events, gvSIG Association, gvSIG Desktop

by ggowtham at June 25, 2015 10:35 AM

gvSIG Team

On the road to gvSIG 2.3

gvSIG_23

As we announced with the publishing of gvSIG 2.2, and following the current policy at the gvSIG project for releasing two versions every year, we plan to release gvSIG 2.3 in December.

The objective is to dedicate the odd versions for deep changes that allow to extend the use field of gvSIG.

For this version we are working on the necessary changes to have an official gvSIG distribution for Mac and for Windows 64 bits available. They are significant changes related to the raster and projection libraries, and we hope they allow us to have these new gvSIG distributions.

We are making changes  related to the geometry support too, in order to solve several problems that have appeared at multi-geometries, as well as include the possibility to work with the M coordinate. This last issue is related to the dynamically segmentation functionality, that we want to include in gvSIG. It will mean a valuable contribution for all the works related to network analysis (roads, railways…).

And what will gvSIG 2.3 have? Well, it will depend on you in a big part, on the development contributions and economical resources that are contributed to the project, that means directly or through contracting of services. The gvSIG Association maintains a team that develop every gvSIG version thanks to all the entities that bet on the professional services that we offer mainly. Bet on the gvSIG Association is to have the best professionals… and besides contributing to the technological evolution of gvSIG.


Filed under: english, gvSIG Desktop

by Mario at June 25, 2015 08:39 AM

June 24, 2015

Blog italiano di gvSIG

Verso gvSIG 2.3

gvsig_23

Come annunciato con il rilascio di gvSIG 2.2, e vista la politica di rilasciare due versioni di gvSIG all’anno, abbiamo deciso di pubblicare gvSIG 2.3 nel prossimo mese di dicembre.

L’intenzione è quella di dedicare le versioni dispari ai cambiamenti più profondi che ampliano l’ambito di utilizzo di gvSIG.

Per questa versione stiamo lavorando sulle modifiche necessarie per rendere disponibili le distribuzioni ufficiali di gvSIG per Mac e Windows a 64 bit. Sono cambiamenti significativi e relativi alle librerie raster e alle proiezioni, che speriamo ci permettano di avere queste nuove importanti distribuzioni di gvSIG.

Stiamo anche facendo modifiche relative al supporto di geometrie, risolvere alcuni problemi che sono sorti con le multigeometrie così come poter essere in grado di lavorare con la misura M delle distanze. Questo ultimo aspetto è legato alla funzionalità di segmentazione dinamica che vogliamo aggiungere a gvSIG e che rappresenterà un contributo prezioso per tutte le operazioni inerenti le analisi delle reti (strade, ferrovie, …).

Cos’altro ci sarà in gvSIG 2.3? In gran parte dipende da voi attraverso contributi allo sviluppo e alle risorse economiche previste per il progetto, sia direttamente che tramite servizi. L’Associazione gvSIG ha una squadra che migliora il progetto gvSIG di versione in versione grazie soprattutto a tutti quei soggetti che si affidano ai nostri servizi professionali. Affidarsi all’Associazione gvSIG vuol dire contare su un gruppo di professionisti eccellenti… e contribuire anche allo sviluppo tecnologico di gvSIG.

by Giuliano Ramat at June 24, 2015 09:23 AM

gvSIG Team

Camino a gvSIG 2.3

gvSIG_23Como ya anunciamos con la salida de gvSIG 2.2, y siguiendo la actual política de publicación del proyecto gvSIG de liberar 2 versiones al año, fijamos como fecha para gvSIG 2.3 el mes de diciembre.

La intención es dedicar las versiones impares a cambios más profundos que permitan expandir el ámbito de uso de gvSIG.

Para está versión estamos trabajando en los cambios necesarios para poder tener distribución oficial de gvSIG para Mac y para Windows 64 bits. Son cambios significativos relacionados con las librerías de ráster y de proyecciones, y que esperamos que nos permitan tener estas nuevas distribuciones de gvSIG.

También estamos realizando cambios referentes al soporte de geometrías, de cara tanto a solucionar algunos problemas que se han presentado con multigeometrías, como a poder trabajar con la coordenada M. Esto último va relacionado con la funcionalidad de segmentación dinámica que queremos incorporar a gvSIG y que supondrá un valioso aporte para todos los trabajos relacionados con redes (carreteras, ferrocarril,…).

¿Y qué más tendrá gvSIG 2.3? Pues en gran parte depende de vosotros. De las contribuciones al desarrollo y de los recursos económicos que se aporten al proyecto, ya sean directos o mediante la contratación de servicios. La Asociación gvSIG mantiene un equipo que evoluciona versión a versión el proyecto gvSIG gracias principalmente a todas aquellas entidades que apuestan por los servicios profesiones que ofrecemos. Apostar por la Asociación gvSIG es disponer de los mejores profesionales…y además contribuir a la evolución tecnológica de gvSIG.


Filed under: gvSIG Desktop, spanish Tagged: gvSIG 2.3

by Alvaro at June 24, 2015 08:26 AM

June 23, 2015

Boundless Blog

Building an OpenLayers 3 Web App Without Writing Code

Building a web app to display your data can be a daunting task if you aren’t a developer, especially if you aren’t familiar with GIS concepts. At Boundless we’ve been working on ways to help our customers build such web maps, leveraging all of the great capabilities now available with the release of OpenLayers3 (www.openlayers.org) without needing to work from the command line.

One of the mechanisms we’ve developed is via a plugin for QGIS. This plugin allows you to publish a QGIS project as an OpenLayers 3 (“OL3”) web app simply by following some prompts and filling in a few forms. This requires no coding skills, however if you have some “dev chops” it is fully extensible (We’ll look at that in a future blog post).

My goal for this post is to walk you through the steps necessary to go from Project & Data to completed web app, all within QGIS using Boundless’s new Web App Builder plugin. The intent is to demonstrate the simplicity of building an app without needing to resort to code.

To start with you need to install QGIS 2.8.2 for the OpenGeo Suite. This is available (using Windows or Mac OS X 10.9 and higher) to Boundless customers at http://boundlessgeo.com/solutions/solutions-software/qgis/

Once installed the Web App Builder is accessible via the plugins drop down (click to zoom all images).
webapp1However before we can create an app we need a QGIS project with the supporting data. In this example we will be using some data from floods in Boulder County, Colorado in 2013 to create a flood event viewer.

I loaded three layers — Total Rainfall, Parcels with Flooding, and Inundated Areas. I also adjusted their symbology for better viewing over a basemap.
webapp2Now that we have our QGIS project let’s build an app!

First choose the Plugins menu -> Boundless -> Web App Builder. This will bring up the Web App Builder Dialogue and help us define our application.
webapp3This dialogue will help us step through the process of creating our app. We’ll start by titling our app, choosing a logo icon, and selecting a theme. The themes can be adjusted to meet your specific needs using the “Configure theme” button. In this example we are going to use the default values for the basic theme.

Under the Base Layers tab we can choose which base map service we would like to use and also select layers that can be used as overlays. For this app we are going to use the MapQuest aerial as our base layer to help show some of the terrain where the rain event occurred and provide the user with better context than a street map. The overlays provide access to services that include near real time weather, additional labeling, etc. For this example we will use the MapQuest labels overlay service to show city names, major roads, etc. Now let’s define the layers we want to place on top of the basemap.
webapp4In the Layers tab we configure the data layers that will be used in our application. By default all the layers we added to our QGIS project, except for basemaps, will show up in the list. In our case we only have a handful of layers — if you had many layers you can search for them using the search bar at the top of the dialogue box. We want to display all of the layers so we will leave them all checked.
webapp5Next we need to decide how the data for our app will be stored. Choosing the “Connect to this layer using” drop down we are presented with a number of choices.
webapp6The data we have for our flooding event viewer is a small static dataset, so using the file directly makes good sense. If we had a larger dataset or dynamic data we could choose to host it in GeoServer or a PostGIS DB. Those options give us greater customization for our data using the power of GeoServer. In our case the QGIS symbology will be created in the app using OL3 symbology and rendered by the application.

Now that we have defined how we want to connect to the layers we need to decide if we want popups and what content we would like to have presented in the popups. Clicking edit opens the popup editor dialogue. It is initially blank, but clicking ‘Add all attributes’ will populate it with a [field_name] pair for each field in the layer.
webapp7In our case we are going to have a popup that shows the Stream Name for the Inundated Areas, no popup for Parcels, and the Total Rainfall layer will have a popup that shows the Min and Max rainfall for that area.

Inundated Areas Popup expression:

<b>StreamName</b>: [StreamName]<br>

Total Rainfall popup expression:

<b>RainfallMin</b>: [RainfallMi]<br><b>RainfallMax</b>: [RainfallMa]<br>

Moving onto the widgets tab we see a large number of controls, tools and widgets to choose from. Selecting a widget will add it to the app, while right clicking on a widget will give you configuration options.
webapp8There’s obviously a lot here – we’ll save exploring widgets for a later post. For the purposes of this posting we are going to use with the default controls and configure the Layers List to allow the user to change the opacity of the layers.
webapp9Let’s add an About Panel widget to the application, and edit the content to let users know more about what they are looking at.
webapp10Once we have configured the controls and widgets we move to the Deploy tab. This tab is used to configure the connections to PostGIS and GeoServer. In our case we are not publishing our data into either PostGIS or GeoServer so we can skip this and move to settings.
webapp11The settings page gives us the opportunity to define how we want to deal with the Extent, zoom levels, and layer styling. For our application we are going to accept all of the defaults.

We’ve finished configuring our application, now let’s preview the app and see how it looks.
webapp13This sample application looks ready to go! If we wanted to make any changes we can step back and change any of the configurations to meet our needs and preview again. Once the application is configured and ready to be published, click Create App. The web app builder will prompt you for a location to save the files, build your application, and ask if you would like to view it.

We have a completed application ready for use, executed with a few clicks of the mouse and filling in some forms. At no point during this process was coding needed.

To find out more about the Web App Builder plugin contact Boundless at sales@boundlessgeo.com.

The finished 2013 Boulder County Flood Viewer can be viewed at http://wilson.boundlessps.com:8080/BoulderCountyFloods2013/

The post Building an OpenLayers 3 Web App Without Writing Code appeared first on Boundless.

by Aaron Miller at June 23, 2015 01:54 PM

June 22, 2015

gvSIG Team

Look for your address or location in gvSIG using Scripting!

In an previous post, we spoke about the utility of the “geopy” library for Geocoding in gvSIG 2 using scripting.

Now, with the next script we are going to search addresses or towns and gvSIG will zoom to that point.

geopy

The first step will be to install the GeoPy library in our computer. For that we have to download the “geopy-1.7.1-patched-for-gvSIG-2.1.0.zip” file and unzip it in the folder:

gvSIG/plugins/org.gvsig.scripting.app.extension/lib/

at the home folder of our user (in that lib folder we will have the geopy and simplejson folders finally). If we had gvSIG opened we have to close it and run it again.

Depending on the operating system, we can find that gvSIG folder in:

  • Linux: /home/MY_USER
  • Windows: C:\Document and Settings\MY_USER or C:\Users\MY_USER

We remember that this library uses the Google addresses browser. It also has its defects like confusions in addresses or the necessity to have an online connection.

Look for any address in gvSIG!capture27

Once the libraries are installed, we will run gvSIG, and we will go to the Scripting Composer (Tools->Scripting->Scripting Composer menu), we will create a script (File->New), with the name that we want (for example ‘Address browser’), and we will add this source code on it:

from gvsig import *
from geopy.geocoders import get_geocoder_for_service
from commonsdialog import *
from geom import *

def main(*args):

    # Google v3: from address to coordinates
    address = inputbox("Search Address", "Search Address",1)
    geolocator = get_geocoder_for_service("googlev3")
    location = geolocator().geocode(address)

    print"Address: ", (location.address), "Coordinates: ", ((location.latitude, location.longitude))

    geomPoint = createPoint(location.longitude, location.latitude,)
    centerView(currentView(), geomPoint.buffer(0.0005))

def centerView(view, geom):
    view.getMap().getViewPort().setEnvelope(geom.getEnvelope())

Then we will open a View in gvSIG, that will be in geographical coordinates on WGS84 (EPSG: 4326) for the correct working, because they are the coodinates that the library gives.

On the View, with the layers included, we will open the scripting launcher (Tools->Scripting->Scripting Launcher menu), and we will run the script that we have created (doble-clicking on it). Once the script has been run, it will ask for the address or town through a text box, and it will center the View to the point finally.

We hope you enjoy this tool!


Filed under: development, english, gvSIG Desktop, scripting

by Mario at June 22, 2015 10:35 AM

GeoSolutions

Meet GeoSolutions at FOSS4G Europe 2015 in Como!

foss4gComo2

Dear Reader, GeoSolutions is proud to announce that we will take part in 2015 FOSS4G Europe in Como, Italy, from 14th to 17th July. We will give one workshop and two presentations on GeoServer, here below you find the details. Workshop
  • GeoServer on steroids: getting the best out of GeoServer. 14th July Afternoon, W08,  with Andrea Aime - This workshop will show how to get from a basic set up to a battle ready, rock solid installation by showing the ropes an advanced user already mastered.
  Presentations
  • Advanced Cartographic Rendering in GeoServer. 15th July, Room VS.9, 2:50 PM, Andrea Aime - This presentation will provide hints, examples and enough information to master SLD in order to create beatiful maps with GeoServer.
  • Managing MetOc and Remote Sensing data with GeoServer. 17th July, Auditorium 2, 11:10 AM, Simone Giannecchini -  This presentation will provide detailed information on how to ingest and configure spatio-temporal data in GeoServer, to be served using OGC services, with examples from WMS and WCS services.
  You can get the full details about all the workshops here and find the complete presentations' program here. If you want further information, don't exhitate to contact us. Looking forward to see you in Como! The GeoSolutions Team, 320x100_eng

by Andrea Filosa at June 22, 2015 10:00 AM

gvSIG Team

¡Busca tu dirección o población en gvSIG mediante Scripting!

En un post anterior comentamos la utilidad de utilizar la librería “geopy” para la geocodificación de direcciones mediante Scripting en gvSIG 2, su uso básico y utilización.

Con el siguiente script vamos a realizar una búsqueda de esta dirección o población y haremos que gvSIG haga un centro de la vista en ese punto que nos devuelve la  petición.

geopy

Como primer paso deberemos instalar la librería GeoPy en nuestro equipo si no lo habíamos hecho. Para ello deberemos descargar el fichero “geopy-1.7.1-patched-for-gvSIG-2.1.0.zip” y descomprimirlo en la carpeta:

gvSIG/plugins/org.gvsig.scripting.app.extension/lib/

que encontraremos en el home de nuestro usuario (en dicha carpeta lib deberemos tener finalmente las carpetas geopy y simplejson). Si tenemos ya arrancado gvSIG deberemos cerrarlo y volverlo a arrancar.

Según el sistema operativo podemos encontrar dicha carpeta gvSIG en:

  • Linux: /home/MI_USUARIO
  • Windows: C:\Document and Settings\MI_USUARIO o C:\Users\MI_USUARIO

Recordamos que esta librería tiene la potencia del buscador de direcciones de Google, ya que utiliza su motor. También tiene sus defectos como confusiones en direcciones por parte del buscador o la necesidad de una conexión online.

¡Busca cualquier dirección con gvSIG!capture27

Una vez tengamos las librerías instaladas arrancaremos gvSIG, iremos al Scripting Composer (menú Herramientas->Scripting->Scripting Composer), crearemos un nuevo script (File->New), con el nombre que queramos (por ejemplo ‘Buscador de direcciones’), y añadiremos el siguiente código en él:

from gvsig import *
from geopy.geocoders import get_geocoder_for_service
from commonsdialog import *
from geom import *

def main(*args):

    # Google v3: de direccion a coordenadas
    address = inputbox("Search Address", "Search Address",1)
    geolocator = get_geocoder_for_service("googlev3")
    location = geolocator().geocode(address)

    print"Direccion: ", (location.address), "Coordenadas: ", ((location.latitude, location.longitude))

    geomPoint = createPoint(location.longitude, location.latitude,)
    centerView(currentView(), geomPoint.buffer(0.0005))

def centerView(view, geom):
    view.getMap().getViewPort().setEnvelope(geom.getEnvelope())

Después iremos a una Vista en gvSIG, que deberá estar en coordenadas geográficas en WGS84 (EPSG: 4326) para que funcione correctamente, ya que son las que nos devuelve la librería.

En la vista, con las capas insertadas, abriremos el lanzador de scripts (menú Herramientas->Scripting->Scripting Launcher), y ejecutaremos el script que acabamos de crear (con doble click sobre él). Una vez ejecutado el script pedirá mediante un cuadro de texto la dirección o población a buscar, para después realizar la petición y hacer un centrado a este lugar en la Vista.

¡Esperamos que os sea útil esta herramienta!


Filed under: development, gvSIG Desktop, scripting, spanish

by Óscar Martínez at June 22, 2015 10:00 AM

From GIS to Remote Sensing

Updated the User Manual of the Semi-Automatic Classification Plugin v. 4.3.3: New Tutorials


I have updated the User Manual of the Semi-Automatic Classification Plugin v. 4.3.3.
It is possible to download the User Manual (licensed under a Creative Commons Attribution-ShareAlike 4.0 Unported License) in English from this link, and an online version in English is available here.
Also, I am preparing new video tutorials.

by Luca Congedo (noreply@blogger.com) at June 22, 2015 08:00 AM

June 21, 2015

From GIS to Remote Sensing

Minor Update: Semi-Automatic Classification Plugin v. 4.3.3

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



Following the changelog:
-fixed interface issues

This update fixes some small issues with the interface.

Please, remember that a Facebook group and a Google+ Community are available for sharing information and asking for help about the Semi-Automatic Classification Plugin.

by Luca Congedo (noreply@blogger.com) at June 21, 2015 05:21 PM

Free and Open Source GIS Ramblings

QGIS 2.10 symbology feature preview

With the release of 2.10 right around the corner, it’s time to have a look at the new features this version of QGIS will bring. One area which has received a lot of development attention is layer styling. In particular, I want to point out the following new features:

1. Graduated symbol size

The graduated renderer has been expanded. Formerly, only color-graduated symbols could be created automatically. Now, it is possible to choose between color and size-graduated styles:

Screenshot 2015-06-21 18.39.25

2. Symbol size assistant

On a similar note, I’m sure you’ll enjoy the size assistant for data-defined size:

Screenshot 2015-06-21 23.16.10 Screenshot 2015-06-21 23.16.01

What’s particularly great about this feature is that it also creates a proper legend for the data-defined sizes:

Screenshot 2015-06-21 23.18.46

3. Interactive class exploration and definition

Another great addition to the graduated renderer dialog is the histogram tab which visualizes the distribution of values as well as the defined class borders. Additionally, the user can interactively change the classes by moving the class borders:

Screenshot 2015-06-21 18.43.09

4. Live layer effects

Since Nyall’s crowd funding initiative for live layer effects was a resounding success, it is now possible to create amazing effects for your vector styles such as shadows, glow, and blur effects:

Screenshot 2015-06-21 18.45.22

I’m very much looking forward to seeing all the new map designs this enables on the QGIS map Flickr group.

Thanks to everyone who was involved in developing and funding these new features!


by underdark at June 21, 2015 05:02 PM

Torsten Rahn

GCI 2014 and Grand Prize Trip

KDE Project:

Many pre-university students have participated in Google Code-In (2014) again and for many of them it has been the first opportunity to make contributions to Free Software and Open Source projects. In opposite to Google Summer of Code the GCI program is organized as a worldwide contest where students at the age of 13-17 years take the challenge to complete as many software development tasks from their mentor organizations as possible. These software development tasks are provided by Open Source Projects that are approved as mentor organizations. And at the end of 2014 KDE has participated as a mentor organization for the fifth year.





The most recent edition of Google Code-In, GCI 2014 has again been very successful: As Heena Mahour described in her Google Code-in 2014 wrap up with KDE there have been more than 277 tasks created by KDE mentors for the students which covered all aspects of the software development cycle and which ranged from creating source code to documentation, research, quality assurance and user interface tasks. It was amazing to see how the students solved nearly all of them and helped to improve KDE applications significantly.





As in previous years the top 24 performers became Grand Prize Winners and won a trip to Google Headquarters in Mountain View, California! In the KDE community the Marble Virtual Globe developers are usually actively involved with GSOC and GCI mentorship. Two of our students - Mikhail Ivchenko and Ilya Kowalewski - have made extraordinary contributions to Marble: They had worked very hard and contributed several important features to Marble - see e.g. Mikhail's blog post about the Tour (don't miss to watch the video!) and Ilya's blog about the Measure Tool improvements. And since they also earned most points they became Grand Prize Winners.
This year I was the happy one who went to Mountain View as a KDE mentor between June 7-10. And the trip was a great opportunity to learn more about the other mentors and the winning students (they were accompanied by a parent each) and to share more about our Free Software work in the KDE project. The Grand Prize Winner trip was lovingly organized by Stephanie Taylor and other members of the Google Open Source Programs Office: It began with a meet-and-greet event on Sunday evening in San Francisco to get to know everyone. On Monday we visited Googleplex in Mountain View. And on Tuesday we had a fun day in San Francisco where we had the choice to visit the Exploratorium, Alcatraz or went on a Segway tour through San Francisco. Being a science guy I picked the Exploratorium. On Wednesday it was time to say goodbye already after enjoying another round of Googler talks, delicious food and swags at the Google San Francisco Office. The whole experience was just awesome and I'd like to thank Stephanie, Carol, Cat and all the other Googlers for organizing this event and for giving us the opportunity to join it.

by torsten rahn at June 21, 2015 09:16 AM

June 20, 2015

GeoExt Team

GeoExt 3 Codesprint - Day 2 and 3


Day 2 and 3 of the GeoExt 3 Codesprint brought a lot of useful outcome. After the sprinters had to do a lot of discussion work on day 1 the following two sprint days could be used to implement a lot of stuff. Here is a list of tasks which were already tackled:

Investigations on an approach to use an ExtJS "Universal App" (optimized for desktop and mobile) with GeoExt components seemed very promising.

First research work for vector support in the PrintProvider class has been done.

A lot of work has been invested on the data models especially in combination with the LayerTree.

A Popup class to show georeferenced popups on the map has been implemented.

A LayerList class for mobile devices has been written.

The FeatureRenderer class has been done, including examples and tests.

A website has been setup for the project.

A lot of examples have been created. Some of them are published on the project website. Some more are following the next days.

The license had to be switched to GPLv3 because Sencha removed the FLOSS exception, which allowed us to license GeoExt under BSD before.


So all in all a really great result of the sprint! Thanks to all sprinters, who worked on this.


But the sprinters did not just work. On Thursday evening was a great social event at Braushaus Bönnsch where the sprinters could enjoy the local food and beer.



To sum it up:
The GeoExt 3 Codesprint was a big and important step for the project! A solid foundation for the future of GeoExt has been created. Stay tuned!

Last but not least a big thank you to all our sponsors. Without their input this sprint would not have been possible. And thanks to terrestris, for beeing such a great host (especially chef Till) .

by geofootballer (noreply@blogger.com) at June 20, 2015 10:39 AM

June 19, 2015

OSGeo News

GDAL/OGR 2.0.0 released

by jsanz at June 19, 2015 08:08 AM

Gis-Lab

Релиз GDAL 2.0


Сегодня (19.06.2015) состоялся релиз GDAL 2.0. GDAL это программная библиотека абстракции для работы с большим количеством растровых и векторных форматов геоданных.
Основные доработки вошедшие в новый релиз:

  • Обобщенная модель для растровых и векторных источников
  • Поддержка кривых
  • Поддержка новых типов данных в атрибутах через подтипы
  • Улучшение RasterIO (сглаживание)
  • Поддержка времени с миллисекундной точностью
  • Были добавлены новые драйверы для растровых и векторных источников и д.р.

Подробнее читаем в 2.0.0-News.

by bishop at June 19, 2015 07:08 AM

June 18, 2015

Even Rouault

GDAL/OGR 2.0.0 released

On behalf of the GDAL/OGR development team and community, I am pleased to announce the release of GDAL/OGR 2.0.0.  GDAL/OGR is a C++ geospatial data access library for raster and vector file formats, databases and web services.  It includes bindings for several languages, and a variety of command line tools.

The 2.0.0 release is a major new feature release with the following highlights:

 * GDAL and OGR driver and dataset unification  
 * 64-bit integer fields and feature IDs
 * Support for curve geometries      
 * Support for OGR field subtypes (boolean, int16, float32)      
 * RasterIO() improvements : resampling and progress callback      
 * Stricter SQL quoting      
 * OGR not-null constraints and default values      
 * OGR dataset transactions      
 * Refined SetFeature() and DeleteFeature() semantics      
 * OFTTime/OFTDateTime millisecond accuracy
 * 64bit histogram bucket count      

 * New GDAL drivers:
    - BPG: read-only driver for Better Portable Graphics format (experimental)
    - GPKG: read/write/update capabilities in the unified raster/vector driver              
    - KEA: read/write driver for KEA format               
    - PLMosaic: read-only driver for Planet Labs Mosaics API               
    - ROI_PAC: read/write driver for image formats of JPL's ROI_PAC project               
    - VICAR: read-only driver for VICAR format               

 * New OGR drivers:
    - Cloudant : read/write driver for Cloudant service               
    - CSW: read-only driver for OGC CSW (Catalog Service for the Web) protocol               
    - JML: read/write driver for OpenJUMP .jml format               
    - PLScenes: read-only driver for Planet Labs Scenes API                
    - Selaphin: read/write driver for the Selaphin/Seraphin format
               
 * Significantly improved drivers: CSV, GPKG, GTiff, JP2OpenJPEG, MapInfo, PG,
SQLite/Spatialite

 * Upgrade to EPSG 8.5 database

 * Fix locale related issues when formatting or reading floating point numbers

You can also find more complete information on the new features and fixes in the 2.0.0.

The release can be downloaded from:
  * http://download.osgeo.org/gdal/2.0.0/gdal200.zip - source as a zip
  * http://download.osgeo.org/gdal/2.0.0/gdal-2.0.0.tar.gz - source as .tar.gz
  * http://download.osgeo.org/gdal/2.0.0/gdal-2.0.0.tar.xz - source as .tar.xz
  * http://download.osgeo.org/gdal/2.0.0/gdalautotest-2.0.0.tar.gz - test suite
  * http://download.osgeo.org/gdal/2.0.0/gdal200doc.zip - documentation/website

As there have been a few changes to the C++ API, and to a lesser extent to the C API, developers are strongly advised to read the migration guide.

by Even Rouault (noreply@blogger.com) at June 18, 2015 08:59 PM

GeoServer Team

GeoServer 2.6.4 Released

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

GeoServer 2.6.4 is a maintenance release of GeoServer recommended for production deployment. This release contains IMPORTANT SECURITY FIXES so please upgrade.

Thanks to everyone who took part by contributing fixes, new functionality, and documentation. Notable changes:

Thanks to Ben Caradoc-Davies (Transient Software Limited) for this release. Thanks also to Kevin Smith (Boundless) for releasing GeoWebCache 1.6.2 and to Jody Garnett (Boundless) for building the GeoServer 2.6.4 DMG.

About GeoServer 2.6

Articles and resources for GeoServer 2.6 series:

by Ben Caradoc-Davies at June 18, 2015 08:37 PM

Boundless Blog

OpenGeo Suite 4.6.1 Now Available

Boundless is announcing the general availability of OpenGeo Suite 4.6.1 for all customers and OpenGeo Suite users. This is a patch release primarily intended to address an identified security vulnerability in GeoServer:

  • GEOS-7032: Reports the ability to request sensitive files using a careful crafted WFS GetFeature request when running GeoServer as root (which is not recommended for production systems). Please note OpenGeo Suite installs GeoServer using the “tomcat” user, limiting the scope of this vulnerability for our customers. While this reduces the risk, we still encourage all users to update their systems.

Boundless Customers
At this moment this security update is available via Boundless as part of OpenGeo Suite 4.6.1, which includes the latest GeoServer 2.7.

Boundless is committed to the security and success of our customers, and will continue to provide early access to important updates and fixes.

GeoServer Community
GeoServer will include this fix in the GeoServer 2.6.4 maintenance release scheduled for availability later today. Those making use of GeoServer 2.7 are encouraged to update to 2.7.2 when it is released later this month.

For more information on availability please see the community release schedule.

UPDATE 06/29/15 – See project blog on GeoServer XEE vulnerability for patched 2.5.x, 2.6.x and 2.7.x releases.

The post OpenGeo Suite 4.6.1 Now Available appeared first on Boundless.

by Jody Garnett at June 18, 2015 05:43 PM

Jackie Ng

For MapGuide, OpenLayers 3 is ready for prime-time.

As some of you may recall, nearly two years ago I landed in MapGuide support for OpenLayers 3.

However, this support was partial as it only targets un-tiled Map Definitions. None of the tiling mechanisms in OpenLayers 3 were compatible with the tiling scheme used by MapGuide meaning OpenLayers 3 cannot consume non-XYZ tiles from MapGuide ...

... Or so I thought.

It turns out that it is indeed possible to consume non-XYZ tiles from MapGuide, here's one such example using the just released v3.6.0 of OpenLayers.

What this means is that OpenLayers 3 is at feature parity with OpenLayers 2 in terms of MapGuide support, meaning it has the core functionality we need to build a MapGuide client mapping application out of.

Many thanks to Andreas Hocevar of Boundless for the code sample.

by Jackie Ng (noreply@blogger.com) at June 18, 2015 03:00 PM

Jackie Ng

MapGuide tidbits: SQLite interoperability

Sometimes, your data has to escape the MapGuide/FDO ecosystem and be consumed from other geo-software. If the limitations of the omnipresent SHP file format leave a lot less to be desired, then the next best thing is SQLite databases.

The reason I say this is because:

  • SQLite files (in our context) are just regular SQLite database with some special tables so mapping software know how to read features from them. You don't need FDO to peek inside the structure of a SQLite database. Any other SQLite database tool or library can get at the data as well.
  • SQLite is a relational(-ish) database. So features you'd expect in an RDBMS (eg. views) are also available in SQLite. Can you say that about SHP files?
  • The biggest reason. There's an OGR driver for SQLite, and it understands FDO's flavor of SQLite databases, and if your mapping software isn't using FDO, it's using GDAL/OGR!
Sure, there's a few quirks here and there, but they can be worked around or fixed.

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

Jackie Ng

MapGuide tidbits: Fixing SQLite data files with no coordinate systems

From the "I lost several hours discovering this so you don't have to" department

Today, I was tasked with producing some KML files. The spatial data was in SQL Server and it needed to be married with some CSV files I had, but I wanted it to get into a more portable format so I can do the bulk of the styling work in MapGuide without having to touch the SQL Server again.

Due to some quirks in this SQL Server database, the SQLite file that were produced from an FDO Toolbox bulk copy did not have any spatial contexts in them. This turns out to be a big problem because MapGuide has to know what coordinate system your data is in for rendering and various outputs to work, especially if coordinate system transformation is required. You can fix and/or flub such a coordinate system using the Coordinate System override section of the Feature Source, but this only works if MapGuide/FDO can read a spatial context from the data store for you to stick in a replacement coordinate system in.

This actually broke the KML support in MapGuide I was intending to use because it needs to know if your data is LL84 or transformable to it and since the SQLite file had none, MapGuide didn't do anything with the data when I wanted a KML export of it. Rather than waste time re-exporting this data in another format, I wanted to see if such files can be "fixed" in-place and be made usable again.

Since SQLite files are actual relational(-ish) databases, you can open them any SQLite database viewer^ (there's a lot of them) to take a look at the contents. When you open such a file, you'll see various tables representing each of your feature classes and some special tables:

  • fdo_columns
  • geometry_columns
  • spatial_ref_sys
fdo_columns contains the FDO property metadata for each column of each table. Without this table, the SQLite FDO provider will treat all columns as strings, even if your column stores numbers, dates, etc.

geometry_columns contains the metadata for the geometry columns.

spatial_ref_sys contains coordinate system information.

In the event that MapGuide reads 0 spatial contexts from your SQLite data store, it's because:
  • There are no rows in spatial_ref_sys. Each row in this table is read as a spatial context
  • Any rows in geometry_columns either have an srid of -1 or an srid with no match in spatial_ref_sys
So with this knowledge, to "fix" such files so MapGuide knows what coordinate system they're in:
  • Insert a new row into spatial_ref_sys
  • Update the srid column of all rows in geometry_columns to the srid of the row you inserted into spatial_ref_sys
Or if none of what I just said made sense, just run the commands in this gist in your SQLite database admin tool of choice. Once done, your SQLite database will have a spatial context which you can then put an override in your Feature Source so that MapGuide knows what coordinate system to interpret your data in.

^ Though FDO Toolbox can technically be used to admin SQLite databases, I am suggesting alternative tools as I am not sure whether the SQLite FDO provider will let you "fix" something that it has an already-open connection to, nor do I know if the SQL commands the fix this will work as intended when going through the SQLite FDO provider. Better to be safe than sorry.

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

    GeoExt Team

    GeoExt is getting the 3

    GeoExt 3 Codesprint 

    Yesterday a group of GeoExt developers came together in Bonn (Germany) to set the foundation for the new GeoExt 3 which will be built upon ExtJS 6 and OpenLayers 3. In Bonn itself 9 sprinters attended on-site and one sprinter worked remotely from Greece.

    The Codesprint has been sponsored by several companies and agencies (either by providing developer manpower or by money donations):

    Thank you for supporting GeoExt!

    Day 1 - Getting Started

    After a decent warmup we had some strategic conversations before hitting the keys. First of all we defined the objectives of the sprint in order to get a kind of prioritized roadmap. After that Kai and Marc presented their work on ExtJS 6 and OpenLayers 3 which tackeled a lot of the architectural project setup (e. g. the package structure and a test suite) and even some class impementations (e.g. a MapPanel and a basic LayerTree), which were demonstrated as working examples. The sprinters agreed to use this pre-work as a good starting point for the implementation stage and therefore we merged the code of Marc and Kais work into the project master.
    After that a lot of strategic discussions were done, which were very productive and necessary to get a common understanding of what we want to achieve.

    Later the day we started hacking and tackled the following tasks:

    The MapPanel class has been reworked to an ExtJS Component and is no more a ExtJS Panel in order to avoid overnesting, which is a first step for mobile support.

    The implementation of a FeatureRenderer started and will be continued the next days.

    First tests for mobile support have been done.

    A script for generating example skeletons has been implemented.

    Work on the print package started and will be continued the next days.

    The GeoExt package (to use in Sencha Cmd architectures) is now available on remote resource.


    So a lot has been done but still many more to do. Stay tuned! 



    Special thanks to the "GeoExt chef Till", who supported us with an excellent soup for lunch!


    by geofootballer (noreply@blogger.com) at June 18, 2015 01:12 PM

    gvSIG Team

    5as Jornadas Argentinas de gvSIG. “Tecnología libre para las ciencias y la educación”

    Inicio_web_Argentinas_2015Los días 24 y 25 de septiembre de 2015 se celebrarán las 5as Jornadas Argentinas de gvSIG en Mendoza, bajo el lema “Tecnología libre para las ciencias y la educación”.

    Ya está abierto el periodo para el envío de propuestas para comunicaciones para las Jornadas. Desde hoy pueden enviarse las propuestas a la dirección de correo electrónico jornadas.argentina@gvsig.org, que serán valoradas por el comité científico de cara a su inclusión en el programa de las Jornadas. Toda la información sobre las normas para la presentación de comunicaciones puede consultarse en el apartado de Comunicaciones de la web. El periodo de recepción de resúmenes finalizará el próximo 29 de julio.

    El próximo día 24 de junio se abrirá el periodo de inscripción. La inscripción a estas jornadas es gratuita.

    ¡Os esperamos!


    Filed under: community, events, gvSIG Desktop, spanish

    by Mario at June 18, 2015 11:24 AM

    GeoTools Team

    GeoTools 12.4 Released

    The GeoTools community is pleased to announce the availability of GeoTools 12.4:

    This release, which is also available from our Maven repository, is made in conjunction with GeoWebCache 1.6.2 and GeoServer 2.6.4. This is a maintenance release of the GeoTools 12 series recommended for production systems.

    A few highlights from the GeoTools 12.4 release notes:
    • Improved handling of the van der Grinten projection
    • Layer-by-layer control of raster interpolation
    • Dynamic raster styling with CQL expression support for color map entries
    • Stability improvements for Oracle curves, geometry decimation, JSON support, GeoTIFF, and World image formats
    • Other fixes: see the release notes for details
    Thanks to Ben Caradoc-Davies (Transient Software Limited) for this release. Thanks also to Jody Garnett (Boundless) for help with Jira release automation.

    About GeoTools 12

    by Ben Caradoc-Davies (noreply@blogger.com) at June 18, 2015 04:34 AM

    June 17, 2015

    Boundless Blog

    A QGIS Clip Show

    In light of our announcement of support and interoperability for QGIS 2.8.2 with our OpenGeo Suite, it’s a good opportunity to look back at highlights of past posts to remind existing users of past tips and demonstrate to new users the power of QGIS.

    • In our most recent post, Anthony Calamito highlights 10 different examples how QGIS can serve the majority of analysts’ needs at significant savings
    • Victor Olaya provided a preview of the MGRS plugin we announced with 2.8.2 support
    • Aaron Miller provided a real-life case study demonstrating how QGIS can assist with supply chain intelligence
    • We provided a 4-part series comparing QGIS to Esri ArcGIS, including visualization, cartography (my personal favorite – Halloween map!), editing, and analysis
    • Victor Olaya also described OpenGeo Explorer, our plugin to help users configure and manage OpenGeo Suite

    At risk of stating the obvious, we’re huge believers in QGIS here. We’re seeing firsthand QGIS capture market share. We’re seeing QGIS growing at a rapid pace in adoption by academia, creating entire generations of users. I’d also like to give a tip of the cap to the QGIS community, the most vibrant and self-sustaining of all open source GIS communities. Boundless is committed to supporting and continuing to build on QGIS capabilities, and we welcome any questions about our capabilities.

    The post A QGIS Clip Show appeared first on Boundless.

    by Sean Brady at June 17, 2015 03:57 PM

    gvSIG Team

    What to do when we get an error in gvSIG

    If we get an error in gvSIG, the most recommendable thing is to send it to the users mailing list of the project, where there’s a huge group of users, and developers can reply directly too.

    Before sending the error to the mailing list we can check if any user has got it previously and it has been solved. Many times it’s the same error got by other users and the solution has been told at the mailing list. For that, we can see the archives of the mailing list: http://osgeo-org.1560.n6.nabble.com/gvSIG-users-f4102847.html and look for our problem at the upper right-hand corner (indicating only to search at the gvSIG users mailing list).

     

    What to send to the users mailing list

    In case we don’t find the solution at the archives of the mailing list we will send the mail to the list (it’s necessary to register previously from http://listserv.gva.es/mailman/listinfo/gvsig_internacional). To find the causes of the error easily we have to:

    • Indicate at the subject of the e-mail the tool where we have got the error and the gvSIG version (for example, “gvSIG 2.1: Error opening a project” or “gvSIG 2.2: Error at the Merge geoprocess”), in order to get an answer as soon as possible.
    • Tell in detail the steps that have been followed before the error (in case it has happened when opening or saving a project, more information has to be provided as much as possible about what layers there were and how they had been created).
    • Attach the next files (it’s recommendable to zip them in an only .zip file, in order to reduce their size):
          • gvSIG.log: This file is removed every time gvSIG is opened, so we must send it before opening a new gvSIG session. If we are working on the same session for a long time, several gvSIG.log files will be created (with a number at the end, gvSIG.log.1, gvSIG.log.2…). We must attach all of them.
          • gvSIG-launcher.log
          • gvSIG-environ.info
          • .gvsproj project file: In case the problem has been when opening or saving a project.

    The first three files are at the gvSIG folder of the user one in our computer, that will be different depending on the operating system:

    • Windows XP: C:\Documents and settings\[user]\gvSIG
    • Windows Vista, 7 and 8: C:\Users\[user]\gvSIG
    • Linux: /home/[user]/gvSIG

    If it’s a very concrete error, like a geoprocess or opening a project, that can be replicated easily, it’s recommendable to close gvSIG, open it again, follow only the steps until the error, and close gvSIG, in order to reduce the gvSIG.log file and make the error detection easy. At this way, the file will contain only the information related to the error.

     

    Registering at the mailing list

    To send e-mails to the mailing list we must register previously from http://listserv.gva.es/mailman/listinfo/gvsig_internacional.

    We can change our preferences later if we don’t want to receive the e-mails. We will be able to send the doubts to the list, and consult replies from

    http://osgeo-org.1560.n6.nabble.com/gvSIG-users-f4102847.html.

    Apart from the errors, doubts and suggestions can be sent to the users mailing list too. There’s also a developers mailing list (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-devel, and the archives of this list is available in http://osgeo-org.1560.n6.nabble.com/gvSIG-developers-f4175719.html).


    Filed under: community, english, gvSIG Desktop, testing

    by Mario at June 17, 2015 12:27 PM

    Paulo van Breugel

    First release candidate of the upcoming GRASS GIS 7.0.1 version is out

    GRASS GIS 7.0.1 RC1 is the upcoming stability release and provides a series of stability fixes, manual improvements and a few language translations. This first release candidate GRASS GIS 7.0.1RC1 provides 168 fixes and improvements with respect to GRASS GIS 7.0.0. See here the announcement and further information. If you want to help testing or […]

    by pvanb at June 17, 2015 07:17 AM