We all know that QGIS is great for designing maps but did you know that QGIS is also great for interactive we maps? It is! Just check out qgis2leaf and qgis2threejs.

To give these two plugins a test run and try to learn some responsive web design, I developed a small concept page presenting cycle routes in 3D.

Qgis2leaf makes it possible to generate Leaflet maps from QGIS layers. It provides access to different background maps and it’s easy to replace them in the final HTML file in case you need something more exotic. I also added another layer with custom popups with images but that was done manually.

The web maps use data CC-BY-3.0: Land Kärnten – data.ktn.gv.at

Qgis2threejs on the other hand creates 3D visualizations based on three.js which uses WebGL. (If you follow my blog you might remember a post a while back which showcased Qgis2threejs rendering OSM buildings.)

This is a great way to explore elevation data. I also think that the labeling capabilities add an interesting touch. Controlling the 3D environment takes some getting used to, but if you can handle Google Earth in your browser, this is no different.

Image of Heiligenblut by Angie (Self-photographed) (GFDL (http://www.gnu.org/copyleft/fdl.html) or CC BY 3.0 (http://creativecommons.org/licenses/by/3.0)), via Wikimedia Commons

The aim of the Cátedra gvSIG is to create a meeting point for users interested in free space technologies. In order to foment an environment of shared knowledge and participating in the dissemination of free geomatics, the chair organizes this international contest to encourage all gvSIG users and free Geographic Information Systems users to share and give visibility to their work. Students and graduates in high school, professional training and university, as well as university professors and researchers from all countries can participate in this contest.

To enter to the competition you must meet the following requirements: Works must be done with free Geographic Information Systems and the subject of the work may address any area of knowledge. Works may have been made in 2015 or before, the papers may be presented collectively and individually and jobs may be sent in Spanish, Valencian or English. In the event the work is based on a new development done through free and open source GIS geospatial technologies, these papers must be subjected to GNU / GPL v3 license.

Among the selected works a prize of 500 euros will be awarded for each of the following categories:

1. Work produced by students of highschool or professional training
   
2. Final University’s Project (Bachelor, Degree or Master)
   
3. Doctoral thesis or research paper.

Submissions should be sent to gvsig@umh.es no later than November 1, 2015. Selected documents will be published in the repository of the Miguel Hernández University. The jury will evaluate the methodology, clarity and innovative nature of the work, assessing as well the relevance and applicability of the research. Winners will be announced in the next International gvSIG Conference [1]. For more information visit the contest page of the Chair (in Spanish [2]) or contact gvSIG (gvsig@umh.es) via email.

The post I Cátedra gvSIG Contest: Works with free GIS appeared first on Slashgeo.org.

En gvSIG 2.1 podemos instalar, entre las bibliotecas de símbolos disponibles, la denominada AIGA.  AIGA es el acronimo del American Institute of Graphic Arts.
AIGA es conocida por sus actividades de diseño técnico, específicamente en la creación de pictogramas del Departamento de Transporte de los Estados Unidos en 1979. Precisamente, basándonos en ese conjunto de pictogramas, hemos generado una nueva biblioteca de símbolos.
Los símbolos puntuales los hemos complementado con un conjunto de símbolos para líneas y rellenos inspirados en la paleta de color utilizada en el documento “Thinking inside the box. AIGA identity and branding guidelines“.
Para instalarlo, como es habitual, debemos utilizar el administrador de complementos de gvSIG.

Una vez instalado podremos utilizar símbolos como estos:

The aim of the Cátedra gvSIG is to create a meeting point for users interested in free space technologies. In order to foment an environment of shared knowledge and participating in the dissemination of free geomatics, the chair organizes this international contest to encourage all gvSIG users and free Geographic Information Systems users to share and give visibility to their work.

Students and graduates in high school, professional training and university, as well as university professors and researchers from all countries can participate in this contest.

To enter to the competition you must meet the following requirements: Works must be done with free Geographic Information Systems and the subject of the work may address any area of knowledge.

Works may have been made in 2015 or before, the papers may be presented collectively and individually and jobs may be sent in Spanish, Valencian or English.

In the event the work is based on a new development done through free and open source GIS geospatial technologies, these papers must be subjected to GNU / GPL v3 license.

Among the selected works a prize of 500 euros will be awarded for each of the following categories:

1. Work produced by students of highschool or professional training
2. Final University’s Project (Bachelor, Degree or Master)
3. Doctoral thesis or research paper.

Submissions should be sent to gvsig@umh.es no later than November 1, 2015.

Selected documents will be published in the repository of the Miguel Hernández University.

The jury will evaluate the methodology, clarity and innovative nature of the work, assessing as well the relevance and applicability of the research. Winners will be announced in the next International gvSIG Conference.

For more information visit the contest page of the Chair (in Spanish) or contact gvSIG gvsig@umh.es via email.

The 10th International gvSIG Conference were held some weeks ago in Valencia (Spain), where more than thirty communications were presented about different themes.

At the Conference there was a session specially dedicated to architecture. Different reports were presented about Geographic Information Systems in an architecture office, urban licenses or energy efficiency certificates, all of them very interesting projects.

All these presentations, as well as their recording, are available. They were concretely these ones:

- GIS applied to project management in an architecture office (PDF: 8.0 MB); VICENTE J. VALERO (Grado en Arquitectura Técnica)

- Geographic Information Systems for urban licenses management (PDF: 4.7 MB); PABLO PERUCHO (Grado en Arquitectura Técnica)

- GIS applied to energy efficiency certificates in the municipality of Llíria (PDF: 5.4 MB); MIGUEL ÁNGEL SIMEÓ (Grado en Arquitectura Técnica)

- Multicriterial metodology for the optimal location searching of a public site (ODP: 10.7 MB; PDF: 4.1 MB); RUBÉN HERNÁNDEZ (Grado en Arquitectura Técnica)

- Questions at this sessions:

We hope this information is useful for you!

This is my evolving overview of 3D Geospatial Open Standards with a focus on web technology: services, HTML5, WebGL. These are notes I keep within Evernote as part of the 3D Geospatial Notebook whose public link is: https://www.evernote.com/pub/justb4ever/3d-geospatial. For sure, resources are missing, let me know. These notes are synced from Evernote using Zapier, so formatting is a bit messy, sorry for that, though I completely revised this blog on jan 30, 2015.

The presentations by Emanuel Belo (Camp2Camp, links below) are an excellent start to get a global overview. He mentions the following categories of 3D standards and their organizations:

Geo: OGC

• 3D Portrayal Services (Proposals: WVS WMS-Like & W3DS WFS-Like) (Just: Now 3DPS)
• KML – XML/COLLADA
• CityGML – representation, storage, and exchange
• CZML (AGI/Cesium) ?

Geo: OSGeo

• TMS (Cesium Terrain Server z.B)

Web: Web3d

•  X3D – Extensible 3D Graphics

Graphics: Khronos Group

• COLLADA – eXchange / interoperability
• glTF – graphic language Transmission Format

Other

• TopoJSON

In the short time I am spending within the 3D domain I think another categorization could be 3D Web Services Standards and 3D Content/Format Standards. A lot of focus is usually on the latter. Within 3D Content/Format Standards my view is that there are the sub-categories based on stages within a 3D rendering pipeline, i.e. from raw source data like CityGML up to 3D-scene encodings like COLLADA and glTF. I see “Terrain” as a separate content category with encodings like height maps and TINs.

I think/hope that 3D Web Services will gain importance: services to request Content in various encodings plus Terrain data. Techniques like tiling (TMS/WMTS) are already very common within the geospatial world. With the latest developments in vector-tiling I see much potential, especially for terrain and textures (raster) draped on a terrain. Streaming as in video streaming, is not common within the geospatial world but may become of use especially in HTML5 apps (via web sockets?).

General
The following presentations by Emanuel Belo from Camp2Camp hit the nail on the head. The content lives up to the title.
Two versions available, video and slides from FOSS4G 2013, Nottingham (missed that unfortunately) and a later 2014 version.

https://www.youtube.com/watch?v=9CgU0zs8DlU 3D Web Services And Models For The Web: Where Do We Stand? Belo FOSS4G13
http://www.slideshare.net/camptocamp/3-d-web-services-and-models-for-the-web Belo – ditto slides [1]
http://www.geospatialworldforum.org/2014/presentation/geo3d/Emmanuel%20Belo%20M.pdf Belo – ditto 2014 version slides

Open Geospatial Consortium – OGC
For open geospatial standards the Open Geospatial Consortium, OGC, is the first standards body to look at. Their standards
are often aligned with corresponding ISO standards and more recently OGC started collaborating more closely with W3C.

At least two Standards Working Groups (WSGs) are dedicated to 3D. The more established
3D Information Management (3DIM, CityGML!)) and the probably lesser known 3D Portrayal SWG.

It should be noted and credited that most of the OGC 3D standards came out of the German GDI-DE project http://www.gdi-3d.de.
At this moment (jan 2015) two main OGC standards are of importance for 3D: CityGML and the draft standard for 3D Portrayal web services: 3DPS.

OGC – 3D Information Modeling – CityGML
“CityGML is a common information model and XML-based encoding for the representation, storage, and exchange of virtual 3D city and landscape models. CityGML provides a standard model and mechanism for describing 3D objects with respect to their geometry, topology, semantics and appearance, and defines five different levels of detail. Included are also generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. CityGML is highly scalable and datasets can include different urban entities supporting the general trend toward modeling not only individual buildings but also whole sites, districts, cities, regions, and countries.”
http://www.citygml.org

SWG: http://www.opengeospatial.org/projects/groups/3dimwg – 3D Information Management (3DIM) Domain Working Group
CityGML: http://www.opengeospatial.org/standards/citygml

OGC candidate 3D Standards | GeoConnexion
http://www.geoconnexion.com/articles/ogc-candidate-3d-standards
http://www.w3ds.org/doku.php

OGC – 3D Web Services – 3D Portrayal

SWG: http://www.opengeospatial.org/projects/groups/3dpswg – 3D Portrayal SWG.
Note the W3DS, WVS, WTS and WPVS are now all obsolete since they have been merged into a single web service standard: the 3D Portrayal Service (3DPS).

A draft version 1.0.0 is now (january 2015) out for public comment within OGC:
http://www.opengeospatial.org/standards/requests/130

“The 3D portrayal standard (3DPS) is an OGC service implementation specification targeting the delivery of 3D portrayals in an interoperable fashion. … When client and server(s) involved share a common set of capabilities, it becomes possible to view and analyze 3D geoinformation from diverse sources in a combined manner. …. The 3DPS combines the essential parts of the suggested W3DS and WVS into one common interface.” and

“ The Open Geospatial Consortium (OGC) and the Web3D Consortium have both been working to address the need for interoperability, as well as the content challenges of volume, access speed, and diversity of devices. The Web3D Consortium has focused on open standards for real-time 3D visualization, including streaming, and their members developed a Geospatial Component extension for X3D. The OGC has focused on developing a service interface to provide interoperable access to 3D geospatial data servers. In 2012, a group of OGC members, building on work done in both organizations, completed the 3D Portrayal Interoperability Experiment (3DPIE) to develop and evaluate best practices for 3D portrayal services.”

“The candidate OGC 3D Portrayal Service Standard is designed to support both client and server side rendering. For client-side rendering, the client requests a 3D model from the server. The server extracts the requested model from the 3D geodata server and generates a 3D scene graph including geometry and textures. Depending on the server’s capabilities, data formats such as X3D, KML and COLLADA can be used to retrieve the scene graph. The rendering of the scene is done on the client side. In a web client, X3DOM and/or XML3D can be used to integrate the scene into an immersive HTML5 experience. However, there are no fixed format requirements, opening the service for other technologies such as JSON-based glTF. For server side rendering, the client passes the requested content and view parameters to the server. The server then generates layered image depictions of the 3D environment for display on the client. In either scenario, the client’s user can query and navigate through the 3D content.”

Link to 3DPS v1.0.0 for public review on jan 29, 2015:

Public comment request: http://www.opengeospatial.org/standards/requests/130
Direct download 3DPS 1.0.0 draft: https://portal.opengeospatial.org/files/61884

For history reasons some notes kept on W3DS and WVS below.

A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata such as landscape models, city models, textured building models, vegetation objects, and streetfurniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates. 3D Scenes can be interactively displayed and explored by internet browsers with 3D plug-ins, or loadedinto virtual globe applications.

The Web View Service (WVS) is a portrayal service for three-dimensional geodata suchas landscape models, city models, vegetation models, or transportation infrastructure

models. A WVS server mainly provides 2D image representing a 3D view on a scene
constructed from 3D geodata that is integrated and visualized by the WVS server. In
addition to these color images of a 3D scene, a WVS server can advertise and deliver
complementary image layers that include geometrical or thematic information: e.g., depth
layers, surface normal data, or object id information.

OGC – 3D Portrayal Interoperability Experiment (3DPIE)
The OGC …. “3D Portrayal Interoperability Experiment (IE) successfully tested and demonstrated different mechanisms for the portrayal, delivery, and exploitation of 3D geodata based on open standards-based formats and services. …approaches for service-based 3D portrayal based on thedrafts for the candidate standards for 3D portrayal, Web 3D Service (W3DS) and WebView Service (WVS).”

Page: http://www.opengeospatial.org/projects/initiatives/3dpie
Report https://portal.opengeospatial.org/files/?artifact_id=49068

NB this ultimately lead to the development of the 3D Portrayal Standard which merged W3DS and WVS.

Open Source Geospatial Foundation – OSGeo
Although OSGeo.org is not a standards body, for years the Tiled Map Service TMS spec is intensively used, probably more than its OGC-counterpart WMTS…
http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification

TMS is finding its use in the 3D landscape not just for tiles containing 2D raster maps to be draped over a terrain, but also more and more as a container for height and (compressed) vector tiles. This is an important development, see e.g. Cesium Terrain Server and its two format-encodings for terrain-tiles:
https://github.com/AnalyticalGraphicsInc/cesium/wiki/Cesium-Terrain-Server

X3D – Web3D
“Extensible 3D (X3D) Graphics and Humanoid Animation (H-Anim) include a coordinated set of steadily evolving ISO standards. “

http://www.web3d.org/standards (mostly X3D, equiv with ISO/IEC 19775 (architecture and
abstract capabilities), 19776 (encodings), and 19777 (API)))

X3DOM
“X3DOM is an adaption of the X3D standard to (X)HTML, ensuring declarative 3D can
be used inside standards-compliant browser. It aims to support a large browser base and
decent X3D feature coverage, while working towards a common declarative 3D standard
in the Declarative 3D community WG at the W3C. The reference implementation is
maintained by Fraunhofer IGD and available under the open-source license MIT.”
http://www.x3dom.org/ –

WebGL
https://www.khronos.org/webgl/
“WebGL is a standard for programming in 3D with the browser as platform. The final
specification of the standard was published in 2010 and is defined by the Khronos Group,
a consortium which is also in charge of Open GL, Open CL and OpenGL ES (embedded
systems). WebGL provide a context into HTML5 canvas that is 3D Computer Graphics
capable without plug-in.”

Cesium
Although CesiumJS is mainly a client JavaScript framework based on WebGL and Dojo, there are also some useful standards originating from the project.

http://cesiumjs.org/data-and-assets/terrain/formats/quantized-mesh-1.0.html quantized mesh via TMS – for terrain services based on TINs.
https://github.com/AnalyticalGraphicsInc/cesium/wiki/CZML-Guide – CZML is a JSON schema for describing a time-dynamic graphical scene

Collada
“COLLADA™ defines an XML-based schema to make it easy to transport 3D assets between applications – enabling diverse 3D authoring and content processing tools to be combined into a production pipeline. The intermediate language provides comprehensive encoding of visual scenes including: geometry, shaders and effects, physics, animation, kinematics, and even multiple version representations of the same asset.COLLADA FX enables leading 3D authoring tools to work effectively together to create shader and effects applications and assets to be authored and packaged using OpenGL® Shading Language, Cg, CgFX, and DirectX® FX.”

https://www.khronos.org/collada/

KML
Originally from Keyhole/Google, but since years an OGC Standard. May embed Collada.

“Keyhole Markup Language (KML) is an XML notation for expressing geographic annotation and visualization within Internet-based, two-dimensional maps and three-dimensional Earth browsers. KML was developed for use with Google Earth, which was originally named Keyhole Earth Viewer. It was created by Keyhole, Inc, which was acquired by Google in 2004. KML became an international standard of the Open Geospatial Consortium in 2008.[1][2] Google Earth was the first program able to view and graphically edit KML files. “
Source: http://en.wikipedia.org/wiki/Keyhole_Markup_Language

OGC Standard: http://www.opengeospatial.org/standards/kml

3D in KML:
https://developers.google.com/kml/documentation/models
http://blog.thematicmapping.org/2008/04/proportional-3d-collada-objects-in-kml.html
http://blog.thematicmapping.org/2008/04/drawing-3d-bars-in-kml.html

glTF
Final stage OpenGL Transmission Format to enable rapid delivery and loading of 3D content by WebGL, OpenGL, and OpenGL ES APIs.

“The “glTF” project aims to define a final stage OpenGL Transmission Format to enable rapid delivery and loading of 3D content by WebGL, OpenGL, and OpenGL ES APIs. glTF together with COLLADA comprise a standards-based content pipeline for rich 3D web and mobile applications. glTF Specification is a work-in-progress from the COLLADA Working Group; it is not an official Khronos-ratified specification yet. It is incomplete and subject to change. The draft specification and related converters and loaders are available on github.”

https://www.khronos.org/
https://www.khronos.org/gltf/

TopoJSON

“TopoJSON is an extension of GeoJSON that encodes topology. Rather than representing geometries discretely, geometries in TopoJSON files are stitched together from shared line segments called arcs. TopoJSON eliminates redundancy, offering much more compact representations of geometry than with GeoJSON; typical TopoJSON files are 80% smaller than their GeoJSON equivalents. In addition, TopoJSON facilitates applications that use topology, such as topology-preserving shape simplification, automatic map coloring, and cartograms.” (i.e. compact TIN-representations!).
https://github.com/mbostock/topojson

Germany: SIG 3D
Germany-based 3D interest group. Started already very early (2002) with 3D geospatial and has a long history. Many useful resources for both standards and implementations can be found via their websites.

“Three-dimensional models of cities and regions play an important role in major applications of architecture, urban planning, surveying, mobile telecommunication or facility management. In the environmental sector 3D city models enable the simulation of noise and exhaust emissions as well as predictions on city climate change affecting a city. Concerning disaster situations like floods, 3D landscape models can help to analyse the affected areas and buildings.”

“Since the beginning of 2010 SIG 3D is part of the German Spatial Data Infrastructure (GDI-DE) and coordinates this context the national and international network of 3D activities.”

http://www.sig3d.org/
Several standards like OGC CityGML W3DS, later 3DPS had their origins here.

The Netherlands: Doorbraak 3D (Breakthrough 3D)
3D initiative within The Netherlands as a follow-up on earlier successful 3D projects like the 3D-Pilot:
http://www.geonovum.nl/documenten/rapport-eindrapportages-3d-pilot-nl-eerste-fase

As a follow-up (2011) of the 3D-Pilot the public standard CityGML-IMGeo was developed. Basically this standardizes detailed smallscale/detailed topography using and extending CityGML. http://www.geonovum.nl/wegwijzer/standaarden/gegevenscatalogus-imgeo-versie-211

History of 3D geo in The Netherlands: http://www.geonovum.nl/onderwerpen/3d-geo-informatie/historie-3d-geo-informatie-nl

Now (jan 2015) starting up a next phase called “3D Doorbraak”, with a recent working conference for establishing the 3D roadmap for The Netherlands: http://www.geonovum.nl/nieuws/werkconferentie-voor-opstellen-roadmap-3d-doorbraak
The choice of standards plays an important part.

See also news items via Twitter (#doorbraak3D): https://twitter.com/search?q=%23doorbraak3D&src=typd

BIM – IFC

Now that geospatial information is obtaining more detail and moving into 3D, integration with standards within the Building and infrastructure industry is one of the most obvious use-cases. Building Information Modelling or BIM is a huge standardization effort within the Building and infrastructure domain.

Geoff ,”Between The Poles”, Zeiss blogs regularly on BIM and Geospatial: http://geospatial.blogs.com/geospatial/bim/

“Building information modeling (BIM) is a process involving the generation and management of digital representations of physical and functional characteristics of places. Building information models (BIMs) are files (often but not always in proprietary formats and containing proprietary data) which can be exchanged or networked to support decision-making about a place. Current BIM software is used by individuals, businesses and government agencies who plan, design, construct, operate and maintain diverse physical infrastructures, such as water, wastewater, electricity, gas, refuse and communication utilities, roads, bridges and ports, houses, apartments, schools and shops, offices, factories, warehouses and prisons.”

Source: http://en.wikipedia.org/wiki/Building_information_modeling

For information exchange the Industry Foundation Classes are put forward.

“The Industry Foundation Classes (IFC) data model is intended to describe building and construction industry data.

It is a platform neutral, open file format specification that is not controlled by a single vendor or group of vendors. It is an object-based file format with a data model developed bybuildingSMART (formerly the International Alliance for Interoperability, IAI) to facilitate interoperability in the architecture, engineering and construction (AEC) industry, and is a commonly used collaboration format in Building information modeling (BIM) based projects. The IFC model specification is open and available.[1] It is registered by ISO and is an official International Standard ISO 16739:2013.”
Source: http://en.wikipedia.org/wiki/Industry_Foundation_Classes

More:
http://www.ifcwiki.org/index.php/Main_Page

“Territory is the socially built space”, with this sentence starts the excellent “Collective mapping tutorial. Critical mapping resources for shared mapping ” in Spanish, by Iconoclasistas (there’s another tutorial in English, with license CC BY-SA 2.0 – Creative Commons, called Collective mapping).

In this tutorial, with licence Attribution Non-commercial Share Alike 2.5, we find a symbology orientated to be used at the collective mapping workshops. Symbology which is not the usual representation of geographical elements to add an iconography for ideological representations.

And although originally the symbology was created to be used in a more crafty way in the different workshops, we think that is really interesting to have it in a opensource GIS and that gvSIG could be a tool to do this type of collective mapping jobs and the analysis of our social reality.

For all these reasons, we want to add to the comunity the new add-on for gvSIG 2.1, which is just a symbol library for collective mapping.

We hope that you like it.

Here is a video showing how to install this library (as usual, from add-ons administrator):

La Cátedra gvSIG comienza sus actividades con la intención de crear un punto de encuentro para los usuarios interesados en las tecnologías espaciales libres. Con el objetivo de crear un entorno de conocimiento compartido y de participar en la difusión de la geomática libre, la cátedra convoca este concurso internacional para animar a todos los usuarios de gvSIG y Sistemas de Información Geográfica libres a compartir y dar visibilidad a sus trabajos.

Pueden participar en este concurso estudiantes y graduados de Bachillerato y Formación Profesional, estudiantes y graduados universitarios, así como profesores universitarios e investigadores de todos los países.

Los trabajos pueden tratar sobre cualquier área de conocimiento, con el requisito de haber sido realizados con Sistemas de Información Geográfica libres. En el caso de que el trabajo se base en un nuevo desarrollo realizado a través de tecnologías geoespaciales libres y SIG libres, estos desarrollos estarán sujetos a una licencia GNU/GPL v3. Los trabajos pueden haber sido realizados en 2015 o con anterioridad, los concursantes podrán presentarse de forma colectiva e individual y su trabajo podrá enviarse en castellano, valenciano o inglés.

Entre los trabajos seleccionados se otorgará un premio de 500 euros para cada una de las siguientes categorías:

1. Trabajo elaborado por alumnos de Bachillerato o Formación Profesional
2. Proyecto Fin de Titulación Universitaria (Licenciatura, Grado, Máster)
3. Tesis doctoral o trabajo de investigación.

Los trabajos deberán enviarse antes del 1 de noviembre de 2015 a la dirección de correo electrónico gvsig@umh.es.

Los trabajos seleccionados se compartirán en el repositorio de la Universidad Miguel Hernández. El jurado evaluará la metodología, la claridad y el carácter innovador de los trabajos, valorando también la pertinencia y aplicabilidad en el caso de trabajos de investigación. Los ganadores serán anunciados en las próximas Jornadas Internacionales gvSIG [1].

Para más información consulta las bases del concurso en la página de la Cátedra gvSIG [2] o contacta a través del correo electrónico gvsig@umh.es.

[1] http://jornadas.gvsig.org
[2] http://gvsig.edu.umh.es

Dear Reader, GeoSolutions is proud to announce that Andrea Aime, our technical lead on GeoServer will attend this year FOSS4G North America in San Francisco to give a workshop and presentation on GeoServer itself. The conference will take place at the Hyatt Regency San Francisco Airport  between 9th and 12th of Marc2015. Specifically the 9th will be dedicated to workshops (here is the workshop schedule) while presentations will be given on 10th, 11th and 12th.

• GeoServer, an introdutction for beginners with Andre Aime, 9th of March 2015 from 9 to 12 - The workshop will provide the attendees with an in-depth introduction to the GeoServer Open Source server useful for those who are (still??) not familiar with it but also for those who already using it as they will have the chance to ask questions directly to one of the main developers behind the software.

• Status of GeoServer WPS  with Andrea Aime,  12th of March 2015 from 12 to 12:35 - This presentation will provide the attendee with an introduction to the GeoServer WPS functionalities, and will highlight the recent improvements in the area. The presentation will finally show some real world examples of applications using GeoServer WPS.

One of the features that can be found in gvSIG 2.1 is advanced labelling, that includes many possibilities and tools to customize label according to user need. The advanced labeling has been migrated from gvSIG 1.x to gvSIG 2.1, keeping all the existing customization options and adding some of the most required options by the user community, like the halo option.

Here are a couple of videos that show some ( of the many ) labelling options .

In this first video we focus on the possibility of labelling with halo or adding a background image for tags.

In the second video we illustrate the possibility to display labels only for selected features.

English translation of Etiquetado avanzado en gvSIG 2.1.

Otra de las funcionalidades que podemos encontrar en gvSIG 2.1 es la de etiquetado avanzado, que a su vez contiene distintas posibilidades y herramientas para confeccionar un etiquetado al gusto del usuario. El etiquetado avanzado ha sido migrado de gvSIG 1.x a gvSIG 2.1, manteniendo todas las opciones de personalización del etiquetado e incorporando al mismo tiempo alguna novedad de las más solicitadas por la comunidad de usuarios, como es la opción de halo.

A continuación un par de vídeos que muestran algunas (de las muchas) opciones de etiquetado.

En este primer vídeo nos centramos en la posibilidad de etiquetar con halo o añadiendo alguna imagen de fondo que acompañe a las etiquetas.

En el segundo vídeo vemos la posibilidad de que las etiquetas se muestren sólo cuando seleccionemos un elemento.

Hi there,

In this post, you will find the examples made in the workshop for beginners about Programming with Scripting Module in gvSIG 2.1 at the 10th International gvSIG Conference in December at Valencia.

During the workshop, we saw a few examples of geoprocessing, starting with the calculation of a buffer area and little by little, adding functionalities according to our needs.

Here the cartography to follow the scripts.We only need a polygone layer and a point layer. You can use your own layers if you want.S

If you don´t know the Scripting Module, we explain how to load the scripts, step by step, at this video. In the code, you only should change the part as ‘initial data’, writing the path where the new lawyer will be recorded. These scripts will not modify the layers already loaded. For the correct running, we should have the View on and one layer selected.

In the first two examples, we can see first, the creation of a buffer area and secondly, adding a new field showing the distance between those points to a reference point.

Script 1: Buffer

Script 2: Buffer and new field with spatial information

Script 2

Also, in the third example, we add a spatial condition. This condition is just that it creates the buffer in those points intersecting with some polygon from the selected layer. In the example, referred to ‘manzanas’, but it can be replaced for any polygon layer. We can see in the symbology how this variable evolves, thinking that the reference point from the example it would be at the left bottom side. We also see that there are points where the buffer has not been generated.

Script 3: Buffer, distance new field and complying the intersection.

Script 3

Another function is, from a point layer, to create a new line layer containing (in this case, a single entity to help us) a geometry with the union of all the points with all the vertices of the line.

In the first example, passing the vertices using the order of an ID field which would be random, and in the second one, using the buffer layer created in the 3rd script and taking as an order, the distance field to create the vertices of the line geometry.

Script 4: Convert points to line

Script 4

Script 5: Convert buffer layer line

Script 5

Finally, an example not explained during the workshop is the generation of lines projecting to that reference point, taking into account the type of layer: points, lines or polygons.

Script 6: Projected lines

Script 6: Initial line layer

Script 6:Initial polygon layer

You can watch the workshop videos on the following links (Spanish/English):

• Spanish: 10as Jornadas Internacionales gvSIG: Taller 5, Scripting en gvSIG 2.1:

https://www.youtube.com/watch?v=DFRUZh0CzbI

• English: 10th Int. gvSIG Conference: Workshop 5, Scripting on gvSIG 2.1:

https://www.youtube.com/watch?v=fKkclGGTHKs

Any doubt, you can ask here, at gvSIG user list or if it is a more specific one, you can contact me: omartinez@gvsig.com

If you are interested in the rest of the presentations of the Conference, you can check them out at this listing.

I hope these examples were useful.

Greetings to all and thank you,

Óscar

The first 2015 batch-mode edition of the geonews.

On the open source / open data front:

• There’s a new free course Introduction to Geospatial Technology Using QGIS (from Feb 23 – Mar 29) which also has content on GitHub
• Beautiful and simple, How to: watercolor pastel style in QGIS
• Announced is the FOSS4G-Europe 2015 conference, this time in Como, Italy, on July 14-17th
• Nice OpenLayers 3 feature: turning vectors into heatmap in Javascript
• Recent updates, GeoTools 12.2 Released, GeoServer 2.6.2 released,
• The mobile Android app Geopaparazzi 4.1.0 is out (4.1.1 actually), and there’s a new similar tool in development, QField (formerly QGIS Mobile) described as “A simplified touch optimized interface for QGIS. Perfect for field work on portable touch devices” over GitHub
• We can help map the Amazonia on OpenStreetMap, with mapazonia.org and on a similar topic, a new tool named To-fix: improving OpenStreetMap through micro tasking, see OSM’s progress in Japan, OpenStreetMap in Japan, 2007-2014
• There’s also progress in terms of open addresses, OpenAddresses Hits 100 Million

On the Esri front:

• Very nicely presented, ArcGIS Open Data – 2014 Year in Review (direct link to the review presentation)
• A useful review, Esri’s Living Atlas of the World and Community Maps 2014 Year-End Review
• A USGS-Esri partnership, The most detailed ecological map of the World “raster data of a resolution 250m and it’s fully interactive”

On the Google front:

• TechCrunch reports that Google is shutting down Maps Coordinate, its Mobile Workforce Management Service, focus is now on Google Maps for Work, and Google Maps Engine is now deprecated
• Now in Street View, the aurora borealis lights up Google Maps
• Two entries for developers, Transit Directions Improvements and easy Maps API integration from Java and Python
• A short GEB article on Google’s Processing of 3D imagery, it apparently takes them a year
• Interesting list that can be interpreted in many ways, Google Earth wish list for 2015

Discussed over Slashdot:

• Still around the corner, Google Glass Is Dead, Long Live Google Glass and What Will Google Glass 2.0 Need To Actually Succeed?
• Another player, Ford Touts Self-driving Car, Launches Global Mobility Experiments
• Acquire pictures in 3D directly, 3D Cameras Are About To Go Mainstream
• Trying to be nicer, Uber Will Provide Transit Data To Cities
• See also the related entry above, First Crowdsourced, Open Data Address List Launches In the UK
• There too, Moscow To Track Cell-phone Users In 2015 For Traffic Analysis

In the miscellaneous category:

• MapBox started integrating the new free 30m SRTM-DEM data and it’s a major improvement, see Australia terrain update and Asia terrain update and South America terrain update and Africa terrain update
• James Fee shares an entry on the importance of Python and Javascript scripting in GIS and in another entry, James reminds us that GIS’ underlying technology keeps evolving at a fast pace
• GeoAwesomeness agrees with James, Evolution of the Geospatial Industry: From GIS to Spatial Computing
• OGC has a 3-parts article on engaging the geoscience research community in standards development
• We mentioned it a year ago, and now it matured, IndoorGML standard for positioning inside buildings is finally out there, there’s also InfraGML being worked on, not a bad thing that W3C and Open Geospatial Consortium announce new collaboration
• Thanks Russia, Russia declassifies Earth-sensing data from its civilian satellites
• More free imagery, Free Data from Indian Resourcesat-2 Satellite via INPE
• It’s easier than ever to get on-site 3D data, Hand held scanners closer to revolutionizing the construction industry
• Hiding crime trends, City Catches Heat Over Crime-Map Change
• Interesting Electronic Frontier Foundation (EFF) article on Oakland’s automatic license plate readers
• That’s why we get tracked, How wireless carriers are making money on selling your location?
• On the other side of the fence, tracking employees, This app will let you track location of your Comcast technician
• Drones can fly after all, FAA issues grants of exemption for commercial UAV operations for construction monitoring, agriculture, and real estate
• Nokia’s HERE app getting attention, HERE app for Android downloaded 2.5M times
• If you’re in the mood to test your geo-geekiness, a series of quiz, #GeoawesomeQuiz 4

In the maps category:

• Nice maps and data, Our World in Data, with ‘visual history’ themes such as war and violence, world poverty and world hunger & food provision
• Looking for nice pictures? Wired published NASA’s Best Images of Earth From Space in 2014 and more nice imagery, Digital Globe’s top satellite images of 2014
• We already saw something similar, Windyty – weather forecast map reinvented
• A map of worldwide industries using forced labor and/or child labor
• That’s a lot of holes, Mapping a Fracking Boom in North Dakota
• People density in Europe, The True Heart of Europe – the Blue Banana
• Via this tweet, a map of our rich-poor walled world
• A funny map of bros, dudes, buddies, fellas and pals in the U.S., The Heart of Dudeness

The post Batch Geonews: QField, IndoorGML Standard, Focus on Google Maps for Work, 30m SRTM-DEM, and much more appeared first on Slashgeo.org.

• PHP and its MapGuide API bindings is installed regardless (it's why mapguide-rest will/should just work out of the box on any supported version of MapGuide), so we can also verify the PHP bits are working by loading a package through the Site Administrator
• This is the configuration that we always want to confirm and verify when testing support for newer versions of windows. The Apache/PHP/Java configurations are mostly self contained and can be generally trusted to work on any windows platform where there is a matching Visual C++ runtime library and a working Java SDK/RE for it.

Quite often, I’ll run across a large or complex shapefile that causes issues (crashing, very poor performance, etc) in QGIS or other desktop GIS.

However, sometimes you have to find a way to deal with these files, and not spend a lot of time worrying about them. Often, the best way is to head back to the mysterious black box that is the command line, and use the ultra-stable suite of tools available there. My favourite for spatial work is GDAL/OGR

I was recently struggling to do a simple dissolve on a large and complex shapefile. I didn’t want to bring it into a database, but QGIS would crash trying to dissolve the shapefile. Of course, OGR had no problem with the file!

Here’s how to turn this (nine features with three different attributes):

Input to dissolve – 3 attributes

Into this (three attributes, three multi-part features!):

Dissolved shapes

Simply use this command (substituting your file names and field names as appropriate) into ogr, and you’re all set!

ogr2ogr outputfile.shp inputfile.shp -dialect sqlite -sql “SELECT dissolvefield,ST_Union(geometry) as geometry FROM inputfile GROUP BY dissolvefield”

• From Debian-GIS to OSGeo live and back (yep shameless self-promotion)

• A GPS watch made of free software and hardware

• From Open Street Map to your preferred graph database...

• FreeCAD
  a hackable design platform 

• Web mapping with MySQL
   An introduction to MySQL GIS

The GeoServer team is excited to announce the release of GeoServer 2.7-beta with some great new features. The download page for 2.7-beta provides links for zip, war, dmg and exe bundles. As a development release, 2.7-beta is considered experimental and is provided for testing purposes. This release is not recommended for production (even if you are enthusiastic by the new features).

This release is made in conjunction with GeoTools 13-beta.  Thanks Jody (and Boundless Victoria) for making this release, Kevin for GeoWebCache 1.7-beta, and a big thanks to Andrea for gathering up the contents (and pictures) for this blog post.

A complete change log is available from the issue tracker.

Please Download and Test

The committers have a great release for you to look forward to, we would like to ask you to download and test. By trying GeoServer out on a wide range of platforms and datasets we can all help the next release be great.

Testing is a key part of the open source social contract. This is your best chance to identify issues early while we still have time to do something about it. If you make use commercial support ask your vendor about their plans for 2.7-beta testing.

When testing Geoserver 2.7-beta please let us know on the user list how it works for you. We will be sure to thank you in the final release announcement and product presentations.

New Features

Color composition and blending

Color composition and blending are two new extensions to SLD allowing the web map styler to control how overlapping layers in a map are merged together. Beyond the simple stacking and translucency control a wide range of effects are now possible by allowing masking and specific color operations for blending layers together in new ways.

A common well known example is a polygon thematic map on top of a DEM, which tends to provide under-par results using only transparency control, but generates very appealing ones when using the “multiply” blending mode:

Alpha masking also allows for neat cartographic tricks, like the one below, where the polygon fill has been cut at the border of the states generating a “inner line” effect:

Check out the documentation for a list of supported operations and some examples. We would like to thank Cleveland Metroparks for sponsoring this improvement.

WPS Clustering

First of, GSIP 119 added support for asynchronous requests over a cluster of GeoServer instances. In WPS an asynchronous request starts by returning the client a URL that can be polled in order to know about the execution progress, and eventually to retrieve the final results.  Previous to 2.7-beta the status information was kept in memory, thus only the GeoServer instance running the process could meaningfully respond to a poll from the client. With GeoServer 2.7-beta a new extension point allows the programmer to create a process status repository that can be shared among the GeoServer instances.

The first default implementation of the shared repository is a Hazelcast based one, leveraging in-memory, replicated and distributed maps to share the state information, while the results (which can be pretty large) are stored in a shared file system. The community is welcomed to develop other variants that could store the information in other places, for example, a relational database, a nosql one, or in the clould (e.g., S3 storage).

WPS Security

GSIP 121 added the ability to provide fine grained access control to processes based on our usual role based authentication system: each process or group of processes can be associated to a list of roles that can access them, while other users will be disallowed seeing or accessing the same processes.

WPS Limits

Integrating with the security, GSIP 123 added support for process execution limits, bringing WPS up to par with the other OGC services in terms of limiting the resources used by a single request. In the main WPS panel one can now configure how much processing time to give synchronous and asynchronous requests:

Also, in the new process security page one can configure a global limit for the size of complex inputs (see above), it is also possible to configure limits on a process by process basis, in order to restrict the size of inputs, the range of numerical values, and the multiplicity of repeatable inputs, to constrain the effort of a WPS process call. All these limits will be dutifully reflected in the DescribeProcess output.

If you’re not satisfied with the above limits and would like to develop new ones, no worries, the current code is setup on a pluggable WPSInputValidator extesion point that will allow you to create new types of input validators.

WPS Dismiss

The final Finally, GSIP 122 added the ability to dismiss an ongoing process from the client that requested the execution, or as an administrator. The new Dismiss operation comes from the WPS 2.0 specification, which GeoServer does not support yet, so it has to be seen as a vendor extension to WPS 1.0, which leverages the executionId parameter returned in the asynch status links to allow execution cancellation, you can read more about it in the user documentation. The administrator instead gets a new user interface panel showing the currently running operations, allowing selection and forceful dismissal of processes that are running:

The user guide contains more details about its usage. We would like to thank NATO STO CMRE for sponsoring all the above WPS improvements.

Refresh of the CSS module

The initial CSS extension (responsible for using CSS to generate SLD styles) was written in Scala. Although wildly popular, and featured up until GeoServer 2.6, the module has not been maintained to the level expected of a GeoServer extension.

Andrea has taken it unto himself to address this gap, rewriting the functionality in Java and making the result available to the GeoTools library.

The new CSS engine performs the same function as the Scala original and has managed to make a few key improvements. In particular the Java implementation can efficiently handle large CSS files without bogging down with minutes of translation time.

The user interface for the CSS editor has also been revamped a bit, making better usage of available screen space, and sporting syntax highlighting and formatting thanks to CodeMirror. This change addresses a common gripes correctly supporting relative images (the generated SLD preserves the relative path) and polygon with strokes are now translated to a single polygon symbolizer (to the benefit of GetLegendGraphic calls). Finally, you’ll notice that the download size have been significantly trimmed, as we don’t need anymore the Scala runtime.

The new translator has been tested against a few hundreds CSS styles already, but of course it’s new, so it’s of paramount importance that you test your own styles, and let us know if you notice any regression.

We take the occasion to thank David Window for creating the initial CSS module, and Andrea Aime for porting it to java and acting as the new maintainer.

Relative time support in WMS/WCS

As you probably knows GeoServer supports time based filtering in both WMS (aka WMS-T) and WCS (as part of WCS-EO). Up until now you had to specify the desired time either as an absolute value, e.g. &time=2011-05-02, or as an absolute range of values, e.g. &time=2011-05-02/2011-05-05.

The work done in GSIP 124 adds support for a vendor specific extension to the time syntax which allows the specification of relative times, e.g., the last 36 hours, “PT36H/PRESENT”, or the day after Decembre 25 2012, “2010-12-25T00:00:00.0Z/P1D”.

This allows for more compact requests, but more importantly, it allows to generate stable, publishable links to instants or intervals relative to the present server time, e.g., the wheather forecast for tomorrow, two days and three days in the future, or the temperature maps for the last three days, maybe in a KML document generated with animations over time.

Miscellaneous

In addition a wide range of improvements have been made:

• For those into printed-maps, we added a new vendor parameter forcing GeoServer to ignore the WMS simple scale computation algorithm, and run a local and accurate one instead, resulting in better integration between printing requirements and maps with scale dependencies.
• The flow-control module now also supports rate based rules, with the ability to slow down, or simply reject, requests that are incoming from a specific client at an excessive rate.
• For those working at the dateline, you’ll be pleased to know that the WCS 2.0 GetCoverage requests can now handle bounding boxes crossing the dateline, and they will take the two halves of your coverage from the antipodes, merge them together in a single output file that will be returned to you (much like the same support for WMS, introduced in 2.6.0).
• For people playing with configuration in the database, the JDBCConfig module and core modules have seen a number of changes to increase scalability and push down into the database as much filtering as possible in a larger number of commonly used code paths.
• The DDS module, allowing extraction of DEM portions using the WMS protocol in order to feed Nasa Worldwind, has seen a number of fixes and now allows the specification of a texture compression format.
• Finally, the map preview has been switched to OpenLayers 3, although the nostalgic can get back the OL2 based one by adding the “-DENABLE_OL3=false” parameter to the JVM startup options. Thanks to Bart for helping add this to GeoServer.

This concludes the most visible changes, if you are missing some please check the full changelog for details, there is quite a bit more stuff in there.

Community modules

In addition to the core GeoServer and extensions we have an active community area for experiments and new volunteers. This release comes with a number of new community modules that you might find useful.

Clustering modules

The community section now holds two clustering modules allowing a cluster of GeoServer instances to work against a shared vision of the data directory.

The first one, contributed by GeoSolutions, works using J2EE JMS messages to share the state against the various nodes, and allows the usage of the normal file based configuration, either in a shared data dir mode, or data dir per node mode. This is know as the “JMS clustering”, see the documentation for more details. The module is ready for testing as it’s part of the nightly builds.

The second one, contributed by Boundless, works by using Hazelcast distributed messages, and it’s designed to work best against the JDBConfig module. At this time there are no released artifacts or documentation, but the adventurous user will find it pretty easy to figure out.

GeoFence

The GeoFence advanced security subsystem has been donated to the GeoServer project by GeoSolutions earlier this year, this module is the plugin connecting a GeoServer instance to the GeoFence rule engine.

GeoFence allows to setup complex security rules and leverage the full power of the underlying GeoServer security subsystem, for example, it’s possible to establish security rules mixing in the same condition data and service being used, limit attributes available to certain users/operations, filter data so that certain records are not visible to the public, force certain default style to given user roles, and so on. The GeoFence wiki contains documentation on how to use and configure the system.

SOLR data store

The SOLR data store makes GeoServer connect to a SOLR server and publish its spatial document via the OGC protocols, efficiently making maps, serving them via the WFS service, and allowing spatial analysis via WPS. The user interface allows to classify sets of documents as layers, and map the document variable structure into the fixed structure of simple feature types served by GeoServer.

You can read an introduction in this blog post, and delve into details in the user documentation.

New WPS output formats

The gs-gpx and gs-kml modules offer two new PPIO to translate feature collection resulting off WPS processes in the respective formats. The KML one, in particular, also supports limited input parsing, allowing to send KML documents as inputs to the WPS services.

The WPS download process

The wps-download community module forms the basis of an “advanced clip and ship” tool that allows a client to ask for data in a specific area, eventually reprojecting it, estimate the download size, and allow the preparazion of a zip package with the desired data, all via asynchronous calls, providing a good replacement for WFS/WCS when the amount of data to be extracted is too large to be delivered via synchronous HTTP calls.

Hace unas semanas se celebraron las 10as Jornadas Internacionales gvSIG en Valencia (España), en las que se presentaron una gran cantidad de ponencias de temáticas distintas. En ellas hubo una sesión dedicada especialmente a arquitectura, en la que se presentaron varias ponencias con temas distintos como Sistemas de Información Geográfica en un despacho de arquitectura, licencias urbanísticas, o certificados de eficiencia energética, todos ellos proyectos muy interesantes.

Están disponibles tanto las presentaciones como la grabación de las mismas. Las ponencias que se presentaron relativas a arquitectura fueron concretamente:

- Los SIG aplicados a la gestión de proyectos en un despacho de arquitectura (PDF: 8.0 MB); VICENTE J. VALERO (Grado en Arquitectura Técnica)

- Sistemas de Información Geográfica para el Control de Licencias Urbanísticas (PDF: 4.7 MB); PABLO PERUCHO (Grado en Arquitectura Técnica)

- Aplicación de los SIG a los certificados de eficiencia energética en la localidad de Llíria (PDF: 5.4 MB); MIGUEL ÁNGEL SIMEÓ (Grado en Arquitectura Técnica)

- Metodología Multicriterio Para La Búsqueda De La Ubicación Óptima De Un Emplazamiento Público (ODP: 10.7 MB; PDF: 4.1 MB); RUBÉN HERNÁNDEZ (Grado en Arquitectura Técnica)

- Ruegos y preguntas de dicha sesión:

¡Esperamos que os sea útil esta información!

• Gathering user credentials from a request, for example from Basic and Digest Authentication headers
• Handling events such as ending the session (logging out), or setting the “Remember Me” browser cookie
• Performing session integration, detecting existing sessions and creating new sessions if necessary
• Invoking the authentication provider chain to perform actual authentication

1. run complex geoprocessing algorithms on demand
2. store the results on a cluster of GeoServer instance with a complete lifecycle management
3. manage the outcomes with the ability to visualize them on a map.

Stace and I would like to welcome Matilda Anne Woodrow, born 5/1/15 at 10:36am.

She is a nice way to start 2015.

After the pretty crappy year that was 2014 it was finally nice to see Matilda in the flesh. The relief of seeing her alive and well is hard to put in words after losing Ellie in 2013.

People always ask about the lack of sleep, but it feels like we have more energy now then we did before. The emotional and physical toll that the pregancy took on our family had pretty much run us into the ground and it felt like it was never ending.

The toll of the pregancy had lead me to massive lack of motivation towards QGIS and pretty much everything else in life, which isn't healthy when you have a family to look after. Pro Tip: Get help if you find yourself in this spot, it be hard to recover if you go over the edge.

Anyway. Here is to a new year. A better year.

A partir del 16 de febrero comienzan unos cursos online gratuitos de gvSIG Desktop, ofrecidos por la Fundación Fessia en colaboración con la Asociación gvSIG.

Con dichos cursos se obtiene la certificación de usuario y la certificación usuario experto en gvSIG Desktop de manera gratuita. El colectivo al que va dirigido es únicamente a trabajadores en activo del sector agrario, forestal y pecuario.

Para este curso hay disponibles 175 plazas para la certificación de usuario y 50 plazas para la certificación de usuario experto. ¡No dejéis pasar la oportunidad!

Para más información se puede consultar la web www.gvsig-fessia.com o remitid las dudas vía email a informacion@gvsig-fessia.com o a través del teléfono 644979959 (en horario de 09.00 h. a 14.00 h.).

Más información sobre fechas, en http://www.gvsig-fessia.com/wordpress/wp-content/uploads/2015/01/NOTA-DE-PRENSA.pdf

The GeoServer team is happy to announce the release of GeoServer 2.6.2. Download bundles are provided (zip, war, dmg and exe)  along with documentation and extensions.

GeoServer 2.6.2 is the next the stable release of GeoServer and is recommended for production deployment. Thanks to everyone taking part, submitting fixes and new functionality:

• The issue with GZIP encoding breaking CSS download in some browsers has been fixed
• Have the pre-generalized store use again the simplified geometries against the PostGIS store (regressed in 2.6.0)
• Relative paths in SLD using a “file://image.png” syntax are supported again (regressed in 2.6.0)
• Removing also layer groups and styles contained in the workspace when the workspace is deleted
• Make WCS 2.0 / WCS EO more lenient when the workspace is not specified in requests, or when a single mosaic granule is requested in EO requests
• Allow disabling “advanced projection handling” for raster data via a system variable (for the few cases in which it misbehaves, fixes are underway, please do report if you see issues)
• A number of minor fixes to WCS capabilities and GetCoverage handling
• Added icelandic language support in the INSPIRE plugin
• Check the release notes for more details
• This release is made in conjunction with GeoTools 12.2

Thanks to Andrea (GeoSolutions), Jody and Kevin (Boundless) for this release

About GeoServer 2.6

Articles and resources for GeoServer 2.6 series:

• GeoServer at FOSS4G
  • State of GeoServer and GeoTools 2014 (slides)
• Raster Views in GeoServer via the CoverageView concept (GeoSolutions)
• Advanced Raster Projection in GeoServer (GeoSolutions)
• Supporting Wind Barbs In GeoServer and GeoTools (GeoSolutions)
• GeoServer now supports Vector Footprints for ImageMosaic (GeoSolutions)
• 2.6.0 announcement and change log
• 2.6-RC1 announcement and change log
• 2.6-beta announcement and change log

English translation of the article by Joaquin del Cerro.

Hi everyone,

I´m back to explain to you, how download the sources of one of the gvSIG project´s example and how compile it and debug it.

In this article, I will use as IDE Netbeans 8, which is the IDE that normally I use for developing with gvSIG long time ago. In the future, I will install an Eclipse and in another post I will tell you how to work with it. Anyway, if you are a developer used to Eclipse, it would not be difficult to take the explained ideas.

Keep in mind that this post doesn´t want to be a NetBeans tutorial, just to explain the steps to follow for being able to download and compile gvSIG plugin with it.

Once you have already followed the steps described in the post  “Como descargar y compilar gvSIG 2.1.0 en Linux y Windows“ and we have all the basic tools installed and set up, we can carry on.

To follow this post, we need internet access. In general, for compiling gvSIG we need internet access. And also:

• An Installable of gvSIG, in my case “gvSIG-desktop-2.1.0-2262-testing-win-x86-standard-withjre.exe”
• An Installable of NetBeans

First of all, we install IDE, NetBeans.

I´ve downloaded it from the NetBeans official website, in downloads:

https://netbeans.org/downloads/

We will find a few distributions availables for downloading:

• Java SE
• Java EE
• C/C++
• HTML5 & PHP
• All

With the distribution “Java SE” will be enough for compiling the majority of gvSIG projects (excluding the ones requiring natives, because they are out of this post´s scope)

Simply we will download it and proceed to install it.

Through the initial set up, it will ask us for two things, where are we going to install it and where is the JDK to use. In this case, we will choose the JDK which we have already installed like it was explained in “Como descargar y compilar gvSIG 2.1.0 en Linux y Windows“.

Once we have installed NetBeans, we will install gvSIG. It will be a standard setup but we will not install it in “Program Files”;, I advise you to install it inside c:/devel, folder, where we have already downloaded the gvSIG sources. I have installed in :

c:/devel/gvsig/2.1.0-2262

The reason of installing it out of “Program Files” is because in my Windows installation, the user doesn´t have administrator privileges and if I do it in there, I will have problems later when I try to deploy the plugin binaries over that installation. Writing on c:/devel folder (created by me), I will not have any privilege problems at all.

Once we have these two things installed, we change the pathfile on “.gvsig-devel.properties” for pointing to the installation of gvSIG which we have just done in “c:/devel”.

Well, one more thing to do. The actual distribution for Windows of gvSIG-desktop doesn´t include a launcher in gvSIG.sh of gvSIG. The launcher is only included in Linux distribution( in future distributions we will include it as well for Windows). Well, for the moment is not present, so we have two options, if we have alredy compiled “org.gvsig.desktop”, we can take it from “org.gvsig.desktop/target/product” folder or if we don´t have it on hand, we can download it from:

http://devel.gvsig.org/svn/gvsig-desktop/trunk/org.gvsig.desktop/org.gvsig.desktop.framework/org.gvsig.andami/src/main/resources-application/gvSIG.sh

We will leave it in the folder where we have installed gvSIG, along with the “gvsig-desktop.exe”.

Once we have these three things, we will boot NetBeans, then, downwnload the project “org.gvsig.landregistryviewer” and we will compile it. We will download it from the url:

http://devel.gvsig.org/svn/gvsig-plugintemplates/org.gvsig.landregistryviewer/trunk/org.gvsig.landregistryviewer/

To do it, we will go to menu:

Team->Subversion->Checkout…

It will show us the following screen:

Then, we will write in the field “Repository url” the value of the url (previously indicated) in where is the example project “org.gvsig.landregistryviewer”. We click on “Next”. It will show us the next page of the assistant, in which we should introduce the folder where we want to download the project. In our case, we will introduce “c:/devel”, and click on “Finish”.

When the project´s download finish, it will tell us about the maven projects presents in the donloaded project and it will ask us if we want to open any of them. The screen dialogue will be something like:

We click on “Open project…” to indicate which of the projects we want to open and it will show us:

We will select the project “org.gvsig.landregistryviewer” and click on “Open”.

When we try to load the project for the first time, probably some error will appear due to the fact that some dependencies are not downloaded, showing us a message like:

We only clik on “Close”.

Now, we will compile the downloaded project. To do that, we select it in the “proyectos” view and click on “Build project” of the toolbar.

The bottom console will be showing the compiling messages and once the process finishes, we will have our plugin compiled and deployed over the gvSIG installation.

So far, we have seen how to prepare our work environment, download and compile the plugin. If we want to see our plugin in action, simply we will boot Console2, go to gvSIG installation folder, c:/devel/gvsig/2.1.0-2262, and run gvSIG.sh.

$ cd c:/devel/gvsig/2.1.0-2262
$ ./gvSIG.sh

Let´s see how to debug our plugin.

We will open the subproject “org.gvsig.landregistryviewer.app.mainplugin”.

It could happen that the plugin doesn´t realise that there are all the dependencies needed, already downloades when the project has been compiled.If this happens, iw will show us:

In this case, we click on “Resolve Problems…” for updating the dependencies. It will show us:

We click on “Resolve…” and wait until the project update. When the update is finished, the atención signal should dissapear and we will close the dialog clicking on “Close”.

Now, we will load the class LandRegistryViewerExtension and put a breaking point at method´s start CreateViewWindow. To do this, we click twice in the line´s number.

Once done the breaking point, we will go to Console2 and we will go to boot gvSIG, but passing before the parameters “–debug –pause”.

This boots the JVM activating the debug for being able to connect with it.

It is possible that depending of the firewall setting, it will show us a message or even that doesn´t work. We need to make sure that we allow the app java.exe to access to 8765 port.

Then, we will back to NetBeans, and connect to gvSIG in debug mode.

It will ask us for connection data…..

When click on “OK”, it will carry on with the running of gvSIG in debug. As we have put a breaking point, it will stop on it and we will be able to debug our plugin.

If we need to see the code of gvSIG, we click on Ctrl-O and type the class name which we want to locate.For instance, if wew want to put a breaking point in the proect creation, we will type Ctrl-O y “DefaultProject” …

And click on “OK”.

If it doesn´t show us the source code (automatically downloaded, well, depending of our NetBeans setting), we can click on “Attach Sources…” and then “Download”.

Once all the sources needed have been downloaded, we close the window clicking on “OK”. It will show us the code for the class “DefaultProject” and we can put a breaking point in its builder.

Well, that´s it for today…..

All I have talked about is related to Windows 7. For Linux developers, it´s quite easy to follow and you just need to change the path c:/devel for the one that you use to leave the sources.

For Eclipse developers, the steps to follow are similars, the most complicated issue could be the support setting of maven which has already NetBeans.

It´s a post quite long (a lot of screenshots), but I think that they could be helpful to follow up the article.

I hope it was useful,
Greetings to all and thank you!

English translation of the article by Joaquin del Cerro.

Hello again,
In the previous article, “Como descargar y compilar gvSIG 2.1.0 en Linux y Windows“ “How to download and compile gvSIG 2.1.0 on Linux and Windows” I left some stuff unclear. Among them, I didn´t comment at all on how to download and compile a gvSIG plugin.

Assuming that we have already been able to install and set up the development tools mentioned in the article, from that point, compile a plugin is pretty simple, the most complicated issue it could be to get the plugin sources to compile.

In the gvSIG project, as a platform for managing development projects tool, we use “redmine”, which can be found at:

• https://devel.gvsig.org/redmine

In the “redmine”, we already have registered several projects, including the one for the gvSIG kernel, “Application: gvSIG desktop”. We can get a projects list at:

• https://devel.gvsig.org/redmine/projects

In almost all of them, we will find the url from which we can download the sources.
We have to consider that a “redmine” project can store more than one development project and this one, in turn, can contain several gvSIG plugins.

Let’s see now, how we would do to download and compile the gvSIG data provider for PostgreSQL.

Looking at the projects list, we will find one named “gvSIG data provider for PostgreSQL”.
We click on the link and it will show us the project page in the redmine. Right there, we will have a link that says something like:

SVN: http://devel.gvsig.org/svn/gvsig-postgresql

We surf to it, and we will find an url like:

http://devel.gvsig.org/svn/gvsig-postgresql/trunk/org.gvsig.postgresql/

We will have a “pom.xml” file, which would be the root of our plugin project. We have to get used that gvSIG projects are multimodule maven projects.

To compile it and run it is pretty simple.
First, we will need to have a previously installed gvSIG 2.1.0. We can use a normal installation of gvSIG or the gvSIG binaries that they were generated as described in the previous article.

If we already have them, we should go to our user HOME and check if there exists a file “.gvsig-devel.properties”. This file contains the path where to find our gvSIG installation to deploy in it the gvSIG binaries plugins that we will compile. If we have compiled the gvSIG kernel in that process, it will be have been created with the appropriate values. We will have in it, something like:

~ $ cd
~ $ cat .gvsig-devel.properties
#Fri Dec 12 00:13:47 CET 2014
gvsig.product.folder.path=C\:/devel/org.gvsig.desktop/target/product
~ $

If we do not have the file already created, simply we will just create it, allowing the entry “gvsig.product.folder.path” point to the gvSIG installation on which we want to deploy the plugin.

Once all of this has been set, simply we will open our Console2 with Busybox (already set up) and run:

~ $ cd c:/devel
~ $ svn checkout http://devel.gvsig.org/svn/gvsig-postgresql/trunk/org.gvsig.postgresql/
... exit svn command...
~ $ cd org.gvsig.postgresql
~ $ mvn install
... exit install command...

If we are in Linux, we only change the command “cd” to adapt to the folder where we want to leave the sources.

Well, this process downloads the sources, compiles them and deploys the binaries of our plugin on the folder which we will indicate in the file “.gvsig-devel.properties”.

On the one hand it will leave us:

• In gvSIG/add-ons the plugin already installed and ready to be loaded at the next start of gvSIG.
• In install the package with our plugin “.gvspkg” if we want to hand it to another user to install it with the Plugin Manager.

Now, we just have to start the gvSIG and it will boot with our plugin.

Keep in mind that if deployed on a gvSIG binaries generated from the source, to boot gvSIG we should boot it running the gvSIG.sh file (even in a Windows system), as it was remarked in the previous article, while if we want to deploy it in a standard installation, we will boot it as normally boots that distribution.

Well, that´s all for now.

As always, I hope that it would be useful for you.

Shortly, I will try to talk about “How to work with an IDE and debug gvSIG”/como trabajar con un IDE y depurar gvSIG.

Greetings to all and thank you

Buenas, teníamos pendiente de publicar los ejemplos realizados durante el Taller de Scripting en las 10as Jornadas Internacionales gvSIG el pasado Diciembre en Valencia.

Durante el taller vimos varios ejemplos sobre geoprocesos, empezando con el cálculo de un área de influencia e ir poco a poco añadiendo funcionalidades según nuestras necesidades.

Adjunto aquí la cartografía necesaria para seguir los siguientes scripts. Solo es necesario una capa de polígonos y una capa de puntos, podéis probarlos con vuestras capas propias.

Si no conoces el Módulo de Scripting, te explicamos paso a paso como cargar los scripts en este vídeo. En el código solamente deberéis de modificar la parte que aparece como ‘datos iniciales’, indicando la ruta donde se grabará la nueva capa. Estos scripts no modificarán las capas que tengáis cargadas. Para su correcto funcionamiento debéis tener la Vista activa y una capa seleccionada.

En los dos primeros ejemplos, podemos ver primero la creación de un área de influencia, y segundo, añadiendo un campo nuevo indicando la distancia de esos puntos a un punto de referencia.

Script 1: Buffer

Script 2: Buffer y nuevo campo con información espacial

Script 2

Además, en el tercer ejemplo, añadimos una condición espacial. Esta condición es que solamente cree el área de influencia en aquellos puntos que intersectan con algún polígono de la capa seleccionada. En el ejemplo hace referencia a la capa ‘manzanas’, pero esta puede ser sustituida por cualquier capa de polígonos. Podemos ver en la simbología como evoluciona esta variable, pensando que el punto de referencia del ejemplo se encontraría en la parte inferior izquierda. También vemos que hay puntos donde no ha generado los buffers.

Script 3: Buffer, nuevo campo distancia y que cumplan la intersección.

Script 3

Otra de las funciones que vimos fue, partiendo de una capa de puntos, crear una capa nueva de tipo línea que contuviera (en este caso una sola entidad para facilitar las cosas) una geometría con la unión de todos los puntos como vértices de la línea.

En el primer ejemplo pasando los vértices utilizando el orden de un campo ID que sería aleatorio, y en el segundo ejemplo, utilizando la capa de buffer creada en el script 3 y tomando como orden el campo de distancia para crear los vértices en la geometría línea.

Script 4: Convertir puntos a línea

Script 4

Script 5: Convertir capa buffer a línea

Script 5

Por último, un ejemplo que no dio tiempo de explicar durante el taller, la generación de líneas que proyectan a ese punto de referencia, haciendo distinción según la capa inicial sea de tipo puntos, líneas o polígonos.

Script 6: Líneas proyectadas

Script 6: Capa inicial de líneas

Script 6: Capa inicial de polígonos

Podéis ver los vídeos del taller, en español e inglés, en los siguientes enlaces:

• Español: 10as Jornadas Internacionales gvSIG: Taller 5, Scripting en gvSIG 2.1:

• Inglés: 10th Int. gvSIG Conference: Workshop 5, Scripting on gvSIG 2.1:

Cualquier otra duda podéis preguntar por aquí, por las Listas de usuarios gvSIG o si es alguna duda concreta podéis contactar conmigo directamente en: omartinez@gvsig.com

Si estáis interesados en ver el resto de ponencias realizadas durante las Jornadas podéis consultarlas en el siguiente listado.

Espero que os sean de utilidad estos ejemplos.

Un saludo,

Óscar

A new feature for QGIS 2.8 is a function editor for expressions. Being able to define your own custom functions has be possible for a while now, over a year, I even have a plugin (Expressions+) that adds some extra ones, however it wasn't easy for new users and required you to create files that lived on python path while also editing the startup.py file for QGIS so that functions got registed at start up. Way too much effort for my liking.

This feature is now exposed via the expression builder on the Function Editor tab. The function editor will create new Python files in qgis2\python\expressions and will auto load all functions defined when starting QGIS. I remember Sean Gillies saying that Python support in a field calculator should be a gateway to full Python programming, can't get any more Python then full Python modules.

The best way to show this feature is a quick video so here it is

The play button in the editor will run the current editor file in the QGIS session and register any functions it finds, it will also save the file in the expressions folder.

You can make a new file by pressing the new file button which will add the basic function template, changing the name in the combobox and hitting save will save the file.

The function editor allows you have to define reuseable functions for your QGIS. If you want to share a function you simply share the .py file from the expressions folder and give it to another user. In future versions of QGIS we might have a way to download other users functions.

Auto expanding values

You can also use the args="auto" keyword in place of the number of args which will let QGIS work it out and expand the arguments for you.

Here is an example

@qgsfunction(args="auto", group='Custom')
def myfunc(value1, value2 feature, parent):
    pass

and can be used like this:

myfunc('test1', 'test2')

QGIS will workout how many arguments your function takes based on what you have defined. Note: The last arguments should always be feature, parent, these are not included in the count.

Raising errors

If you need to report a error from a function simply use the raise method like normal in QGIS and raise an exception.

@qgsfunction(args="auto", group='Custom')
def myfunc(value1, value2 feature, parent):
    raise Expection("Hahah Nope!")

The function wrapper will catch the exception and raise it though the expression engine.

A couple of things to note

• New functions are only saved in the expressions folder and not in the project file. If you have a project that uses one of your custom functions you will need to also share the .py file in the expressions folder.
• The editor doesn't unregister any functions. If you define a function called test, hit play, change the name to test_2, hit play, both functions will exist until you reload QGIS.

Entre el gran número de novedades que encontraremos en gvSIG 2.1, además de todas las nuevas funcionalidades, migración de funcionalidades existentes en versiones anteriores y corrección de errores, el usuario de gvSIG encontrará un buen número de bibliotecas de símbolos que se unen a las ya existentes.

Estas bibliotecas de símbolos no vienen instaladas por defecto en gvSIG, ya que en muchos casos se trata de simbologías temáticas o específicas de determinadas áreas de aplicación; pero todas ellas van en la instalación base, con lo que no es necesaria la conexión a internet para poder instalarlas en nuestro gvSIG.

Hoy vamos a comentar una de estas librerías temáticas. Se trata de la denominada “Weather” y que permite integrar en gvSIG simbología para realizar mapas climáticos acorde al estándar definido por la Organización Meteorológica Mundial en su documento “WMO No. 485 – Manual on the Global Data Processing and Forecasting System Manual” (con versiones en inglés, español, francés y ruso).

Adicionalmente se ha tenido en cuenta el trabajo del grupo MetOceanDWG de OGC en relación a la simbología para representar la climatología.

Veamos en el siguiente vídeo como instalar la biblioteca “Weather”:

English translation of the article by Joaquin del Cerro.

Hi, I ‘m here again.
This time to speak about a very quick scripting .

A few days ago Oscar Martinez told me that he had seen a python library to access geocoding services , GeoPy ; but there was the problem that he was unable to use it in gvSIG … as it was designed for a newer python version than the one used in gvSIG.

While we were glancing , we realised that by changing few small things, it could become usable for the python version of gvSIG 2.1.0 .

To use GeoPy you have just to install the library , which can be done by unzipping the  “geopy-1.7.1-patched-for-gvSIG-2.1.0.zip” file in the folder:

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

located in user home. If you have already executed gvSIG, it should be closed and restart .

In Linux you can find this folder in $ HOME , and for Windows in :

C: \ Document and Settings \ my_user
or
C: \ Users \ my_user

Once installed the library GeoPy it can be used quite simply. If you execute the gvSIG scripts “Composer” , and create a new one with the following code , then you can start testing without any problems.

from gvsig import *
from commonsdialog import *

from geopy.geocoders import get_geocoder_for_service

def main(*args):

  street = inputbox("Insert street","street")
  if street == None:
    return
    
  geolocator = get_geocoder_for_service("googlev3")

  location = geolocator().geocode(street)

  print(location.address)
  print((location.latitude, location.longitude))
 
  msgbox("Found:\n"+location.address+"\n"+str((location.latitude, location.longitude)))

You can perform more complex actions such as open a table containing street names and civic addressing, read them and go creating a shapefile with points provided by geolocalisation service, but for the moment you can go on playing with this.

Greetings to all