Welcome to Planet OSGeo

January 17, 2019

Hilbert Curve of order 4:


Hilbert Curve of order 6:
Code is in the JEQL script repo.

import jeql.std.function.HashFunction;

hilbertOrder = 6;
side = Val.toInt( Math.pow(2, hilbertOrder) );
count = side * side;

radius = 1;

t = select * from Generate.sequence( 0, count-2 );

t = select i, geom: Geom.buffer(hilbertEdge, 0.4)
let 
hilbertPt1 = HashFunction.hilbertPoint(hilbertOrder, i),
hilbertPt2 = HashFunction.hilbertPoint(hilbertOrder, i+1),
hilbertEdge = Geom.createLineFromPoints( hilbertPt1, hilbertPt2 )
from t;

t1 = select *,
styleFill: clr, styleStroke: clr, styleStrokeWidth: 1
let
clr = Color.toRGBfromHSV(Val.toDouble(i) / count, 1, 1)
from t;
Mem t1;

The function hilbertPoint uses the efficient algorithm from http://threadlocalmutex.com/.  Code is on Github.

by Dr JTS (noreply@blogger.com) at January 17, 2019 05:58 PM

January 16, 2019

Se você já usou ou está ambientado a utilizar o GeoServer, deve lembrar que ao realizar a instalação, no primeiro acesso, você utiliza o usuário admin (que é o administrador do sistema).

Porém, não é desse usuário que irei falar nesse post, e sim do usuário “root” que muitos desconhecem.

Devido a natureza altamente configurável, a segurança do GeoServer pode ocasionar que um administrador interrompa a autenticação normal, desabilitando todos os usuários, inclusive as contas administrativas.

Por esse motivo, o subsistema de segurança do GeoServer contém uma conta “root” que está sempre ativa, independentemente do estado da configuração de segurança. Assim, no estilo UNIX, essa conta fornece o status de “super usuário” e destina-se a fornecer um método de acesso alternativo para corrigir problemas de configuração. É importante ressaltar que seu nome não pode ser alterado e a senha da conta “root” é a senha mestra.

Por padrão, a senha mestra é gerada e armazenada em um arquivo denominado security/masterpw.info usando texto simples (não encriptado). Ao atualizar o diretório de dados de um GeoServer existente (versões 2.1.x e inferiores), o algoritmo tenta descobrir a senha de um usuário com a permissão ROLE_ADMINISTRATOR. Se tal senha for encontrada e o tamanho da mesma tiver no mínimo 8 caracteres, o GeoServer usa essa senha como senha mestra.

Desta forma, o arquivo security/masterpw.info é um risco de segurança. O administrador deve ler este arquivo, verificar a senha mestra registrando-se no GeoServer como usuário “root” e depois disso este arquivo deve ser removido.

Por padrão, o login na interface administrativa e nas APIs REST usando a senha mestra está desativado. Para ativá-lo, você precisará alterar manualmente o Master Password Provider no arquivo config.xml, (geralmente localizado em security/masterpw/default/config.xml), adicionando a seguinte instrução:

<loginenabled>true</loginenabled>

Fonte: GeoServer Documentation

by Fernando Quadro at January 16, 2019 12:31 PM

January 15, 2019

Nel 2018 ho fatto una scelta piuttosto originale per guidare le mie letture: ho recuperato a casa dei miei genitori un pacco di libri rimasti impilati negli ultimi anni, generalmente arrivati in regalo, che per qualche motivo non mi ero mai portato via. Libri che non avevo letto, ecco. Libri che avevo dimenticato di leggere. Uno magari potrebbe decidere di leggere solo una certa autrice per tutto l’anno, solo libri pubblicati nel 1965, o qualche criterio del genere.

Ho finito la pila di libri non letti e poi mi sono tuffato dentro 4 3 2 1 come una lontra nel fiume.

Daniele De Silva, Non avevo capito niente

Questo non era rimasto impilato ma mi ha dato l’idea di una annata a tema. Un po’ sconnesso nell’incedere ma è stata una bella lettura, forse troppo veloce.

Annamaria Fassio, I giorni del Minotauro

Un giallo piemontese edito da Frilli. Ben architettato e ambientato.

Chinua Achebe, Non più tranquilli

Se con Le cose crollano eravamo di fronte alla tragedia di una società antica, di un suo protagonista inizialmente invincibile, il salto di due generazioni ci porta in un tempo dell’Africa quasi contemporaneo, eppure ancora legato a quella società antica, ai suoi legami indissolubili da cui è difficile sciogliersi anche per chi è apparentemente molto brillante.

Antonio Pennacchi, Canale Mussolini

A me Canale Mussolini non è piaciuto. Ho faticato per leggerlo. Ho sperato a lungo che abbandonasse la prosa dal fare omerico via via che la storia si dipanava, ripetendosi sempre uguale, e invece niente. Ci ho sperato un po’ perché varie persone erano rimaste entusiaste. Di sicuro è scritto per conquistare il lettore. Di sicuro non avevo mai letto una giustificazione così lunga del fascismo, così assolutoria per chi ne è stato protagonista al minuto e così, diciamo, controversa nella figura del narratore. È difficile sospendere il giudizio mentre si legge questa epopea familiare fatta di personaggi tragici, immobili.

Come dice, scusi? Canale Mussolini avrebbe vinto il Premio Strega e io non capisco un’acca della letteratura italiana contemporanea? Ma io sto unicamente raccontando il libro come l’ho trovato io, che guarda caso poi risulta scritto da un prete, e sempre quest’anno mi son trovato con un altro illustre premiato ancor più penoso, e in fin dei conti se per far rinascere l’epica italiana dobbiamo sorbirci un revisionismo palloso e ripetitivo, allora lasciamola nella tomba. Questa è la mia versione dei fatti, poi vedete voi e andate in malora.

Enrico Giannichedda, Quasi giallo

Non conosco molti archeologi che scrivono gialli (ad eccezione, forse, di Fred Vargas che non è proprio un’archeologa). Quindi non sono preoccupato di dire che questo quasi giallo non mi è piaciuto moltissimo. Forse perché le parti archeologiche, che abbondano e quasi debordano, mi sono note in buon dettaglio sia per studio sia per averle sentite proprio dalla voce di Enrico Giannichedda, e in questa cornice sembrano paradossalmente meno interessanti. Forse perché le parti gialle sono abbastanza solidamente nel solco del genere, senza però essere veramente nel solco giallo della copertina, magari più noir o 10YR 2/1. Altri che hanno letto il libro non sono rimasti soddisfatti dal finale, che però tutto sommato a me piace.

Michele Serra, Ognuno potrebbe

Michele Serra è un membro di quella categoria di persone che svolgono il meschino dovere di partorire ogni giorno un pensierino da scolaro delle elementari per la pubblica fruizione. La forma libresca non migliora l’esito e questa storia di un precario, scritta da uno che il precario non sa nemmeno recitarlo sotto forma di macchietta, non piace proprio.

Timur Vermes, Lui è tornato

Tanto inquietante (oggi ancora più di quando è stato scritto, solo nel 2011) quanto scopppiettante, questo è il libro che più mi è piaciuto leggere nel 2018, carico di continui rilanci che solo un buonsenso ormai intorpidito può considerare assurdi. Non ho visto il film che ne è stato tratto, in cui il protagonista non è Hitler bensì Mussolini, ma ne ho parlato con alcuni che lo hanno visto: il discorso è andato a parare sul “messaggio” che l’autore trasmette. Io penso che sia un messaggio molto implicito, che l’autore abbia saputo mostrare in modo eccellente come funzionano, come possono funzionare certi meccanismi psicologici e sociali che hanno conseguenze rapidamente irreparabili, senza bisogno di manifestare una “ovvia” valutazione negativa che avrebbe reso molto meno incisivo il suo autentico messaggio. In ogni caso, lui è tornato già parecchie volte negli ultimi anni e sembra che non siano state vendute abbastanza copie di questo libro.

Edoardo Nesi, Storia della mia gente

Chi abbia dato un premio a questo libro, dovrebbe almeno giustificare il vistoso errore grammaticale del titolo, poiché questa è una storia individuale e solipsistica, vissuta e narrata alla prima persona singolare, da parte di un autore che, del suo passato rimpianto da rampollo fallito di famiglia operosa, ricorda i nomi propri dei macchinari (femminili, ovviamente) ma non quelli degli operai. Uno che dedica varie pagine al Martini nell’ambito del tracollo economico della piccola media impresa manifatturiera italiana. Uno che è felice di scendere in piazza a manifestare perché lo fa stare bene.

Il motivo del blasone è presto detto, essendo l’autore stato precedentemente inserito nella shortlist ha deciso di titillare il premio stesso con continui rimandi ad esso, rendendolo (immaginiamo a propria insaputa) co-protagonista di questa farsa che sa rendersi lucida solo in forma onirica – rivelandosi anche genuinamente impregnata di razzismo.

Paul Auster, 4 3 2 1

Questo libro, questi libri, sono anzitutto una smisurata forma di devozione, una lunghissima dichiarazione d’amore verso la scrittura e la letteratura, verso New York e Parigi e forse anche verso l’essere ebrei negli Stati Uniti. Non per caso la prima parte mi ha ricordato fortissimamente Middlesex, così come il rimando continuo tra storia personale e storia collettiva, non un semplice sfondo ma un palcoscenico.

Il volume è imponente e ha richiesto una certa disciplina nella lettura, evitando tassativamente di leggere più di un capitolo al giorno per non andare in confusione, ma la trama è certo uno degli elementi meno portanti del capolavoro, come prevedibile. Trama che è composta anche di frammenti, mattoni autobiografici composti in modi sempre diversi.

Ci sono capoversi lunghissimi che vorresti non finissero mai. Ci sono liste, ma che liste, di libri, di film, di poesie, di musica. C’è tantissimo sesso, muoiono molte persone e sono sempre le stesse persone i personaggi che vivono 4, 3, 2 vite leggermente o completamente diverse dall’una che tiene il filo.

Si ride, si gode e si soffre moltissimo con questo libro.

Paolo Lazzarin, Patagonia

Questo che mi ha regalato Elisa il 26 dicembre è un delizioso resoconto fotografico di viaggio. La Patagonia, al di là delle frasi da guida turistica, è difficile da spiegare, e la vastità degli spazi soverchia la vista, la mente. Questo viaggio si è svolto principalmente lungo la catena andina, via terra in direzione sud e via mare in direzione nord. Il nostro viaggio, più spezzato e incoerente, era stato certamente meno lento ma comunque sfogliando le pagine ho ritrovato quelle montagne, quelle strade e quei guanachi — perché poi sono uno dei compagni di viaggio più memorabili. Grazie.


Nel 2019 ho deciso che leggerò solo libri scritti da autrici.

by Stefano Costa at January 15, 2019 07:41 PM

A new module of the free course about GIS for archaeologists is now available, and we are now halfway through the course. At this module we will see how we can use Geographic Information Systems to georeference historical maps, so we can use them for our projects and cross them with current cartography.

During the exercise, we will proceed to georeference a scanned image with historical information of a city using reference cartography.

If you have not done the previous exercises, we recommend you to start with the first module.

We remind you that the data to follow the course can be downloaded in a compressed .zip file from this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

Module 4. Managing historical maps: Georeferencing images

Previous modules:

Module 1: Preparation of an archaeological project

Module 2: Digitalizing prospection areas

Module 3: Analysis of prospection results: Vector geoprocessing

by Mario at January 15, 2019 01:42 PM

Os traemos un nuevo módulo con el que llegamos al ecuador del curso gratuito de SIG aplicados a Arqueología. En este tema veremos como podemos utilizar los Sistemas de Información Geográfica para georreferenciar mapas antiguos, pudiendo así utilizarlos para nuestros proyectos y cruzarlos con cartografía actual.

Durante el ejercicio, a partir de una imagen escaneada con información histórica de una ciudad, procederemos a georreferenciarla utilizando cartografía de referencia.

Si aún no has realizado los ejercicios anteriores, te recomendamos que empieces por el primer módulo.

Os recordamos que los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip en este enlace.

Para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, siempre podéis utilizar la lista de usuarios de gvSIG.

Tema 4. Gestionando mapas antiguos: georreferenciación de imágenes

Temas anteriores

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

Tema 2: Digitalizar zonas de prospecciones

Tema 3: Análisis de resultados de prospecciones: Geoprocesos vectoriales

 

by Alvaro at January 15, 2019 01:42 PM

Todo e qualquer trabalho deve ter um limite espacial, e não é diferente para os estudos ambientais.

É comum utilizarmos como referência os limites das bacias hidrográficas para determinar nossas áreas de estudo. Porém, como realizamos esse procedimento dentro do QGIS 3.4?

Confira nossa postagem e veja diferentes formas de desenhar sua área de estudo.

Desenho livre no QGIS

Um dos caminhos é desenhar manualmente os limites da sua bacia hidrográfica utilizando um modelo digital de terreno (MDT) e suas curvas de nível.

Para realizar esse procedimento, iremos baixar um MDT da JAXA (Agência Espacial Japonesa), a qual disponibiliza gratuitamente, mediante cadastro, esses dados para o mundo inteiro com resolução de 30 metros (1 arco segundo).

O registro é realizado fornecendo dados simples, como nome, instituição, nacionalidade, propósito e e-mail. Clique aqui para realizá-lo. Logo após o registro, você receberá um e-mail para confirmar sua conta e em seguida, outro com o ID e senha de acesso.

Ao acessar o banco de dados da JAXA, você encontrará um mapa índice, no qual você deverá selecionar o local da sua área de interesse. Em seguida, uma nova janela irá abrir para que você dê mais um zoom na sua área de interesse. Por fim, após essa ultima seleção, você conseguirá fazer o download do MDT.

Mapa índice apresentado no site da JAXA para download do modelo digital do terreno.Mapa índice apresentado no site da JAXA para download do modelo digital do terreno.

Após realizar o download o seu MDT, adicione ele ao QGIS utilizando o gerenciador de fonte de dados (“Open Data Source Manager”), especificamente na guia Raster. Ou ainda, clicando em Camada (Layer), adicionar camada (Add Layer) e adicionar camada raster (Add Raster Layer).

Como o MDT baixado abrange uma área muito extensa e para evitar processamento desnecessário de curvas de nível, iremos recortar ele usando a ferramenta “Clip raster by extent”.

Essa ferramenta esta disponível pelo GDAL, dentro de Processing Tools (Processing > Toolbox), ou pelo atalho Ctrl + Alt + T.

Nesta ferramenta, você irá determinar qual é o arquivo raster a ser recortado (1), onde ele será recordado (2) e onde o resultado será salvo (3). No nosso caso, iremos demarcar um retângulo em uma bacia hidrográfica qualquer, mas você pode abranger sua área de interesse e acrescentar alguns quilômetros a este recorte.

Ferramenta para recortar arquivos matriciais no QGIS.Ferramenta para recortar arquivos matriciais no QGIS.

Com um MDT menor, podemos executar a ferramenta “Contour” para extrairmos as curvas de nível do nosso raster. Esta ferramenta também encontra-se no Processing Toolbox e ao abrir ela, você terá que fornecer dados como o MDT (Input Layer), intervalo entre as curvas de nível (Interval between contour lines) e onde as curvas de nível serão salvas.

Ferramenta para criação de curvas de nível no QGIS.

Lembrando que este procedimento pode ser realizado sem as curvas de nível, porém, elas auxiliam bastante na delimitação de bacias hidrográficas, pois os divisores de águas são sempre perpendiculares às linhas das curvas de nível.

Desta forma, verifique a localização do seu empreendimento (ou área de interesse) e lance ele no seu mapa (ou abra o shapefile de localização dele) e em seguida, marque um ponto a jusante dele (de preferência, usando shapefile da rede hidrográfica local).

A partir desse ponto a jusante, iremos desenhar nossa área de estudo.

Para criar um novo shapefile (e desenhar nossa área de estudo), iremos clicar em Camadas (Layer), Criar Camada (Create Layer) e Nova Camada Shapefile (New Shapefile Layer). Na janela que será aberta, você deverá fornecer informações como o nome do arquivo, geometria (neste caso, deve ser polígono), sistema de coordenadas e os campos da tabela de atributos.

Criação de um novo shapefile no QGIS 3.4.Criação de um novo shapefile no QGIS 3.4.

Agora, para realizar o desenho, você deve clicar no ícone com um lápis amarelo enquanto o shapefile criado esteja selecionado. Ao realizar esse procedimento, você irá ligar o modo de edição.

Logo ao lado deste botão (lápis amarelo), há um ícone para criação de novos polígonos, clique nele para começar a desenhar sobre o MDT e as curvas de nível.

Existem várias formas de começar a delimitar sua bacia hidrográfica (neste caso, nossa área de estudo). É possível começar marcando os topos (partes mais altas) no MDT e a partir do ponto a jusante, iremos ligar esses pontos com linhas perpendiculares às das curvas de nível. O vídeo a seguir demonstra esse procedimento.

Como delimitar uma bacia hidrográfica manualmente.

Há outros vídeos, como este aqui, porém, são mais extensos (mas em português).

Após finalizar a delimitação da sua bacia hidrográfica, clique com o botão direito e o QGIS irá criar um novo polígono. Não se esqueça de clicar no disquete para salvar as modificações realizadas no seu shapefile.

O resultado deste procedimento é apresentado na figura a seguir para o MDT que baixamos do site da JAXA.

Área de estudo delimitada usando MDT e curvas de nível.Área de estudo delimitada usando MDT e curvas de nível.

Desta forma, você pode criar inúmeras áreas de estudos, seja contornando os divisores de águas a partir de um MDT ou contornando a área industrial por meio de uma imagem aérea.

Usando limites já definidos de BH

Você pode baixar os limites de bacias hidrográficas de fontes oficiais como IMA (SC) e EPAGRI. Após realizar o download destes arquivos, basta copiar e colar a sua bacia hidrográfica de interesse para delimitar sua área de estudo.

Esse procedimento é realizado criando-se um novo arquivo vetorial (como apresentado acima). Liga-se o modo edição para o arquivo contendo as bacias hidrográficas já delimitadas, seleciona-se o polígono da bacia hidrográfica de interesse e copia-se ela.

Agora, vá até o shapefile criado (em branco) e cole o polígono recém copiado.

Existe ainda uma terceira forma de delimitar bacias hidrográficas de forma automática, porém, deixaremos essa opção para outras postagem. Caso tenha ficado com alguma dúvida, deixe ela nos comentários que estaremos respondendo assim que possível.

by Fernando BS at January 15, 2019 06:00 AM

January 14, 2019

Promoção: De volta às Aulas com a GEOCURSOS

A Geocursos lançou uma nova promoção que vai sortear uma bolsa de estudos de 100% no dia 15 de fevereiro. O ganhador poderá escolher entre os cursos de:

OpenLayers 4 (EAD)
PostgreSQL (EAD)
DBA PostGIS (Ao vivo)

Veja como participar, lendo o regulamento logo abaixo.

REGULAMENTO DO SORTEIO

– SIGA o perfil da @geocursos no instagram
– CURTA a foto oficial da promoção (no instagram)
– MARQUE um amigo(a) nos comentário da publicação do instagram (não vale fake, empresas ou famosos)
– Pensamento POSITIVO

Participe quantas vezes quiser, quanto mais comentar, mais chances de ganhar, desde que usando nomes de amigos diferentes.

Informações sobre os cursos é só falar com a @geocursos no direct.

O Resultado será divulgado no dia 15/02 nos stories.

PS1: O perfil do ganhador deve estar público/aberto.
PS2: O ganhador tem até dia 18/02 para se manifestar via direct (@geocursos), caso contrário, realizaremos novo sorteio.
PS3: A inscrição no curso (OpenLayers ou PostgreSQL) se dará 3 dias após divulgação do resultado, e o ganhador terá 3 meses para realizar o curso.
PS4: O Curso DBA PostGIS, é online e ao vivo, e tem início no dia 16/03 (sábado).

Boa sorte!

by Fernando Quadro at January 14, 2019 10:54 AM

January 11, 2019

Never too late to look back. Inspired by the concise bullet-point-style of Tom Kralidis’ Cheers to 2018,  my personal highlights of living and working in the Open Source Geospatial and OSGeo(.nl|org)-world in 2018. I’ll post 2019 reso’s later. Not just personal projects, but also events from the OSGeo.nl Local Chapter in which I am involved since its beginnings.

January

February

  • As first-timer went to TheThingsNetwork Conference. What an amazing event! For some years already into Lora(WAN) and maintaining a TTN Gateway, I learned so much, also from the workshops there, that I wrote a separate blog-post about this event.
  • Started contracting (eventually until sept 30, 2018) at Dutch Kadaster to migrate the entire Smart Emission (SE) Platform to Kadaster infrastructure. Initially just migrating the SE Docker Images, normally two-weeks (to be honest, a day’s) work, BUT, as a (nice) surprise learned we had to move SE “To The Cloud”, that is to Azure Kubernetes (AKS), well that kept me and one Kadaster-colleague (learned a lot from you Gerwin!) busy till end of september at least  2-3 days a week!

March

  • As first-timer went to the OSGeo 2018 Code Sprint in Bonn. Mainly to work on GeoHealthCheck. (GHC). Another highlight! Not the least since I finally met the great Tom Kralidis! I had been working on GHC with Tom a couple of years but we somehow never met IRL. Spent most of week on a single PR (per-Resource scheduling) which required a re-architecture of GHC. But more importantly socializing with Tom and other folks there, well, Bonn, need I say more…Thanks organizers: Astrid Emde et al. for this great week!
  • In that same codesprint week I also attended several talks at the yearly FOSSGIS Conference  there. The FOSSGIS Conference is a major event in Europe as it involves all German-speaking (DACH) countries, plus their OpenStreetMap communities. Even with my high-school German language knowledge very well to follow.  As an exception to the rule I was grateful to be allowed to give a GeoHealthCheck presentation in English. Thanks to CCC, FOSSGIS always videotapes all talks, so you can watch some of my stuttering here.

April

  • With OSGeo.nl we and our community-members more and more try to organize small, hands-on events that are lightweight to organize. The NLExtract Hacking Day was a success! Thanks to organizer Frank Steggink (who also wrote the report), and a great space offered by WebMapper (Edward MacGillavry) in the Social Impact Factory Utrecht.

May

  • What happened in this month? Luckily GitHub tracks my activity. Many commits for the Smart Emission Kubernetes challenge. I see a week without commits in May: made a great hiking trip with friends in Ireland: the Kerry Way. Rain? Only one evening when walking to the pub (always live music there)!

June

  • More work on map5.nl, a subscription service for Dutch topographic, historical- and embellished hillshade and arial maps I started to host in 2015. Plus ongoing Smart Emission stuff.
  • Gradually, a heat-wave was overtaking The Netherlands. Climate change?

July

  • Heat-wave more and more building up.. But that did not stop the great OSGeo.nl organizing team to host the second FOSS4G-NL in Almere. July 10-11. Kudos to Erik Meerburg and team for two great days of workshops and conf!
  • At the FOSS4G-NL I had the honor to open the conference and  present the national Dutch GeoForum: geoforum.nl. We jointly (Kadaster, WebMapper, OSGeo.nl) extended the existing Dutch Kadaster PDOK Forum. As OSGeo.nl we did not want to launch yet another forum but to bundle forces.  Since that launch hundreds of folks registered.
  • Week after: off to FOSS4G-EU in Guimarães,Portugal. FOSS4G-EU is always something special. Folks gather from literally every country in Europe. From the Baltic States to Croatia. In a cosy atmosphere Jorge Gustavo Rocha and the LOC made this into a great event. Great talks during the day and every evening (and sometimes nights) in this small-town university city it was easy to find and gather with the OSGeo-folks on the main square Largo da Oliveira.

August

  • Started to seriously deploy the five AirSensEUR (ASE) stations. First at an RIVM air quality station in Breukelen next to the main A2 highway. With the great help of Jan Vonk of RIVM we managed to attach and digitally connect these stations at their premises. To have an idea, read my blog post on this effort. The ASE stations will gather raw, uncalibrated, Air Quality data there for two months and use the onsite RIVM measurements as reference for later calibration.

September

  • Again a small gap in my GitHub commit history: two weeks with my family (and our great Labrador Jamie) in rural France: Auvergne and Ardeche. I always love to set out GPS-hikes at home, hacking some of the French IGN topo-maps for personal use, and see how these turn out on the spot.

 

Oktober

  • Contract with Dutch Kadaster ended on sept 30. Just in time we migrated the entire Smart Emission stack to Azure Kubernetes (AKS). Well, IMHO Kubernetes is just awesome, especially after a few years of ad-hoc Docker deployment. Yes, a learning curve and devops-paradigm shift. Though for smaller projects in 2019 I am now combining Ansible with Docker (Compose).
  • After two months of gathering data for calibration, deployed the five AirSensEUR (ASE) stations at their target locations within The Netherlands. At each location challenges: an ASE needs 3 things: 1) to be firmly/rain-protected mounted physically, 2) 220V current and 3) WIFI. That combination turned out to be a challenge at each spot. But finally all five ASEs are now humming at their spots.

  • And with OSGeo.nl we had the second 2018 QGIS-Day at Ordina Utrecht. Thanks to the LOC: Jonas, Coen et al. Observation: all hands-on workshops were overcrowded!

November

December

  • Through my various projects thinking: All GeoData is Spatio-Temporal. Presented in Eindhoven at a Ruimteschepper event: LoRaWAN TheThingsNetwork makers event. Slides are here.  For one thing attempted to bridge the world of IoT with OGC SensorWeb via the SensorThings API in a PoC.

  • That’s almost it of 2018. A last brainwave on GeoHealthCheck usability made me to introduce interactive Plotly.js based interactive history Run-graphs. Together with and thanks to Tom Kralidis reviewing that was my final GitHub commit in 2018. Ok finalized on jan 3, 2019 but what a year!

 

 

 

by Just van den Broecke at January 11, 2019 02:04 AM

January 10, 2019

Prezado leitor,

Você tem interesse em aprender a trabalhar com banco de dados espacial, e possui conhecimento prévio em algum banco de dados? Então esta é a sua oportunidade!

A GEOCURSOS acaba de lançar a Turma 5 do Curso DBA PostGIS. Este curso online oferece uma visão completa que vai desde uma revisão sobre o PostgreSQL até tópicos avançados do PostGIS, apresentando como trabalhar em sua totalidade com esta poderosa extensão espacial do banco PostgreSQL.

Este curso é formado pelos nossos cursos PostGIS Básico (16 horas online) + PostGIS Avançado (20 horas online) e acontecerá entre os dias 16 de março e 19 de maio (aos sábados).

Se você fosse comprar os cursos separadamente sairia pelo valor de R$ 798,00. Porém o curso esta com uma super promoção, e está saindo por apenas R$ 549,00.

Para maiores informações e para ver a ementa completa do curso, acesse:

http://www.geocursos.com.br/dba-postgis

by Fernando Quadro at January 10, 2019 11:25 AM

We are honored to announce the international geospatial community that the registration for the geospatial event of the year FOSS4G 2019 is now open! And more…

We’ve made a promise to the community and we are delighted to stand before you today and say that we kept our word. We promised to do our best to make this global FOSS4G the most affordable of all times and it is! Joining the geospatial international community for one week packed with dynamic, valuable, timely events in a vibrant European capital city is more at hand than ever before. The EarlyBird for FOSS4G 2019 Bucharest is at the historical level of 330 EUR and it offers you everything you could ever need for such a tech gathering: access to plenary session (28-30 august), access to conference tracks (28- 30 august), access to 300+ talks, access to mobile app, ability to contact attendees, access to Ice Breaker Party (29 august), access to Gala Dinner (29 august), access to Pub Race Offers (28-30 august), access to Academic papers post event, access to presentations post event, conference kit, email support.

Furthermore, FOSS4G 2019 #historicalearlybird comes with a surprise not to be missed! For the first 100 participants, we have prepared 100 special FOSS4G 2019 T-shirts! This way, we – the Bucharest Local Organizing Committee – show our appreciation for your early, comforting support for the conference. If this you might have expected, our next surprise will definitely.. surprise you! We are deeply thankful for the opportunity to invite you in our home, Romania and we would like to offer you a small, captivating Romanian Passport. Curious? Be among the first 100 FOSS4G 2019 participants and you’ll receive a wonderful collection of interesting facts of Romania all packed in the Curious Passport.

No FOSS4G would be possible without the valuable input of sponsors. They are the conference’s backbone contributing to the values, principles and progress of our community. Support us in our work to organize FOSS4G2019 Bucharest as one of the most memorable FOSS4G events. The call for sponsors is now open. Please, take a look at our suggestions and find the one that best suits your needs and preferences.

Sponsoring is not yet possible but you want to actively contribute to the success of FOSS4G 2019 Bucharest? Become a volunteer! Besides valuable input in making FOSS4G 2019 happen, you will receive a free ticket to the conference (including the ice breaker and gala dinner). Interested?

Sponsorship is not for you, neither volunteering but you still want to help FOSS4G 2019, then Spread the Word!

Of course, FOSS4G 2019 is much much more than T-shirts and wonderful new places to visit. Program, Workshop and Academic committees are almost fully formed and ready for action! We are honored to say that the FOSS4G 2019 program will be shaped by remarkable people in the geospatial international community. Check out the Committee webpage to see who will review your FOSS4G 2019 contribution as Call for Papers and Workshop will open next week!

Follow us in the following months and find out all about the geospatial event of the year!

by Vasile Crăciunescu at January 10, 2019 08:42 AM

January 09, 2019

A new module of the free GIS course applied to Archeology is now available. With this module we are already starting to explore some of the advanced tools of Geographic Information Systems.

We will see how to apply vector geoprocesses to analyze the geographic information related to an archaeological site. We will also work with the information obtained from a GPS in a GPX file.

If you have not done the previous exercises, we recommend you to start with the first module.

We remind you that the data to follow the course can be downloaded in a compressed .zip file from this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

Module 3. Analysis of prospection results

Previous modules:

Module 1: Preparation of an archaeological project

Module 2: Digitalizing prospection areas. GIS applied to Archeology

 

 

by Mario at January 09, 2019 09:30 AM

Os traemos un nuevo módulo del curso gratuito de SIG aplicados a Arqueología. Con este tema ya empezamos a explorar algunas de las herramientas avanzadas de los Sistemas de Información Geográfica.

Veremos como aplicar geoprocesos vectoriales para analizar la información geográfica relacionada con un yacimiento. También se trabajará con la información obtenida con un GPS en un fichero GPX.

Si aún no has realizado los ejercicios anteriores, te recomendamos que empieces por el primer módulo.

Os recordamos que los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip en este enlace.

Para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, siempre podéis utilizar la lista de usuarios de gvSIG.

Tema 3. Análisis de resultados de prospecciones

Temas anteriores

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

Tema 2: Digitalizar zonas de prospecciones

 

by Alvaro at January 09, 2019 08:57 AM

January 08, 2019

We are pleased to announce the GRASS GIS 7.4.4 release

What’s new in a nutshell

The new update release GRASS GIS 7.4.4 is release with a few bugfixes and the addition of r.mapcalc.simple esp. for QGIS integration. An overview of the new features in the 7.4 release series is available at New Features in GRASS GIS 7.4.

As a stable release series, 7.4.x enjoys long-term support.

Binaries/Installer download:

Source code download:

More details:

See also our detailed announcement:

About GRASS GIS

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

The GRASS Development Team, January 2019

The post GRASS GIS 7.4.4 released: QGIS friendship release appeared first on GFOSS Blog | GRASS GIS and OSGeo News.

by neteler at January 08, 2019 11:58 AM

It was a long and winding road but we are very excited to announce the general availability of QField 1.0 Release Candidate 1.

Packed with loads of useful features like online and offline features digitizing, geometry and attributes editing, attribute search, powerful forms, theme switching, GPS support, camera integration and much more, QField is the powerful tool for those who need to edit on the go and would like to avoid standing in the swamp with a laptop or paper charts.

With a slick user interface, QField allows using QGIS projects on tablets and mobile devices. Thanks to the QGIS rendering engine, the map-results are identical and come with the full range of styling possibilities available on the desktop.

We ask you to help us test as much as possible this Release Candidate so that we can iron out as many bugs as possible before the final release of QField 1.0.

You can easily install QField using the playstore (http://qfield.org/get), find out more on the documentation site (http://qfield.org) and report problems to our issues tracking system (http://qfield.org/issues)

QField, like QGIS, is an open source project. Everyone is welcome to contribute to make the product even better – whether it is with financial support, enthusiastic programming, translation and documentation work or visionary ideas.

If you want to help us build a better QField or QGIS, or need any services related to the whole QGIS stack don’t hesitate to contact us.

by Marco Bernasocchi at January 08, 2019 06:59 AM

Quando estamos trabalhando em um projeto ambiental, utilizamos vários dados de diferentes compartimentos, seja do meio físico, biótico ou socioeconômico. E quando essa informação pode ser representada espacialmente, usamos um sistema de informações geográficas (SIG) para visualizá-las.

Após finalizar a interpretação desses dados, exportamos os resultados no formato de mapas, os quais devem atender um padrão definido, caso contrário, teríamos vários mapas (do mesmo projeto) com aparências (i.e. layouts) diferentes.

Entretanto, como podemos padronizar essa confecção de mapas? Como salvamos nosso projeto no ArcGIS e no QGIS? Como podemos utilizar inúmeras vezes o mesmo template?

Confira nossa postagem e descubra.

Já comentamos em um dos nossos vídeos como realizar a organização das suas pastas do seu SIG. Nesta postagem, iremos mostrar um passo a passo para você criar seu template de mapa, de modo que você possa sempre aproveitá-lo em outros mapas e projetos.

Criando seu mapa base no ArcGIS

No ArcGIS, logo após abrir o software, normalmente, ele abre uma janela com alguns layouts de mapas já estabelecidos. Porém, no nosso caso, queremos criar um mapa novo, então, iremos clicar em New Maps (Novos Mapas) > Meus Templates (My Templates)(1) > Mapa Vazio (Blank Map)(2) e depois em OK (3).

Criando um mapa em branco no ArcGIS.Criando um mapa em branco no ArcGIS.

Defina o sistema de coordenadas do seu projeto e vá no Layout View.

Para definir o sistema de coordenadas do seu projeto, clique com o botão direito sobre o Data Frame na tabela de conteúdos (Table of Contents), vá em propriedades e em seguida, na aba Sistema de Coordenadas. Nesta aba, você escolhe qual sistema irá adotar.

No Layout View, insira e organize todos os elementos do seu mapa, tais como:

  • Título;
  • Legenda;
  • Norte;
  • Escalas gráfica e numérica;
  • Grade de coordenadas;
  • Outros elementos (por exemplo, autor, empresa, data e sistema de coordenadas adotada).

Não esqueça também de modificar as configurações do papel, que pode ser modificada clicando sobre o fundo com o botão direito e selecionando Configuração de Página e Impressão (Page and Print Setup).

Janela para configuração da página / folha de impressão no ArcGIS.Janela para configuração da página / folha de impressão no ArcGIS.

Após inserir os elementos do seu mapa, vá em Arquivo (File) e clique em Salvar (Save) ou Salvar Como (Save As). Uma nova janela será aberta solicitando onde você quer salvar o arquivo no formato MXD, que representa um documento do ArcMap.

Ao compartilhar esse documento, você estará enviando somente o layout do mapa e não estará incluso os arquivos que você abriu nele, tais como shapefiles e rasters.

Um exemplo de mapa criado é apresentado na figura abaixo.

Exemplo de Layout criado no ArcGIS.Exemplo de Layout criado no ArcGIS.

Agora, com este arquivo no formato MXD é possível, ao abrir um novo projeto no ArcGIS, selecioná-lo para que você abra as mesmas configurações de layout que você já havia criado.

Para replicar esse layout para outros mapas, crie cópias deste arquivo MXD e renomeie elas com o nome do novo mapa (e.g. “mapaSolos.mxd”, “Hidrografia.mxd”).

Criando seu mapa base no QGIS 2.18

Na versão 2.18 do QGIS, é possível criar vários templates utilizando o gerenciador de layouts. Este pode ser acessado clicando-se em Projeto (Project), Novo Compositor de Impressão (New Print Composer). Após clicar neste item, o QGIS irá solicitar o nome do layout. Podemos chamá-lo de “Mapa A4 Retrato”.

Após o compositor de impressão ser aberto, é possível modificar as configurações da página na aba do lado direito (1) e em seguida, adicionar os item como Norte, Legenda e Escala pelos menu lateral (2) ou pelo menu superior Layout (3).

Compositor de mapas do QGIS 2.18.Compositor de mapas do QGIS 2.18.

Agora, após adicionar e organizar todos os elementos do seu mapa, clique em Compositor (Composer) e em seguida em Salvar Projeto (Save Project). Isso irá salvar o projeto e os layouts do compositor de layouts.

Lembre-se que ao clicar sobre um elemento, suas propriedades podem ser mudadas na aba do lado direito do compositor.

A figura abaixo mostra um exemplo de layout criado no QGIS 2.18.

Exemplo de mapa base criado no QGIS 2.18.Exemplo de mapa base criado no QGIS 2.18.

O arquivo salvo estará no formato QGS, formato dos projetos salvos no QGIS 2.18. Cabe salientar que no QGIS, por meio do compositor de impressões, é possível duplicar o layout que você já criou e aproveitá-lo para outro mapa com dados similares.

Leia também: Layout de Mapas no QGIS (II) e Layout de Mapas no QGIS (III)

Com esse arquivo QGS, você poderá duplicá-lo (criar cópias) para desenvolver outros mapas utilizando sempre o mesmo template.

Criando mapa base no QGIS 3

O procedimento para criação de templates no QGIS 3 é semelhante à versão 2.18, entretanto, ao salvar seu projeto, você verá que ele estará no formato QGZ.

Lembrando também que alguns itens (botões) mudaram de posição no compositor de mapas do QGIS 3, mas nada que interfira no desenvolvimento dos seus templates de mapas.

Agora você já conhece os caminhos para desenvolver seus templates de mapas e agilizar o desenvolvimento de novos mapas, sem precisar ter que criá-los manualmente.

by Fernando BS at January 08, 2019 05:02 AM

January 07, 2019

In December, we wanted to know what QGIS.ORG should focus on in 2019.

Portuguese 

selection_002

Based on these results, in today’s PSC meeting, we’ve decided that the 2019 grant programme will be focusing on bug fixing and polishing existing features. So thanks to everyone who provided feedback!

New question

This month, we’d like to know if you have ever contributed to improving QGIS and – if yes – how. As you’ll see, there are many different ways to contribute to QGIS, so please go ahead and take the survey.

The survey is available in English, Spanish, Portuguese, French, Italian, Ukrainian, and Danish. If you want to help us translate user questions in more languages, please get in touch!

by underdark at January 07, 2019 09:03 PM

January 05, 2019

PyQGIS 101: Introduction to QGIS Python programming for non-programmers has now reached the part 10 milestone!

Beyond the obligatory Hello world! example, the contents so far include:

If you’ve been thinking about learning Python programming, but never got around to actually start doing it, give PyQGIS101 a try.

I’d like to thank everyone who has already provided feedback to the exercises. Every comment is important to help me understand the pain points of learning Python for QGIS.

I recently read an article – unfortunately I forgot to bookmark it and cannot locate it anymore – that described the problems with learning to program very well: in the beginning, it’s rather slow going, you don’t know the right terminology and therefore don’t know what to google for when you run into issues. But there comes this point, when you finally get it, when the terminology becomes clearer, when you start thinking “that might work” and it actually does! I hope that PyQGIS101 will be a help along the way.

by underdark at January 05, 2019 02:31 PM

January 04, 2019

O Java Code Sprint 2018 foi um evento ambicioso que reuniu projetos Java da OSGeo para analisar a compatibilidade com Java 11. Com uma ótima resposta da comunidade, o GeoServer agora pode rodar no Java 11!


GeoServer Server Status Page

Esse sprint foi uma resposta importante da comunidade às mudanças do Java. A motivação imediata é dar aos usuários a opção de usar o Java 11 na próxima versão do GeoServer (2.15.x), agora que o OpenJDK está assumindo como projeto principal. Também temos o prazer de informar que o Java 8 continuará sendo suportado (graças ao compromisso da RedHat e da Adopt OpenJDK), dando a todos a oportunidade de migrar quando estiverem prontos.

É importante observar que o Java 11 não suporta mais o mecanismo de extensão usado para as bibliotecas JAI e ImageIO nativas. Onde as bibliotecas podiam ser instaladas diretamente no Sistema Operacional para aumento de performance das mesmas.

Como experimentar:

1. Faça o download e instale o Java 11 (jdk.java.net/11)

2. Faça o download do GeoServer 2.15-M0

3. O GeoServer 2.15-M0 será executado sob o Java 11 sem configuração adicional no Tomcat 9 ou mais recente e no Jetty 9.4.12 ou mais recente.

4. A distribuição binária inclui uma versão compatível do Jetty.

Fonte: GeoServer Blog

by Fernando Quadro at January 04, 2019 12:52 PM

With the recent GeoTools 21-M0 Milestone release available for everyone to try out ... we can finally report back on our success at the OSGeo Java 2018 Code Sprint. References: Java 11 Quickstart shows how to use the GeoTools with the new module system Java is still free for background on Java 8 and Java 11 support options (or our Java Install page  summary table) Technical Challenge The

by Jody Garnett (noreply@blogger.com) at January 04, 2019 08:05 AM

January 03, 2019

We publish the second module (of seven) of the free ‘GIS applied to archaeology’ course, where you will learn to create geographic information through the editing tools offered by the open source software called ‘gvSIG Desktop’.

We will start by creating a new layer of information that will represent our prospection areas. In that layer we will create new geometries and we will fill its attribute table in with alphanumeric information.

We will also see how to add information to an existing layer using the ‘table join’ tool.

To follow these exercises you will start with the project created in the first module of the course, so if you have not done already we recommend you start there.

The data to follow the course can be downloaded compressed in a .zip file on this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

Module 2: Creating geographic information

Previous modules:

Module 1: Preparation of an archaeological project

by Mario at January 03, 2019 10:45 AM

Os traemos el segundo módulo (de siete) del curso gratuito de SIG aplicados a arqueología, donde aprenderemos a crear información geográfica mediante las herramientas de edición que ofrece el software libre y gratuito gvSIG Desktop.

Comenzaremos creando una nueva capa de información que representará nuestra zona de prospecciones. En esa capa iremos creando nuevas geometrías y rellenando su información alfanumérica.

También veremos como agregar información a una capa existente mediante la herramienta de unión de tablas.

Para realizar estos ejercicios partiremos del proyecto creado en el primer módulo del curso, por lo que si aún no lo has hecho te recomendamos que empieces por ahí.

Los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip en este enlace.

Recuerda que para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, podéis utilizar la lista de usuarios de gvSIG.

Tema 2: Crear información geográfica

Temas anteriores

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

by Alvaro at January 03, 2019 10:12 AM

The Java 2018 code sprint was an ambitious event gathering up OSGeo Java projects to look at Java 11 compatibility. With a great response from the GeoServer community we are pleased to announce the GeoServer can now run in Java 11!

This sprint was an important response by our community to changes in the Java roadmap. The immediate motivation is to give our users the option of using Java 11 in the coming year now that OpenJDK is taking over as lead project. We are also pleased to report that Java 8 will continue to be supported (thanks to the commitment of RedHat and Adopt OpenJDK) giving everyone a chance to migrate when ready.

We had 11 participants for the sprint – thanks to everyone who attended!

  • David Vick (Boundless), Devon Tucker (Boundless), Jim Hughes (CCRi), Jody Garnett (Boundless) Kevin Smith (Boundless), and Torben Barsballe (Boundless) gathered at the Boundless office in Victoria, Canada.
  • Andrea Aime (GeoSolutions) and Antonello Andrea (Hydrologis) participated from Andrea’s home office in Italy.
  • María Arias de Reyna (GeoCat), Ian Turton (Astun), Landon Blake (BKF Engineers), and Brad Hards participated remotely.

With support from OSGeo and event sponsors many individuals were able to meet up in person, with those hosed at the Boundless Victoria office enjoying the occasional break outside.

How to try it out:

To get started:

  1. Download and install Java 11 from jdk.java.net/11
  2. Download the GeoServer 2.15-M0 milestone release of GeoServer
    • The GeoServer 2.15-M0 will run under Java 11 with no additional configuration on Tomcat 9 or newer and Jetty 9.4.12 or newer.
    • The binary distribution includes a compatible version of Jetty.

We need your help:

  • pulling together running on java 11 instructions for additional application servers, please download the WAR bundle to help out
  • testing the windows installer

Sponsors

Thanks to Gaia3D for leading with a silver sponsorship, and ASTUN Technology, OSGeo:UK, and ATOL for their bronze sponsorships.

Gaia3d

AstunLogo.png

uk.osgeo.org Atol

These sprints also require people to function, and we appreciate Boundless, GeoCat, ASTUN Technology, GeoSolutions and CCRi for their in-kind participation.

Boundless

Astun.png   Ccri.

Geosolutions GeoCat

Key accomplishments:

  • GeoServer was upgraded to Spring 5. Thanks to David Vick and everyone for this (especially the Spring Security upgrade with James).
  • Kevin went through the same steps for GeoWebCache for a difficult couple of days.
  • The EMF models that drive much of our parsing technology were upgraded. Thanks to Ian who worked through this, putting us in a much better spot to make changes to our codebase.
  • Torben helped remove countless references to internal “com.sun” classes.
  • A big thanks to Andrea for stepping up where needed (i.e. everywhere) and encouraging everyone through out the week
  • Thanks to Andrea and Brad for preliminary work that made this sprint possible.
  • Thanks to Jody for doing the milestone release.

Outstanding issues:

Certain components and dependencies could not be upgraded as no Java 11-compatible versions have been released. These have been removed or replaced by different libraries where possible, but some incompatible libraries remain.

The remaining issues are primarily either Internal API usage or Illegal access. These will only cause problems when running on Java 11:

Internal API usage

Some components and dependencies reference internal Java API. Depending on the nature of this API, calling this code may cause a runtime error or a warning when running on Java 11. If you run into any unusual failures when running under Java 11, please report them.

Examples of libraries producing these warnings:

  • freemarker template library (used for GetFeatureInfo responses)
  • ehcache library used for image mosaic performance
  • Java Advanced Imaging used for image processing

Illegal Access

Java 11 introduces stricter access constraints on reflective operations. For now, such issues will only cause a warning in the logs, of the form:

WARNING: Illegal reflective access by …

In future versions of Java, this will instead cause a runtime error.

Known warnings you can expect when running in Java 11:

  • org.hsqldb.persist.RAFileNIO
  • org.parboiled.transform.AsmUtils
  • org.fest.reflect.util.Accessibles
  • com.google.protobuf.UnsafeUtil
  • net.sf.cglib.core.ReflecUtils

If you run into a reflective access warning about a package not in this list, please report it.

Community Modules

The following community modules do not yet support Java 11:

  • printing
  • script
  • spatiallite
  • monitor-hibernate

Further reading:

by jgarnett at January 03, 2019 01:23 AM

January 02, 2019

We've released version 3.1 of the Plugin Builder for QGIS 3.x. This version contains a number of bug fixes and performance enhancements.

Here are some of the changes included since version 3.0.3:

  • Fix issue with reload on generated plugins
  • Move dialog creation to run method to improve startup performance
  • Move help file generation files to proper method
  • Include missing tags file
  • Attempt to compile resources.qrc when plugin is generated (requires pyrcc5 in path)
  • Set deployment directory in Makefile based on user OS (pb_tool is recommended over make)
  • Check for valid URL format for tracker and repository

Compiling Resource File

If you have the resource compiler pyrcc5 in your path, the resource file will be compiled automatically when you generate your new plugin. This means it's ready to deploy and test without any further steps.

Using pb_tool

Although a Makefile is created when you generate a new plugin, you are encouraged to use pb_tool for compiling, deploying, and managing your plugins. It runs everywhere and simplifies your plugin development.

pb_tool works with both Python 2.x and 3.x.

See http://g-sherman.github.io/plugin_build_tool/ for information.

Installing Plugin Builder

You can install Plugin Builder 3.1 from the Plugins -> Manage and Install Plugins... menu. Version 3.1 works on QGIS versions 3.0 and up.

Plugin Builder Links

Pull requests and code contributions are encouraged.

January 02, 2019 09:00 AM

January 01, 2019

This post is to wish you all a very happy new year!

2018 has been a great year for the Semi-Automatic Classification Plugin (SCP), with the release of the version 6 for QGIS 3.
I'm very grateful to all the people who have contributed to this project, through their work translating the interface and the user manual, fixing bugs and reporting issues, and donating.



In 2019 I'll continue the development of the SCP, in particular designing the new version 7 (which should be released in the early 2020), and of course maintaining the version 6.
In the new version 7 I'll focus on the development of new features for automating and improving the processing of remote sensing images, in particular:
  • development of parallel processing in order to reduce the computational time;
  • integration with ESA SNAP software for the preprocessing of Sentinel-2 images;
  • development of standalone APIs to use the tools through the command line or Python;
  • improvement of the user interface.
I'll consider updating the version 6 with some of these new features during 2019. And of course I'll write new tutorials about applications and case studies.
Again, I wish you a very happy new year!

For any comment or question, join the Facebook group about the Semi-Automatic Classification Plugin.

by Luca Congedo (noreply@blogger.com) at January 01, 2019 08:00 AM

In a previous article Using pg upgrade to upgrade PostGIS without installing older version I demonstrated a trick for upgrading to a newer PostgreSQL instance from PostGIS 2.2 - 2.whatever without having to install the older version of PostGIS in your new PostgreSQL service. Unfortunately that trick does not work if coming from PostGIS 2.1 because in PostGIS 2.2 we renamed a c lib function that backed sql functions in 2.1.

Fear not. There is still a way to upgrade from 2.1 to 2.5 without installing an older version of PostGIS in your new PostgreSQL instance. To do so, you need to add a step and that is to remove the functions in 2.1 that are backed by this renamed lib function. In upcoming PostGIS 3.0, we've added this function back and have it throw an error so that even coming from PostGIS 2.1, you can upgrade just the same as you do from later versions.

Continue reading "Using pg_upgrade to upgrade PostgreSQL 9.3 PostGIS 2.1 to PostgreSQL 11 2.5 on Yum"

by Regina Obe (nospam@example.com) at January 01, 2019 06:48 AM

We are happy to share a GeoServer 2.15-M0 milestone release with downloads (zip|war|exe), documentation (html|pdf) and extensions.

This milestone release is provided for everyone considering a Java 11 operational environment in 2019.  A milestone release provides a technology preview and a chance to support the development team with early feedback:  your assistance and participation is requested!

This release is a result of participation in the OSGeo Java 2018 Code Sprint and is made in conjunction with GeoTools 21-M0 and GeoWebCache 1.15-M0. We would like to thank organizations participating in the code sprint (Boundless, GeoSolutions, GeoCatAstun TechnologyCCRi) along with sprint sponsors (Gaia3Datol, osgeo:uk, Astun Technology). Our gratitude goes out to the individuals who worked so hard to bring everything together.

Java 11 Support

The provided binary download works with either Java 8 or Java 11. Tomcat 9 or newer is required for the WAR install.

We will the update the user guide compatibility list based on your feedback and testing of this 2.15-M0 milestone release. Please note that Java 11 no longer supports the Java 2 extension mechanism used for native JAI and native ImageIO.

This is a good opportunity to review your operational environment and help test GeoServer with the environment you intend to use in 2019.

Java Roadmap Considerations

Our initial concerns with respect to continued availability of the Java 8 platform have been alleviated by industry action and commitment. Extensive Java 8 support options are now available, with RedHat making a public commitment to contribute fixes to the OpenJDK 8 codebase, and a range of organizations committed to making OpenJDK 8 builds available on a range of platforms.

Oracle has changed to a six month release schedule, donating additional components to OpenJDK to make it lead platform. Long term support (beyond six months) is being offered from a range of organizations notably RedHat OpenJDK  and Adopt OpenJDK.

The net effect of these changes:

  • If you have been using Oracle JDK up until now it is time to review your options
  • Java 8 will continue to be available
  • The Java ecosystem is now led by the open-source Open JDK project

See the GeoTools user guide for a table outlining the Java 8 and Java 11 alternatives to consider in the year ahead.

About GeoServer 2.15 Series

Additional information on the GeoServer 2.15 series:

by jgarnett at January 01, 2019 05:56 AM

GeoTools project is closing out 2018 with a GeoTools 21-M0 milestone release featuring Java 11 compatibility: geotools-21-M0-bin.zip geotools-21-M0-doc.zip geotools-21-M0-userguide.zip geotools-21-M0-project.zip maven repository This milestone release is a preview of GeoTools 21 giving everyone a chance to help test Java 11 compatibility. This release works with both Java 8 and Java 9,

by Jody Garnett (noreply@blogger.com) at January 01, 2019 05:36 AM

December 29, 2018


Community inside
Parody of "intel inside®" logo,
a trademark of Intel Corporation.
Image SVG.
"Community inside" is the "intel inside®" of Open Source Software. It's an indicator of quality and long term sustainability.

Why? Because in the digital economy, collaboration out-competes competition!

So prioritise software developed by healthy communities. Look for diverse, supportive, meritocratic, productive, welcoming and inspiring teams. Then engage productively with them.

More ...

by Cameron Shorter (noreply@blogger.com) at December 29, 2018 07:44 PM

December 28, 2018

What a year!  Following on from 2017, in no particular order, here goes: Bonn Code Sprint: talk about a worthwhile event!  It was great to meet old and new OSGeo hackers.  Serious progress made on many projects (keep reading) OWSLib: thanks to Carsten Ebrecht, we finally have a much better handling on tests (moving to […]

by tomkralidis at December 28, 2018 05:59 PM

This is the 7th progress report of the GDAL SRS barn effort.

On the PROJ side, things are consolidating up. Tens of "random" fixes have been pushed due to the GDAL autotest suite triggering a number of interesting cases. The C API has also been enhanced to accommodate for the needs of GDAL and libgeotiff. We also have received feedback from an early adopter (a developer of a pyproj binding based on PROJ master). The major development items have been the move of the WKT 1 syntax validation from GDAL to PROJ, as well as the development of an equivalent WKT 2 syntax validator in PROJ (this task has been useful to uncover a few minor issues in the draft of the future WKT2:2018 standard). A reorganization of the PROJ source tree (with a conversion of most C files to C++ files) has also been done, as a preliminary step, for a pull request to better integrate the new ISO-19111 functionality I developed those last months with the existing C API.

Regarding libgeotiff, a v1.4.3 maintenance version has been released with the fixes of the last two years, before the new works for the integration of PROJ master are done. libgeotiff development has been moved from Subversion to https://github.com/OSGeo/libgeotiff. As a preliminary step, continuous integration capability has been added to test compilation under Linux/GCC and Windows/Visual Studo, with a few runtime tests.
A pull request is ready with the integration of PROJ master with libgeotiff. It features:
  • PROJ master / PROJ 6 as a required depedency of libgeotiff
  • Use of the proj.db database to resolve the various coded values, mostly in the GTIFGetDefn() "normalization" function of libgeotiff, instead of using the .csv files previously generated from the EPSG database. Typically an EPSG code identifying a projected CRS is resolved them into its base elements: projection method, projection parameters, base geodetic CRS, etc..
  • Complete removal of those .csv files and associated functionality
This work will be merged once the above mention PROJ pull request that affects naming of the new functions of the C API has been merged and taken into account. This gdalbarn branch of libgeotiff has also been succesfully integrated in the internal libgeotiff copy of the GDAL gdalbarn branch.

Regarding GDAL, a maintenance v2.3.3 and feature v2.4.0 versions have been released for the same reasons as above.
Most methods of the OGRSpatialReference class have now been re-implemented to rely on the PROJ C API to do queries and state changes, which avoids potentially lossy import / export to WKT 1. Similarly to the libgeotiff work, the ImportFromEPSG() functionality now relies on proj.db, and consequently all EPSG or ESRI related .csv files have been removed from the GDAL data directory. I've also drafted a plan regarding on how to be able to take into account WKT 2 by GDAL raster drivers, and proposed changes regarding how to better handle the gap between the axis order as mandated by the CRS authority (for example latitude first, longitude second for geographic CRS in the EPSG dataset) and the actual order of the values in raster metadata or vector geometries. The first part (use of OGRSpatialReference in raster driver) has been implemented in the gdalbarn branch and the second part is in good progress, with the drivers now advertizing their data axis to CRS axis mapping. The ongoing work is to make  OGRCoordinateTransformation use the PROJ API to automatically compute the best transformation pipeline, enabling late-binding capabilities.



by Even Rouault (noreply@blogger.com) at December 28, 2018 01:12 PM

December 23, 2018

We are happy to announce the release of GeoServer 2.13.4. Downloads are available (zipwar, and exe) along with docs and extensions.

This is a maintenance release recommended for production use (for newer projects please use the 2.14.x series, as this is last community sponsored 2.13.x release).
This release is made in conjunction with GeoTools 19.4 and GeoWebCache 1.13.4.

Highlights of this release are featured below, for more information please see the release notes (2.13.4 | 2.13.32.13.2 | 2.13.1 | 2.13.02.13-RC1 | 2.13-beta).

Improvements and Fixes

  • Significant speedup in WMTS capabilities document generation when source data is not in WGS84
  • GeoPackage improvements, speed up raster reading and reprojection, make sure global coverage GeoPackage can be displayed
  • Removed gml:id attribute from GML 3.1 encoding (was added in previous releases by mistake)
  • NetCDF output format improvement, fixing projection coefficients in some cases, make sure data packing takes into account all data slices when calculating linear transformation coefficients
  • WCS 2.0 compliance improvements, DescribeCoverage output schema compliance fixes when using GeoServer extensions, returning correct exception type when subsetting request is out of range on time/elevation/custom dimension axis
  • KML request handling fixes, support for sortBy and CQL filtering on layer groups
  • GWC related fixes, could not modify blobstore configuration without changing its name too, wrong axis order in configuration when saving EPSG:4326 gridset configurations
  • Styling related improvements, cannot read dynamic SLD served by an apache server, SLD 1.1 posted to the REST API resulted in garbled content
  • And various others, please see the release notes for details

About GeoServer 2.13 Series

Additional information on the 2.13 series:

 

by Andrea Aime at December 23, 2018 09:42 AM

December 20, 2018

PyWPS-4.2.0 Released

At long last, a new PyWPS release is out. A new chapter in the PyWPS 4 story is now complete and as 2018 comes to an end, it is time to look back at what happened since the major release in December of 2016.

PyWPS remains fully reliant on pro bono contributions without any sort of commercial organisation around it. This means the project largely depends on how the community is able to contribute at any given time. However, it also means there are no clients to attend or shareholders to appease, no hard deadlines or sales demos. PyWPS evolves organically, to the tune of the community’s wishes.

Relying on voluntary contributions does not mean progress is slow, much to the contrary. In recent times PyWPS has had more simultaneous contributors than at any moment before in its history. This is largely due to the major step taken with PyWPS 4 towards modern Python technologies, but also to regular contributions from the Google Summer of Code (GSoC) programme and various students thesis. During these two years the Project Steering Committe (PSC) was expanded to six members, and last May PyWPS finally graduated as an OSGeo project.

In order to manage development, the Project Steering Committe (PSC) meets regularly (usually at FOSS4G events) and performs basic housekeeping: issues are reviewed and split among a series of milestones that set out a development plan. As development progresses, new issues naturally pop up, and there is always a patch or an improvement that developers wish to include in the next release. Like the Red Queen from Alice in Wonderland, the backlog for the next release seems to always have as many issues resolved as new ones to resolve. Time drags on and the perfect tidy release remains ellusive. So in the end PyWPS 4.2 is mostly a commemorative release, celebrating two years since the major release and making official all the improvements introduced since.

What are then the main improvements introduced with PyWPS 4.2? Foremost is the progressive improvement of the class model, step by step making the library more solid, agile and easier to maintain. Among other things, the input/output handling classes were refactored, the test battery was expanded and streamlined with continuous integration tools. Other relevant improvements include:

  • Introduction of Jinja2 templates to automate the generation of outputs.
  • Support for process execution in HPC environments, using Slurm or GridEngine.
  • Support for streamed URL-based data inputs (e.g. OpenDAP).
  • Automated process documentation with Sphinx.
  • New validators for JSON, DODS links and netCDF formats.

And along the way, many bugs were fixed.

The organic nature of the project has meant that the goals set out by the PSC are not always met. For instance, PyWPS 4.2 still does not fully support version 2 of the WPS standard. But such is the nature of community driven projects: evolution goes along the needs of the community and not necessarily according to grand plans. There are instead other great improvements in the pipeline, like the containerisation of processes, or the automatic storage of outputs in a database. Please get involved if these developments interest you, or if you would like other improvements to be introduced.

A word also regarding the WSGI applications provided as example services using PyWPS. pywps-flask remains the most popular but a backlog of small issues has built up. During the holiday season developers will be lending attention to these issues. Usability issues with the containers of both pywps-flask and pywps-django will also be addressed during this time.

Finally the PSC would like to thank everyone that has contributed to PyWPS these past two years: from those doing the code heavy lifting, to testers, bug reporters, documentation contributors. Every bit of contribution is precious. Thank you all for making PyWPS what it is today!

Merry Christmas and a Happy New Year.

December 20, 2018 12:00 AM

December 19, 2018

In recent years, Geographic Information Systems (GIS) have radically evolved the way in which spatial data are collected, analyzed and interpreted. Because of their characteristics, GIS have become useful applications for archaeologists. The appearance of gvSIG, with a complete suite of GIS solutions in open source software, has meant that more and more professionals in the sector are adopting gvSIG as a working tool.

However, there is still a wide ignorance of the potential of GIS in archaeology, and there are only a few free teaching materials that allows training in its use. For these reasons, from the gvSIG Association, we launch a course that will allow to know of these technologies. A free course, with open source software (gvSIG Desktop).

In this first post we want to present the main characteristics of the course, together with the first video-tutorial. As of January 2019, we will publish all the modules weekly until the agenda is completed. To follow the course, it is recommended that participants have prior knowledge about how archaeological projects are carried out.

Registration of the course and how it works

It is not necessary to register anywhere. The course is online and can be followed from anywhere in the world. The course will be available in English and Spanish.

Each week we will publish a post on this blog that will contain a video-tutorial with exercises and access to the course data. Therefore, you only need to follow the video-tutorials to complete the course.

For doubts or problems in the use of software, or about the exercises, you can use the gvSIG users mailing list:

http://www.gvsig.com/en/community/mailing-lists

List of topics

The list of topics is composed of 7 modules. Each module will contain a video-tutorial with practical exercises. The data to follow the course can be downloaded in a .zip file from this link.

  1. Preparation of an archaeological project: views, layers and tables
  2. Create geographic information: Alphanumeric information and digitalization
  3. Prospecting results analysis: Vector geoprocesses
  4. Managing old maps: Georeferencing of images
  5. Reservoir territorial analysis: Raster geoprocesses and digital terrain models (MDT)
  6. Hydrological analysis to locate materials or archaeological sites
  7. Graphical output of an archaeological project: Maps

And if you want to get a certificate?

Such as in other previous courses that we have published, many of you asked us about the possibility to obtain a certificate. To cover this possibility, at the end of the course we will publish a practical exercise to be solved, and to demonstrate that you have acquired the knowledge imparted during the course. This exercise is completely optional, only for those who want to get the certification.

To pay for the evaluation time of the exercises and the issuance of the certificate, apart from delivering the correctly solved exercise, 25 € will have to be paid. The way of payment will be indicated at the end of the course.

Module 1: Preparation of an archaeological project: Views, layer and tables

Ready? Well, let’s start with the first topic, where besides learning where to download gvSIG Desktop – the software that we will use for the course – we will see how to prepare an archaeological project working with the main components of a GIS: Views, layers and tables.

by Mario at December 19, 2018 12:10 PM

En los últimos años, los Sistemas de Información Geográfica (SIG) han evolucionado de forma radical la forma en que los datos espaciales se recopilan, analizan e interpretan. Por sus características los SIG se han convertido en aplicaciones de gran utilidad para los arqueólogos. La aparición de gvSIG, con una suite completa de soluciones SIG en software libre, ha hecho que en la actualidad sean cada vez más los profesionales del sector que adoptan gvSIG como herramienta de trabajo.

Sin embargo aún hay un amplio desconocimiento del potencial de los SIG en arqueología, y poco acceso a material educativo y gratuito que permita formarse en su uso. Por estos motivos, desde la Asociación gvSIG, lanzamos un curso que pretendemos que ayude a dar a conocer estas tecnologías. Un curso gratuito, con software libre y gratuito (gvSIG Desktop).

En este primer post queremos presentaros las características principales del curso, junto al primer vídeo-tutorial. A partir de enero de 2019 iremos publicando semanalmente todos los módulos hasta completar el temario. Para aprovechar al máximo el curso se recomienda que los participantes tengan un conocimiento previo de cómo se llevan a cabo los proyectos arqueológicos.

Inscripción y funcionamiento del curso

No es necesario inscribirse en ningún sitio. El curso es online y se podrá realizar desde cualquier parte del mundo. El curso estará disponible en inglés y castellano.

Cada semana publicaremos un post en este blog que tendrá un vídeo-tutorial con ejercicios y acceso a los datos del curso. Por tanto, sólo necesitáis ir siguiendo los vídeo-tutoriales para completar el curso.

Para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, podéis utilizar la lista de usuarios de gvSIG:

http://www.gvsig.com/es/comunidad/listas-de-correo

Temario

El temario se compone de 7 módulos. Cada módulo presentará un vídeo-tutorial con ejercicios prácticos. Los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip de este enlace.

  1. Preparación de un proyecto arqueológico: vistas, capas y tablas
  2. Crear información geográfica: Información alfanumérica y digitalización
  3. Análisis de resultados de prospecciones: Geoprocesos vectoriales
  4. Gestionando mapas antiguos: Georreferenciación de imágenes
  5. Análisis territorial de yacimientos: Geoprocesos ráster y modelos digitales de terreno (MDT)
  6. Análisis hidrológico para localizar materiales o yacimientos arqueológicos
  7. Salida gráfica de un proyecto arqueológico: Mapas

¿Y si quiere obtener un certificado?

Como en otros cursos anteriores que hemos publicado, muchos de vosotros nos preguntáis por la posibilidad de obtener un certificado. Para cubrir esta posibilidad, al final del curso publicaremos un ejercicio práctico a resolver que permitirá demostrar que habéis adquirido los conocimientos impartidos durante el curso. La realización de este ejercicio es totalmente opcional. Sólo para aquellos que quieran tener la certificación.

Para costear el tiempo de evaluación de los ejercicios y la emisión del certificado, además de entregar el ejercicio correctamente resuelto habrá que abonar 25 €. La forma de pago se indicará junto al ejercicio final.

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

¿Preparados? Pues vamos a comenzar con el primer tema, donde además de aprender de dónde descargar gvSIG Desktop – el software que utilizaremos para el curso – veremos como preparar un proyecto arqueológico trabajando con los principales componentes de un SIG: Vistas, capas y tablas.

by Alvaro at December 19, 2018 11:56 AM

A Planet Labs anunciou ontem a aquisição da Boundless Spatial, Inc., empresa de soluções de software geoespacial com sede em St. Louis, que é a responsável pelo desenvolvimento do GeoServer. A aquisição expande os negócios comerciais da Planet com o governo dos EUA e clientes da agricultura comercial. A Boundless é líder em software de gerenciamento de dados geoespaciais e está alinhada com o objetivo de fornecer novos serviços de assinatura de dados geoespaciais e acelerar a adoção em clientes corporativos.

Com a aquisição da Boundless, a Planet pretende alavancar a tecnologia e o conhecimento da Boundless implantados dentro do governo dos EUA para facilitar ainda mais a utilização dos seus produtos. Além disso, este acordo também trará novos clientes do governo dos EUA para Planet.

A Planet manterá o escritório da Boundless em St Louis (MO) e em conjunto com a equipe da Planet que trabalha diretamente com o governo dos EUA formará uma subsidiária chamada Planet Federal.

Sobre os outros escritórios da Boundless nos EUA, e também sobre os funcionários que trabalham remotamente nada foi dito!

Fonte: Planet

by Fernando Quadro at December 19, 2018 11:55 AM

December 18, 2018

Thumb

The new release of OpenMapTiles comes with many smaller changes. Version 3.9 brings rendering of docks and piers, support for multilingual street names and other improvements.

Docks and Piers

The biggest visual change is the newly added support for rendering docks and piers. Piers are now rendered in a similar way like bridges while docks were added to the water layer. This modification will have the biggest impact on complicated harbors structures like Liverpool’s harbor or spectacular structures like the famous Brighton Palace Pier.

OpenMapTiles Liverpool

Multilingual street names

To solve a pain in bilingual countries we added support for multilingual streets. It follows all other map elements like place names, country names or named points of interest. Street name labels are now rendered in all 58 languages and the selection of displayed language is done automatically based on end-user preferences or by an app developer decision.

Many changes for multilingual street names has been made by the Helsinki Regional Transport Authority. They use our maps on their websites, in the application as well as printed on the public transport stops. Another user of OpenMapTiles and contributor to the project is the Qwant map team.

Talking about languages, improvement have been made for Vietnamese and Azerbaijani nonlatin labels and there is brand new support for the Malayalam language.

Other changes in OpenMapTiles 3.9

  • National parks in the Park layer have their names.
  • Indoor POI layer contains layer and level attributes.
  • The type of sport for a pitch POI can be distinguished via subclass attribute.
  • Improved rendering of 3D buildings.
  • Fixed issues with small islands in Scandinavia.

For detailed information, read the full changelog.

View all improvements on our map and start using it via MapTiler Cloud or self-hosted OpenMapTiles.

by Martin Mikita (info@maptiler.com) at December 18, 2018 11:00 AM