Welcome to Planet OSGeo

June 26, 2025

Prezados leitores,

Se você utiliza o GeoNode e gostaria que ele disponibilizasse como opção de idioma o Português Brasileiro, saiba que você mesmo pode adicioná-lo no GeoNode. Lembrando que este tutorial foi realizado com a versão 4.4.2 do GeoNode, então vamos aos passos:

1. Baixar os arquivos de tradução

> wget https://geocursos.com.br/geonode_ptbr/locale.rar
> wget https://geocursos.com.br/geonode_ptbr/mapstore.rar

Você deve baixar esses arquivos em uma pasta do servidor, eu baixei os arquivos e coloquei-os dentro da pasta /opt/geonode_custom/

Feito isso, descompacte os arquivos e você terá 2 pastas: locale e mapstore

2. Acessar o container do Django

> docker exec -it django4my_geonode /bin/bash

3. Alterar o arquivo settings.py

> cd /usr/src/my_geonode/my_geonode
> vim settings.py

Adicione o seguinte trecho de código ao final do arquivo settings.py

LANGUAGES = (
    ('en-us', 'English'),
    ('pt-br', 'Português Brasileiro'),
)

MAPSTORE_TRANSLATIONS_PATH = [
    '/static/mapstore/ms-translations',
    '/static/mapstore/gn-translations',
    '/static/mapstore/project-translations'
]

Após salvar o arquivo settings.py, saia do container e vá para a pasta onde você baixou os arquivos da tradução.

4. Copiar os arquivos de tradução para o container do Django/GeoNode

> cd /opt/geonode_custom/locale
> docker cp pt_BR/ django4my_geonode:/usr/src/my_geonode/my_geonode/locale
> docker cp en_US/ django4my_geonode:/usr/src/my_geonode/my_geonode/locale
> cd ..
> cp mapstore/ django4my_geonode:/usr/src/my_geonode/my_geonode/static/

5. Reiniciar o container do Django

docker restart django4my_geonode

Agora é só você acessar o seu GeoNode e selecionar o idioma Português Brasileiro

by Fernando Quadro at June 26, 2025 08:32 PM

https://www.osgeo.org/foundation-news/sol-katz-award-for-geospatial-free-and-open-source-software-call-for-nominations-2025/

The Open Source Geospatial Foundation would like to open nominations for the 2025 Sol Katz Award for Geospatial Free and Open Source Software.

The Sol Katz Award for Free and Open Source Software for Geospatial (FOSS4G) will be given to individuals who have demonstrated leadership in the FOSS4G community. Recipients of the award will have contributed significantly through their activities to advance open source ideals in the geospatial realm.

Solomon ‘Sol’ Katz was an early pioneer of FOSS4G and left behind a large body of work in the form of applications, format specifications, and utilities while at the U.S. Bureau of Land Management. This early FOSS4G archive provided both source code and applications freely available to the community. Sol was also a frequent contributor to many geospatial list servers, providing much guidance to the geospatial community at large.

Sol unfortunately passed away in 1999 from Non-Hodgkin’s Lymphoma, but his legacy lives on in the open source world. Those interested in making a donation to the American Cancer Society, as per Sol’s family’s request, can do so at https://donate.cancer.org .

Nominations for the Sol Katz Award should be sent to solkatzaward at lists dot osgeo dot org with a description of the reasons for this nomination (after sending, please wait for the moderator to accept your message). Nominations will be accepted until end-of-day 12th September Anywhere on Earth. A recipient will be decided from the nomination list by the OSGeo selection committee.

The winner of the Sol Katz Award for Geospatial Free and Open Source Software will be announced virtually during the FOSS4G 2025 event in Auckland, New Zealand. The hope is that the award will both acknowledge the work of community members, and pay tribute to one of its founders, for years to come.

It should be noted that past awardees and selection committee members are not eligible.

Past Awardees:

Selection Committee 2025:

  • Jeff McKenna (chair)
  • Frank Warmerdam
  • Markus Neteler
  • Steve Lime
  • Paul Ramsey
  • Sophia Parafina
  • Daniel Morissette
  • Helena Mitasova
  • Martin Davis
  • Venkatesh Raghavan
  • Arnulf Christl
  • Gary Sherman
  • Maria Brovelli
  • Andrea Aime
  • Astrid Emde
  • Even Rouault
  • Anita Graser
  • Ariel Anthieni
  • Sandro Santilli
  • Howard Butler
  • Tom Kralidis

1 post - 1 participant

Read full topic

by jsanz at June 26, 2025 04:32 PM

Vom 02. bis 06. Juni 2025 fand der GeoStyler Code Sprint in Bussigny statt.
13 Personen aus Deutschland, Frankreich und Schweiz haben teilgenommen.
Die Veranstaltung wurde gefördert durch den FOSSGIS e.V..

Unter anderem wurde an folgenden Themen im Rahmen des Code Sprints gearbeitet:

  • OGC API Styles für GeoStyler REST API
  • Verbesserungen an GeoStyler CLI, UI und Demo Anwendung
  • Aufsetzen eines eigenen GeoStyler Servers
  • Weiterentwicklung des ArcGIS und OpenLayers Parsers

GeoStyler REST ist somit ab sofort OGC API Styles konform und bietet die Möglichkeit, einen Kartenstil in unterschiedlichen Formaten auszugeben, bspw. mapbox, OpenLayers FlatStyles, SLD, QGIS. Hierdurch können Kartenstile zentral verwaltet und unterschiedlichen Anwendungen zur Verfügung gestellt werden.

Ein ausführlicher und detaillierter Artikel ist hier zu finden: https://geostyler.org/codesprint-2025/.


Teilnehmende GeoStyler Code Sprint 2025

June 26, 2025 12:00 AM

June 25, 2025

The QGISUC2025 team has done an awesome job recording and editing the conference presentations. All “presentation” type talks where the presenter has accepted to be published are now available in a dedicated list on the QGIS Youtube channel.

I also had the pleasure of presenting our Trajectools plugin and you can see this talk here:

Thank you to all the organizers, speakers, and participants for the great time!

by underdark at June 25, 2025 06:39 PM

It was such a pleasure to be part of the QGIS User Conference 2025 in Norrköping! The event was extremely well organised — a big thank you to the amazing local team for pulling it all together so smoothly. Personally, it felt special to be back in Sweden, almost 20 years after my Uppsala university days. I truly enjoyed giving the opening keynote and sharing the latest from the QGIS project — and of course, showcasing all the QField greatness we’ve been working so hard on 💚


🚀 Talks & Presentations

🎊 QGIS.org updates

As Chair of the QGIS.org association, I had the opportunity to share recent updates from the QGIS community. I spoke about ongoing development efforts, community growth, funding initiatives, and collaborations that help keep the project moving forward.
The focus was on the people who make QGIS possible — contributors, sponsors, local user groups, and everyday users — and how their involvement continues to shape the project’s direction and ensure its long-term sustainability.

👉 Slides here (unfortunately keynotes and workshops were not recorded)


💡 Extending QFieldCloud – Ideas and Practical Examples

In this talk, Michael, one of our Full stack GeoNinja and Web Cartography teacher, explained how QFieldCloud can be extended by integrating additional Django apps. This allowed, for example, the generation of QField projects, reacting to events from fieldwork, adding new websites and APIs, and executing entire QGIS models as QFieldCloud jobs.

After a technical introduction, various practical examples were explored. It was shown how OpenStreetMap data can be fully automated to download offline-capable QField projects. Attendees got inspired by how an own WebGIS is brought to life in QFieldCloud using OpenLayers. Furthermore, he demonstrated how remote sensing data can be downloaded, analysed in a QGIS pipeline, and the results made available in QField projects. Finally, the discussion focused on how these capabilities can be optimally used in combination with QField plugins.


🛣 SIGNALO: An Open-Source Solution for Mapping Road Signs in QGIS 

Presented by Denis, our Industry Solution Team Lead, SIGNALO is a QGIS-based solution for mapping road signs, powered by a PostGIS database. It addresses the challenge of representing vertical data on maps while ensuring compliance with Swiss norms, yet remains highly customizable for use at local, regional, or national levels. Moreover, the flexible design allows for easy adaptation to other countries.

In this talk, Denis explored both the technical foundations of the project and the organizational strategies that enable its open-source development.

📱 1.5 Million Reasons to Use QField

In this talk, I shared our vision for the future of QField — the world’s most popular open-source mobile GIS solution. With over 1.4 million downloads and 500,000 active users, QField is making a real difference for fieldwork around the globe.
I spoke about where we’re headed next, what new features are coming, and how we at OPENGIS.ch are working to empower professionals across all sectors with powerful, flexible, and open tools for mobile geospatial workflows.


💧 Standardizing Groundwater Data Collection with QField

We were excited to see Alexandra Nozik from the Leibniz Centre for Tropical Marine Research (ZMT) present her work on a QField project designed to standardize groundwater data collection in remote tropical regions. The setup uses QGIS layers, predefined parameters, and metadata standards to ensure high-quality, consistent field data. Integrated with QFieldCloud, the workflow improves data accuracy, reduces data loss, and enables real-time collaboration. The project will be published on GitHub as a ready-to-use package, supporting reliable and comparable groundwater data collection across the scientific community.

📱 QField and QFieldCloud – seamless fieldwork for QGIS 

In this workshop, Zsanett, QField Product Manager, went through the complete fieldwork process: setting up a QGIS project, publishing the project via QFieldCloud, collecting data via the QField mobile app and synchronising the field data back to your main dataset in the office. QField works on top of QGIS and allows users to set up maps and forms in QGIS on their workstation and deploy them in the field. QField uses QGIS’s data providers (OGR, GDAL, PostGIS and others) and supports most common file formats. QField combines a minimal design with sophisticated technology that allows intuitive viewing and editing of data. QField’s map rendering is supported by the QGIS rendering engine, so the results are identical and the full range of styling options available on the desktop is available. Editing forms in QField respect the QGIS configuration and are optimised for touch interaction. QFieldCloud makes field collaboration much easier. Participants learned about configuring users with different rights, collecting offline and online data, and synchronizing field data and QGIS project data.


🚀 Our first international QField Day

On June 4th, the first international QField Day took place in Norrköping, right after the QGIS User Conference. This free half-day event was dedicated to QField, QFieldCloud, and the mobile GIS community, bringing together users, contributors, and developers for an afternoon of field-tested workflows, live demos, community stories, and open discussions. It was a great opportunity to connect, exchange ideas, and explore the future of mobile geospatial tools in the open-source ecosystem.
Definitely not our last one. 💚


🤝 Supporting Open Source

We were proud to support QGIS UC25 in Norrköping, Sweden, as Platinum Sponsors — reaffirming our commitment to the open-source geospatial community and the continued growth of the QGIS ecosystem.


👋 Looking Ahead

We’re already looking forward to the next gathering — QGIS UC26 will take place in Switzerland 🇨🇭!

After the conference, I joined the contributor meeting along with four QGIS developers from OPENGIS.ch. It was a fantastic chance to collaborate in person, help shape the future of QGIS, and reconnect with old friends from the community.

by Marco Bernasocchi at June 25, 2025 04:45 AM

June 24, 2025

June 23, 2025

Prezado leitor,

Se você está trabalhando com o GeoNode e está tendo alguma dificuldade para gerar o certificado digital (SSL), vou detalhar como você pode fazer utilizando o Lets Encrypt. Vamos aos passos:

1. Instalar o certbot (para gerar o certificado)

> sudo apt install -y certbot

2. Parar o Nginx

> docker stop nginx4my_geonode

3. Gerar o certificado para o domínio desejado

> sudo certbot certonly -d fernandoquadro.com.br

O certbot irá gerar os arquivos privkey.pem e fullchain.pem na pasta /etc/letsencrypt/archive/fernandoquadro.com.br

4. Copiar os arquivos para o nginx no docker

No container do Ngnix existe a pasta /certificate_symlink, é nela que ficam armazenados os arquivos do certificado SSL. Você precisa então, substituir os arquivos que você criou com o certbot pelos que estão por default nessa pasta. Para isso, entre na pasta onde estão os arquivos que você gerou e execute o seguinte comando:

> docker cp fullchain.pem nginx4my_geonode:/certificate_symlink
> docker cp privkey.pem nginx4my_geonode:/certificate_symlink

Após realizada a cópia confira se está tudo certo. Caso ele tenha criado com o nome fullchain1 ou privkey1, a sugestão é apagar os antigos e renomear os novos.

5. Alterar as variáveis no arquivo .env

Para finalizar é necessário que você altere as seguintes variáveis do seu arquivo .env para https. São elas:

– SITEURL
– NGINX_BASE_URL
– GEOSERVER_WEB_UI_LOCATION
– GEOSERVER_PUBLIC_LOCATION

Lembre-se de alterar também as variávels HTTP_HOST (que ficará em branco) e HTTPS_HOST:

– HTTPS_HOST=fernandoquadro.com.br

Por último, lembre-se de setar as variaveis abaixo, para production:

– DOCKER_ENV=production
– LETSENCRYPT_MODE=production

6. Reiniciar o Nginx

> docker start nginx4my_geonode

Agora é só abrir o navegador e verificar se deu tudo certo e seu GeoNode está com o HTTPS ativado.

Dica: Se precisar conferir o nome dos arquivos, a configuração dos arquivos pem, fica na pasta /etc/nginx no docker no arquivo nginx.https.available.conf

by Fernando Quadro at June 23, 2025 03:09 PM

June 22, 2025

Week 18 was my biggest, most social, most fun, and most satisfying week yet. I did a gravel ride with a friend on Wednesday, hiked to the alpine tundra in Rocky Mountain National Park with my daughter on Thursday, ran in 35 °C heat on Friday, and then treated myself to a fast run up and down Horsetooth Mountain early this morning.

Outside of training, I quit taking Naproxen, continued passive and active heating training, and started seeing a physical therapist about my Achilles tendinopathy. I learned that part of the solution will be loading my calf muscles, but without lengthening the muscle and thus stressing the tendon. The therapist also reassured me that I can run when it feels good. I don't need a boot or crutches or anything like that.

Here are the numbers for the week:

  • 20.3 miles running (and hiking)

  • 14 hours, 59 minutes all training

  • 4,187 feet D+ running (and hiking)

The hike to Flattop Mountain in Rocky was super fun. I loved the chance to spend all day with my adult kid and help her kick off a "couch to Fourteener" program. It was my first trip on foot this season to treeline and above, and I felt good. I was also impressed at how well my Salomon Ultra Glide shoes served on an alpine trail. I'll feel confident wearing them at Never Summer or The Bear, as long as conditions are mostly dry.

https://live.staticflickr.com/65535/54606250897_214f6f386b_b.jpg

A human sitting on a rock overlook, facing a gorge and granite peaks with some stripes of snow.

https://live.staticflickr.com/65535/54607338308_68181796f1_b.jpg

A smooth trail through rocks and tundra well above treeline.

Yesterday (Saturday) I went for a nice long bike ride in the heat of the day. Today I got out of bed early to run in the coolest part of the day. I took just one handheld bottle (2 scoops of Tailwind) and hiked and ran to Horsetooth Mountain via the Spring Creek Trail. I went pretty hard and was just a little off my personal bests (from 2021) for some of the long uphill segments. I'm very excited about this. Consistent training, even if not in my favorite form, has been working.

Coming off the summit, I met a friend and chatted for a while, and then headed down, down, down to my car. I had to take a short walking break after a sharp rock strike on one of my heels, but was otherwise able to run three miles to the bottom without riding my brakes.

Next week is a scheduled rest week. I plan to do some high intensity workouts of shorter duration, some recovery rides, short easy runs, yoga, Pool HIIT, and sauna sessions.

https://live.staticflickr.com/65535/54607437760_e5f972a9d9_b.jpg

Mount Milner and a green valley south of Horsetooth Mountain.

by Sean Gillies at June 22, 2025 11:02 PM

June 21, 2025

Jeremy Garniaux shared these pics from a display in the forecourt of the Gare De Lyon. “A beautiful series of almost MapsInTheWild was waiting for me this morning on the forecourt of the Gare de Lyon this morning, as I arrived.”

I wonder how they chose the images for this display?

by Steven at June 21, 2025 09:00 AM

Welcome to the Living Planet Symposium 2025 in our hometown Vienna! In an effort to help meet the event's sustainability goals, we are refraining from distributing printed materials. Our handouts are instead provided as the following digital files and websites. Find us at our booth F13, level 0 or ...

June 21, 2025 12:00 AM

June 20, 2025

This blog post isn’t about GIS, mapping, conferences or travel, so feel free to skip it if you want. However, if you’re interested in my experiences of becoming a Dad, read on. Be warned - it is quite a long post (~3000 words, ~6 pages) and contains details about birth, C-sections and medical treatment.

Picture of Baby, first of many!

This is the story of bringing our son, Baby Bearman, into the world.

I’m calling him Baby Bearman here a) because we don’t have a name for him yet (you have 6 weeks after birth to decide, and we have been rather preoccupied recently!) and b) I don’t want this blog post to be the first thing that comes up when people search for his name!

Baby Bearman was due on Wed 25th June 2025, but ended up arriving early on Sun 8th June 2025, 2 and a half weeks early (at 37 weeks 4 days). All of us (Baby, Mum and Dad) are now doing well, although it has been quite a struggle at times.

Tue 3rd June

We start our journey at our antenatal appointment on Tue 3rd June, my wife, Louise’s blood pressure was borderline high. The reading was just under the threshold for them to worry about, so the midwife said to keep an eye on it and phone if we have questions.

Sun 8th June ~10am

On Sunday, Louise’s blood pressure was still a little high, so we phoned up the maternity advice line at 10am and they advised us to come in. Things started speeding up then, and happened very quickly, compared to the last 37 weeks /8 months!

We came in, and Louise had a blood pressure series done, where her blood pressure was taken every 5 minutes for half an hour. It was a bit high, so they sent blood and urine off for additional tests, and monitored the baby for an hour. The consultant explained a bit about pre-eclampsia, while Louise’s blood pressure was high, her urine dip test for protein was negative. You need to have both for pre-eclampsia to be diagnosed. To preempt further development of pre-eclampsia, the consultant recommended we consider early delivery of the baby. Usually they would wait until 41 weeks to induce (if the birth wasn’t spontaneous), but he recommended we induce at 39 weeks (18th June). Louise was given medication to reduce her blood pressure and we were booked for a followup appointment on the next day.

Sun 8th June ~4pm

On the way home, Louise developed a headache and took paracetamol. She continued to feel worse, and her headache got worse, so we phoned up (4:44pm). They advised us to come back in. She was feeling sick and threw up in the car. We got to Dorchester, and to the maternity unit. A nurse coming off shift took one look at her and took us straight in. We were in a shared ward and they assessed her. She was also suffering from edema (swelling) during pregnancy, but it had suddenly increased by now. Her blood pressure was higher. They tried to get an IV in but it was quite tricky because the pre-eclampsia makes the blood vessels smaller, compounded by the fact she had thrown up, so didn’t have much liquid left in her. She was given pills to reduce blood pressure but just threw them up again. She was also suffering photophobia - aversion to light - all the way from home into Dorchester, which is another symptom of pre-eclampsia. There were five people around Louise at this point, so it was getting rather crowded. We were moved to a private room. There they managed to get an IV in, done by an anesthesiologist with an ultrasound machine.

I would later discover that if the midwife had trouble getting an IV in, or taking blood, they would ask a consultant. If the consultant couldn’t do it, then the anesthesiologist would try. If they had trouble, they would use an ultrasound machine to see the blood vessels to help them gain access. At this point, Louise needed an anesthesiologist and an ultrasound machine!

They gave her IV paracetamol for her headache (which she would later describe as a migraine) and IV medications to lower her blood pressure. The consultant explained that the blood pressure was a result of the pre-eclampsia, and we later discovered that the pre-eclampsia had come on very very quickly. He said that Louise needed the placenta removed, and therefore needed to give birth. For this she needed an emergency C-section (caesarean section) as soon as possible. Louise’s consent was needed, and the consultant managed to explain the options in a way she could understand in the state she was in. Her blood pressure was still quite high at this point (one reading was 164/111, which is very high). The baby was being monitored throughout all of this, and he was fine. For the C-section operation, her blood pressure had to be under control. Therefore they put her on blood pressure medication via IV, and monitored her from about 7pm to about 10pm.

Sun 8th June ~10pm

By about 10pm, Louise’s blood pressure was under control and we were taken in for the C-section. I had to change into scrubs, and was allowed to be in the theatre with her. There must have been at least 10 people in the room and it was quite a busy experience. We had a great anesthesiologist, who talked Louise and myself through the whole process. Louise chose a spinal tap for pain management; less severe than a general anesthetic and so Louise could be conscious throughout the whole procedure. Her blood pressure was a little problematic, and there were a couple of times where she was quite out of it. Everything went well though and Baby Bearman was born at 22:46.

After they had taken the baby out, I was allowed to take some photos, and also cut the umbilical cord. It was quite a surreal experience and I was privileged to be a part of it.

We had about half an hour in recovery after the C-section. Louise recovered very quickly with the major pre-eclampsia symptoms disappearing as soon as the placenta was removed. We were then transferred to a room, with mum and baby having hourly checks. We had a midwife with us all the time, with a second mid wife there most of the time until 8am.

Mon 9th June

We stayed in the same room for most of the rest of the day. They still took hourly observations, but in general we were left to sleep. The baby slept a bit, but a lot of the time he wanted to be held, and when you are holding a baby you can’t sleep, so we didn’t get much sleep that day or Monday night. Louise was on fluid restriction, so limited to drinking 75ml per hour.

Monday day and evening progressed in a bit of haze. I did go and get some food from the hospital restaurant: a jacket potato at lunch time, which went down well, and some very spicy sweet and sour for dinner, which I had trouble eating. Louise had food brought to her (as the patient) which she demolished very effectively.

At 6:30pm, we were moved to room 4, where we would be for the rest of our stay. Monday night was really hard for both of us, as the baby wanted a lot of cuddles and wasn’t keen on being put down. I did have a bed, so when Louise had the baby I could lie down, but found it very hard to sleep as I was too stressed.

Tue 10th June

On Tuesday morning I went to get cereal in the day room. I sat there to eat it to have a bit of time out of our room, and I was completely overwhelmed. I sat there and cried. I had trouble processing what had happened, and looking back on it now, I was so sleep deprived (no sleep on Sunday night and not much on Monday night) I couldn’t process anything.

Another visitor came over and asked if I was OK. I said both mum and baby were OK (I didn’t realise at this point how serious things had been for Louise or the baby). She said she thought someone had died, based on how I was.

Later on Tuesday morning, one of the midwives visited and we talked a bit. This was mostly how Louise was getting on and how the baby was. Nobody explicitly asked me how I was doing. However, I knew enough about my mental health to realise that I was struggling and that I needed to say something, and this midwife looked like the person to say it to. I said to her I was struggling with everything. She listened and said we could talk. We had a good talk, and I tried to explain how I felt. It was at this point I realised I hadn’t slept for 48 hours+, which contributed to how I was feeling. The midwife explained about how we had to support each other and tag-team with the baby, i.e. I do some feeding and cuddling while Louise rests, and Louise does feeding and cuddling while I rest. She also let us know that it is often the case that the second night after birth (i.e. last night, Monday night for us) was the worst.

Given that we were likely to be in the hospital a bit longer, I was encouraged to go home for a bit of a break. Due to the fact the pre-eclampsia had come on so quickly, and we came in two and half weeks earlier than planned, I had brought no spare clothes with me. We already had stuff packed for the baby (nappies, wipes, etc.) and a couple of bits for Louise (maternity top, change of underwear) but I didn’t have anything. When we left on Sunday I did have the presence of mind to throw some snacks and drinks in a bag which were a life saver.

I went to Sainsbury’s to pick up some muslin and socks for the baby and I had a lovely call from my brother in law, Peter (Louise’s brother). He knew that I was an only child, and he said he knew people would be seeing how Louise and the baby were doing, but he wanted to ask how I was doing. I was touched by this and very grateful for the phone call.

While I was driving home, I had a very deep and meaningful thought. Of course, it seemed deep and meaningful at the time, but I was lacking in sleep, so it could be complete rubbish! I thought that whilst my world has completely changed with the birth of my son, the rest of the world hasn’t changed at all. Everything is exactly the same as it was before he was born. From globally crucial things like the wars in Russia/Ukraine and Israel and climate change, to the mundane and everyday, like the oddly designed set of traffic lights by Asda in Weymouth which you have to be very careful driving through. Since then everything has sunk in a bit more, so I am more used to him being here, and everything seems less “different”.

Tuesday night in hospital was better. We planned a bit and managed to tag-team, with me doing some feeds while Louise rested and Louise doing some feeds while I rested. We both got a bit of rest, although looking back now, we both still slept badly in the hospital, but it was so much better than the night before by comparison! I had jacket potato for dinner that evening.

Of course, Louise was in quite a lot of pain from the C-section. She had been given regular paracetamol, and at this point two doses of ibuprofen. One midwife on Tuesday evening refused to give Louise ibuprofen, despite her having it previously. The midwife said it wasn’t written on her chart, so she couldn’t have it; despite Louise’s protests that she’d had it twice already! She gave Louise dihydrochloride instead which was supposed to be a more powerful painkiller, but it didn’t make much impact on Louise’s pain. In fact the pain got worse, because she didn’t get the ibuprofen. Later on, Louise said this issue with the pain medication set back her recovery.

After the shift change, a new midwife came on and gave Louise ibuprofen when she asked for it, which helped with her pain. Apparently the ibuprofen had actually been written on Louise’s chart, but in “a funny place”. We never established what that meant.

Later on the same evening Louise was given a dose of Nifedipine, medicine to manage her high blood pressure. Her blood pressure had been monitored 4 hourly and was still high, an after effect of the pre-eclampsia. In the early hours of the morning, very suddenly Louise had heart palpitations and a very fast heart rate. It was quite scary for her. She used the call button, but by the time someone had come the palpitations had eased a bit. A cardiac nurse did come in and run an ECG test to check Louise’s heart, and everything looked fine. She didn’t have the palpitations again. Louise had been prescribed Nifedipine every twelve hours after the C-section - 9am and 9pm, 20mg. When 9am came around, the Nifedipine pills looked different to the ones she’d had at 9pm the previous night. At 9am she had two small pink pills which we were told was 20mg; at 9pm night before she’d had two different pills (maybe a different brand), which she was told was 2 x 10mg but we suspect were 2 x 20mg pills. This probably caused the heart palpitations. This was rather worrying and we have tried to keep a close eye on the pills since. This is quite tricky in hospitals, particularly when sleep deprived and when the pills are delivered in a small paper cup, it’s hard to know what they are. Also when they are delivered with a not great bedside manner, this makes it harder to ask and check what you are being given.

Wed 11th June

Louise had been very unwell with the pre-clampasia and was getting better having given birth, and with our sleep deprived states it was hard to process our emotions, so we were struggling a bit. Later on that morning, we had a visit from the feeding team, and Baby was weighed. He’d lost 12.8% from his birth weight.

It’s usual for babies to lose some weight after giving birth - going from a nice warm, dark womb where food is provided on demand through an umbilical cord, to a bright, (relatively) cold, dry world, where you actually have to suckle and swallow to get food is quite a shock to the system! Particularly if you are born at only 37 weeks and 4 days, so ~2.5 weeks early (although babies are fully developed at 37 weeks).

The 12.8% loss is more than the typical 10% loss that is normal, so they were a bit worried about his weight and feeding. The feeding team talked to us about his feeding. He was happy going on Louise’s breast, but wasn’t suckling so hadn’t really taken on any milk since birth. They put us on a feeding plan, with a specific amount of milk (50ml) to give him every 3 hours. Louise was producing milk, so they introduced us to a breast pump, which we used, and then gave to Baby in a bottle. We then topped it up to 50ml with formula, every 3 hours. I was shown the ropes for sterilising the kit and bottles, and given the task of fetching, cleaning and sterilising the kit for every feed. Louise said that I spent a lot of time looking after the baby on Wednesday, giving her time to sleep and recover.

Louise’s parents visited today and arrived early afternoon. It was lovely to see them, and they stayed until around 5pm. We had dinner down in the hospital restaurant - jacket potato again for me and then they headed off. I slowly was feeling better and the visit made a nice change from the hospital routine.

It is amazing how frequently the advice around birth and newborns changes. One of our midwives, who was a third year student midwife, said that something she had learnt in her first year of study had now changed, with a better technique for feeding directly after birth. The advice changes frequently, and it even changed while we were in hospital! Louise had her C-section dressing checked, and removed this evening. Later on, the same midwife came back and said the advice for C-section dressings had changed, and now they were left on for five days rather than three, as this had been shown to reduce infection, so they replaced Louise’s dressing.

By Wednesday evening, everything was getting better and we were feeling more on top of things. We had some great advice from one of the midwives that evening about bottle feeding and successfully burping a baby - apparently burping is something they actually have to learn how to do!

The feeding plan the baby was on was going well, and Louise was expressing milk well. I was getting used to sterilising the equipment each time, and making the 55 metre walk, each way, twice every three hours (a total of 1.76 km every 24 hours), to get the bottles for Louise to express, and then return them and to wash and sterilise them. Louise was still trying to breast feed but having very limited success.

Later on that evening I had woken up for the ~1am feed and wasn’t feeling particularly with it. We needed the steriliser and bottles for Louise to express and I wasn’t feeling up to the long walk, so we asked one of the staff to get it for us, which they were very happy to do. She returned with the sterilising kit, but not the bottles. We asked her whether the bottles were there and she swore blind that they were not there. She got us some new bottles so Louise could do the expressing. The following feed I was more with it, so I went and checked and discovered the bottles were there, exactly where I said they were!

Thu 12th June

On Wednesday I had run around doing lots of things, and I think I had probably over done it: I wasn’t feeling that great. I broke down and cried again. I hadn’t eaten much and I think my brain had processed a bit more of what had happened and was struggling with it. We did have some good news that we were likely to be discharged on Thursday!

One of the midwives came to go through the discharge process, and in the check in, Louise said to her that I had been struggling. She had a chat with me, and asked whether I was looking after myself and whether I’d been eating enough. Thinking about it, I’d not really been eating enough since Sunday. Sunday night I had nothing, being preoccupied with the C-section (although I had had a main meal in the middle of the day). Monday I had toast for breakfast, jacket potato for lunch and a bit of sweet and sour pork for dinner. Tuesday I had cereal for breakfast, risotto for lunch (when I went home to pick up stuff) and jacket potato for dinner. Wednesday was toast for breakfast, jacket potato for lunch and jacket potato again for dinner. So I had been eating much less than normal for me. Discovering this, she essentially kicked me out of the room to go and get some lunch while she went through feeding and baby checks with Louise, which would take a while. I am eternally grateful for this and I took the opportunity to go to a nearby pub and have a decent burger and chips. I felt much better after this and was rather amazed that I had ended up in this position - missing out meals and not eating enough is not at all normal for me.

Louise’s parents arrived about 3pm, while we were getting sorted for discharge. I made various trips back to the car with stuff, and also managed to fit the child seat. We had had the child seat for a little while, but I hadn’t actually fitted it yet as I was planning on having 3 more weeks to work out how to fit it, before Baby was born!

We got out of the hospital about 5pm, and by pure coincidence saw the anesthesiologist from Louise’s C-section. She was thrilled to see us, and to see us leaving - Louise had been quite poorly because of the pre-eclampsia when she last saw us, so she said it was such a massive difference to see her looking so much better.

Over our 4 nights and 5 days in the hospital, we had some great care and met some fantastic staff - I can’t thank them enough for their time, patience and skill in looking after us. However, it was also clear they were massively overworked, short staffed and a couple of them were mediocre or even poor. The NHS is a fantastic institution with some great staff, but it also has some major issues. We can’t wave a magic wand and solve these issues but we need to find solutions that work, whilst keeping all of the fantastic elements that are in it.

by Nick Bearman at June 20, 2025 11:00 PM

TorchGeo 0.7.1 Release Notes

This is a bugfix and maintenance release. While there are no new features or API changes, this release includes important bug fixes, documentation improvements, and minor enhancements across datasets, models, trainers, and testing.

Dependencies

  • dependabot: update pandas group in unison (#2818)
  • jsonargparse: silence deprecation warnings (#2774)
  • segmentation-models-pytorch: 0.5+ now required (#2740)
  • setuptools: 77.0.1+ now required (#2703)

Data Modules

  • NAIP/Chesapeake: fix train/test overlap (#2834)
  • SKIPP'D: add to docs (#2778)
  • VHR-10: add to docs (#2776)

Datasets

  • Intersection/UnionDataset: simplify crs/res getter/setter (#2754)
  • BigEarthNet v2: fix validation directory name (#2825)
  • CopernicusPretrain: dataset yields, not returns (#2768)
  • EuroSAT: download split file even if image directory already exists (#2840)
  • FTW: add predictions to plot (#2731, #2735)
  • FTW: add uncompressed test data to git (#2746)

Models

  • API: ensure all models are in utility functions/hub (#2733)
  • CopernicusFM: fix flaky tests (#2710)
  • CopernicusFM: typo fixes (#2770, #2844)

Samplers

  • Samplers: samplers yield, not return (#2766)
  • PreChippedGeoSampler: fix type hints in tests (#2720)

Trainers

  • Classification: apply sigmoid before threshold in plot (#2793)
  • Instance Segmentation: denormalize images before plotting (#2744)
  • Instance Segmentation: fix support for non-RGB images (#2752)
  • Object Detection: fix support for non-RGB images (#2752)
  • Semantic Segmentation: apply sigmoid before threshold in plot (#2793)
  • Semantic Segmentation: pretrained ViT weights are now supported (#2787)

Documentation

  • README: update TorchGeo paper citation (#2729)
  • README: update syntax in VHR-10 example (#2705)
  • Related Libraries: add GeoDeep and srai (#2730, #2758)
  • Related Libraries: DeepForest used to support TensorFlow (#2734)
  • Landsat TM: fix number of channels for pretrained weights (#2836)
  • Update PyTorch doc site links (#2794)

Tutorials

  • Intro to PyTorch: use transforms (#2723)
  • Intro to Geospatial: typo fixes (#2706)
  • Earthquake Detection: speed up tutorial testing (#2721)
  • Contribute DataModule: typo fixes (#2708)
  • Contribute NonGeoDataset: fix sphinx directive (#2784)

Contributors

This release is made possible thanks to the following contributors:

by ashnair1 at June 20, 2025 06:37 PM

Matthew Edney spotted this map of Yonkers on the floor of the stage at a performance of Hello Dolly. “Map of Manhattan/Yonkers on floor of stage for Lyric Stage production of Hello Dolly (in Boston) … nifty” Nifty indeed!

by Steven at June 20, 2025 09:00 AM

This past Tuesday in Bern, the Swiss QGIS community came together for the 2025 edition of the QGIS.ch User Meeting — and we at OPENGIS.ch were proud to be deeply involved across the entire event, from presentations to hands-on workshops.

Sharing Insights and Innovation

The day began with our CEO, Marco Bernasocchi, opening the conference with an update on the QGIS project, covering exciting news about the upcoming QGIS 4 release and the ongoing website revamp (slides here). Shortly after, he took the stage again to present the latest improvements in QField, including new features, user experience (UX) enhancements, and under-the-hood upgrades that continue to enable efficient field data collection (slides here).

In collaboration with Timothée Produit from IG Group SA, our colleague Isabel Kiefer presented tools and streamlined processes for installing, managing, and updating TEKSI (and other) modules. These solutions are a testament to our mission of simplifying complex GIS infrastructure in public and private organisations alike.

Later in the morning, our CTO Mathias Kuhn gave a compelling talk on Machine Learning and AI in QGIS, showing real-world use cases and technical innovations that bridge geospatial workflows with intelligent automation.

Strengthening QGIS Security

As part of our commitment to sustainability and professionalisation in open source GIS, we are also proud to be a partner of Oslandia in the QGIS Security Project, which Vincent Picavet presented during the event. This initiative aims to ensure that QGIS continues to meet the highest standards of security — a crucial foundation for its growing adoption in critical infrastructures around the world.

Hands-on with QField – in Three Languages!

In the afternoon, OPENGIS.ch hosted a fully booked, multilingual QField workshop, attended by 25 enthusiastic participants. The session provided hands-on experience for users who wanted to take their QGIS projects into the field and was an excellent opportunity to exchange best practices and tips from real-world use cases and get some sun 🙂

OPENGIS.ch Tools in Action

Even outside of our sessions, tools developed by OPENGIS.ch were featured prominently throughout the day:

  • QField played a key role in the Zermatt use case presentation, demonstrating its flexibility and robustness in alpine field operations.
  • The Model Baker plugin, to which we contribute heavily, was showcased with its new multilanguage support for QGIS models — a significant step forward for the Swiss context and its multilingual projects.

A Thriving Community

As always, the QGIS.ch user meeting was a reminder of the strength and passion of the Swiss open source geospatial community. A huge thank you to the organizers, speakers, and participants who made the event such a success — we’re already looking forward to the next one!


Stay connected:
👉 QField website
👉 QFieldCloud
👉 Model Baker plugin

by Marco Bernasocchi at June 20, 2025 04:55 AM

KonGeoS - Konferenz der Geodäsie-Studierenden

Die KonGeoS ist die Konferenz der Geodäsie-Studierenden der Hochschulen im DACH-Raum und findet zweimal jährlich statt. Ziel ist es die Studierenden der 24 Geodäsie-Fachschaften aus Deutschland, Österreich und der Schweiz miteinander zu vernetzen. Die KonGeoS tourt, ähnlich wie die FOSSGIS-Konferenz, dabei durch die Universitäten und Hochschulen des DACH-Raumes. Vom 19. bis 22. Juni 2025 fand die KonGeoS an der Universität Bonn statt.

Beim Ausstellerforum am Freitagnachmittag informierten Torsten Brassat, Torsten Friebe, Harald Schwarz und André Henn über Open-Source-GIS und OpenStreetMap. Zahlreiche Studierende kamen mit Interesse oder Fragen am Stand vorbei.

Fotoeindrücke


FOSSGIS-OSGeo-OSM-Stand ist nachgefragt (Foto Torsten B.)


FOSSGIS-OSGeo-OSM-Stand ist gut nachgefragt und hat auch mal Ruhe (Foto Harald S.)

June 20, 2025 12:00 AM

June 19, 2025

💡 Estamos orgullosos de sumar nuestra experiencia en geointeligencia a esta alianza con Finnegans SA, integrando datos operativos y territoriales directamente en su ERP.

Con soluciones como formularios dinámicos y captura de datos en tiempo real (imágenes, ubicación, trazabilidad, notas de voz), llevamos la digitalización un paso más allá.

Gracias Finnegans por confiar en nosotros para seguir transformando industrias desde los datos.

#AlianzasFinnegans #FinnegansGOAgro #FinnegansGOConstructoras #Geointeligencia #TransformaciónDigital #ERP #KanTerritory

by KAN Territory & IT at June 19, 2025 08:30 PM

June 18, 2025

June 17, 2025

Prezados leitores,

Neste post irei apresentar como você pode instalar o GeoNode via Docker em uma máquina rodando o Ubuntu Linux 22.04. Ao final dessa instalação você estará com uma instância do GeoNode executando no seu localhost.

Sem enrolação, vamos aos passos:

1. Instalar os pacotes do S.O

> sudo add-apt-repository universe
> sudo apt-get update -y
> sudo apt-get install -y git-core git-buildpackage debhelper devscripts python3.10-dev python3.10-venv virtualenvwrapper
> sudo apt-get install -y apt-transport-https ca-certificates curl lsb-release gnupg gnupg-agent software-properties-common vim

2. Adicionar os repositórios do Docker

> sudo mkdir -p /etc/apt/keyrings
> curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
> sudo chmod a+r /etc/apt/keyrings/docker.gpg
> echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

3. Adicionar os pacotes do Docker

> sudo apt-get update -y
> sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-compose
> sudo apt autoremove --purge
> sudo reboot

4. Adicionar seu usuário ao grupo docker

> sudo usermod -aG docker ${USER}
> su ${USER}

5. Preparar o ambiente

> sudo mkdir -p /opt/geonode_custom/
> sudo usermod -a -G www-data geonode
> sudo chown -Rf geonode:www-data /opt/geonode_custom/
> sudo chmod -Rf 775 /opt/geonode_custom/

Dica: Se o nome do seu usuário não for geonode, substitua pelo nome do seu usuário na linha 2 e 3 acima.

6. Clonar o código fonte

> cd /opt/geonode_custom/
> git clone https://github.com/GeoNode/geonode-project.git -b 4.4.2

Dica: É importante ressaltar que o número que você passar após o -b é na realidade a versão que você quer baixar/instalar do GeoNode

7. Criar uma instância do Django

> source /usr/share/virtualenvwrapper/virtualenvwrapper.sh
> mkvirtualenv --python=/usr/bin/python3 my_geonode
> pip install Django==3.2.13
> django-admin startproject --template=./geonode-project -e py,sh,md,rst,json,yml,ini,env,sample,properties -n monitoring-cron -n Dockerfile my_geonode
> cd /opt/geonode_custom/my_geonode

OBS: Chamaremos nossa instância de my_geonode. Você pode alterar o nome conforme desejar.

8. Criar o arquivo .env

> python create-envfile.py

9. Construa os containers

> docker-compose -f docker-compose.yml build --no-cache

10. Finalmente execute o container

> docker-compose -f docker-compose.yml up -d

Agora é só aguardar todos os containers aparecerem como done, e você já pode acessar o GeoNode no seu navegador digitando http://localhost/

Se você quiser mais detalhes sobre a instalação basta acessar a documentação oficial do GeoNode, clicando aqui.

by Fernando Quadro at June 17, 2025 08:43 PM

June 16, 2025

June 15, 2025

I didn't do a lot of running in week 17, but none of it was flat. I did a solid uphill treadmill run on Thursday and a hot trail run at Lory State Park on Saturday.

  • 12.8 miles running

  • 10 hours, 40 minutes all training

  • 3,667 ft D+ running

In addition to those two runs, I did a hard elliptical workout and rode a bike three days. I did some weight training at home and at the gym, and did two sauna sessions. I'm trying to do 2-3 20-minute sessions a week in June to get ready for potentially hot weather at Never Summer. Andrew Huberman has a nice long podcast episode about the science of deliberate heat exposure that I found super interesting. If you haven't heard it, it's well worth a listen.

I went out for 2.5 hours in sunny 30 °C conditions yesterday and felt warm, but okay. The modest amount of heat training that I've been doing seems to be working. I'm going to stick with passive heating in the sauna a few times a week and one hot run every week. As much as I enjoy hearing about David Roche's extreme heat traing regimen, I won't be buying a heat suit or core temperature sensor.

Like I said last week, I've found it hard to adapt to downhill running when I'm not doing much downhill running. Today my quads are quite sore after yesterday's three miles of steep descents. I need to do more, that's all there is to it!

https://live.staticflickr.com/65535/54590919877_4ea4398481_b.jpg

A faint 4WD trail through grass and flowers over the top of a small summit under a mostly blue summer sky.

by Sean Gillies at June 15, 2025 11:52 PM

June 14, 2025

Reinder spotted this in a thrift shop. It’s a book of Ukrainian poems translated into English. We are wondering if the map is Kiev or …? Maybe one of our Ukrainian followers can help us out? Regardless this is a high impact book cover and could become one of my favourites.

by Steven at June 14, 2025 09:00 AM

June 13, 2025

Week 16, the end of the first half of my trail running season. I started out sick, but was able to get back into training pretty quickly. I had a nice gravel ride Wednesday, some tempo treadmill Thursday, a 2.5 hour ride on Saturday with a significant amount of comfortably hard uphill pedaling, and a 90 minute uphill treadmill run on Sunday. I avoided my usual group classes at the gym.

I continued with the therapeutic dose of Naproxen, iced my left Achilles tendon every night, and did no running on pavement or trails. Walking felt better all week, I'm happy to report.

It's seven weeks to Never Summer. It's weird to approach it with a base, a solid base, of cycling, and uphill treadmill and elliptical sessions, without the hundreds of miles of real trail running that I've done in the past.

My fitness level is pretty good. Based on my perceived level of exertion during workouts, my resting heart rate, and my body weight, it seems like I'm back where I was at this point in 2023. That's great, I'm pumped! I'm eager to do some fast downhill running before Never Summer. That's the thing that's hard to simulate in the gym, and I've been feeling soreness after my rare downhill runs this spring.

It'll be interesting to see how I fare on an alpine run like Twin Sisters, for sure. I'm planning that outing now.

by Sean Gillies at June 13, 2025 02:39 AM

Nach dem Motto nach der Konferenz ist vor der Konferenz wollte das Local Team Göttingen zeitnah mit den Konferenz-Vorbereitungen starten.

Janine, Daniel, Maik, Volker und Katja vom Konferenzorgateam und zwei Neumitglieder aus Göttingen trafen sich am 12. und 13. Juni mit den Ansprechpartnern aus der Öffentlichkeitsarbeit und Raumvergabe der Universität Göttingen. Die erste Grobplanung zur Raumnutzung und Positionierung der Catering- und Ausstellerflächen steht nun bereits fest. Beim gemeinsamen Kennlerntreffen an der mitveranstaltenden Fakultät für Geowissenschaften und Geographie wurden Ideen zur Programmgestaltung und zum Rahmenprogramm besprochen.

Die FOSSGIS 2026 wird vom 25.-28.03.2026 in Göttingen stattfinden. Der erste Teil der Konferenz von Mittwoch bis Freitag wird im Zentralen Hörsaalgebäude, welches große Hörsäle und ein großzügiges Foyer bietet, ausgerichtet. Der OSM-Samstag und Codesprint findet voraussichtlich an der Fakultät für Geowissenschaften und Geographie auf dem Nordcampus statt.

Es wird 2026 möglich sein in der Mensa gleich nebenan zu Mittag zu essen.

Unter anderem haben wir mögliche Locations für den Inoffiziellen Start und die Abendveranstaltung erkundet und getestet.


Links: Foyer im ZHG, Mitte: Mensa, rechts: Foyer der Geofakultät am Nordcampus

June 13, 2025 12:00 AM

June 12, 2025

Reinder sent us this superb map of Amsterdam made out of padlocks. He said ” map of padlocks in the Groenburgwal (canal) in Amsterdam. To commemorate the 750th anniversary of the city. They do this here because many people attach a padlock to the nearby bridge. To kind of ‘seal’ the eternity of their love. Quite a remarkable example of modern art.”

by Steven at June 12, 2025 09:00 AM

June 11, 2025

June 10, 2025

The GeoServer community has readied the following CVE vulnerabilities for public disclosure.

The release announcements listed above have been updated.

Free software is a participation sport - to create a patch for a prior release volunteer with community development.

Q: How often should I upgrade GeoServer?

GeoServer operates with a time boxed release cycle, maintaining “stable” and “maintenance” releases, over the course of a year.

  • Upgrade GeoServer twice a year as new stable releases are made.

  • Once the release you are using has entered “maintenance” it is a good idea to upgrade (before the release is no longer supported).

  • GeoServer security policy provides one year of support. You may also contact our service providers for extended support beyond this timeframe.

Q: Notification of security vulnerabilities?

Stay up to date:

  1. Please monitor release announcements for the heading “Security Considerations”.

    Security Considerations

    This release addresses several security vulnerabilities, and is a recommended upgrade for production systems.

    You can review the release announcement, and decide to update.

  2. When everyone has had an opportunity to update the details of the vulnerability are announced.

    Security Considerations

    This release addresses several security vulnerabilities, and is a recommended upgrade for production systems.

    • CVE-2024-29198 Unauthenticated SSRF via TestWfsPost (Moderate)
  3. Review the full vulnerability to learn more:

    CVE Report

  4. Scanning tools also have access to this information when the report is published:

    CVE Scan Results

Q: Notification of security reports?

As incoming security reports contain sensitive information they are only shared with representatives of the geoserver-security email list.

Participation in geoserver-security, like commit access, is volunteer based and reflects trust.

Please review GeoServer Security Policy if you are in a position to help out.

by Jody Garnett at June 10, 2025 12:00 AM

June 09, 2025