Welcome to Planet OSGeo

February 12, 2016

Margherita Di Leo

A Geospatial report of FOSDEM16

FOSDEM is a huge free non-commercial conference gathering open source developers from all over the world. It is the most important event of this kind, held every February at ULB, Brussels since 2000. It is always amazing how a conference that is offered for free could reach such a high level of offer in terms of content and services. Remember that it is also possible to sponsor it. FOSDEM 2016 was another successful edition, fully packed with interesting talks.




Several presentations of interest for the "geospatial" world were also given. Most of them were concentrated in "our" geospatial devroom, that was organised this year for the second time by members of various geo communities such as OSGeo, LocationTech and OSM, and coordinated by Johan van der Wauw. The devroom was well attended, and featured a wide overview of recent developments in geospatial applications. Talks have been recorded and will be available soon on FOSDEM website; slides of each presentation are also being added to the talks listed on the Geospatial devroom page.



We presented the results of OSGeo students who took part in Google Summer of Code 2015, featuring for each project one slide with a short description provided by the students themselves. We had asked the students to summarize their work in a template describing the state of the project before and after their contribution, enhancing their addition. Some students also provided a graphical image to better summarize the project.
We had the pleasure of having Stephanie Taylor and Mary Radomile, from Google's GSoC organisation team, among the audience, who kindly made themselves available for answering questions regarding the program. Mentoring organisations' application period for GSoC 2016 starts in a few days - we're going to apply again for OSGeo, keep fingers crossed!



The geospatial devroom confirmed itself as the reference event at FOSDEM for the "geospatial people". For next year, an idea could be to look for sponsorship in order to facilitate keynotes or speakers that request travel grants, like for example this year could have been the case for GSoC students to come and present their work themselves. 



At least a couple of keynote talks deserve mention as well. The first was a really moving tribute in memoriam of Ian Murdock, one of the founders of the Debian project recently passed away.




The other was given by Blake Girardot and summarised the outstanding work carried out by the Humanitarian OpenStreetMap Team (HOT).



A report by madi and anne, GSoC 2015 admins @OSGeo

by Margherita Di Leo (noreply@blogger.com) at February 12, 2016 02:08 PM

February 11, 2016

Narcélio de Sá

QGIS – Criando um mapa de localização

Olá galera, gravei esse vídeo tutorial por conta da solicitação do colega Alexandre Santos, lá no grupo de discussão da comunidade QGIS Brasil.

Esse grupo é , se não o maior, um dos maiores repositório de conteúdos sobre QGIS na internet brasileira. São mais de 1800 integrantes trocando conhecimentos com uma média de 300 postagens por mês.

Criando o mapa de localização no QGIS

Lá no grupo o Alexandre fez a seguinte questão:

Prezados Listeiros,

Gostaria de fazer um mapa implodido da área de estudo, como demonstrado na figura abaixo, alguém conhece algum tutorial, imagino que uma figura como essa use QGIS + GIMP, muito obrigado,

Modelo QGIS

Alexandre

E nesse vídeo tutorial eu apresento uma forma de criar um mapa nos moldes desse que o Alexandre apresentou. O vídeo é um pouco longo, por isso eu criei um sumário onde é possível pular para uma parte específica do vídeo.

Sumário do vídeo:

Apresentação
Criação das regras de simbologia
Configurando pre-definições
Criando compositor de impressão
Adicionando pre-definições
Conectando os mapas com as linhas
Adicionando escala e norte
Exportando mapa para figura
Inserindo mapa em documento de texto

Nos link abaixo você pode baixar os arquivos utilizados no tutorial:

Dados a nível mundial: http://www.naturalearthdata.com/downloads/
Dados a nível nacional e estadual – IBGE 2014: ftp://geoftp.ibge.gov.br/malhas_digitais/municipio_2014/

Música utilizada no vídeo: The Fiery Furnace – Ethan Meixsell http://bit.ly/20TzLdc

The post QGIS – Criando um mapa de localização appeared first on Narcélio de Sá.

by Narcélio de Sá at February 11, 2016 08:00 PM

Fernando Quadro

GISVM: Uma máquina virtual para GIS

As vantagens de utilização de software de código aberto e licenciamento livre, na área das Geotecnologias, são hoje reconhecidas internacionalmente. É indiscutível o seu sucesso em inúmeros projetos, incluindo os de grande envergadura e complexidade, demonstrando a maturidade e a fiabilidade daquelas soluções. Apesar disso, persistem ainda dificuldades dos usuários em dar os primeiros passos na adoção de software livre, principalmente os que usam software fechado e que demonstram uma natural inércia à mudança para esse novo mundo.


gisvm_small

A GISVM, do inglês Geographic Information System Virtual Machine, é uma máquina virtual construída exclusivamente com software livre, e concebida para facilitar a iniciação em soluções de software livre para Sistemas de Informação Geográfica (GIS).

Criada na plataforma VMware, tem pré-instalado o sistema operacional Ubuntu (Linux) e um conjunto de aplicativos para GIS, devidamente configurados e prontos para utilização. Do vasto conjunto de aplicativos disponíveis no mercado de software livre para GIS, foram selecionados alguns dos mais populares de forma a disponibilizar as principais ferramentas que um usuário possa necessitar para a área das Geotecnologias.

Você pode obter mais informações sobre o GISVM lendo um artigo na página 15 da 3ª edição da Revista FOSSGIS Brasil.

by admin at February 11, 2016 05:29 PM

Le blog de Geomatys

Constellation-SDI s’exporte en Bolivie

L’UMSA (Universidad Mayor de San Andres), responsable du portail Geovisor Bolivien, a choisi d’utiliser le logiciel Constellation-SDI pour la diffusion des images satellites de la zone au travers  de son portail.  Le prototype du portail géographique universitaire GeoVisor IIGEO a pour but de valoriser les recherches UMSA-IRD sur l’environnement et les sociétés par l’analyse spatiale et historique des données, informations et […]

by Dorian Ginane at February 11, 2016 10:00 AM

gvSIG Team

gvSIG en la radio

Ayer tuve la oportunidad de hablar sobre Sistemas de Información Geográfica, geomática libre y gvSIG en la Cadena COPE, una emisora de radio de España y dentro de un programa dedicado al Colegio Oficial de Ingeniería Geomática y Topográfica. Toda una experiencia esto de estrenarse en las ondas.

Os dejo con la grabación:

http://www.ivoox.com/2016-02-10-coigt-hablando-sig-gis-audios-mp3_rf_10387856_1.html

radio


Filed under: opinion, press office, spanish

by Alvaro at February 11, 2016 09:27 AM

February 10, 2016

portailSIG

Python à finalité géospatiale: pourquoi débuter avec le module ogr alors qu'il existe des alternatives plus simples et plus didactiques ?

Niveau Débutant
Logiciels utilisés Python
Plateforme Windows | Mac | Linux | FreeBSD

La plupart des débutants dans l'utilisation des modules Python à finalité géospatiale libres commencent par le module GDAL/OGR, nommé osgeo dans la suite, du fait que l'importation du module se fait par la commande (et non open ogr).

from osgeo import ogr

Le module est certes très puissant lorsqu'on le connait bien (voir Python: utilisation des couches vectorielles et matricielles dans une perspective géologique, sans logiciel SIG , par exemple) mais son problème, pour les débutants, est qu'il est relativement difficile à appréhender, complexe à utiliser et relativement peu "Pythonesque" du fait de sa conception (interfaçage de la librairie C++ originale). Ceci n'est pas une critique, loin de là, mais je trouve qu'il est peu adapté pour débuter alors qu'il existe d'autres modules plus faciles à comprendre.

Il suffit de se rendre sur des sites comme GIS StackExchange ou le ForumSig pour s'en rendre compte: la prise en main du module est loin d'être évidente lorsqu'on débute...

De la complexité des choses...

Le très beau site Python GDAL/OGR Cookbook est une des références pour l'utilisation du module, hormis les livres. Il illustre la plupart des traitements qui peuvent être effectués. Prenons le cas de la création d'un simple Polygone qui se fait de la manière suivante (Create a Polygon):

from osgeo import ogr
# Create ring
ring = ogr.Geometry(ogr.wkbLinearRing)
ring.AddPoint(1179091.1646903288, 712782.8838459781)
ring.AddPoint(1161053.0218226474, 667456.2684348812)
ring.AddPoint(1214704.933941905, 641092.8288590391)
ring.AddPoint(1228580.428455506, 682719.3123998424)
ring.AddPoint(1218405.0658121984, 721108.1805541387)
ring.AddPoint(1179091.1646903288, 712782.8838459781)
# Create polygon
poly = ogr.Geometry(ogr.wkbPolygon)
poly.AddGeometry(ring)

Il faut

  1. créer une géométrie ogr (LinearRing), c'est-à-dire, l'enveloppe linéaire extérieure du polygone;
  2. la « peupler » avec des points au format ogr, qui vont la définir;
  3. créer une géométrie ogr Polygon;
  4. et enfin le construire à partir de son enveloppe extérieure.

Il existe d'autres modules qui permettent de le créer de manière beaucoup plus simple (comme geojson, Shapely, PyGeoif, Shapy Karta, GeoDjango ou GeoPandas)

# Create polygon
poly = {
    'type': 'Polygon',
    'coordinates': [[
        (1179091.1646903288, 712782.8838459781),
        (1161053.0218226474, 667456.2684348812),
        (1214704.933941905, 641092.8288590391),
        (1228580.428455506, 682719.3123998424),
        (1218405.0658121984, 721108.1805541387),
        (1179091.1646903288, 712782.8838459781) ]]}

ou

Polygon([(1179091.1646903288, 712782.8838459781),(1161053.0218226474, 667456.2684348812),(1214704.933941905, 641092.8288590391),(1228580.428455506, 682719.3123998424),(1218405.0658121984, 721108.1805541387),(1179091.1646903288, 712782.8838459781)])

Notons que rien ne vous empêche à ce stade d'utiliser le dictionnaire précédent (poly) pour créer une géométrie ogr

import json
poly = json.dumps(poly)
polygon = ogr.CreateGeometryFromJson(poly)

De la simplification des choses...

Le but de ces nouveaux modules est donc clairement de simplifier la vie des utilisateurs en n'utilisant que des simples objets Python standards, listes, dictionnaires et arrays NumPy pour traiter les données sans faire appel à des commandes externes comme osgeo, PyQGIS ou ArcPy, à titre d'exemple.

  1. Leur particularité est qu'ils disposent tous du protocole Geo_interface (voir Les modules Python à finalités géospatiales: quid, quando, ubi ?) où, en simplifiant, tous les traitements se font à l'aide de simples dictionnaires Python (voir Python Geo_interface applications)
  2. Certains d'entre eux se basent, tout comme osgeo, sur la librairie GDAL/OGR (simplification des procédures avec un autre interfaçage de la librairie C++ originale), d'autres sur la librairie C++ GEOS, d'autres sont écrits en pur Python et enfin certains combinent le tout avec le module Pandas, module de plus en plus utilisé dans le monde scientifique (équivalent aux dataframes  de R avec une kyrielle d'applications, voir Sam & Max: Le pandas c’est bon, mangez-en, par exemple);
  3. Certains fournissent des lignes de commandes comme ogr_info, etc.
  4. Ils sont disponibles pour les versions 2.7.x et 3.x de python

Ils sont donc particulièrement adaptés aux débutants comme nous allons le voir. Nous nous focaliserons ici sur les couches vectorielles, laissant les couches rasters pour plus tard.

Lire des couches vectorielles

Nous utiliserons ici Fiona et GeoPandas qui sont les plus connus de cette « nouvelle vague » pour les explications.

Lecture

Je vous laisse découvrir les principes de lecture d'un fichier shapefile avec le module osgeo dans Cookbook: Vector Layers. Vous constaterez qu'il  faut beaucoup de lignes et de commandes à retenir pour simplement extraire le schéma d'un fichier shapefile, sa projection et les géométries et données de la table attributaire....

Avec Fiona

Comme déjà dit auparavant, c'est un nouvel interfaçage de la librairie C++ GDAL/OGR et donc comparable à osgeo.ogr. Tout se fait avec des dictionnaires Python.

import fiona
# j'ouvre le fichier dans un itérateur Python
couche = fiona.open('strati_or.shp')
# le schéma de couche
couche.schema
{'geometry': 'Point', 'properties': OrderedDict([(u'id', 'int:10'), (u'dip', 'int:2'), (u'dip_dir', 'int:3'), (u'dir', 'int:9'), (u'type', 'str:10'), (u'x', 'int:10'), (u'y', 'int:10')])}
# la projection de la couche
couche.crs # au format proj4
{u'lon_0': 4.367486666666666, u'ellps': u'intl', u'y_0': 5400088.438, u'no_defs': True, u'proj': u'lcc', u'x_0': 150000.013, u'units': u'm', u'lat_2': 49.8333339, u'lat_1': 51.16666723333333, u'lat_0': 90}
# premier élément
couche.next()
{'geometry': {'type': 'Point', 'coordinates': (272070.600041, 155389.38792)}, 'type': 'Feature', 'id': '0', 'properties': OrderedDict([(u'id', 0), (u'dip', 30), (u'dip_dir', 130), (u'dir', 40),(u'type', u'incliné'), (u'x', 272071), (u'y', 155389)])}
# d'où
elements = [elem for elem in couche]
elements[0]['geometry']
{'type': 'Point', 'coordinates': (272070.600041, 155389.38792)}
elements[0]['properties']
OrderedDict([(u'id', 0), (u'dip', 30), (u'dip_dir', 130), (u'dir', 40), (u'type', u'inclin\xe9'), (u'x', 272071), (u'y', 155389)])
elements[0]['properties']['dip_dir']
130

Vous comprenez alors aisément que tous les traitements se résument à la simple manipulation de dictionnaires (modifier le schéma d'un shapefile ou modifier un élément de la table attributaire par exemple). Pour traiter ensuite les données, vous avez l'embarras du choix avec Shapely (géométries, ou les autres déjà cités)  NumPy, SciPy, Scikit-learn ou autres modules spécifiques.

Avec GeoPandas

Avec ce  module, vous entrez dans un autre monde encore peu connu des géomaticiens, le module Pandas. Vous créez directement un DataFrame, ou une Serie Pandas (respectivement GeoDataFrame et GeoSeries) à l'aide des modules Shapely et Fiona. Le traitement des DataFrames Pandas est abondamment illustré sur Internet.

import geopandas as gp
# création d'un GeoDataframe à partir du fichier shapefile
couche = gp.GeoDataFrame.from_file('strati_or.shp')
# affichage classique avec Pandas des 5 premiers éléments du DataFrame couche 
couche.head()
   dip  dip_dir  dir                             geometry  id      type     x       y  
0   30      130   40   POINT (272070.600041 155389.38792)   0   incliné   272071  155389 
1   55      145   55  POINT (271066.032148 154475.631377)   1  retourné   271066  154476
2   40      155   65  POINT (273481.498868 153923.492988)   2   incliné   273481  153923
3   80      120   30  POINT (270977.604378 153144.810665)   3  retourné   270978  153145
4   40      130   40  POINT (267162.940066 150990.398109)   4   incliné   267163  150990
# aperçu rapide des propriétés de la couche
couche.describe()
             dip     dip_dir         dir         id              x         y  
count  12.000000   12.000000   12.000000  12.000000      12.000000      12.000000 
mean   59.416667  170.416667   80.416667   5.500000  270592.666667  152742.166667 
std    21.094844   71.147042   71.147042   3.605551    2508.060364    2508.06036 
min    30.000000  120.000000   30.000000   0.000000  267163.000000  2150442.000000  
25%    40.000000  133.750000   43.750000   2.750000  268675.500000   150910.750000
50%    57.500000  145.000000   55.000000   5.500000  270824.500000  152728.000000    
75%    78.500000  155.000000   65.000000   8.250000  272423.500000  154375.000000   
max    90.000000  327.000000  237.000000  11.000000  274188.000000  155389.000000   

Vous pouvez alors utiliser toutes les fonctions de GeoPandas ou de Pandas pour traiter les données géométriques et numériques et utiliser le pandas Ecosystem (Statsmodels, Sklearn-pandas, etc) en plus des modules précédemment cités.

Avec les autres

Ce protocole de lecture des données sous forme de dictionnaire (geo_interface) peut être appliqué avec d'autres modules, voir ogr_geointerface.pyPyShp_geointerface.pyPostGIS_geointerface.py, spatialite_geointerface.py, ou mapnik_geointerface.py.

Exemple avec PyShp (shapefile):

def records(filename):  
    # generateur 
    reader = shapefile.Reader(filename)  
    fields = reader.fields[1:]  
    field_names = [field[0] for field in fields]  
    for sr in reader.shapeRecords():  
        geom = sr.shape.__geo_interface__  
        atr = dict(zip(field_names, sr.record))  
        yield dict(geometry=geom,properties=atr)    
import shapefile
elem = records('strati_res.shp')
elem.next()
{'geometry': {'type': 'Point', 'coordinates': (272070.600041, 155389.38792)}, 'properties': {'dip_dir': 130, 'dip': 30, 'cosa': -0.6428, 'sina': -0.6428}}

 Exemple avec osgeo:

def records(shapefile):  
    # generateur
    reader = ogr.Open(shapefile)
    layer = reader.GetLayer(0)
    for i in range(layer.GetFeatureCount()):
        feature = layer.GetFeature(i)
        yield json.loads(feature.ExportToJson())
from osgeo import ogr
elem = records('strati_res.shp')
elem.next()
{'geometry': {'type': 'Point', 'coordinates': (272070.600041, 155389.38792)}, 'properties': {'dip_dir': 130, 'dip': 30, 'cosa': -0.6428, 'sina': -0.6428}}

Sauvegarder des couches vectorielles

Avec Fiona

Vous sauvegardez des dictionnaires Python. Par exemple dans l'exemple suivant, je veux créer un nouveau shapefile basé sur le précédent en créant de nouveaux champs et en éliminant certains:

import fiona
from fiona.crs import from_epsg
 # définition des fonctions de calcul
import math
sind = lambda x: math.cos( math.radians(x))
cosd = lambda x: math.cos( math.radians(x))
# définition du schéma du nouveau shapefile
schéma = {'geometry': 'Point', 'properties': {'dip' : 'int:2', 'dip_dir' :'int:3', 'cosa': 'float:11.4','sina':'float:11.4'}}
# définition du crs du nouveau shapefile
crs = from_epsg(31370) # ou en reprenant simplement le crs du shapefile en entrée, comme dans la suite
# je le remplis avec le dictionnaire
with fiona.open('strati_or.shp') as entree:
   with fiona.open('strati_res.shp','w',driver='ESRI Shapefile', crs=entree.crs,schema= schéma) as sortie:
       for elem in entree:
          # conctruction du dictionnaire et sauvegarde 
          geom = elem['geometry'] # puisque c'est la même géométrie
          prop = {'dip': elem['properties']['dip'],'dip_dir': elem['properties']['dip_dir'], 'cosa': cosd(elem['properties']['dip_dir']), 'sina': sind(elem['properties']['dip_dir']) }
          sortie.write({'geometry':geom, 'properties': prop})

Avec GeoPandas

C'est encore plus simple, car après avoir effectué les changements dans le GeoDataFrame précédent  (couche),  il suffit, pour  sauvegarder le shapefile résultant de:

couche.to_file('strati_res.shp')

Quelques exemples pour vous convaincre

Je reprendrai ici quelques-unes de mes réponses sur GIS StackExchange

Pour ceux qui sont allergiques au format GeoJSON

Vous pouvez utiliser Shapely ou GeoPandas pour transformer vos géométries au format WKT par exemple, mais il y a une solution plus simple, le module geomet

elem= {'geometry': {'type': 'Point', 'coordinates': (272070.600041, 155389.38792)}, 'properties': {'dip_dir': 130, 'dip': 30, 'cosa': -0.6428, 'sina': -0.6428}}
from geomet import wkt
print wkt.dumps(elem['geometry'], decimals=2)
POINT (272070.60 155389.39)

Pour ceux qui préfèrent les commandes (ogr_info, ogr2ogr, etc.)

Fiona dispose de la commande Fio avec autant de possibilités que les commandes d'OGR (voir Fiona-Rasterio-Shapely Cheat Sheet)

$ fio info strati_or.shp
{"count": 12, "crs": "+ellps=intl +lat_0=90 +lat_1=51.1666672333 +lat_2=49.8333339 +lon_0=4.36748666667 +no_defs +proj=lcc +units=m +x_0=150000.013 +y_0=5400088.438", "driver": "ESRI Shapefile", "bounds": [267162.940066, 150441.970164, 274188.072595, 155389.38792], "crs_wkt": "PROJCS[\"Belge_1972_Belgian_Lambert_72\",GEOGCS[\"GCS_Belge 1972\",DATUM[\"Reseau_National_Belge_1972\",SPHEROID[\"International_1924\",6378388,297]],PRIMEM[\"Greenwich\",0],UNIT[\"Degree\",0.017453292519943295]],PROJECTION[\"Lambert_Conformal_Conic_2SP\"],PARAMETER[\"standard_parallel_1\",51.16666723333333],PARAMETER[\"standard_parallel_2\",49.8333339],PARAMETER[\"latitude_of_origin\",90],PARAMETER[\"central_meridian\",4.367486666666666],PARAMETER[\"false_easting\",150000.013],PARAMETER[\"false_northing\",5400088.438],UNIT[\"Meter\",1]]", "schéma": {"geometry": "Point", "properties": {"id": "int:10", "dip": "int:2", "dip_dir": "int:3", "dir": "int:9", "type": "str:10", "x": "int:10", "y": "int:10"}}}

Conclusions

Alors bien sûr, ces modules ne peuvent pas faire tout ce que fait le module osgeo, car ils ne s'adressent qu'à des fichiers (et non à l'accès des données provenant de SBGD comme PostGIS, MongoDB, CouchDB, SpatiaLite et autres ou le traitement des services WFS, par exemple, c'est d'ailleurs souligné dans les "Rules of Thumb" du Manuel de Fiona par Sean Gillies).  Mais ils peuvent servir à créer des fichiers à partir de ces données comme dans la question  Forum SIG: Python avec osgeo.org, ouvrir un WFS - Débutant;

D'après mon expérience, ils sont beaucoup plus faciles à maîtriser pour les débutants et sont plus rapides que PyQGIS (ou ArcPy d'après mes collègues) pour les mêmes traitements. Une fois compris, il est beaucoup plus facile d'aborder le module osgeo.

Alors pourquoi débuter avec osgeo.ogr ?

Site officiel : Python: traitement des couches vectorielles dans une perspective géologique, lecture et enregistrement des couches sous forme de dictionnaires avec le module Fiona


Creative Commons License
licence Creative Commons Paternité-Pas d'Utilisation Commerciale-Pas de Modification 2.0 France

by Martin Laloux at February 10, 2016 08:22 PM

OSGeo News

Welcome to the University of Trento to GeoForAll

by jsanz at February 10, 2016 06:30 PM

OSGeo News

Welcome to the University of Heidelberg to GeoForAll

by jsanz at February 10, 2016 06:12 PM

Free and Open Source GIS Ramblings

QGIS 3.0 plans

News about the path to QGIS 3.0 …

QGIS.org blog

qgis-icon-60x60

Ok so quick spoiler here: there is no QGIS 3.0 ready yet, nor will there be a QGIS 3.0 for some time. This article provides a bit more detail on the plans for QGIS 3.0. A few weeks ago I wrote about some of the considerations for the 3.0 release, so you may want to read that first before continuing with this article as I do not cover the same ground here.

lot of consideration has gone into deciding what the approach will be for the development of QGIS 3.0. Unfortunately the first PSC vote regarding which proposal to follow was a split decision (4 for, 3 against, 1 abstention and 1 suggestion for an alternative in the discussion). During our PSC meeting this week we re-tabled the topic and eventually agreed on Jürgen Fischer’s proposal (Jürgen is a QGIS PSC Member and the QGIS Release Manager) by a much more unanimous…

View original post 1,208 more words


by underdark at February 10, 2016 10:48 AM

QGIS Blog

QGIS 3.0 plans

 

qgis-icon-60x60

Ok so quick spoiler here: there is no QGIS 3.0 ready yet, nor will there be a QGIS 3.0 for some time. This article provides a bit more detail on the plans for QGIS 3.0. A few weeks ago I wrote about some of the considerations for the 3.0 release, so you may want to read that first before continuing with this article as I do not cover the same ground here.

lot of consideration has gone into deciding what the approach will be for the development of QGIS 3.0. Unfortunately the first PSC vote regarding which proposal to follow was a split decision (4 for, 3 against, 1 abstention and 1 suggestion for an alternative in the discussion). During our PSC meeting this week we re-tabled the topic and eventually agreed on Jürgen Fischer’s proposal (Jürgen is a QGIS PSC Member and the QGIS Release Manager) by a much more unanimous margin of 8 for, 1 neutral and 1 absent. Jürgen’s proposal is largely similar to the Proposal 2 described in my previous posting. I want to make some special notes here about our discussion and subsequent decision which will hopefully help to clarify the thinking behind our decision for other interested observers.  First let me lay out Jürgen’s plan in his own words:

My preferred approach would still be:

  • Do a Qt5/PyQt5/Python3 branch in parallel, actually work on it until it’s ready, make it master and release it as 3.0
  • Meantime keep working on master (2.x) and keep releasing them every 4 months as usual

Everyone can work on the branch (s)he wants (or is hired to), but needs to consider if (s)he want to do it (or spend funds on):

  • only for 2.x: knowing that it will be released soon; but might become unusable because platforms drop support for stuff it depends on sooner or later
  • only for 3.x: not knowing when that will ever release or
  • for both: knowing that work needs to be done twice.
  • People adding features to the master branch will be responsible to ensure that their work gets merged to 3.0 branch.

As PSC we should maintain the environment for people to do something for QGIS – but we cannot tell them to – so we don’t have resources we can actually plan with and that means we can either release something when the big thing is ready or what we have in fixed intervals.” – Jürgen Fischer

What follows are some further details and clarifications to our preferred approach:

Why do parallel development?

Parallel development of 3.0 maintaining our master branch with 2.x code in it has advantages and disadvantages. First the advantages:

  • If we encounter major technical difficulties / release blockers in the 3.0 branch, it will not impact on our normal 3 monthly release cycle.
  • Our binary build systems (Linux, Windows and OSX binaries) will be unaffected until 3.0 is ready.
  • It is very likely that building 3.0 binaries on different platforms is going to have difficulties for each platform. For example OSGEO4W has no Python3 and Qt5 packages yet. Someone needs to see to the creation of the required package as a separate exercise from the actuals development of a version of QGIS that will take advantage of these updated libraries. We don’t yet know what problems may be in countered in preparing these.
  • “Don’t break what already works”: we have a working and relatively stable master branch and we don’t want to do a ‘cowboy stunt’ and break it. We prefer to wait until the 3.0 branch is mature, has passing tests and is known to work well before merging it into master and treating it as our ‘best we currently have’ master branch.

Of course nothing in life is completely easy, there are also some disadvantages:

  • Some developers may feel that running two mainstream branches is dilution of effort. To counter this, our public recommendation is that after 2.16 comes out, all QGIS contributors are strongly encouraged to provide their patches against the 3.0 branch. Any features applied to the master branch is not guaranteed to be part of the 3.0 release.
  • Regular merging of master to the 3.0 branch may prove more and more difficult over time as the two branches diverge more. Again we will strongly encourage that developers submitting new features after the 2.16 release do so against the 3.0 branch.
  • 3.0 branch won’t have auto build system for nightly binaries in the beginning. Since we expect that the initial branch of 3.0 will break these anyway, Having a separate branch is actually an advantage here as it will give binary packages some time to get their build systems up to speed.

To clarify things for developers wondering where to commit their work: we discourage people from writing new features in master after 2.16 is released and rather ask them to make their changes in the 3.0 branch. Only those who really need to see their features in the next 2.18 release would have to dual commit.

Isn’t it better to work on 3.0 in the master branch?

Some queries have been raised about whether it would be better to rather work on 3.0 in the ‘master branch’ and relegate the 2.x code base to a side branch (instead of our intended approach which is to keep master tracking 2.x until 3.0 is ready and then merge it to master). We feel that keeping master tracking the 2.x code base is more conservative – it will not break existing packaging / build systems and if there is any major hitch in 3.0 development the release process will continue unabated based on the 2.x code set. While 3.0 is under development, package builders will have time to figure out the packaging process while still keeping the regular nightly builds against 2.x running. The implication of this is that 2.18 may contain only bug fixes which were applied to the 2.x branch and no significant new features.

The schedule will not be fixed

One thing that we want to make really clear (and was a key point in our many discussions) is that there will be no fixed release date for QGIS version 3.0. There are several reasons for this:

  • As a steering committee, we can only set the QGIS ship pointing in a given direction, our power to actually make work happen is extremely limited. This is because we are a community made up largely of volunteer developers or developers working on a commission basis for third party clients. We have no say in how these contributors spend their time.
  • We do not yet know which (if any) major technical issues will be encountered during the development of 3.0. Any such issues could very well delay the roll out of QGIS 3.0.

Instead our plan is to make the 2.16 release and then effectively move all developer effort to the 3.0 branch as best we can (through close liaison with our developer community).

To clarify things for those wondering when they will give 3.0 to their users: The actual release date for 3.0 its interterminate, but the general aim is still to try to encourage everyone to get it ready for 1 year from now. Remember that as an open source community we cannot directly ensure that project timelines are met since our developer force is largely volunteer based or work according to their own companies agendas.

Will 3.0 be a Long Term Release (LTR)?

It is our recommendation that we wait until 3.2 is ready before designating it an LTR – there are going to be large changes in the code base for 3.0 and we would rather stabilise things a bit before applying the LTR label to the release.

 

Looking forward to 3.0

Personally I am very much looking forward to the release of QGIS 3.0 – it represents another huge milestone in our project, it affords us a great opportunity to get rid of a lot of cruft out of our code base and API’s and it will arm us with a set of modern, new libraries that will see us through the next several years. Rock on QGIS 3.0!

timsutton

QGIS PSC Chairman


by Tim Sutton at February 10, 2016 07:38 AM

gvSIG Team

HydroloGIS joins the gvSIG Association

Valencia, Spain – Bolzano, Italy – February 10, 2016

HydroloGIS, the company behind the open source projects Geopaparazzi and JGrasstools, has officially joined the gvSIG Association.

What this small Italian based company brings to the Association, is the expertise of their environmental engineers in the fields of hydro-geomorphological analyses and risk mapping, as well as water management, processing of LiDAR data and digital field mapping. The reason their experts were keen to join the development model of the gvSIG Association was mainly the fact that it is based on knowledge sharing, solidarity and cooperation, three principles which reflect the way HydroloGIS was conceived from the outset and the way it has evolved over the past 11 years.

This new member adds a range of new tools related to hydrology, hydraulic and geomorphology to the already substantial product catalog created by the member companies DISID, Scolab, ICarto and Creativa:

  • gvSIG Desktop, the Open Source Geographic Information System
  • gvSIG Roads, a solution for road infrastructure management based on a free applications suite
  • gvSIG Online, a web platform dedicated to fast deployment of location aware websites
  • gvNIX, a tool for rapid web application development

“For HydroloGIS this is a win-win situation. We can now better concentrate on our core business of scientific environmental modeling and mobile application development. Together with the gvSIG Association we are able to offer our solutions at any level of the software stack, whether it’s web, desktop GIS or mobile. The Association’s strong commitment to open source, cooperation and solidarity reflects everything HydroloGIS believes in”, declared the founders of HydroloGIS.

Alvaro Anguix, general manager of the gvSIG Association, stated about the new member company: “We are satisfied with the incorporation of HydroloGIS in the gvSIG Association. On the one hand, we increase our know-how with experts in strategic sectors like water management, and our development ability, relying on developers on recognized geoprocessing and LiDAR tools like JGrasstools, and GIS for mobile devices, like Geopaparazzi. On the other hand, the incorporation of a new company, in this case at a European level, is a further step toward the consolidation of a business model based on solidarity, collaboration and shared knowledge.”

About the gvSIG Association

The gvSIG Association is an open international non-profit organization. Its members, all of which are SME’s and organizations internationally renowned for their expertise on geomatics, are involved in the development of the gvSIG project and the diffusion of the FOSS4G (Free and Open Source Software for Geospatial). At present the gvSIG Association consists of one of the biggest network of experts in free geomatic software world-wide. The gvSIG Association offers services at the highest professional standard, as their numerous references will testify. The open source philosophy of the gvSIG Association is implemented by activating a complete knowledge transfer to its clients, supplying them with binaries, source code, documentation as well as a comprehensive training programme of the services provided. More at www.gvsig.org.

About HydroloGIS

HydroloGIS is an Environmental Engineering Company whose aim it is to correlate IT and engineering through the development and the application of environmental models in support of the engineering design. The environmental models for the evaluation of the variables necessary for the engineering design are developed in co-operation with the Department of Environmental and Civil Engineering of the University of Trento. In addition HydroloGIS actively co-operates in research projects with the University of Bolzano. More at www.hydrologis.com.

Contacts:
Alvaro Anguix
gvSIG Association
info@gvsig.org

Silvia Franceschi
HydroloGIS
info@hydrologis.com


Filed under: Business, english, gvSIG Association

by Alvaro at February 10, 2016 06:43 AM

Andrea Antonello

HydroloGIS joins the gvSIG Association

Today HydroloGIS turns 11.

11 years of Open Source software philosophy and development. 11 years of knowledge sharing and solidarity.

Today HydroloGIS​ joins the GvSIG​ Association, an international non-profit organization and network of SME’s involved in the development of the gvSIG project and the diffusion of the FOSS4G.

Also the gvSIG Association turns 11 this year, so we not only share our business model based on solidarity, collaboration and shared knowledge.

This is an important step for us. Please read more about it here: Joining gvSIG



by andrea antonello (noreply@blogger.com) at February 10, 2016 06:05 AM

February 09, 2016

Narcélio de Sá

Mapeando o Zika vírus.

A Organização Mundial de Saúde estabeleceu um comitê de emergência em resposta à propagação explosiva do Zika vírus nas Américas. O vírus já afetou pessoas em 23 países das Américas (esse número pode ter aumentado na data de publicação desse post). A disseminação do zika vírus e sua provável ligação com casos de microcefalia tornaram-se uma emergência de saúde pública internacional, apesar de ainda não haver uma prova científica de que o zika seja a causa do aumento de casos de microcefalia.

A febre por Vírus Zika (ZIKAV) é uma doença viral aguda, transmitida principalmente por mosquitos, como Aedes aegypti.  O vírus da Zika provoca uma doença semelhante à dengue e não pode ser evitado pelo uso de drogas ou vacinas.

Evolução da doença no mundo:

O vírus Zika foi isolado pela primeira vez em primatas não humanos em Uganda, na floresta Zika em 1947, por esse motivo esta denominação. Entre 1951 a 2013, evidências sorológicas em humanos foram notificadas em países da África (Uganda, Tanzânia, Egito, República da África Central, Serra Leoa e Gabão), Ásia (Índia, Malásia, Filipinas, Tailândia, Vietnã e Indonésia) e Oceania (Micronésia e Polinésia Francesa).

Nas Américas, o Zika Vírus somente foi identificado na Ilha de Páscoa, território do Chile no oceano Pacífico, 3.500 km do continente no início de 2014.

O Zika Vírus é considerado endêmico no Leste e Oeste do continente Africano. Evidências sorológicas em humanos sugerem que a partir do ano de 1966 o vírus tenha-se disseminado para o continente asiático.

Atualmente há registro de circulação esporádica na África (Nigéria, Tanzânia, Egito, África Central, Serra Leoa, Gabão, Senegal, Costa do Marfim, Camarões, Etiópia, Quênia, Somália e Burkina Faso) e Ásia (Malásia, Índia, Paquistão, Filipinas, Tailândia, Vietnã, Camboja, Índia, Indonésia) e Oceania (Micronésia, Polinésia Francesa, Nova Caledônia/França e Ilhas Cook).

Casos importados de Zika vírus foram descritos no Canadá, Alemanha, Itália, Japão, Estados Unidos e Austrália (12) Adicionar Ilha de Páscoa.

A propagação do Zika vírus pelo mundoA propagação do Zika vírus pelo mundo

Mapeando o Zika vírus:

Centers for Disease Control and Preventio – CDC (Centros para Controle e Prevenção de Doenças) é uma agência federal que desenvolve e apoia atividades de promoção da saúde, prevenção e preparação nos Estados Unidos.  Na sua página é possível acessar um mapa estático dos países com transmissão ativa do vírus Zika. É possível encontrar também um mapeamento detalhado dos casos de Zika nos Estados Unidos

Captura de tela de 2016-02-09 00-38-15

Já o site HealthMap, que fornece mapa interativo de diversas doenças infecciosas, lançou agora um mapa do vírus Zika. O HealthMap não é um mapa de casos confirmados do vírus Zika, mas traça notícias de diferentes fontes de dados, incluindo “agregadores on-line de notícias, relatos de testemunhas e relatórios oficiais validados”. A ideia é proporcionar uma visão geral do atual surto de vírus Zika.

Captura de tela de 2016-02-09 00-48-51

No Brasil a prefeitura de Porto Alegre desenvolveu um projeto chamado “ Onde está o Aedes? ” que tem como objetivo mapear os pontos de monitoramento de mosquitos da dengue. A página além de ser muito informativa apresenta um Mapa semanal de infestação do mosquito Aedes aegypti.

Captura de tela de 2016-02-09 00-50-12

Fontes:

www.washingtonpost.com
www.cdc.gov
www.healthmap.org
www.who.int
www.googlemapsmania.blogspot.com.br

The post Mapeando o Zika vírus. appeared first on Narcélio de Sá.

by Narcélio de Sá at February 09, 2016 04:08 AM

February 08, 2016

gvSIG Team

Libro: Laboratorio di gvSIG applicato all’Urbanistica

gvsig_urban

Pubblichiamo il libro “Laboratorio di gvSIG applicato all’Urbanistica“, tradotto in italiano da Alessandra Massenti, basato sui vari laboratori che abbiamo realizzato durante le Giornate gvSIG dell’anno appena trascorso.
L’obiettivo del workshop è quello di mostrare attraverso una serie di esercizi applicativi
l’utilità di gvSIG nel settore dell’Urbanistica.
Il workshop non ha la pretesa di affrontare in maniera approfondita l’applicazione dei Sistemi Informativi Geografici nel settore urbanistico, tuttavia può servire come
introduzione per suscitare interesse di urbanisti e pianificatori verso gvSIG.
Download:

 


Filed under: gvSIG Desktop, Italian, training Tagged: urbanistica

by Alvaro at February 08, 2016 06:02 PM

gvSIG Team

Georreferenciación de cartografía histórica con gvSIG (vídeo)

El pasado viernes y como parte del Máster de Valoración, Catastro y Sistemas de Información Territorial de la Universidad Miguel Hernández de Elche se realizaron una serie de webinars, entre los que destacamos el denominado “Georreferenciación de cartografía histórica con gvSIG”.

Os dejamos con el enlace a la grabación del webinar:

Una oportunidad para asistir a esta clase magistral de uso de geomática libre aplicada a la cartografía histórica.


Filed under: events, gvSIG Desktop, spanish Tagged: cartografía histórica, georreferenciación, HGIS

by Alvaro at February 08, 2016 09:35 AM

February 07, 2016

OSGeo News

Invitation to NASA CitySmart Challenge - Solutions For Sustainable Cities

by jsanz at February 07, 2016 07:07 PM

OSGeo News

Geo for All Newsletter - Feb 2016 now published

by jsanz at February 07, 2016 07:00 PM

February 05, 2016

gvSIG Team

Político, promete TIC que te sale barato

Imaginemos al representante político de turno visitando un barrio y prometiendo a los vecinos que se va a construir un centro de salud para atender sus necesidades. Da igual que sea un centro de salud, un colegio, un polideportivo o la variante de una carretera. Desde el primer momento todos asumen de forma natural dos cosas: En primer lugar que para llevar adelante dicha promesa será necesario que haya un dinero, una licitación y una contratación; y en segundo lugar, seguro que nadie piensa que va a pasar por el solar y a la siguiente semana ya va a estar allí el centro de salud construido.

Es posible que el político del que estamos hablando tenga voluntad transformadora, que vea que hay cosas que no funcionan, que hay mucho por hacer para el bien de la Comunidad, pero claro hacer realidad las promesas llevan su tiempo. ¿Seguro? ¿Todo? Por supuesto que no, hay cosas que puedes prometer y en breve construir. Las TIC.

Político, piensa en cualquier solución que pueda resultar un aporte para tu ciudadanía. Sea el ámbito que sea, Judicial, Educativo, Sanitario, Industria, Agrícola, etc ¿Que esos cambios implican cambios legislativos que suponen impacto en los Sistemas de Información? Que más da, si todo el mundo sabe que esto de la informática es darle a una tecla. Total, como si la tecnología influyera en los procesos sociales, productivos, económicos o financieros en el Siglo XXI. Como si para dar salida a nuevas propuestas u ocurrencias no fueran necesarios procesos telemáticos y adaptar o modificar Sistemas de Información.

Ahora va a resultar que para hacer una promesa que tenga impacto TIC, va a ser necesario que se disponga de recursos económicos, y que estos tomen forma en un proceso de licitación y contratación. Además me querrás decir que cuando estén los contratos adjudicados, va a resultar que se va a necesitar un tiempo para construirse y estar en disposición de ser utilizados. Pero que se creen esto de las TIC, ¿Acaso pensaran que están hablando de procedimientos de ingeniería que llevan sus tiempos?

Y mira que está mal que estos de las TIC pongan pegas en que se ha de armar un expediente administrativo para el proceso de contratación. Seguro que son capaces de quejarse de que tienen que hablar con interventores y abogacías con nula especialización en el sector. Son capaces de decir que si desde que se inicia el procedimiento hasta que finaliza transcurre un año, en ese lapso de tiempo la tecnología ha avanzado de forma que la correspondencia entre el objeto del contrato y su implementación no es la óptima en ese momento.

A lo mejor el político quiere cambiarse el teléfono móvil cada seis meses porque se le queda obsoleto. ¿Pero la tecnología de los Sistemas de Información? Y bueno, el capricho de querer tener ya interlocutores jurídicos con especialización en el sector TIC, eso debe ser ya cosa de excéntricos.

Uf, y si esta es la situación, si esta es la visión del rol y los tiempos de los procesos tecnológicos que tienen los representantes políticos, si además hay que explicarles que estamos hablando de un Sector Estratégico y el papel del Software Libre como garante de Soberanía Tecnológica. Como se dice en Valencia: Ai mare, quant treball tenim per davant

@GabrielCarrionR


Filed under: opinion, spanish

by Gabi at February 05, 2016 11:56 AM

February 04, 2016

Marco Bernasocchi

Increasing the stability of processing algorithms

Processing just got a new testing framework to improve the long-term stability of this important plugin. And you can help to improve it, even if you are not a software developer! This is yet another piece in our never-stopping crusade to
See more ›

by Matthias Kuhn at February 04, 2016 06:41 PM

Ivan Minčík

GIS.lab Web - New Generation QGIS Web and Mobile Interface

Last year, GIS.lab team has decided to start a development of brand new version of our GIS web publishing interface known as GIS.lab Web. Our goal is to have a web application built on top of modern technologies, with very modern UI, optimized for mobile devices. Also, we want to build a hybrid Android application from the same code base, but with native UI interface. All of this standing on the shoulders of our favourite QGIS desktop and server software.

We have realized very soon, that if we would separate this project from the core GIS.lab system, we can produce generally usable QGIS web interface, usable with or without GIS.lab infrastructure. Maybe, even replace current version of QGIS Web Client.

This week, first alpha version of GIS.lab Web was born.

For a quick look, see the screenshots below,





GIS.lab Web



watch our short screencast,

GIS.lab Web


or try it yourself.

Thanks to all helping this happen. Looking forward for any feedback.

GIS.lab Web on GitHub - https://github.com/gislab-npo/gislab-web

by Ivan Minčík (noreply@blogger.com) at February 04, 2016 04:39 PM

Nathan Woodrow

Rendering web images as markers in QGIS

So here is an idea.  Say you have a point layer that has a link to a static image from a web cam. Lets say it is a traffic camera for this use case.

Selection_0272016-02-04 21_30_36-QGIS 0a64c16

We can use that feed to see the image in a browser. Cool. But what would be even cooler is if we could get the images into QGIS as markers without having to download each image each time for a update ourselves.

Turns out it’s pretty easy – could be easier no doubt but lets just go with this route for now.  For this you will need: a custom expression function, and data defined SVG path locations. (We have to use SVG markers because QGIS doesn’t have image markers just yet)

Lets write that custom expression function.  We need a SVG marker so lets set that for the layer and also edit the data defined path

svg.png

Hit the New file button and define a new function called show_camera. 

import requests
import base64

@qgsfunction(args='auto', group='Custom')
def show_camera(feed, feature, parent):
    svg = """
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg>
  <g>
    <image xlink:href="data:image/jpeg;base64,{0}" height="256" width="320" />
  </g>
</svg>
"""
    data = requests.get(feed, stream=True).content
    name = feed[-16:]
    b64response = base64.b64encode(data)
    newsvg = svg.format(b64response).replace('\n','')
    path = r"C:\temp\camera\{0}.svg".format(name)
    with open(path, 'w') as f:
        f.write(newsvg)
    return path.replace("\\", "/")

This will take the image feed, load it with the Python request library, base64 the image, stick the data in to a SVG, save the SVG to disk, and return the path to the new SVG.

We have to save to disk because QGIS can’t load SVGS from strings, although that would be a cool feature. I am also using base64 because a linked file SVG didn’t render in QGIS.

Once we have defined that we can use the function like so

show_camera( "url" )

looking at the output preview we have

'C:/temp/camera/MRMETRO-1216.jpg.svg'

Which looks right. Hit OK on the expression.

Before hitting Apply just make the size of the marker a little bigger as it will make the image to small to see, I used 35 for the demo. You should also pick a SVG marker from the list that is used as the default one if there is no valid path returned.

Hit Apply. Magic :)

qgis

The images are getting download and saved into C:\temp\camera for this demo but you could add some more magic around that.

Something to note is that each time you refresh the map you are making a bunch of web requests to get the new images. You could avoid this by tracking the image times and only grabbing new ones if a set time has elapsed.  I will leave that up the reader, however here is a link to a Gist with the code if you wish to fork it

Big hat tip to QGIS and its multi threaded rendering that still allows you to continue to work while it renders and downloads the images in the background.


Filed under: Open Source

by Nathan at February 04, 2016 12:13 PM

gvSIG Team

II gvSIG Chair Contest

 

Cartel gvSIG-catedra-II-ingles

The gvSIG Chair Contest is announced for the second year to reward works about free Geographic Information Systems, in university world as well as in learning one. 

The aim of these awards is to foment gvSIG use in particular and free geospatial technologies in general, as well as to encourage all gvSIG and free Geographic Information Systems users to share and give visibility to their work.

Awards are aimed at students or graduates in secondary school or professional training, university students or graduates and university teachers, and researchers from all the countries.

At the next link you can find more information about dates, type of works accepted, amount of prizes, etc. (in Spanish):

http://gvsig.edu.umh.es/ii-concurso-catedra-gvsig/bases-ii-concurso/

You can see the video of the International gvSIG Conference where the winners of the last edition were presented:

And the video of the project rewarded at the last edition:



Filed under: community, english, gvSIG Association, gvSIG Desktop, press office

by Mario at February 04, 2016 11:38 AM

February 03, 2016

OSGeo News

OSGeo Foundation turns 10!

by jsanz at February 03, 2016 04:01 PM

Narcélio de Sá

V Congresso Brasileiro de Educação Ambiental Aplicada e Gestão Territorial

O V Congresso Brasileiro de Educação Ambiental Aplicada e Gestão Territorial será sediado na Universidade Federal do Ceará, Departamento de Geografia, campus do Pici, em Fortaleza – Ceará. O evento objetiva promover debates e trocas de experiências acadêmicas a nível nacional, buscando contribuir com a difusão de ideias e trabalhos que buscam a construção de uma sociedade mais sustentável.

Local do evento:

Ver Mapa Ampliado

Trata-se de um momento singular no contexto nacional, com espaços destinados a discussão e intercâmbio de conhecimentos atrelados a temas relacionados com o evento que será constituído por um conjunto de palestras, minicursos e apresentação de trabalhos científicos por acadêmicos e técnicos, o que propiciará uma maior troca de conhecimentos entre os participantes do congresso.

Este evento envolve parcerias entre a Universidade Federal do Ceará – UFC (Programa de Pós-Graduação em Geografia – PPGe e Programa de Desenvolvimento e Meio Ambiente – PRODEMA), 15 universidades públicas brasileiras e ​uma estrangeira (Cuba), incluindo seus respectivos programas de graduação e pós-graduação, além de diferentes grupos de pesquisa.

Eixos Temáticos:

  • Eixo 1: Educação ambiental, sustentabilidade e gestão comunitária.
  • Eixo 2: Educação Patrimonial e cultura afrobrasileira e indígena.
  • Eixo 3: Ecopedagogia na educação formal e informal

  • Eixo 4: Sociobiodiversidade e biotecnologias alternativas.
  • Eixo 5: Bacias hidrográficas: planejamento e gestão ambiental.
  • Eixo 6: Planos diretores e políticas culturais e territoriais.

  • Eixo 7: Territórios, populações tradicionais e conflitos sociais.
  • Eixo 8: Geotecnologias aplicadas à gestão ambiental participativa.
  • Eixo 9: Cartografia temática aplicada em áreas de risco.

Para mais informações, acesse: http://congressoambiental.webnode.com/

The post V Congresso Brasileiro de Educação Ambiental Aplicada e Gestão Territorial appeared first on Narcélio de Sá.

by Narcélio de Sá at February 03, 2016 03:17 PM

February 02, 2016

gisky

Report of Geospatial@FOSDEM 2016


Last Sunday, during FOSDEM the second edition of the geospatial devroom was happening.
As said before we had a nice lineup with 15 presentations with topics ranging from established GIS tools, Open Streetmap, 3D visualisation and spatial databases.

Anyway, I did the first presentation on SAGA GIS, and I was happy to have some very nice slides prepared by other members of the SAGA community.
Next up was Hugo Mercier (Oslandia) who presented Tempus. Planning multimodal transportation is a very hard problem, and it was nice to see that you can actually get the sources of the whole project. Next up was Astrid Emde presenting Mapbender, an OSGeo project allowing one to create web SDI's easily.
The next talk by Zeeshan Ali, "Build a geo-aware OS" was one where I was looking forward to : the talk is not one you usually encounter during FOSS4G conferences, but an example of the crosspolination of technologies you get at FOSDEM. It shows how location can now be used in Gnome (and other projects building on FreeDesktop) using common API's.
Getting ready to add location using a raspberry zero

Next up we got a full room for the presentation of Margherita Di Leo and Anne Ghisla presenting the results of the Google Summer of code projects coached at OSGeo.
This is how we like our devroom: full!


Everything got even more crowded for the next talk by Tuukka Hastrup on open journey planning. As people kept trying to enter our room even though it was full, I decided to play doorkeeper and missed the actual talk. 


For those who don't get it "FULL", stop entering!
But based on the feedback and the slides, I'm really looking forward to the video of the talk.
Still in a crowded room Ilya Zverev gave a talk about mapping with OSM with a phone . Rather than mapping using satellite imagery, it makes more sense to map when you are actually in the field.


The next talks were all focused on 3D. Thomas Bremer talked about how one could implement a flight simulator in javascript. He focused on the different components that could build such a simulator. I hope to see a demo of this soon. The next talk was on the integration of Openlayers and Cesium. I missed the talk myself (one has to get lunch at one point), but I got some nice feedback. The last talk in our 3D theme was Vincent Mora on iTowns, showing impressive Lidar scans of large parts of Paris. Even though many of us are still struggling with 2D, a lot of data collection is now 3D and I think GIS systems still have to catch up.

The next block of four presentations were all on databases. Starting of with MySQL GIS. I was pleasantly suprised by the presentation. MySQL and Oracle got some bad press in some open source communities, but I believe the way they are working on MySQL is examplary: not only is MySQL catching up quickly with other (spatial) databases, this is largely done by improving the underlying boost geometry library, which can be leveraged by other projects. Oracle is currently sponsoring 2 developers on that project.
Also Rasdaman, a raster array database extension for PostgreSQL was presented. Even though their use cases may currently be 'far from the bed' of many developers, I like the fact that they are not only implementing a product, but also shaping the standards (OGC and ISO) on the way. 
The third presentation focused on the geographical capabilities of a completely different type of database: mongoDB. I see a lot of possibilities of this database for geodata which is not as structured as classic databases. Nice to see their performance is improving.
The last presentation in the on pivotal Greenplum database was sometimes hard to follow, but I will definitely check it out further: I was not aware of the database, but it is a parallel database based on Postgresql, meaning that postgis functionality can be used, but also the extensions for trajectory data which were the topic of the presentation.

Closing the devroom was a presentation on geocoding by Ervin Ruci, which is a topic where the performance of open solutions can still be improved a lot.


At the end of the day, the closing keynote of FOSDEM, which was given by the people of HOT OSM. A full Janson is always something special, and this is definitely true for a topic of a talk I'm so familiar with.


Closing Keynote about Humanitarian Openstreetmap

To conclude, I believe the devroom at FOSDEM was a great event, and I really think it has its special role compared to other events such as FOSS4G and State of the Map - the chance to meet other open source communities.

Videos of the day should be available soon, thanks to the incredible FOSDEM video team and Anne Ghisla and Thomas Gratier who helped with the camera/organisation.

by Johan Van de Wauw (noreply@blogger.com) at February 02, 2016 09:36 PM

gvSIG Team

II Concurso Cátedra gvSIG

Cartel-concurso-gvSIG-e1454354155281

Por segundo año se convoca el Concurso Cátedra gvSIG que premia trabajos realizados con Sistemas de Información Geográfica Libres, tanto en ámbitos universitarios como de enseñanza.

Estos premios tienen como objetivo fomentar el uso de gvSIG en particular y de las tecnologías geoespaciales libres en general, así como animar a todos los usuarios de gvSIG y Sistemas de Información Geográfica libres a que compartan y den visibilidad a sus trabajos.

Los premios están dirigidos a estudiantes o egresados de secundaria y formación profesional, estudiantes o egresados universitarios y profesores universitarios e investigadores de todos los países.

En el siguiente enlace podéis encontrar más información sobre plazos, tipos de trabajos aceptados, cuantía de los premios, criterios de valoración, etc:

http://gvsig.edu.umh.es/ii-concurso-catedra-gvsig/bases-ii-concurso/

Podéis consultar los ganadores de la edición anterior y acceder a los trabajos en:

http://blog.gvsig.org/2015/12/21/i-concurso-catedra-gvsig-ganadores/

Así como el vídeo de las Jornadas Internacionales gvSIG donde se dieron a conocer los ganadores:

Y el vídeo de presentación de la tesis premiada en la edición anterior:



Filed under: community, press office, spanish Tagged: Concurso, premios, Tesis, TFG

by Alvaro at February 02, 2016 05:06 PM

OSGeo News

Our huge thanks to Jeff McKenna

by jsanz at February 02, 2016 09:25 AM

OSGeo News

New OSGeo President and Updated Board of Directors

by jsanz at February 02, 2016 07:34 AM

February 01, 2016

OSGeo News

Floodhack helps mitigating Floods

by jsanz at February 01, 2016 09:17 PM

gvSIG Team

gvSIG Roads, gestión de carreteras con software libre: Vídeos de la aplicación y webinar disponible

Como ya hemos comentado en post prevíos, gvSIG Roads es un nuevo producto de la Asociación gvSIG para la gestión integral de carreteras.

Lo que hoy os mostramos son una serie de vídeos para que podáis conocer más en detalle la aplicación. Estos vídeos están explicados en un webinar recientemente realizado sobre gvSIG Roads.

Flujo de trabajo, gestión de incidencias…

Flujo de trabajo, gestión de incidencias e inventario

Creación de inventario

Control económico

Creación de incidencias en dispositivo móvil

Creación de inventario en dispositivo móvil

Creación de tramos con gvSIG Desktop

Modificación de tramos con gvSIG Desktop

El vídeo con la grabación del webinar con la explicación detallada de gvSIG Roads, más la contestación de las preguntas de los asistentes podéis encontrarlo en el siguiente enlace:

Nota: En la primera media hora del webinar hubo unos pequeños problemas técnicos con el audio, que fueron solventados posteriormente.

Si estás interesado en implantar gvSIG Roads 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.

Post relacionados:


Filed under: gvSIG Roads, spanish

by Alvaro at February 01, 2016 06:02 PM

OSGeo-fr

State Of The Map France 2016

Nous avons le plaisir à vous annoncer la tenue de l'édition 2016 du State Of The Map France, qui se déroulera du
vendredi 20 au dimanche 22 mai, à Clermont-Ferrand.

Les inscriptions sont ouvertes ici :
https://www.helloasso.com/associations/openstreetmap-france/evenements/s...

Ce sera, comme chaque année, une belle occasion de nombreuses rencontres autour d'OSM : l'occasion pour chacun de nous de mettre des visages sur des noms, l'occasion aussi de confronter les points de vues et les attentes, entre contributeurs et utilisateurs, amateurs et professionnels. Et, évidemment, l'occasion de passer un bon moment, car quoi qu'on dise, un State Of The Map, c'est aussi voire surtout un moment de convivialité.

Le déroulement suivra la trame désormais habituelle :
Ouverture en session plénière le vendredi matin, puis présentations en tous genres vendredi après-midi et samedi toute la journée. Le dimanche, discussions libres, ateliers auto-organisés et hackathon champêtre. Nous profiterons aussi de l'occasion pour tenir une Assemblée Générale de l'association OSM France le samedi en fin d'après-midi.

Le programme de la conférence est à co-construire. Si un sujet vous tient à cœur, si vous souhaitez intervenir, surtout faites le savoir.
Dans un autre registre, si votre entreprise souhaite sponsoriser l'évènement, les propositions sont aussi bienvenues.

Pour toutes vos suggestions et questions, une seule adresse :
sotm [at] openstreetmap [point] fr

Les premiers détails de l'organisation sont publiés ici :
http://openstreetmap.fr/sotmfr2016
Les suivants y seront aussi, surveillez cette page.

by delaye at February 01, 2016 05:01 PM

GIS for Thought

Mapping Google Location Data

A cool python script has been created that allows you to easily convert your google location (Takeout) data into a shapefile.

You can get your data from: Google Takeout
And you only need the “Location History – JSON format”

The conversion python script can be downloaded from: GitHub

The python script requires GDAL and its python bindings, but can be easily run if you installed QGIS using the OSGeo4W installer. From the advanced installer, under the Lib section.

instruct

Then using the OSGeo4W Shell.
shell

Run the command:

python "C:\FullPath_to_Python_Script\read_location_data.py" "C:\FullPath_to_Input_File\LocationHistory.json" "C:\output_path" output_file_name ESRI_Shapefile

Example:

python "C:\FilePath\Takeout\Location History\read_location_data.py" "C:\FilePath\Takeout\Location History\LocationHistory.json" "C:\FilePath\Takeout\Location History" output ESRI_Shapefile

Then just style it in QGIS as desired.
GoogleTakeOut

by Heikki Vesanto at February 01, 2016 12:00 PM

January 31, 2016

Cameron Shorter

OSGeo-Live metrics going public in next release

With the upcoming OSGeo-Live 9.5 release, we will make OpenHub metrics very visible, adding a "Metrics" tab from the main OSGeo-Live page, which links to our existing OSGeo-Live OpenHub summaries.

Most OSGeo-Live projects have very compelling metrics, demonstrating an established and active development community. However, there are a few projects where OpenHub metrics are dated, incorrectly suggesting a lack of project activity. As such, I encourage all projects to review their OpenHub metrics before the next OSGeo-Live release, and update where appropriate.

Start by looking here: http://live.osgeo.org/en/metrics.html

About OSGeo-Live

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

by Cameron Shorter (noreply@blogger.com) at January 31, 2016 03:37 AM

January 30, 2016

OSGeo-fr

FOSS4G-fr 2016, nous attendons vos propositions !

Le FOSS4G-fr 2016 est un événement dédié à la géomatique Open Source et aux données géographiques libres, organisé par l'association OSGeo-fr. Il aura lieu du 10 au 12 mai 2016 à l'ENSG (École Nationale des Sciences Géographiques) à Marne-la-Vallée, France.

Cet événement comprend deux jours de conférences précédés d'une journée de workshops. Il vous permettra de découvrir les dernières tendances et technologies du domaine, ainsi que certaines de leurs applications concrètes.

Cet événement s'adresse tant aux utilisateurs qu'aux développeurs d'outils géomatiques Open Source. Retrouvez plus d'informations sur le site de l'événement: http://foss4g.osgeo.fr.

Vous êtes expert sur un domaine lié aux SIG libres ? Vous avez utilisé les outils de l'OSGeo dans un contexte spécifique (projet d'envergure, données très volumineuses, client reconnu, projet innovant, etc.) ? Vous participez à un projet libre lié à l'OSGeo ? Alors n'hésitez pas à proposer une présentation !

Les participants au FOSS4G-fr 2016 souhaitant présenter leurs projets soumettre un résumé avant le 13 mars 2016 minuit (heure de Paris). Les résumés doivent être envoyés via le formulaire en ligne http://foss4g.osgeo.fr/soumission.html.

» Retrouvez la procédure complète sur le site dédié à l'événement.

by simo at January 30, 2016 03:59 PM

January 29, 2016

Gis-Lab

Вышел GDAL 1.11.4 и 2.0.2

Вышел коррекционный релиз библиотеки GDAL для версий двух веток (1.х и 2.х). Релиз исправляет ошибки, выявленные с момента выхода 1.11.3 и 2.0.1.

Исходники 1.11.4 брать тут:

http://download.osgeo.org/gdal/1.11.4/gdal-1.11.4.tar.xz
http://download.osgeo.org/gdal/1.11.4/gdal-1.11.4.tar.gz
http://download.osgeo.org/gdal/1.11.4/gdal1114.zip

Исходники 2.0.2 брать тут:

http://download.osgeo.org/gdal/2.0.2/gdal-2.0.2.tar.xz
http://download.osgeo.org/gdal/2.0.2/gdal-2.0.2.tar.gz
http://download.osgeo.org/gdal/2.0.2/gdal202.zip

Подробнее о релизах можно почитать по ссылкам (англ.):
http://trac.osgeo.org/gdal/wiki/Release/1.11.4-News
http://trac.osgeo.org/gdal/wiki/Release/2.0.2-News

Настоятельно рекомендуется перейти на вторую ветку, т.к. поддержка первой ветки может быть скоро прекращена.

by bishop at January 29, 2016 11:01 PM

Jackie Ng

Announcing: mapguide-rest 1.0 RC4

Here's the 4th (and I am most certain, the last) release candidate of mapguide-rest 1.0

Here's what's new in this release

CORS support

CORS support has been added, allowing for cross-domain AJAX requests to be made to mapguide-rest. This is opt-in and has to be enabled by un-commenting the MapGuide.Cors section in config.php

New Selection APIs

New APIs have been added to make it easier to work with selections

You can see these APIs in action with the updated kitchen sink sample application




Updated Swagger UI

The version of swagger UI and spec we use has been updated. Where possible JSON/XML content parameters have an associated model schema giving you an idea of how the content should be structured



Other Changes



Download

by Jackie Ng (noreply@blogger.com) at January 29, 2016 01:10 PM

gvSIG Team

Webinar “Georreferenciación de cartografía histórica con gvSIG”

El próximo viernes día 5 de febrero de 2016 se realizará el webinar “Georeferenciación de cartografía histórica con gvSIG”.

El webinar tendrá lugar a las 11:00-UTC (ver horario según localización), y será impartido por Manuel Madrid García, profesor del Máster en Valoración, Catastro y Sistemas de Información Territorial, de la Universidad Miguel Hernández de Elche.

La cartografía histórica tiene un indudable valor documental ya que los mapas antiguos son descripciones gráficas rigurosas de un determinado lugar o territorio en un momento concreto de la historia. Cuando además somos capaces de superponer un mapa antiguo sobre uno actual, el valor documental del primero es todavía mayor ya que somos capaces de visualizar la evolución del territorio a lo largo del tiempo. Dado que la mayoría de mapas antiguos están en soporte papel, para conseguir esta superposición es necesario digitalizarlos y dotarlos de coordenadas absolutas referidas a un sistema global, lo que se conoce como georreferenciación. En este seminario se mostrarán técnicas de georreferenciación de mapas antiguos utilizando el Sistema de Información Geográfica libre gvSIG.

Los participantes del webinar podrán realizar preguntas en directo y realizar comentarios mediante el hashtag #georrefgvsig.

Este seminario estará accesible en directo desde el canal de YouTube del servicio de innovación docente de la Universidad Miguel Hernández de Elche.


Filed under: community, events, gvSIG Desktop, spanish, training

by Mario at January 29, 2016 12:26 PM

gvSIG Team

How to export layers from gvSIG for loading them in Google Earth

From gvSIG we can export our vector layers (parcels, roads, rivers…) and load them in Google Earth. Layers that we create, as well as layers downloaded from the different public administrations websites, can be visualized in Google Earth, exporting them from gvSIG.

Google_Earth_1

To be able to load that information in Google Earth we must have it in KML format, that is the vector format supported by it, so we have to export our SHP file to a new layer.

For that, we have to load the layer in a View in gvSIG, and put it in active mode. Then we’ll go to ‘Layer’->’Export to…’ menu.

At the first window we’ll select the KML format as export format.

Then, at the next window we’ll be able to mark the “Show attributes in balloon” option, that would allow us to get the information from the attribute table when we click on an element in Google Earth. In case we have the view and the layer in gvSIG in a reference system different to the supported one in Google Earth, (geographic coordinates, WGS84 Datum, EPSG4326), it would allow us to select the option to export the layer in that reference system. At this way it would be visualized correctly in Google Earth.

At the next window we would indicate the output file, and at the end window we would indicate what elements we want to export (all the elements, only the selected ones at that moment on the layer or the elements that meet a requirement by a filter).

The KML file that has been created will be the file that we will be able to load in Google Earth. For that, once the application is open, we go to the File->Open menu. When we select the KML file from our computer it will zoom on the area where our cartography is.

If we had marked the option to show the information of the attributes, when we click on them a box will be opened with that information.

Google_Earth_2

If the layer is made up by a line, like a footpath, we would be able to fly along the path in an automatic way.

Here you can see a video about how to do it:

We hope you enjoy it!

 


Filed under: english, gvSIG Desktop Tagged: Google Earth

by Mario at January 29, 2016 10:03 AM

gvSIG Team

Cómo exportar capas de gvSIG para cargar en Google Earth

Desde gvSIG podemos exportar nuestras capas vectoriales (parcelas, carreteras, ríos…) y cargarlas en Google Earth. Tanto las capas que nosotros creamos como las que descargamos, ofrecidas por las distintas administraciones, pueden visualizarse en Google Earth exportándolas desde gvSIG.

Google_Earth_1

Para poder cargar dicha información en Google Earth deberemos tenerla en formato KML, que es el formato vectorial que soporta, por lo que deberemos exportar nuestra capa SHP a una nueva capa.

Para ello, deberemos cargar la capa deseada en una Vista en gvSIG, y poniéndola activa, iremos al menú Capa->Exportar a…

En la primera ventana del asistente, seleccionaremos el formato KML como formato de exportación.

Después, en la siguiente ventana podremos marcar la opción de “Mostrar atributos en globos”, que nos permitiría obtener la información de la tabla de atributos cuando pinchásemos sobre un elemento. También, en caso de que nuestra vista en gvSIG y la capa que estamos exportando no estén en el sistema de referencia de Google Earth (coordenadas geográficas, Datum WGS84, EPSG4326), nos ofrecerá la opción de que nos exporte nuestra capa en dicho sistema de referencia. De esa forma se visualizaría correctamente en Google Earth.

Google_Earth_4En la siguiente ventana indicaríamos el nombre del fichero de salida, y finalmente en la última ventana indicaríamos qué elementos queremos exportar (todos los elementos de la capa, solo los elementos que tuviésemos seleccionados en ese momento, o los que cumpliesen un determinado filtro).

El fichero KML creado será el que podemos cargar en Google Earth. Para ello, una vez abierta la aplicación, deberemos acceder al menú Archivo->Abrir. Al seleccionar el fichero KML de nuestro disco hará automáticamente un zoom a la zona en la que se encuentra la cartografía.

Si hemos marcado la opción de mostrar la información de los atributos, si pinchamos sobre ellos nos abrirá un cuadro con dicha información.

Google_Earth_2

Si la capa cargada está formada por una línea, como por ejemplo un sendero, podríamos hacer que nos realice un vuelo sobre dicho sendero, siguiendo la línea del mismo.

Aquí podéis ver un vídeo sobre cómo realizarlo:

¡Esperamos que os guste!


Filed under: gvSIG Desktop, spanish Tagged: Google Earth

by Mario at January 29, 2016 08:59 AM

Prodevelop

#DICE project: latest video available now online

Find out all about the #DICE project in our latest video available now online https://www.youtube.com/watch?v=GelbjpCka8E&feature=youtu.be&a=

DICE video

DICE is a new Horizon 2020 research and innovation action started in February 2015, funded under the ICT-09-2014 sub-call. DICE aims at defining a framework for quality-driven development of Big Data applications. DICE will offer a novel UML profile and tools that will help software designers reasoning about reliability, safety and efficiency of data-intensive applications. The DICE methodology will cover quality assessment, architecture enhancement, continuous testing and agile delivery, relying on principles of the emerging DevOps paradigm.

Please visit: http://www.dice-h2020.eu/

by cjoubert at January 29, 2016 07:24 AM