#postgis — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #postgis, aggregated by home.social.
-
Ugh. Could not drag + drop the city parcel data from #QGis into #PostGIS, but at least the message helps.
=
Failed to import layer!Feature write errors:
Creation error for features from #-9223372036854775808 to #-9223372036854775808. Provider errors were:
PostGIS error while adding features: ERROR: numeric field overflow
DETAIL: A field with precision 23, scale 15 must round to an absolute value less than 10^8.Stopping after 16940 error(s)
Only 17013 of 33953 features written
= -
Mastodon! :aroaceheart:
Ya tengo la serie completa: 171 meses (abril 2012 – junio 2026) de mediciones de contaminación lumínica de España, con 181.101 tiles en la base de datos #PostGIS del VPS.
Los datos vienen del satélite VIIRS (mide la luz que emite la Tierra de noche) y de elevación SRTM de la NASA, todos públicos. Yo me he encargado de procesarlos, recortarlos a España y montar una primera versión de API (aunque por ahora solo la conozco yo, porque el VPS es modesto y todavía tiene que evolucionar).
Todo está disponible en Internet Archive, aunque aún estoy actualizando algunos ficheros:
https://archive.org/details/spain-night-sky-elevation-2026
Si alguien necesita datos de luz nocturna a escala nacional con 14 años de historia, ahí están.
-
#PostGIS 3.7.0beta2 released
-
PostGIS 3.7.0beta2 landed today. Requires PostgreSQL 14 through 19beta2, GEOS 3.10+, Proj 6.1+, and GEOS 3.15+ for the full feature set.
The fix list is unusually security-heavy for a beta, including hardening the extension install and upgrade SQL against object resolution in writable schemas.
-
GeoSQL: Agent skill for geospatial data work: Volodymyr Bilonenko’s #GeoSQL gives #AIagents a map-in-the-loop for writing and validating spatial SQL across #PostGIS, #BigQuery, #Snowflake, and #Wherobots. By rendering results and checking them against real geography, the #agent catches...
https://spatialists.ch/posts/2026/08/10-geosql-agent-skill-for-geospatial-data-work/ #GIS #GISchat #geospatial #SwissGIS -
13 years ago I was down in the Caribbean working. Led to my discovery of QGIS. Also led to me learning how business works the hard way. 13 years later the USVI calls. They have a problem and the only way to fix it is PostGIS. I fix it and then ask "why are you calling me" - DOGE Cuts and they are up against a deadline, no money, and no friends because of the no money. Figured it out. Gave them an answer with three lines of SQL code. #QGIS #POSTGIS
-
Steigende Lizenzkosten, geänderte Modelle, wachsende Abhängigkeiten? Muss nicht sein.
Thorsten Hildebrand zeigt bei #WhereGroupShorts „Aufbau einer #GDI mit #OpenSource", wie eine vollständige GDI ohne Vendor Lock-in aussieht – von #PostGIS über #MapServer bis #Mapbender.
Volle Kontrolle über Daten, Software & Infrastruktur.
#DigitaleSouveränität beginnt nicht mit einem großen Migrationsprojekt – sondern mit dem ersten offenen Baustein. Heute schon möglich.
-
Vacation project: Home discgolf course pocket guide. Using #WebODM, @qfield and @qgis to create maps stored in #PostGIS
https://raw.githubusercontent.com/klakar/maps/6e962c87735862a3ae9d716431c1bbae672ba390/Cards.pdf -
#PostGIS 3.7.0alpha1 released
-
CVE-2026-1207 is a Django SQL injection flaw (CVSS 8.3) in PostGIS raster lookups. Canada's CCCS says it is exploited in the wild. Patch now.
-
@ioster @harmonia_amanda Pourquoi uniquement #Paris ?
On a désormais le nuage de points LIDAR HD de l'IGN qui permet d'avoir la précision suffisante pour calculer les altitudes et une pente moyenne pour chaque tronçon de rue.
À ma connaissance ça n'a jamais été fait de façon ouverte en opendata, mais ce n'est pas si compliqué à faire avec des softs #SIG #OpenSource ( #PostGIS par exemple ). Il faut prévoir un peu de traitement et de volume de données par contre.
-
⏳ Deadline extended! The #FOSS4G NA team is looking for talks to fill key gaps in the program for key areas, including:
- The business of open source
- Community
- Resilience
- Core tools like #QGIS & #PostGIS🔥 Submit now—spots are filling fast.
https://www.foss4gna.org/news-2026/call-for-proposals-extended-for-talks-and-lightning-talks
-
Is there anybody in my timeline using #owntracks recorder? I have the problem that my instance is extremely slow. Any Alternative using the geoJSON capabilities of #PostGIS instead of the plain files?
-
#PostGIS Tiger Geocoder 2025.1 released
-
I have an pdf vector picture I'd like to upload georeferenced to #postgis. Converting to tif/png is possible but gets unreadable (and still way bigger). I want that as picture, not as way etc (because it should keep it's look). Anything I did miss, or "just ignore the file size and upload as raster"? #gis
-
I spent about 30 minutes figuring out how to manage #PostGIS database migrations using a #RubyOnRails app with activerecord-postgis-adapter and the connecting to it via #QGIS: https://youtube.com/live/6vr9mwKsgJw?feature=share
-
I finally published the FitPub Helm chart on Artifact Hub! 🎉
Huge thanks to @McPringle for @fitpub - I'm genuinely inspired by the project.
Tested it locally today, and I'm planning to deploy on Infomaniak KaaS. My goal is to make self-hosting FitPub simpler, so I packed in plenty of quick-start commands and solid docs.
That's why I was quiet on Codeberg this weekend 😅
https://github.com/oliinykdm/fitpub-helm
#FitPub #Helm #Kubernetes #FOSS #SelfHosted #Fediverse #DevOps #ActivityPub #SpringBoot #postgis
-
Fid you know you can follow #PostGIS issue tracker on the Fediverse via RSS parrot ? Here it is: https://rss-parrot.net/u/trac.osgeo.org.postgis.report.16
I mention because there's an intense activity as @komzpa squashes every but with the help of another kind of parrot.
Parrots everywhere ! 🦜
Don't let #AI set you down, use it for the good while the free ride lasts.
Of course any additional humans eyes on the activity is welcome, we all known how sneaky can an #LLM be.
-
#osm2pgsql version 2.3.0 released:
- improved expire functionality
- style testing util for #lua import scripts
- new id cache function
- more geometry processing functions
- various cleanup and bug fixes -
Is this possible using PostGIS?
It feels like it should be an obvious use-case, but the right approach isn't clear to me after reading the docs.
Imagine having one set of paths (actually bike rides) and another set of segments (parts of rides where I time myself).
Instead of giving my money and data to abusive companies like Strava, I want to match my rides against the segments to track my best times as well as progression.
Thus, I need to efficiently match subsegments of the rides to the segment database.
What is the most efficient way to leverage PostGIS to do this? If I can make this work, I want to turn this into a Fediverse service.