En el marco del convenio con el Banco Interamericano de Desarrollo sede Perú (BID Perú), se llevó a cabo el proyecto de análisis de calidad de información geoespacial generados en el contexto del programa “Apoyo a la Plataforma Nacional de Ciudades Sostenibles y Cambio Climático en Lima” para el Ministerio de Ambiente de la República de Perú (MINAM). Este proyecto consistió en realizar el control de calidad de más de 400 capas de información geoespacial en función de los requerimientos establecidos en la familia de normas ISO 19100 que apuntan a regular y a normalizar la generación de información geoespacial con el objetivo de garantizar su interoperabilidad. El objetivo final de este trabajo fue aportar al proceso de mejora de la calidad e interoperabilidad de los datos al Plan Nacional de Adaptación al Cambio Climático (NAP, por sus siglas en inglés) en Perú. 

El NAP consiste en un exhaustivo documento en donde se plasman los principales lineamientos para planificar la implementación de medidas diseñadas específicamente para reducir los riesgos derivados del impacto del cambio climático. A su vez, este documento pretende ser una fuente de información disponible para la toma de decisiones a nivel gubernamental en torno a ésta problemática. En este sentido, entre los objetivos que persigue el NAP, se presentan los siguientes: 

1: Integrar y articular diversos instrumentos de gestión: Estrategia Regional de Cambio Climático, NDC y Planes Locales de Adaptación al Cambio Climático.  

2: Desarrollar un análisis de riesgos climáticos a nivel nacional y regional para 5 áreas temáticas: Agua, Bosques, Agricultura, Pesca y Acuicultura y Salud; y para 4 amenazas clave: movimientos en masa, inundaciones, cambio en las condiciones de aridez y retroceso glaciar.

3: Actualizar las medidas de adaptación establecidas en cada uno de los instrumentos de gestión, de acuerdo con las necesidades de las poblaciones y los ecosistemas.

Para llevar a cabo el proceso de revisión y control de calidad de la información generada en este contexto, se trabajó en conjunto con las empresas productoras de la información geoespacial y en constante comunicación con representantes del BID Perú. Estas empresas habían sido convocadas por el Ministerio de Ambiente de Perú en convenio con BID y la organización World Wide Fund for Nature (WWF) con el objetivo de analizar y generar información para: el “Plan de Adaptación Costera para el Área Metropolitana de Lima (AML)”, los “Estudios base sobre riesgo de desastres por riesgos naturales y crecimiento urbano en el AML” y los “Estudios de análisis urbanístico, prefactibilidad y diseños constructivos para acciones estratégicas de accesibilidad, multimodalidad y desarrollo orientado al transporte en el Sistema Integrado de Transporte (SIT) de Lima y Callao”. Toda la información geoespacial generada en el marco de estos tres productos fue el objeto de análisis de la consultoría realizada por Kan.  

La premisa que guió el desarrollo de este proyecto fue alcanzar un nivel de calidad del dato óptimo que permitiera a los organismos disponibilizar la información producida garantizando el libre acceso, la interoperabilidad, la confiabilidad y la calidad. 

En primera instancia se presentaron requisitos para la presentación de la información para asegurar el libre acceso. En este sentido, se solicitó que la información pudiera ser consultada a través de software libres, para que pudieran ser consumidos sin necesidad de pagar una licencia para hacerlo, siendo el formato “geopackage” el indicado para cumplir esta condición. 

El análisis de la información se basó en una metodología específica desarrollada por el equipo SIG de Kan, fundamentada en las normas 19115-3, 19139, 19110 y 19157 que hacen referencia a los formatos e implementación de metadatos, a la catalogación de objetos geográficos y a la calidad del dato, respectivamente. Todo el contenido de estas normas se plasmaron en matrices analíticas que luego fueron aplicadas a cada una de las capas de información. Estas matrices permitieron relevar el estado de la información en relación a: la completud de sus metadatos, formatos de interoperabilidad de la información, calidad del dato, referencias sobre su linaje, uso y propósito, su consistencia lógica y topológica, el análisis de sus atributos, entre otros puntos. En total, se establecieron seis categorías de análisis: 

A: Compatibilidad del conjunto de datos

B: Interoperabilidad del conjunto de datos

C: Interoperabilidad conjunto de metadatos

D: Interoperabilidad – Metadatos de la capa

E: Compatibilidad de la capa

F: Calidad del dato

Para cada categoría se definieron una serie de elementos de análisis que en total suman 47 ítems. El objetivo final de esta revisión fue cuantificar la usabilidad de la información geográfica producida, estableciendo un rango de usabilidad. Este rango va entre -1 y 1, siendo los valores cercanos a -1 aquellos que incumplen en más de un 50% los elementos establecidos para el análisis y los valores cercanos a 1 aquellos que cumplen en más de un 50% los elementos. De esta forma se obtuvo un resultado parcial de usabilidad por capa y un resultado global de usabilidad para el conjunto de datos. Luego de haber realizado el análisis, se confrontaron los resultados obtenidos con lo establecido por las normas, de esta manera se creó un documento de recomendaciones y sugerencias para la mejora de la calidad e interoperabilidad del dato. 

Este proyecto permitió conocer la calidad de la información generada en el proyecto e identificar aquellos aspectos posibles de mejorar para garantizar la interoperabilidad de la información. Luego de este proceso de análisis, las empresas aplicaron las recomendaciones y sugerencias realizadas por el equipo SIG de Kan con el que alcanzaron un nivel óptimo de calidad del dato.

GeoServer 2.24-RC release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a release candidate intended for public review and feedback, made in conjunction with GeoTools 30-RC, GeoWebCache 1.24-RC, mapfish-print-v2 2.3-RC and geofence-3.7-RC.

Thanks to Andrea Aime (GeoSolutions) and Jody Garnett (GeoCat) for working on making this release candidate.

Release candidate public testing and feedback

Testing and providing feedback on releases is part of the open-source social contract. The development team (and their employers and customers) are responsible for sharing this great technology with you.

The collaborative part of open-source happens now - we ask you to test this release candidate in your environment and with your data. Try out the new features, double check if the documentation makes sense, and most importantly let us know!

If you spot something that is incorrect or not working do not assume it is obvious and we will notice. We request and depend on your email and bug reports at this time. If you are working with commercial support your provider is expected to participate on your behalf.

Keeping GeoServer sustainable requires a long term community commitment. If you are unable to contribute time, sponsorship options are available via OSGeo.

IAU authority support and EPSG assumption removal

The new gs-iau extension module provides support for planetary CRSs, sourced from the International Astronomical Union. This allows to manage GIS data over the Moon, Mars, or even the Sun, with well known, officially supported codes.

In addition to that, many bug fixes occurred in the management of CRSs and their text representations (plain codes, URL, URIs) so that the EPSG authority is no longer assumed to be the only possibility, in a variety of places, such as, for example, GML output. The code base has seen this assumption for twenty years long, and while we made a good effort to eliminate the assumption, it could be still lurking in some places. Please test and let us know.

To learn more about this extension please visit the user-guide documentation. Thanks to Andrea Aime (GeoSolutions) for working on this activity.

• GSIP-219 - Multiple CRS authority support, planetary CRS
• GEOS-11075 IAU authority : planetary CRS support
• GEOS-11001 Support other CRS authories in WFS
• GEOS-11002 Support other CRS authorities in WMS
• GEOS-11056 Support other CRS authorities in WCS
• GEOS-11064 Support other CRS authorities in WPS
• GEOS-11066 Support other CRS authorities in importer
• GEOS-11076 SRSList should show authorities other than EPSG, if available
• GEOS-10970 CatalogBuilder cannot handle CRS in authorities other than EPSG
• GEOS-10971 XStreamPersister cannot save CRS references using authorities other than EPSG
• GEOS-10972 Resource page CRS editors would not work with authorities other than EPSG

GeoServer Printing Extension Updates

The printing extension has seen big changes - with a host of new functionality developed by GeoSolutions over the years. With this update the printing module can now be used out-of-the-box by GeoNode and MapStore (no more customization required).

• Max number of columns configuration for multi column legends
• Simple colored box icon in legends
• Explicit support of Geoserver CQL_FILTER parameter (also with layers merge support)
• Legend fitting
• Don’t break legend items
• Reorder legends block in columns
• Images content
• Dynamic images page
• Multipage legends
• Custom intervals in ScalebarBlock
• Clustering Support
• HTML rendering in text blocks
• Extra Pages
• Group Rendering in attribute blocks
• Skip rendering of pages
• Automatic X-Forwarded-For
• Parsing of Base64 encoded images

Thanks to GeoSolutions for adding functionality to mapfish-print for the GeoNode project. Jody Garnett (GeoCat) was responsible for updating the mapfish print-lib for Java 11 and gathering up the functionality from different branches and forks.

• GEOS-11132 mapfish-print-v2 2.3-RC

New Security > URL Checks page

This release adds a new Check URL facility under the Security menu. This allows administrators to manage OGC Service use of external resources.

For information and examples on how to use the URL Check page, visit user guide documentation.

• GSIP 218 - Control remote HTTP requests sent by GeoTools \ GeoServer
• GEOS-10949 Control remote resources accessed by GeoServer
• GEOS-11048 Improve URL checking

Developer updates

Internal refactor to remove “org.opengis” package usage

The GeoTools project moved away from using the “org.opengis” package after complaints from OGC GeoAPI working group representatives, using the same package name. Interfaces have been moved to the “org.geotool.api” package, along with some general clean up.

While this does not affect GeoServer users directly, it’s of consequence for those that have installation with custom, home grown plugins that might have to be migrated as a consequence. For those, the GeoTools project offers a migration guide, along with a refactoring script that might perform the migration for you, or else, get you close to a working point. GeoServer itself has been migrated using these scripts, with minimal manual intervention.

For more details, and access to the migration script, please see the GeoTools 30 upgrade guide.

Thanks to Jody Garnett (GeoCat), Andrea Aime (GeoSolutions), and Ian Turton (ASTUN Technologies) for all the hard work on this activity. We would also like to thank the Open Source Geospatial Foundation for setting up a cross-project activity and financial support to address this requested change.

• GEOS-11070 Upgrading to GeoTools 30.x series, refactor to org.geotools.api interfaces

Community modules updates

While not strictly part of this release, it’s interesting to know about some community module advances that can be found only in the the 2.24.x series.

Two extensions are no longer actively supported and are now available as community modules:

• GEOS-10960 Downgrade imagemap module to community
• GEOS-10961 Downgrade xslt extension to community

The following community modules have been removed (due to lack of interest):

• GEOS-10962 Remove wms-eo community module
• GEOS-10963 Remove SAML community module
• GEOS-10966 Remove importer-fgdb community module
• GEOS-10967 Remove teradata community module
• GEOS-10977 Remove wmts-styles community module
• GEOS-10978 Remove nsg-wmts community module
• GEOS-10984 Remove ows-simulate community module

OGC API community modules continues to improve

The OGC API community module keeps improving. In particular, thanks to the GeoNovum sponsorship, GeoSolutions made the OGC API Features module pass the OGC CITE compliance tests, for the “core” and “CRS by reference” conformance classes. Along with this work, other significant changes occurred:

• Made the API version number appear in the service path, easing future upgrades
• Support for configurable links, required to get INSPIRE download service compliance.

In addition to that, the new “search” experimental conformance class allows to POST complex searches against collections, as a JSON document, in a way similar to the STAC API.

Those interested in this work are encouraged to contact Andrea Aime (GeoSolutions).

• GEOS-10924 Support JSON-FG draft encoding in OGC API - Features
• GEOS-11045 Implement proposal “OGC API - Features - Part n: Query by IDs”
• GEOS-10882 Add an option to remove trailing slash match in OGC APIs
• GEOS-10887 Add angle brackets to OGC API CRS Header
• GEOS-10892 Allow configuring custom links for OGC API “collections” and single collection resources
• GEOS-10895 Make OGC API CITE compliant even if the trailing slash is disabled: landing page exception
• GEOS-11058 Support other CRS authorities in OGC APIs
• GEOS-10909 Don’t link from OGC API Features to WFS 2.0 DescribeFeatureType output, if WFS is disabled
• GEOS-10954 Split ogcapi community module package into single functionality packages

DataDir Catalogue loader

For folks working with very large catalogues some improvement from cloud native geoserver are now available to reduce startup time.

Thanks to Gabriel Roldan for folding this improvement into a community module for the rest of the GeoServer community to enjoy.

• GEOS-11049 Community module “datadir catalog loader”

GeoServer Access Control List Project

The GeoServer Access Control List project is an independent application service that manages access rules, and a GeoServer plugin that requests authorization limits on a per-request basis.

Gabriel Roldan is the contact point for anyone interested in this work.

• GSIP 217 - GeoServer ACL project

The vector mosaic and FlatGeoBuf modules sport significant performance improvements

FlatGeoBuf is a “A performant binary encoding for geographic data”, a single file format that also manages to be cloud native and include a spatial index. GeoServer provides access to this format thought the WFS FlatGeobuf output format, which not only can write the format, but also read it as a standard data store.

The Vector Mosaic datastore supports creation of mosaics made of single file vector data, useful in situations where the access to data is targeted to sub-pages of a larger data set (e.g., data for a single time, or a single customer, or a single data collect, out of a very large uniform set of vectors) and the database storage for it is become either too slow, or too expensive.

These two modules make a great combo for those in need to handle very large vector datasets, by storing the FlatGeoBuf on cheap storage.

In particular, the FlatGeoBuf module saw speed improvements that made it the new “fastest vector format” for cases where one needs to display a large data set, all at once, on screen (PostGIS remains the king of the hill for anything that needs sophisticated filtering instead).

For reference, we have timed rendering 4 million tiny polygons out of a precision farming collect, using a 7 classes quantile based SLDs. Here is a tiny excerpt of the map:

And here are the timings to render the full set of polygons, putting them all on screen, at the same time, with a single GetMap request:

• PostGIS, 113 seconds
• Shapefile, 41 seconds
• Flatgeobuf, 36 seconds

The tuning is not complete, more optimizations are possible. Interested? Andrea Aime is the contact point for this work.

Release notes

New Feature:

• GEOS-10992 Make GWC UI for disk quota expose HSQLDB, remove H2, automatically update existing installations
• GEOS-11000 WPS process to provide elevation profile for a linestring

Improvement:

• GEOS-10926 Community Module Proxy-Base-Ext
• GEOS-10934 CSW does not show title/abstract on welcome page
• GEOS-10973 DWITHIN delegation to mongoDB
• GEOS-10999 Make GeoServer KML module rely on HSQLDB instead of H2
• GEOS-11005 Make sure H2 dependencies are included in the packages of optional modules that still need it
• GEOS-11059 Map preview should not assume EPSG authority
• GEOS-11081 Add option to disable GetFeatureInfo transforming raster layers
• GEOS-11087 Fix IsolatedCatalogFacade unnecessary performance overhead
• GEOS-11090 Use Catalog streaming API in WorkspacePage
• GEOS-11099 ElasticSearch DataStore Documentation Update for RESPONSE_BUFFER_LIMIT
• GEOS-11100 Add opacity parameter to the layer definitions in WPS-Download download maps
• GEOS-11102 Allow configuration of the CSV date format
• GEOS-11116 GetMap/GetFeatureInfo with groups and view params can with mismatched layers/params

Bug:

• GEOS-8162 CSV Data store does not support relative store paths
• GEOS-10452 Use of Active Directory authorisation seems broken since 2.15.2 (LDAP still works)
• GEOS-10874 Log4J: Windows binary zip release file with log4j-1.2.14.jar
• GEOS-10875 Disk Quota JDBC password shown in plaintext
• GEOS-10899 Features template escapes twice HTML produced outputs
• GEOS-10903 WMS filtering with Filter 2.0 fails
• GEOS-10921 Double escaping of HTML with enabled features-templating
• GEOS-10922 Features templating exception on text/plain format
• GEOS-10928 Draft JSON-FG Implementation for OGC API - Features
• GEOS-10936 YSLD and OGC API modules are incompatible
• GEOS-10937 JSON-FG reprojected output should respect authority axis order
• GEOS-10958 Update Spotbugs to 4.7.3
• GEOS-10981 Slow CSW GetRecords requests with JDBC Configuration
• GEOS-10985 Backup Restore of GeoServer catalog is broken with GeoServer 2.23.0 and StAXSource
• GEOS-10993 Disabled resources can cause incorrect CSW GetRecords response
• GEOS-11015 geopackage wfs output builds up tmp files over time
• GEOS-11016 Docker nightly builds use outdated GeoServer war
• GEOS-11033 WCS DescribeCoverage ReferencedEnvelope with null crs
• GEOS-11060 charts and mssql extension zips are missing the extension

Task:

• GEOS-11091 Upgrade spring-security to 5.7.10
• GEOS-11094 Bump org.hsqldb:hsqldb:2.7.1 to 2.7.2
• GEOS-11103 Upgrade Hazelcast version to 5.3.x
• GEOS-10248 WPSInitializer NPE failure during GeoServer reload
• GEOS-10904 Bump jettison from 1.5.3 to 1.5.4
• GEOS-10907 Update spring.version from 5.3.25 to 5.3.26
• GEOS-10941 Update ErrorProne to 2.18
• GEOS-10987 Bump xalan:xalan and xalan:serializer from 2.7.2 to 2.7.3
• GEOS-10988 Update spring.version from 5.3.26 to 5.3.27 and spring-integration.version from 5.5.17 to 5.5.18
• GEOS-11010 Upgrade guava from 30.1 to 32.0.0
• GEOS-11011 Upgrade postgresql from 42.4.3 to 42.6.0
• GEOS-11012 Upgrade commons-collections4 from 4.2 to 4.4
• GEOS-11018 Upgrade commons-lang3 from 3.8.1 to 3.12.0
• GEOS-11019 Upgrade commons-io from 2.8.0 to 2.12.0
• GEOS-11020 Add test scope to mockito-core dependency
• GEOS-11062 Upgrade httpclient from 4.5.13 to 4.5.14
• GEOS-11063 Upgrade httpcore from 4.4.10 to 4.4.16
• GEOS-11067 Upgrade wiremock to 2.35.0
• GEOS-11080 Remove ASCII grid output format from WCS
• GEOS-11084 Update text field css styling to look visually distinct
• GEOS-11092 acme-ldap.jar is compiled with Java 8

For the complete list see 2.24-RC release notes.

About GeoServer 2.24 Series

Additional information on GeoServer 2.24 series:

• Control remote HTTP requests sent by GeoTools/GeoServer
• Multiple CRS authority support, planetary CRS

Release notes: ( 2.24-RC )

This is it, race week. Wednesday I'm flying to Salt Lake City and driving to Logan. Friday before dawn I'm headed up the trail to Bear Lake.

Week ~5 was a rest week at the end of a big training block. I biked and ran for less than 4 hours. Week ~4 I ran for 12 hours, 53 miles, and 8,500 feet of elevation gain. Much of that was above 10,000 feet in Rocky Mountain National Park, my go-to for accessible high country. I ran up to Granite Pass, 12,100 feet, just below the Longs Peak boulder field, and test drove the gels that will be served at the Bear 100. Spring Energy's Awesome Sauce is good! I could eat them all day. Spring's Speednut product is a bit harder for me to stomach. One of those every few hours might be all I can take.

At the end of week ~4 I did some volunteering at the Black Squirrel Trail Half-Marathon, a race I've run several times. I helped park cars in the pre-race darkness and get first-timers pointed toward registration and the starting line. I saw the Milky Way in the clear, dark early morning sky. I caught up with the race directors, Nick and Brad, and saw other friends in the first mile of the course. Volunteering at events is always needed and fun. I recommend it.

In week ~3, I ran for 9.5 hours, 42 miles, and 5,700 feet. In the interest of fine tuning, I went out in the heat of the day and took my poles. In week ~2, last week, I got the new COVID vaccination and did less running and more yoga and body-weight strength and mobility exercise. Split squats with dumbbells made me sore, but I am over it now.

Where am I at now, in week ~1? I think I have enough experience and adequate training this year to finish. Three events of 40 miles, including one overnight, and one at very high elevation. The heart palpitations that were troubling me last year almost never occur now. I'm well over my most recent sinus infection. I've got all the gear I need and am physically and psychologically prepared for hot weather, cold weather, and rain or snow. The race will have more food than I can eat along the way and will deliver my five drop bags to aid stations and the finish line. I don't have a crew or pacer for the run, but think I'll be fine without. Reality is that it's harder to have these as you get older. Your family is busy and your friends are busy with their own families. I'm shy, but not shy about forming small ad-hoc teams on the trail, so I expect to be fine on that front.

The Bear 100 Endurance Run starts with 5,000 feet of climbing in the first 10 miles. I can do this. At least it's at the beginning and not the end. That leaves only 17,000 feet for the last 90 miles. I'm joking about this to keep my spirits up. This will be super hard, a big bump up from my hardest week of training, and I'll need to go even deeper into the unknown than I've done at the Never Summer 100K. I'm ready to see what happens out there.

The one thing that's concerning me is that I have a persistent ache in my right foot. Yesterday I went out for an hour in my Nike Terra Kiger's to see if I might want to bring them along as a shoe option. The answer is no: they don't have enough padding for my foot in its current condition. I feel worse today than yesterday. There's at least a small chance that I have a bone stress problem. The pain and swelling is right on the "N-spot". I'm not going to let this stop me from starting and will see how it goes on Friday. I've got a pretty high pain threshold and will be stashing some ibuprofen in my later drop bags. Cold rain and cold, numb feet, if the forecast holds, might help, too. How is that for positive thinking?

If you want to follow along on Friday and Saturday, the live tracking should be at https://data0.adilas.biz/bear100/. My bib number is 314. That website currently shows last year's race. I expect that this year's progress will be shown on Friday morning.

I'm pausing my job search and open source work to focus on next weekend's adventure. Forgive me if I don't respond before October 5-6. After I'm back I'll be prioritizing the job search over open source. Not for long, I hope!

Thanks to our generous donors and sustaining members, we are in the wonderful position to be able to further extend our 2023 Grant Programme and to fund two additional projects that came in very close 5th and 6th in the voting results:

• QEP#261 Cachable provider metadata API — or how to the QGIS loading times
• QEP#236 Unification of all geometric and topological verification methods

On behalf of the QGIS.ORG project, I would like to thank everyone who helped with the fund raising and everyone who stepped up and joined our donor and sustaining membership programme.

You must be logged into the site to view this content.

You must be logged into the site to view this content.

This summer, I had the honor to — once again — speak at the OpenGeoHub Summer School. This time, I wanted to challenge the students and myself by not just doing MovingPandas but by introducing both MovingPandas and DVC for Mobility Data Science.

I’ve previously written about DVC and how it may be used to track geoprocessing workflows with QGIS & DVC. In my summer school session, we go into details on how to use DVC to keep track of MovingPandas movement data analytics workflow.

Here is the recording of the session live stream and you can find the materials at https://github.com/movingpandas/movingpandas-examples/blob/opengeohub2023/README.md

We are extremely happy to announce that we have partnered strategically with Oslandia to push the leading #fieldwork app #QField even further.

In the world of fieldwork, accuracy and efficiency are paramount. As GIS specialists, we understand the importance of reliable tools that streamline data collection and analysis processes. That’s why we are thrilled to join forces with Oslandia, a company that shares our passion for open-source development and innovation.

Embracing Open Source Development

At OPENGIS.ch, we have always been committed to the principles of true open-source development. We firmly believe collaboration and shared knowledge drive progress in the GIS community. With Oslandia, we have found a partner who shares our values and cares as much as we do about the QGIS ecosystem.

QGIS, the world’s most popular open-source geographic information system software, has already significantly impacted the GIS industry, providing users with versatile mapping tools and capabilities and is the base upon which QField is built. As main contributors to #QGIS, both OPENGIS.ch and Oslandia are dedicated to driving its growth and ensuring its availability to all.

Advancing QField and QFieldCloud Together

QField, with almost 1 million downloads, is the leading app for fieldwork tasks. It empowers professionals in various sectors, such as environmental research, agriculture, urban planning, and disaster management, to efficiently collect data and conduct analyses in the field. With our strategic partnership with Oslandia, we are committed to pushing the boundaries of QField even further.

Our joint efforts will ensure that QField will keep setting trends in the industry, surpassing the evolving needs of GIS specialists and empowering them to excel in their fieldwork tasks.

A Synergy of Expertise

The collaboration between OPENGIS.ch and Oslandia represents a true synergy of expertise. Our combined capabilities will enable us to tackle complex challenges quickly and deliver cutting-edge solutions that address the unique requirements for seamless #fielwork.

Conclusion

At OPENGIS.ch, we are excited about the opportunities our partnership with Oslandia brings. Together, we will continue championing open-source development, empowering GIS specialists in each sector to perform their fieldwork tasks more effectively and efficiently.

With QField as our flagship app, we are confident that this strategic collaboration will result in even greater advancements, benefiting our target audience of surveying professionals, fieldwork experts, and GIS specialists, as well as casual users who need a user-friendly solution for their projects.

Join us in celebrating this exciting new chapter as we embark on a shared journey towards innovation and excellence in fieldwork applications.

Who are we?

For those unfamiliar with Oslandia, OpenGIS.ch, or even QGIS, let’s refresh your memory:

Oslandia is a French company specializing in open-source Geographic Information Systems (GIS). Since our establishment in 2009, we have been providing consulting, development, and training services in GIS, with reknown expertise. Oslandia is a dedicated open-source player and the largest contributor to the QGIS solution in France.

As for OPENGIS.ch, they are a Swiss company specializing in the development of open-source GIS software. Founded in 2011, OPENGIS.ch is the largest Swiss contributor to QGIS. OPENGIS.ch is the creator of QField, the most widely used open-source mobile GIS solution for geomatics professionals.

OPENGIS.ch also offers QFieldCloud as a SaaS or on-premise solution for collaborative field project management.

Some may still be unfamiliar with #QGIS ?

It is a free and open-source Geographic Information System that allows creating, editing, visualizing, analyzing, and publicating geospatial data. QGIS is a cross-platform software that can be used on desktops, servers, as a web application, or as a development library.

QGIS is open-source software developed by multiple contributors worldwide. It is an official project of the OpenSource Geospatial Foundation (OSGeo) and is supported by the QGIS.org association. See https://qgis.org

A Partnership?

Today, we are delighted to announce our strategic partnership aimed at strengthening and promoting QField, the mobile application companion of QGIS Desktop.

This partnership between Oslandia and OPENGIS.ch is a significant step for QField and open-source mobile GIS solutions. It will consolidate the platform, providing users worldwide with simplified access to effective tools for collecting, managing, and analyzing geospatial data in the field.

QField, developed by OPENGIS.ch, is an advanced open-source mobile application that enables GIS professionals to work efficiently in the field, using interactive maps, collecting real-time data, and managing complex geospatial projects on Android, iOS, or Windows mobile devices.

QField is cross-platform, based on the QGIS engine, facilitating seamless project sharing between desktop, mobile, and web applications.

QFieldCloud (https://qfield.cloud), the collaborative web platform for QField project management, will also benefit from this partnership and will be enhanced to complement the range of tools within the QGIS platform.

Reactions

At Oslandia, we are thrilled to collaborate with OPENGIS.ch on QGIS technologies. Oslandia shares with OPENGIS.ch a common vision of open-source software development: a strong involvement in development communities, work in respect with the ecosystem, an highly skilled expertise, and a commitment to industrial-quality, robust, and sustainable software development.

With this partnership, we aim to offer our clients the highest expertise across all software components of the QGIS platform, from data capture to dissemination.

On the OpenGIS.ch side, Marco Bernasocchi adds:

The partnership with Oslandia represents a crucial step in our mission to provide leading mobile GIS tools with a genuine OpenSource credo. The complementarity of our skills will accelerate the development of QField and QFieldCloud and meet the growing needs of our users.

Commitment to open source

Both companies are committed to continue supporting and improving QField and QFieldCloud as open-source projects, ensuring universal access to this high-quality mobile GIS solution without vendor dependencies.

Ready for field mapping ?

And now, are you ready for the field?

So, download QField (https://qfield.org/get), create projects in QGIS, and share them on QFieldCloud!

If you need training, support, maintenance, deployment, or specific feature development on these platforms, don’t hesitate to contact us. You will have access to the best experts available: infos+mobile@oslandia.com.

 

Geomatico dedica un día al mes a colaborar en aquellos proyectos que más nos llaman la atención tecnológica o socialmente. Es lo que llamamos el día del imasdé (I+D), que empieza con todos los trabajadores votando a qué dedicaremos las siguientes horas de trabajo.

Como no podía ser de otra manera, esta jornada del 13 de septiembre la dedicamos al precioso proyecto HOT-OSM (Humanitarian OpenStreetMap Team) que había hecho un llamamiento urgente para ayudar a mapear las zonas afectadas por el dramático terremoto del sur de Marruecos.

Primero hicimos una pequeña introducción a OpenStreetMap (OSM) para profanos para aquella parte del equipo que no tenía experiencia anterior con el proyecto. Vimos los diferentes editores, iD, JOSM y estudiamos un poco las primitivas geométricas que caracterizan el proyecto y por supuesto las Map Features. Ya en HOT, decidimos en que proyecto íbamos a colaborar y nos pusimos a ello.

Seleccionando zona de trabajo en HOT-OSM

Había que que cartografiar los edificios dentro de las rejillas que seleccionábamos. En el mismo proyecto de HOT, se explicaba claramente como realizar la tarea a partir de JOSM. Así, mediante el plugin de crear edificios, pudimos aportar nuestro granito de arena a la zona.

Puede ser complejo definir distinguir exactamente los contornos de los edificios en Marruecos

Fue muy gratificante, tanto por la tarea, como por la dinámica del trabajo, el compartir una jornada completa con las compañeras realizando un trabajo “sencillo“ en el que a la vez podíamos estar comentando otros aspectos de nuestro día a día. ¡Viva el día del imasdé y HOT-OSM!

Micho, Marta y Alex trabajando en HOT-OSM pero posando disimuladamente para la foto

Paul Ramsey and I recently had a Fireside chat with Path to Cituscon. Checkout the Podcast Why People care about PostGIS and Postgres. There were a surprising number of funny moments and very insightful stuff.

It was a great fireside chat but without the fireplace. We covered the birth and progression of PostGIS for the past 20 years and the trajectory with PostgreSQL. We also learned of Paul's plans to revolutionize PostGIS which was new to me. We covered many other side-line topics, like QGIS whose birth was inspired by PostGIS. We covered pgRouting and mobilitydb which are two other PostgreSQL extension projects that extend PostGIS.

We also managed to fall into the Large Language Model conversation of which Paul and I are on different sides of the fence on.

Continue reading "Why People care about PostGIS and Postgres and FOSS4GNA"

Your direct access to the shared resources of the QGIS community.

We, a team of researchers from four U.S. universities, are excited to announce a significant new project to support and expand the global GRASS GIS community. We have been awarded a prestigious grant (award 2303651) from the U.S. National Science Foundation (NSF) to bolster and broaden the software ecosystem of GRASS GIS for a world that increasingly relies on location-based information. The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

You must be logged into the site to view this content.

A while back, one of our ninjas added a new algorithm in QGIS’ processing toolbox named ST-DBSCAN Clustering, short for spatio temporal density-based spatial clustering of applications with noise. The algorithm regroups features falling within a user-defined maximum distance and time duration values.

This post will walk you through one practical use for the algorithm: large-scale fire event analysis and visualization through remote-sensed fire detection. More specifically, we will be looking into one of the larger fire events which occurred in Canada’s Quebec province in June 2023.

Fetching and preparing FIRMS data

NASA’s Fire Information for Resource Management System (FIRMS) offers a fantastic worldwide archive of all fire detected through three spaceborne sources: MODIS C6.1 with a resolution of roughly 1 kilometer as well as VIIRS S-NPP and VIIRS NOAA-20 with a resolution of 375 meters. Each detected fire is represented by a point that sits at the center of the source’s resolution grid.

Each source will cover the whole world several times per day. Since detection is impacted by atmospheric conditions, a given pass by one source might not be able to register an ongoing fire event. It’s therefore advisable to rely on more than one source.

To look into our fire event, we have chosen the two fire detection sources with higher resolution – VIIRS S-NPP and VIIRS NOAA-20 – covering the whole month of June 2023. The datasets were downloaded from FIRMS’ archive download page.

After downloading the two separate datasets, we combined them into one merged geopackage dataset using QGIS processing toolbox’s Merge Vector Layers algorithm. The merged dataset will be used to conduct the clustering analysis.

In addition, we will use QGIS’s field calculator to create a new Date & Time field named ACQ_DATE_TIME using the following expression:

to_datetime("ACQ_DATE" || "ACQ_TIME", 'yyyy-MM-ddhhmm')

This will allow us to calculate precise time differences between two dates.

Modeling and running the analysis

The large-scale fire event analysis requires running two distinct algorithms:

• a spatiotemporal clustering of points to regroup fires into a series of events confined in space and time; and
• an aggregation of the points within the identified clusters to provide additional information such as the beginning and end date of regrouped events.

This can be achieved through QGIS’ modeler to sequentially execute the ST-DBSCAN Clustering algorithm as well as the Aggregate algorithm against the output of the first algorithm.

The above-pictured model outputs two datasets. The first dataset contains single-part points of detected fires with attributes from the original VIIRS products as well as a pair of new attributes: the CLUSTER_ID provides a unique cluster identifier for each point, and the CLUSTER_SIZE represents the sum of points forming each unique cluster. The second dataset contains multi-part points clusters representing fire events with four attributes: CLUSTER_ID and CLUSTER_SIZE which were discussed above as well as DATE_START and DATE_END to identify the beginning and end time of a fire event.

In our specific example, we will run the model using the merged dataset we created above as the “fire points layer” and select ACQ_DATE_TIME as the “date field”. The outputs will be saved as separate layers within a geopackage file.

Note that the maximum distance (0.025 degrees) and duration (72 hours) settings to form clusters have been set in the model itself. This can be tweaked by editing the model.

Visualizing a specific fire event progression on a map

Once the model has provided its outputs, we are ready to start visualizing a fire event on a map. In this practical example, we will focus on detected fires around latitude 53.0960 and longitude -75.3395.

Using the multi-part points dataset, we can identify two clustered events (CLUSTER_ID 109 and 1285) within the month of June 2023. To help map canvas refresh responsiveness, we can filter both of our output layers to only show features with those two cluster identifiers using the following SQL syntax: CLUSTER_ID IN (109, 1285).

To show the progression of the fire event over time, we can use a data-defined property to graduate the marker fill of the single-part points dataset along a color ramp. To do so, open the layer’s styling panel, select the simple marker symbol layer, click on the data-defined property button next to the fill color and pick the Assistant menu item.

In the assistant panel, set the source expression to the following: day(age(to_date('2023-07-01'),”ACQ_DATE_TIME”)). This will give us the number of days between a given point and an arbitrary reference date (2023-07-01 here). Set the values range from 0 to 30 and pick a color ramp of your choice.

When applying this style, the resulting map will provide a visual representation of the spread of the fire event over time.

Analyzing a fire event through histogram

Through QGIS’ DataPlotly plugin, it is possible to create an histogram of fire events. After installing the plugin, we can open the DataPlotly panel and configure our histogram.

Set the plot type to histogram and pick the model’s single-part points dataset as the layer to gather data from. Make sure that the layer has been filtered to only show a single fire event. Then, set the X field to the following layer attribute: “ACQ_DATE”.

You can then hit the Create Plot button, go grab a coffee, and enjoy the resulting histogram which will appear after a minute or so.

While not perfect, an histogram can quickly provide a good sense of a fire event’s “peak” over a period of time.

In August 13 new plugins that have been published in the QGIS plugin repository.

Here’s the quick overview in reverse chronological order. If any of the names or short descriptions piques your interest, you can find the direct link to the plugin page in the table below the screenshot.

Cesium ion

Browse and add datasets from Cesium ion

Land Use Analyzer

A plugin for Land Use spatial analysis tools

GNAVS

GNSS Navigate and Save

Soar – the new atlas

Import or export maps via the Soar platform

FotovolCAT

Spatial analysis automation for solar power station sitting in Catalonia

QGISSPARQL-Layer2Triple

Layer2Triple

osm2topomap

A plugin intended to intermediate the process of using OSM data for official (authoritative) Topographc Maps, or rather, databases

Plugin Exporter

A QGIS plugin for exporting plugins

GetBaseLine

GetBaseLine

Fast Field Filler

The plugin was created to quickly fill in the fields in the attribute table.

Radiation ToolBox Plugin

Plugin for loading data from Safecast and other radiation monitoring devices

LocationIQ Geocoding and Maps

LocationIQ integration to add geocoding and map tiles to QGIS

Proxy Handler

Adds prefix proxy addresses to connections

Read more »

You must be logged into the site to view this content.

Today, I want to point out a blog post over at

https://geocompx.org/post/2023/ogh23/

written together with my fellow “Geocomputation with Python” co-authors Robin Lovelace, Michael Dorman, and Jakub Nowosad.

In this blog post, we talk about our experience teaching R and Python for geocomputation. The context of this blog post is the OpenGeoHub Summer School 2023 which has courses on R, Python and Julia. The focus of the blog post is on geographic vector data, meaning points, lines, polygons (and their ‘multi’ variants) and the attributes associated with them. We plan to cover raster data in a future post.

The GeoTools team are pleased to announce the release of the latest stable version of GeoTools 28.5     geotools-28.5-bin.zip    geotools-28.5-doc.zip    geotools-28.5-userguide.zip    geotools-28.5-project.zipThis release is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.22.5. We are grateful to Peter Smythe (AfriGIS) for carrying out the

The GeoTools team are pleased to announce the release of the latest stable version of GeoTools 28.5     geotools-28.5-bin.zip    geotools-28.5-doc.zip    geotools-28.5-userguide.zip    geotools-28.5-project.zipThis release is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.22.5. We are grateful to Peter Smythe (AfriGIS) for carrying out the

Habiendo finalizado con éxito la etapa de capacitación de la iniciativa Geoalfabetización mediante la utilización de Tecnologías de la Información Geográfica, lanzamos la convocatoria a participar de la edición 2023 del concurso: Proyectos de Geografía con estudiantes y gvSIG Batoví. Pueden acceder aquí a la convocatoria y bases.

Todos los años tenemos alguna novedad y este año no es la excepción:

• tenemos el apoyo del Instituto Panamericano de Geografía e Historia (la iniciativa fue seleccionada por el Programa de Asistencia Técnica 2023, Proyecto PAT No. GEOG-04/2023 Geoalfabetización mediante la utilización de Tecnologías de la Información Geográfica)
• este año participa también la Dirección General de Educación Técnico Profesional (UTU)
• la certificación se obtiene participando del curso y del concurso
• contamos con la colaboración de la Universidad Politécnica de Madrid en la organización de la iniciativa

Agradecemos el apoyo de todas las instituciones que hacen posible la realización de esta propuesta. 

GeoServer 2.22.5 release is now available with downloads ( bin, war, windows) , along with docs and extensions.

This is a maintenance release of GeoServer providing existing installations with minor updates and bug fixes. GeoServer 2.22.5 is made in conjunction with GeoTools 28.5, and GeoWebCache 1.22.5.

Thanks to Peter Smythe (AfriGIS) for making this release.

2023-09-05 update: GeoServer 2.22.5 has been recompiled and uploaded to SourceForge. The initial upload was accidentally compiled with Java 11 and would not function in a Java 8 environment.

Thanks to Jody Garnett (GeoCat) for this update, and Steve Ikeoka for testing in a Java 8 environment.

Java 8 End-of-life

This GeoServer 2.22.5 maintenance release is final scheduled release of GeoServer 2.22.x series, and thus the last providing Java 8 support.

All future releases will require a minimum of Java 11.

Release notes

Improvement:

• GEOS-10856 geoserver monitor plugin - scaling troubles
• GEOS-11048 Improve URL checking
• GEOS-11081 Add option to disable GetFeatureInfo transforming raster layers
• GEOS-11099 ElasticSearch DataStore Documentation Update for RESPONSE_BUFFER_LIMIT
• GEOS-11100 Add opacity parameter to the layer definitions in WPS-Download download maps

Bug:

• GEOS-10874 Log4J: Windows binary zip release file with log4j-1.2.14.jar
• GEOS-10875 Disk Quota JDBC password shown in plaintext
• GEOS-10901 GetCapabilities lists the same style multiple times when used as both a default and alternate style
• GEOS-10903 WMS filtering with Filter 2.0 fails
• GEOS-10932 csw-iso: should only add ‘xsi:nil = false’ attribute
• GEOS-11025 projection parameter takes no effect on MongoDB Schemaless features WFS requests
• GEOS-11035 Enabling OSEO from Workspace Edit Page Results in an NPE
• GEOS-11054 NullPointerException creating layer with REST, along with attribute list
• GEOS-11055 Multiple layers against the same ES document type conflict with each other
• GEOS-11069 Layer configuration page doesn’t work for broken SQL views

Task:

• GEOS-11062 Upgrade httpclient from 4.5.13 to 4.5.14
• GEOS-11063 Upgrade httpcore from 4.4.10 to 4.4.16
• GEOS-11067 Upgrade wiremock to 2.35.0
• GEOS-11092 acme-ldap.jar is compiled with Java 8

For the complete list see 2.22.5 release notes.

About GeoServer 2.22 Series

Additional information on GeoServer 2.22 series:

• GeoServer 2.22 User Manual
• Update Instructions
• Metadata extension
• CSW ISO Metadata extension
• State of GeoServer (FOSS4G Presentation)
• GeoServer Beginner Workshop (FOSS4G Workshop)
• Welcome page (User Guide)

Release notes: ( 2.22.5 | 2.22.4 | 2.22.3 | 2.22.2 | 2.22.1 | 2.22.0 | 2.22-RC | 2.22-M0 )

Nos hacemos eco del lanzamiento de la 6ª edición del Curso-Concurso TIGs y gvSIG Batoví. Este año viene con una importante novedad, Colombia se suma a esta iniciativa uruguaya.

Y se ha comunicado que más de cien docentes de Uruguay y Colombia ya se inscribieron al curso TIGs y gvSIG Batoví… ¡enhorabuena!

The third week of my season's big training block was my biggest yet from the climbing perspective. My runs averaged 220 feet of elevation gain (D+) per mile, which is what the Bear 100 course will demand of me in 5 weeks. Here are last week's numbers.

• 20 hours, 37 minutes

• 76.2 miles

• 16,775 feet D+

Extrapolating that to 100 miles, naively, predicts a 28 hour finish. That would be amazing! There's no way I'm going to finish in 28 hours. I think I'll be able to keep up this week's average pace for 60 miles and then will slow down dramatically after that. We'll see!

Next week I'm giving myself a break from long hilly runs. I'll do daily runs of not much more than an hour, yoga, some strength and conditioning. And I'll be working on my race day planning: gear, drop bags, fueling, etc.

Moving GRASS GIS Docker Images to the OSGeo Repository In the field of open source software development and deployment, the accessibility and maintenance of resources is of paramount importance. To this end, there has been a major change in the repository structure for the GRASS GIS Docker images. In the past years, these Docker images have been maintained and hosted under the mundialis organisation’s repository. The company mundialis has played a crucial role in providing and maintaining these images, ensuring their availability and stability for the wider GIS community.

Read more »

Cada año, desde 2007, la Infraestructura de Datos Espaciales de la República Argentina (IDERA) extiende su invitación a los apasionados de la información geoespacial a unirse a las Jornadas IDERA. Este evento anual se ha convertido en una tradición, y en 2023, se llevó a cabo en la hermosa ciudad de Santa Rosa, provincia de La Pampa, Argentina. Es un hecho que IDERA se enorgullece de propiciar un espacio donde los expertos pueden compartir y celebrar los avances en el campo de la información geoespacial.

El equipo de Kan participó de este evento, que tuvo como objetivo central impulsar la publicación de datos, productos y servicios geoespaciales de manera eficiente y oportuna, con la finalidad de respaldar la toma de decisiones basadas en evidencias. Las XVII Jornadas IDERA fueron el punto culminante de este esfuerzo, transformándose en el evento geoespacial del año en Argentina. Fue un momento invaluable para intercambiar ideas y debatir sobre los avances y desafíos relacionados con la publicación y utilización de información geoespacial abierta, interoperable y accesible para el desarrollo del país.

Bajo el lema “La comunidad de IDERA hacia un marco integrado de información geoespacial”, las XVII Jornadas IDERA proporcionaron un espacio de reflexión sobre las propuestas globales emergentes destinadas a desarrollar, integrar y fortalecer la gestión de información geoespacial. Este enfoque permitirá mejorar las Infraestructuras de Datos Espaciales en los diferentes niveles jurisdiccionales de Argentina.

La agenda de las XVII Jornadas IDERA estuvo repleta de eventos emocionantes y presentaciones interesantes. Los talleres y ponencias que realizamos desde Kan fueron los siguientes:

Presentación institucional de KAN en el espacio de networking

Taller “Potenciá el uso de tus datos geo con Geonode 4” 

Presentación de casos de éxito en el grupo de provincias

Taller “Recolección de datos en campo con Kobo” Ponencia “

Desarrollo de un Sistema de Monitoreo y Manejo Integral de Humedales a partir de Información Satelital” 

Además aprovechamos para compartir y asistir a otras charlas y muestras de nuestros colegas. Muchísimas gracias IDERA por esta oportunidad única para conectarnos con otros expertos, dejarnos aprender de sus experiencias y contribuir al avance de la comunidad de información geoespacial en Argentina. ¡Nos vemos el próximo año!

Gli atti del workshop Archeofoss 2022 sono stati pubblicati in open access su Archeologia e Calcolatori. Li trovate qui http://www.archcalc.cnr.it/journal/idyear.php?IDyear=2023-07-26 come numero 34.1 della rivista.

Ho curato insieme a Julian Bogdani l’edizione di questo volume ed è quindi motivo di soddisfazione, anche per i tempi rapidi con cui siamo arrivati alla pubblicazione grazie al lavoro collettivo degli autori e autrici, di chi ha fatto il referaggio, della redazione e della casa editrice.

Rimane una mancanza in questo volume rispetto alla ricchezza dei due giorni di incontro, delle sette sessioni tematiche, delle discussioni guidate da chi ha moderato le sessioni, ibride eppure vivacissime. La mancanza in parte è fisiologica ma in parte deriva da un certo numero di autrici e autori che non hanno presentato il proprio contributo per la pubblicazione. Ad esempio, nella sessione sui dati stratigrafici che ho moderato con Emanuel Demetrescu erano stati presentati 7 interventi ma solo 2 sono confluiti come paper nel volume.

Nei prossimi anni dovremo fare di più per fare in modo che gli atti raccolgano ancora più fedelmente il convegno.

Ci ritroveremo con la comunità Archeofoss a Torino nel mese di dicembre 2023.

In the next release of GeoTools 30.0 there are some breaking API changes to look forward to:org.opengis package is renamed to org.geotools.api packageThis release will include update instructions, and a migration script, to fix your code.This is a breaking change, the formal change control proposal is here.Why is this changingThe GeoAPI Implementation Specification is a Java standard (Interfaces

QGIS Server provides numerous services like WMS, WFS, WCS, WMTS and OGC API for Features. These last years, a lot of efforts were made to offer a robust implementation of the WMS 1.3.0 specification.

We are pleased to announce that QGIS Server LTR 3.28 is now certified against WMS 1.3.0.

This formal OGC certification process is performed once a year, specifically for the Long Term Release versions. But, as every change in QGIS source code is now tested against the formal OGC test suites (using OGC TeamEngine) to avoid any kind of regressions, you can always check any revision of the code against OGC failures in our Github continuous integration results.

All this has been possible thanks to the QGIS’s sustaining members and contributors.

For fun I'm using the bitwise complement operator ~ in the title of this post. Race week is week ~0. On Monday, it was 6 weeks to race week. I'm starting to feel fit, close to my 2020-2021 form.

The numbers for the week:

• 16 hours, 54 minutes

• 71 miles

• 12,165 feet D+

I've run six days in a row and my shortest run was today's: an hour and 20 minutes. I went out for five hours in Rocky Mountain National Park on Wednesday, two hours in Lory State Park on Friday, and five and a half hours at Horsetooth Open Space on Saturday.

Soaking hot and tired feet in the Big Thompson River below Fern Lake in RMNP.

Below the Westridge Wall in Lory S.P.

Alone on Arthur's Rock, looking NE across the reservoir and plains.

Towers trail tailgating

A bear was active around Towers Trail yesterday, but successfully avoided me. According to some bikers, it crossed the trail behind my back near the top during my first lap. If I'd turned when I heard them shouting, I might have seen it. I know there are bears up there, but have never seen one while I've been on the trail. It's a good time to be filling up on chokecherries, that's for sure.

Next week I'm going to increase my training volume a little more. Instead of two 5.5 hour runs, I'll aim for 3 x 4 hours.

Today, Jeff Sikes @box464@firefish.social, alerted me to the fact that “Twitter has removed all media attachments from 2014 and prior” (source: https://firefish.social/notes/9imgvtckzqffboxt). So far, it seems unclear whether this was intentional or a system failure (source: https://mas.to/@carnage4life/110922114407553901).

Since I’ve been on Twitter since 2011, this means that some media files are now lost. While the loss of a few low-res images is probably not a major loss for humanity, I would prefer to have some control over when and how content I created vanishes. So, to avoid losing more content, I have followed Jeff’s recommendation to create a proper archival page:

https://anitagraser.github.io/twitter-archive/

It is based on an export I pulled in October 2022 when I started to use Mastodon as my primary social media account. Unfortunately, this export did not include media files.

To follow me in the future, find me on:

https://fosstodon.org/@underdarkGIS

Btw, a recent study published on Nature News shows that Mastodon is the top-ranking Twitter replacement for scientists.

To find other interesting people on Mastodon, there are many useful tools and lists, including, for example:

• Cartography, Geovisualization & GIS on Mastodon
• Geographers on Mastodon list
• Followgraph for Mastodon

In this summer plugin update, we explore 51 new plugins that have been published in the QGIS plugin repository.

Here’s the quick overview in reverse chronological order. If any of the names or short descriptions piques your interest, you can find the direct link to the plugin page in the table below the screenshot.

JAPATI
The QGIS plugin is used by agencies in the West Java provincial government to upload data and create map services on the geoserver in order to publish data internally and publicly
BD TOPO® Extractor
This tool allows you to extract specific data from IGN’s BD TOPO®. The extraction is based on either an extent drawned by the user on the map canvas or a layer’s extent.
Opacity Set
Sets opacity 0.5, 0.75 or 1 for selected raster layer.
USM toolset (Urban Sprawl Metric toolset)
The USM Toolset was developed to facilitate the calculation of Weighted Urban Proliferation (WUP) and all components of urban sprawl for landscapes that include built-up areas (e.g., dispersion (DIS), land uptake per person (LUP).
DAI
DAI (Daily Aerial Image)
France Commune Cadastre
Search for a cadastral parcel with the French cadastre API
Two distances intersection
Get the intersection of two distances (2D cartesian)
IDG
Plugin providing easy access to data from different SDI
SPAN
SPAN is a flexible and easy to use open-source plugin based on the QGIS software for rooftop mounted PV potential estimation capable of estimating every roof surface’s PV potential.
CSV Batch Import
Batch import of CSV vector layers
Imagine Sustainability
sustainability assessment tool based on geographic MCDA algorithms. Especially suitable for Natura 2000 sites, based on pyrepo-mcda package(https://pyrepo-mcda.readthedocs.io/)
QGIS Hub Plugin
A QGIS plugin to fetch resources from the QGIS Hub
VFK Plugin
Data českého katastru nemovitostí (VFK)<br><br>Czech cadastre data (VFK)
LinearReferencing
Tools for linear referenced data
CIGeoE Circumvent Polygon
Changes the line to circumvent a polygon between the intersection points
UA XML importer
Імпортує геометрію ділянки, обмежень, угідь та територіальних зон з кадастрового обмінного файлу XML
eagris
QGIS eAGRI plugin
Geojson Filling
Allows to fill imported geojson layers with pre-defined field values
Save All
File saving script that saves qgis project file and all vector and raster layers into user-specified folder. Automatically detects file type and saves as that file type (supports SHP, GPKG, KML, CSV, and TIF). All styles and formatting are saved with each layer (except for KML), ensuring that they are opened up with the proper style the next time the project is opened. Temporary layers are made permanent automatically.
Fast Density Analysis
A fast kernel density visualization plugin for geospatial analytics
StreetSmart
This plugin manages the Street Smart imagery
FilePath
Copies the path of layer
pandapower QGis Plugin
Plugin to work with pandapower or pandapipes networks
Eqip
Qgis Pip Management
Infra-O plugin
Plugin for Finnish municipal asset management.
Add to Felt
Create a collaborative Felt (felt.com) map from QGIS
Lahar Flow Map Tools
This plugin is for opening and processing results from LaharFlow
Station Offset
This plugin computes the station and offset of points along polylines and exports those values to csv for other applications
Jilin1Tiles
Jilin1Tiles
SiweiEarth
This plugin is used to load the daily new map provided by Siwei Earth.
QdrawEVT
Easily draw and select entities in the drawing footprint. Installation of the plugin “Memory layer saver” highly recommended. See Read_me.txt file in the Help folder of the plugin. Dessiner et selectionner facilement les entités dans l’emprise du dessin. Installation du plugin “Memory layer saver” fortement recommandé. Voir fichier Lisez_moi dans le dossier Hepl du plugin. Merci !
Fuzzy Logic Toolbox
This plugin implements the fuzzy inference system
feature_space
A plugin to plot feature space and export areas as raster or vector
Panorama Viewer
Plugin for QGIS to view 360-degrees panoramic photos
Map Segmenter
Uses machine learning to segment a map into ares of interest.
ALKIS Plugin
Das Plugin verfügt über zwei Werkzeugkästen und insgesamt vier einfache Werkzeuge. Im Werkzeugkasten “Gebäude” finden Sie drei nützliche Werkzeuge, um ALKIS-Gebäudedaten aufzubereiten. Sie können Dachüberstände erstellen, Gebäude auf der Erdoberfläche extrahieren und redundante Gebäudeteile eliminieren. Im Werkzeugkasten “Nutzung” steht Ihnen ein weiteres Werkzeug zur Verfügung, mit dem Sie die Objektarten in den Objektartengruppen Vegetation, Siedlung, Verkehr und Gewässer zuordnen können. Das Plugin erfordert als Datengrundlage ALKIS-Daten im vereinfachten Format, die in NRW, Deutschland, frei verfügbar sind. Dieses Plugin wurde zu Demonstrationszwecken entwickelt. Das Ziel besteht darin, in einer Videoreihe die Entwicklung eines Plugins ohne die Anwendung von Python vorzustellen. Die Tutorials dazu findet ihr in der folgenden Playlist: https://www.youtube.com/playlist?list=PLq5L9pOv_ur5wRAVHt3iVw61mUUpb54aJ
isobenefit
Isobenefit Urbanism plugin for QGIS.
UA_MBD_TOOLS
Tools for
Qpositional
assessment the positional quality of geographic data
Terraform
Implementation of popular topographic correction algorithms and various methods of their evaluation.
PathoGAME
The goal is to find the location of the contamination as soon as possible.
Azure Maps Creator
Provides access to Azure Maps Creator services
CIGeoE Identify Dangles
Identifies dangles in a viewport
Delete Duplicate Fields
Delete duplicate or redundant fields from a vector file
LocationFinder
Allow QGIS to use LocationFinder (interactive geocoding)
COA TPW Polygonizer
This plugin can be used to create polygons that track the shape of a line network, including the proper handling of intersections with common nodes of the line segments.
XPlan-Umring
Create XPlanGML from polygon(s)
Tweet my river
AI Tweet classifier for river layers
3DCityDB Tools
Tools to visualize and manipulate CityGML data stored in the 3D City Database
GroundTruther
A toolset for Seafloor Caracterization
Faunalia Toolkit
Cartographic and spatial awesome analysis tool and much much more!

The PostGIS Team is pleased to release PostGIS 3.4.0! This version works with versions PostgreSQL 12-16, GEOS 3.6 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.12+ is needed. To take advantage of all SFCGAL features, SFCGAL 1.4.1+ is needed.

• source download md5
• NEWS
• PDF docs: en ja fr
• HTML Online en ja fr de ko_KR
• Cheat Sheets:
  • postgis: en ja fr
  • postgis_raster: en ja fr
  • postgis_topology: en ja fr
  • postgis_sfcgal: en ja fr
  • address standardizer, postgis_tiger_geocoder: en ja fr

This release is a major release, it includes bug fixes since PostGIS 3.3.4 and new features.

Community Meeting to celebrate the GRASS GIS 40th birthday!! The GRASS GIS Community Meeting was held in the Czech Republic from June 2 to 6 at the Faculty of Civil Engineering of the Czech Technical University in Prague. The meeting was a milestone event to celebrate the 40th birthday of GRASS GIS and brought together users, supporters, contributors, power users and developers to celebrate, collaborate and chart the future of GRASS GIS.

nuget.org support finally provided a resolution on my account issue and I was able to regenerate my publishing keys.

As a result, the 6.0m12 release (6.0.0-pre500) nuget packages are now finally available on nuget.org

• OSGeo.MapGuide.ObjectModels
• OSGeo.FDO.Expressions
• OSGeo.MapGuide.MaestroAPI

Ho scritto un articolo sul nuovo forum per gli appassionati di ceramica italiana. Treni e tazzine da caffè, una accoppiata particolare!

You must be logged into the site to view this content.