Welcome to Planet OSGeo

May 03, 2016

GeoServer Team

GeoServer 2.9-RC1 Released!

The GeoServer team is pleased to announce GeoServer 2.9-RC1. Downloads are available (zipwardmg and exe) along with docs and extensions.

This release is made by Torben Barsballe (Boundless) in conjunction with GeoWebCache 1.9-RC1 and GeoTools 15-RC1.

This is a release candidate for final testing before we release 2.9.0.

Highlights:

  • This release requires Java 8 and is compatible with Oracle JDK and OpenJDK
  • GeoServer now requires Servlet 3 (so Tomcat 7 or newer if you are doing a WAR install)
  • Update to Spring 4 and JAI-EXT to 1.0.9
  • For more information, check the 2.9-beta, 2.9-beta2, and 2.9-M0 release notes.

Fixes since beta:

For more information see 2.9-RC1 release notes.

About GeoServer 2.9

Articles, docs, blog posts and presentations:

GeoServer Community

GeoServer Community modules provide an area for ideas and experimentation. Community highlights for this release:

  • The YSLD Styling language provides a more concise alternative to SLD, while still sharing the same structure.

Community modules should be considered a work-in-progress and are subject to quality assurance, documentation IP checks and a maintainer before being considered ready for release.

by tbarsballe at May 03, 2016 08:48 PM

GeoTools Team

GeoTools 15-RC1 Released!

The GeoTools team is pleased to announce GeoTools 14-RC1:
This release is also available from our Maven repository.

This release is made by Torben Barsballe (Boundless) in conjunction with GeoWebCache 1.9-RC1 and GeoServer 2.9-RC1.

This is a release candidate for final testing before we release 15.0.

Fixes since beta:
  • FilteringSimpleFeatureCollection breaks visitor optimizations
  • ReprojectFeatureResults/ReprojectFeatureCollection breaks visitor delegation
  • GeometryClipper can generate polygons without any inner area, laid on the clipping area border
For more information see 15-RC1 release notes.

by Torben Barsballe (noreply@blogger.com) at May 03, 2016 08:46 PM

Fernando Quadro

Como criar sua camada a partir do OpenStreetMap

O site OpenStreetMap Data disponibiliza camadas dos continentes, oceano, entre outras. Estas informações são bastante utilizadas em qualquer mapa como base, mas dependendo do caso, ter a camada completa não é interessante.

Por isso, vamos ensinar como você pode baixar esse dado e realizar o recorte (clipe) apenas da informação que deseja. Neste exemplo vamos utilizar o arquivo de oceano para poder explicar como realizar o procedimento.

Baixe o arquivo de polígonos do oceano completo, que está disponível em http://openstreetmapdata.com/data/water-polygons

Importe o arquivo em uma base de dados PostgreSQL, com o nome ocean_all, para que possamos recortar no tamanho desejado no banco de dados:

shp2pgsql -s 4326 -I -D water_polygons.shp ocean_all | osm psql

Para realizar o recorte da tabela ocean_all você deve utilizar o SQL descrito abaixo. Para você entender melhor, ele primeiro calcula a extensão da área de trabalho (extent), em seguida, usa essa medida para o recorte da tabela completa (com dados de todo o mundo), criando uma nova tabela denominada ocean, apenas com os dados locais.

CREATE TABLE ocean AS
WITH bounds AS (
SELECT ST_SetSRID(ST_Extent(way)::geometry,4326) AS geom
FROM planet_osm_line
)
SELECT 1 AS id, ST_Intersection(b.geom, o.geom) AS geom
FROM bounds b, ocean_all o
WHERE ST_Intersects(b.geom, o.geom);

Note que utilizei informações da tabela planet_osm_line, esta tabela encontra-se no post “Publicando mapa com dados do OpenStreetMap (Parte 1)” deste blog.

Caso você não tenha esta tabela, você pode usar uma outra que tenha o extent da região selecionada ou criar o polígono em hora de execução e substitui o trecho abaixo:

ST_Extent(way)::geometry

Por:

SELECT ST_GeomFromText('POLYGON((-71.1776585052917 42.3902909739571,-71.1776820268866 42.3903701743239,
-71.1776063012595 42.3903825660754,-71.1775826583081 42.3903033653531,-71.1776585052917 42.3902909739571))');

Lembrando que as coordenadas tem que ser substituídas pelas coordenadas que representam a sua área de influência.

by Fernando Quadro at May 03, 2016 10:10 AM

May 02, 2016

Fernando Quadro

Publicando mapa com dados do OpenStreetMap (Parte 1)

OpenStreetMap (OSM) contém uma grande riqueza de dados, mantido por uma comunidade mundial de mapeadores. Para mapear os dados com fonte aberta a única forma para que seja possível construir um conhecimento compartilhado é através da colaboração.

A construção de um mapa usando dados do OSM pode ser assustador: você tem que extrair os dados a partir do servidor central, ou encontrar um pacote de download; escolher e utilizar ferramentas para convertê-lo para seu banco de dados; produzir um produto cartográfico; e, escolher e usar uma ferramenta para publicar esse produto.

map1

Este tutorial irá explorar a implantação de um produto cartográfico usando um pequeno conjunto de ferramentas fácil de instalar:

1. OpenGeo Suíte, para armazenar os dados e publicá-los para o mundo.
2. Bash scripts e cURL para automatizar a configuração do mapa.

Para este post vou considerar que você já baixou e instalou o OpenGeo Suite, conectou ao servidor de banco de dados e criou uma instância com suporte espacial.

Estaremos construindo um mapa rodoviário com informações de uma única cidade. Para manter o volume de dados pequeno, vamos trabalhar com Victoria no Canadá para este exemplo.

Os arquivos de dados do OpenStreetMap para cidades estão disponíveis individualmente no site Mapzen. Nós iremos baixar e descompactar esses arquivos.

https://s3.amazonaws.com/metro-extracts.mapzen.com/victoria.osm2pgsql-shapefiles.zip

Dentro do arquivo zip contém arquivos de ponto, linha e polígono. A fim de alinhar os nomes de tabela com o nosso processamento mais adiante neste tutorial, vamos nomeá-los para planet_osm_point , planet_osm_line e planet_osm_polygon durante a importação. Se você importar utilizando a interface gráfica do pgShapeLoader, lembre-se do seguinte:

1. Definir o SRID dos dados para 4326
2. Definir os nomes da tabela de forma adequada conforme citado acima
3. Definir o nome da coluna de geometria

Nota: Você pode usar também o shp2pgsql (linha de comando), caso seja de sua preferência.

Os arquivos que baixamos no OSM incluem as informações das estradas, mas não possui dados do oceano. A fim de obter o mapeamento do oceano pronto, é preciso baixar um arquivo diferente.

Você pode baixar o arquivo oceano inteiro em http://openstreetmapdata.com. No entanto, o arquivo é muito grande, e pode precisar de muito processamento para usar em um projeto pequeno. Você pode baixar o arquivo dos oceanos já clipado para a nossa área de teste no link abaixo:

http://files.boundlessgeo.com/workshopmaterials/osm-base-victoria-ocean.zip

Depois de ter baixado o arquivo oceano, descompacte-o, e em seguida, carregue-o para o banco de dados.

Neste momento temos apenas quatro tabelas no nosso banco de dados: pontos, linhas, polígonos e o oceano. Para construir o mapa, nós selecionamos um subconjunto de tabelas genéricas. Para inseri-las no seu banco de dados basta executar o script create_tables.sql.

Esse script criará tabelas como hidrologia, parques, estacionamento, floresta, prédios, entre outros.

No próximo post veremos como configurar nossas tabelas no GeoServer, incluir estilos e publicá-los na web.

by Fernando Quadro at May 02, 2016 03:37 PM

gvSIG Team

gvSIG Festival: First virtual gvSIG Conference is coming!

festival portada v03

From May 23rd to 27th there’s an event that you can’t miss: the first gvSIG Festival. In this case it doesn’t matter where you live or even what language you speak since you will be able to attend (virtually) more than twenty webinars in different languages

There is no doubt that gvSIG is increasingly worldwide project: if it has a strong implementation in Portuguese and Spanish speaking countries, it’s currently well-known in more an more countries, in every continent, in every language.

An idea that we were thinking about during the last months was to show varied experiences and in different languages, removing the limitations of the events in an only place. And this take us to this first gvSIG Festival.

From some weeks ago we have a webinar service at the gvSIG Association, so we have decided to organize a first virtual conference.

This time we have decided not to open call for presentations but inviting some colleagues of the gvSIG Community to tell us about some experiences related to the gvSIG technology (gvSIG Desktop, Online, Roads…). For sure at the next edition (we are sure that it will be successful!) we will open a period for sending proposals to convert it in a more global and open event.

We think that the program meets the objective to show the variety of uses and users that take part of the gvSIG Community.

There will be presentations in English, Spanish, French, Portuguese, Turkish and Russian.

We will count with speakers and works developed in Argentina, Brazil, Colombia, Costa Rica, Spain, United States of America, France, India, Italy, Kenya, Mexico, Paraguay, Peru, Russia, Somaliland, Turkey y Uruguay.

They will speak about how the gvSIG technology can be applied in different themes like mental health, civil protection, cooperation, historic studies, roads management, acoustic analysis, hydrology, tourism, urban analysis…, in conclusion about how gvSIG can help to meet the needs of the society and improve the life of the inhabitants of the Earth.

Working from a variety of countries, under the same project that is built on the collaboration, solidarity and shared knowledge bases.

You can consult the complete program in: www.gvsig.com/festival

Notes:

  • We will publish the information about how to register at the webinars soon. 
  • The webinar platform allows to connect  to the webinars from any operating system.
  • Attendees will be able to ask questions that will be answered during the webinar.

 


Filed under: community, english, events, press office, training

by Mario at May 02, 2016 01:45 PM

Gis-Lab

Релиз GDAL 2.1

Вышел релиз GDAL/OGR 2.1.0. GDAL/OGR это библиотека на C++ для доступа к пространственным
данным в растровых и векторных форматах, базам геоданных и веб сервисам. Библиотека
включает биндинги к нескольким языкам программирования и набор различных утилит
командной строки.

http://www.gdal.org/

Релиз 2.1.0 включает следующие новые возможности:

* RFC 26: Добавлено кеширование блоков для каналов очень больших растров (WMS, WMTS, …)
http://trac.osgeo.org/gdal/wiki/rfc26_blockcache
* RFC 48: Поддержка географической сетевой модели (Geographical networks, GNM)
​https://trac.osgeo.org/gdal/wiki/rfc48_geographical_networks_support
* RFC 58: Добавлена функция DeleteNoDataValue():
https://trac.osgeo.org/gdal/wiki/rfc58_removing_dataset_nodata_value
* RFC 59.1: Утилиты GDAL/OGR теперь доступны как функции библиотеки:
https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library
Реализовано для gdalinfo, gdal_translate, gdalwarp, ogr2ogr, gdaldem, nearblack,
gdalgrid, gdal_rasterize, gdalbuildvrt и доступно в биндингах C, Python, Perl и Java.
* RFC 60: Добавлена поддержка нативных данных в OGR
​https://trac.osgeo.org/gdal/wiki/rfc60_improved_roundtripping_in_ogr
Implemented in GeoJSON driver
* RFC 61: Поддержка значения М в геометриях (XYM или XYZM).
​https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries
Реализовано в Shapefile, PostgreSQL/PostGIS, PGDump, MEM, SQLite,
GeoPackage, FileGDB, OpenFileGDB, CSV, VRT

* Новые растровые драйверы:
​CALS: чтение/запись для растров CALS Type I
​DB2: чтение/запись для БД DB2 (только Windows)
​ISCE: чтение/запись (#5991)
​MRF: read/write driver for Meta Raster Format (#6342)
​SAFE: чтение продука ESA SENTINEL-1 SAR (#6054)
​SENTINEL2: чтение продукта ESA SENTINEL-2 L1B/LC1/L2A
​WMTS: чтение сервисов OGC WMTS

* Новые векторные драйверы:
​AmigoCloud: чтение/запись сервиса AmigoCloud
​DB2: чтение/запись БД DB2 (только Windows)
​MongoDB: чтение/запись
​netCDF: чтение/запись
​VDV: чтение/запись VDV-451/VDV-452, со специализацией на специальном
Австрийском официальном открытом формате дорожного графа

* Существенные улучшение в драйверах:
​CSV: новые опции, возможность редактирования
​ElasticSearch: поддержка чтения/записи любых типов геометрий
​GeoJSON: поддержка редактирования существующих файлов, поддержка “нативных
данных” (RFC 60)
​MBTiles: Добавлена возможность записи растров. Исправления
​PDF: Добавлена библиотека PDFium в качестве возможного бэкенда.
​PLScenes: Добавлена поддержка V1 API
​VRT: Повышение разрешения многоканальных растров низкого разрешения по
панхроматическому каналу высокого разрешения (пан-шарпенинг) на лету
​GTiff: многопоточное сжатие для некоторых типов

* Библиотека Port: Добавлены виртуальные ФС ​/vsis3/, ​/vsis3_streaming/, ​/vsicrypt/

* Обновления БД СК EPSG до версии v8.8
* Общие улучшения, очистка кода, исправление предупреждений компилятора, а также
ошибок от статических анализаторов.
* Исправлены некоторые форматы для корректной работы со сбойными файлами (в
основном в American Fuzzy Lop)

Более подробную информацию по возможностям и исправлениям в релизе 2.1.0 можно
почитать по ссылке:

http://trac.osgeo.org/gdal/wiki/Release/2.1.0-News

Ссылки для скачивания:
* http://download.osgeo.org/gdal/2.1.0/gdal210.zip – исходники в zip
* http://download.osgeo.org/gdal/2.1.0/gdal-2.1.0.tar.gz – исходники в .tar.gz
* http://download.osgeo.org/gdal/2.1.0/gdal-2.1.0.tar.xz – исходники в .tar.xz
* http://download.osgeo.org/gdal/2.1.0/gdalautotest-2.1.0.tar.gz – тесты
* http://download.osgeo.org/gdal/2.1.0/gdal210doc.zip – документация / сайт

Руководство по миграции:
https://svn.osgeo.org/gdal/branches/2.1/gdal/MIGRATION_GUIDE.TXT

by bishop at May 02, 2016 01:36 PM

gvSIG Team

gvSIG Festival: ¡Llegan las primeras jornadas virtuales de gvSIG!

festival portada v03

Del 23 al 27 de mayo hay una cita que no os podéis perder: el primer gvSIG Festival. En este caso no importa dónde vivas e incluso que idioma hables, pues durante una semana vas a poder asistir (virtualmente) a más de una veintena de webinars en distintos idiomas.

No cabe duda que gvSIG es cada vez un proyecto más internacional: si en su primera fase de expansión tuvo una fuerte implantación en países de habla hispana y portuguesa, actualmente se está dando a conocer con fuerza en cada vez más países, en todos los continentes, en todos los idiomas.

Una idea que llevaba tiempo rondándonos por la cabeza era poder mostrar experiencias diversas y en diversos idiomas, eliminando las limitaciones que conlleva realizar un evento en un determinado lugar. Y eso nos lleva a este primer gvSIG Festival.

Desde hace unas semanas disponemos de un servicio de webinar en la Asociación gvSIG, con lo que ya sólo nos quedaba lanzarnos a la aventura de organizar unas primeras jornadas virtuales.

Nos hemos decidido a no hacer un llamado abierto a ponencias e invitar a algunos compañeros y compañeras de la Comunidad gvSIG a contarnos algunas experiencias relacionadas con la tecnología gvSIG (ya sea gvSIG Desktop, Online, Roads…). Eso sí, en la segunda edición (¡estamos seguros de que esto será un éxito!) abriremos convocatoria para convertir esta iniciativa en un evento todavía más global y abierto.

El programa creemos que cumple perfectamente con el objetivo de mostrar la variedad de usos y usuarios que forman parte de la Comunidad gvSIG.

Tendremos ponencias en Español, Francés, Inglés, Portugués, Ruso y Turco.

Contaremos con ponentes y trabajos desarrollados en Argentina, Brasil, Colombia, Costa Rica, España, Estados Unidos, Francia, India, Italia, Kenia, México, Paraguay, Perú, Rusia, Somaliland, Turquía y Uruguay.

Nos hablarán de cómo la tecnología gvSIG se puede aplicar a temas tan variopintos como la salud mental, protección civil, cooperación, estudios históricos, gestión de carreteras, análisis acústico, hidrología, turismo, análisis urbanos,…en definitiva, de como gvSIG puede ayudar a responder a las necesidades de la sociedad y a mejorar la vida de los habitantes de este planeta.

Trabajando desde una gran variedad de países, bajo un mismo proyecto que se construye sobre las bases de la colaboración, la solidaridad y el conocimiento compartido.

Podéis consultar el programa completo en: www.gvsig.com/festival

Notas:

– En breve publicaremos la información para inscribirse a los webinars.

– La plataforma de webinar permite conectarse desde cualquier sistema operativo.

– Los asistentes podrán realizar preguntas que serán contestadas durante el webinar.

 


Filed under: community, events, press office, spanish Tagged: Festival

by Alvaro at May 02, 2016 11:41 AM

OSGeo News

GDAL/OGR 2.1.0 released

by jsanz at May 02, 2016 10:22 AM

Even Rouault

GDAL/OGR 2.1.0 released

On behalf of the GDAL/OGR development team and community, I am pleased to announce the release of GDAL/OGR 2.1.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.1.0 release is a major new feature release with the following highlights:
  • New GDAL/raster drivers:
    • CALS: read/write driver for CALS Type I rasters
    • DB2: read/write support for DB2 database (Windows only)
    • ISCE: read/write driver
    • MRF: read/write driver for Meta Raster Format
    • SAFE: read driver for ESA SENTINEL-1 SAR products
    • SENTINEL2: read driver for ESA SENTINEL-2 L1B/LC1/L2A products
    • WMTS: read driver for OGC WMTS services
  • New OGR/vector drivers:
    • AmigoCloud: read/write support for AmigoCloud mapping platform
    • DB2: read/write support for DB2 database (Windows only)
    • MongoDB: read/write driver
    • netCDF: read/write driver
    • VDV: read/write VDV-451/VDV-452 driver, with specialization for the Austrian official open government street graph format
  • Significantly improved drivers:
    • CSV: new options, editing capabilities of existing file
    • ElasticSearch: read support and support writing any geometry type
    • GeoJSON: editing capabilities of existing file, "native data" (RFC 60) support
    • MBTiles: add raster write support. fixes in open support
    • PDF: add PDFium library as a possible back-end.
    • PLScenes: add support for V1 API
    • VRT: on-the-fly pan-sharpening
    • GTiff: multi-threaded compression for some compression methods
  • Port library: add /vsis3/, /vsis3_streaming/, /vsicrypt/ virtual file systems
  • Upgrade to EPSG database v8.8 
  • General sanitization pass to clean-up code, fix a lot of compiler warnings, as well as issues pointed by static code analyzers.
  • Fixes in a number of drivers to be more robust against corrupted files . 
You can also find more complete information on the new features and fixes in the 2.1.0.

The release can be downloaded from:
  * http://download.osgeo.org/gdal/2.1.0/gdal210.zip - source as a zip
  * http://download.osgeo.org/gdal/2.1.0/gdal-2.1.0.tar.gz - source as .tar.gz
  * http://download.osgeo.org/gdal/2.1.0/gdal-2.1.0.tar.xz - source as .tar.xz
  * http://download.osgeo.org/gdal/2.1.0/gdal-grass-2.1.0.tar.gz - source of GDAL GRASS plugin
  * http://download.osgeo.org/gdal/2.1.0/gdalautotest-2.1.0.tar.gz - test suite
  * http://download.osgeo.org/gdal/2.1.0/gdal210doc.zip - documentation/website



As there have been a few changes that affect the behaviour of the library, developers are strongly advised to read the migration guide.

by Even Rouault (noreply@blogger.com) at May 02, 2016 09:48 AM

OSGeo News

GeoCat renews Gold OSGeo Sponsorship

by jive at May 02, 2016 03:55 AM

May 01, 2016

Free and Open Source GIS Ramblings

How to create round maps in Print Composer

If you follow me on Twitter, you’ve probably seen previews of my experiments with round maps. These experiments were motivated by a recent question on GIS.stackexchange whether this type of map can be created in QGIS and while it’s not very convenient right now, it is definitely possible:

http://www.quantarctica.org

All maps in this post are created using data from the Quantarctica project.

I’ve been planing to try the Quantarctica datasets for a long time and this use case is just perfect. When you download and open their project, you’ll see that they have already clipped all datasets to a circle around Antarctica:

Quantarctica project with some custom styling

Quantarctica project with some custom styling

Since the map of the full extent of the dataset is already clipped to a circle, the overview map is easy to deal with. The detail map on the other hand is rectangular by default:

circle_maps_start

Since we cannot change the shape of the map item, we have to use a mask instead. To create a circular mask, we can add an ellipse shape:

circle_maps_addellipse

The main challenge when creating the mask is that there is no inverted polygon renderer for shapes in print composer. I’ve evaluated to workarounds: First, I created a style with a wide white outline that would cover all map parts outside the circle shape. But this solution slowed the print composer down a lot. An alternative, which doesn’t suffer from this slowdown is using draw effects:

circle_maps_mask_style

In particular, I created a big outer glow effect:

circle_maps_mask_style_effect

Note that the effect only works if the symbol itself is not transparent. That’s why I set the symbol fill to black and used the Lighten blending mode:

circle_maps_mask

Voilà! Both maps appear are nicely circular.

It is worth noting though that this workaround has a downside: it is not possible to create automatic grids/graticules for these maps. The graticule in the overview map only works because it is a layer in the main project that was already clipped to the circular shape.

Finally, you can add more depth to your map by adding shadows. To create the shadow effect, I added additional ellipse items which are styled with a drop shadow draw effect. If you only enable the drop shadow effect, you will notice that the shadow is cut off at the ellipse bounding box. To avoid this undesired effect, you can add a transform effect, which reduces the size of the drawn shape and it’s shadow so that the shadow fits into the bounding box:

circle_maps_mask_shadow_effect

It requires some manual adjustments to place the shadow at the optimal location on top of the mask:

circle_maps_mask_shadow

Add another ellipse to create the shadow for the overview map.

For more cartography tips and tricks check my new book QGIS Map Design or join my QGIS training courses.


by underdark at May 01, 2016 01:53 PM

April 29, 2016

Paul Ramsey

OGR FDW Update

I’ve had a productive couple of weeks here, despite the intermittently lovely weather and the beginning of Little League baseball season (not coaching, just supporting my pitcher-in-training).

13 Days

The focus of my energies has been a long-awaited (by me) update to the OGR FDW extension for PostgreSQL. By binding the multi-format OGR library into PostgreSQL, we get access to the many formats supported by OGR, all with just one piece of extension code.

As usual, the hardest part of the coding was remembering how things worked in the first place! But after getting my head back in the game the new code flowed out and now I can reveal the new improved OGR FDW!

OGR FDW Update

The new features are:

  • Column name mapping between OGR layers and PgSQL tables is now completely configurable. The extension will attempt to guess mapping automagically, using names and type consistency, but you can over-ride mappings using the table-level column_name option.
  • Foreign tables are now updateable! That means, for OGR sources that support it, you can run INSERT, UPDATE and DELETE commands on your OGR FDW tables and the changes will be applied to the source.

    • You can control which tables and foreign servers are updateable by setting the UPDATEABLE option on the foreign server and foreign table definitions.
  • PostgreSQL 9.6 is supported. It’s not released yet, but we can now build against it.
  • Geometry type and spatial reference system are propogated from OGR. If your OGR source defines a geometry type and spatial reference identifier, the FDW tables in PostGIS will now reflect that, for easier integration with your local geometry data.
  • GDAL2 and GDAL1 are supported. Use of GDAL2 syntax has been made the default in the code-base, with mappings back to GDAL1 for compatibility, so the code is now future-ready.
  • Regression tests and continuous integration are in place, for improved code reliability. Thanks to help from Even Roualt, we are now using Travis-CI for integration testing, and I’ve enabled a growing number of integration tests.

As usual, I’m in debt to Regina Obe for her timely feedback and willingness to torture-test very fresh code.

For now, early adopters can get the code by cloning and building the project master branch, but I will be releasing a numbered version in a week or two when any obvious bugs have been shaken out.

April 29, 2016 06:00 PM

Fernando Quadro

Criando um aplicativo com OpenLayers 3 sem escrever código (Parte 2)

No último post, iniciamos a criação da nossa webapp a partir de um projeto do QGIS. Agora, precisamos decidir como serão armazenados os dados para nosso aplicativo. Escolhendo a opção “Connect to this layer using” são apresentados uma série de opções.

webapp6

Os dados que temos para o nosso visualizador de eventos de inundação é uma amostra pequena, por isso usar diretamente o arquivo neste caso é questão de bom senso. Se tivéssemos um conjunto de dados maior ou dados dinâmicos poderíamos escolher para armazená-los no GeoServer ou PostGIS. No nosso caso, a simbologia será criado no aplicativo usando simbologia do OL3 que será renderizada pela própria aplicação.

Agora que nós definimos como queremos conectar as camadas precisamos decidir se queremos popups, e qual o conteúdo que gostaríamos de ter apresentado nele. Clicando em “Edit” abre a janela do editor de pop-up. Ela está inicialmente em branco, mas clicando em “Add all atributes” irá preenchê-lo com a tag [field_name] para cada campo da camada.

webapp7

No nosso caso, vamos ter um pop-up que mostra o nome do fluxo para as áreas inundadas, sem pop-up para as parcelas, e a camada de precipitação total terá um pop-up que mostra a precipitação mínima e máxima para essa área.

O próximo passo é a aba “Widgets” onde vemos um grande número de controles, ferramentas e widgets para nossa escolha. A seleção de um widget irá adicioná-la ao aplicativo, enquanto o botão direito sobre um widget vai lhe dar as opções de configuração do mesmo.

webapp8-939x1024

Há obviamente muitas opções nesta tela. Para efeitos desta postagem vamos usar apenas os controles padrão e configurar a lista de camadas (Layer List) para permitir que o usuário mude a opacidade das mesmas.

webapp9

Vamos adicionar um “About Painel” para o aplicativo e editar o conteúdo para que os usuários saibam mais sobre o que eles estão visualizando.

webapp10-826x1024

Uma vez que tenha configurado os controles e widgets vamos para a aba “Deploy”. Esta aba é usada para configurar as conexões com PostGIS e GeoServer. No nosso caso, não estamos publicando nossos dados em qualquer PostGIS ou GeoServer, por isso podemos ignorar e ir para aba “Settings”.

webapp11-943x1024

A página de configurações (Settings) nos dá a oportunidade de definir como queremos lidar com o Extent do mapa, níveis de zoom, e estilo dos layers. Para a nossa aplicação, vamos aceitar todos os padrões.

Após terminar de configurar nossa aplicação vamos visualizar o aplicativo (Preview) e ver como ficou.

webapp13

Nossa aplicação de exemplo está pronta! Se quisermos fazer quaisquer mudanças podemos voltar e alterar qualquer uma das configurações para atender às nossas necessidades e pré-visualizar novamente. Uma vez que o aplicativo está configurado e pronto para ser publicado, clique em “Create App”. O construtor da webapp irá pedir-lhe um local para salvar os arquivos, criar seu aplicativo, e perguntará se você gostaria de vê-lo.

Nós temos uma aplicação concluída pronto para uso, executada com apenas alguns cliques do mouse e preenchimento de algumas telas. Em nenhum momento durante este processo foi necessário codificação.

O projeto “2013 Boulder County Flood Viewer” pode ser visto completo em http://wilson.boundlessps.com:8080/BoulderCountyFloods2013/

Esta publicação é uma tradução livre do post “Building an OpenLayers 3 Web App Without Writing Code” publicado pela Boundless.

Fonte: Boundless

by Fernando Quadro at April 29, 2016 10:21 AM

April 28, 2016

GeoSpatial Camptocamp

FOSSGIS 2016 & AGIT 2016

Camptocamp participera à la conférence FOSSGIS qui se tiendra cette année en association avec AGIT à Salzbourg, en Autriche!

Cet article FOSSGIS 2016 & AGIT 2016 est apparu en premier sur Camptocamp.

by Elisabeth Leu at April 28, 2016 03:33 PM

Paulo van Breugel

Use R to get gbif data into a GRASS database

Introduction GBIF The Global Biodiversity Information Facility (GBIF) is an international open data infrastructure that allows anyone, anywhere to access data about all types of life on Earth, shared across national boundaries via the Internet. GBIF provides a single point of access through http://www.gbif.org/ to species records shared freely by hundreds of institutions worldwide. The […]

by pvanb at April 28, 2016 03:06 PM

Fernando Quadro

Criando um aplicativo com OpenLayers 3 sem escrever código (Parte 1)

Construir uma aplicação web para exibir seus dados pode ser uma tarefa difícil se você não for um desenvolvedor, especialmente se você não está familiarizado com os conceitos de SIG.

A equipe do OpenGeo Suite (Boundless) tem buscado maneiras de ajudar seus clientes a construir mapas na web, aproveitando todas as funcionalidades agora disponíveis com o lançamento do OpenLayers 3 sem a necessidade de trabalhar a partir da linha de código.

Um dos mecanismos desenvolvido para isto foi um plugin para o QGIS. Este plugin permite você publicar um projeto feito no QGIS como um aplicativo web OpenLayers 3 (“OL3”), basta seguir algumas instruções e preencher alguns formulários. Isso não requer nenhuma habilidade de codificação.

O objetivo deste post é orientá-lo através dos passos necessários para transformar seu projeto do QGIS em uma aplicação web completa, tudo a partir do QGIS usando o plugin “Web App Builder”. A intenção é demonstrar a simplicidade de construção de um aplicativo sem a necessidade de recorrer ao código.

Para começar, você precisa instalar QGIS 2.8.2 (versão para o OpenGeo Suite). Esta opção está disponível (usando o Windows ou Mac OS X 10.9 e superior) em http://boundlessgeo.com/solutions/solutions-software/qgis/

Uma vez instalado o Web App Builder é acessível através dos menu de “Plugins”.

webapp1

No entanto, antes que possamos criar um aplicativo precisamos de um projeto QGIS com os dados de apoio. Neste exemplo iremos utilizar alguns dados de inundações em Boulder County, Colorado (2013) para criar um visualizador de eventos de inundação. Serão carregadas três camadas – Total de precipitação, as parcelas com inundações e as áreas inundadas.

Agora que temos o nosso projeto QGIS vamos construir um webapp!

Primeiro, escolha o menu Plugins -> Boundless -> Web App Builder. Isso fará com que abra a tela do Web App Builder para nos ajudar a definir a nossa aplicação.

Miller2_1

Esta janela vai nos ajudar no processo de criação do nosso aplicativo. Vamos começar pelo título do nosso aplicativo, escolhendo o ícone do logotipo, e selecionando um tema. Os temas podem ser ajustados para atender às suas necessidades específicas, usando o botão “Configure theme”. Neste exemplo vamos usar os valores padrão para o tema básico.

Sobre a aba “Base Layers”, podemos escolher qual serviço de mapa base que queremos usar e também selecionar as camadas que podem ser usadas como sobreposições. Para esta aplicação, vamos usar o MapQuest como a nossa camada de base para ajudar a mostrar o evento de chuva que possa ter ocorrido e fornecer ao usuário um contexto melhor do que um mapa de rodovia. As camadas de sobreposição proporcionam acesso a serviços que incluem clima quase em tempo real, rotulagem adicional, etc. Para este exemplo vamos usar o MapQuest Labels como serviço de sobreposição para mostrar nomes de cidades, estradas principais, etc. Agora vamos definir as camadas que desejamos colocar sobre o mapa base.

webapp4

Na guia “Layers” vamos configurar as camadas de dados que serão usadas em nossa aplicação. Por padrão, todas as camadas que foram adicionadas ao nosso projeto QGIS, com exceção das camadas base, vai aparecer na lista. No nosso caso temos apenas três camadas – se você tiver muitas camadas pode procurá-las usando a barra de busca na parte superior da caixa de diálogo. Queremos mostrar todas as camadas por isso vamos deixar todas marcadas.

webapp5-939x1024

No próximo post daremos continuidade na criação da nossa aplicação web, não perca!

by Fernando Quadro at April 28, 2016 10:14 AM

gvSIG Team

gvSIG Festival: Keep Calm More Info Coming Soon

by Alvaro at April 28, 2016 09:33 AM

April 26, 2016

OSGeo News

Astun Technology Renew Silver OSGeo Sponsorship

by jive at April 26, 2016 01:54 PM

longwayaround.org.uk

OpenLayers 2 Custom Build

A bit of a blast from the past now that OpenLayers 3 has been released but it may be useful for someone who is working on or maintaining an OpenLayer 2 project.

Create a list of OpenLayers 2 classes used within a code base suitable for including in a custom build profile.

cd /path/to/your/js/
grep --ignore-case --recursive --no-filename --only-matching 'new OpenLayers\.[a-z0-9\.]*' | \
sed -e 's/new //' -e 's/\./\//g' -e 's/$/\.js/' | \
sort | \
uniq

Explanation

  • Find instances of new OpenLayers.FOO in all source files below the current directory using grep
  • Remove "new " from each matching line, replace the dots which separate the parts of the class name with forward slashes and add .js to the end to complete the path all using sed (each -e applies an expression to each line)
  • Sort the list with sort
  • Remove duplicates with uniq

Caveats

Vector Renderers

If you find OpenLayers/Layer/Vector.js in the list then the vector rendering classes will need to be included manually:

OpenLayers/Renderer/Canvas.js
OpenLayers/Renderer/SVG.js
OpenLayers/Renderer/VML.js

Utility Classes

If you are using classes such as OpenLayers.Pixel, OpenLayers.LonLat. You will find that when using the build script you get an error as the source files can not be found as the class names do not match the location in the OpenLayers source. In most cases for these base classes you can simply remove them from the build config file as they will be automatically included as they are referenced by the other classes such as OpenLayers.Map.

by walkermatt at April 26, 2016 01:00 PM

Fernando Quadro

GeoServer 2.9 beta 2 released

A equipe do GeoServer anunciou no último dia 22 o lançamento do GeoServer 2.9-beta2. Na versão anterior 2.9-beta foi descoberta uma incompatibilidade com o Java 8, resultando em um planejamento de emergência e um atraso no cronograma de lançamento da versão 2.9.0.

Para esta versão podemos destacar como mais importante, os seguintes itens:

– Compatibilidade com o Java 8 (Oracle JDK e OpenJDK).
– GeoServer agora exige Servlet 3 (para Tomcat 7 ou superior, se você estiver fazendo uma instalação a partir de um arquivo WAR)
– Negative-date agora suportada (para compatibilidade com GeoNode)
– Nova API REST
– Atualização para Spring 4 e JAI-EXT 1.0.9

Esta versão 2.9-beta2 é lançada em conjunto com GeoTools 15-beta2 e GeoWebCache 1.9-beta2. Vale lembrar que versões beta são destinados ao feedback do público e não são recomendados para uso em produção.

Fonte: GeoServer Blog

by Fernando Quadro at April 26, 2016 10:23 AM

April 25, 2016

GeoSolutions

GeoSolutions’ Workshops at FOSS4G 2016

FOSS4G 2016

Dear Readers,

As we have previously announced, GeoSolutions will be attending FOSS4G Bonn 2016, from 22nd to 26th of August. Our technical lead Andrea Aime together with our Director Simone Giannecchini will hold a few workshops involving GeoServer:

August 22nd, Monday:

  • Web Mapping with OGC Services and GeoServer: an Introduction. 9.00-13.00. More information here.

August 23rd, Tuesday:

  • I have data with TIME, ELEVATION and other dimensions: what can GeoServer do for me? 9.00-13.00. More information here.
  • Enterprise class deployment for GeoServer and GeoWebcache: Optimizing performances and robustness. 14.00-18.00. More information here.

Find the detailed workshops program here. We will update this blogpost in order to give you the full and definitive information about our workshops and presentations as they are finalized.

Contact us if you want further information! Hope to see you in Bonn next August to talk about GeoServer, MapStore, GeoNetwork as well as to discuss our our Enterprise Support Services can help your organization reach his goals with confidence.

The GeoSolutions Team,

Geosolutions

by simone giannecchini at April 25, 2016 03:12 PM

Fernando Quadro

Encontre seu caminho com o OpenStreetMap

OpenStreetMap (OSM) não é só para as ruas, ele também contém uma quantidade impressionante de trilhas para caminhadas. A questão então é a seguinte: Como posso extrair a rota do OpenStreetMap e usá-lo no meu GPS?

É isso que Bjorn Sandvik ensina seu blog, através de um passo a passo de como planejou sua caminhada que cruzará os Alpes de Oberstdorf a Vernago (Alemanha).

Neste tutorial, você verá como baixar os dados do OSM no formato shapefile, selecionar sua rota e exportá-la no formato GPX para utilizar no seu GPS.

Fonte: MasterMaps

by Fernando Quadro at April 25, 2016 10:41 AM

Paulo van Breugel

VIF stepwise variable selection

Abstract In modelling, multicollinearity in the set of predictor variables is a potential problem. One way to detect multicollinearity is the variance inflation factor analysis (VIF). In GRASS GIS, the VIF for a set of variables can be computed using the r.vif addon. This addon furthermore let’s you select a subset of variables using a […]

by pvanb at April 25, 2016 09:09 AM

April 23, 2016

QGIS Blog

Promoting and using QGIS for the enterprise

Over the years, QGIS has gained more functionality, more users and more people and organisations who make their livelihood from it. As an Open Source project, there are two things that we value most highly (and equally):

  • Our community of users
  • Our community of project contributors

The two groups are intermingled, co-dependent and indispensable to the project. As both these groups have grown, our reach has grown. Now as a project we touch the lives of (by best estimation) hundreds of thousands of users and contributors around the world.

It is a natural consequence of such reach that QGIS has become an attractive platform for companies on which to build service based business models to their customers. From this rises the advent of ‘enterprise’ offerings – service packages tailored for large corporate and government institutions which need service level agreements, guaranteed turn around times, helpdesk support and so on. As a volunteer driven, grass roots project we are not in the position to, and do not have the interest in catering to this class of user base via support agreements etc. Commercial support is far better taken care of through third party service providers that have the infrastructure and legal means to set up such service offerings.

As the momentum grows around such enterprise services it is probably an inevitable consequence that tension may arise between third party service providers and the QGIS core project. In simplistic terms this tension can be seen as the dichotomy between those of us who view our work on QGIS as a labour of love versus those who see their work around QGIS as a labour of commercial enterprise. Of course there are many cases where the people providing such support do come from the community, do see their work as a labour of love, but as the stakes get higher and the size of support companies grows (to the point where they are also recruiting staff from outside the QGIS community), there is more opportunity for this dichotomy to realise itself.

The reality is that much like the relationship between project contributors and our community of users, there is a huge amount of potential symbiosis between the QGIS developer community and the growing number of value added resellers providing services around QGIS: many of the improvements, bug fixes and other enhancements produced by value added resellers make their way back into the core QGIS offering, whilst the body of work produced by the community of QGIS project contributors becomes the basis around which value added resellers build their marketplace offering.

Over the years we have tried to be sensitive to the fact that many people rely on QGIS for their livelihood – initiatives such as our Long Term Release programme, the creation of test suites and heavy investment of donated project funds into bug fixing (among many other similar initiatives) have all gone a long way to making QGIS a viable platform for value added resellers. We would like to ask that resellers give the QGIS project similar consideration in their marketing and work endeavours. As such I would like to present a few simple guidelines below that you should use as guiding principles in your interaction with the QGIS project. I will use a hypothetical company ‘ACME Corp.’ in my examples below:


Respect the license

QGIS is published under the GPL v2 or greater license. The letter of the license states that if you extend the source code  of QGIS, and publish those changes (for example by making it available on a download site for your users), you need to publish the source code changes too, making them available to your users. In the spirit of the license, you should share your improvements to QGIS with the greater project (e.g. by making your code tree publicly accessible).

Similarly when publishing a plugin, don’t ship it with proprietary binary ‘blobs’, or only with .pyc (compiled python files) leaving out the original python sources. If you do absolutely have to ship it with a binary (for example you need a c-compiled python module for your plugin), make sure to provide a clear trail to the upstream sources for those binary elements.

I personally find discussions of licensing get quickly tedious and I prefer to emphasise the spirit of open source rather than getting stuck in legalese: “We share our work with you, you share your work with us and we all benefit“. It’s really that simple for me. When you stray from this maxim, you are very likely to, at best, ruffle feathers and, at worst, create a really bad impression about your company and the people that work for it.

 

Don’t present your work as our work

It seems obvious, but many miss the nuance here. If you wrote a marvellous plugin to count sheep in farm fields because it will add great value to your customers, call it ‘ACME. Corp sheep counter’, not ‘QGIS Sheep Counter’. Also bear in mind that the word ‘QGIS’ is trademarked (the trademark is owned by the QGIS.org community). If you want to name your project, you should read our trademark guidelines. Contact us at trademark@qgis.org if you have any uncertainty about how you are using the word ‘QGIS’ in your brand.

Don’t present our work as your work

This is the corollary to the above. Our community works incredibly hard to make QGIS, the web site, the documentation, triage bugs, provide help on the mailing lists and forums. All that effort can be disregarded in a single line of careless copy like ‘QGIS by ACME Corp. is the next best thing since sliced cheese‘. Show a little love to the people that built the platform for your service offering and refer back to the parent QGIS project and its community as the progenitor of all the goodness you are sharing with your clients. That does not denigrate the valuable service that you provide your customers and it lets them know that you represent your company and work fairly and contribute back to the source project that you are basing your services on.

Friends don’t fork

Forking in Open Source is the process by which you create your own divergent copy of the  software and maintain it independently, often resulting in two incompatible versions (at the source code level) of the same project. Nobody really wins from that. Your customers lose the ability to migrate projects, workflows and knowledge between the community maintained version of QGIS and your modified one. In reality forking is normal (its the standard workflow in GitHub for example), but I really am referring to the process whereby you create an heavily diverged copy of the source code. When you create a divergent fork, your developers get stuck in a one directional highway which takes them further and further away from the original code base and any opportunity to capitalise on the work of other contributors from the QGIS community. There is also an economic imperative not to make a divergent fork – to quote community member Vincent Picavet:

“… forking a project is not a good idea in terms of economics. Maintaining software is more than half of the TCO [Total Cost of Ownership], and on the medium-long term, maintaining a fork of QGIS will cost much more than integrating the specific code into the master codebase, even if initial costs are higher for master integration.”

Don’t rebrand

Every few months I get an email from a value added service provider asking me if I can help them produce a version of QGIS which is rebranded as ‘ACME Corp. GIS’. By rebranding here I mean deep rebranding – not just replacing the splash screen (which I am generally OK with), but changing the word ‘QGIS’ everywhere in the source code and user interface to ‘ACME Corp. GIS’.  Beyond the fact that you instantly break all sorts of things like QGIS project file support, you also create a fork that will require massive amounts of maintenance  to keep in sync with the upstream project.

Integrate your team with the QGIS community

One great way to give your clients a good service and to ensure that your work is well accepted is to integrate your developers with the QGIS community. By that I mean let them subscribe to our mailing lists, participate in architecture and other discussions, fix issues, contribute code, attend our 6 monthly hackfests and generally be part of the ebb and flow of the project. There are so many benefits to doing this – both to QGIS and yourself – which is probably evidenced by the fact that the most well known QGIS value added service providers each have a number of developers participating in the community. My main motivation above all other reasons is that they will gain the sensitivity to know how to get your improvements integrated into the code base, and the trust and camaraderie of the other community members which is great when the time comes that they need help solving problems.

 

Integrate your work with the QGIS code base

Whereas above we ask you not to fork, how can you be sure your changes will be acceptable so that you do not need to maintain a fork? Whenever you are thinking about new features for your clients, I encourage you to think about how to make them generic enough that they can be incorporated into the main code base. Once you do that, you have an automatic delivery platform of your work to your users. QGIS has a well established release routine and the features shipped with QGIS get tested and used by many thousands of users. Besides you are benefitting from the features others are funding, why not pay the same compliment back by designing your features in a way that everyone can use them, not only your clients?

Keep us in the loop

There is so much going on around the QGIS project we often get surprised by things people do. More often than not it is a pleasant surprise but sometimes it isn’t. If you are planning some big new feature or creating a new service around QGIS, I highly recommend that you share it with the community early in your planning process. In particular for the case of new features that you would like to see in the main code base, coming along with an ACME Corp. 10,000 line code contribution with no prior consultation creates ample room for friction. If you want to know that a larger feature you are planning will be accepted, check out our QEP (QGIS Enhancement Proposal) process.

Don’t only contribute code

For some reason coders are treated as the main heros in the story of an Open Source project. Many people overlook the fact that there is a far larger team of translators, document writers, sys admins, authors, artists, testers and enthusiasts who contribute a massive amount of effort into the project. When you are thinking about how to contribute back to the project, take a moment to think about all the infrastructure around the project and how you might help that along – as well as the cool new features you plan to contribute to the code base.


 

There are many other things that you can do to integrate yourself into the community, but my real point in this article is that although QGIS is Free Software, it is not made for free. Take a look at the QGIS page on Ohloh if you want to get a feel for just how much effort has gone into QGIS. Many people have put a lot of sweat equity into QGIS and the only reward they get for their work (if they are lucky) is recognition and appreciation. Think of them when you build services on top of QGIS and find ways to acknowledge and motivate them!

Here’s looking forward to seeing many thousands of people making their livelihood by offering services around QGIS!

timsutton

Tim Sutton

(QGIS Project Chair)


by Tim Sutton at April 23, 2016 10:24 AM

April 22, 2016

GeoServer Team

GeoServer 2.9-beta2 released

The GeoServer team is pleased to announce the release of GeoServer 2.9-beta2. The previous 2.9-beta discovered an incompatibility with Java 8, resulting in a bit of emergency planning and a delay to the 2.9.0 release schedule.

Download bundles are available (zip, war, dmg and exe). A reminder that beta releases are intended for public feedback and are not recommended for production use.

Highlights:

  • This release requires Java 8 and is compatible with Oracle JDK and OpenJDK
  • GeoServer now requires Servlet 3 (so Tomcat 7 or newer if you are doing a WAR install)
  • Negative-date now supported (for GeoNode compatibility)
  • New REST API for installation status
  • For more information check the release notes for beta2 (history beta1|M0)
  • Update to Spring 4 and JAI-EXT to 1.0.9

This 2.9-beta2 release is released in conjunction with GeoTools 15-beta2 and GeoWebCache 1.9-beta2. Thanks to Jody Garnett (Boundless) and Kevin Smith (Boundless) for this release.

Beta Testing

The GeoServer Team has been hard at work to bring you this beta release. Thanks to the committers for taking part in the emergency spring-4 upgrade and community members joining for subsequent testing and quality assurance: Justin Deoliveira and Andrea Aimie, Emanuele Tajariol, Damiano Giampaoli, Ben Caradoc-Davies, Niels Charlier, Mauro Bartolomeoli, Jody Garnett, Jukka Rahkonen, Brad Hards, Kevin Smith, Chris Snider, Torben Barsballe, Christian Mueller, Luigi Pirelli  … and next you!

Here is our priorities for testing:

  • Seeking confirmation on Java 8 compatibility (test Oracle JDK and OpenJDK on a range of platforms)
  • Testing of the user-interface (although the team has performed extensive manual testing we need your help)
  • Release packaging (check for anything out of date, any issues starting up)
  • GeoServer security integration

We have a couple known issues to keep in mind when testing:

  • Windows installer “Install as service” needs a configuration change once installed (GEOS-7507)
    Open wrapper.conf and update contents with: wrapper.app.parameter.1=org.eclipse.jetty.start.Main
  • Windows installer “Run manually” may have an issue with startup.bat (GEOS-7509)
  • Several issues have been reported with the Demo Page (GEOS-7513)

About Geoserver 2.9

Articles, docs, blog posts and presentations:

The GeoServer team extends our thanks to wicket upgrade sprint sponsors: OSGeo, Boundless, Vivid Solutions, How 2 Map, San Jose Water Company, Transient and Geobeyond.

by jgarnett at April 22, 2016 12:02 AM

April 20, 2016

Andrea Antonello

Geoss2Go: a survey organizer and configurator for Geopaparazzi

If you are a Geopaparazzi user you might have dreamt many times of something that would allow to configure geopaparazzi for a particular survey with few clicks.

Well, you might remember that HydroloGIS participated to the MYGEOSS call for innovative apps by the European Commission and was one of the winning teams.

The result of all this is the app Geoss2Go and in this post I will explain you what it is capable of. Fasten your seat belts.

Installation


Geoss2Go can be simply installed from google play.

If one doesn't have access to google play, an APK binary ready for installation can be downloaded from the github releases page.

Create a new profile

Once launched, Geoss2Go will present the following view:




To create a new profile we can simply push the red button on the upper right part of the view.

Once pushed, the main profile info dialog will pop-up. There the user can insert a profile name and some description about the profile:



Once ok is pushed, the empty profile is created:

The profile's cardview gives information about its content, listing the number of basemaps, spatialite databases and forms.

Delete a Profile

Through the trashcan option it is possible to delete any loaded profile.

The user will be prompted to make sure profiles are not removed out of error:


  


Styling the Profile

Geoss2Go allows for a very simple styling. It is possible to apply a color to the profile cardview, in order to have a better visual feedback (colors are often useful to define categories).

Also the color plays and important role during the interaction with geopaparazzi.

By selecting the color palette button, the color selection dialog will pop-up:



Once pushed the ok button, the profile cardview will appear colored:

Adding data to the profile

To add data to a profile, the user needs to push the settings icon (the upper right icon of the cardview).

The view the opens is divided in different tabs, namely:


  • PROFILE INFO
  • BASEMAPS
  • SPATIALITE DATABASES
  • FORMS
  • PROJECT


Let's have a look at each of these.

Profile info

In this tab the main information about the profile are visualized:


  • name
  • description
  • creation date

Name and description can also be modified from this view, while the creation date is readonly.

From this tab it is also possible to activate the profile through the switch at the bottom of the view.



Since only one profile can be active at a time, the activation of a profile automatically disables the previous active profile, if there had been one.

Once a profile is active, in the main view it is marked with two red lines in the top and bottom part:

Basemaps

The Basemaps tab gives the possibility to add raster background maps to the configuration. Currently supported extensions are:

  • map: mapsforge maps
  • mbtiles
  • sqlite: sqlite databases containing rasterlite2 data
  • mapurl: mapurl files that can contain configurations for local or online service (tms or wms)


Through the plus button on the top right part of the view it is possible to browse the device's filesystem and select the resources to add.



It is possible to import mapurl definitions directly from WMS GetCapabilities url.

To do so:


  • first copy the WMS url to the device clipboard 
  • push the ADD WMS button on the right side of the action
  • a dialog will open. Paste the url into the text field



  • push the refresh button at the left of the text field to retrieve the available layers



  • select the desired layer and push ok. The mapurl file will be created and added directly to the list of basemaps



For the above example the WMS of the Province of Bolzano has been used as example.

Spatialite Databases

The Spatialite Databases tab gives the possibility to add vector databases to the configuration.

The database has to be a valid spatialite database with the extension sqlite.

Through the plus button on the top right part of the view it is possible to browse the device's filesystem and select the resources to add.



Forms

The forms tab gives the possibility to add a json file of forms definitions to use in the profile.

Once the file is added (through the upper right plus button), basic information and the names of the forms contained in the file are shown:



Project

It is also possible to bind a profile to a single project database. This happens only in the case in which the user selects a geopaparazzi database in this tab. In that case, as we will see later, from within geopaparazzi it will no longer be possible to open an existing project or create a new one.



Import and Export profiles

It is possible to import and export profile definitions. In the main view from the context menu in the actionbar, the two entries related to import and export have to be used.

Export

When pushing the Export Profiles menu entry, the profiles definitions are exported into a fixed file in the path:

/SDCARD_PATH/geoss2go/profiles_config.json

Import

When pushing the Import Profiles menu entry, the profiles definitions are imported from the fixed file in the path:

/SDCARD_PATH/geoss2go/profiles_config.json

The imported profiles are added to the profiles already present in the app.

In order to support sharing of data and profile configurations, the path of the data contained in the imported files are adapted to the sdcard path of the current device. This way relative paths in the sdcard are maintained and datasets can be loaded.

We will see this in the demo set showcase. In that case you download and import data that someone else prepared, but they will work in your device, even if the paths of the data refer to a different sdcard path.

Try it out with a demo project

To give you a better understanding about the possibilities of geoss2go, we prepared a demo profiles set for you.

Before starting with this make sure you have both geopaparazzi and geoss2go.

To go on it is mandatory that you run each app at least once.

Then download the profiles_config.json file and save it inside the folder:
/SDCARD_PATH/geoss2go

Download the demo dataset zip and extract it on your device's sdcard.

Once these steps were completed, inside the sdcard you should find, beyond others, the following structure:
sdcard
   |
   |-- geoss2go
   |        `-- profiles_config.json
   |-- geoss2go_demo
   |        |-- vienna
   |        `-- bolzano


If the above structure has been successfully created on your device, you are ready to import the demo profiles configuration.

Launch geoss2go and from the main view context menu select the Import Profiles entry.



Once run, the demo projects should have been instantly added to your main view:



Demo Bolzano

Let's have a look at the demo bolzano profile. It is actived already.

In the basemaps tab we find several layers coming from online mapping services:



In the spatialite databases tab one database is present:



The profile has also been personalized with a specific set of forms for the survey:



From the info available we know that there will be 3 different forms available in this profile:


  • Generalita' evento
  • Scheda danni
  • Colata detritica


No project file has been defined in the PROJECT tab, which means that with this profile, we can use any project we want and also create new projects.

Demo Bolzano in Geopaparazzi

So what happens once we launch geopaparazzi? Well, apparently nothing:



But the devil is in the details and as we recall, the profile defined 3 things:

  • basemaps
  • spatialite database
  • forms

So let's have a look at the available tile sources. They are available through the first icon in the actionbar:



As one can see in the image below, the only available data sources are the ones defined in the profile.



Usually Geopaparazzi has an add datasource button in this view. But when a profile is active, only those datasets can be used. No other dataset can be added or removed.

Well, once I select for example the source OI.ORTHOIMAGECOVERAGE.2011 and go to the mapview, I will be presented with the following nice map:



In background the aerial imagery is visible, which was expected. But what are those overlays?

Obviously the spatialite database! To have a look at it, we can access the context menu button and then select Spatialite data list from the menu.

Again we will be presented with a blue view, where the blue reminds the user about the fact that a certain profile is being applied.

The spatialite view shows one database with 4 tables, which are the ones visible in the map.



As for the basemaps, also here it is not possible to add or remove tables and databases.

Last but not least, also the forms have been personalized by the active profile.

If we try to add a new form based note from the mapview using the add note button:



The add note view will also appear personalized with blue background. And the available froms will be the ones defined in the profile:



If we open a form, the usual form layout will be presented:



Demo Vienna

Let's have a look at the demo of Vienna dataset. To do so you need to open geoss2go again and activate the right profile.

By now you should be able to do that and the result should look like:



Have a look at what is inside this profile. You might note, beyond other things that no form has been defined, but a project has been added.

Let's have a look what that means inside Geopaparazzi.

Demo Vienna in Geopaparazzi

Since the demo vienna profile had defined a fix project, Geopaparazzi needs to tell that the user once it opens. It does so by placing in background the color of the profile:



Exactly the same as for the Bolzano demo, the basemaps view only presents the sources defined in the profile:



And if we select the ortophoto, we will see the following in the map view:



Again, as for the Bolzano demo, a whole pile of vectorlayers are available from the profile definition. Since the Vienna demo has been though of as a sightseeing profile, data as museums, bikeways, campings and even the famous Xmas markets are available.



Conclusions

Geoss2Go can be an extremely powerful tool for professionals to better organize their work. But it can also be used to plan vacations (I do it), to keep data organized in categories, by nation, by project, by whatever necessary.

Together with Geopaparazzi it gives the possibility to standardize the layout of surveys for teams in a simple and effective way. Installing datasets and survey forms has never been that simple (remember the demo profiles import?).

We hope you will enjoy this app as much as we are already...



by andrea antonello (noreply@blogger.com) at April 20, 2016 09:58 AM

gvSIG Team

gvSIG 2.3: Working on new improvements

gvSIG_improvement

In 2015 we established a rule for releasing two gvSIG versions per year, that we achieved at the gvSIG 2.1 and gvSIG 2.2 versions. In 2016 the dynamics would be to release another two versions, gvSIG 2.3 and gvSIG 2.4, the first one before Summer and the other one at the end of this year. However we decided to broke the rules and we announced that we were going to release three gvSIG versions in 2016. Therefore we started the gvSIG 2.3 stabilization period in December in the last year, and in February we released the first RC version (release candidate to the final one). We planned to dedicate a few more resources to fix important bugs and release the final gvSIG 2.3 version.

However there have been good news that will make us follow the rules. That means, that we are going to delay the gvSIG 2.3 releasing some months, and only two versions are released instead three versions in 2016.

Good news? Yes, we aren’t going to provide resources to stabilize gvSIG because a large amounts of new functionalities have been contracted, that will allow to increase the quality of gvSIG (even more) and convert it in a more powerful GIS. These new developments have a deadline, so we have decided to dedicate all our resources to them. The secondary effect has been the delay of that version, that in the other side was changing the publishing dynamics.

And what are we working on? We are working in a large number of improvements. Some of them will be included at the next gvSIG 2.3 version. Here you have a short list with the main tasks:

  • External map providers like Google Maps or Bing Maps access.
  • Google Street View access.
  • LiDAR data access and management (in 2D Views as well as in 3D ones).
  • Vector data loading on 3D Views.
  • Extrusion in 3D Views.
  • Complete support of the projections database in 3D Views (currently it only supports EPSG:4326), so raster reprojection from 2D to 3D.
  • Geoprocessing for building layers detection and creation, and automatic height detection from LiDAR data.
  • LRS tools support for PostGIS database.
  • CSV files importer similar to the Libreoffice one.
  • New 3D functionalities (animation, temporary data…).
  • Raster architecture refactoring (note: If you are going to make raster developments we recommend you to contact us so that your work can be integrated with the changes to be made).
  • Projections support: finishing the transition started GDAL use in projections.

Now you sure will wait the next version enthusiastically.  

:-):-)


Filed under: development, english, gvSIG Desktop

by Mario at April 20, 2016 08:48 AM

Petr Pridal

Epsg.io: Transformation of coordinate systems

Epsg.io was successfully updated with latest EPSG database 8.9. We are happy to announce new features:

Transformation of coordinate systems

http://epsg.io/transform/ can transform one coordinate system into another just with one click.



Decimal to degrees/minutes/secs

To convert decimal to degrees/minutes/secs was never easier. Just click the button at http://epsg.io/transform/


Get coordinates on a map

Any place in the world in any coordinate system. Pick a location of your choice. You can choose from six different base maps at http://epsg.io/map/









by Hynek Přidal (noreply@blogger.com) at April 20, 2016 07:51 AM

April 19, 2016

Free and Open Source GIS Ramblings

Interview: QGIS in journalism

Last year, I published the short post QGIS on the rise with journalists showcasing how QGIS is used by journalists with examples from the Los Angeles Times and Financial Times.

The latest QGIS case study now features an interview with Steven Bernard (Interactive Design Editor at the Financial Times) by A. Neumann and T. Sutton.

QGIS is now an integral part of our mapping workflow. (…) I would say 80% of our maps are now produced in QGIS. read more …

It’s great to see all the great examples of QGIS used to communicate international news. Thanks to everyone involved in this interview for sharing this case study with the community!


by underdark at April 19, 2016 08:23 PM

Jackie Ng

MapGuide Open Source 3.1 pre-flight check

Okay, all systems should be go to start the release cycle for the first beta of MapGuide Open Source 3.1 real soon. A lot of time was wasted spent on refactoring the vagrant-based build system on Linux to ensure that making this and future releases of MapGuide and FDO a more simpler affair:

  • The bulk of the shell provisioning logic from our current Vagrantfiles have been offloaded to their own shell scripts, making the Vagrantfiles now a super-thin script that calls the main provisioning script with the right MapGuide/FDO branch names and version numbers
  • As a result, in terms of making future releases, we just have to update branch names and version numbers in one central location (the Vagrantfile) instead of what we currently do, which is updating the branch names and version numbers in all our shell scripts
These changes were made not only for the current build system, but also back-ported for use in producing future 3.0 and 2.6 point releases. Meaning once 3.1 drops, you should see 3.0.1 and 2.6.2 point releases following real soon.

So before we kick the build system into gear, I think I'll give a good week or two to pore through the current MapGuide/FDO/Fusion bug lists to see what stuff we can easily knock off before I hit the big red button.

by Jackie Ng (noreply@blogger.com) at April 19, 2016 02:08 PM

Fernando Quadro

A importância do Open Data para o Brasil

Na última semana tive uma experiência um pouco desagradável quando precisei acessar os dados espaciais da Secretaria Municipal de Meio Ambiente de São Paulo. Depois do episódio fiquei pensando: Será que os orgãos governamentais tem noção da importância de se ter essas informações disponíveis em portais de Open Data?

Eu sinceramente acho que eles não tem a dimensão do que a disponibilização dessa informação pode gerar tanto pra eles como órgão como para nós cidadãos.

A disponibilidade dessas informações é muito importante tanto para a área governamental, acadêmica e privada, pois a partir dela pode-se gerar inúmeros estudos, pesquisas e melhorias em diversos setores da sociedade.

8016184339_927ea75bd6

Hoje, já é possível apontar muitas áreas onde os dados abertos governamentais estão criando valor. Dentre essas áreas posso citar:

– Transparência e controle da Democracia
– Melhoria ou criação de produtos e serviços privados
– Inovação
– Melhoria na eficiência dos serviços públicos
– Melhoria na efetividade dos serviços públicos
– Acompanhamento do impacto de politicas públicas
– Produzir novos conhecimentos a partir da combinação de várias fontes de dados e enxergar padrões em grandes volumes de dados

Embora existam inúmeros exemplos de como os dados abertos já estão criando valor tanto social quanto econômico, ainda não sabemos que coisas novas se tornarão possíveis. Novas combinações de dados podem criar novos conhecimentos e descobertas, que podem levar a campos de aplicação totalmente novos. Isso já acontece desde o século XIX, quando o Dr. Snow combinou dados sobre mortes devido ao cólera com a localização das cisternas d’água. Isso levou à construção do sistema de esgoto de Londres e melhorou a saúde geral da população.

open_data_key

Existe um potencial inexplorado que pode ser libertado se transformarmos os dados públicos governamentais em dados abertos. Isso só irá acontecer se eles forem realmente abertos, ou seja, se não houver restrições (legais, financeiras ou tecnológicas) para a sua reutilização. Cada restrição exclui pessoas da possibilidade de reutilizar os dados públicos e torna mais difícil encontrar valiosas maneiras de fazê-lo. Para que o potencial de inovação seja realizado, dados públicos precisam ser dados abertos.

Então me pergunto: Se o órgão é público, as informações são geradas a partir de recursos públicos, porque estes dados ainda não estão públicos?



by Fernando Quadro at April 19, 2016 11:03 AM

Nathan Woodrow

Styling maps in QGIS is better when it’s interactive

I’m sure you are all well aware of my hate of blocking dialogs, and when it comes to styling QGIS has a few and they annoy me to no end. With new fancy map making tools like MapBox and CartoDB all having nice non blocking styling options it’s about time QGIS followed suit to bring better control and faster workflows to users.

The first stage of the dock is complete, pending feedback of course, and merged into master.

Introducing the map styling dock:

2016-04-19 20_27_00-Action center

Having the style (label only at the moment) options in a dock widget opens up some really nice workflows to map styling.

Firstly, now you don’t have to do the Open -> Change Setting -> Apply -> Close -> Open dance each time you want to change a layer style.  The dock is linked to the active layer in the legend so you can move around freely, update settings, and move on.

Second, we can now have a great workflow and allow for live updating. Yes you did read that right, it will live update the map as you change values. How bloody great is that!  Reducing the feedback loop is always the best.  If it can be done live, do it live.  There is a Reset button if you make a mistake.

Third, all styling options will now live in a single location going forward. Once we have moved style, diagrams, blend modes, it will be a one stop shop for styles with no annoying dialogs getting in the way.

In QGIS 2.14 we also have this awesome feature for rule based labels, however that added another dialog, and I wasn’t going move to a dock just to have another dialog block me two steps down the road. So now all the rules based labels dialogs are panels inside the main dock. When adding a new rule it will show the rule editor, and the list when not.  Remember how I said the dock updates the map live, well that also applies when you add/update rules.  The dock will update the canvas as the rule changes even before you hit save on the rule

2016-04-19 20_48_36-Action center

2016-04-19 20_48_28-Action center

The new styling dock is in master now, although might not be in the nightly build for a day or so.

You can check out some videos of the dock in action here:

Super keen on any feedback and ideas anyone might have.  Give it a try and let me know what you think.

EDIT: I would also like to add that what I have started/done is only possible because of the great work that has been done before me. Big thanks to all the people that have done work to enable me to make this feature,  label settings, threaded rendering, data defined buttons, etc.


Filed under: Open Source, qgis Tagged: qgis

by Nathan at April 19, 2016 10:58 AM

Jo Cook

PortableGIS 5.6

NOTE: Due to a couple of issues that have just been reported with this release, I’m working on fixing those and will release a new version asap. Unless it’s urgent, it might be better to wait before downloading!

I’m pleased to announce the latest release of Portable GIS. This version (v5.6) has the following changes:

  • QGIS 2.14 LTR
  • By popular demand: Geoserver 2.8

You can download the setup exe and the md5 checksum here.

Older versions are still available but have been archived to avoid confusion.

As always, please let me know of any problems via the Portable GIS google group.

Note that I will shortly be publicising a GitLabs repository for the changed files, along with developer and user documentation, to allow people to roll their own versions or contribute to development. This work is nearly complete, so watch this space!

April 19, 2016 10:20 AM

April 18, 2016

GeoSolutions

Developer’s Corner: GeoServer-Manager 1.7.0 released

GeoServer

Dear All, this short blog post is for sharing with you that we just released GeoServer-Manager version 1.7.0. Special thanks to all the contributors! This version of GeoServer-Manager is compatible with GeoServer 2.8.x and current Master (2.9.x) and requires Java >= 1.6.0. Here’s a list of most important changes:
  • #126  Add a DBType for Oracle Datastore
  • #162 Publish Shapefiles and GeoTiffs and assign workspaced style
  • #173 Add ArcGrid Support
For additional information you can check merged PR and closed Issues on the project's GitHub repository. If you have questions or if you just want to talk to us about the using the library in your project, please, subscribe to the mailing list here. In any case, do not hesitate to contact us.
Home:
https://github.com/geosolutions-it/geoserver-manager Download: https://github.com/geosolutions-it/geoserver-manager/releases Documentation: https://github.com/geosolutions-it/geoserver-manager/wiki
 
Regards, the GeoSolutions Team.
320x100_eng

by simone giannecchini at April 18, 2016 02:53 PM

gvSIG Team

EMT Valencia: ejemplo de geoportal de transporte público con software libre

Uno de los primeros proyectos que realizamos en la Asociación gvSIG fue la puesta en marcha del geoportal de EMT, la empresa municipal de transporte de Valencia. Hace ya más de un lustro desde que está en marcha y sigue siendo la web de referencia para consultar el cómo ir de un sitio a otro de la ciudad utilizando los distintos medios de transporte disponibles: metro, autobús, bicicleta, Valenbisi (servicio público de alquiler de bicicletas) o a pie.

Todo los desarrollos se realizaron sin gastar un euro en licencias, utilizando exclusivamente software libre y pese al tiempo que ha pasado sigue siendo uno de los planificadores de rutas de transporte urbano más completos que uno puede encontrar. Un ejemplo más de porqué la Asociación gvSIG se ha convertido en un referente internacional en geomática libre.

Mediante este geoportal podemos calcular cualquier ruta, indicando los medios de transporte que queremos utilizar y nos informará de las distintas rutas posibles, permitiendo evaluar cada una de ellas y seleccionar la más adecuada para el usuario. Entre los detalles de ruta llega incluso a calcular el ahorro de emisiones de CO2 causantes del efecto invernadero (comparándolo con la cantidad de árboles que harían falta para ahorrar dicha cantidad de CO2 en un día) respecto a realizar el mismo recorrido con un coche privado.

Además de las herramientas relacionadas directamente con el cálculo de rutas, el usuario encuentra un buen número de utilidades: descubrir qué elementos de interés hay cerca de un punto, consultar las rutas y horarios de cada línea de autobús, visualizar por categorías los puntos de interés, imprimir planos de ruta, etc.

A continuación tres vídeos que muestran en funcionamiento la aplicación…aunque lo mejor es que cuando vengáis a Valencia (por ejemplo, para las próximas Jornadas Internacionales de gvSIG) lo probéis y descubráis toda la utilidad de esta aplicación (http://www.emtvalencia.es/geoportal/)

Si esto es lo que hacíamos en nuestros inicios…imaginad qué podemos hacer ahora.

Si estás interesado en implantar soluciones de este tipo en tú organización, contacta con nosotros: info@gvsig.com . Además de contar con los mejores expertos en geomática libre estarás ayudando al mantenimiento y desarrollo de la tecnología gvSIG.


Filed under: Business, geoportal, gvSIG Association, Projects, spanish Tagged: autobus, metro, planificador, rutas, transporte

by Alvaro at April 18, 2016 12:05 PM

Fernando Quadro

Livro: Learning QGIS

Ainda a tempo para o QGIS 2.14 foi atualizado o livro “Learning QGIS 3rd Edition” para refletir as últimas melhorias realizadas no software.

Para comemorar a editora fez uma promoção para 100 cópias do livro que estão com desconto de 30% (para impressão) e 50% (para eBook), basta utilizar os seguintes códigos:

Livro impresso: 30% de desconto
Códido do cupom: prt30LeaQS

Livro digital (eBook): 50% de desconto
Código do cupom: LeaQSebok50

qgis_IMG0339

É importante ressaltar que os códigos são válidos até 30 de abril de 2016 ou até esgotar as 100 cópias promocionais.

Fonte: Free and Open Source GIS Ramblings

by Fernando Quadro at April 18, 2016 10:20 AM

gvSIG Team

gvSIG 2.3: Trabajando en nuevas mejoras

gvSIG_improvement

En 2015 establecimos la norma de publicar dos versiones de gvSIG al año, que cumplimos con la salida de gvSIG 2.1 y gvSIG 2.2. En 2016 la dinámica sería publicar otras dos versiones, gvSIG 2.3 y gvSIG 2.4, una antes de verano y otra para finales de año. Sin embargo, decidimos saltarnos la norma y anunciar que sacaríamos tres versiones de gvSIG en 2016. Para ello comenzamos el período de estabilización de gvSIG 2.3 en diciembre del año pasado y en febrero publicamos la primera RC (candidata a final). La previsión era dedicar unos pocos recursos más a corregir los bugs (errores) importantes destacados y ya publicar la versión final de gvSIG 2.3.

Sin embargo ha habido una buena noticia que va a provocar que nos saltemos la excepción y sigamos la norma. Es decir, que atrasemos la publicación de gvSIG 2.3 unos meses y, finalmente, en 2016 vean la luz dos versiones de gvSIG en lugar de tres.

¿Buena noticia? Sí, porque el motivo de no dedicar recursos a finalizar la estabilización de gvSIG ha sido la contratación de una gran cantidad de nuevas funcionalidades que van a permitir dar un salto de calidad (otro más) a gvSIG y convertirlo en un SIG todavía más potente. Esos nuevos desarrollos además tienen fecha de entrega, por lo que hemos tomado la decisión de dedicar todos nuestros esfuerzos a ello y como efecto secundario retrasar la salida de una versión que, por otro lado, se salía de la dinámica de publicación de versiones establecida.

¿Y en qué estamos trabajando? Pues en un buen número de mejoras, algunas de las cuales verán la luz en la próxima gvSIG 2.3. Aquí va un breve listado de las principales tareas:

  • Acceso a proveedores de mapas externos como Google Maps y Bing Maps.
  • Acceso a Google Street View.
  • Acceso y manejo de datos LiDAR (tanto en Vistas 2D como en Vistas 3D).
  • Carga de datos vectoriales en Vistas 3D.
  • Extrusión en Vistas 3D.
  • Soporte completo de la base de datos de proyecciones en Vistas 3D (actualmente sólo soporta EPSG:4326) y, por tanto, reproyección ráster de 2D a 3D.
  • Geoprocesos para detección y generación de capas de edificaciones, y detección automática de alturas a partir de datos LiDAR.
  • Soporte de las herramientas de LRS/Segmentación Dinámica para bases de datos PostGIS.
  • Importador de ficheros csv al estilo LibreOffice.
  • Nuevas funcionalidades 3D (animaciones, datos temporales,…)
  • Refactoring de la arquitectura ráster de gvSIG. (nota: Si vas a hacer desarrollos ráster, te recomendamos que te pongas en contacto con nosotros, para que tu trabajo se pueda integrar con los cambios que se van a realizar).
  • Soporte a proyecciones: finalizar la transición iniciada para el uso de GDAL en proyecciones.

Ahora seguro que todavía esperareis con más ganas la salida de la próxima versión de gvSIG.

:-):-)


Filed under: development, gvSIG Desktop, spanish Tagged: 3D, Bing Maps, Google Maps, gvSIG 2.3, LiDAR, Street View

by Alvaro at April 18, 2016 08:52 AM

April 17, 2016

Bjorn Sandvik

Finding your way with OpenStreetMap

OpenStreetMap is not only for streets, it also contains an impressive amount of hiking trails. I’m currently planning a a week’s hike in June, crossing the Alps from Oberstdorf to Vernago. How can I extract the route from OpenStreetMap and use it on my GPS?

The route visualised in CartoDB. Interactive version.
The BBBike extract service allows you to download OSM data for your region of choice.

You can select your area of interest by using the map interface, or by specifying the map bounds coordinates. 
I selected an area covering the entire route, and ordered the data in a Shapefile format. Within a minute I received an email with a download link.

The extract contains 8 shapefiles, and we only need the roads shapefile, which also contains hiking trails. If I open the shapefile in QGIS it looks like this:

Roads and hiking trails in the Alps.  
You'll have great difficulties finding your trail on this map, so let's add a basemap from OpenStreetMap.  Save this as an XML file on your computer:


Drag the file onto your QGIS dashboard. If you do this before loading the roads shapefile you'll make sure that they are displayed in the same projection, and that the roads and trails are shown on top:

OSM road network shown on top of OSM map tiles in QGIS.
It's still hard to distinguish hiking trails from roads, as they all look the same. We can easily change the style of hiking trails in the style editor:

Select categorized style and give the path type an extra boost so it stands out on the map. 
The paths are now easier to see:

Paths marked in red.
Next we need to select the path we plan to follow. Use the "Select Features(s)" tool and click on the path segments you plan to follow.



Select the path segments you plan to follow. 
When you've marked your route, you can right click the roads layer and select "Save As...". Check that you only want to save selected features:

Save your track as a new shapefile.
It's best to have your route as a continuous line (or one for each day if you're on a long trek), and you can use the "Join multiple lines" plugin in QGIS to achieve this. The plugin will also handle gaps in your route by drawing a direct line between them.

Just select the full path and click on "Join multiple lines". Save the results. 

We now have a shapefile of our planned hiking route, thanks to OpenStreetMap, BBbike and QGIS.

Next, I want to upload the shapefile to CartoDB to create an interactive map showing of the route (also shown as the first image above). You can also study the route on top of detailed aerial imagery from Bing on my tracking site:

Interactive version (click on "Route" in the top menu.
You can also save your track as a KML file in QGIS, and open it in Google Earth - a great way of getting a visual impression of the hike before you go.

Planning your hike with Google Earth. 

The last step is to upload the track to your GPS so you can use it for navigation. Open the track shapefile in QGIS, and save it in the GPX format.

Right click the track layer and select "Save As..."

I then use Garmin Basecamp to transfer the route to my GPS:

Transfer the route to your GPS device.
Then we're ready for takeoff!

by Bjørn Sandvik (noreply@blogger.com) at April 17, 2016 10:30 AM

April 15, 2016

Free and Open Source GIS Ramblings

Learning QGIS 3rd ed. discounts

In time for QGIS 2.14 (soon to be LTR), I have updated “Learning QGIS” to reflect the latest improvements of our favorite GIS.

To celebrate, we are giving away 100 copies of the book at 30% (for print) and 50% (for eBook) discount if you use the following codes:

30% off  the Print version
Code: prt30LeaQS

50% off the eBook version
Code: LeaQSebok50

(Codes are valid until 30th April 2016 or we’ve reached 100 copies.)

B05278_MockupCover_Normal


by underdark at April 15, 2016 06:08 PM

From GIS to Remote Sensing

A study about demographic growth and remote sensing presented at FOSS4G Argentina 2016


I was recently informed that the Semi-Automatic Classification Plugin (SCP) for QGIS is cited in an interesting paper (in Spanish) by Patricia Alejandra Rosell and Magalí Natalia Vicente (graduated at the Departamento de Ingeniería de la Universidad Nacional del Sur, Bahía Blanca, Argentina), which was presented at the FOSS4G Argentina 2016 (Conferencia de Geomática Libre Buenos Aires, Argentina. 5-9 de Abril), an important conference about free geographic software.
The authors used several Landsat images, processed using the SCP, in order to calculate spectral indices related to built-up, and estimating urban growth from 1986 to 2015 in the study area of Puan Partido (Buenos Aires Province, Argentina).

The NDVI calculated for 1986 (Rosell and Vicente, 2016)

by Luca Congedo (noreply@blogger.com) at April 15, 2016 05:38 PM