Welcome to Planet OSGeo

March 20, 2024

February 24, 2024

It’s my pleasure to share with you that Trajectools 2.0 just landed in the official QGIS Plugin Repository.

This is the first version without the “experimental” flag. If you look at the plugin release history, you will see that the previous release was from 2020. That’s quite a while ago and a lot has happened since, including the development of MovingPandas.

Let’s have a look what’s new!

The old “Trajectories from point layer”, “Add heading to points”, and “Add speed (m/s) to points” algorithms have been superseded by the new “Create trajectories” algorithm which automatically computes speeds and headings when creating the trajectory outputs.

“Day trajectories from point layer” is covered by the new “Split trajectories at time intervals” which supports splitting by hour, day, month, and year.

“Clip trajectories by extent” still exists but, additionally, we can now also “Clip trajectories by polygon layer”

There are two new event extraction algorithms to “Extract OD points” and “Extract OD points”, as well as the related “Split trajectories at stops”. Additionally, we can also “Split trajectories at observation gaps”.

Trajectory outputs, by default, come as a pair of a point layer and a line layer. Depending on your use case, you can use both or pick just one of them. By default, the line layer is styled with a gradient line that makes it easy to see the movement direction:

while the default point layer style shows the movement speed:

How to use Trajectools

Trajectools 2.0 is powered by MovingPandas. You will need to install MovingPandas in your QGIS Python environment. I recommend installing both QGIS and MovingPandas from conda-forge:

(base) conda create -n qgis -c conda-forge python=3.9 
(base) conda activate qgis
(qgis) mamba install -c conda-forge qgis movingpandas

The plugin download includes small trajectory sample datasets so you can get started immediately.

Outlook

There is still some work to do to reach feature parity with MovingPandas. Stay tuned for more trajectory algorithms, including but not limited to down-sampling, smoothing, and outlier cleaning.

I’m also reviewing other existing QGIS plugins to see how they can complement each other. If you know a plugin I should look into, please leave a note in the comments.

by underdark at February 24, 2024 07:26 PM

February 23, 2024

La escasez de agua en la agricultura, agravada por el cambio climático, amenaza la seguridad alimentaria. Los sistemas de riego eficientes son clave para mitigar estos desafíos, optimizando el uso del agua y fortaleciendo la resiliencia agrícola.

Entre 2022 y 2023 hemos desarrollado un gemelo digital de gestión del agua en agricultura junto al IRTA (Instituto de Investigación y Tecnología Agroalimentaria). En la aplicación web se pueden monitorizar y analizar casi 300 mil parcelas simbolizadas semanalmente por 17 indicadores (unos 250 millones de registros por año) que permiten optimizar la irrigación.

by Geomatico at February 23, 2024 01:17 PM

February 22, 2024

Publicada la Segunda Edición del Libro “Introducción a los Sistemas de Información Geográfica con QGIS” de Federico Gazaba

Una pregunta recurrente en redes sociales es ¿Dónde puedo encontrar un manual para aprender a usar QGIS? o ¿Cómo puedo iniciarme en el uso de los Sistemas de Información Geográfica (SIG)? Hace aproximadamente 3 años Federico Gazaba publicaba la pimera versión de su libro “Introducción a los Sistemas de Información Geográfica con QGIS” un manual que en su momento fue de referencia obligada para las personas usuarias de QGIS en habla hispana pero que con el paso del tiempo había quedado desactualizado debido a la aparición de nuevas versiones de QGIS.

Recientemente el autor nos comentaba que se estaba preparando una actualización de libro y no nos ha hecho esperar mucho, el 22 de Febrero nos anunciaba en el canal de Telegram de QGIS en español que la versión 2.0 había sido publicada: _“Hola amigos #geoinquietos !. Lo prometido es deuda, les traigo la versión 2.0 de mi libro libre “Introducción a los Sistemas de Información Geográfica con QGIS”. Esta versión actualiza los contenidos de la versión anterior a QGIS 3.34 Prizren.".

El libro ha sido publicado bajo la licencia CC BY-SA 4.0 lo que permite que sea compartido o modificado, para cualquier proposito, con libertad mientras se respete la atribución al autor y se comparta con la misma licencia. Se puede descargar aquí o aquí el repositorio del libro se puede encontrar en GitHub

Este libro es otro ejemplo que demuestra que los proyectos de software libre y open source permiten compartir y colaborar en este tipo de iniciativas donde podemos participar de forma activa y generar grandes sinergias en sus aplicaciones y desarrollos en beneficio, tanto de las comunidades que las desarrollan como las que las usan.

Federico Gazaba es profesor de Matemáticas y Técnico Maestro Mayor de Obras y actualmente es docente en el Instituto de Formación Docente y Técnica 122 “Presidente Illia” de Pergamino (Provincia de Buenos Aires, Argentina) y Director de Sistemas de Información Georreferenciada de la Municipalidad de Pergamino. Desde el año de 2013 es usuario de QGIS y es un entusiasta del las tecnologías libres y de los datos espaciales abiertos. La creación del manual nace de la necesidad de impartir cursos de QGIS a sus colegas de municipalidad y es el resultado de la sistematización de esas enseñanzas. Desde 2016, de forma ininterrumpida, imparte cursos introductorios a los SIG para diferentes instituciones.

Puedes seguir a Federico en la siguientes redes sociales:

February 22, 2024 08:00 PM

February 21, 2024

February 20, 2024

We are happy to announce that QGIS User Conference will take place on 9-10 September 2024 in Bratislava, Slovakia.


The traditional Contributor Meeting will be held right after the conference on 11-13 September 2024 at the same venue.

Learn more about the user conference and the contributor meeting at the event’s web site: https://uc2024.qgis.sk/

The call for papers for the user conference is now open – you can submit proposals for talks and workshops by 31 March 2024:
https://uc2024.qgis.sk/call-for-papers/

We have also started call for sponsors, with sponsorship opportunities at various levels. More details here:
https://uc2024.qgis.sk/sponsors/

User Conference

The QGIS User Conference is an annual event that brings together users and developers of QGIS. The conference provides an opportunity for attendees to learn about the latest developments in QGIS, share their experiences with others, and network with other QGIS users and
developers.

Contributor Meeting

QGIS Contributor Meetings are volunteer-driven events where contributors to the QGIS project from around the world get together in a common space – usually a university campus. During these events, contributors to the QGIS project take the opportunity to plan their work, hold face-to-face discussions and present new improvements to the QGIS project that they have been working on. Everybody attending the event donates their time to the project for the days of the event.
As a project that is built primarily through online collaboration, these meetings provide a crucial ingredient to the future development of the QGIS project. The event is planned largely as an ‘unconference’ with minimal structured programme planning.

For more details and to sign up, please visit the corresponding wiki page https://github.com/qgis/QGIS/wiki/27th%E2%80%90Contributor%E2%80%90Meeting%E2%80%90in%E2%80%90Bratislava

by underdark at February 20, 2024 07:17 PM

February 19, 2024

February 18, 2024

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

This is the last planned maintenance release of GeoServer 2.23.x, providing existing installations with minor updates and bug fixes. Sites using the 2.23.x series are encouraged to upgrade to GeoServer 2.24.x, or eventually wait next month, for the 2.25.0 release, and upgrade their installation, with the help of the upgrade guide.

GeoServer 2.23.5 is made in conjunction with GeoTools 29.5, and GeoWebCache 1.23.4.

Thanks to Andrea Aime (GeoSolutions) for making this release.

Release notes

New Feature:

  • GEOS-11225 AuthKey synchronize the user/group automatically
  • GEOS-11279 metadata: allow same field on multiple tabs

Improvement:

  • GEOS-11213 Improve REST external upload method unzipping
  • GEOS-11246 Schemaless plugin performance for WFS
  • GEOS-11260 JNDI tutorial uses outdated syntax
  • GEOS-11276 Use style_body to define CSS style for a layer
  • GEOS-11288 Improve input validation in ClasspathPublisher

Bug:

  • GEOS-11174 GWC rest api returns erroneous truncated response when gzip http encoding is enabled
  • GEOS-11205 Layer page: style image fails if it is in isolated workspace
  • GEOS-11250 WFS GeoJSON encoder fails with an exception if an infinity number is used in the geometry
  • GEOS-11255 Multiple inserts in WPS with different idGen strategies does not work
  • GEOS-11256 Cannot retrieve LegendGraphic from a PostGIS datastore with ‘hideEmptyRules’ and ‘Support on the fly geometry simplification’ enabled
  • GEOS-11278 metadata: only selected tab is submitted
  • GEOS-11285 GWC REST Content-Encoding gzip returns broken response
  • GEOS-11291 GeoFence: Cleanup stale log4j references

For the complete list see 2.23.5 release notes.

Community Updates

Community module development:

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

About GeoServer 2.23 Series

Additional information on GeoServer 2.23 series:

Release notes: ( 2.23.5 | 2.23.4 | 2.23.3 | 2.23.2 | 2.23.1 | 2.23.0 | 2.23-RC1 )

by Andrea Aime at February 18, 2024 12:00 AM

February 15, 2024

Dear QGIS Community,

We are very pleased to announce that this year’s round of grants is now available. The call is open to anybody who wants to make a contribution to QGIS funded by our grant fund, subject to the call conditions outlined in the application form.

The deadline for this round is in four weeks, on 14 March 2024.

There are no new procedures in 2024. Please note the following guidelines established in previous years: 

  • The proposal must be submitted as a ‘QEP’ (QGIS Enhancement Proposal) issue in the repo: https://github.com/qgis/QGIS-Enhancement-Proposals (tagged as Grant-2024). Following this approach will allow people to ask questions and provide public feedback on individual proposals.
  • Proposals must clearly define the expected final result so that we can properly assess if the goal of the proposal has been reached.
  • The project budgets should account for PR reviewing expenses to ensure timely handling of the project-related PRs and avoid delays caused by relying on reviewer volunteer time. 
  • In the week after the QEP discussion period, the proposal authors are expected to write a short summary of the discussion that is suitable for use as a basis on which voting members make their decisions. 

The PSC of QGIS.ORG will examine the proposals and has veto power in case a proposal does not follow guidelines or is not in line with project priorities.

For more details, please read the introduction provided in the application form.

We look forward to seeing all your great ideas for improving QGIS!

by underdark at February 15, 2024 07:09 PM

Just like the European Space Agency (ESA), we advocate for and actively support Open Science, as we believe in the significance of collaborative efforts in advancing scientific knowledge and addressing global challenges. We acknowledge the transformative power of Open Science in driving interdiscipl ...

February 15, 2024 12:00 AM

February 13, 2024

There are times when I need a regular grid for an entire projection extent.  Meaning, for the extent of an entire projection, I need to create a regular grid of uniform tiles across the projection.  In past projects, these grids have been very helpful for data alignment and clipping data into uniform shapes and sizes. This has proved especially helpful in Machine Learning pipelines where I need to ensure pixel to pixel alignments between rasters in a specified location.

Gridding, tiling, and indexing type work has been around forever in geospatial, so there is not much to say about the method.  Basically, you take an extent and cut it up into a grid. In this case, the extent is for an entire projection.

I built a repository on Github and a quick method to do this via one command.

make build-grid epsg="EPSG:2193" width=1000 height=1000

For this method, the width and height are the desired grid cell size.  The units are the units for the projection.  EPSG:2193 (NZTM) is in metre units, so running the command above will make a grid of the NZTM projection populated with 1000m by 1000m cells.

The GitHub repository can be run using the Make/Docker method or users can access the python script directly using:

python3 create-grid.py EPSG:2193 1000 1000

In order to do so, you will need to have installed:

  • GDAL
  • GeoPandas
  • PyProj
  • Shapely

Happy mapping!

by xycarto at February 13, 2024 03:19 AM

February 08, 2024

February 07, 2024

According to the definition of software quality given by french Wikipedia

An overall assessment of quality takes into account external factors, directly observable by the user, as well as internal factors, observable by engineers during code reviews or maintenance work.

I have chosen in this article to only talk about the latter. The quality of software and more precisely QGIS is therefore not limited to what is described here. There is still much to say about:

  • Taking user feedback into account,
  • the documentation writing process,
  • translation management,
  • interoperability through the implementation of standards,
  • the extensibility using API,
  • the reversibility and resilience of the open source model…

These are subjects that we care a lot and deserve their own article.

I will focus here on the following issue: QGIS is free software and allows anyone with the necessary skills to modify the software. But how can we ensure that the multiple proposals for modifications to the software contribute to its improvement and do not harm its future maintenance?

Self-discipline

All developers contributing to QGIS code doesn’t belong to the same organization. They don’t all live in the same country, don’t necessarily have the same culture and don’t necessarily share the same interests or ambitions for the software. However, they share the awareness of modifying a common good and the desire to take care of it.

This awareness transcends professional awareness, the developer not only has a responsibility towards his employer, but also towards the entire community of users and contributors to the software.

This self-discipline is the foundation of the quality of the contributions of software like QGIS.

However, to err is human and it is essential to carry out checks for each modification proposal.

Automatic checks

With each modification proposal (called Pull Request or Merge Request), the QGIS GitHub platform automatically launches a set of automatic checks.

Example of proposed modification

Result of automatic checks on a modification proposal

The first of these checks is to build QGIS on the different systems on which it is distributed (Linux, Windows, MacOS) by integrating the proposed modification. It is inconceivable to integrate a modification that would prevent the application from being built on one of these systems.

The tests

The first problem posed by a proposed modification is the following “How can we be sure that what is going to be introduced does not break what already exists?”

To validate this assertion, we rely on automatic tests. This is a set of micro-programs called tests, which only purpose is to validate that part of the application behaves as expected. For example, there is a test which validates that when the user adds an entry in a data layer, then this entry is then present in the data layer. If a modification were to break this behavior, then the test would fail and the proposal would be rejected (or more likely corrected).

This makes it possible in particular to avoid regressions (they are very often called non-regression tests) and also to qualify the expected behavior.

There are approximately 1.3 Million lines of code for the QGIS application and 420K lines of test code, a ratio of 1 to 3. The presence of tests is mandatory for adding functionality, therefore the quantity of test code increases with the quantity of application code.

In blue the number of lines of code in QGIS, in red the number of lines of tests

There are currently over 900 groups of automatic tests in QGIS, most of which run in less than 2 seconds, for a total execution time of around 30 minutes.

We also see that certain parts of the QGIS code – the most recent – are better covered by the tests than other older ones. Developers are gradually working to improve this situation to reduce technical debt.

Code checks

Analogous to using a spell checker when writing a document, we carry out a set of quality checks on the source code. We check, for example, that the proposed modification does not contain misspelled words or “banned” words, that the API documentation has been correctly written or that the modified code respects certain formal rules of the programming language.

We recently had the opportunity to add a check based on the clang-tidy tool. The latter relies on the Clang compiler. It is capable of detecting programming errors by carrying out a static analysis of the code.

Clang-tidy is, for example, capable of detecting “narrowing conversions”.

Example of detecting “narrowing conversions”

In the example above, Clang-tidy detects that there has been a “narrowing conversion” and that the value of the port used in the network proxy configuration “may” be corrupted. In this case, this problem was reported on the QGIS issues platform and had to be corrected.

At that time, clang-tidy was not in place. Its use would have made it possible to avoid this anomaly and all the steps which led to its correction (exhaustive description of the issue, multiple exchanges to be able to reproduce it, investigation, correction, review of the modification), meaning a significant amount of human time which could thus have been avoided.

Peer review

A proposed modification that would validate all of the automatic checks described above would not necessarily be integrated into the QGIS code automatically. In fact, its code may be poorly designed or the modification poorly thought out. The relevance of the functionality may be doubtful, or duplicated with another. The integration of the modification would therefore potentially cause a burden for the people in charge of the corrective or evolutionary maintenance of the software.

It is therefore essential to include a human review in the process of accepting a modification.

This is more of a rereading of the substance of the proposal than of the form. For the latter, we favor the automatic checks described above in order to simplify the review process.

Therefore, human proofreading takes time, and this effort is growing with the quantity of modifications proposed in the QGIS code. The question of its funding arises, and discussions are in progress. The QGIS.org association notably dedicates a significant part of its budget to fund code reviews.

More than 100 modification proposals were reviewed and integrated during the month of December 2023. More than 30 different people contributed. More than 2000 files have been modified.

Therefore the wait for a proofreading can sometimes be long. It is also often the moment when disagreements are expressed. It is therefore a phase which can prove frustrating for contributors, but it is an important and rich moment in the community life of a free project.

To be continued !

As a core QGIS developer, and as a pure player OpenSource company, we believe it is fundamental to be involved in each step of the contribution process.

We are investing in the review process, improving automatic checks, and in the QGIS quality process in general. And we will continue to invest in these topics in order to help make QGIS a long-lasting and stable software.

If you would like to contribute or simply learn more about QGIS, do not hesitate to contact us at infos+qgis@oslandia.com and consult our QGIS support proposal.

by Julien Cabieces at February 07, 2024 12:55 PM

February 06, 2024

Update: The programme is now public.

The programme for pgconf.dev in Vancouver (May 28-31) has been selected, the speakers have been notified, and the whole thing should be posted on the web site relatively soon.

Vancouver, Canada

I have been on programme committees a number of times, but for regional and international FOSS4G events, never for a PostgreSQL event, and the parameters were notably different.

The parameter that was most important for selecting a programme this year was the over 180 submissions, versus the 33 available speaking slots. For FOSS4G conferences, it has been normal to have between two- and three-times as many submissions as slots. To have almost six-times as many made the process very difficult indeed.

Why only 33 speaking slots? Well, that’s a result of two things:

  • Assuming no more than modest growth over the last iteration of PgCon, puts attendence at around 200, which is the size of our plenary room. 200 attendees implies no more than 3 tracks of content.
  • Historically, PostgreSQL events use talks of about 50 minutes in length, within a one hour slot. Over three tracks and two days, that gives us around 33 talks (with slight variations depending on how much time is in plenary, keynotes or lightning talks).

The content of those 33 talks falls out from being the successor to PgCon. PgCon has historically been the event attended by all major contributors. There is an invitation-only contributors round-table on the pre-event day, specifically for the valuable face-to-face synch-up.

Seminary Room

Given only 33 slots, and a unique audience that contains so many contributors, the question of what pgconf.dev should “be” ends up focussed around making the best use of that audience. pgconf.dev should be a place where users, developers, and community organizers come together to focus on Postgres development and community growth.

That’s why in addition to talks about future development directions there are talks about PostgreSQL coding concepts, and patch review, and extensions. High throughput memory algorithms are good, but so is the best way to write a technical blog entry.

Getting from 180+ submissions to 33 selections (plus some stand-by talks in case of cancellations) was a process that consumed three calls of over 2 hours each and several hours of reading every submitted abstract.

The process was shepherded by the inimitable Jonathan Katz.

  • A first phase of just coding talks as either “acceptable” or “not relevant”. Any talks that all the committee members agreed was “not relevant” were dropped from contention.
  • A second phase where each member picked 40 talks from the remaining set into a kind of “personal program”. The talks with just one program member selecting them were then reviewed one at a time, and that member would make the case for them being retained, or let them drop.
  • A winnow looking for duplicate topic talks and selecting the strongest, or encouraging speakers to collaborate.
  • A third “personal program” phase, but this time narrowing the list to 33 talks each.
  • A winnow of the most highly ranked talks, to make sure they really fit the goal of the programme and weren’t just a topic we all happened to find “cool”.
  • A talk by talk review of all the remaining talks, ensuring we were comfortable with all choices, and with the aggregate make up of the programme.

The programme committee was great to work with, willing to speak up about their opinions, disagree amicably, and come to a consensus.

SFU

Since we had to leave 150 talks behind, there’s no doubt lots of speakers who are sad they weren’t selected, and there’s lots of talks that we would have taken if we had more slots.

If you read all the way to here, you must be serious about coming, so you need to register and book your hotel right away. Spaces are, really, no kidding, very limited.

February 06, 2024 04:00 PM

In an earlier post, I showed how it is possible to permanently position a legend in the QGIS Cloud map as part of a QGIS Cloud Pro subscription. To achieve this, the appearance of the map view was changed using CSS. In this post, I will describe exactly what this is and how it works. The appearance of the QGIS Cloud Web Client is controlled via CSS. CSS stands for Cascading Style Sheets.

February 06, 2024 12:00 AM

February 05, 2024

QGIS 3.36 is round the corner and as usual, there will be several new exciting features with the new release. Below is the list of features our team has added to the new release. This was made possible by generous funding from clients.

Render point clouds as a surface in 2D map views

Point clouds are rendered as individual points by default. Depending on the zoom level and density of the points, you might not be able to get a full picture of the map.

Rendering points as surface enables you to have a better understanding of the data before trying to do any analysis or processing. This has been possible in 3D map views for a couple of QGIS releases, now we have added the functionality also in 2D map views.

The feature generates a surface using triangulation on-the-fly from the points using the same symbology. Below you can see the difference between a point cloud rendered as individual points and rendered as a surface:

Point clouds as surface

Point clouds as individual points vs. as a TIN surface

The good news is that rendering as a surface also works well with global map shading, allowing users to get a nice hillshade:

Point clouds as surface with hillshade with hillshade

Point clouds as surface with hillshade

To enable this feature, you need to check the option for Render as a Surface (Triangulate) under the Layer Styling panel.

Point clouds styling panel

Settings to display point clouds as surface

Pro-tip: if the on-the-fly rendering as a surface takes too long to render, try increasing the Maximum error: for example 0.6 mm instead of the default 0.3 mm.

Flexible styling of classes

Previously, point cloud data visualisation in QGIS was limited to rendering all points with a uniform size and opacity. This made it difficult to differentiate between different point classes and highlight specific features of interest. To address this issue, we have introduced a new feature that allows users to customise the point size and opacity for each point cloud data class. This provides a flexible way for visualising point cloud data, allowing users to highlight specific point classes, e.g. by increasing the point size.

Assigning size and opacity to each point cloud class

Assigning size and opacity to each point cloud class

Point clouds with different sizes and opacity levels

Point clouds with different sizes and opacity levels

Set 3D map view extent in 2D map

Effectively navigating and visualising large-scale 3D datasets can be challenging on PCs with limited resources. To address this issue, we introduced a new feature that allows users to interactively limit the 3D scene, enabling them to focus on specific areas of interest. This new feature, conveniently accessible from the toolbar, eliminates the need for tedious manual entry of coordinates for bounding boxes. Instead, users can simply drag and draw a box around the desired area, instantly restricting the 3D scene to that specific extent. This interactive approach significantly enhances the user experience and streamlines the process of exploring and analysing 3D data:

Interactive selection of 3D map scene from 2D map

Interactive selection of 3D map scene from 2D map

Python API for 3D views

Creating and viewing 3D maps in QGIS with the correct camera location and angle, scene tilt, light, and other parameters can be a time-consuming and error-prone process. This is because it requires users to manually adjust these settings, often through trial and error. However, with the introduction of the new 3D map view API in QGIS, Python plugins can now automate this process, making it much easier, consistent and more efficient to create high-quality 3D maps that are visually appealing and informative.

# List all open 3D map canvases
iface.mapCanvases3D()
# [<qgis._3d.Qgs3DMapCanvas object at 0x7f23491b5e10>]
canvas = iface.mapCanvases3D()[0]

Now let’s try something more complicated:

# Let's change some settings!
ms = canvas.mapSettings()
ms.setEyeDomeLightingEnabled(True)
ms.setBackgroundColor(QColor('beige'))
ms.setTerrainMapTheme('dtm')
ms.setFieldOfView(110)

# Move the camera to look at specific map coordinates in layer's CRS
cam = canvas.cameraController()
mapPoint = QgsVector3D(-498175.92, -1205400.58, 210)
worldPoint = ms.mapToWorldCoordinates(mapPoint)
cam.setLookingAtPoint(worldPoint, 60, 45, 100)

# Create four new 3D map views
c1 = iface.createNewMapCanvas3D('South View')
c2 = iface.createNewMapCanvas3D('West View')
c3 = iface.createNewMapCanvas3D('North View')
c4 = iface.createNewMapCanvas3D('East View')

# Apply settings to all open 3D map views
for canvas in iface.mapCanvases3D():
	canvas.mapSettings().setEyeDomeLightingEnabled(True)

# Define a camera pose to update the views' cameras
pose = QgsCameraPose()
pose.setCenterPoint(QgsVector3D(0, 210, 0))  # This is in 3D world coordinates
pose.setDistanceFromCenterPoint(100)
pose.setPitchAngle(75)  # Tilt the camera by 75 degrees
pose.setHeadingAngle(0)  # Looking towards North
c1.cameraController().setCameraPose(pose)
pose.setHeadingAngle(90)  # Towards East
c2.cameraController().setCameraPose(pose)
pose.setHeadingAngle(180)  # Towards South
c3.cameraController().setCameraPose(pose)
pose.setHeadingAngle(270)  # Towards West
c4.cameraController().setCameraPose(pose)

# We can set the 3D map views 2D extent to always match the main 2D canvas one
# Our 3D views get updated while zooming/panning the main 2D canvas
canvas = iface.mapCanvas()
canvas.extentsChanged.connect(lambda :c1.mapSettings().setExtent(canvas.extent()))
canvas.extentsChanged.connect(lambda :c2.mapSettings().setExtent(canvas.extent()))
canvas.extentsChanged.connect(lambda :c3.mapSettings().setExtent(canvas.extent()))
canvas.extentsChanged.connect(lambda :c4.mapSettings().setExtent(canvas.extent()))

Changing 3D view settings through Python

Changing 3D view settings through Python

More point clouds attributes

LAS/LAZ/COPC point clouds have a classificationFlags attribute that stores four types of information (Synthetic, Keypoint, Withheld, and Overlap) in a single value. This saves space, but it makes it difficult to use the information for styling or filtering, as you need to write complex expressions.

To make it easier to use, we are following the approach introduced in PDAL 2.6: the classificationFlags attribute gets replaced with four separate attributes: Synthetic, Keypoint, Withheld, and Overlap. This will make it easier to include these attributes in styling and filtering expressions.

Performance enhancement for rendering

To improve the performance of point cloud rendering in QGIS, we introduced a new caching system to minimise the need for repeated decompression of LAS node data while panning or zooming. This caching mechanism efficiently stores decompressed points for each unique combination of layer URI, node, requested attributes, filter extent, and filter expression. This enables rapid rendering of previously cached nodes, significantly enhancing the overall rendering performance in 2D and 3D maps.

Performance can vary depending on actual data, but on a local sample COPC file, it renders 7 times faster with this change.

Labels for mesh layer

Viewing mesh data has been possible through styling, plotting or using the Identify tool. But now you can also create labels on mesh surfaces or vertices similar to vector layers.

To display labels for your mesh data, simply open the styling panel and enable labels for:

  • Labels on Vertices
  • Labels on Surfaces

Label settings for mesh layers

Label settings for mesh layers

Below is an example of mesh Z values at vertices (yellow) and mesh areas at cell centre (purple):

Example of labels on a mesh layer

Example of labels on a mesh layer

Want more changes in QGIS?

Do you want to see more improvements and new features in QGIS? Do not hesitate to contact us to discuss your requiremnets.

February 05, 2024 08:00 AM

February 04, 2024

My 32 week running season starts on February 19 and ends on September 29, at Bear Lake if everything goes right. My preseason running has been light on running because of various maladies. I strained my back at the end of December and just as I recovered from that I experienced some knee inflammation that was badly aggravated by running. For the past three weeks I've switched to weight training and chugging on the elliptical machines at a nearby gym. I'm doing 5x5s of squats, deadlifts, etc three times a week and 4-5 x 3 minute hard elliptical intervals once or twice a week. In between I've been walking briskly on the bike path or hiking on trails. I'd hoped to be actually running 6 hours a week by now, but am adjusting and getting some good workouts in. By February 19, I think I'll be able to take my interval workouts outside and switch from hiking to running without beating up on my knee.

by Sean Gillies at February 04, 2024 11:09 PM

The Open Source Geospatial Foundation (OSGeo) today celebrates its 18th anniversary, underscoring its pivotal role in the development of open source geospatial software and its impact on the world. Founded in 2006, OSGeo’s mission is to support and promote the collaborative development of open geospatial technologies and data. Over the years, it has become a cornerstone of the open geospatial community, fostering innovation, education and adoption of open source geospatial software worldwide.

The post Celebrating 18 Years of the Open Source Geospatial Foundation (OSGeo) appeared first on Markus Neteler Consulting.

by Markus at February 04, 2024 02:42 PM

February 03, 2024

Tools used: QGIS 3.34.3 Prizren; Inkscape 1.2, a web browser Most of this is reasonably standard ‘get data, make maps’ – you can flick straight to cartographic magic for the un-standard parts if you want! The product Brief and design choices The brief for this map was to visualise a bicycle ride route – and… Read More »Route mapping using Strava, OpenStreetMap and QQIS

by Adam at February 03, 2024 11:16 PM

Besides following hashtags, such as #GISChat, #QGIS, #OpenStreetMap, #FOSS4G, and #OSGeo, curating good lists is probably the best way to stay up to date with geospatial developments.

To get you started (or to potentially enrich your existing lists), I thought I’d share my Geospatial and SpatialDataScience lists with you. And the best thing: you don’t need to go through all the >150 entries manually! Instead, go to your Mastodon account settings and under “Import and export” you’ll find a tool to import and merge my list.csv with your lists:

And if you are not following the geospatial hashtags yet, you can search or click on the hashtags you’re interested in and start following to get all tagged posts into your timeline:

by underdark at February 03, 2024 09:54 AM

February 01, 2024

GeoSpatial Techno is a startup focused on geospatial information that is providing e-learning courses to enhance the knowledge of geospatial information users, students, and other startups. The main approach of this startup is providing quality, valid specialized training in the field of geospatial information.

( YouTube | LinkedIn | Facebook | Reddit | X )


A Comprehensive Guide to publishing a Shapefile in GeoServer

In this session, we want to talk about “How to Publish Shapefile in GeoServer” comprehensively. If you want to access the complete tutorial, simply click on the link

Introduction

The Data section contains configuration options for all the different data-related settings that GeoServer uses to access and publish geospatial information. It also describes how to load, manage, and publish data in the GeoServer web interface. Each section contains the specific pages that provide add, view, edit, and delete capabilities.

Note. In this blog post, we used GeoServer version 2.20.0.

Workspaces

A Workspace serves as a means to group and organize similar layers together. It enables you to associate multiple layers and stores with a single workspace. Each workspace can be managed independently, with its own security policies, data administrator, and web services. Generally, a workspace is created for each project, along with its corresponding stores and layers.

Add a workspace

To create a new workspace, navigate to Data > Workspaces page. Click on the Add new workspace, then you have to enter a Workspace Name and Namespace URI.

  • Workspace Name: It is an identifier describing your project. It must not exceed ten characters or contain spaces (due to use as an XML “prefix” when downloading content).
  • Namespace URI: URI stands for Uniform Resource Identifier, is a formal system for uniquely identifying resources, and consists of two types: URL and URN. A Namespace URI does not need to point to an actual location on the web and only needs to be a unique identifier.
  • Default Workspace: This setting is useful when you only have one workspace defined. The setting allows users to communicate with the web service using just the layer name (rather than prefix:layer name required when managing hundreds of workspaces). select the Default Workspace checkbox to assign this as your default workspace.
  • Sometimes the same feature type needs to be published multiple times with a different mapping and with the same name. This can be done in GeoServer using Isolated Workspaces functionality.

Press the Submit button to save your new workspace.

Edit a workspace

To view or edit a workspace, click on the Workspace name, then a workspace configuration page will be displayed.

  • For Settings, select the Enabled checkbox to customize the settings and contact details for the workspace level. This allows you to define an introduction to your workspace, and override the global settings for your workspace.
  • Use the checkbox located next to each service to override the Global Settings for the associated service. Once enabled, clicking on the Services link will open the settings page for the service, allowing default values for the service title, abstract, and other details to be supplied.
  • The Security tab allows to set data access rules at the workspace level. To create/edit the workspace’s data access rules, check/uncheck checkboxes according to the desired role.

Remove a workspace

To remove a workspace, select it by clicking the checkbox next to the workspace. Multiple workspaces can be selected, or all can be selected by clicking the checkbox in the header. Click the Remove selected workspace(s) link. Now you will be asked to confirm or cancel the removal.

Pressing OK removes the selected workspace(s).

Stores

The Stores manage the connection parameters between GeoServer and the data sources where your spatial data reside. They provide a mechanism for GeoServer to connect to various data repositories, including file systems, databases, and cloud storage services. Each store represents a unique data source and has its configuration settings.

Add a store

To add a Store, navigate to Data > Stores page. Click on Add new store, then you will be prompted to choose a data source. GeoServer supports several different data formats, but they are classified into three types: “Vector data”, “Raster data”, and “Cascaded Services”.

  • Vector data formats include Shapefile, GeoPackage, PostGIS, and Properties. The most common and widely used option is Shapefile.
  • Raster data formats include ArcGrid, GeoPackage, GeoTIFF, ImageMosaic, and WorldImage. The most used and well-known are the GeoTIFF and the WorldImage. GeoTIFF is a spatial extension of the “TIFF” format and tags image files with geographic information. A WorldImage is similar, but georeferencing information is saved in an external text file.
  • Cascaded Services include WFS, WMS, and WMTS. GeoServer can proxy a remote Web Map Service and Web Map Tile Service and load it as a store in GeoServer.

Other data sources are supplied as GeoServer extensions. Extensions are downloadable modules that add functionality to GeoServer. Click the appropriate data source to configure the store, because the connection parameters vary depending on data format.

To create a Shapefile data store, follow these steps:

  • Select the desired workspace from the drop-down menu.
  • Enter the Data Source Name. Make sure the “Enabled” checkbox is selected. Otherwise, access to the store along with all the datasets defined, will be disabled for it.
  • In the “Shapefile location”, click on the Browse link to define the location of the shapefile.
  • The DBF file format has a field for character encoding, but it doesn’t always accurately indicate the actual encoding used. As a result, it is important to specify the DBF character set correctly when decoding strings to ensure accurate interpretation of the data.

When finished, press the Save button. Now it will automatically redirect to the Add New Layer page, which will be completely described in the Layer section. Next, we will explain how to edit and remove the store.

Edit a store

To view or edit a store, click on the Store name. A Store configuration page will be displayed. The exact contents of this page depend on the specific format of the Store. After your configuration is modified, press the Save button.

Remove a store

To remove a Store, click the checkbox next to the store. Multiple stores can be selected, or all can be selected by clicking the checkbox in the header. Click the Remove selected stores. You will be asked to confirm the removal of the configuration for the store(s) and all resources defined under them.

Pressing OK removes the selected Store(s), and returns to the Stores page.

Layers

From the administration interface, navigate to the Data > Layers page. On this page, you can view and edit existing layers, add a new layer, or remove a layer. It also shows you the type of layers in the Type column, with a different icon for vector and raster layers, according to the geometry shape. The Title, Workspace, and Store values of each layer are shown.

Add a layer

Clicking the Add a new layer, brings up a New Layer Chooser panel. The menu displays all currently enabled stores. If you want to add a new layer for a published resource, click on Publish Again. Note that when republishing the name of the new layer may have to be modified to avoid conflict with an existing layer.

The beginning sections (Basic Resource Info, Keywords, and Metadata link) provide metadata, specifically textual information that makes the layer data easier to understand and work with. The metadata information will appear in the capabilities documents which refer to the layer. These options are:

  • Name: The identifier used to reference the layer in WMS requests that are filled automatically. Note that for a new layer for an already-published resource, the name must be changed to avoid conflict.
  • Enabled: A layer that is not enabled won’t be available to any kind of request, it will just show up in the configuration and in REST config.
  • Advertised: A layer is advertised by default. A non-advertised layer will be available in all data access requests (for example, WMS GetMap, WMS GetFeature) but won’t appear in any capabilities document or the layer preview.
  • Title: The human-readable description to briefly identify the layer to clients that filled automatically. GeoServer provides an item for the title and abstract and describes how to specify metadata in different languages. By default, it’s disabled and can be enabled from the i18n checkbox.
  • Abstract: It describes the layer in detail.
  • Keywords: List of short words associated with the layer to assist catalog searching. To add a new keyword, enter your keyword, then press the Add Keyword button to add it.
  • Metadata & Data Links: It allows linking to external documents that describe the data layer. The Type input provides a few example types, like FGDC or ISO19115, but allows any other type to be declared. Format provides its mime type, while URL points to the actual metadata.

A Coordinate Reference System (CRS) defines how georeferenced spatial data relates to real locations on the Earth’s surface. GeoServer needs to know the CRS of your data. This information is used for computing the latitude/longitude bounding box and reprojecting the data during both WMS and WFS requests.

  • Native SRS: Specifies the coordinate system the layer is stored in. Clicking the projection link displays a description of the SRS.
  • Declared SRS: Specifies the coordinate system GeoServer publishes to clients.
  • SRS Handling: Determines how GeoServer should handle projection when the two SRSes differ. Possible values are:
    • Force declared: This is the default option and normally the best course of action. Use this option when the source has no native CRS, has a wrong one, or has one matching the EPSG code.
    • Reproject from native: This setting should be used when the native data set has a CRS that does not match any official EPSG. E.g. Lambert Conformal Conic to WGS84.
    • Keep native: This is a setting that should be used in very rare cases. Keeping native means using the declared one in the capabilities documents, but then using the native CRS in all other requests.

The Bounding Box determines the extent of the data within a layer. It includes two items: “Native Bounding Box” and “Lat/Lon Bounding Box”. Generate the bounds for the layer by pressing the Compute from data and Compute from native bounds button in the Bounding Boxes section.

Vector layers have a list of the “Feature Type Details”. These include the Property and Type of a data source. Remember that, if you want to change your data by ArcGIS or QGIS, like add or remove features or fields, or edit the attribute table contents, there is no need to create a layer again in the GeoServer, just press the Reload feature type, so your layer will be updated.

Remember that GeoServer, by default, publishes all the features that are currently available in the layer. However, if you wish to limit the features to a specific subset, you can achieve this by specifying a CQL filter in the configuration. Upon completing the layer configuration, finalize the process by pressing the Save button. This action will create the layer based on the specifications you have provided.

Edit a layer

To view or edit a layer, click on the Layer Name from the Layer page. A layer configuration page will be displayed. After your configuration is modified, press the Save button.

Remove a layer

To remove a layer, select the checkbox next to the layer. Multiple layers can be selected, or all can be selected by clicking the checkbox in the header. By clicking the Remove selected layers link, you will be asked to confirm the removal of the configuration for the layer(s) and all resources defined under them.

Press OK removes the selected layer(s), and returns to the Layers page.

by GeoSpatial Techno at February 01, 2024 12:00 AM

January 30, 2024

La última versión de gvSIG Desktop además de considerables mejoras ha traído un cambio en la interfaz del programa, modernizando el aspecto de los iconos utilizados.

Hoy os compartimos el manual completo en PDF de gvSIG Desktop 2.6, que es una guía estupenda para los nuevos usuarios y a los que lleváis tiempo trabajando con gvSIG Desktop os puede ser útil para familiarizaros con los nuevos iconos.

Y aunque seréis los menos, para los que queráis seguir utilizando el juego de iconos «clásico» podéis instalarlo desde el Administrador de Complementos.

El manual de gvSIG Desktop 2.6 se puede descargar en este enlace.

by Alvaro at January 30, 2024 10:23 AM

January 29, 2024

Lizmap Web Client 3.7

Nous sommes heureux d'annoncer la sortie de Lizmap Web Client 3.7, la nouvelle version majeure de l'application.

Financeurs

Avignon
Territoire de Belfort
Calvados French province
Direction Départemental du Territoire et de la Mer de l'Hérault
Faunalia
Lons-le-Saunier
Grand Narbonne urban community
Valabre

Pré-requis et installation

Il est désormais requis d'avoir un QGIS serveur minimum 3.22. Cependant, nous recommandons fortement d'utiliser une version LTR plus récente, comme la version 3.28 ou bien même la prochaine version LTR 3.34. Consultez la feuille de route QGIS.

Pour utiliser pleinement de cette version 3.7, n'oubliez pas de mettre à jour votre extension Lizmap dans QGIS bureautique. Nous avons écrit un article dédié sur cette nouvelle version.

Fonctionnalités

Refonte du thème par défaut

Un nouveau thème est disponible, apportant une interface utilisateur plus à jour. Il est désormais également plus facile de mettre à jour ces couleurs, car cela a été centralisé en utilisant seulement quelques variables CSS.

Nouveau thème

Dataviz

Dans l'extension, vous pouvez trouver de nouveaux paramètres pour chaque graphique. Par exemple, il est possible de définir deux titres différents, selon l'endroit où le graphique est affiché : soit dans le panneau principal de visualisation de données, soit dans une popup.

La principale nouvelle fonctionnalité est la mise en page par Glisser&Déposer. Nous nous sommes inspirés de la fonctionnalité native de QGIS concernant la Mise en page du formulaire Glisser-Déposer. Dans Lizmap, lorsque vous avez de nombreux graphiques à afficher, vous pouvez les organiser en onglets ou conteneurs.

Dans QGIS, voici un exemple de mise en page des graphiques :

New Drag&Drop layout for Dataviz

et voici le résultat dans Lizmap Web Client :

New Drag&Drop layout for Dataviz

Ces nouvelles fonctionnalités ont été financées par DDTM 34.

Légende

C'est l'une des fonctionnalités les plus visibles et attendues de Lizmap, il est possible de cocher/décocher les éléments de la légende individuellement.

Nous avons également revu la façon dont Lizmap gérait les couches de base dans le projet (fonds de carte). Les utilisateurs sont désormais invités à utiliser le groupe baselayers dans la légende pour définir les couches de base. À l'aide d'une version à jour de l'extension, vous pouvez utiliser l'onglet "Fonds" pour vous aider.

Nous avons également décidé d'utiliser le même comportement que dans QGIS Bureautique concernant la manière dont les utilisateurs manipulent la légende. Désormais, lors de l'activation d'un groupe, toutes les couches incluses dans ce groupe ne seront pas activées automatiquement.

New theme

Pour inclure ces nouvelles fonctionnalités, beaucoup de re-factorisation du code Javascript ont été réalisées sous le capot, financées par le département du Calvados et Le Grand Narbonne.

Mise en page

Dans l'extension, un nouveau panneau sur les mises en page a été ajouté. Vous êtes invités à jeter un œil à ces nouveaux paramètres. Il est possible de :

  • définir par mise en page si nous l'activons ou non sur l'interface Web. Avant, il était seulement possible de choisir d'activer ou non l'impression à l'échelle des propriétés du projet
  • définir les groupes Lizmap qui sont autorisés à accéder à chaque mise en page
  • définir une icône personnalisée lorsque la mise en page est basée sur un atlas.
  • réduire le nombre de formats disponibles. Plus besoin de Javascript pour avoir une interface simplifiée
  • ...

Nouvelles options concernant les mises en page dans l'extension

Ces nouvelles fonctionnalités ont été financées par DDTM 34.

Au cours de ce travail, nous avons déprécié l'extension QGIS serveur AtlasPrint. Lizmap utilise désormais la fonctionnalité native de QGIS Serveur pour exporter en PDF un élément de l'atlas.

Edition

WebDAV

Faunalia a contribué directement au code source de Lizmap en ajoutant le support WebDAV dans le formulaire d'édition lorsque l'outil d'édition a été défini sur stockage WebDAV. Vous pouvez consulter la documentation en ligne. Cela fonctionne également lors de l'affichage de la popup.

Relations entre les tables

Le support des relations 1-n entre tables a été amélioré lors de l'édition de ces couches :

  • Ajout d'une nouvelle entité "enfant" depuis la popup d'un parent
  • Affichage du tableau des entités "enfants" depuis le formulaire d'édition d'un parent

Add a child

Add a child

Ces améliorations des relations 1-n ont été financées à la fois par la ville d'Avignon et Valabre.

Dessin

Texte et mesure

Il est possible d'annoter la carte avec du texte dans l'outil de dessin. Les mesures ont également été améliorées.

New draw text and measure options

Ces fonctionnalités ont été financées par le Territoire de Belfort et Lons-le-Saunier.

Contraintes

Lors du dessin de certaines géométries sur Lizmap, vous pouvez désormais définir une contrainte de longueur et/ou d'angle.

Constraints

Action

De nouveaux "contextes" ont été ajoutés à la fonctionnalité Actions. Avant, les actions n'étaient disponibles que pour le contexte d'entité. Avec la version 3.7, les actions peuvent être définies dans le contexte couche (similaire à la fonctionnalité native de QGIS) ou même au niveau duprojet.

Nouveaux contextes pour les actions

Ces nouveautés ont été financées par Porte du Soleil.

Javascript

En raison du travail qui a été effectué lors de la légende ou d'autres fonctionnalités de Lizmap, certains scripts Javascript précédents pourraient ne plus fonctionner et devront être adaptés.

Bonne nouvelle, certains de ces anciens scripts pourraient ne plus être nécessaires. Par exemple, à propos de la légende, vous êtes invités à passer au thème QGIS natif.

Téléchargement

Vous pouvez télécharger le dernier zip sur notre page des sorties.

Vous pouvez également consulter la liste des modifications complètes ("changelog") de la version 3.7.0, en anglais.

Modules

À la date du 29 janvier 2024, voici la liste des modules qui ont été mis à jour pour 3.7 :

Les autres modules sont en cours.

Nous espérons que vous allez apprécier cette nouvelle version 🦎

L'équipe 3Liz

by L'équipe 3Liz at January 29, 2024 11:00 AM

Lizmap Web Client 3.7

3Liz is pleased to announce the release of Lizmap Web Client 3.7, the new major version of the application.

Funders

Avignon
Territoire de Belfort
Calvados French province
Direction Départemental du Territoire et de la Mer de l'Hérault
Faunalia
Lons-le-Saunier
Grand Narbonne urban community
Valabre

Pre-requirements and installation

It is now required to have a minimum QGIS server 3.22. However, we highly recommend using the latest LTR version, i.e. version 3.28 or even soon the next LTR version 3.34. Check the QGIS roadmap.

To take full advantage of this version 3.7, don't forget to update your Lizmap plugin in QGIS desktop. We've written an article dedicated to this new version.

Features

Overhaul of the default theme

A new theme is available, bringing a more up-to-date UI. It's now also easier to update these colors, because it has been centralized using just a few CSS variables.

New theme

Dataviz

In the plugin, you can find new settings about each plot. For instance, it's possible to set two different titles, depending on where the plot is displayed : either in the main dataviz panel or within a popup.

The main new feature is the Drag&Drop layout. We have been inspired by the native feature in QGIS about the Drag&Drop form layout. In Lizmap, when you have many plots to display, you can organize them in tabs or containers.

In QGIS, this is an example of the layout :

New Drag&Drop layout for Dataviz

and the result in Lizmap Web Client :

New Drag&Drop layout for Dataviz

These new features have been funded by DDTM 34.

Legend

This is one of the most visible and expected feature in Lizmap, it's possible to check/uncheck the legend items individually.

We also reviewed the way Lizmap was managing base layers in the project. Users are now invited to use the baselayers group in the legend to define your base layers. With an updated version of the plugin, use the "Baselayers" tab to help you.

We also decided to stick to the same behavior as in QGIS Desktop on how users are manipulating the legend. Now, when enabling a group, it will not toggle "ON" all layers included within this group.

New theme

To include these new features, a lot of Javascript refactoring has been done under the hood, funded by both Calvados province and Le Grand Narbonne.

Layouts

In the plugin, a new panel about layouts landed. You are invited to have a look to these new settings. It's possible to :

  • set per layout if we enable it or not on the web interface. Before, it was only possible to choose to enable or not printing capabilities at the project level.
  • define Lizmap groups which are allowed to access this layout
  • define a custom icon when the layout is based on an atlas.
  • reduce the number of formats available. No more Javascript needed to have a simplified interface
  • ...

New print options in the plugin

These new features have been funded by DDTM 34.

During this work, we deprecated the QGIS server plugin AtlasPrint. Lizmap now uses the native feature from QGIS Server for printing an atlas feature.

Editing

WebDAV

Faunalia contributed directly on the Lizmap source code by adding WebDAV support in form when the editing widget has been set to WebDAV storage, check the online documentation. It works as well when displaying the popup.

Relations between tables

The support of relations 1-n between tables has been improved when editing these layers :

  • Adding new "child" features from the popup of a parent
  • Displaying the table of "child" features from the editing form of a parent

Add a child

Add a child

These improvements about relations 1-n were funded by both Avignon city and Valabre.

Drawing

Text and measures

It's possible to annotate the map with some text in the drawing tool. Measures have been improved as well.

New draw text and measure options

These features were funded by Territoire de Belfort and Lons-le-Saunier.

Constraints

When digitizing some geometries on Lizmap, you can now set some length and/or angle constraints.

Constraints

Actions

Some new scopes have been added the Actions feature. Before, it was only the feature scope. With 3.7, Actions can be defined in the layer scope or (similar to QGIS native actions feature) or even in the project scope.

New contexts for Actions

These new features have been funded by Porte du Soleil.

Javascript

Due to the work which have been done during the legend or other features in Lizmap, some previous Javascript script might not work anymore and need to be adapted.

Good news, some of these legacy scripts might not be needed anymore. For instance, about the legend, you are invited to switch to the native QGIS theme feature.

Download

You can download the latest zip on our releases page.

You can also check the full changelog of version 3.7.0.

Modules

As of January 29rd 2024, this is the list of modules which have been released for 3.7 :

Other modules are work-in-progress.

We hope you will enjoy this new version 🦎

The 3Liz team

by The 3Liz team at January 29, 2024 11:00 AM

January 27, 2024

The Trajectools toolbox has continued growing:

I’m continuously testing the algorithms integrated so far to see if they work as GIS users would expect and can to ensure that they can be integrated in Processing model seamlessly.

Because naming things is tricky, I’m currently struggling with how to best group the toolbox algorithms into meaningful categories. I looked into the categories mentioned in OGC Moving Features Access but honestly found them kind of lacking:

Andrienko et al.’s book “Visual Analytics of Movement” comes closer to what I’m looking for:

… but I’m not convinced yet. So take the above listed three categories with a grain of salt. Those may change before the release. (Any inputs / feedback / recommendation welcome!)

Let me close this quick status update with a screencast showcasing stop detection in AIS data, featuring the recently added trajectory styling using interpolated lines:

While Trajectools is getting ready for its 2.0 release, you can get the current development version directly from https://github.com/movingpandas/qgis-processing-trajectory.

by underdark at January 27, 2024 01:38 PM

January 26, 2024

I must have said this before but I will say it again, if you live anywhere near to London and you are into geotech, maps or location influenced applications then you should give Geomob a try. I’d offer you a money back guarantee but as it’s free that isn’t necesary but more on that later.

On Wednesday night (24th Jan 2024) we had nearly a hundred people attending what truly was a cracking event, the room was full (almost overfull), the speakers were eclectic, wide ranging and brilliant, the conversation was sparkling and mappy and it was a treat to be able to stand outside the pub drinking in January.

For a run down on the 5 speakers and their talks have a look at the @Geomob thread on mastodon

The talks covered a new javascript library, a Welsh language version of OSM, crowd sourcing neighbourhood boundaries in New Zealand, mapping bus routes and stops in India and the audience favourite (and mine) A Map Inside. This was a perfect selection of talks, technical, quirky, passionate and absorbing. As always, the best is saved for the end when we go to the nearby pub and chat, make new friends and discover new opportunities.

There is something very special about Geomob and that is perhaps evidenced by its expansion from its origins in London to regular events in Barcelona, Berlin, Finland, Lisbon, Munich and Tel Aviv. Geomob would not be possible without the energy and commitment of Ed Freyfogle whose company OpenCage is the principal sponsor of the events (and the podcast) and the generous sponsors – OpenCage, Mappery, Esri UK, Ed Parsons, Geolytix and SplashMaps.

But here is the rub, the numbers are increasing (which is good) and beer prices are also increasing (which is not so good) so the cost of running the events is increasing faster than sponsorship. We need more sponsors or larger sponsorship to keep Geomob growing and spreading geo-goodness to a wider audience, can you help us? It could be an individual or a company sponsoring events in a city or worldwide or it could be that you would like to sponsor a podcast episode and get a mention of your organisation as a sponsor in our podcast (great if you are hiring or launching a new service). Ed and I have some ideas for novel approaches to sponsorship and would be happy to discuss them with you, just message me through the contact form.

Geomob always needs speakers at the events and on the podcast so if you fancy presenting or being interviewed get in touch with us.

by Steven at January 26, 2024 02:38 PM

January 25, 2024

January 24, 2024

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

This is a stable release of GeoServer recommended for production use. GeoServer 2.24.2 is made in conjunction with GeoTools 30.2, and GeoWebCache 1.24.2.

Thanks to Jody Garnett (GeoCat) for making this release, everyone who contributed, and to Georg Weickelt and Peter Smythe for preflight testing.

Security Considerations

This release addresses security vulnerabilities and is considered an essential upgrade for production systems.

See project security policy for more information on how security vulnerabilities are managed.

Release notes

Improvement:

  • GEOS-11213 Improve REST external upload method unzipping
  • GEOS-11246 Schemaless plugin performance for WFS
  • GEOS-11219 Upgraded mail and activation libraries for SMTP compatibility

Bug:

  • GEOS-9757 Return a service exception when client provided WMS dimensions are not a match
  • GEOS-11051 Env parametrization does not save correctly in AuthKey extension
  • GEOS-11223 Layer not visible in preview/capabilities if security closes the workspace, but allows access to the layer
  • GEOS-11224 Platform independent binary doesn’t start properly with default data directory
  • GEOS-11235 preauthentication filters - session reuse even after having logout
  • GEOS-11241 ModificationProxy breaks information hidding on CatalogInfo.accept(CatalogVisitor) exposing the proxied object
  • GEOS-11250 WFS GeoJSON encoder fails with an exception if an infinity number is used in the geometry
  • GEOS-11255 Multiple inserts in WPS with different idGen strategies does not work

Task:

For the complete list see 2.24.2 release notes.

Community Updates

Community module development:

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

About GeoServer 2.24 Series

Additional information on GeoServer 2.24 series:

Release notes: ( 2.24.2 | 2.24.1 | 2.24.0 | 2.24-RC )

by Jody Garnett at January 24, 2024 12:00 AM

January 23, 2024

January 20, 2024

Fine anno, tempo di elenchi (bilanci, no). Nel 2023 ho letto pochino.

David Graeber, Debito

Questo è il libro che mi ha impegnato per più tempo. È un saggio, ed era da tempo che non leggevo un saggio, non sono più abituato allo stile e all’impegno richiesto. È un testo rivoluzionario a livello sociologico e psicologico (smonta il senso di colpa!) ancora più che a livello economico. Ha uno stile abbastanza scorrevole (per me) ma comunque è denso di nozioni, confronti tra fatti e conseguenze scagliate come frecce ad ogni pagina. Non conoscevo David Graeber prima della pubblicazione postuma del libro L’alba di tutto (The dawn of everything), scritto a quattro mani con l’archeologo David Wengrow. Ho pensato che non ci fosse nessuna fretta e fosse invece un bene partire da qui per conoscere il lavoro di Graeber, e sono contento di averlo fatto.

Enzo Barnabà, Morte agli Italiani!

Il massacro di Aigues-Mortes, che il 17 agosto 1893 costò la vita a nove operai italiani linciati da una folla inferocita, rappresenta un episodio capitale nella storia dei rapporti tra l’Italia e la Francia.

Questo libro di Enzo Barnabà è breve, preciso e senza orpelli.

Racconta la tragedia del massacro di Aigues-Mortes, le premesse che lo hanno reso possibile, le conseguenze che ebbe in Italia capaci di sconvolgere gli assetti politici sia del governo sia delle giovani formazioni socialiste.

Lucia Tozzi, Dopo il turismo

Questo libro è stato scritto di getto nei mesi del lockdown. Trafigge come una spada convinzioni e luoghi comuni, in modo anche un po’ crudele. Il turismo è insostenibile. Distrugge le comunità delle persone, i luoghi abitati da queste comunità.

Sono passati appena 3 anni e sembra la cronaca della rivoluzione mancata di un altro pianeta. Abbiamo già dimenticato tutto quello che è accaduto e quello che avrebbe potuto accadere.

Il libro può essere “acquistato” gratuitamente in formato ePub dal sito dell’editore nottetempo.

Luca Mercalli, Salire in montagna

La cosa che mi fa incazzare di questo libro è che è scritto da una persona di cui avevo una stima incondizionata, frutto di altre letture (non della trasmissione televisiva). Ma questo libro sembra scritto da Paolo Rumiz. Infatti Mercalli ce l’ha con chi abita in montagna, con chi non ci abita più, con chi non ci abita e non ci ha mai abitato. Lo scopo principale del libro è lamentarsi della burocrazia che gli impedisce di costruire la sua seconda casa, dove può trovare riparo dalle zanzare della sua abitazione indipendente di pianura. Salire in montagna sarebbe un antidoto al riscaldamento globale, dice il sottotitolo, ma se va bene dire una fesseria del genere al bar, trovarlo propagandato da un climatologo fa per l’appunto incazzare. Le montagne tutte e in particolare le Alpi sono uno degli ecosistemi più fragili di fronte al cambiamento climatico, e per fortuna questa semplice nozione fa capolino qua e là tra le pagine del libro. Costruire una casa recuperando un edificio storico invece che buttarlo giù è una bella cosa, molto costosa (ma Mercalli alla fine non ci dice quanto) ma ne vale la pena perché potremmo ripopolare la montagna lavorando al computer, secondo la logica deformata di questo libro. Non ne sopporto l’idea di fondo perché è la propaganda di una idea individualista, come se i venti milioni di abitanti della pianura padana potessero trovare spazio per la loro seconda casa sulle montagne e salvarsi così tutti dal riscaldamento globale (che li lascerà comunque a morire di fame). E nelle prime pagine è riportata virgola per virgola una pseudoetimologia sull’idronimo della Dora presa da Wikipedia, che mi ha reso da subito indisposto. E non c’è nemmeno una carta geografica.

Assia Djebar, Bianco d’Algeria

Questo libro è sicuramente quello che ho faticato di più a leggere, nonostante non sia molto lungo. Trasuda nella sua componente principale un dolore immenso, il dolore di un popolo intero. Parla dello sradicamento ineludibile di chi deve usare la lingua degli oppressori per esprimersi, anche quando questa espressione raggiunge livelli altissimi e anche quando gli oppressori francesi si manifestano come la più grande sciagura mai accaduta al popolo algerino. Parla di profondissimi legami con le persone che per la libertà hanno messo tutto il proprio corpo e non solo il proprio intelletto, a costo di perdere la vita.

Chinelo Okparanta, Sotto gli alberi di udala

Questo libro inizia con una carta geografica della Nigeria, e questo potrebbe essere sufficiente a metterlo vicino al mio cuore (perché mi piacciono molto le carte geografiche). Ritrovo il Biafra devastato e dilaniato dalla ferocia della guerra civile di Metà di un sole giallo, con un pesantissimo supplizio in più. La protagonista è costretta a vivere con crescente angoscia la propria omosessualità, perché in Nigeria è un peccato mortale che viene punito in modo sommario, anche con linciaggi. Ma nella seconda parte si riaccende la speranza. È la stessa Africa dove oggi vacilla un po’ il colonialismo europeo.

Beata Umubyeyi Mairesse, I tuoi figli ovunque dispersi

Anche questo libro è un racconto di sradicamento, che attraversa più generazioni. Tra Ruanda e Francia, tra nonna, madre, figlio, la protagonista trova un senso, anche linguistico, al proprio passato e al proprio futuro, nonostante il trauma del genocidio, della fuga dal genocidio e dello sradicamento che ne deriva. Bellissimo, straziante e lucido.

Gabriela Wiener, Sanguemisto

Anche questo libro è un racconto di sradicamento, che attraversa più generazioni (non ho sbagliato a fare copia e incolla). È un libro molto forte che si aggancia quasi chimicamente con letture accademiche che sto facendo in questo periodo, su archeologia e colonialismo (in Italia non esiste il postcolonialismo). Ma è anche un tripudio agrodolce di femminilità.


Inizio il 2024 leggendo L’incendio di Cecilia Sala e Tutta intera di Espérance Hakuzwimana.

by Stefano Costa at January 20, 2024 11:46 AM

January 18, 2024

Os traemos una presentación de la Infraestructura de Datos Espaciales (IDE) de Albacete, proyecto estratégico destinado a proporcionar un marco tecnológico y organizativo para la gestión, acceso y uso de la información geoespacial en el ámbito del municipio de Albacete. Este proyecto ha tenido como objetivo principal mejorar la toma de decisiones, impulsar el desarrollo urbano sostenible y fomentar la colaboración entre los diferentes actores involucrados en la planificación y gestión del territorio.

La ponencia presenta los trabajos principales y avances de la implantación de la IDE de Albacete. Durante el proyecto se ha llevado a cabo tanto la recopilación, integración y homogeneización de una amplia variedad de datos geoespaciales como el desarrollo de herramientas orientadas a ampliar la funcionalidad de la IDE y a fomentar la participación de los distintos departamentos municipales.

En cuanto a los avances logrados, se ha implementado una plataforma tecnológica robusta y escalable, con base tecnológica en la Suite gvSIG, que permite la gestión eficiente de la información geoespacial y su difusión a través de un conjunto de geoportales y servicios web interoperables. Además de los geoportales de uso interno,se ha publicado un visor cartográfico principal y un número creciente de geoportales temáticos (turismo, urbanismo, movilidad, etc.).

Además, se han desarrollado herramientas específicas que facilitan el acceso y uso de los datos geoespaciales por parte de los diferentes usuarios del Ayuntamiento de Albacete, destacando integraciones con otros sistemas informáticos como el gestor de expedientes SEDIPUALBA / SEGEX, el Catastro con acceso a datos protegidos o el Padrón. Integrada con la IDE desarrollada con gvSIG Online, también se cuenta con la app móvil gvSIG Mapps para la toma de datos en campo, tanto en modo online como offline, y un catálogo de metadatos basado en Geonetwork.

Por último, hay que reseñar que el proyecto también ha implicado un esfuerzo en formación y divulgación entre el personal técnico del Ayuntamiento de Albacete.

En conclusión, la implantación de la Infraestructura de Datos Espaciales de Albacete representa un paso significativo hacia una gestión territorial más eficiente y sostenible. Un proyecto que puede servir de referencia para otros municipios con necesidades similares.

by Alvaro at January 18, 2024 02:04 PM

January 17, 2024