Pieter is a true map geek.
“I wanted to learn the names of the neighbourhoods in #Ghent, so I made me a #puzzle. I added the neighbourhoods in #OpenStreetMap , then made a custom theme in #MapComplete and use the ‘export as PNG’-functuon. The background is a modified stylesheet for @protomaps“
I did say true map geek!!
MapsintheWild The Neighbourhoods of Ghent, piece by piece
I just emailed the Bear 100 race director, Cody Draper, and said that I'm injured and won't recover in time to start in 6 weeks. I'm also too injured to do Black Squirrel in 3 weeks and will be emailing Nick and Brad next.
What's the injury? When I came home from vacation and started to ramp up my running, my right Achilles tendon became sore and very inflamed. On July 17 I went out for a 30 mile run and had to bail at mile 20. I took some time off from trail running and have been chugging on an elliptical trainer at my gym. Yesterday I tried some running on the bike path behind my house and couldn't even go a mile without excruciating pain. I'm calling it, my season is over. The last time I had serious Achilles tendonitis like this was at the end of my ultimate frisbee career 20 years ago. It took 4 months before I could run without pain. I'm going to keep going to the gym, ice and rest, see some specialists, and get ready for 2025.
For the last month of July, one short of 30 new plugins were published in the QGIS plugin repository.
Here follows the quick overview in reverse chronological order. If any of the names or short descriptions catches your attention, you can find the direct link to the plugin page in the table below:
| MariaDB to QGIS |
| Fetches longitude (x) and latitude (y) data from MariaDB and writes it to a Shapefile or GeoPackage and adds it to your map. |
| Print Selection |
| Outputs selected features to text console. |
| DeraPro |
| DeraPro for projects and studies allows the download of the reference spatial data of Andalusia and make a cut of the information for a specific study area. |
| QPackageQGZ |
| QPackage is a tool to save both your QGIS project and data contained in the project to a new directory. |
| ArgentinaGeoServices |
| A QGIS plugin to import WMS Geoservices from Argentina. |
| T Vertical Sessions |
| Used to Vertical Sessions of Lidar Point Cloud. |
| BuenosAires Converter |
| A QGIS plugin that converts layers to EPSG:9497. |
| Make Sector |
| Plugin to create sector, circle radius, and spidergraph delimited and vector layer. |
| CBERS-4A WPM Explorer |
| The CBERS Explorer is a specialized plugin developed to facilitate the search and retrieval of images from the China-Brazil Earth Resources Satellite (CBERS) program, specifically focusing on the CBERS-4A satellite with Wide Field Imager (WPM) data. |
| FPT Plot Alocation |
| Plot alocation for forest inventory. |
| QGISpell |
| Creates context menu spell checking for attribute data based on ENCHANT libraries. |
| ur-scape Data Importer |
| Import data to ur-scape. |
| MorphAL |
| MorphAL plugin for QGIS. |
| LER+ |
| Nem adgang til LER2 forespørgsler. |
| Threshold to ROI |
| Create ROI (Region of Interest) with threshold values. |
| Spell Checker |
| Check the spelling of words in Print Layout elements. |
| Filter By Selection |
| Filter a given layer by the selected feature and attribute of another layer. |
| Natur i Norge kartlegging |
| Natur i Norge (NiN) mapping tool. |
| AIAMAS – AI-Assisted Map Styler |
| Symbolize your vector layers in seconds. |
| Sentinel 2 Image Downloader |
| This plugin allows users to download Sentinel-2 images. |
| MapSafe |
| Safeguard datasets using masking, encryption and notarisation. |
| GPX Maker for GARMIN® devices |
| This plugin exports GPX files for GARMIN® devices. |
| QGIS Sound Effects |
| Add sound effects to QGIS to make work less boring. |
| Mosaic Tool |
| A plugin to mosaic bands from selected raster layers. |
| Polaris |
| QGIS interface for Polaris through Polaris-Studio |
| ArcGeek Calculator |
| A comprehensive toolset for coordinate calculations, conversions, spatial operations, watershed analysis, land use analysis, and flood simulation in QGIS. |
| Auxiliary Labeldata Importer |
| Helps you to import Labeldata, stored in an auxiliary Layer from another Project. |
| Sections |
| Creates a section polygon layer from a point layer. |
| Slownik warstw |
| Tworzy słownik w formie pliku txt rozdzielanego tabulacjami dla wybranych warstw, program pozwala na eksport pełnych nazw pól danej warstwy oraz wersje jako powstanie po zmienie z gpkg do shp. |
Aprenda a criar a sua própria Infraestrutura de Dados Espaciais com o GeoNode, uma plataforma para gestão e publicação de dados geoespaciais que reúne projetos open source maduros e estáveis sob uma interface consistente e fácil de usar, permitindo que os usuários, compartilhem seus dados de forma rápida e fácil.
Este curso visa capacitar os profissionais no uso eficiente da plataforma GeoNode, e tem como objetivos:
Familiarizar os participantes com os conceitos fundamentais do Geonode e suas capacidades.
Explorar o funcionamento de servidores de mapas e seus benefícios.
Apresenar como realizar a criação de usuários e grupos de acessos às suas informações.
Ensinar como realiza a criação de seus Mapas, Dashboards e GeoStories.
Realizar a integração do Geonode com o QGIS através de plugins.
Quer saber mais?
O Curso é oferecido na modalidade EAD Ao Vivo, com uma carga horária de 18 horas divididos em 6 encontros. Porém, essas aulas são gravadas e ficam disponíveis ao aluno por 12 meses em nosso portal do aluno.
Então, se por acaso você não puder comparecer em alguma das aulas ao vivo, não se preocupe, você poderá rever a aula gravada a qualquer momento.
Ficou interessado?
Acesse: https://geocursos.com.br/geonode
WhatsApp: https://whats.link/geocursos
¿Te apasionan las tecnologías geoespaciales de código abierto? Si es así, FOSS4G Europe 2024 en Tartu, Estonia, fue el evento que no debiste perderte.
¿Alguna vez te has preguntado cómo el software de código abierto está revolucionando el mundo de los Sistemas de Información Geográfica (SIG)? FOSS4G Europe 2024 reunió a expertos y entusiastas de todo el mundo para explorar esta pregunta y mucho más.
Durante siete días, del 1 al 7 de julio, Tartu se convirtió en el epicentro de la innovación geoespacial. En esta ocasión, nuestro CEO, Ariel Anthieni y nuestro Sales Engineer, Adrián Yoris, tuvieron la oportunidad de participar de este evento.
La conferencia ofreció una serie de talleres interactivos, presentaciones de vanguardia y sesiones plenarias con ponentes de renombre. Uno de los momentos destacados fue la presentación sobre la implementación de SIG de código abierto en proyectos comunitarios, donde se discutió cómo estas herramientas están transformando la gestión de recursos naturales en regiones rurales.
Un ejemplo notable fue el estudio de caso de una comunidad en Estonia que utilizó software SIG de código abierto para mejorar la gestión de sus bosques, resultando en una optimización del 20% en la recolección de datos y una mejor conservación ambiental. Esta historia ejemplifica cómo la tecnología puede ser una fuerza para el bien común.
Además, Ariel fue invitado a participar en el panel “Changing the mindset of ‘Open Source is just for those who can’t afford to pay licenses’”, junto a otros expertos como Codrina Ilie de Terrasigna y Matthias Kuhn de OPENGIS.ch, para compartir su experiencia como CEO de Kan Territory & IT, y comentar sobre cómo las soluciones basadas en código abierto pueden transformar sectores públicos y privados, ofreciendo innovación personalizada e integración eficiente de tecnologías geoespaciales.
FOSS4G Europe 2024 no solo fue un evento educativo, sino también una celebración de la colaboración y la innovación en el ámbito de los SIG. Si te lo perdiste, no olvides seguir las actualizaciones y prepararte para la edición internacional que se realizará en Belém, Brasil. Comparte tus experiencias y pensamientos en los comentarios, y sigue explorando más sobre el fascinante mundo de las tecnologías geoespaciales de código abierto.
¡Nos vemos en Brasil en la FOSS4G Internacional!
Créditos de la Foto: Andres Tennus (fotógrafo de la FOSS4G Europe)
Doug Greenfield shared this wine map “Finger Lakes Wine Center @ Sonnenberg Gardens.”
MapsintheWild Finger Lakes Wines
I came across a brilliant thread on Mastodon by Sarah Dal discussing how she worked out what the most remote post box in the UK was. But there was one remark that bothered me, she said that to convert her lat, lon points to OSGB (EPSG:4326 to EPSG:27700 for the nerds) she had to go to the Ordnance Survey site to find some software to do this. Since she already had the points in QGIS this seemed like an unnecessary side quest to me. When I commented that she could have done this in QGIS she said that she always seemed to get it wrong.
I’m confused by this (and by the many other people who ask questions on gis.stackexchange.com about the same
thing) so I’ve put together this video showing how I would do this. Basically, you right click on the layer
you want to reproject and select export->Save features as and then just change the drop down box to the
projection you need. QGIS will then save the features and add that layer to your project. You shouldn’t see
any difference other than the colour of the points will change (as QGIS assigns a new random colour to the new
layer).
And yes, I really should have split the Northern Irish post boxes out into a separate file and projected them to the Irish grid but this is just a demo.
Garrett Speed shared this “This Afghani restaurant in ‘s-Hertogenbosch has a bread holder with a map of Afghanistan as the base”
MapsintheWild Afghani Bread Holder
You must be logged into the site to view this content.
Harry Wood wrote “We arrived at Ilhabela for some Brazil beach time. It’s an island off the Sao Paulo coast. Here’s the kids getting tactile with a relief map in the hotel.”
Looks like fun
MapsintheWild A Tactile Experience in Ilhabela
Nick Duggan shared this neat map, not sure where he spotted it.
MapsintheWild 30 Minute Walks in Central London
Via Reinder “This fantastic piece of textile art by Miep van Riessen consists of embroidered names of victims, and is at the same time a quite adequate ‘geographical impression’ of the region where the disaster took place: the Dutch province of Zeeland. “
MapsintheWild Watersnood 3
by Luca Congedo (noreply@blogger.com) at August 02, 2024 10:04 PM
Sorry, this entry is only available in French.
Reinder shared this “On the 1st of February 1953 a disastrous flood occurred in the southwest of The Netherlands. More than 1800 people lost their lives and an entire infrastructure was devastated. This is known as the Watersnood, and it is the topic of the Watersnoodmuseum in Ouwerkerk in the province of Zeeland.”
MapsintheWild Watersnood 1
And a new share from LeCatopgrahe with these custom underwear coming from Hop & Down.
MapsintheWild Custom underwear
GeoServer is updating our communication channels!
We know people do not like signing up for mailing lists, Twitter has been Xed out, and it is time to move on.
Welcome to the GeoServer User forum:
Taking part is easy (sign-in with credentials you already have):
Login to discourse.osgeo.org:
Login “with LDAP” to use your OSGeo UserID (also used for other osgeo services).
The button appears greyed out, but this is only poor styling choice. The button is enabled and works.
Use “Log in with GitHub” to use GitHub credentials.
More options are added over time.
You may also use “Sign Up” if you want to create an account just for use with the Forum.
Unsubscribe from geoserver-users email list.
We will continue to operate the geoserver-user list for the month of August, and then do a final synchronization of any outstanding email messages to complete the migration.
Navigate to the category GeoSever / User to enjoy the forum.
Use New Topic to start a new conversation.
To test please send introduce yourself we are looking forward to meeting you.
If you enjoy the out-of-band timezone friendly mailing list experience - Discourse allows you to subscribe to notifications, and use email to post and reply to topics.
Sign-in to Discourse as above.
From your profile preferences, use the email tab to adjust email settings.
IMPORTANT: Email is only sent when you are not logged in to the discourse website!
Navigate to GeoSever User category, and use the bell to change notifications to Watching.
You can then join the GeoServer Users Group.
If you wish to update any email rules the new mailing is user.geoserver.discourse.osgeo.org
You can send email to geoserver-user@discourse.osgeo.org to start a new topic.
To test please send an email to introduce yourself (rather than a test message).
GeoServer is occasionally active on social media:
If you enjoy social media we would love some assistance reposting and highlighting our community activity. Contact us on your preferred social media platform to help out.
How a mechanical issue leads to a new map in the wild. Back home, I had a problem with a lawn mower. I called a friend for help, who finally came with this fabulous T-shirt!
MapsintheWild World T-Shirt
You must be logged into the site to view this content.
Raf shared this “Tasty cupcakes from Forn de Mont-ral, Prades, Catalunya”
MapsintheWild Cup Cakes from Mont-Ral
Today, we celebrate a true geospatial legend: GRASS GIS!
The post Happy 41st birthday, GRASS GIS! appeared first on Markus Neteler Consulting.
Tom MacWright shared this picture of the Panorama of the City of New York, an urban model of New York City and the centrepiece of the Queens Museum. For more information, click here.
MapsintheWild Panorama of New York City
This is literally what I thought when I saw this picture. The sentence makes sense for a French speaker; the English version would be: not mix apples and pears, but I also found apples and oranges. Always happy to learn the usage if you want to comment on our socials.
Anyway, my title is misleading about the subject; the picture shows handkerchiefs from Chris Chambers.
MapsintheWild Do not mix dishcloths and napkins
You must be logged into the site to view this content.
My employer, Elastic, has a number of philanthropic initiatives but definitely the one I love the most is the Volunteering Time Off (VTO). We are given 40 hours per year from our working hours to contribute to projects and initiatives we care about. Employees have full freedom to choose what they want to do with that time and are encouraged to use it.
In my case, over this almost 5 years I have to admit I haven’t used all that time every year but I tried to get the most of it. During COVID I did some remote work for a local NGO that works for fair trade, giving them a webinar about Open Source among other things (see update from December 2019 and following months). I also spent a few days working on some admin tasks for the Open Source Geospatial Foundation and I’ve already written here about a couple sessions I did for Cibervoluntarios, training seniors and teens about safe browsing and email.
Last week I was showcased in the company blog, along with other colleagues, on different projects to contribute to. In my case, last year I joined the mapping efforts after the Morocco Earthquake and took a full day mapping roads and streets of a rural area, as part of the coordinated efforts from the Humanitarian OpenStreetMap team (reported on my October community update). I’m very happy to have this support from my employer to leave things aside when an emergency like this arises, granted there are no other urgent issues at work.
As a personal call to action, I’d love to get back to Cibervoluntarios activities. This year has been quite busy; let’s see after summer if there’s room for getting out and engaging with them.
I know I haven’t updated this site in a while, I’ll write one soon! 😅
We have a new website!
We recently launched our new website at QGIS.org. It is a ground-up overhaul and provides a fresh take on the first contact point for existing or potential users wishing to engage with the QGIS project and discover its value proposition.
A new strategy for QGIS.org websites
In this blog post, we would like to provide an overview of the goals that we had for building the new QGIS.org website and the bigger picture of how this website update fits into the broader strategy for our website plans for QGIS.
About two years ago, we started experimenting with building a new QGIS.org website based on Hugo. Hugo, as a technology choice, was less important than was our intent to develop a more modern site that addressed our strategic goals.
After some ‘in-house’ (i.e. volunteer-based) work to develop an initial version of the site, we received the go-ahead to use QGIS funds for this and put out a call in October 2023 for a company to support our work. This was ultimately won by Kontur.io, who, together with our volunteers, brought the work into high gear.
Initial analysis of the questions and actions to be quickly answered by qgis.orgGoal 1: Speak to a new audience
Our primary goal was to speak to a new audience. We are confident that QGIS can compete with all of the commercial vendors providing GIS software. We didn’t convey that well on our old website. We feel that QGIS was too apologetic in how it presented itself. We wanted a website which inspires confidence while addressing the needs of a corporate or organisational decision-maker who is looking at the QGIS project during their GIS software selection process.
The old website was very focused on the developer and contributor community. Obviously, those aspects are important since, without our fantastic community, the QGIS project would not exist. The messaging around open source is also important. Yet these ideas are secondary to the idea that QGIS is one of the best (if not the best) desktop GIS applications out there on the market – open-source or otherwise. We need to present it in this professional perspective.
So, the first goal was to change the messaging to focus on QGIS’s value proposition and take a very professional approach to presenting ourselves on the website.
User group and requirements analysis for the potential qgis.org visitorsGoal 2: Harmonisation
The second goal was to start the process of harmonising all of our website properties. QGIS.org, over the years, has built many different web properties. For example, there’s the plugins website, the feed, the changelog, the sustaining members website, the lessons website and the certification website, the new resources hub website, the API documentation, the user documentation, the user manual, the training manual, various other documentation efforts, and more. Some of those are combined in one application, There are also some less well-known resources, like our analytics.qgis.org and another one for plugin analytics. In short, we’ve a lot of resources!
With so many different web properties, they’ve devolved over time: each has its own look and feel, navigation approach and how you interact with it. Some of them were translated, and some of them were not. We want to harmonise all of these sites so that the user does not notice any change in user experience when they move from one QGIS-related site to another.
Goal 3: Harmonising deployment
In the underlying process of these changes, we’re also redeploying all of the websites on new servers, which are more up-to-date and use better security and maintenance practices. Plenty of work is happening in the background to ensure that all of the servers are in a better-maintained state, document how they’re maintained, and so on.
Goal 4: A hub and spokes
The objective of the new site design is to allow quick movement between the QGIS auxiliary sites. The QGIS.org site will form a hub that effortlessly takes visitors to whichever QGIS-related site they need to complete the task they are busy with. If you’re moving between these sites, the experience should be seamless. You should not really even be aware that you’re moving between different websites. Other than looking at the URL bar, the user presentation and experience should be harmonious between all of them.
One way we are planning to achieve this is to have a universal menu bar and footer. You will see that in the new website’s design, there is a menu bar across the top. This menu bar has two levels: the top menu and the second level, where the search bar is.
The universal menu bar In this second row, auxiliary sites will have their own sub-menu whilst keeping the shared top-level menu. So if you, for example, are moving around in plugins and want to review the plugin list or submit a new plugin, all of that navigation will be on the second line where the search bar is currently. Regardless of which subdomain you are on, the top-level menu bar will be the same, allowing you to easily navigate back to the hub or to another subdomain.
The footer will be unified and shared between all sites, and the cascading style sheets and styling will be unified across all of the QGIS websites.
In the next phase, we will work to achieve this coherence across all the websites, though we still have a few more tweaks to make to the qgis.org site first.
Goal 5: DOTDOTW – do one thing, do one thing well
We plan to break some auxiliary websites apart into separate pieces. So, for example, the changelog management, certification management, sustaining members management, and lessons management are all in one Django app. We will split them into small single-purpose applications using some common UX metaphors so that each is a standalone application that makes it easy for a potential contributor to understand everything the application does. This will also simplify management as we can upgrade each auxiliary site on separate development cycles. We will also finally have semantic URLs, e.g. certification.qgis.org, to take you to the different areas of interest on the site.
The plugins.qgis.org is also going to be refactored so that it just has plugins and not the resource sharing we’ve added in the last few years. The resource sharing will go into its own subdomain. Similarly, the Planet website will get split into its own website (the planet is a blog aggregator or RSS aggregator) that will be in its own managed instance. Some other components (like the analytics) are difficult to split out like this because they’re linked to the same database. We will try to make sure that those are more discoverable and theme them as much as possible to match the rest of the website experience.
Goal 7: Encapsulation
Another goal we had for the QGIS.org makeover was to make the site performant and self-contained. By self-contained, we mean that it should not ‘call’ out to CDN, Google or other platforms for resources like fonts, CSS frameworks, javascript libraries, etc. There were two reasons for this:
Our approach also facilitated the creation of a very performant website, as you can see here. We will try to adhere to these principles for the auxiliary site updates we do in the future, too.
The question has come up: Why did we not want to translate the new QGIS.org when it was translated before?
Firstly, we should make it clear that we do not plan to remove translations from the user documentation, the user manual, and so on, where we think they have the most value.
For the main QGIS.org site, we question whether there is a high value in translating it. Here are some reasons why:
1. Lingua franca: If you are an IT manager in a non-English-speaking country and you want to evaluate some software, you’re going to run into a product page that presents itself in English – it is the norm for IT procurement to work in English for reviewing software products and so on.
2. Automation: Automated translations inside browsers are getting better and better. While these translations are still not completely adequate, we think they will be in one or two years’ time.
3. Translation integrity: Our pursuit of Goal 1 means that we would no longer find it acceptable to have partial website translations. We also need to ensure that the wording and phrasing are consistent with the English messaging. We also have concerns about the QA process regarding trust and review – we want to ensure that any translation truly reflects the meaning and intent of the original content and has not been adjusted during the translation process.
4. Cohesion: Our most important point is raised if we go back to this idea of cohesion between the different websites like QGIS.org, plugins.qgis.org and so on. As well as having the same styling, we also don’t want to switch between languages as you hop between the sites. We aim to present them all as one site. If we translate QGIS.org and then take you to our auxiliary sites, e.g., plugins.qgis.org, the feed, or certification pages, which are in English only, the experience is jarring.
So we must either translate everything into all of the same languages, or work in English. Translating everything is a mammoth task for the translators and for us to retrospectively add translation support to each platform. Thus, we prefer the approach of harmonising everything to one language and then focusing our translation efforts on three areas:
We can leave the rest of the experience in English and instead focus on harmonising, for now, both in terms of look and feel and the technology used.
When we consider everything as one big website and what the bigger plan is, it is hopefully clearer why we didn’t think translating the landing page and QGIS.org was the best approach.
We hope to use more QGIS funding to support this work in the future. We’re also hoping to work again with Kontur to start moving all these auxiliary sites into their own projects, applying our style guidelines to each. Independently of that, Tim (volunteer), Lova (QGIS funded), and others are already getting started with this process.
Do you have strong opinions about the website? Contact Tim on the PSC mailing list if you would like to get involved as a volunteer. We would love to hear from designers, word smiths, marketers, information architects, SEO specialists, web developers and those who think they can help us achieve our goals.
We hope our goals and process make sense for everybody and that we were able to lay out a clear, logical argument about why we don’t want to translate the new website quite yet. We want to focus on these overarching goals and then return to them later if they are still a priority for people. Everything we have built is Open Source and available at this repo, where you can also find an issue tracker to report issues and share ideas relating to the new website.
Thanks for reading. Go spatial without compromise 
Cheers, Tim, Marco and Anita
