Le portail francophone de la géomatique

Feeds

3227 items (0 unread) in 115 feeds

Dans la presse

• Décryptaéo, l'information géographique
• Directions Magazine : A la une
• Directions Magazine : Blogue
• Les Rencontres Décryptagéo
• SIG la lettre : divers
• Directions Magazine : Communiqués de presse
• BalizMedia : Communiqués de presse
• Revue Internationale de Géomatique : Numeros de 2012
• magazine CARTO

Du côté des éditeurs

• Imagerie Géospatiale
• Virtual Earth in Europe by Arnaud
• Geospatial made in France
• GéoTrouveTout
• Humblogue
• le blog decigeo
• Articque - Les Sytèmes d'Analyse Géographique, la cartographie, le géomarketing et la géostatistique
• GeoConcept
• arcOrama, un blog sur les SIG, ceux d ESRI en particulier
• arcOpole - Actualité du Programme
• arcUtilisateurs
• Géoclip, le générateur d'observatoire cartographique
• Le blog de Geomatys
• Camptocamp
• Blog GEOCONCEPT FR

Toile géomatique francophone

• Le blog TIC » Information Géographique
• Geospatial air du temps by Géo212
• Monde géonumérique
• Le petit blog cartographique
• ReLucBlog - SIG, MOZILLA & NTIC
• GeoInWeb
• Le monde de la Géomatique et des SIG ... tel que je le vois
• Géographie 2.0
• BloGoMaps - google maps france
• GeoRezo.net - Géoblogs
• Geotribu
• Benjamin Chartier
• neogeo
• OpenSource, Geospatial et Web ?.0
• Faire joujou avec son GPS
• Géomatique et Topographie
• HelioMap
• La chronique de la parallaxe
• Remote In Every Sense
• UrbaLine
• GEMTICE
• Serial Mapper
• SIG-o-Matic
• Librairie La GéoGraphie • Actualité internationale
• Les Cafés géographiques
• Une carte du monde.
• Les blogs du Diplo - Visions cartographiques
• Oslandia
• Le Forum français de l'OGC
• Inventis Géomarketing
• Blogue de la géomatique du MSP
• Blog technique de Nicolas Boonaert
• WebMapping
• A GeoSpatial World
• Cartes et Cartographie / Maps and Mapping
• Sample Digital Orthophoto Images
• Silatitudes - Accueil
• RSS Libre@vous
• Blog d'Intelli3
• Audissey
• GeoReader's Digest
• Michael TRANCHANT
• Le blog d'Henri Pornon
• Data and GIS tips
• Geo By The Cloud
• 123 Opendata
• ReLucBlog
• L'Atelier de Cartographie
• AdrienVH.fr, le blog » Cartographie
• Cartes et figures du monde
• Baptiste Coulmont » cartographie
• l'aménagerie » SIG
• geomarketing.ca
• Libertic
• My Geomatic
• OpenStreetMap France
• Sigea : actualités
• Géosource
• www.touraineverte.com
• archeomatic
• Geographica » Cartographica
• Tutoriels et formations gratuits des logiciels SIG ArcGIS, MapInfo, ArcView GIS etc.
• simon mercier
• GIS-blog.fr
• Séries temporelles
• Le blog d'Alexandre Cazaux
• Veille cartographie
• TempoGéo
• Chroniques Cartographiques
• Carnet (neo)cartographique
• Blog SIG & Territoires ---- Le blog SIG pour la gestion territoriale
• GEOMATIQUE
• GEOMATICK

Géomatique anglophone

• Planet Geospatial - http://planetgs.com
• Google Maps Mania
• All Points Blog
• Directions Media - Podcasts
• Navx
• James Fee GIS Blog
• OGC News Feed

Blogs GeoRezo.net

• Parcell'air
• Le coin de l'open-source géospatial
• INSPIRE by clouds
• Les GéoBlogs
• Infobulle
• Le blog SIG & URBA
• Blog Interopérabilité & GéoInformation

Autres planets

• Planet OSGeo

Autres planets

• 02 June 2020
• 18:05

  gvSIG Team: gvSIG Online: Custom legends

  sur Planet OSGeo

  One of the novelties of the latest version of gvSIG Online is that apart from the typical types of legend (unique symbol, unique values, expressions or intervals) we can create custom legends through the SLD format.

  Thanks to this format we can load symbologies that we have previously created in a layer in a Desktop GIS on the one hand, and on the other hand we can apply symbology of different types to apply heat maps, patterns, transformation functions …

  You will be able to consult all these options in the Geoserver documentation, and in this video you will be able to see how it works and some practical cases:

• 17:57

  gvSIG Team: gvSIG Online: Leyendas personalizadas

  sur Planet OSGeo

  Una de las novedades de la última versión de gvSIG Online es que aparte de disponer de los tipos de leyenda típicos (símbolo único, valores únicos, expresiones o intervalos) podemos crear leyendas personalizadas a través del formato SLD.

  Gracias a este formato podemos, por una parte, cargar simbologías que hayamos creado en una capa previamente en un SIG de Escritorio, y por otro lado podemos aplicar simbología de distintos tipos aplicando mapas de calor, patrones, funciones de transformación…

  Podéis consultar todas estas opciones en la documentación de Geoserver, y en este vídeo podéis ver mejor su funcionamiento y algunos casos prácticos:

• 1:45

  Narcélio de Sá: TecnoloGEO 10 – Dado é informação e informação é dinheiro.

  sur Planet OSGeo

  Neste podcast: O TecnoloGEO 10 traz até você um bate-papo com Murilo Cardoso, Narcélio de Sá e Professor Lobão do canal Mais Geo nesse episódio gravado no dia do Geógrafo iremos conversar sobre o IBGE, a importância do Censo para o subsidio de informações para políticas públicas, estudos e pesquisas científicas das áreas econômicas, educacionais, de saúde, sociais e muitas outras.

  Comemora-se, no dia 29 de maio, o dia do geógrafo. O profissional formado em Geografia é responsável por estudar, analisar e compreender a lógica de produção e transformação do espaço humanizado, bem como a relação desse com o meio natural. Assim, a pertinência do geógrafo é a abordagem da interação entre natureza e sociedade.

  Comemora-se, no dia 29 de maio, o dia do geógrafo. O profissional formado em Geografia é responsável por estudar, analisar e compreender a lógica de produção e transformação do espaço humanizado, bem como a relação desse com o meio natural. Assim, a pertinência do geógrafo é a abordagem da interação entre natureza e sociedade.

  O IBGE tem várias atribuições ligadas às geociências e estatísticas sociais, demográficas e econômicas. Incluem-se entre elas a realização de censos e a organização das informações por eles obtidas, de modo a suprir órgãos das esferas governamentais federal, estadual e municipal, bem como outras instituições e o público em geral.

  Aperte o ? para começar o TecnoloGEO #10

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 10: Livros:

  • Direito Administrativo Geográfico. Fundamentos na Geografia e na Cartografia Oficial do Brasil – Luiz Ugeda
  • Fahrenheit 451 – Ray Bradbury
  • O Homem do Castelo Alto – Philip K. Dick

  Filmes/Séries

  • Idiocracia (2006) – Mike Judge
  • The Handmaid’s Tale
  • Black Mirror
  • Explained
  • História Direto ao Assunto
  • Segunda Guerra em Cores
  • O Homem do Castelo Alto
  • A Outra História Americana

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 10 – Dado é informação e informação é dinheiro. appeared first on Narcélio de Sá.

  
• 01 June 2020
• 16:58

  GIScussions: Free is great but time is money

  sur Planet OSGeo
  Free is Great – thanks to William White via Unsplash

  I’ve been thinking about this post for a while now and I finally wanted to write something about gaming freemium. What do I mean by “gaming freemium”? How much effort will you go to in order to avoid paying for something?

  Most free services place a limit on the usage that you can get for nothing, the clever ones give you enough to make the service really useful and make their money from a small percentage of users who see sufficient value in having less limited access to the service to be willing to pay.

  We all love a free service, particularly if it is very useful or enjoyable, but a lot of us have a resistance to taking the leap across the payment chasm between free and premium. I know I have resisted, strategised, justified and wasted time and energy many times rather than pay!

  Let me give you a couple of examples from my recent experiences.

  I have had a Google account for almost 15 years, I use gmail for most of my mail, I use Drive for online document collaboration and storing presentations, I use Forms for all sorts of things and I use Photos as a backup for my photo collection. When I started using Google they offered 2 or 5GB of storage with the free account, that has gradually increased to 15GB and some types of data (eg. photos in medium res) do not count towards my 15GB. Recently I started receiving warning messages telling me that my storage was close to the limit. I hacked around looking for ways to strip attachments from emails (not as easy as it should be) or to move some of my storage to another account or deleting some stuff that I probably didn’t need or …

  What I didn’t do was just pay £16/year to upgrade because the service was free when I started and I wanted it to stay free! After several attempts and quite a few hours trying to reduce my storage size I realised that £16 was not an unreasonable charge to have effectively unlimited usage of my Google mail and Drive.

  I have been using ZeroSSL and Let’s Encrypt to generate free SSL certificates for 3 websites that I manage. The service is a bit fiddly for a non-tech like me but it works and after spending several hours the first time I generated and installed the certificates, I have now got this down to an hour’s work every 3 months (Let’s Encrypt certificates only last 3 months). When I went to ZeroSSL last week their whole service had changed and while I could generate a single free certificate, multiple certificates required a paid account or perhaps I could work out a way to register for 3 different free accounts with different email addresses. After my Google storage experience I decided to check out what it would cost to buy SSL certificates from one of the budget providers (I don’t have any e-commerce activities). The aptly named CheapSSL had a very helpful person providing online chat advice to answer my queries and in a few minutes I had bought 3 certificates with a year’s duration for less than £16. Job done and I won’t have to update the certificates for a year! Next year I will probably buy the even cheaper 3 or 4 year certificates to save having to install them each year.

  I could go on with further examples but hopefully you get the point, even if I only valued my time at £10 or £15 an hour (and I promise you that I don’t) it would be cheaper to pay for SSL Certificates or Google storage rather than burn time trying to find a free alternative or a workaround.

  But time is money – thanks to Luis Villasmil via Unsplash

  My pal Ed Freyfogle runs a geocoding service at OpenCage Data. They offer a “Free Trial” tier which allows up to 2,500 hits a day but note the account is for trial purposes not production use. The FAQ says

  How long can I use the free trial?
  
  As long as you need for testing. That is what it is there for. If you decide to use our service in production you should become a customer.Please note: inactive free trial accounts are deleted after six months.
  
  Can I just use multiple free trial accounts?
  
  No, don’t do that. The free trial is a way to test our service – do not use it for anything mission critical. If you need production level reliability, become a customer.

  That’s pretty clear and sounds fair to me. When I chat with Ed he often regales me with amusing tales of the extents to which people will go to exceed the 2,500/day limit without paying – fake emails, spoofing IP addresses, all sorts of wheezes. Of course if you really are desperate to get geocodes for nothing you could:

  • download the OpenStreetMap data for the whole world on which the OpenCage service is based
  • you could build your own geocoder
  • you could run it on your own server
  • and you could update the data on a regular basis

  There’s loads of how to advice on downloading OSM and setting up a geocoder out there if you search. If you build your own geocoder that will give you unlimited free geocoding except for the time it would take you to build and maintain and the cost of the server or PC. If that sounds like too much time and hassle why not consider paying someone else to do it for you? If you want a top reverse geocoding service to support your business needs have a look at OpenCage.

  Remember – Free is great but time costs money

• 11:00

  CARTO Blog: US Protest Map & Visualizing Police Violence

  sur Planet OSGeo
  A week ago African-American George Floyd tragically died whilst in police custody sparking a wave of unrest and protests in cities across the US. As with any societal issue...
• 31 May 2020
• 2:00

  PostGIS Development: PostGIS 2.3.11

  sur Planet OSGeo

  The PostGIS Team is pleased to release PostGIS 2.3.11. This is the last bug fix release of the PostGIS 2.3 series. Please upgrade to 2.4 or higher if you want to continue receiving bug fixes.

  • source download
  • NEWS
  • PDF docs en

  If you come across any issues, feel free to report via our ticket tracker [https:] or mailing list with details as described here. For security issues, send reports to security@postgis.net.

  Continue Reading by clicking title hyperlink ..
• 29 May 2020
• 11:00

  CARTO Blog: City Pedestrianization & Micromobility Post COVID-19

  sur Planet OSGeo
  Cities around the world are already becoming smarter using Location Intelligence for a wide range of use cases from urban planning and micromobility analysis, to ensuring c...
• 28 May 2020
• 14:30

  Jackie Ng: Introducing FdoCmd, the missing CLI for FDO

  sur Planet OSGeo
  Fixing long time annoyances is not the only standout feature of the upcoming 1.4 release of FDO Toolbox. This release will also introduce a new command-line tool that replaces the existing FdoInfo.exe and FdoUtil.exe tools and combines their functionality into a single, flexible, script-friendly CLI tool.
  
  The original FdoInfo/FdoUtil tools were implemented with the goal of getting a basic command-line experience for FDO functionality without much thought into proper best practices for how CLI tools should behave and work in a shell scripting context.
  In the many years since, having accumulated experience in using various CLI tools (in particular, the git command-line client) and .net libraries coming into existence like CommandLine, which makes creating .net CLI applications in the behavioral template of git and friends dead-simple, I saw the re-activation of FDO Toolbox development as an opportunity to do away with FdoInfo/FdoUtil and build a proper CLI tool that can act as a true command-line companion for FDO Toolbox.
  And thus FdoCmd.exe was born.
  To understand why FdoCmd.exe came to be, it probably helps to explain what my high-level goals were for FdoCmd.exe

  • It has to verb-based.
  • It has to be mostly self-documenting and its functionality easily discover-able.
  • Its output has to be in a form that allows for it to be easily capture/parsing in shell scripts. Since FDO Toolbox is a windows-only tool, we are primarily referring for FdoCmd.exe to be easily driven by Powershell script, powershell being the predominant shell scripting environment for Windows.
  • It has to have functional parity with the core features provided by its GUI counterpart. The normal things you do in FDO Toolbox (the windows application) should be also doable in FdoCmd.exe.

  Each goal I'll be explaining in greater detail below.
  Verb-based terminology
  FdoCmd.exe is a verb-based CLI. What we mean by this is that the first argument you pass to FdoCmd.exe is the verb that you want to run followed by arguments specific to that particular verb. The most famous example of CLI tools that follow a verb-based pattern is the git command line client. 
  When using the git command-line client, every command always starts with "git":

  • git add somefile.txt
  • git commit -m "some commit message"
  • git reset --hard
  • git merge origin/master

  FdoCmd.exe follows this same pattern for all the functionality it provides.
  Self-documenting and discoverability
  The verb-based design contributes to the discover-ability of FdoCmd.exe. What do we mean by this? If you run FdoCmd.exe without arguments, you effectively get a "directory listing" of all supported verbs.
  
  
  From here you know what verbs to use, and you can drill down further. Want to know what arguments you need for the list-schemas verb? Just run FdoCmd.exe list-schemas and the tool will tell you.
  
  And for some verbs, we even provide some examples.
  
  
  It is this discoverability that lends to the self-documenting nature of the tool. There's really no need to write a dedicated set of documentation for this tool when the tool can tell you itself how its meant to be used.
  Shell-scripting friendliness
  FdoCmd.exe was designed with the requirement that it should be easy to write shell scripts around the tool. On windows, the predominant shell scripting environment is Powershell, so the outputs of FdoCmd.exe is such that it can be easily parsed and processed in powershell code.
  For example, listing the classes of a data store prints each class name line by line.
  
  Which is easily captured as a string array when invoked within a powershell script
  

  1 2 3 4

  $classNames = & .\FdoCmd.exe list-classes --provider OSGeo.SHP --connect-params DefaultFileLocation D:\fdo-trunk\Providers\SHP\TestData\Sheboygan foreach ($className in $className) { Write-Host "Doing something with: $className" }

  
  Where applicable, FdoCmd.exe provides CSV output for its verb, which when combined with the ConvertFrom-CSV cmdlet allows powershell to easily consume FdoCmd.exe output for particular verbs as an array of objects. For example, you can query out features as CSV (along with the usual querying features like filtering and selective output of properties)
  
  Which easily allows for powershell scripts to read features as arrays of objects.
  

  1 2 3 4 5 6 7 8 9

  $records = & .\FdoCmd.exe query-features --class Parcels --from-file D:\fdo-trunk\Providers\SHP\TestData\Sheboygan\Parcels.shp --schema Default --filter "RNAME LIKE 'SCHMITT%' AND RYEAR > 1950" --properties FeatId RNAME RYEAR RBILAD RCITY RZIP --format CSV | ConvertFrom-CSV foreach ($record in $records) { $fid = $item.FeatId $name = $item.RNAME $addr = $item.RBILAD $city = $item.RCITY $zip = $item.ZIP # Do stuff with these values }

  
  For convenience, querying features through FdoCmd also supports GeoJSON output for easy conversion of feature data to GeoJSON.
  
  If you recall my previous post on splitting out a SHP file to individual GeoJSON files per feature, FdoCmd.exe has all the tools (pun intended) to now do this in a single powershell script!
  
  

  1 2 3 4 5 6 7 8 9

  $srcPath="C:\TestData\national-esri-fe2019\COM_ELB_region.shp" $featIds = & .\FdoCmd.exe query-features --from-file $srcPath --class COM_ELB_region --properties FeatId --computed-properties FileName "concat(lower(Elect_div), '_new_0_', lower(State))" --format CSV | ConvertFrom-CSV foreach ($item in $featIds) { $fid = $item.FeatId $fn = $item.FileName $outPath = "C:\TestData\electorates_geojson\$fn.geojson" & .\FdoCmd.exe query-features --from-file $srcPath --class COM_ELB_region --filter "FeatId = $fid" --format GeoJSON | Out-File -FilePath $outPath Write-Host "Saved: $outPath" }

  
  Functional parity with FDO Toolbox
  Anything you normally do in FDO Toolbox, you should be able to do in FdoCmd.exe as well.

  • Creating/Destroying data stores
  • Introspecting required provider parameters to connect, create, destroy data stores.
  • FDO provider registration/unregistration
  • Walk the structure (schemas/classes) of any data store
  • Listing/creating/destroying spatial contexts
  • Exporting/Applying FDO schemas 
  • Querying features in a feature class
  • Run SQL commands on data stores where the provider supports SQL commands
  • Easily bulk copy features from a feature class to a target data store
  • Executing existing bulk copy / join definition files

  Along with some convenience functionality that is exclusive to FdoCmd.exe:

  • Get a total count of features in any feature class
  • Get the extent of any feature class
  • CSV or GeoJSON output for feature/SQL query commands

  Where to from here?
  As far as I am concerned, when FDO Toolbox 1.4 is released (coming real soon!). The FdoCmd.exe tool that ships with it will be functionally complete.
  The only thing that can be improved on at that point would be to port it over to C++ and built against the native FDO APIs (instead of the windows-only .net wrapper APIs), so it can be part of the FDO native binary set, whether it's on Windows or Linux. That way, even if there won't be FDO Toolbox for Linux, at least you'll have access to its functionally equivalent CLI tool.
• 26 May 2020
• 20:12

  Fernando Quadro: Curso Online de GeoServer em Junho

  sur Planet OSGeo

  Caros leitores,

  Gostaria de informá-los que estão abertas as inscrições para mais uma turma do Curso Online de GeoServer que estarei ministrando pela GEOCURSOS. O objetivo do curso é que você aprenda a configurar e compartilhar dados geográficos na internet com o GeoServer.

  Esta é a turma de número 20, devido a isso houve uma atualização do conteúdo do curso, além da inclusão de carga horária, agora com 15h, e conteúdo inédito. Veja abaixo a nova ementa:

  • Introdução aos padrões OGC
  • Instalação e configuraç&ao
  • Publicação de dados vetoriais
  • Publicação de dados PostGIS
  • Formatos de saída
  • Instalação de Plugins
  • Como realizar upgrade de versão
  • Cache
  • Estilos utilizando SLD
  • Substituição de variáveis no SLD
  • Utilização da API Rest
  • Criação de camadas com SQL View
  • Segurança
  • Boas práticas
  • Preparação do GeoServer para ambiente de produção
  • Gerar HeapMap com o padrão WPS
  • Como utilizar o plugin Importer
  • Aplicação prática com OpenLayers

  O curso ocorrerá entre os dias 30 de junho e 09 de julho (terças, quartas e quintas) das 20:00 as 22:30 (horário de Brasília).

  Aqueles que poderem divulgar para seus contatos, agradeço. Quem quiser saber mais informações sobre o curso, pode obtê-las nos seguintes links:

  • Site do curso ( [www.geocursos.com.br] )
  • Twitter ( [twitter.com] )
  • Facebook ( [www.facebook.com] )
  • Instagram ( [www.instagram.com] )
• 14:51

  Fernando Quadro: Canal da Geocursos no YouTube

  sur Planet OSGeo

  Prezados leitores,

  Ontem (25/05) a Geocursos inaugurou seu canal no YouTube e eu estou aqui para convidá-los a conhecer!

  Neste espaço será publicado dicas, notícias e novidades sobre Geotecnologia livre e também será falado sobre os nossos assuntos favoritos: GeoServer, PostGIS, OpenLayers, WebGIS, e muitos mais.

  Gostaria então de convidar vocês a assistirem e a comentarem o primeiro vídeo e a se inscreverem no canal!

  
  
  

• 25 May 2020
• 21:47

  Narcélio de Sá: TecnoloGEO 09 – A vida o universo e tudo mais.

  sur Planet OSGeo

  Enclosure: [download]

  Neste podcast: O TecnoloGEO 09 leva você ao fim do Universo a bordo da nave Coração de Ouro para homenagear o dia da Toalha, o dia mais Nerd do ano, com um bate-papo entre Murilo Cardoso, Narcélio de Sá e Luiz Sadeck sobre geotecnologias absurdas ou não que seriam dignas da mente brilhante de Douglas Adams. Embarque você também nessa viagem em busca da pergunta certa para a resposta que explica a Vida, o Universo e Tudo Mais.

  25 de Maio, o dia da Toalha.

  O dia 25 de maio, conhecido como Dia da Toalha, foi escolhido pelos seguidores da série Guia do Mochileiro das Galáxias para homenagear o autor Douglas Adams. Ele possui esse nome em referência ao terceiro capítulo do livro, onde Adams dedica uma pagina inteira às diferentes utilidades de uma toalha.

  O dia 25 de maio também é conhecido como o Dia do Orgulho Nerd por ter sido o dia da premiere de Star Wars Episódio IV: Uma Nova Esperança em 1977. No entanto, os fãs de Star Wars preferem comemorar o Star Wars Day no dia 4 de maio devido ao trocadilho em inglês “May the Forth be with you”. Nós inclusive lançamos um episódio no dia 04 de maio, TecnoloGEO 06 – Ciência de dados: Que a força esteja com você!.

  Aperte o ? para começar o TecnoloGEO #09

  Podcast: Download do TecnoloGEO 09
  

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 09: Livros:

  • O guia definitivo do mochileiro das galáxias – Douglas Adams
  • O ócio criativo – Domenico De Masi
  • O Futuro do Trabalho – Domenico De Masi
  • O Futuro Chegou – Domenico De Masi
  • A Sociedade Pós-industrial – Domenico De Masi
  • A Quarta Revolução Industrial – A Quarta Revolução Industrial
  • A Terceira Onda – Alvin Tofler

  Filmes

  • O Silêncio dos Inocentes – Jonathan Demme
  • A Família Addams – Barry Sonnenfeld
  • A Bela e a Fera – Gary Trousdale , Kirk Wise
  • Terminator 2: Judgment Day – Terminator 2: Judgment Day
  • O Guia do Mochileiro das Galáxias – Garth Jennings
  • A Vida de Brian – Terry Jones
  • Monty Python e o Cálice Sagrado – Terry Gilliam , Terry Jones

  Música

  • Innuendo – Quenn
  • Nevermind – Nirvana
  • Blood Sugar Sex Magik – Red Hot Chili Peppers
  • OK Computer – Radiohead

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 09 – A vida o universo e tudo mais. appeared first on Narcélio de Sá.

  
• 19:12

  Fernando Quadro: Live sobre GeoServer

  sur Planet OSGeo

  Prezados leitores,

  A convite do Anderson Medeiros estarei participando de uma Live no canal da ClickGeo hoje as 20:30h falando um pouco sobre os “Primeiros Passos com o GeoServer para Publicação de Mapas Online”.

  A Live será um bate-papo onde apresentarei como iniciar com o GeoServer e também suas potencialidades para interoperabilidade de dados espaciais na internet.

  Se você ficou interessado, segue abaixo o link da Live:

  
  
  

• 13:51

  Jackie Ng: Fixing and improving long-standing FDO Toolbox annoyances

  sur Planet OSGeo
  After 5+ years of inactivity, the FDO Toolbox project has roared back to life.
  
  What prompted this burst of development activity? Years upon years of eating my own dogfood in my day job. Every-time I needed to load spatial data? Whip out the toolbox. Every-time I needed to take a peek at some spatial data to see what I'm dealing with? Whip out the toolbox. But those many years of self-usage also revealed many annoyances I had with using the tool and it was a constant battle between "just fix the problem already" and "we can workaround it".
  
  For the longest time, "we can workaround it" had always been the winner, but those annoyances and pain points have built up to a critical mass of annoyance where I've finally decided to nip these problems in the bud once and for all.
  
  So for this post, I'm going to outline some common scenarios and how the upcoming 1.4 release of FDO Toolbox will make these scenarios much simpler to carry out.
  
  Scenario: Connecting to an RDBMS server with lots of data stores
  
  Ever connect to a SQL Server that has lots of databases within (eg. 50+) and the current connect UI forces you to wait for the FDO provider to enumerate all those databases to load into a combo-box where you then have to pick and sift through to find your database in question.
  
  
  Or heaven forbid, one of these 50+ databases is slightly misconfigured security-wise, and blows up the data store enumeration process. The UI in its current form has no escape hatch. You literally cannot make a connection to this SQL Server through the UI provided as a result. Now the actual bug is no longer an issue because the upcoming release will include FDO 4.1, whose SQL Server provider has this fix, but this scenario is being used as an example of the failings of the current connect UI.
  
  Most of the time, you probably already know the name of the database you want to connect to, so in the upcoming release, that combo-box is now editable, allowing you to bypass this whole enumerating all the databases by putting in the name of the database directly and going straight to connect
  
  
  
  Scenario: Setting up a bulk copy involving lots of files
  
  Say you made a blank SQL Server database, and you want to load in these data files
  
  How would you do this in current FDO Toolbox? It would be as follows:
  

  1. Connect to the SQL server database
  2. Connect to your data files
  3. Create a new bulk copy
  4. For each data file, add a copy task and pick the source feature class to copy and its destination target
  5. Review all the copy task options. Did you not want to copy/map all the properties? Well, you'll have to un-map them one-by-one.
  6. This is probably a once off thing, but the UI doesn't allow you to execute this right away. You have to give the bulk copy a name and save it out to a bulk copy task.
  7. Then you can execute this by right clicking the task on the Tasks tree and executing it.
  8. Grab a coffee/tea while the bulk copy does its thing

  Now depending on how many files you are trying to load in, step 4 and 5 of this process are the most tedious step of the lot whose tediousness scales up with the number of files you're trying to load in.
  In the upcoming release, we're going to streamline this process by giving you a new UI do specify multiple copy tasks at once!
  
  
  Here's a gif of how long it takes to set up a full bulk copy of multiple SHP files into SQL Server.
  
  
  Could you imagine how long this would've taken in current FDO Toolbox? What's more, you don't even have to save the task to execute it. There's now an Execute button in the bulk copy editor UI for you to execute the bulk copy in-place!
  
  
  Scenario: I want a quick peek at the data
  I use SQL Server Management Studio a lot when working with SQL Server databases directly and one of the features I take for granted in this tool is the ability to quickly preview the first 1000 results of any table I select.
  I yearned for such a feature when going back to FDO Toolbox to take a quick peek at some spatial data and being annoyance at the absence of such a feature. So in the upcoming release, I've implemented such a feature!
  
  
  Scenario: Copying data with non-standard/foreign projections into SQL Server
  A common dataset I use when testing out FDO Toolbox or MapGuide is the Parcels.shp that comes with the SHP FDO Provider test suite.
  So imagine my surprise that when I set up a bulk copy to load this file into a blank SQL Server db, that the process completely fails!
  
  
  The actual logged error in question being:
  
  
  This error is thrown by the SQL Server provider and reveals a strange corner case with blank SQL Server databases. The key thing to note was that this database was created outside of FDO Toolbox (I created it through SQL Server Management Studio). When you create a fresh database in SQL Server through FDO Toolbox like so:
  
  You don't actually get a fully blank database in SQL Server, if you look at it through alternate tools you'll see this little table called f_scinfo
  
  What is this table? This table is used to store FDO spatial context information about geometry columns/properties. So when we start the bulk copy into this blank database, the FDO provider creates this table automatically, which leads to the error at hand.
  The error is due to the fact that when creating a spatial context in SQL Server, it tries to resolve a matching entry in the sys.spatial_reference_systems system table. Failing that, it tries to do an in-memory lookup of its local copy of ExtendedCoordSys.txt if you have one. If no matching entry is found through either means, it throws the aforementioned error. The Parcels.shp file is actually in the (LL/EPSG:4326) projection, but the name and WKT presented from the SHP file does not resolve to a coordinate system that SQL Server knows about.
  So with the problem identified, the upcoming release presents the solution. For created copy tasks, there is a new option node available.
  
  That when right-clicked presents an option to show a new spatial context override UI where you can replace the CS name/wkt from the source with a name/wkt that is known to SQL Server. When bulk copy creates its spatial contexts, it will use the name/wkt from the override settings if specified.
  
  If you've ever used the Coordinate System Override feature in MapGuide Feature Sources, this is effectively the same concept but used for bulk copying in FDO Toolbox: A way to "fix" problematic coordinate systems in the source.
  
  Alternatively, if you don't want to create a spatial context from source during the bulk copy and want to reuse an existing spatial context already on the target connection instead, we now provide that option as well.
  
  
  Right-clicking this node presents a list of available target spatial contexts to map to.
  Scenario: Copying data out of Oracle (through the King.Oracle provider)
  If you have an Oracle database, then you are probably familiar with the quirks that come with reading data out of it through the King.Oracle FDO provider.

  1. The weird tilde notation for feature class names (unless you set up the KingFdoClass table)
  2. Spatial contexts always starting with "OracleSrid"

  If you ever want to bulk copy data out of Oracle through this provider, these quirks live on in the data stores you've copied to, which may complicate any application code you have that may be working against this data store as the king oracle-isms have seeped into the data store.
  In the upcoming release, through the multiple copy task UI, you now have the ability to specify the name of the target feature class if creating one. No more tildes!
  
  Similarly, on the new spatial context override UI already shown, you may nominate a new name for the spatial context to be created. No more "OracleSrid" either!
  In closing
  This is not the full summary of what will be coming in the upcoming 1.4 release, but these features and improvements are the ones I believe will have the most impact in making the things you currently use FDO Toolbox for that much easier.
• 11:00

  CARTO Blog: Mastercard Geographic Insights updated with new features & metrics

  sur Planet OSGeo
  Mastercard Geographic Insights, (Geo Insights) has been helping business leaders across industries to make more informed decisions and better understand their customers. A ...
• 2:00

  SourcePole: GeoZero, a zero-copy API for processing geospatial data

  sur Planet OSGeo

  Since a few years I get more and more obsessed about the performance of my daily work tools. It took a long time to realize how slow today's software is, compared to similar software I was working with 20 or even 30 years ago. Software bloat compensating any hardware performance improvements seems to belong to the laws of nature.

• 24 May 2020
• 15:30

  Jackie Ng: Announcing: vscode-map-preview 0.5.2

  sur Planet OSGeo
  This release future-proofs the extension by using the recommended webview APIs and adding a CSP to the generated preview HTML used to display the map.
  
  In the grand scheme, everything should be working as before.
  
  Special thanks to Matt Bierner of the VSCode team for the heads up on this issue.
• 14:35

  Free and Open Source GIS Ramblings: Movement data in GIS #30: synchronized trajectory animations with QGIS temporal controller

  sur Planet OSGeo

  QGIS Temporal Controller is a powerful successor of TimeManager. Temporal Controller is a new core feature of the current development version and will be shipped with the 3.14 release. This post demonstrates two key advantages of this new temporal support:

  1. Expression support for defining start and end timestamps
  2. Integration into the PyQGIS API

  These features come in very handy in many use cases. For example, they make it much easier to create animations from folders full of GPS tracks since the files can now be loaded and configured automatically:

  

  Script & Temporal Controller in action (click for full resolution)

  All tracks start at the same location but at different times. (Kudos for Andrew Fletcher for recordings these tracks and sharing them with me!) To create an animation that shows all tracks start simultaneously, we need to synchronize them. This synchronization can be achieved on-the-fly by subtracting the start time from all track timestamps using an expression:

  directory = "E:/Google Drive/QGIS_Course/05_TimeManager/Example_Dayrides/"
  
  def load_and_configure(path):
      path = os.path.join(directory, filename)
      uri = 'file:///' + path + "?type=csv&escape=&useHeader=No&detectTypes=yes"
      uri = uri + "&crs=EPSG:4326&xField=field_3&yField=field_2"
      vlayer = QgsVectorLayer(uri, filename, "delimitedtext")
      QgsProject.instance().addMapLayer(vlayer)
  
      mode = QgsVectorLayerTemporalProperties.ModeFeatureDateTimeStartAndEndFromExpressions
      expression = """to_datetime(field_1) -
      make_interval(seconds:=minimum(epoch(to_datetime("field_1")))/1000)
      """
  
      tprops = vlayer.temporalProperties()
      tprops.setStartExpression(expression)
      tprops.setEndExpression(expression) # optional
      tprops.setMode(mode)
      tprops.setIsActive(True)
  
  for filename in os.listdir(directory):
      if filename.endswith(".csv"):
          load_and_configure(filename)
  

  The above script loads all CSV files from the given directory (field_1 is the timestamp, field_2 is y, and field_3 is x), enables sets the start and end expression as well as the corresponding temporal control mode and finally activates temporal rendering. The resulting config can be verified in the layer properties dialog:

  

  To adapt this script to other datasets, it’s sufficient to change the file directory and revisit the layer uri definition as well as the field names referenced in the expression.

  This post is part of a series. Read more about movement data in GIS.

• 21 May 2020
• 20:57

  Free and Open Source GIS Ramblings: Spatial on air: talking Python on the MapScaping Podcast

  sur Planet OSGeo

  Podcasts have become huge. I’m an avid listener of podcasts myself. I particularly enjoy formats that take the time to talk about unconventional topics in detail.

  My first podcast experience was on the QGIS podcast hosted by Tim Sutton in 2014. Unfortunately, it seems like the podcast episodes are not online anymore.

  Recently, I had the pleasure to join the MapScaping Podcast by Daniel O’Donohue to talk about Python for Geospatial: 

  Other guests Daniel has already interviewed include:

  • Kurt Menke talking first about QGIS and in a second episode on QField and Input (data collection apps based on QGIS) and
  • Paul Ramsey on Vector Tiles from PostGIS

  Another geospatial podcast I really enjoy is The Mappyist Hour by Silas and Todd. Unfortunately, it’s a bit silent there now but it’s definitely worth to listen into their episode archive. One of my favorites is Episode 9 where Linda Stevens (Hecht) discusses her career at ESRI, the future of GIS, and the role of Open Source Spatial in that future:

  If you listen to and want to recommend other spatial podcasts, please share them in the comments!

• 13:34

  Andrea Antonello: SMASH 1.2.0 is out... and it is packed with goodies!

  sur Planet OSGeo
  SMASH 1.2.0 is out in the google and apple stores and it comes packed with a whole set of new features. Not even sure where to start. Here we go...
  Welcome and Project ViewWe never had it, but it was time.When SMASH starts up it need to check some permissions, layers, data, forms and much more. Now you will be notified and see something is going on:
  
  After that the projects view comes. Make your choice, new/old or fast choice between recent?
  
  
  
  Data formats

  Some new formats are available now.
  Raster files in World image format

  SMASH now supports loading of raster imagery in the tiff/jpg/png + worldfile (tfw/jgw/pgw) + projection file.
  
  So once you load the rasters in the layer view, it will check the projection.
  
  In this case we have 3 different projections and while 4326 and 3857 are supported. So the first time this happens you will need to tap on the layer to try to download the proj definition for the projection.If you are lucky enough, the epsg was recognized and the definition downloaded. Now the dataset is loaded. Mind that while on vector data a re-projection is really performed, in case of raster images, the images is just warped using the boundaries. So this could lead to some unwanted distortions. So always bet to use 4326 data for rasters.
  The result is quite nice and transparency can be applied where needed.
  Here below a jpg loaded in 32632:
  
  
   and a tiff loaded in 3857:
  
  
  Small confession: this is the reason there has been also a version 1.1.0. We found out there were some issues with the projection of the raster imagery files and decided to fix them an release right away.
  Shapefile read supportSMASH now supports shapefiles ( outch, who would want them?). 
  
  
  And they are actually styled with SLD:
  
  And can be queried:
  
  They are and will always be (unless someone pays tons of money) read-only layers. All the editing will be moved to geopackage in future.
  
  WMS/TMS supportTMS has already been supported, now WMS is also here. And there is a beautiful catalog to hold them:
  
  
  
  
  
  The maps are actually live maps which help to see if a service works even before adding it.
  
  WMS looks the same and both can export and import the definitions:
  
  
  To add a new definition, since that is a rude thing to do on the device, we tried to make it as comfortable as possible:
  
  
  Layer managementLayers can now be dragged to reorder them and they can be removed with a right-to-left swipe.
  If they support zooming to or styling, it is found in a right-to-left swipe.
  
  
  Note that this is now harmonized in all list views with zoom and style.
  
  Notes:
  
  
  and logs:
  
  
  
  
  GPS  The biggest new is for sure the fact that SMASH now supports background logging, i.e. logging with the screen off. No image here, but you know what that means.
  We also added to the settings view:
  
  
  a GPS live view to be able to play with the settings and see what happens:
  
  
  As you can see the rose of incoming points is visible in the background, so give an idea of what is going on.
  
  
  
  Last but not least, it is possible to activate a counter for GPS points (all vs filtered) to be seen on the main view in the GPS icon:
  
  
  Other notable things Debug viewWe added a debug view, accessible from the settings:
  
  
  Better drawers layout The left and right drawer and the actionbar have been reviewed.
  The right drawer is now accessible by icon and contains all the tools, in expandable sumenus.
  
  
   As a result the left drawer is now more clean and project related:
  
  
  And an online help has been added, which is never bad :-)
  
  The GPS info panel has been cleaned up a bit and one can copy each coordinate to the clipboard:
  
  
  
  
   Notes have labelsWe added labels also to project notes:
  
  
  Grid A nice grid plugin has been added to flutter map, so we added it here also:
  
    Reprojection support As mentioned in the raster imagery part, support has been added for projections. If a projection is not known, it will be required to download its definition. After that vector data will be reprojected properly. This part is still a bit experimental. But it already looks good. Small things

  • sharing the position has now the Openstreetmap url
  • fixes have been done in the forms engine

  
   Guess that is all! Enjoy!
  
  PS: as usual the user manual is lagging behind a version. Is there some gentle soul out there that would be willing to help?
  
  
• 12:28

  GeoServer Team: GeoServer 2.16.3 released

  sur Planet OSGeo

  We are pleased to announce the release of GeoServer 2.16.3 with downloads (war|zip), HTML documentation and extensions.

  This is a stable release recommended for production systems.

  Improvements and Fixes

  This release includes a number of improvements, including:

  • New “clip” vendor option in WMS GetMap.
  • The SLD generation service can now create classified styles with per class percentages of occupation.
  • Various WMS cascading improvements, including:
    • Options to configure min/max scale denominator for cascaded WMS layers, as well as to limit the cascading requests to the declared BBOX.
    • Options to configure formats and styles used in cascading.
    • GetLegendGraphic now works with external WMS layers too.
  • The configuration UI got improved too, in particular:
    • It’s possible to show dates of creation and last modification in the resource lists (layers, stores, and so on).
    • Search filters in lists are now remembered when moving across pages.
    • Data level security can be edited in a new dedicated tab at the single resource level (e.g., while in the layer page).
  • Mass truncation requests added to GWC, and the tile layer page lists layers faster
  • Monitoring can now skip post-processors, and can log the time needed to render each layer in a multi-layer request.
  • WFS supports per workspace stored queries.
  • The SQL Server now ships with the latest open source JDBC driver by Microsoft, no longer need to fetch it separately.
  • The download process (community module) can now return image mosaic single granules in their native CRS, when requesting a single one out of a heterogeneous CRS mosaic.
  • Layer level CQL filter is now respected by complex feature layers too.

  Fixes included in this release:

  • WMS legend decorations got some attention, improving their size management
  • Improved support for map wrapping while using rendering transformations generating raster data (raster to raster or vector to raster ones)
  • And various others!

  For more information check the 2.16.3 release notes.

  Community Updates

  For developers building from source, our community modules are a great place to collaborate on functionality and improvements.

  • The templated JSON-LD output format, supporting both simple and complex features, has been backported to 2.16.x. We are grateful for the sponsorship of the French geological survey – BRGM and the French environmental information systems research center – INSIDE, which made its development possible.

  About GeoServer 2.16

  Features, presentations and reference material on the 2.16 series:

  • State of GeoServer 2.16 (video|slides)
  • GeoServer Feature Frenzy 2019 (video|slides)
  • New SLDService extension using data classification for style generation
  • New authentication key extension available
  • Server status page now includes system status details
  • GDAL 2.x binaries are now used for GDAL image formats along with OGR WFS output and WPS output formats
  • Release Notes (2.16.2 | 2.16.1|2.16.0|2.16-RC1)

• 11:41

  GeoTools Team: GeoTools 22.3 released

  sur Planet OSGeo
  The GeoTools team is pleased to announce the release of GeoTools 22.3: geotools-22.3-bin.zip geotools-22.3-doc.zip geotools-22.3-userguide.zip geotools-22.3-project.zip maven repository GeoTools 22.3 is a stable release and is recommended for new development and production systems. This release is made in conjunction with GeoServer 2.16.3. Fixes and Improvements Improvements: Maven
• 11:00

  CARTO Blog: Using Spatial Analysis to Measure UK Gentrification

  sur Planet OSGeo
  Deepening social inequalities have remained a constant in our contemporary urban landscapes. Particularly within global cities like London, the disparities have become incr...
• 8:33

  gvSIG Team: Conferencia online: gvSIG, innovación tecnológica y social para la gestión del territorio

  sur Planet OSGeo

  

  La Red Nacional de Estudiantes de Ingeniería Topográfica, Geodésica y Geomática AC de México organiza la conferencia online “gvSIG, innovación tecnológica y social para la gestión del territorio” que se celebrará hoy, 21 de mayo de 2020, a las 21:00 de España; 14:00 de México y Colombia; 15:00 Chile;…

  El enlace para asistir es: [https:]]

• 20 May 2020
• 19:26

  GIScussions: Maps vs Cartography

  sur Planet OSGeo

  This week a minor spat broke out on the twittersphere, so what’s new you ask?

  maybe if you really want to encourage people to make maps… tweeting a chart with 6x "don't make a map", 4x "don't do it", 3x "don't share your map", 1x "just stop now" and 1x "PS buy my book" is not the most empowering way to do it [https:]]

  — Anonymaps (@Anonymaps) May 19, 2020

  The chart in question is Ken Field’s somewhat ironic decision tree on whether one should make a map

  

  I need to emphasise that this is a joke that makes a serious point (IMHO) and the promotion of Ken’s excellent book Cartography. is the punchline.

  This prompted Amber Bosse, who describes herself as a critical cartographer, to reference Ken and other “critical cartographers” in her talk at the Atlas in a Day event. It seems to me that her key messages are summed up in these quotes

  “Cartography has a PR problem”

  “Caring about the look of the map and not giving much attention to what the map does in the world”

  “A certain section of twitter uses #cartofail to publicly call out those who have made supposedly bad maps”

  She calls out the president of the International Cartographic Association for saying

  “the number of maps created today can be rather overwhelming, but their communicative quality is not always convincing … just because one can more easily map today, this does not mean one should”

  Sound advice that I cannot but agree with.

  Amber then sets out her own position which is very centred around the way making a map can be empowering for minority groups and the oppressed. She suggest that it is important to consider “How people who the map represents feel about the map” rather than whether the map complies with established cartographic design standards.

  I don’t think cartographers who are critical of others’ efforts are necessarily trying to enforce anything, I think they are questioning whether the map communicates effectively to its intended audience.

  Amber goes on to set out her own criteria for judging a map.

  “Does this map represent my story in a way that resonates with me? Does this capture our truth in ways that we own?”

  “Love does not just represent the experience of colonisation and white supremacy in ways that the patriarchy considers beautiful”

  This is a highly producer centric view of mapmaking, what matters is how the mapmaker feels about their map and whether they feel empowered. She concludes by saying

  “We don’t need a handful of people mapping perfectly, we need millions of people doing it imperfectly”

  I find it interesting that Amber switches from talking about cartography to talking about mapping, because I think there is a difference.

  Millions of people can make a map (the tools are widely available and in many cases free) and with a basic level of competence they can use their maps to explore data and possibly to get some insight into that data. Of course you can make mistakes, confirm your own biases and get things wrong but that may not matter if you are making the map for yourself. It’s quite similar to downloading a table of data and making a chart or an infographic, if you don’t understand statistics you could make some quite glaring errors. Over time, with a little study, you will start to make better maps. If you share your map with colleagues they may well point out flaws in your map or suggest ways to improve it.

  If Amber’s criteria for a “good map” are meant for people making a map for their own consumption then I guess that is ok, where I would disagree is when those maps get published to a wider audience. When you publish a map I think you do need to be aware that the viewers may not have the same level of knowledge about the content or domain that you have. We know that the way people perceive colours and shapes, let alone understand and interpret the statistical calculations behind a map, will impact the information and understanding that they take from the map.

  Those cartographic design principles that Amber rails against represent the accumulated wisdom and research of many map makers, not all of whom are patriarchal oppressors. Of course you can choose to ignore them but others are entitled to question whether those choices are effective.

• 11:00

  CARTO Blog: New Location Data Available for COVID-19 Recovery Analysis

  sur Planet OSGeo
  More than two months have passed since the World Health Organization declared the outbreak of COVID-19 a worldwide pandemic. Governments from all over the world have had to...
• 19 May 2020
• 11:00

  CARTO Blog: Workplace Social Distancing with Indoor Mapping Software

  sur Planet OSGeo
  As many of us start to slowly emerge from weeks and months of lockdown, many large companies are working out how we return to offices, factories, restaurants and large comm...
• 18 May 2020
• 14:05

  Andrea Antonello: Geopaparazzi vs. ESRI Collector - a user story

  sur Planet OSGeo
  Andrew Mitchell appeared a couple of years ago in the geopaparazzi community and soon marked a differenece. It is one of those users that put effort in making the tool they use better. He soon started to open issues about usability... many issues. And those many issues made me crazy, since he was right and most of the time I had to react with improvements and fixes, but also contributed to a better geopaparazzi.
  
  A couple of days ago he shared his experience on the field with Geopaparazzi and with ESRI Collector. Needless to say that I loved the read.
  
  Pasting the whole content here as it was sent to the geopaparazzi mailinglist:
  
  
  
  
  
  ESRI Collector vs Geopaparazzi
  Background Information
  Most environmental consulting firms use Collector. It is the defacto industry standard for GIS data collection. However, I have on most occasions had serious issues with it and now use Geopaparazzi. The following table provides a comparison between the two systems based on slightly more that a years of practice with both systems. In most cases, I would start with Collector and then switch over to Geoparazzi when Collector experienced an issue that was hard to work around. That said, others found Collector to be fine and stable. It could be that the iPhone version is better than the Android version. Even so, many limitations would remain. This review concentrated on issues that have caused grief in the field, rather than what works well.
  Geopaparazzi has fewer issues, but some occasionally arise, particularly teething issues with the new version 6. However, any serious issues have rapidly been resolved. At the time of writing Geopaparazzi 6.0.3 was being compared with an up-to-date, professionally managed ESRI ecosystem. 
  
  

  Collector	Geopaparazzi
  Primarily an online data collection system with an off-line capability	Began as an off-line system but has ability to utilise some cloud services for importing base data and form designs. Does not appear to have the ability to upload new or updated data to a live GIS system.
  Projects are created in ArcGIS Pro then delivered to an Android device by cellular network - downloads can be painfully slow - it is also confusing when you open a downloaded project and are outside the project area as the imagery for your current location will be shown, not the imagery for the defined project area.	Project usually created on the fly on the device by starting a new project. - loading base maps or spatialite data via USB is very simple and quick. - it is simple to centre the view on a base map.
  Background Images
  Background images are limited to those hosted by ESRI online. Imagery that can be displayed in ArcGIS Pro is not able to be (we can’t figure out how) be displayed as a background image on the mobile device. This prevents recent, high quality imagery such as nearmap from being available in the field. Spatial misalignments of background imagery from ESRI cannot be corrected. Potentially imagery is not preserved when Collector is used in online mode when the device screen is turned off. More work is	Background images can be downloaded via cellular network on the fly or you can manually pre-load the area of interest by dragging the screen over the area of interest. This method is very good for linear areas such as under an aircraft flight path. Background imagery persists between sessions. Background images can also be created in a GIS as an mbtiles file. If the original image is a from a web server such as Open Street Map, then each image level will have a different amount of detail. This is very good for navigation to site. Zoom dependent visibility can also be used in a GIS to show

  needed to test this but it seems that the same tiles are downloaded each time they are needed. If the internet is congested, background imagery will display slowly or a network error will be reported. It is possible to create tile package files (ptk files) which contain background imagery for Collector, however an add-in is required for ArcMap. These images can then be copied into the device over a USB connection. This capability has not been tried by us.	or hide project layers and this information will be burned into the mbtiles when they are created. Any imagery that can be displayed in a GIS can be converted to mbtiles. I often use a hillshade blended with an aerial photo. If the webserver imagery is not located correctly, it is possible to create mbtiles with the imagery shifted to its correct location.
  Navigation
  North up display	Heads up display or north up display – user selects
  Data collection
  Both are similar. Both open the keyboard for pick list entries. This is a pain as the keyboard takes up space that could be used to show more picklist entries. Drawing lines and polygon features in collector is very easy and very refined
  Tracks
  No tracks by default, although there is a workaround.	Records tracks when track logging is activated. Basis of track point recording can be adjusted in settings
  Data management
  In online mode, no data management is necessary. In off-line mode, data has to be synced. Sometimes there are issues with syncing. Uploaded data is available to most users via Arc Maps Online and to the GIS team via ArcGIS Pro. Retrieving the data for third party applications requires extra steps such as exporting the data to a folder that is reachable by the applications. The data cannot just be copied out of ArcMaps online. The ability to select rows is disabled. Copying the feature database from the server to a local machine also did	There is some cloud support, but I have not used it. It requires setting up a Postgres Server and some configuration. I just copy the gpap file from the device and paste it into a folder on my windows PC. A micro USB cable is required for the physical connection. Prior to copying the gpap file, I may choose to export the photos and gps tracks, which are stored within the gpap database. Managing this data requires some procedures and an organised filing system but the data can be opened and processed by any suitable application.

  not make the data available. The database claims to be empty on local machine but has data on the source machine.
  Viewing form data
  Form data can be viewed by clicking on points on the map in the field or by clicking on points displayed in ArcOnline. A mini- web page is opened showing the collected information.	Data is collected in JSON format, with the JSON form specification also saved in each record. It is a bit like pdf forms, where the data is saved inside the pdf document and has to be extracted later. This would be a pain if you do not run a system that can do this (gv-SIG) and are not able to write your own. The great advantage of this approach is that form design can be evolved in the field. Data already collected is totally unaffected. Extracted data can be converted to a GIS data file such as a shapefile, just added to a database table or rendered as html or kml.
  Usability
  In Collector, it is easy to press the back button too many times and to quit the project and even the application by accident. Issues can occur if a data point is right on the edge of the defined project area. It is not-possible/very difficult as Collector resists the edge of the project area being dragged into the centre of the screen. This is an issue if you have to approach the target via areas that are outside the project area. Symbol size in our projects is very small, usually round dots. If the colours used are similar, it is hard to tell what the colour is. Also if the coloured dot is used on a strongly coloured background, our eyes will colour balance and the perceived colour will shift. Screens are prone to clutter. If contour lines are used, then seeing the data can be like looking through spiders web.	In Geopaparazzi, accidentally quiting the current project or the application is very unlikely. Quiting has to be deliberate. Screen position is not limited to the project area. Symbol size, colour and shape is under user control. Screen clutter is manageable. Layers that are only used for navigation can be burned into the background layer.
  Multi-user/multi-session experience
  This is Collectors’ strongest point. When a	Geopaparazzi is not well suited to live

  project is synced, data collected or updated by other people becomes visible. For the field operator, responsibility for managing the data ends as soon as the data is synced. If the data fails to sync, and this can happen, then the data is lost (iPads and Collector!). ArcPro is required to make Collector projects so GIS support is required.

  updates in the field as far as I know. It is possible to create a new project everyday and to import data from that project into a GIS. I have written an application that can append data from incoming gpap files into a master database, however as far as I know, the Geopaparazzi ecosystem otherwise lacks this capability. Being able to start a new project anywhere at anytime provide great flexibility.

• 11:00

  CARTO Blog: Why Precision Matters in Indoor Mapping Software

  sur Planet OSGeo
  Pre COVID-19, Indoor Mapping was already one of the highest growth location analytics use cases, with hospitals, shopping malls & airports all investing in technology t...
• 6:09

  Narcélio de Sá: TecnoloGEO 08 – OpenStreetMap: Um mapa para todos mapearem.

  sur Planet OSGeo

  Enclosure: [download]

  Neste podcast: O TecnoloGEO 08 traz até você um bate-papo com Murilo Cardoso, Narcélio de Sá e Wille Marcel, onde iremos conversar sobre o OpenStreetMap esse grandioso projeto que cria e distribui dados geográficos livres para todo o mundo.

  O OpenStreetMap é uma ferramenta para criar e compartilhar informação num mapa. Qualquer um pode contribuir para o OSM, e milhares de pessoas fazem isso todos os dias. Tem interesse em contribuir para o OSM? Seguindo este guia, rapidamente você será capaz de começar a fazer mapas digitais com o OpenStreetMap.

  O OpenStreetMap® é disponibilizado em dados abertos, sob a licença Open Data Commons Open Database License (ODbL) pela Fundação OpenStreetMap (OSMF). Nós que fazemos o TecnoloGEO agradecemos o trabalho desenvolvido por todos os © contribuidores do OpenStreetMap.

  Aperte o ? para começar o TecnoloGEO #08

  Podcast: Download do TecnoloGEO 08
  

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 08: Livros:

  • Great City Maps: A Historical Journey Through Maps, Plans, and Paintings – Smithsonian Institution
  • Great Maps – Jerry Brotton
  • A Catedral e o Bazar – Eric Steven Raymond
  • Exploring From Home: A map coloring book – Mapbox
  • Geoinformação em urbanismo: cidade real x cidade virtual – Cláudia Maria de Almeida, Gilberto Câmara
  • A Grande Mudança – Nicholas Carr

  Filmes

  • Cidades de Papel (2015) – Jake Schreier
  • Lion – A Longa Estrada Para Casa (2016) – Garth Davis

  Vídeos

  • Playlist com vídeos sobre OSM
  • Vox Borders
  • Ação dos voluntários do OSM no Haiti
  • Vídeo de celebração dos 10 anos do OSM
  • OpenStreetMap: The map that saves lives | CNBC International

  Games

  • SimCity
  • Cities: Skylines

  Sugestões de links:

  • OSMCha (OpenStreetMap Changeset Analyzer)
  • Referências iniciais sobre o OSM
  • Guia para mapeamento no OSM
  • Guia para mapeamento Humanitário no OSM
  • Quadro Cidade (1984) de Claudio Tozzi
  • Grupo do TecnoloGEO no Telegram

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 08 – OpenStreetMap: Um mapa para todos mapearem. appeared first on Narcélio de Sá.

  
• 2:00

  GeoNode: GeoNode 3.0 and 2.10.4 are out!

  sur Planet OSGeo
  GeoNode 3.0 and 2.10.4 are out!
  

  This Post is gonna kick things off by summarizing the latest releases 2.10.4 and GeoNode 3.

  Yeah, you understood correctly, there is a new major version out now. However, let's start at the beginning.
  
  With the life of Python 2.7 ending in 2020 — it is a matter of course: GeoNode needing an overhaul for python 3 compatibilities.
  
  To stick with clarity and precision, the development team has decided to give the new child a name as major version: GeoNode 3 was born!

  Alongside a lot of helping hands inside our community, two major contributors took the challenge in doing the main work on the Code Base of GeoNode 3. Namly Geosolutions (Italy) and Catalyst (New Zealand). The ladder being a relatively new contributor — concerning our community, and we'd love to see more contributions!

  Both releases fix several minor, major and security issues. Further GeoNode 3 brings several new features you should not miss!

  Features GeoNode 3

  • Python upgrade 3.7+
  • Django upgrade 2.2.12
  • GeoServer upgrade 2.16.2
  • Moved Documentation to dedicated repository and build
  • Integration of MapStore as new map viewer/composer
  • Drop of GeoExt, with MapStore client as the new official one
  • Local analytics/monitoring extension
  • Support for centralized analytics dashboard
  • Improvements">[https:] to frontend for low-bandwidth environments
  • B/R refactoringwith new features that make it able to be used for syncing instances
  • Read-Only and Mantenance modes
  • GeoLimits
  • Added "DOI" field to base metadata
  • Extend resource search api with abstract and purpose fields
  • Improved Remote Services and Metadata Fetch
  • Improved Message Inbox and Messaging & Norification System
  • Improved Thumbnails and Thumbnails Upload / edit before posting
  • Improved Managemend Command

  To rule out any misunderstandings:
  Whenever you see GeoNode 2.x make sure your virtual environment uses Python 2.7. In case you see a shining 3 at the end of GeoNode — you have to use Python 3.7.

  For all other things which have been added, do not miss to read — the release notes for GeoNode 2.10.4 and GeoNode 3!
  
  Last but not least in case you're planning a manual install of version 3, be sure to visit the updated docs. You can report any issues or feature requests at our Issue Tracker @ Github.
  
  Stay healthy & happy GeoNod'ing!

  This Website is licensed CC by SA 2012. - GeoNode Contributors. Designed by Spatial Dev

• 17 May 2020
• 20:01

  Martin Davis: JTS Overlay - the Next Generation

  sur Planet OSGeo
  In the JTS Topology Suite, Overlay is the general term used for the binary set-theoretic operations intersection, union, difference and symmetric difference.  These operations accept two geometry inputs and construct a geometry representing the operation result.  Along with spatial predicates and buffer they are the most important functions in the JTS API.
  
  Intersection of MultiPolygons
  Overlay operations are used in many kinds of spatial processes. Any system aspiring to provide full-featured geometry processing simply has to provide overlay operations.  In fact, many geometry libraries exist solely to provide implementations of overlay. Notable libraries include the ESRI Java API, Clipper and wagyu.  Some of these provide overlay only for polygons, which is the most difficult case to compute.
  
  Overlay in JTS 
  
  The JTS overlay algorithm supports the full OGC SFS geometry model, allowing any combination of polygons, lines and points as input.  In addition, JTS provides an explicit precision model, to allow constraining output to a desired precision.  The overlay algorithm is also available in C++ in GEOS.  There it provides overlay operations in numerous systems, including PostGIS, QGIS, Shapely, and r-sf.  This codebase has had an long lifespan; it was developed back in 2001 for the very first release of JTS, and while there have been improvements over the years the core of the design has remained unchanged.
  
  However, there are some long-standing issues with JTS overlay.  The most serious one is that in spite of much valiant effort over the years, overlay is not fully robust.  The constructive nature of overlay operations makes them particularly susceptible to the robustness issues which are notorious in geometric algorithms using floating-point numerics.  It can happen that running an overlay operation on seemingly innocuous, valid inputs results in the dreaded TopologyException being thrown.  There is a steady trickle of issue reports about this in JTS, and even more for GEOS (such as here, here and here...).
  
  Another issue is that the codebase is complex, and thus hard to debug and modify. Partly this is because of the diversity of inputs and the explicit precision model.  To support this the JTS overlay algorithm has a rich and detailed semantics.  But some of the complexity is due to the original design of the code. This makes it difficult to incorporate new ideas for improvements in performance and robustness.
  
  Next Generation Overlay
  
  So for many years it's been on my mind that JTS overlay needs a thorough overhaul. I chipped away at the problem over time, but it was clear that it was going to be a major effort.  Now, thanks to the support of my employer Crunchy Data, I've at last been able to focus on a complete rewrite of the JTS overlay module.  It's called OverlayNG.
  
  The basic algorithm remains the same:
  

  1. Extract the input linework, and node it together
  2. Build a topology graph from the noded linework
  3. Compute a full topological labelling of the graph
  4. Extract the resultant polygons, lines and points from the graph

  This algorithm is time-tested and is able to handle the complexities of multiple geometry types and topology collapse. The new codebase benefits from 20 years of experience to become simpler and more modular, with increased testability, and potential for reuse.
  OverlayNG has the following improvements:
  

  • A snap-rounding noder is available to make overlay fully robust.  This eliminates the possibility of TopologyExceptions (when an appropriate precision model is used).

  Intersection operation with Snap-rounding and Topology Collapse removal

  • Snap-rounding allows full support for specifying the output precision model.  The precision model can be specified independently for each overlay call, which is more flexible and easier to use.  The use of snap-rounding also provides fully valid precision reduction for geometries.  This makes it feasible for the first time to fully operate in a fixed-precision regime.

  Precision Reduction turned all the way up to 11

  • Significant performance optimizations are included (notably, one which makes polygon intersection much faster in many cases)

  Intersection of a MultiPolygon with a grid (7x faster with OverlayNG)

  • Pluggable noding allows providing different noding strategies.  One use is to run OverlayNG with the original floating-point noder, which is faster than snap-rounding (but of course has the robustness issues noted above).  Another is to use a special-purpose noder to provide very fast polygonal coverage union.

  Union of a polygonal coverage (10x faster with OverlayNG)

  • A modular and cleaner codebase allows easier testability, maintenance, enhancement and reuse.  A winged-edge graph model is used for the topology graph. This is simpler and less memory intensive.
  • The rebuild gives an opportunity to make some semantic improvements: 
  • Empty results are returned as empty atomic geometries of appropriate type, rather than awkward-to-handle empty GeometryCollections
  • Linear output is merged node-to-node.  This gives union a more natural and useful  semantic

  A benefit of the new codebase is that it is easier to enhance and extend.  For example, it should be straightforward to finally provide a SplitPolygon function for JTS.  Another potential extension is overlay for Polygonal Coverages.
  Code that is so widely used needs to be thoroughly tested against real-world workloads.  Initially OverlayNG will be released as a separate API in JTS.  This allows it to be used along with the original overlay.  It can be used as a fallback for cases which fail in the original overlay process.  Once the new code has been proved out in real world use, it is likely to become the standard overlay code path. Also, the code will be ported to GEOS soon, where we're hoping it will provide significant benefits to the many systems that use GEOS.
  
  I'll be posting more articles about aspects of OverlayNG soon. The code is almost ready to release, after some final testing. In the meantime, the pre-release code is available in a Git branch. It would be great to get as much beta-testing as possible before final release, so try it out and log some feedback!
  
  
  
  
  
  
  
• 14 May 2020
• 11:00

  CARTO Blog: HIPAA Compliance in Geospatial Healthcare Analytics

  sur Planet OSGeo
  Location Intelligence and Spatial Analysis is more and more frequently being leveraged by companies and organizations working in healthcare. In fact the healthcare industry...
• 13 May 2020
• 21:23

  QGIS Blog: QGIS Server and OGC API Features

  sur Planet OSGeo

  Based on text and information from Paul Blottiere and Alessandro Pasotti (both QCooperative)

  QGIS Server implements a number of OGC services, such as WMS, WFS, WCS or WMTS and extends these services where useful. Thanks to the efforts of a number of QGIS Server developers and companies, QGIS 3.10 (and 3.4 before) had been certified by the OGC for the WMS 1.3.0 service, and is also a WMS reference implementation.

  

  Last year in 2019, a new protocol has been developed and named OGC API Features (commonly known as WFS3). With the purpose of having an up-to-date QGIS Server, both OSGeo and QGIS.ORG have dedicated funds to work on the implementation of this brand-new service: but we wanted to do it right, so the ambition was also to reach the OGC certification!

  This new protocol with REST interfaces gets rid of the XML specification to use the OpenAPI standard as well as the JSON open format instead. In other words, it’s not just another protocol to support, but a whole package of changes and fresh mechanisms to work on. It was quite a challenge!

  QGIS core developers of QCooperative were remotely participating in OGC sprints to closely monitor the development of the new OGC API Features protocol. Hence, we started its implementation and a fully operational version landed in QGIS Server 3.10.

  Implementation and features

  As a reminder, the WFS protocol allows to query, retrieve and manipulate vector features, unlike the WMS format which provides raster outputs. OGC API Features is the natural continuity and consistently provides basic mechanisms to retrieve features and corresponding information in a specific area (the famous GetFeatureInfo request in WFS 1.X).

  In addition, QGIS Server also provides transactions for the OGC API Features protocol. This means basically that we can update, insert or delete features in the underlying data. And of course, everything can be easily reached and configured through QGIS Desktop.

  Yet another interesting thing to note is also the full support of the date and time filtering. Nifty!

  And last, but not least, QGIS Server 3.10 provides a default HTML template with an embedded map to explore the data served by the server. There’s literally nothing to configure, it’s just there as soon as you work with the OGC API Features protocol :).

  

  OGC Certification

  Once the implementation was completed, we started to address the OGC certification goal. To avoid unwanted regressions along the way, we first added nightly tests by updating the dedicated QGIS repository for OGC tests. From that moment, HTML reports are available day-to-day to monitor development over time.

  Then, some bugfixes and backports later, we’re finally there: OGC tests are green on the development version, 3.12 and 3.10 releases. Yippee!

  

  Conclusion

  Now that everything is in order, the last step is to start the formal OGC certification process. From now on, the dedicated QGIS OGC Team takes care of further operations.

• 11:00

  CARTO Blog: London vs New York: Which city has the higher average building height?

  sur Planet OSGeo
  Many comparisons have been made between these two iconic cities, not least in terms of size, population and other factors like quality of life and the best pizza slice, but...
• 7:15

  QGIS Blog: Greetings from your new QGIS project Chair

  sur Planet OSGeo

  Dear community,

  First of all, I would like to thank Paolo for his work during the last two years as Chair and for the years before that, and years to come in his role as PSC member. I’m looking forward to keeping up the good work with him.

  Secondly, I would like to thank all the community voting members for all the great inputs during the discussion phase of the AGM and for the fantastic participation in the voting process where we had more than an 80% turnout.

  It is a pleasure to see that besides approving the more formal points (annual report, financial report, budget and auditors), the AGM approved all matters arising:

  • We now have two new honourable voting members: Harrissou Sant-anna and Nyall Dawson. Honourable members are specially designated voting members, whose position does not need to be affiliated with a country user group. Congratulations, and thank you, you are both such an inspiring example to our community!
  • Many QGIS users and contributors are geoscientists or geoinformatics specialists. As such, we need to act responsibly and serve as role models. Thanks to the approval of our new environmental policy, QGIS.ORG and the QGIS community committed ourselves to act responsibly regarding our actions and activities where it has any relevant influence on the environment. This will mainly affect our server infrastructure and our physical contributor meetings. The complete policy can be found in appendix 1 of our AGM minutes or on our website.

  Beyond thanking Paolo as outgoing chair, I’d especially like to thank Tim, Andreas, Anita and Jürgen for the great work they are doing in the PSC and in general the incredible drive they have in helping to make QGIS thrive. I’m sure that with the help of our new Vice-Chair Alessandro Pasotti we’ll be able to take QGIS to even greater heights. Welcome, Alessandro!

  Last, but definitely not least, I’d like to thank every single member of this amazing community for all your help documenting, coding, translating, testing, designing, teaching, supporting and in general spreading the QGIS love.

  I never thought, when I first started using QGIS 0.6 in 2005 that 15 years later I would be given the honour of becoming the official face of such an amazing heart.

  Have a great week, rock on QGIS!

  Marco Bernasocchi

  Incoming Chair of the QGIS.ORG Board

   

  For Reference, here an extract of my published vision for QGIS.org:

  I want to help QGIS and it’s community thrive under the value proposition of:

  Making the most amazing opensource GIS that provides users with value and that meets their needs by providing great functionality and usability, being cost-effective whilst being actively supported by a vibrant and knowledgeable community.

  Sharing our work under an open-source license is part of the approach by which we achieve that value proposition as it allows broad collaboration with our developers and users community.

  I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I want our focus to be on allowing both pragmatic and ideological views to respectfully coexist and enrich each other.

  One of my main motivations to be part of the PSC and to make myself available as project Chair is to help QGIS keep this incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, the key is maintaining the right balance between sustainable processes (that guarantee the great quality QGIS has been known for) and an interesting and motivating grassroots project to ensure that QGIS remains an attractive project for volunteers to contribute to and help QGIS and its community to grow to become even more the reference [Open Source] GIS project.

• 12 May 2020
• 9:40

  Stefano Costa: All my source code repositories are now on Codeberg

  sur Planet OSGeo

  I have moved all my personal source code repositories to Codeberg! Codeberg is the free home for your free projects. Because free and open source software deserves a free and open source platform.

  Codeberg.org is a provider for git source code hosting, based on the Gitea software. Gitea is open source, so there are many servers around, large and small, and there is no centralization. Gitea is very easy to use and it follows the same visual and conceptual paradigms that are common on other platforms. Git itself of course is and remains decentralized. For this reason I could easily switch many providers since I started using Git around 2008: repo.or.cz, gitorious. But that’s the technical side of it.

  Codeberg is run by Codeberg e.V., a no profit organization based in Germany. That means the platform is not run with the purpose of making money (not a bad thing per se, of course) or gathering user data, or accumulating enough social klout to sell the entire platform. It’s a service for the community, just like Wikipedia and OpenStreetMap. And there’s more: you can join Codeberg e.V. and become an active member. You’ll need to pay a small annual fee (which helps cover the costs of infrastructure) and you can participate in the discussions and decisions that shape the future of Codeberg. When I decided to move my repositories to Codeberg, I thought it was an excellent opportunity to give a strong support to this initiative and encourage more users to join us.

  Gitea is open source and it’s not difficult to run your own server. But, as any sysop knows, running thousands of separate servers doesn’t scale, that is, the costs of hosting 1000 repositories on 1000 separate servers are a lot higher that keeping those same 1000 repositories on 1 server only. Keeping a server running and up to date takes time, too. So I think it’s better to keep some of the advantages of centralized platforms and change what is really wrong with them: the software must be free, the governance must be open, the funding should come from users.

  .org hosting on .com was a historical mistake we all made. Time to correct it!

  Andreas Shimokawa

  I took the move to Codeberg as an opportunity to improve my good practice in software development and repository management:

  • I’m not creating “vanity” organizations like I did in the past: all repositories are under the steko user and I will consider creating an organization only when there is an actual community around a project (like we did for Total Open Station)
  • I’m trying to avoid overengineering with planned releases, issues, and anything that puts stress where fun and passion should be
  • I’ll be signing all Git commits with my GPG key
  • I will never again cite a source code repository in an academic paper: instead I will upload the snapshot to Zenodo, get a DOI and cite that (I did this mistake too many times in the past, even recently, only to realize how volatile these URLs can be)

  If you are an open source developer, I encourage you to join me on Codeberg!

  What’s wrong with GitHub?

  In the past 10 years the (apparently) unstoppable trend has been of concentrating the development of most open source software on GitHub, a proprietary service that was acquired by Microsoft last year. When that happened, some people became worried upon realizing that one of the giant monopolies had taken possession of their favourite platform. However, GitHub was a proprietary service all along, and it was made possible by venture capital. It was silly to make it a sacred place, as was teaching students Git as merely the tool behind GitHub, or using GitHub Pages as the “best” option for your website. Yes, there are millions of developers using GitHub, and it makes a lot of things easy, for free… but that comes at a price. I had started deleting repositories from GitHub last year, now only a few ones remain but I will delete those as well. While my personal repositories are moving to Codeberg, at this time Total Open Station remains on GitHub (of course I will try to move it as well, but that’s not a decision I can take by myself and it’s not even on the table).

  Some people moved to Gitlab.com, the flagship website of the company with the same name. The Community edition of Gitlab is open source, and it’s used by Debian, Gnome, Framasoft and other large projects. I had been using Gitlab.com for a few years and I dislike it from many points of view, mostly descending from the fact that it’s funded by venture capital. There were many revealing episodes: asking female employees to wear high heels; putting forward a ‘no politics at workplace’ stance, in order to keep quiet how much they’re looking for big contracts with all branches of the US government including Immigration and Customs Enforcement (ICE). They messed with users’ privacy and retracted introducing telemetry after public outrage. And I’m not even touching the technical side, since GitLab started as a simple GitHub clone and is now a behemoth all about putting your projects in Kubernetes. I have deleted and rectracted almost all repositories and I will delete everything shortly (my user account may remain there, empty, because I don’t like name squatting). In short, if you self host Gitlab, it may be fine, but I would never recommend putting your open source efforts on gitlab.com.

  The old Bitbucket, where I had many of my early Mercurial repositories, is dropping support for Mercurial and suffers from all the same problems of other proprietary platforms. I converted all those repositories and I’m moving those as well, even the old ones that I consider archived, because I think there’s some value in them.

• 11 May 2020
• 20:23

  Narcélio de Sá: TecnoloGEO 07 X-Habilidades para Alavancar a sua carreira nas Geotecnologias

  sur Planet OSGeo

  Enclosure: [download]

  Neste podcast: O TecnoloGEO 07 traz até você um bate-papo com Murilo Cardoso e Narcélio de Sá, onde iremos discutir 8 habilidades necessárias para você ser um profissional de GIS de sucesso no mundo de hoje.

  Sentamos para discutir um artigo publicado no LinkedIn por Chris Akin onde ele apresenta 8 habilidades críticas que você precisa ter para ser um profissional bem-sucedido na área de GIS.

  Aperte o ? para começar o TecnoloGEO #07

  Podcast: Download do TecnoloGEO 07
  

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 07: Livros:

  • Como Fazer Amigos e Influenciar Pessoas – Dale Carnegie
  • Faça Como Steve Jobs – Carmine Gallo
  • Storytelling: Aprenda a contar histórias com Steve Jobs, Papa Francisco, Churchill e outras lendas da Liderança – Carmine Gallo
  • HQ Maus – Art Spiegelman
  • HQ Magneto. Testamento – Carmine di Giandomenico
  • Empreendedorismo para Subversivos – Facundo Guerra 

  Filmes

  • 2001: Uma Odisséia no Espaço (1968) – Stanley Kubrick
  • Catálogo de filmes do universo X-Men

  Vídeos

  • Lives de R – Geocast
  • Lives de Python – Geocast

  Sugestões de links:

  • Geocast Brasil
  • 8 Critical Skills You Need to be a Successful GIS Professional

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 07 X-Habilidades para Alavancar a sua carreira nas Geotecnologias appeared first on Narcélio de Sá.

  
• 9:04

  Stefano Costa: Archeologia nel Mediterraneo e colonialismo: seconda puntata

  sur Planet OSGeo

  Questo articolo è stato scritto nel 2012 ed è rimasto in bozze per 8 anni. Mi pare ancora degno di vedere la luce del sole e lo pubblico tale quale con qualche aggiornamento ai link.

  Riprendendo il discorso iniziato qualche tempo fa su archeologia italiana e colonialismo, metto sul piatto altri appunti.

  Il primo punto importante, che ho dato per scontato in precedenza, è che tutto questo ragionamento si applica a quel particolare sottoinsieme dell’archeologia rappresentato dalla ricerca universitaria o accademica in genere, l’unica che in modo sistematico si dedica alla ricerca sul campo all’estero.

  Non penso che ci siano davvero parametri per giudicare se un ricercatore o un gruppo di ricerca siano colonialisti o meno. I problemi di cui ho parlato sono dei temi di riflessione, che conducono il discorso nell’ambito della questione colonialista e fanno diventare una gomena il filo che nessuno può negare ci leghi al colonialismo con la F maiuscola. Sul rapporto tra colonialismo e fascismo di ieri nell’Italia di oggi ci sono spunti in più di un punto di questa intervista a Wu Ming 2. Incluso un riferimento alla rivista Interventions: international journal of postcolonial studies, purtroppo costosissima.

  Avere una pratica colonialista facendo archeologia a volte è semplicemente un fatto. Non essere colonialisti facendo archeologia nel Mediterraneo è difficile, secondo me. Avere una teoria colonialista è una cosa diversa.

  Io penso che nel ventunesimo secolo la parola chiave sia strumentalità: ovvero intendere un luogo, con il suo patrimonio archeologico, semplicemente come uno strumento (indispensabile) per condurre la propria ricerca e per accrescere il proprio prestigio accademico. È evidente che questo concetto non è limitato alle ricerche svolte all’estero, e già questo mi sembra un elemento molto importante, perché apre la strada ad una riflessione sul “colonialismo dietro casa”, sugli archeologi che arrivano da fuori a imporre la loro agenda ad una comunità, a una società.

  Va considerato il punto importante dei finanziamenti per la ricerca. In Italia una parte importante della ricerca all’estero è finanziata dal Ministero degli Esteri (il quadro è ben documentato sul sito web del Ministero). Di questo tema ho avuto modo di parlare con Andrew Bevan alcuni mesi fa. Il confronto con le esperienze straniere ? in modo particolare di ex (?) potenze coloniali ? è importante ma per qualche motivo mi voglio soffermare sull’Italia e sugli italiani.

  Il discorso sulla ricerca dell’esotico è molto complesso, e probabilmente va nella direzione di una riflessione più profonda sull’identità. Ma identità personale e identità politica si incontrano sempre, anche quando non vorremmo.

  E non dimentichiamo infine di pensare anche all’Italia colonizzata. Non credo esista un elenco di tutte le missioni di ricerca archeologica straniere in Italia. Ma certamente sarebbe interessante averlo, e sarebbe molto lungo. Non solo si scava e si cammina per l’Italia, ma si organizzano anche incontri di alto profilo (e non da ieri).

• 10 May 2020
• 15:57

  Free and Open Source GIS Ramblings: TimeManager is dead, long live the Temporal Controller!

  sur Planet OSGeo

  TimeManager turns 10 this year. The code base has made the transition from QGIS 1.x to 2.x and now 3.x and it would be wrong to say that it doesn’t show ;-)

  Now, it looks like the days of TimeManager are numbered. Four days ago, Nyall Dawson has added native temporal support for vector layers to QGIS. This is part of a larger effort of adding time support for rasters, meshes, and now also vectors.

  The new Temporal Controller panel looks similar to TimeManager. Layers are configured through the new Temporal tab in Layer Properties. The temporal dimension can be used in expressions to create fancy time-dependent styles:

  

  TimeManager Geolife demo converted to Temporal Controller (click for full resolution)

  Obviously, this feature is brand new and will require polishing. Known issues listed by Nyall include limitations of supported time fields (only fields with datetime type are supported right now, strings cannot be used) and worse performance than TimeManager since features are filtered in QGIS rather than in the backend.

  If you want to give the new Temporal Controller a try, you need to install the current development version, e.g. qgis-dev in OSGeo4W.

  Update from May 16:

  Many of the limitations above have already been addressed.

  Last night, Nyall has recorded a one hour tutorial on this new feature, enjoy:

• 11:37

  GRASS GIS: GRASS GIS 7.8.3 released

  sur Planet OSGeo
  GRASS GIS 7.8.3 released with many GUI updates
• 9:12

  Stefano Costa: I deleted my Keybase account

  sur Planet OSGeo

  Keybase was acquired by Zoom, the videoconferencing company. In case you never heard of Keybase, it’s a service providing “identity” proofs tied to cryprographic keys, pulling together the various digital identities that many of us have online.

  My Keybase account was deleted. None of the proofs exists anymore, even those that I had published on a few websites that I don’t even use anymore (like Twitter). I had never used it except for that vanity ‘look at my identities’ feeling. And to think that in the beginning many respected FOSS leaders jumped in like it was an amazing solution to GPG usability issues… Now it’s filled with fake accounts eager for cryptocurrency.

  As many have noted, Keybase was bound to be sold from the beginning since it was based on venture capital funding. It may be difficult to put it in practice, but my resolution is to never create new accounts on web services provided by VC funded startups. And even without the VC, the Keybase server and infrastructure always was a proprietary black box ? you have no way of running your our Keybase server. Clever marketing had this centralization pictured as the best solution to the wide fragmentation that makes many possible uses of cryptographic keys difficult for most people.

  Of course I had never uploaded my private keys to Keybase, despite this being strongly encouraged by the official documentation. But there’s a good chance that some people did that, and it doesn’t sound too good.

  I don’t think I will look for a replacement, even though a few alternatives have already been announced (keys.pub, openpgp proofs). My current GPG key is found at keys.openpgp.org and many email clients can retrieve it on the fly thanks to WKD.

• 06 May 2020
• 16:31

  gvSIG Team: Extending free certification for online courses about Geographic Information Systems til September

  sur Planet OSGeo

  Some weeks ago we launched free certification  for online gvSIG Desktop courses about Geographic Information Systems applied to different topics, offered by gvSIG Association, to help you make confinement more bearable. Although the situation in many countries is improving, there is still some time ahead of us in which many people will have to stay at home, and that is why we have decided to extend the free certification until September 30, 2020.
  

  For that, everyone who submits the certification exercises before that date, will be able to get the certificate of achievement completely free of charge.

  

  These courses are made with of gvSIG Desktop 2.4 version, available at: Download gvSIG Desktop 2.4

  The courses available are:

  • GIS applied to municipality management
  • GIS applied to archaeology
  • GIS applied to criminology

  These courses are also available in Spanish, and the course about GIS applied to municipality management is also available in French.

• 16:05

  QGIS Blog: QGIS Annual General Meeting – 2020

  sur Planet OSGeo

  Dear QGIS Community

  We recently held our 2020 QGIS Annual General Meeting. The minutes of this meeting are available for all to view.

  I would like to welcome our new QGIS Board Chair: Marco Bernasocchi and our new QGIS Board Vice-Chair and QGIS PSC Member, Alessandro Pasotti. In case you are not familiar with Marco and Alessandro, you can find short introductions to them below. I will continue to serve on the PSC and am pleased also to say that the project governance is in good hands with Jürgen Fischer, Andreas Neumann and Anita Graser kindly making themselves available to serve on the PSC for another two years. It is also great to know that our project founder, Gary Sherman, as well as long-term PSC member Tim Sutton continue to serve on the PSC as honorary PSC members. They both set the standard for our great project culture and it is great to have his continued presence.

  QGIS has been growing from strength to strength, backed by a really amazing community of kind and collaborative users, developers, contributors and funders. I am looking forward to seeing how it continues to grow and flourish and I am excited and confident it will do so with Marco acting as the project chair and representative. Rock on QGIS!

  Marco Bernasocchi (http://berna.io @mbernasocchi)

  

  I am an open source advocate, consultant, teacher and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English and Spanish and love travelling.

  I work as director of OPENGIS.ch which I founded in 2011. Since 2015 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we (6 superstar devs and myself) develop, train and consult our client on any aspect related to QGIS.

  My first QGIS (to be correct for that time QuantumGIS) ever was “Simon (0.6)” during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives. In 2008, when starting my MSc, I made the definitive switch to ubuntu and I started working more and more with QGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters thesis. Since three years the University of Zurich invites me to hold two seminars on Entrepreneurship and Open Source. In November 2011 I attended my first Hackfest in Zürich where I started porting all QGIS dependencies and developing QGIS for Android under a Google Summer of Code. A couple of years and a lot of work later QField was born. Since then I’ve always tried to attend at least to one Hackfest per year to be able to feel first hand the strong bonds within our very welcoming community. In 2013 i was lucky enough to have a release named after a suggestion I saved you all from having QGIS 2.0 – Hönggerberg and giving you instead QGIS 2.0 – Dufour. In 2018 I’ve been honored to be nominated Co-chair of the QGIS PSC, since then I’ve been taking care of GitHub, the user groups, running votes, elections, doing some small work on the website, giving more talks on opensource advocacy and foremost helping in the day to day work needed to help our amazing project keep on growing.

  Beside my long story with QGIS as user and passionate advocate I have a long story as QGIS service provider where we are fully committed to its stability, feature richness and sustainable development. For that in 2019 we started our own QGIS sustainability initiative financed through our support contracts.

  Alessandro Pasotti (@elpaso [https:] , [https:] )

  

  I am an open source software developer and I live in Italy. By education I’m an agronomist with some topography and pedology background, but I turned to the dark side early in my career and I started programming any kind of device that has a chip inside as soon as their price dropped low enough. I started using Linux in 1994 and after some real work as an R&D data analyst for a big pharmaceutical company I started my own small business that was making map-based web applications for the touristic market (there was no Google Map and such at that time) and it is for this reason that I discovered GRASS, Mapserver, PostGIS and finally QGIS when I needed a GIS viewer.

  Over the years I’ve made minor contributions to several open source projects and I created a bunch of QGIS Python plugins, but it is from the QGIS Lisbon Hack-Fest in 2011 that I really got involved within the community and my first big contribution was a new website for the fast growing set of QGIS Python plugins (the one that it is already in production today at https://plugins.qgis.org ).

  8 years ago I re-started to write some C++ code and I’m now a QGIS core developer and a proud member of this amazing community.

  Regards

  Paolo Cavallini (outgoing Chair)

• 10:11

  gvSIG Team: Ampliación de la certificación gratuita de los cursos online sobre Sistemas de Información Geográfica hasta septiembre

  sur Planet OSGeo

  Hace unas semanas pusimos en marcha la certificación gratuita de los cursos online sobre Sistemas de Información Geográfica aplicados a distintas temáticas que ofrece la Asociación gvSIG, para hacer más llevaderos estos días de confinamiento. Aunque va mejorando la situación en muchos países aún queda un tiempo por delante en el que muchos tendréis que permanecer en casa, y es por eso por lo que hemos decidido ampliar la certificación gratuita hasta el 30 de septiembre de 2020.

  Para ello, todas las personas que entreguen las pruebas de certificación hasta dicha fecha, podrán obtener el certificado de aprovechamiento de forma totalmente gratuita.

  

  Estos cursos están realizados con la versión 2.4 de gvSIG Desktop, disponible en: Descarga de gvSIG Desktop 2.4

  Los cursos disponibles son los siguientes:

  • SIG aplicado a gestión municipal
  • SIG aplicado a arqueología
  • SIG aplicado a criminología

  Estos cursos están disponibles también en inglés, y el curso de gestión municipal además en francés.

• 05 May 2020
• 11:12

  gvSIG Team: Google Summer of Code 2020. gvSIG Projects

  sur Planet OSGeo

  Two students have been selected to work on gvSIG projects for Google Summer of Code 2020. Congratulations to Giani Carlevaro and José Olivas.

  

  More info: [https:]]

• 11:00

  CARTO Blog: 10,000 Dutch Bridges: A Foray into Using BigQuery Connector

  sur Planet OSGeo
  One of my favorite parts about working at CARTO is getting to test out the new features that our product team is constantly shipping. A month or so ago, it was our Kepler c...
• 11:00

  CARTO Blog: Using Spatial Data in Retail Analytics Post COVID-19

  sur Planet OSGeo
  With countries cautiously relaxing lockdown restrictions, retailers are keen to understand how best to recover from the huge impact that COVID-19 has had on their business....
• 10:38

  gvSIG Team: Demo Day Smart Cities: La relación ciudad – ciudadano en tiempos de COVID-19 y cómo se adaptan los municipios

  sur Planet OSGeo

  La pasada semana fuimos invitados por AVAESEN a participar en el “Demo Day Smart Cities: La relación ciudad – ciudadano en tiempos de COVID-19 y cómo se adaptan los municipios”, una jornada participativa sobre la respuesta smart city contra la pandemia COVID-19. Durante el evento se habló sobre modelos de interacción innovadora ciudad-ciudadano a través de la tecnología, con casos concretos de España y Europa.

  Nuestra participación “La importancia de las tecnologías de localización ante emergencias sanitarias” planteó los beneficios y bondades del uso de la Suite gvSIG ante situaciones como la del COVID-19. Y, entre otras cosas, hablamos por primera vez de un nuevo miembro del catálogo tecnológico de gvSIG, gvSIG Mapps, sobre el que pronto esperamos daros más información.

  Podéis ver nuestra participación (y el resto del evento) aquí:

  Si estáis interesados en implantar alguna de las soluciones gvSIG planteadas podéis contactar con nosotros en info@gvsig.com

• 9:45

  XYCarto: Basic GRASS GIS with BASH, plus GDAL

  sur Planet OSGeo

  As a follow-up to the last blog, I thought it would be helpful to demonstrate how next to break up the elevation example into individual watersheds. The reason being, in my last example I demonstrated the process using a square raster tile. Hydrological processes are not accurate when run on square tiles. It is best to run further processes, like stream order extraction, on complete watersheds.

  If you are reading this and want to follow along, it is very helpful to go back and read this blog. The following builds off that last example.

  I’ll break this into two parts:

  1. Creating multiple watershed boundaries of different sizes with GRASS and using a basic loop in BASH for the process.
  2. Clipping the original raster by the watershed boundaries using GDAL and SQL with a basic loop in BASH.

  Creating Watershed Boundaries with Varying Sizes

  This section will modify the script created in the last post.

  Notice in the previous script, when I used r.watershed, I set the threshold value to 100000. You can use this value to set the minimum size of your watershed based on cell units. I see this as minimum number of pixels per watershed since your cell unit is the size of your pixel.

  threshold=100000
  accumulation=${rasterName}_accumulation
  drainage=${rasterName}_drainage
  stream=${rasterName}_stream
  basin=${rasterName}_basin
  r.watershed elevation=$fillDEM threshold=$threshold accumulation=$accumulation drainage=$drainage stream=$stream basin=$basin --overwrite
  

  Have a play setting the threshold value to different values, like 2000000 or 5000. You will get very different outputs in your watersheds vector layer. Try to determine the upper most threshold value you can input before GRASS can no longer determine a watershed.

  Warning: really small threshold values will take very long to process and give very poor results, like thousands of very tiny watersheds of little to no value in analysis.

  Once you have found you upper most limit for you threshold, determine a few lesser values and build them into a list. Maybe take the upper limit, half it, then half it again.

  Make that into a list into a variable:

  $ list=$(echo 2000000 1000000 500000)

  Then loop the list to iterate through your threshold values when running r.watershed in GRASS. All we change from the last script is the threshold value to use the item from the list. Note we add the threshold value as part of the name too.

  Use the standard form of a BASH loop:

  for i in $list
  do
      echo $i 
  done
  

  Loop with GRASS watershed commands:

  list=$(echo 2000000 1000000 500000)
  
  for i in $list
  do
      # Run watershed operation on fill sink raster
      threshold=$i
      accumulation=${rasterName}_accumulation_${i}
      drainage=${rasterName}_drainage_${i}
      stream=${rasterName}_stream_${i}
      basin=${rasterName}_basin_${i}
      r.watershed elevation=$fillDEM threshold=$threshold accumulation=$accumulation drainage=$drainage stream=$stream basin=$basin --overwrite
  
      # Convert Basin (watershed) to vector format
      basinVect=${rasterName}_basinVect_${i}
      r.to.vect input=$basin output=$basinVect type=area column=bnum --overwrite
  
      # Export catchment to vector format
      basinVectOut=${outDir}/${rasterName}_basinVectOut_${i}.shp
      v.out.ogr input=$basinVect output=$basinVectOut type=area format=ESRI_Shapefile --overwrite
  done
  

  Full script example here

  Your outputs this time will be a collection of shapefile watersheds constructed by your threshold value.

  Clipping your Raster by Individual Watersheds using GDAL, OGR and SQL

  The watersheds layers are full of nice watersheds, however you cannot simply clip the elevation raster by the full vector file. For the clip, you need to select each individual watershed first. The following will demonstrate how to list each of those watersheds and use them as a clip file via a loop.

  To start, set up a test directory for your processed raster outputs:

  $ mkdir grass_test/raster_watersheds

  The basic command for clipping a raster with a vector in GDAL is:

  $ gdalwarp -of GTiff -cutline input_shapefile_for cut.shp input_raster_to_be_cut.tif output_raster.tif

  You could create a shapefile for each watershed and clip your raster by that watershed individually using the command above, but the process would be fraught with errors and take a very long time.

  It is much easier to automate the process using a combination of ogrinfo, sql and gdal.

  We’ll do this with an example using JM_basinVectOut_2000000.shp you just created.

  JM_basinVectOut_2000000.shp

  In the example, we’ll:

  1. Read and list individual watersheds from the vector layer, by listing all the ‘cat’ values leveraging the ogrinfo -sql switch.
  2. Using the list, we’ll clip the original raster by each individual watershed

  First, list the ‘cat’ values in the vector watershed layer.

  The basic ogrinfo command is:

  $ ogrinfo /grass_test/JM_basinVectOut_2000000.shp

  For this operation; however, we need to list the information of each row in the attributes:

  $ ogrinfo -geom=NO -q -sql "SELECT cat FROM JM_basinVectOut_2000000" /grass_test/JM_basinVectOut_2000000.shp

  In the above ogrinfo command lists all of the rows for the ‘cat’ column, excluding any geographic information for the file. To do this we use the ‘-sql’ switch available in ogrinfo.

  Note when using the ‘-sql’ switch you need a layer name, ‘JM_basinVectOut_2000000’ from the shapefile. The layer name is just the name of the shapefile with the .shp removed.

  Use grep to select the parts from the output you want and sed to clean up the outputs for a tidy list.

  $ ogrinfo -geom=NO -q -sql "SELECT cat FROM JM_basinVectOut_2000000" /home/ireese/grass_test/JM_basinVectOut_2000000.shp | grep 'cat (Integer)' | sed s/'cat (Integer) =//g'

  Make it a list variable:

  $ watershedList=$(ogrinfo -geom=NO -q -sql "SELECT cat FROM JM_basinVectOut_2000000" /home/ireese/grass_test/JM_basinVectOut_2000000.shp | grep 'cat (Integer)' | sed s/'cat (Integer) =//')

  Before we loop the process in gdal lets look quickly at why this list was created.

  In gdalwarp we are going to again leverage the ‘-sql’ switch in order to select each individual watershed row and clip only by that row. We’ll be writing the a basic ‘sql’ similar to the above, but instead filtering by each watershed:

  SELECT cat FROM watershed WHERE cat=$i

  So, putting all the bits together, using clip and SQL, in gdalwarp we get:

  $ gdalwarp -of GTiff -dstnodata -9999 -cutline $inputVector -csql "SELECT cat FROM $inputVectorLayerName where cat='$i'" -crop_to_cutline input_raster_to_be_cut.tif output_raster.tif

  Note, I am using ‘-crop_to_cutline’ and ‘-dstnodata’. Basically I’m saying, crop the output raster the bounding box of the input vector and set a ‘nodata’ value of -9999 to the pixels outside the clip area.

  Now we need put this all together in a script to loop the process.

  
  #!/bin/bash
  
  # set base path
  outDir=grass_test
  outDirRast=grass_test/raster_watersheds
  
  # Set raster as variable
  raster=${outDir}/lds-tile-jm-GTiff/JM.tif
  rasterName=$( basename $raster | sed 's/.tif//g' )
  
  #prep your input vectors
  inputVector=/home/ireese/grass_test/JM_basinVectOut_2000000.shp
  inputVectorLayerName=$(basename $inputVector | sed 's/.shp//')
  
  #create your watersheds list
  watershedList=$(ogrinfo -geom=NO -q -sql "SELECT cat FROM $inputVectorLayerName" $inputVector | grep 'cat (Integer)' | sed s/'cat (Integer) = //')
  
  for i in $watershedList
  do
      gdalwarp -of GTiff -dstnodata -9999 -cutline $inputVector -csql "SELECT cat FROM $inputVectorLayerName where cat='$i'" -crop_to_cutline $raster $outDirRast/${rasterName}_${i}.tif
  done
  

  Copy the above script, check your file paths, and save it in a text editor as:

  rasterClipByWatershed.sh

   

  To run the script:

  $ bash grass_test/rasterClipByWatershed.sh

  Final Note
  In the above process, it may be necessary to run some clean up operations to remove invalid geometries in the watersheds vector layer. I did not include this, but it is helpful to resave the watersheds shapefile first by running a buffer operation with a buffer value of ‘0’. This will remove the invalid geometries. You can run this in GRASS or using ogr2ogr with PostGIS. Here is an ogr2ogr with PostGIS example:

  $ ogr2ogr -f "ESRI Shapefile" output_vector.shp input_vector.shp -dialect sqlite -sql "select id, ST_buffer(Geometry,0) as geom from input_vector" -overwrite

  All the scripts from the past two posts can be found here.

  Let me know of this helpful. I could potentially move on to doing some more basic hydro analysis with GRASS and BASH, but these things take time and energy. It would be good to know if these sorts of blogs have value to the wider geospatial world.

• 04 May 2020
• 14:10

  Narcélio de Sá: TecnoloGEO 06 – Ciência de dados: Que a força esteja com você!

  sur Planet OSGeo

  Enclosure: [download]

  Neste podcast: O TecnoloGEO 06 traz até você a continuação do bate-papo sobre ciência de dados com Murilo Cardoso, Narcélio de Sá, Luiz Sadeck e Felipe Sodré, onde iremos discutir sobre a formação do profissional de ciência de dados.

  Nesse episódio teremos uma indicação super especial para você que pretende explorar as potencialidades do R para análises espaciais, não deixe de ouvir o episódio até o final para conferir essa novidade do Geocast.

  Aperte o ? para começar o TecnoloGEO #06

  Podcast: Download do TecnoloGEO 06
  

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 06: Livros:

  • Geografia conceitos e temas – Iná Elias de Castro
  • Como mentir com estatísticas – Darrell Huff – 1954
  • A Simple Introduction to DATA SCIENCE – 2013 – Lars Nielsen
  • Data Science do Zero: Primeiras Regras com o Python – Joel Grus
  • 21 lições para o século 21 – Yuval Noah Harari
  • Sapiens – Uma Breve História da Humanidade – Yuval Noah Harari

  Filmes

  • O Homem que Mudou o Jogo (2011) – Bennett Miller
  • O Jogo da Imitação (2014) – Morten Tyldum
  • Transcendence: A Revolução (2014) – Wally Pfister
  • Lucy (2014) – Luc Besson
  • Matrix (1999) – Lana Wachowski , Lilly Wachowski
  • 2001: Uma Odisséia no Espaço (1968) – Stanley Kubrick

  Vídeos

  • O que é Data Science?
  • GeoDa Software
  • Prediction by the Numbers – NETFLIX

  Sugestões de links:

  • Geo Independência – Felipe Sodré
  • Epistemologia dos SIG – Gilberto câmara
  • Fundamentos epistemológicos da ciência da geoinformação – Gilberto câmara
  • Geographic Data Science- Alex Singleton e Daniel Arribas-Bel
  • Geographic Data Science with PySAL and the pydata stack
  • Essential geospatial Python libraries
  • Will robots take my job?
  • Geo-Python 2019
  • Lives de PyQGIS
  • Spatial Data Science with R

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 06 – Ciência de dados: Que a força esteja com você! appeared first on Narcélio de Sá.

  
• 03 May 2020
• 16:06

  GeoSolutions: Upcoming Free Webinar: What’s new in GeoServer 2.17?

  sur Planet OSGeo

  

  Dear Reader,

  As most of you readers are aware, GeoServer is a very  popular open source tool to publish geospatial data. We, at GeoSolutions, are very fortunate to have in our team key code contributors, as well as, customers that support the advancement of GeoServer for the greater benefit of the geospatial community. Version 2.17 was released a week ago. A blog with detailed information is available at the GeoServer blog. In this post, I highlight some new functionality and invite you to a webinar on May 11th to learn more about the release from our GeoServer lead developer, Andrea Aime,

  The GeoServer 2.17 release comes with many interesting new functionalities, let us briefly introduce some of them.

  Faster, due to improvements in GeoWebCache

  You will experience a much better startup performance because of the improvement to load the tiles layers configuration. Now, you can have  better control over failed seeding operations, by configuring error tolerance on single threads and across seed jobs (enabling seeding threads to continue if they encounter failures, like it occurred in the past).

  

  Ability to render vector tiles with Mapbox Styles

  You can now configure GeoServer to serve layers as vector tiles which can be used as sources for Mapbox styles rendered by web applications such as OpenLayers.

  

  Improved the ability to read and write MBTiles files in GeoServer

  Now you can read and write MBTiles files in GeoServer. You can use MBTiles as a raster input datastore as well as an WMS GetMap output format.

  [caption id="" align="alignnone" width="767"] MBTiles[/caption]  

  And more functionality like:

  • Added support for FlatGeoBuf (incredible binary encoding for fast transfers)
  • Added functionality to view and manage resources in the data directory (e.g. configuration files, icons and fonts)
  • Better manage security for layers when looking at layer
  • Ability to view when a layer was created and last modified
  • Improved the rendering of icons and maps
  • Enable changing background in the SLD
  • Enable ability to enable/advertise layer groups
  • Ability to add custom dimension in vector layers (similar to time and elevation, dimensions in WMS)
  • Added more capabilities to WMS Cascading (e.g. specify format, min/max scale denominators for cascaded layers)
  • Added support for JSON-LD
  • Added support for OpenAPI
  • And much more..

  We cordially invite you to join the webinar on Monday May 18th at 11:00 EDT / 3:00 pm GMT (check more time zones), to learn more about this release from our GeoServer Technical Lead, Andrea Aime. We are planning to do 30 minutes presentation and 30 minutes for questions.  You can register by clicking on the button below.

  

  Hope to see you virtually on May 18th, meanwhile stay safe and keep strong!

  Cordially,

  Luis
• 4:04

  XYCarto: Basic GRASS GIS with BASH

  sur Planet OSGeo

  I love GRASS… GIS

  But this wasn’t always the case.

  GRASS GIS was, for a long time, something I dismissed as ‘too complex’ for my everyday geospatial operations. I formulated any number of excuses to work around the software and could not be convinced it had practical use in my daily work. It was ‘too hard to set-up’, ‘never worked well with QGIS’, and ‘made my scripting processes a nightmare’.

  I am here to officially say I’ve been very wrong for a very long time. GRASS GIS is pretty amazing and is a wonderfully easy tool to script.

  Recently I scripted a model for extracting river centrelines from high resolution elevation data. During the process I thought how useful it would have been, way back, to have a simple example for setting up an environment and scripting a BASH process using GRASS. So, I built one for myself.

  The following example provides the steps for a simple catchment extraction on a piece of LINZ 8m elevation data. The example is only for demonstration of running a basic BASH/GRASS set up with a hydrology command and NOT a demonstration for how to do hydrology using GRASS. The 8m elevation data is not the best data for hydrological extraction; however, these data do provide a nicely sized dataset to use as practice and will give results. Also please note, catchment extraction on a square raster is will not give accurate results at the edges of the raster.

  In this example we will:

  1. Download a small piece of elevation data from the LINZ Data Service
  2. Build a GRASS environment to process these data
  3. Build a BASH script to process the catchments
  4. Import the elevation into the GRASS environment
  5. Perform some basic GRASS operations (fill and watershed)
  6. Export raster format for viewing
  7. Export the vector catchments to shapefile

  The following assumes you are working in a Linux environment and have a basic knowledge of BASH scripting. I tested this process using Ubuntu 18.04 and GRASS 7.4. I have 16GB RAM on my machine.

  If you do not all ready have it, you can install GRASS as follows:

  $ sudo apt-get install grass-core

  If interested, but not necessary, you can install functionality for building GRASS plug-ins:

  $ sudo apt-get install grass-dev

  Create yourself a directory to work in:

  $ mkdir grass_test

  Download a piece of elevation data from the LINZ Data Service, place in your directory:

  [https:]]

  From the Tiles Table, I downloaded the JM tile in EPSG:2193.

  Within your directory you will need to build a ‘PERMANENT’ folder in order for GRASS to do its magic. This folder will be set to operate in the projection of your data. Be sure your data is in the same projection as the environment you built. The data is downloaded in EPSG:2193, New Zealand Transverse Mercator (NZTM), so we set the GRASS environment to work in this projection:

  $ grass -c epsg:2193 -e grass_test/GRASS_ENV

  ‘-c’ will create your directory using epsg:2193 and ‘-e’ will exit once this operation is complete.

  Running this command will build a PERMANENT folder in:

  grass_test/GRASS_ENV

  providing all the bits GRASS needs to operate. Your folder structure will look like:

  grass_test/GRASS_ENV/PERMANENT

  Have a look inside the folder and see what GRASS built for itself.

  The key from now on is to always run your BASH script through this environment. Running your script in this environment will allow you to perform BASH and GRASS commands at the same time.

  First, let’s look at the the basic command to run a BASH script using a GRASS environment.

  $ grass grass_test/GRASS_ENV/PERMANENT --exec sh grass_test/catchment.sh

  The above says, launch GRASS using this environment

  grass_test/GRASS_ENV/PERMANENT

  and execute, –exec, this script

  /grass_test/catchment.sh

  Let’s build the BASH script. In this we will:

  1. Import the elevation data. GRASS likes to work in its own data formats
  2. Set the region for where the operation will be performed. GRASS needs to know where the operation is going to be performed.
  3. Perform the operations, r.fill.dir and r.watershed
  4. Export a raster to .tif format
  5. Export the vector outputs to .shp format

  
  #!/bin/bash
  
  # set base path
  outDir=grass_test
  
  # Set raster as variable
  raster=${outDir}/JM.tif
  
  # Set a base name for the data. This is used to demonstrate that normal
  # BASH commands can be used in this process, along side GRASS
  rasterName=$( basename $raster | sed 's/.tif//g' )
  
  # Import raster data
  r.in.gdal input=$raster output=$rasterName --overwrite
  
  # Set region. IMPORTANT so GRASS knows where the data is located.
  # This region is set for the duration of the following commands
  g.region rast=$rasterName
  
  # Fill sinks
  fillDEM=${rasterName}_filldem
  directionDEM=${rasterName}_directiondem
  areasDEM=${rasterName}_areasDEM
  r.fill.dir input=$rasterName output=$fillDEM direction=$directionDEM areas=$areasDEM --overwrite
  
  # Export a raster for viewing
  areaOut=${outDir}/${rasterName}_areas.tif
  r.out.gdal input=$areasDEM output=$areaOut
  
  # Run watershed operation on fill sink raster
  threshold=100000
  accumulation=${rasterName}_accumulation
  drainage=${rasterName}_drainage
  stream=${rasterName}_stream
  basin=${rasterName}_basin
  r.watershed elevation=$fillDEM threshold=$threshold accumulation=$accumulation drainage=$drainage stream=$stream basin=$basin --overwrite
  
  # Convert Basin (watershed) to vector format
  basinVect=${rasterName}_basinVect
  r.to.vect input=$basin output=$basinVect type=area column=bnum --overwrite
  
  # Export catchment to vector format
  basinVectOut=${outDir}/${rasterName}_basinVectOut.shp
  v.out.ogr input=$basinVect output=$basinVectOut type=area format=ESRI_Shapefile --overwrite
  

  There you have it. A simple BASH script, set up for running some GRASS commands, running on your LINUX machine.

  Putting it all together

  Set up you environment, copy the above script, paste it into a text editor, save it as:

  grass_test/catchment.sh

  Now run

  $ grass grass_test/GRASS_ENV/PERMANENT —exec sh grass_test/catchment.sh

  Your output catchments shapefile should be similar to the image below

  

   

  Click here for the next step in this process; how to clip your raster using the watershed layer using GDAL and loops.

  Let me know if this was helpful or if you would like to see any changes.

• 02 May 2020
• 14:01

  Free and Open Source GIS Ramblings: QGIS video tutorials: election maps, hydrology, and more

  sur Planet OSGeo

  Mapping spatial decision patterns, such as election results, is always a hot topic. That’s why we decided to include a recipe for election maps in our QGIS Map Design books. What’s new is that this recipe is now available as a free video tutorial recorded by Oliver Burdekin:

  This video is just one of many recently published video tutorials that have been created by QGIS community members.

  For example, Hans van der Kwast and Kurt Menke have recorded a 7-part series on QGIS for Hydrological Applications:

  and Klas Karlsson’s Youtube channel is also always worth a follow:

  For the Pythonically inclined among you, there is also a new version of Python in QGIS on the Automating GIS-processes channel:

   

• 30 April 2020
• 17:12

  Oslandia: (Fr) Entretien avec Vincent Picavet

  sur Planet OSGeo

  Sorry, this entry is only available in French.

• 15:31

  geomati.co: ¿Quiénes somos Geomatico, la empresa de la web "1km"?

  sur Planet OSGeo

  En 3 días, hemos pasado de ser conocidos sólo en el mundo del GIS y las aplicaciones geográficas a ser la “empresa de 1km.geomatico.es”, tras más de tres millones de visitas en un fin de semana. Para todos los que no habíais oído hablar de nosotros, somos una cooperativa galaico-catalana que llevamos 8 años desarrollando software geo de código libre para necesidades concretas de empresas y AAPP. Estamos especializados en movilidad (trabajamos por ejemplo para Transportes Metropolitanos de Barcelona, Siemens o el Puerto de Barcelona) pero también colaboramos con cualquier sector que necesite de las últimas tecnologías geo, como el medioambiental (Food Agriculture Organization de las Naciones Unidas). Podéis consultar nuestros proyectos en nuestra página web geomati.co - por ahora, pues estamos en proceso de cambiar de nombre a geomatico.es -.

  La idea de 1km.geomatico.es surgió con la intención de ayudar con una pequeña aportación en estos tiempos difíciles. No queríamos sacar ningún provecho económico de ello y contamos con la inestimable ayuda (también desinteresada) de Mapbox para dar servicio al enorme tráfico (casi 20.000 usuarios simultáneos durante el sábado) que fue un auténtico reto. Os agradecemos muchísimo el interés y vamos a intentar seguir aportando nuevas funcionalidades que os ayuden durante el desconfinamiento. Mucho ánimo a todos, pronto podremos vernos aunque sea con un poco de distancia.

  

  Contacto: info@geomatico.es

• 11:00

  CARTO Blog: Acquiring New Customers with Geomarketing for Online Retailers

  sur Planet OSGeo
  Before the COVID-19 pandemic, expected spend on online retail sales was expected to surpass $6.5tn by 2023. It remains to be seen whether the spike in online retail sales a...
• 29 April 2020
• 18:50

  gvSIG Team: Calling for gvSIG Community to update gvSIG Desktop 2.5.1 translations

  sur Planet OSGeo

  The first release candidate to final gvSIG 2.5.1 version is available now, and it is in the stabilization phase. In parallel the translations of the interface are being updated in order to have the final version with as many languages as possible.

  Currently gvSIG is translated to more than 25 languages, thank to the participation of the Community.

  There are two ways of collaboration: updating any of the existing languages, as well as translating gvSIG interface to a new language in which gvSIG is not translated currently.

  If you are interested in translating gvSIG interface you can contact the gvSIG Project [info@gvsig.com] and we would send the instructions to do it.

  Translations that aren’t finished when the final version is released will be published as a package to be loaded from the gvSIG Add-ons manager.

  We expect your collaboration!

   

• 18:45

  gvSIG Team: Llamamiento a la Comunidad gvSIG para actualizar las traducciones de gvSIG Desktop 2.5.1

  sur Planet OSGeo

  Recientemente se ha publicado la primera versión candidata a final de la nueva versión 2.5.1 de gvSIG Desktop, encontrándose en fase de estabilización. Paralelamente se están actualizando las traducciones de la interfaz para tener la versión final disponible en el mayor número de idiomas posible.

  Actualmente gvSIG se encuentra traducido a más de 25 idiomas, gracias a la participación de la Comunidad.

  Existen dos formas de colaboración, bien actualizar cualquiera de los idiomas ya existentes en versiones anteriores, o bien traducir a algún idioma en el que no se encuentre traducido gvSIG actualmente.

  Si estáis interesad@s en traducir la interfaz de gvSIG podéis poneros en contacto con el proyecto [info@gvsig.com], y os indicaremos las instrucciones.

  Las traducciones que no estén finalizadas en el momento de la publicación de la versión final se publicarán como paquetes que podrán ser cargados directamente desde el Administrador de complementos de gvSIG.

  ¡Esperamos vuestra colaboración!

• 11:00

  CARTO Blog: Assessing Potential Impact of COVID-19 on Rural Communities

  sur Planet OSGeo
  To date the majority of confirmed COVID-19 cases have been centered on major metropolitan areas, but as infection rates there begin to stabilize and reach their peak, atten...
• 28 April 2020
• 18:10

  geomati.co: One kilometer from home

  sur Planet OSGeo

  On March the 23rd, after five weeks of COVID-19 lockdown, president Sanchez announced that Spain will begin easing restrictions. In this first attempt at  loosening measures across the country, children under the age of 14 will now be allowed to go outside of their homes for one hour a day, accompanied by an adult. The measure limits travel to no further than 1 kilometer from home. But just how far is 1 kilometer? To help navigate these new rules, Geomatico, a Spanish GIS company, developed a non-profit web application using donated tools from Mapbox that allows adults and children to visualize a 1 kilometer radius around their home.

  In ten days, 1km.geomatico.es has become a reference for individuals and families throughout Spain looking to safely leave their house for the first time in over a month. Thanks in part to Mapbox’s support, the team has been able to deliver this mapping service for free to over 7 million users in multiple languages and municipal districts.  

  Want to see what 1 kilometer compliance looks like where you live? Check out the application here.

  

  Want to see what 1 kilometer compliance looks like where you live? Check out the application here.
  

• 16:44

  gvSIG Team: First release candidate to final gvSIG 2.5.1 version is now available to be tested

  sur Planet OSGeo

  The first release candidate (RC1) to final gvSIG 2.5.1 version is now available to download on the project website. In this first distribution we have put at your disposal the portable version so that you test it and send us the errors that you detect in order to fix them for the final version.

  

  As we informed you some time ago, this new version is the result of the correction of the most relevant errors that had been detected after releasing gvSIG 2.5, a version with big changes. In addition, new functionalities developed in recent months have been added, bringing considerable improvements to the application. We will inform you shortly of all the improvements in this new gvSIG Desktop version.

  To test it you just have to download the .ZIP file, unzip it in a path without spaces (and not directly on C:\ in Windows) and you can run it. Then if you detect any error you can inform us about it it as always through the users mailing lists.

  We expect your collaboration with testing.

• 16:44

  gvSIG Team: Primera candidata a final de la nueva versión gvSIG 2.5.1 disponible para su testeo

  sur Planet OSGeo

  La primera Candidata a versión final (RC1) de gvSIG 2.5.1 ya está disponible para descargar en la web del proyecto. En esta primera distribución hemos puesto a vuestra disposición la versión portable para que la testeéis y nos hagáis llegar los errores que detectéis de cara a corregirlos para la versión final.

  

  Como os informamos hace un tiempo, esta nueva versión es el resultado de la corrección de los errores más relevantes que habían surgido tras la publicación de la versión 2.5, una versión que llevaba grandes cambios. Aparte se han añadido nuevas funcionalidades desarrolladas durante estos últimos meses que aportan considerables mejoras a la aplicación. En breve os informaremos de todas las mejoras de la nueva versión de gvSIG Desktop.

  Para testearla solo debéis descargar el fichero .ZIP, descomprimirlo en una ruta sin espacios (y en Windows que no esté directamente en C:\) y ya podéis ejecutarla, y si detectáis algún error nos lo podéis modificar como siempre a través de las listas de usuarios.

  Esperamos vuestra colaboración con el testeo.

• 13:47

  GeoServer Team: GeoServer Group in Portuguese on WhatsApp

  sur Planet OSGeo
  

  The Portuguese GeoServer email list is slowing down and moving to WhatsApp for a more agile and efficient experience exchange.

  The group created on WhatsApp to discuss GeoServer in Portuguese (Brazilian) already has more than 150 users!

  If you speak Portuguese, and wish to stay informed or exchange experiences on GeoServer, click on the link below to join the Group.

  [bit.ly]

• 27 April 2020
• 12:02

  geomati.co: 1km.geomatico.es en TV3

  sur Planet OSGeo

  [https:]]
  

  
• 11:39

  geomati.co: 1km.geomatico.es en la Cadena SER

  sur Planet OSGeo

  [https:]]
  

  
• 11:13

  geomati.co: 1km.geomatico.es en Huffington Post

  sur Planet OSGeo

  [https:]]

  
• 11:09

  geomati.co: 1km.geomatico.es en La Sexta

  sur Planet OSGeo

  [https:]]
  

  
• 11:03

  geomati.co: 1km.geomatico.es en La Voz de Galicia

  sur Planet OSGeo

  [https:]]
  
  

  
• 5:01

  Narcélio de Sá: TecnoloGEO 05 – Ciência de dados – isso serve em primeiro lugar para fazer…

  sur Planet OSGeo

  Enclosure: [download]

  Neste podcast: O TecnoloGEO 05 traz até você um bate-papo sobre ciência de dados com Murilo Cardoso, Narcélio de Sá, Luiz Sadeck e Felipe Sodré, onde iremos discutir sobre a ciência de dados, seu caráter interdisciplinar e suas implicações na área da análise espacial.

  Nesse episódio teremos uma indicação super especial para você que pretende explorar as potencialidades do R para análises espaciais, não deixe de ouvir o episódio até o final para conferir essa novidade do Geocast.

  Aperte o ? para começar o TecnoloGEO #05

  Podcast: Download do TecnoloGEO 05
  

  O tecnoloGEO é encabeçado por Murilo Cardoso (@niilistativo) , Narcélio de Sá (@narceliodesa) e Luiz Sadeck (@sadeckgeo), o projeto tem a pretensão de ser semanal e contar sempre com convidados, que sejam relevantes ao assunto em pauta da vez, pra bater aquele bate papo descontraído e informativo sobre as Geotecnologias.

  Referências e Indicações do TecnoloGEO 05: Livros:

  • Geografia conceitos e temas – Iná Elias de Castro
  • Como mentir com estatísticas – Darrell Huff – 1954
  • A Simple Introduction to DATA SCIENCE – 2013 – Lars Nielsen
  • Data Science do Zero: Primeiras Regras com o Python – Joel Grus
  • 21 lições para o século 21 – Yuval Noah Harari

  Filmes

  • O Homem que Mudou o Jogo (2011) – Bennett Miller
  • O Jogo da Imitação (2014) – Morten Tyldum
  • Transcendence: A Revolução (2014) – Wally Pfister
  • Lucy (2014) – Luc Besson
  • Matrix (1999) – Lana Wachowski , Lilly Wachowski
  • 2001: Uma Odisséia no Espaço (1968) – Stanley Kubrick

  Vídeos

  • O que é Data Science?
  • GeoDa Software

  Sugestões de links:

  • Geo Independência – Felipe Sodré
  • Epistemologia dos SIG – Gilberto câmara
  • Fundamentos epistemológicos da ciência da geoinformação – Gilberto câmara
  • Geographic Data Science- Alex Singleton e Daniel Arribas-Bel
  • Geographic Data Science with PySAL and the pydata stack
  • Essential geospatial Python libraries
  • Will robots take my job?
  • Geo-Python 2019
  • Lives de PyQGIS
  • Spatial Data Science with R

  Deixe seu comentário e participe!

  Contatos:

  • tecnologeopodcast@gmail.com
  • [https:]]
  • https://instagram.com/tecnologeo 

  Murilo Cardoso:

  • [https:]]
  • [https:]]

  Narcélio de Sá

  • www.narceliodesa.com
  • [https:]]

  Luiz Sadeck

  • [https:]]
  • [twitter.com]

  The post TecnoloGEO 05 – Ciência de dados – isso serve em primeiro lugar para fazer… appeared first on Narcélio de Sá.

  
• 26 April 2020
• 11:48

  QGIS Blog: QGIS Grants #5: Call for Grant Proposals 2020

  sur Planet OSGeo

  Dear QGIS Community,

  Our previous rounds of grant proposals have always been a great success (2019, 2018, 2017, 2016). We are very pleased to announce that this year’s round of grants is now available. The call is open to anybody who wants to make a funded contribution to QGIS, subject to the call conditions outlined in the application form.

  The deadline for this round is 24th May 2020.

  For more details, please read the introduction provided in the application form.

  We look forward to seeing all your great ideas for improving QGIS!

• 24 April 2020
• 13:52

  Fernando Quadro: GeoServer no WhatsApp

  sur Planet OSGeo

  Prezados leitores,

  Gostaria de informá-los que já a algum tempo foi criado no WhatsApp um grupo de discussão sobre GeoServer. Com a desaceleração dos grupos de e-mail, O WhatsApp e o Telegram são as ferramentas que tem sido adotadas para uma troca de experiência mais ágil e eficiente.

  Quem tiver interesse de fazer parte do grupo, que já possui mais de 100 inscritos, basta clicar no link abaixo:

  [bit.ly]

  Nos encontramos lá!

• 11:50

  gvSIG Team: Funcionalidades y ventajas de gvSIG Online, la plataforma integral para creación de una Infraestructura de Datos Espaciales

  sur Planet OSGeo

  gvSIG Online es uno de los productos principales de la Suite gvSIG, que permite crear geoportales de forma sencilla en unos pocos minutos, y con el que se puede publicar tanto cartografía ráster como vectorial, tanto capas locales como servicios web externos, y aplicar simbologías de diferentes tipos (incluso varias leyendas para una misma capa y que el usuario decida cuál desea visualizar). Aparte, es posible seleccionar qué geoportales son públicos y cuáles son privados, y qué capas serán visibles solamente para ciertos usuarios o grupos de usuarios (muy útil para dar permisos a los distintos departamentos de una entidad), no habiendo límite de proyectos, de capas, de usuarios, de descargas…

  

  Gracias a las herramientas de edición básica que incluye gvSIG Online, es posible editar las capas vectoriales tanto de forma gráfica (añadir nuevas geometrías, eliminarlas, desplazarlas, o editar vértices) como de forma alfanumérica (editar los atributos de su tabla asociada).

  Además, se han incluido herramientas de dibujo, que permiten dibujar ciertos elementos (puntos, líneas, polígonos y textos) sobre los geoportales, a modo de “capa virtual”.

  En referencia a la conexión con plataformas externas, una de las ventajas de gvSIG Online es que se puede conectar con gestores de expedientes o de documentos (Gestiona, Alfresco, SEGEX…), con sensores (para visualización en tiempo real de la situación de autobuses urbanos, del número de plazas de aparcamiento libres, de situación del tráfico…), etc.

  Respecto a las capas ráster, gvSIG Online soporta el formato GeoTIFF. Uno de los casos más comunes de uso en este caso es el de georreferenciar previamente con gvSIG Desktop una imagen escaneada (planos de Catastro en formato papel, Planes Generales de Ordenación Urbana antiguos…) y subirlos posteriormente a gvSIG Online, de forma que se dispone de una información muy útil gracias a la superposición con otro tipo de capas.

  Una de las últimas novedades de gvSIG Online es la posibilidad de importar ficheros vectoriales (shp, kml o json) o servicios externos (como por ejemplo un servicio WMS o WFS) directamente sobre un geoportal. Esta información estará asociada a una sesión, son capas “virtuales”.

  Otra de las funcionalidades importantes es la del parámetro temporal, donde teniendo una capa con uno o dos campos de tipo fecha (del momento del evento, o fecha alta/fecha baja) podemos ver cómo ha evolucionado la información analizada, muy útil por ejemplo para ver cómo era una parcela en una fecha anterior, o analizar cierto tipo de dato por tiempo como delitos, licencias de obra…

  Respecto a la información alfanumérica, el usuario que crea el geoportal puede decidir qué datos de los que hay en la tabla de atributos de una capa quiere que sean visibles en el proyecto, y además, cuáles se quieren mostrar directamente en la ventana de “Información” sobre la Vista. También se pueden enlazar ficheros PDF e imágenes a cualquier geometría, con lo que se amplia considerablemente la información a mostrar de cada una de ellas.

  Por otro lado, el usuario puede decidir si quiere que una capa se pueda descargar directamente desde la plataforma, pudiendo ser actualmente descargada en formato SHP, CSV o GML, lo que evita tener otros portales aparte para ello.

  Con el nuevo catálogo de metadatos se puede disponer de toda la información de las capas incluidas en la plataforma, pudiendo realizar búsquedas por área, tipo de dato, etc., además de tener una descarga más avanzada con límite de tamaño o de descargas, de forma que los administradores pueden aceptar o no la petición realizada por el usuario.

  Por otro lado, mediante la herramienta de “Compartir Vista” podremos enviar un enlace a otra persona en el que se muestre directamente un geoportal concreto, con ciertas capas visibles y en el encuadre deseado.

  Otras funcionalidades disponibles en gvSIG Online son la posibilidad de poder crear librerías de símbolos para aplicar a las capas de tipo punto, poder crear desplegables para ciertos campos de la tabla de atributos de forma que al editar la capa se pueda elegir entre los valores propuestos (muy útil para toma de datos en campo como inventarios, inspecciones o censos), búsqueda por coordenadas y conversión de coordenadas de un sistema de referencia a otro, Swipe o cortinilla (para comparar los cambios o información entre dos o más capas), etc.

  Desde la plataforma también se puede imprimir una zona concreta, disponiendo de varias plantillas por defecto, que el usuario puede elegir junto a la escala, texto legal, etc.

  Gracias al plugin de Geocodificación, los administradores de la plataforma pueden configurar diferentes geocodificadores (Nominatim, Google, servicios propios…), lo que permite realizar búsquedas de topónimos de una forma sencilla y obtener los resultados encontrados en cada uno de los geocodificadores configurados.

  Finalmente, se ha desarrollado un plugin que permite conectar a Catastro de España (pero aplicable a cualquier país que disponga de una conexión a sus datos catastrales), mediante el cual se pueden realizar búsquedas por referencia catastral, dirección o polígono/parcela, y también obtener la información catastral de una parcela seleccionada sobre gvSIG Online.

  Actualmente son muchas las entidades, tanto administraciones públicas, como empresas, que han adoptado gvSIG Online como su plataforma para gestionar su información geográfica. Entre ellas hay varios ayuntamientos, gobiernos regionales, ministerios, consorcios de bomberos, empresas de gestión de aguas, empresas del sector del petróleo y el gas, organizaciones no gubernamentales, o empresas de servicios de medio ambiente. Ejemplos de ellos son la IDE de Uruguay, el Servicio de Información Cartográfica de la Pobla de Vallbona (Valencia, España), o el Portal de Ecologistas en Acción.

  En el siguiente vídeo se muestran las principales funcionalidades de gvSIG Online, y para más información sobre la implementación de la plataforma, podéis escribir un correo a info@gvsig.com:

• 11:00

  CARTO Blog: OOH Bounce Back: 2020 Predictions

  sur Planet OSGeo
  Almost every industry is being affected by COVID-19, and OOH is no exception. To take China as an example, OOH spend in January was down 90% during full lockdown, recoverin...
• 23 April 2020
• 19:08

  GeoSolutions: Health SDI, Simple APIs and Web Map Clients for COVID Tracking

  sur Planet OSGeo

  

  Dear Reader,

  Sharing of health data has become one of the most important data sharing activities in the last months. The general population and authorities need to know the current situation not only about reported cases, deaths and recovered, but other data (e.g. hospital beds, ventilators, etc.) that supports properly responding to the COVID-19 pandemic. In addition to this health data, there are other non-health datasets (e.g. boundaries, socio-economic data) that provide context, complement and help decision makers better understand the possible actions to take. So, in today’s health emergency situation, an information sharing infrastructure with modern web visualization tools is critical to guide the way we share health and complementary data. 

  In this blog I am going to 1) highlight the importance of a Health Spatial Data Infrastructure (SDI) documented in a recent paper published by OGC, which I co-authored, 2) make the case that sharing of data should be easy, and 3) provide an example of a dashboard tracking COVID-19 data based on MapStore.

  The Open Geospatial Consortium (OGC) published some weeks ago the white paper: Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture. It provides reference to initiatives (e.g. EO4Health, Eo2Heaven, INSPIRE Human Health and Safety Specifications,)  that have occurred in the last years related to building an infrastructure that enables the collection, exchange, integration, analysis, and visualization of health and non-health data to help identify and address health issues at global and local level. The sections I consider worth reading are: Section 4.7. Pandemic Response,  Section 5 Data Considerations and Related Recommendations, and  Section 6 - Health SDI Architecture Framework.

  Section 4.7 discusses the development and use of different indexes (e.g. Transmission Risk Index) that are only possible to develop if there is enough information available. This is the reason why a Spatial Data Infrastructure is critical. This is the reason why we need to publish the data on the Web using open standards, following recommendations from Section 5 that takes into account security, anonymization and suggested formats and interfaces (e.g. WFS or WMS). 

  Section 6 provides a discussion on the architecture and also a workflow about what is needed when creating indexes that involve different types of data (See Figure 1). What is critical from the workflow is the catalog, which is the heart of an SDI. If you don't know what data is available you can’t put it together in a fast manner and it requires phone calls, emails, searching, scraping websites, etc., wasting precious time when building a common operational picture.

  [caption id="attachment_5221" align="aligncenter" width="1024"] Figure 1 - Health SDI Workflow[/caption] Worth to mention, that the prototype of a Health SDI was advanced in a recent OGC initiative, well documented in an OGC video. The tool used was GeoNode which is an-easy-to-setup tool for SDIs that allows the data to be easily cataloged, updated and shared via open standards.

  Organizations harvesting information from different sources to create dashboards mostly rely on personal communications and getting the data from official web reports available at government/intergovernmental websites. Then, they create “machine readable formats” such as JSON or CSV that are ingested in the web clients. The “manual process” of getting the data requires a lot of human power, and fortunately for this crisis there are a lot of people willing to help. This is not the ideal. Government and other official sources should be making data available via open standards following the recommendation in the report.

  At GeoSolutions, we were investigating how COVID-19 data was being published. We found an initiative, the COVID Tracking Project that actually does a great job on aggregating data for the US states. They perform quality control, publish the provenance, and make the data available via a simple Data API. If organizations around the world can follow simple APIs like the one mentioned, it will be easier to aggregate data in our current and other health emergency events. Also, fortunately, OGC is working on simple APIs that will enable government, agencies and projects (similar to the COVID Tracking Project), to share data via an open-standard simple API

  Based on the previous mentioned project, and the simplicity of their API, we wanted to develop a simple sleek dashboard for tracking COVID-19 cases in the US. We wanted to reuse the best tools that we have in house at GeoSolutions, so we reused MapStore to build such a dashboard; you can reach it live here.

  [caption id="attachment_5240" align="aligncenter" width="1024"] Figure 2 - US COVID Tracking Dashboard with MapStore[/caption]

  The client interacts directly with the API. There is no database on the backend and this is the reason it can be installed in a S3 bucket (which is a cheaper option than using a virtual machine under EC2). The user interface allows to view more than one variable at a time by enabling the user to select from the left side and displaying bubble plots located at the centroids of each state. The user can also view and order the statistics on the right column enabling easy comparison among the states. Hovering over a state shows all the data for that particular state, as it is shown for New York . Also, in our spirit of open source advocates, we have released the code at GitHub under a BSD License.

  Sharing data via open standards is important, as well as, simple APIs that can enable web clients to provide dashboards and critical information to end users. I hope you find this blog useful and can inspire some ideas about sharing and visualizing pandemic tracking.  If you would like GeoSolutions to help with your health data publication, cataloging or visualization needs we are here to help!

  Please don’t hesitate to contact us. We would love to hear how we can help you!

  Cordially,

  Luis Bermudez CEO GeoSolutions USA
• 22 April 2020
• 14:13

  Fernando Quadro: GeoServer 2.17.0 disponível para download

  sur Planet OSGeo

  Ontem, 21 de abril, foi anunciado o lançamento do GeoServer 2.17.0, que já está disponível para download, juntamente com sua documentação e extensões. Esta versão foi desenvolvida com o GeoTools 23.0 e GeoWebCache 1.17.0.

  Nesta versão muitas novas funcionalidades foram adicionadas, confira:

  • MBStyle agora é extensão no GeoServer
  • Navegador de Recursos disponível no GeoServer
  • Gerenciar segurança por recurso no GeoServer
  • FlatGeoBuf: Novo Community Module do GeoServer
  • Melhorias no GeoWebCache
  • Melhorias no serviço WMS do GeoServer
  • Melhorias na OGC API do GeoServer
  • Melhorias na renderização do GeoServer

  Fonte: GeoServer Blog

• 10:24

  GeoTools Team: GeoTools 23.0 released

  sur Planet OSGeo
  The GeoTools team is pleased to share the availability GeoTools 23.0: geotools-23.0-bin.zip geotools-23.0-doc.zip geotools-23.0-userguide.zip geotools-23.0-project.zip This release is published to our new osgeo maven repository, and is made in conjunction with GeoServer 2.17.0. OpenSource is a team effort and we would like to thank everyone who helped to test the release candidate: Ian
• 9:13

  GIScussions: Mapping Israel from biblical times to the present day

  sur Planet OSGeo

  I first presented this talk in 2018 and I’ve since been invited to talk on the subject a few times. Each time the presentation evolves as people ask great questions which encourage me to find new material or friends send me interesting new sources.

  I did a zoom presentation to a group at my Synagogue last weekend which was recorded. There were a few glitches with the technology (including the red line that someone accidentally drew on the screen part way through!) and I lost my connection a couple of times. I’ve edited as best as I can but the first few sentences are missing.

  I’ve tried to contrast the different focuses of Christian and Jewish map makers when mapping the Holy Land and how their maps evolved over time. There are a heck of a lot of maps, some are exquisite, some are historic and one or two may be being shared for the first time.

  It’s difficult to talk about Israel in almost any context (yes, even cartography) without it becoming contentious, even more so as a politically liberal Jew. I’ve tried my best to avoid that and to stick to the maps, I hope you enjoy them.

• 9:00

  Lutra consulting: QGIS development on macOS

  sur Planet OSGeo

  We introduced a new packaging and build environment for QGIS and its dependencies for macOS. This will bring a completely new experience for QGIS macOS developers and subsequently, the users.

  Overview of the changes

  • What is new?
  • QGIS development on macOS
  • Development of the QGIS-Deps package
  • Next steps

  What is new

  In 2019, we upgraded the QGIS macOS packaging to address several issues at the time. This was made possible with the help of the QGIS project and donors who supported our work.

  The upgraded system had a more transparent and automated packaging approach. But it came with its own limitation. We have been using Homebrew to fetch the QGIS dependencies and to compile only QGIS for the LTR, PR and nightly releases. The main problems with this approach are:

  • Homebrew can only support one version of a package. This will limit QGIS to be built against multiple versions of, for example GDAL or Proj libraries. In one hand, we want QGIS nightlies to use more bleeding edge versions of the dependencies (e.g. for plugin or core developers) . On the other hand, using a more stable and tested versions of the dependencies for PR or LTR are not recommended (e.g. users and organisations). OSGeo4W offers the same approach for different versions of QGIS in Windows. Unfortunately, Homebrew does not offer such an option.

  • Continuous integration has been a major part of QGIS infrastructure to ensure pull requests by developers do not break workflows in certain Operating Systems. Microsoft Windows and Linux have been well supported in the CI. But with the macOS packages, it was left to user to test and report back any bugs after Pull Requests were merged to QGIS source code.

  With the recent work, we have addressed both of the above issues. QGIS and almost all of its dependencies are built from sources. It will be also possible to easily integrate the code with the current CI for macOS with GitHub Workflows. This will bring more stability and control over the way we build and package QGIS for our users, whilst helping developers to identify issues with their pull requests for macOS platform, before merging them to the QGIS source code.

  QGIS development on macOS

  If you want to check the latest QGIS master on macOS or tweak the code to see some new exciting features, now it should be easier with the following steps, to compile QGIS from source code an a clean machine:

  1. Install XCode

  • Upgrade to latest MacOS version
  • Install latest XCode from the official AppStore
  • Open XCode and accept license
  • Install command line tools from XCode, AppStore or from command line by sudo xcode-select --install

  2. Install Qt and QGIS-Deps

  • Download the latest install qgis-deps script and check the version of Qt required
  • Install the required Qt version referenced from the official Qt download area. Or alternatively download qt-version.tar.gz from deps area
  • Download latest qgis-deps package too.
  • Run install_qgis_deps.bash script to install Qt in /opt/Qt/5.14.1/clang_64 and QGIS-Deps to /opt/QGIS/qgis-deps-0.3.0 folder. You may need to use root privileges or create those folders under /opt/ and assign the right permission beforehand.

  3. Install other tools

  • Install Homebrew
  • Install minimal set of packages required for macOS build tools listed in this list

  You may use MacPorts, Conda or other packaging system, but by the end you need cmake, git, astyle and other useful tools to be on the system PATH

  4. Download and compile QGIS

  • Open the terminal (Note that the qgis-deps package is not yet signed, so you may need to add Terminal to System Preferences -> Security & Privacy -> Privacy -> Developer Tools)
  • In your work folder (e.g. ~/Projects/), clone QGIS with git clone git@github.com:qgis/QGIS.git
  • Create a build folder mkdir -p ~/Projects/build-QGIS
  • Go to the created empty directory cd ~/Projects/build-QGIS
  • Run CMake to generate the build system (use your download qgis-deps and qt package)

    QGIS_DEPS_VERSION=0.3.0;\
    QT_VERSION=5.14.1;\
    PATH=/opt/QGIS/qgis-deps-${QGIS_DEPS_VERSION}/stage/bin:$PATH;\
    cmake -DQGIS_MAC_DEPS_DIR=/opt/QGIS/qgis-deps-${QGIS_DEPS_VERSION}/stage \
        -DCMAKE_PREFIX_PATH=/opt/Qt/${QT_VERSION}/clang_64 \
        ../QGIS
    

  Note that all libraries are picked from qgis-deps and not from system /usr/lib or Homebrew’s /usr/local/ or system Frameworks /Library/Frameworks/. Especially check Proj, GDAL, sqlite3 and Python paths. You should see output similar to this:

  -- QGIS version: 3.13.0 Master (31300)
  -- Found OpenCL: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/OpenCL.framework (found version "1.2")
  -- Found OpenCL C++ headers: /Users/peter/Projects/mesh/QGIS/external/opencl-clhpp/include
  -- Found GRASS 7: /opt/QGIS/qgis-deps-0.3.0/stage/grass78 (7.8.2, off_t size = 8)
  -- Looking for openpty
  -- Looking for openpty - found
  -- Found Proj: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libproj.dylib version 6 (6.3.1)
  -- Found GEOS: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libgeos_c.dylib (3.8.1)
  -- Found GDAL: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libgdal.dylib (3.0.4)
  -- Found Expat: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libexpat.dylib
  -- Found Spatialindex: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libspatialindex.dylib
  -- Found Qwt: /opt/QGIS/qgis-deps-0.3.0/stage/lib/qwt.framework (6.1.4)
  -- Found LibZip: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libzip.dylib
  -- Found libzip: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libzip.dylib
  -- Found Sqlite3: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libsqlite3.dylib
  -- Found Protobuf: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libprotobuf.dylib (found version "3.11.4")
  -- Found Protobuf: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libprotobuf.dylib
  -- Found ZLIB: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libz.dylib (found version "1.2.11")
  -- Found zlib: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libz.dylib
  -- Found PostgreSQL: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libpq.dylib
  -- Found SpatiaLite: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libspatialite.dylib
  -- Qt WebKit support enabled
  -- Found Qt version: 5.14.1
  -- Found QScintilla2: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libqscintilla2_qt5.dylib (2.11.4)
  -- Found QtKeychain: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libqt5keychain.dylib
  -- Found QCA: /opt/QGIS/qgis-deps-0.3.0/stage/lib/qca-qt5.framework (2.3.0)
  -- Found QCA OpenSSL plugin
  -- Found Libtasn1: /opt/QGIS/qgis-deps-0.3.0/stage/include
  -- Pedantic compiler settings enabled
  -- Found PythonInterp: /opt/QGIS/qgis-deps-0.3.0/stage/bin/python3 (found suitable version "3.7.7", minimum required is "3")
  -- Found Python executable: /opt/QGIS/qgis-deps-0.3.0/stage/bin/python3
  -- Found Python version: 3.7.7
  -- Found Python library: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libpython3.7m.dylib
  -- Found Python site-packages: /opt/QGIS/qgis-deps-0.3.0/stage/lib/python3.7/site-packages
  -- Found PyQt5 version: 5.14.1
  -- Found SIP version: 4.19.21
  -- Found QScintilla2 PyQt module: 2.11.4
  -- txt2tags not found - disabled
  -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
  -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
  -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
  -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
  -- Performing Test COMPILER_HAS_DEPRECATED_ATTR
  -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
  -- Found exiv2: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libexiv2.dylib
  -- HDF5: Using hdf5 compiler wrapper to determine C configuration
  -- Found HDF5: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libhdf5.dylib;/opt/QGIS/qgis-deps-0.3.0/stage/lib/libz.dylib;/usr/lib/libdl.dylib;/usr/lib/libm.dylib (found version "1.10.0")
  -- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
  -- Found NetCDF: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libnetcdf.dylib
  -- Found LibXml2: /opt/QGIS/qgis-deps-0.3.0/stage/lib/libxml2.dylib (found version "2.9.10")
  -- Looking for updwtmpx
  -- Looking for updwtmpx - not found
  -- Found GSL: -L/opt/QGIS/qgis-deps-0.3.0/stage/lib -lgsl -lgslcblas
  -- Using PROJ 6 srs database.
  -- Ctest Binary Directory set to: /Users/peter/Projects/mesh/build-QGIS/output/bin
  -- Configuring done
  -- Generating done
  -- Build files have been written to: /Users/peter/Projects/mesh/build-QGIS
  

  • Compile QGIS make -j4 and wait for [100%] mark :)
  • Now you can run QGIS with command ./output/bin/QGIS.app/Contents/MacOS/QGIS or open ./output/bin/QGIS.app

  Notes:

  • If you use QT Creator, you can open already generated project to modify files from it.
  • The critical CMake variable is QGIS_MAC_DEPS_DIR and you must ensure it contains valid qgis-deps installation
  • You can add more variables to CMake command to tweak the build settings, e.g. enable 3D with ‘-DWITH_3D’, etc.
  • Consult QGIS’s [INSTALL [https:] for latest developement tips

  Development of the QGIS-Deps package

  If you want to help with development of the qgis packages on macOS, please feel free to contact peter.petrik@lutraconsulting.co.uk. The development is taking place on public QGIS-Mac-Packager repository.

  Next steps

  Currently, we are carrying out the following tasks:

  • to move all-in-one QGIS bundle for LTR/PR/nighlies to use this new package of dependencies. Check out Twitter for for any news on the packages. We are aiming to have the new packaging in place for the QGIS 3.14 release, which will bring GDAL 3 and Proj 6 to macOS users

  • to sign the qgis-deps packages, so that developers do not need to tweak Privacy settings to use it for compiling QGIS and its dependencies.

• 21 April 2020
• 17:17

  GeoServer Team: GeoServer 2.17.0 Released

  sur Planet OSGeo

  Enclosure: [download]

  We are happy to announce GeoServer 2.17.0 release candidate is available for testing. Downloads are available (zip and war) along with docs and extensions.

  This is a GeoServer release candidate made in conjunction with GeoTools 23.0 and GeoWebCache 1.17.0.

  This is an exciting release and a lot of great new functionality has been added.

  Fixes since Release Candidate Bugs

  • [GEOS-5188] – LegendDecoration does not respect target size
  • [GEOS-9537] – Restore plugin is not able to correctly restore styles anymore
  • [GEOS-9551] – Rendering Transformation can cause bad rendering on reprojection to 3995
  • [GEOS-9559] – GeofenceAccessManager fails to cut geometries in coverages
  • [GEOS-9566] – Migrate to repo.osgeo.org repository
  • [GEOS-9567] – [Backup/Restore] Rest Controller not able to backup secured resources

  Improvement

  • [GEOS-9512] – RasterDownload on Heterogeneous CRS Mosaic: avoid reprojection of granules having same CRS as the target CRS.
  • [GEOS-9543] – GeoServer REST documentation: Parser error duplicated mapping key

  MBStyle module graduated to extension

  The MBStyles module has received a deep review and many visual differences have been resolved, to the point that it can now display properly some of the OpenMapTiles styles as-is, with good fidelity, here is an example:

  

  The module has also graduated to extension status, so you will now find it in all releases.

  MBTiles community module reading vector tiles

  The above map has been rendered not with one functionality, but two! Did you know one can put vector tiles in a MBTiles file? The community module mbtiles-store can read both raster and vector tiles now, and will serve the tiles for vector rendering.

  It makes the perfect match with the MBStyle module, one can read vector tiles and render them using the styles they were designed for. Want to give it a quick try? Go to the OpenMapTiles web site and download an area of interest, for personal usage, and configure all layers. Then grab the osm-bright-gl-style, set it up, and configure it as a “style group” layer group type. Done:

  Web resource extension

  Ever had to fiddle with the data directory on a remote server, maybe trying to setup the control-flow configuration, or upload a Freemarker template? It can be annoying business, one often needs some sort of side access, like SSH. The Resource Browser module, freshly graduated into a supported extension, comes to the rescue, providing a tools page where administrators can browse the data directory, inspect files, edit them, and upload new ones too:

  Manage authorization from each resource

  Ever added a new layer and forgot to setup security for it? It’s a common occurrence, when the configuration of the layers and its security are done in different pages.

  GeoServer 2.17 has a new “Security” tab in each page, allowing you to setup the security for a given resource directly in its configuration page:

  

  Edit security settings there, and the layer security configuration will be updated as a consequence. The same goes for workspaces and layer groups.

  Track last change of each resource

  GeoServer 2.17 tracks, and allows to show, the date of creation and last modification of major configuration resources, such as workspaces, stores and layers, in their respective list page.

  Turn it on in the server configuration page, and see the result in list pages:

  

  This new setting is off by default, you’ll have to go and explicitly turn it on if you care to see the dates.

  Map rendering improvements

  GeoTools label “shield” support already allowed to put together a graphic along with a label, with the goal of supporting road label shields. GeoServer 2.17.0 includes the ability to lay them out separately, so that the mark and labels are not centered with each other but, for example, one above the other. This allows to setup point markers that appear only as long as their label is showing up too:

  

  It’s also possible to setup a background color for the map at the style level, using a new Background element inside UserStyle. Background is a fill:

  <?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="http://www.opengis.net/sld" xmlns:sld="http://www.opengis.net/sld" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" version="1.0.0">
    <sld:NamedLayer>
      <sld:Name>Sea color background</sld:Name>
      <sld:UserStyle>
        <sld:Name>Background sample</sld:Name>
        <sld:Background>
          <sld:CssParameter name="fill">#F2EFE9</sld:CssParameter>
        </sld:Background>
        <sld:FeatureTypeStyle>
          <sld:Rule>
             ...
          </sld:Rule>  
      </sld:UserStyle>
    </sld:NamedLayer>
  </sld:StyledLayerDescriptor>

  

  Traditionally one can render multi-script labels by specifying a long list of family names in the “font-family”, e.g.:

  <sld:Font>
    <sld:CssParameter name="font-family">Noto Sans Regular</sld:CssParameter>
    <sld:CssParameter name="font-family">Noto Sans Adlam Regular</sld:CssParameter>
    <sld:CssParameter name="font-family">Noto Sans Adlam Unjoined Regular</sld:CssParameter>
    <sld:CssParameter name="font-family">Noto Sans Armenian Regular</sld:CssParameter>
    <sld:CssParameter name="font-family">Noto Sans Balinese Regular</sld:CssParameter>
     ...
  </sld:Font>

  If the font names all share a common prefix, it’s now possible to be more concise and just use a function instead, specifying the common base name, letting GeoServer find all possible variants e.g.:

  <sld:Font>
    <sld:CssParameter name="font-family">
      <ogc:Function name="fontAlternatives">
        <ogc:Literal>Noto Sans</ogc:Literal>
      </ogc:Function>
    </sld:CssParameter>
  ...
  </sld:Font>
  

  As a further labelling related feature, when performing conflict resolution the map renderer can now try to shrink the size of labels in search of a place to fit them. The new vendor option is called “fontShrinkSizeMin” and represents the minimum size to use. Here is an example, the two polygons share the same TextSymbolizer definition, in one the label size has been reduced to allow the label to fit:

  

  Moving to line symbolizers, it’s now possible to drape a linear mark along a line. Before, it was just possible to repeat it along a line, but the output would not have looked continuous, especially at turns. Now, if you have a mark that starts and ends at the same height, it can literally be made continuous along the line, e.g. using this style:

         <LineSymbolizer>
           <Stroke>
             <GraphicStroke>
               <Graphic>
                 <Mark>                                  
        <WellKnownName>wkt://LINESTRING (0 0, 0 -0.5, 0.5 -0.5, 0.5 0.5, 1 0.5, 1 0)</WellKnownName>
                   <Stroke>
                     <CssParameter name="stroke">0xFF0000
                     </CssParameter>
                     <CssParameter name="stroke-width">2</CssParameter>
                     <CssParameter name="stroke-linecap">round</CssParameter>
                   </Stroke>                                           
                 </Mark>            
                 <Size>20</Size>                            
               </Graphic>                
             </GraphicStroke>            
           </Stroke>       
  <VendorOption name="markAlongLine">true</VendorOption>             
         </LineSymbolizer>
  

  Results in the following (you cannot see at first it, but the size of the mark can be slightly altered to fit the segments length, and if it’s not enough, it gets cut and reconnected):

  

  As a final note, there has been a number of small improvements to rendering performance, that will be especially visible when rendering a complex map, with many rules, features to be rendered, and labels (you know, like OpenStreetMap).

  Enabled/advertised for layer groups

  Up to now, the ability to enable/disable and advertise was limited to layers. No more, in GeoServer 2.17 you can now do the same with layer groups:

  Custom WMS dimension for vector layers too

  GeoServer supports standard WMS dimensions, TIME and ELEVATION, on both raster and vector datasets. However, user defined dimensions, also known as custom dimensions, were supported only by raster layers (typically, image mosaics). You can now configure them on vector layers as well:

  WMS cascading improvements

  The WMS cascading functionality has seen several improvements, including:

  • Possibility to choose the cascading format, expose the remote layer styles, while choosing which ones to advertise.
  • Possibility to configure min/max scale denominators for cascaded layers, as well as restrict cascading to the bounding box declared in the capabilities document.

  GeoWebCache love

  Significant improvements have been made to GeoWebCache and its integration with GeoServer, including:

  • Much better startup performance when integrated in GeoServer, the time to load the tiled layers configuration is a fraction of what it used to be.
  • Much faster tile layer listing in the GeoServer “tile layers” page
  • File system tile layout can be configured between classic (small folders), XYZ and TMS (for static cache generation)
  • Better control over failed tile seed operations. Seeding threads used to stop at the first failure, now error tolerance can be configured on the single thread and across the seed job:

  JSON-LD community module

  GeoServer 2.16 introduced a number of improvements in the WFS GeoJSON complex feature output. This release adds instead support for JSON-LD, as a community module.

  Unlike the GeoJSON approach, based on automatic conventions, the JSON-LD module is driven by configuration, a JSON file giving the output format directives on how to encode the output based on complex input features.

  The output format is available for both the WFS and new OGC Features API modules

  OGC API community module updates

  The OGC API community module delivers latest updates for OGC API services:

  • An up to date OGC Features API, updated to the last official release, with draft extensions to support filtering and multiple CRSs, along with tiling vector data
  • A OGC Tiles API, providing tiled collections in both rendered (maps, pngs, jpeg) and data (vector tiles) format, with draft extension to support on the fly filtering
  • A draft implementation of the OGC Styles API, supporting description and discovery of styles in multiple formats, and links from collections to their relevant styles, and back.
  • Two more experimental APIs, image API to manage image mosaic contents, and changeset API to figure out which areas of a tiled collection changed as a result of changes to the image mosaic backing them.

  Development is still heavily ongoing, and specs are still evolving at a fast pace, but we invite you to try them out, enjoy their simplicity, and contribute to their evolution.

  FlatGeoBuf community module

  Are you using GML or GeoJSON to fetch data client side, and you’re not happy with the data transfer performance? You need to actually use the geometries client side, for editing, analysis and topological operations, and would like to avoid the clipping done in vector tiles?

  Then you are the perfect candidate to try out our new FlatGeoBuf output format community module. FlatGeoBuf is “a performant binary encoding for geographic data based on flatbuffers that can hold a collection of Simple Features including circular interpolations as defined by SQL-MM Part 3.” While new, it’s making its way in several open source projects, it’s supported by the latest versions of GDAL/OGR and easy to embed in both OpenLayers and Leaflet. The format can also be streamed out, and rendered progressively client side, like in this OpenLayers demo.

  This is just a screenshot, please follow the link to play with it live! And more!

  There are several other new features and improvements, including:

  • Curved geometries are now supported in SQL Server too, in addition to the existing support for PostGIS and Oracle.
  • Support for workspace specific stored queries.
  • java.util.Math has been exposed in Freemarker templates.
  • It’s now possible to contribute an extension without signing an OSGeo CLA, as long as it’s self-contained and has a license compatible with GeoServer own.
  • The ncWMS compatibility community module has been improved, allowing to query a time list or a time range in GetTimeSeries, as well as ignoring NODATA pixels.
  • When renaming the layers, the pertinent authorization rules will be updated to match.
  • GeoTools has a new “ElasticGeo” community module, which allows to read data from ElasticSearch geo extensions. It still needs a nightly build packaging in Geoserver, volunteers welcomed.
  • GeoPackage can now be used with WMS and WFS time support.
  • Stand alone GeoWebCache has a new Swift blob store module, the integration with GeoServer would require custom packaging for it, volunteers welcomed.

  Find out more in the release notes.

  About GeoServer 2.17

  Additional information on GeoServer 2.17 series:

  • FOSDEM GeoServer Orientation presentation (slides|video)
  • Full OSM data directory for GeoServer available on GitHub
  • Code of Conduct
  • Release notes (2.17.0, 2.17-RC)

• 11:00

  Mapgears: What's new in eVouala version 13?

  sur Planet OSGeo

  

  A lot has changed in eVouala these past few months and we are very proud of all the new features that have appeared in the platform to better serve our users!

  Without further ado, let’s get started!

  Library

  The library is where all of your data sources are centralized: Excel CSV, Shapefiles, geodatabases and web services can all be found in this section of the platform.

  New data source options

  

  In version 13 of eVouala, we have added a whole new set of data connectors and import options for more flexibility. These new options include:

  • AIS feed connector
  • URL connector (to fetch data from the Web)
  • Geofence connector
  • ArcGIS Online connector
  • SPOT and Garmin InReach feeds

  New and updated basemaps

  

  As usual, we updated our existing basemaps on a quarterly basis with the most recent data from OpenStreetMaps, while also correcting some issues with character sets.

  Two new basemaps have been added to the platform:

• A terrain-centric basemap
• A streets-centric basemap
Recovering deleted data



Have you ever deleted a file permanently just to regret it a few days later where it would save you countless hours? I know it definitely happened to me more than once.

That’s why we implemented a “Trash” section where all of your deleted data, maps, apps and other platform resources are temporarily kept. If you need to recover one of these elements, you can just navigate to the Trash and click recover.

Maps

The Maps section is where you interconnect, filter and customize the presentation of your data in a map format.

Introducing the Query Builder



The Query Builder allows you to separate your data in different classes according to specific values to customize the presentation on the map.

With an intuitive graphical interface, it is easier than ever to create custom filters to really get the functionality you are looking for.

Automatic categories



Going even further, eVouala can now automatically detect patterns in your datasources to suggest filters and speed up the map creating process.

Importing maps inside other maps



Another quality of life improvement that arrived in the version 13 of eVouala is the ability to import a map inside another map.

More precisely, you can now import every datasource, filter and customization that already exist inside a map instead of importing them separately.

Toggling classes



It is now possible to individually display or hide a specific class of a datasource inside the layer tree.

Easy graduated legends



Want to display your data as a range of colors depending on its value? We added an intuitive graphical interface to create customized graduated legends.

Web Apps

The Web Apps section is where you take your Maps to the next level. You can add various tools (measure, print, etc.), data analytics and custom code.

Enhanced App Studio



The app studio is where you can pick and customize all of the tools you want to appear on your applications. It has been improved to make it more user friendly, replacing the JSON structure with graphical components.

Movable Layer Tree



In order to get a bit more map area, you can now put the Layer Tree inside the data browser.

New toolbar options



The toolbars of the platform have been reworked to offer a better user experience and just look slicker overall.

Dock/Undock your Apps



A big feature coming to version 13 of eVouala is the ability to dock and undock your web applications.

Historically, you could only use cloud platforms while connected to the Internet, but the undocking feature comes to change that. You can now use the app while offline and push your modifications to the server once you are able to access the Internet.

Faster filter options



The search functionalities used to filter data have been improved to be able to smoothly sift through millions of records.

Mouseover data



Pretty self-explanatory, you can now have your users see the data by just hovering their mouse over it.

Areas of interest



Version 13 introduced the ability to save your favorite areas of the map (or Areas of interest), allowing you to quickly navigate between zones that are important to you.

Patterns



Definitely one of the most powerful features of eVouala, patterns empower users who are familiar with code (CSS and JavaScript) to have fine control over the output and appearance of data both in the data browser and individual data popups.

Administration

The administration section regroups all the users, groups, permissions and back-end functionalities of eVouala.

Refined permissions system



The permissions system has been enriched with roles, privileges and designated managers for finer control over who can access which resources.

Subscription fields



Version 13 introduced the ability to subscribe to a datasource, notifying you every time it is edited by another user.

SMS notifications



Linked to the previous new feature, it is possible to receive SMS notifications through the platform when a specific action is being performed: a datasource was edited, an object entered inside a geofence, a certain value went over a threshold, etc.

User activity log



eVouala now automatically log user activity: log ins/outs, data imports/exports, edits, etc.

Private messages



With version 13, we added to functionality of send private messages to another user from the profile area.

Reports

You can now create simple reports that can be exported in CSV, HTML or PDF. If you wish to create more complex reports, you can use Jaspersoft report templates.