#postgis — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #postgis, aggregated by home.social.
-
#PostGIS 3.7.0rc1 released
-
#PostGIS 3.7.0rc1 released
-
#PostGIS 3.7.0rc1 released
-
#PostGIS 3.7.0rc1 released
-
#PostGIS 3.7.0rc1 released
-
postgis_tiger_geocoder 2025.2 shipped on August 23, the second release since it split out of PostGIS core. It now requires PostgreSQL 16 or later and lives in its own repo.
PostGIS 3.6 is the last series to bundle it. 3.7 will ship without it. -
postgis_tiger_geocoder 2025.2 shipped on August 23, the second release since it split out of PostGIS core. It now requires PostgreSQL 16 or later and lives in its own repo.
PostGIS 3.6 is the last series to bundle it. 3.7 will ship without it. -
postgis_tiger_geocoder 2025.2 shipped on August 23, the second release since it split out of PostGIS core. It now requires PostgreSQL 16 or later and lives in its own repo.
PostGIS 3.6 is the last series to bundle it. 3.7 will ship without it. -
subiendo el ultimo dump del #postgis de #radiance a @internetarchive par que esté con las ultimas funciones API corregidas, con paciencia en una terminal minimizada :)
-
subiendo el ultimo dump del #postgis de #radiance a @internetarchive par que esté con las ultimas funciones API corregidas, con paciencia en una terminal minimizada :)
-
subiendo el ultimo dump del #postgis de #radiance a @internetarchive par que esté con las ultimas funciones API corregidas, con paciencia en una terminal minimizada :)
-
subiendo el ultimo dump del #postgis de #radiance a @internetarchive par que esté con las ultimas funciones API corregidas, con paciencia en una terminal minimizada :)
-
subiendo el ultimo dump del #postgis de #radiance a @internetarchive par que esté con las ultimas funciones API corregidas, con paciencia en una terminal minimizada :)
-
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
= -
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
= -
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
= -
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
= -
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.
-
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.
-
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.
-
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.
-
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 released
-
#PostGIS 3.7.0beta2 released
-
#PostGIS 3.7.0beta2 released
-
#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.
-
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.
-
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.
-
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 -
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 -
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 -
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 -
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
-
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
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
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 -
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 -
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 -
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 -
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
-
#PostGIS 3.7.0alpha1 released
-
#PostGIS 3.7.0alpha1 released
-
#PostGIS 3.7.0alpha1 released
-
#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.
-
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.
-
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.