Planet Georezo » Planet OSGeo

Un Planet est un site Web dynamique qui agrÃ¨ge le plus souvent sur une seule page, le contenu de notes, d'articles ou de billets publiÃ©s sur des blogs ou sites Web afin d'accentuer leur visibilitÃ© et de faire ressortir des contenus pertinents aux multiples formats (texte, audio, vidÃ©o, Podcast). C'est un agrÃ©gateur de flux RSS. Il s'apparente Ã un portail web.
Vous pouvez lire le billet sur le blog La Minute pour plus d'informations sur les RSS !

Feeds

8831 items (0 unread) in 53 feeds

Dans la presse

Du côté des éditeurs

Toile géomatique francophone

Géomatique anglophone

Blogs GeoRezo.net

Abonnez vous à cette page (RSS) !

Planet OSGeo

Skip to page: 1 2 3 ... 19

01 October 2022
22:22
Stefano Costa: IOSACal 0.6 released with new features for simulation and quantiles
sur Planet OSGeo
I’m happy to announce that IOSACal version 0.6 was released on October 1st, 2022.

IOSACal 0.6 brings new features for simulating radiocarbon dates and obtaining quantiles, added respectively by Hythem Sidky and Roger Creel, who both contributed to IOSACal for the first time. I want to thank both for their efforts to share improvements to the IOSACal source code by sticking to the code of conduct and contribution rules of the project.

The documentation at [https:]] has been updated substantially, and some pages are now generated directly from Jupyter notebooks. You can download those notebooks and quickly start working on your own research notebooks.

You can get this update as usual with pip install iosacal or by updating your requirements.txt to this version:
```
iosacal==0.6.0
```
IOSACal 0.6 brings several improvements to the development process, most notably continuous integration (CI) thanks to Codeberg CI. All pull requests are automatically run through iosacal’s own test suite (coverage is not yet complete but it is improving). The detailed list of all changes is at [https:]]

The demo web application was discontinued, and usage with MyBinder or Google Colab is now encouraged.

That’s it for now, development continues at [https:]] !

This article is also available via the new IOSACal updates newsletter!
17:50
Free and Open Source GIS Ramblings: Visualizing IOT time series with QGIS & MobilityDB
sur Planet OSGeo
Today’s post presents an experiment in modelling a common scenario in many IOT setups: time series of measurements at stationary sensors. The key idea I want to explore is to use MobilityDB’s temporal data types, in particular the tfloat_inst and tfloat_seq for instances and sequences of temporal float values, respectively.

For info on how to set up MobilityDB, please check my previous post.
Setting up our DB tables
As a toy example, let’s create two IOT devices (in table iot_devices) with three measurements each (in table iot_measurements) and join them to create the tfloat_seq (in table iot_joined):
```
CREATE TABLE iot_devices (
    id integer,
    geom geometry(Point, 4326)
);
INSERT INTO iot_devices (id, geom) VALUES
(1, ST_SetSRID(ST_MakePoint(1,1), 4326)),
(2, ST_SetSRID(ST_MakePoint(2,3), 4326));
CREATE TABLE iot_measurements (
    device_id integer,
    t timestamp,
    measurement float
);
INSERT INTO iot_measurements (device_id, t, measurement) VALUES
(1, '2022-10-01 12:00:00', 5.0),
(1, '2022-10-01 12:01:00', 6.0),
(1, '2022-10-01 12:02:00', 10.0),
(2, '2022-10-01 12:00:00', 9.0),
(2, '2022-10-01 12:01:00', 6.0),
(2, '2022-10-01 12:02:00', 1.5);
CREATE TABLE iot_joined AS
SELECT 
    dev.id, 
    dev.geom, 
    tfloat_seq(array_agg(
        tfloat_inst(m.measurement, m.t) ORDER BY t
    )) measurements
FROM iot_devices dev 
JOIN iot_measurements m
  ON dev.id = m.device_id
GROUP BY dev.id, dev.geom;
```
We can load the resulting layer in QGIS but QGIS won’t be happy about the measurements column because it does not recognize its data type:
Query layer with valueAtTimestamp
Instead, what we can do is create a query layer that fetches the measurement value at a specific timestamp:
```
SELECT id, geom, 
    valueAtTimestamp(measurements, '2022-10-01 12:02:00') 
FROM iot_joined
```
Which gives us a layer that QGIS is happy with:
Time for TemporalController
Now the tricky question is: how can we wire our query layer to the Temporal Controller so that we can control the timestamp and animate the layer?

I don’t have a GUI solution yet but here’s a way to do it with PyQGIS: whenever the Temporal Controller signal updateTemporalRange is emitted, our update_query_layer function gets the current time frame start time and replaces the datetime in the query layer’s data source with the current time:
```
l = iface.activeLayer()
tc = iface.mapCanvas().temporalController()
def update_query_layer():
    tct = tc.dateTimeRangeForFrameNumber(tc.currentFrameNumber()).begin().toPyDateTime()
    s = l.source()
    new = re.sub(r"(\d{4})-(\d{2})-(\d{2}) (\d{2}):(\d{2}):(\d{2})", str(tct), s)
    l.setDataSource(new, l.sourceName(), l.dataProvider().name())
tc.updateTemporalRange.connect(update_query_layer)
```
Future experiments will have to show how this approach performs on lager datasets but it’s exciting to see how MobilityDB’s temporal types may be visualized in QGIS without having to create tables/views that join a geometry to each and every individual measurement.
30 September 2022
18:24
Free and Open Source GIS Ramblings: Detecting close encounters using MobilityDB 1.0
sur Planet OSGeo
It’s been a while since we last talked about MobilityDB in 2019 and 2020. Since then, the project has come a long way. It joined OSGeo as a community project and formed a first PSC, including the project founders Mahmoud Sakr and Esteban Zimányi as well as Vicky Vergara (of pgRouting fame) and yours truly.

This post is a quick teaser tutorial from zero to computing closest points of approach (CPAs) between trajectories using MobilityDB.
Setting up MobilityDB with Docker
The easiest way to get started with MobilityDB is to use the ready-made Docker container provided by the project. I’m using Docker and WSL (Windows Subsystem Linux on Windows 10) here. Installing WLS/Docker is out of scope of this post. Please refer to the official documentation for your operating system.

Once Docker is ready, we can pull the official container and fire it up:
```
docker pull mobilitydb/mobilitydb
docker volume create mobilitydb_data
docker run --name "mobilitydb" -d -p 25432:5432 -v mobilitydb_data:/var/lib/postgresql mobilitydb/mobilitydb
psql -h localhost -p 25432 -d mobilitydb -U docker
```
Currently, the container provides PostGIS 3.2 and MobilityDB 1.0:
Loading movement data into MobilityDB
Once the container is running, we can already connect to it from QGIS. This is my preferred way to load data into MobilityDB because we can simply drag-and-drop any timestamped point layer into the database:

For this post, I’m using an AIS data sample in the region of Gothenburg, Sweden.

After loading this data into a new table called ais, it is necessary to remove duplicate and convert timestamps:
```
CREATE TABLE AISInputFiltered AS
SELECT DISTINCT ON("MMSI","Timestamp") *
FROM ais;

ALTER TABLE AISInputFiltered ADD COLUMN t timestamp;
UPDATE AISInputFiltered SET t = "Timestamp"::timestamp;
```
Afterwards, we can create the MobilityDB trajectories:
```
CREATE TABLE Ships AS
SELECT "MMSI" mmsi,
tgeompoint_seq(array_agg(tgeompoint_inst(Geom, t) ORDER BY t)) AS Trip,
tfloat_seq(array_agg(tfloat_inst("SOG", t) ORDER BY t) FILTER (WHERE "SOG" IS NOT NULL) ) AS SOG,
tfloat_seq(array_agg(tfloat_inst("COG", t) ORDER BY t) FILTER (WHERE "COG" IS NOT NULL) ) AS COG
FROM AISInputFiltered
GROUP BY "MMSI";

ALTER TABLE Ships ADD COLUMN Traj geometry;
UPDATE Ships SET Traj = trajectory(Trip);
```
Once this is done, we can load the resulting Ships layer and the trajectories will be loaded as lines:
Computing closest points of approach
To compute the closest point of approach between two moving objects, MobilityDB provides a shortestLine function. To be correct, this function computes the line connecting the nearest approach point between the two tgeompoint_seq. In addition, we can use the time-weighted average function twavg to compute representative average movement speeds and eliminate stationary or very slowly moving objects:
```
SELECT S1.MMSI mmsi1, S2.MMSI mmsi2, 
       shortestLine(S1.trip, S2.trip) Approach,
       ST_Length(shortestLine(S1.trip, S2.trip)) distance
FROM Ships S1, Ships S2
WHERE S1.MMSI > S2.MMSI AND
twavg(S1.SOG) > 1 AND twavg(S2.SOG) > 1 AND
dwithin(S1.trip, S2.trip, 0.003)
```
In the QGIS Browser panel, we can right-click the MobilityDB connection to bring up an SQL input using Execute SQL:

The resulting query layer shows where moving objects get close to each other:

To better see what’s going on, we’ll look at individual CPAs:
Having a closer look with the Temporal Controller
Since our filtered AIS layer has proper timestamps, we can animate it using the Temporal Controller. This enables us to replay the movement and see what was going on in a certain time frame.

I let the animation run and stopped it once I spotted a close encounter. Looking at the AIS points and the shortest line, we can see that MobilityDB computed the CPAs along the trajectories:

A more targeted way to investigate a specific CPA is to use the Temporal Controllers’ fixed temporal range mode to jump to a specific time frame. This is helpful if we already know the time frame we are interested in. For the CPA use case, this means that we can look up the timestamp of a nearby AIS position and set up the Temporal Controller accordingly:
More
I hope you enjoyed this quick dive into MobilityDB. For more details, including talks by the project founders, check out the project website.

This post is part of a series. Read more about movement data in GIS.

16:42

QGIS Blog: Plugin Update September 2022

sur Planet OSGeo

The QGIS plugin repository currently lists 1710 plugins and the list keeps on growing. September has been busy with 16 new plugins. It can be challenging to stay up to date.

Our monthly plugin update is meant to provide you a quick overview of the newest plugins. 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.

Site Schedule Optimization

Finds an optimal multi-day schedule for traveling to a set of locations.

Sentinel-5p data explorer

Sentinel-5p data explorer manage NC files from satellite “Sentinel-5p”.

CityTimer

Evaluate the distance from the 15min city of a context

Drone Path

This plugin prepares a drone flight path based on input polygon and drone camera parameters. This plugin gives a Fly Litchi compatible csv file with way points for the drone path.

Previsioni

This plugin connect to Previsioni API.

BecaGIS

BecaGIS GeoProcessing, Field Calculation Tools and Expressions

SenseRemote Detection

AI detection algorithms for remote sensing images.

Geotuileur

Plugin associated with the IGN France service of the same name: Geotuileur.

Groundwater Buffer Raster

Expands and interpolates edge values of Water Surface Elevation (WSE) rasters to produce groundwater (GW) buffer rasters

KoALA_Nx

KoALA-Nx supports optimal network analysis in various network environments. Users can apply the tool in all network environments, such as roads, railroads, and pedestrians. KoALA-Nx provides two functions: distance-based network analysis and time-based network analysis

Data Range Filter Legend Widget

Filter layer elements from the legend, using sliders that cover the range of each numeric field.

CO2_Sequestration

This plugin predicts the tree CO2 Sequestration by simply knowing the tree Diameter at Breast Height (DBH) and height of the tree.

PEC_Avalia

Realiza a avaliação da acurácia posicional em produtos e dados cartográficos, a partir de normas e padrões brasileiros

SecQuery

Render geodesic buffers with 4-32 sectors and query the point data in them.

Nearest with greater value

Get name (or ID) of and distance to the nearest feature with greater value in a certain field of a point layer. Returns point layer with added attributes and a line layer with connecting lines.

ODKConnector

Plugin to connect to the ODK (Open Data Kit) for data retrieval.

29 September 2022
22:13
Fernando Quadro: Esqueci a senha do GeoServer, e agora?
sur Planet OSGeo
Se você tiver acesso de gravação ao diretório de dados e não tiver definido uma senha mestra, poderá alterar a senha de administrador editando o seguinte arquivo:
```
security/usergroup/default/users.xml
```
Dentro desse arquivo você deve alterar seguinte linha:
```
<user enabled="true" name= "admin"
password="digest1:D9miXH/hVgfxZJscMbfXtbtliG0WOxhLfsznyWfG38X2pda2JOSV4POi55PQI4tw"/>
```
Para:
```
<user enabled="true" name="admin" password="plain:PASSWORD"/>
```
Onde PASSWORD é sua nova senha temporária em texto simples.

Como armazenar senhas em texto simples é uma prática ruim, você deve fazer login e alterar a senha do administrador novamente para garantir que ela seja armazenada como um hash criptografado, não como texto simples. Para isso vá até o menu Segurança/
Usuários,Grupos,Funções/Usuários/Grupos/ e clique em admin, preencha uma nova senha (duas vezes) e pressione Salvar.

Verifique novamente o arquivo security/usergroup/default/users.xml para certificar-se de que a senha agora está armazenado corretamente (não texto simples).
11:00
CARTO Blog: Data warehouses vs. GPU accelerated analytics for geospatial analysis
sur Planet OSGeo

Analyzing and visualizing large amounts of geospatial data has sometimes seemed like a pipe dream to many analysts involved in GIS or geospatial analysis. Limitations on fi...
10:12
gvSIG Team: 18as Jornadas Internacionales gvSIG: Inscripciones y ampliación de plazo de envío de propuestas
sur Planet OSGeo

Ya está abierto el periodo de inscripción de las 18as Jornadas Internacionales gvSIG, que se celebrarán del 30 de noviembre al 2 de diciembre de 2022 junto a las Jornadas GeoLIBERO 2022 en la Escuela Técnica Superior de Ingeniería Geodésica, Cartográfica y Topográfica (Universitat Politècnica de València, España).

La inscripción es totalmente gratuita (con aforo limitado) y se ha de realizar a través del formulario existente en la página web de las Jornadas.

En unas semanas se publicará el programa con todas las ponencias y talleres previstos, tanto para usuarios como para desarrolladores, con toda la información sobre cómo inscribirse en ellos.

Por otro lado, os informamos que se ha ampliado el plazo de envío de resúmenes, siendo la nueva fecha límite el 14 de octubre. Las normas para el envío de comunicaciones podéis encontrarlas en la web de las jornadas.

¡Esperamos vuestra participación!
28 September 2022
16:25
W3C Maps for HTML Community Group: Why Spatial Is Very Special
sur Planet OSGeo
Web Semantics¹
TL;DR: “machines” use the HTML structure of Web pages to enable the coherent transmission of the document content’s meaning to the user. Maps and locations are not currently reflected in HTML’s structure, nor browser rendering engines, and so a) their meaning is proprietary to Web sites, concocted as they are, from ever-more-opaque code, and b) Web-based assistive technology, aka “machines”, are unable to follow the markup that might convey locations to users, and so the machines need hints, which are typically omitted or badly implemented. Maps and location are important for everyone, but especially important for non-visual users who must rely on textual location descriptions and search. Maps and location semantics may also be important on the Web for future applications such as the metaverse, digital twins, smart cities, the Web of Things, spatial data infrastructure, indoor mapping and autonomous vehicles, to name a few. To sustainably and fairly enable these applications on the Web, maps and location should be integrated in the browser engines, with standardised HTML semantics.
1. The usage of the word “semantics” in this document is distinct from that of its usage in the Semantic Web. The latter is not discussed here.
2. Understanding semantics – Tink
HTML semantics are for a11y²
Web pages contain a mix of structure (HTML markup) and content (text, images, media, etc). Web pages are structured using HTML elements so that the “machines” that process them (browsers, screen readers, search engine crawlers, etc) understand what the parts are and can render or process them accordingly. Machines process HTML element structure, so that humans can consume and understand the meaning of the HTML contents. The standardised meaning accorded HTML elements (structure) is often described as HTML semantics, which refers to how that markup is specified and how it is intended to be processed. The contents of an HTML page also have meaning (for humans, mostly), and it is the raison d’être of browsers and assistive technology to facilitate the transmission of the images’, graphics’ and text’s meaning to the user, through graphic or other rendering techniques.
Web maps model physical space, just like words model conceptual space
In an analogous way that humans use language and text to convey ideas, Web maps describe the physical world with coordinate reference systems (CRS) and math (of course). That is, maps may reflect the real, physical world. The relation between this model and the real world can easily be experienced, right now, by anyone with a smartphone, by viewing your device’s location, rendered on a web map, as a symbol:
Map showing user location
An example of well-known CRS coordinates are provided by the WGS 84³ coordinates reported for your device by its Global Positioning System (GPS) sensor. The geospatial standards community has spent decades of effort, and billions of dollars defining and standardising the details of spatial CRS, to enable geographic information to be processed and rendered by machines, for use by humans. These coordinates represent the most fundamental map semantics. The relationship between the multi-billion dollar GPS CRS system and the map on your phone is today provided exclusively by the JavaScript on the page, not by the browser engine. In other words, the browser doesn’t ‘understand’ the map, it leaves that up to each site, with a very few, very large sites dominating and brokering that space.

3. About This Standard
Pokémon Go Map
Extended and augmented reality (XR, AR) can also be models of reality, collectively known as the Immersive Web. The (potential) commonality between the Immersive Web and Web maps is that, to some degree, they each represent physical and virtual reality integrated together, sometimes relying on user device sensors to “place” the user into the virtual representation, as shown by both our Web map examples above. The value of placing the user into a virtual representation of reality, be it a 2D map or 3D representation, lies in the accessibility, privacy and performance delivered by HTML semantics, and rendered by browsers for the benefit of the user. Such value can only be realised only if all Web sites have a simple (declarative), open (standard) and fair way to represent physical reality that does not depend for existence on procedural browser extension (JavaScript, WebGL, WASM etc.).
Web maps require JavaScript When everyone is responsible (for map accessibility), no one is responsible
A key argument against extending or even relying on JavaScript to deliver map and location semantics to the user (even if a non-DOM standard library did exist) is that providing accessibility for maps and location content for the Web then becomes the responsibility of individual Web sites and library developers. When everyone is responsible for creating accessible content, when that content is or must be created with JavaScript, canvas, or WebGL, or WASM, inaccessible content is often the result. Other essential characteristics of the Web besides accessibility are also lost or harmed when JavaScript is used as a substitute for HTML semantics, including: performance, generality, internationalisation, and crawl- and search-ability. In short, while JavaScript (and its sidekick JSON) is a fantastic language to progressively enhance the Web experience, it should not be looked to as a focus for Web standardisation of mapping.
Third-party Web map providers What is “special” about spatial?
At our recent Maps for HTML community meeting in September 2022, we had the beginnings of a really interesting, and I believe important discussion, about the intimate relationship between accessibility, map semantics, and rendering. Boaz Sender, from Bocoup, showed us an example of a prototype browser intervention that they have been researching, using a dynamic Leaflet-powered, OpenStreetMap-backed map of Denver, Colorado. The “intervention” part was where the whole map, and especially the set of features highlighted on the map was rendered on request, not graphically, but in an alternate “view” representing the map as a simple text list. This seems to be a prototype implementation of a really important idea, and one that has come up before in our community, and it is an idea that is gaining traction in the mobile app world (yes, the Web Platform community should pay attention – mobile apps surpass the Web by far in location-based usage).
A Leaflet.js Web map of Denver
Ed Parsons raised what I consider to be a profound question about the Denver map example: What is it about the map, besides being visually obvious to someone familiar with United States geography, that tells us that it’s a map of Denver? Even the text list representation of the map might not indicate that these are features from Denver, and the map itself even might not be labelled as such, despite the importance of such labelling. Still, there is something significant about the meaning of that map that is instantly obvious to users of its visual rendering that is clearly missing from the current Web.
Globally shared coordinate semantics, defined by a Web standard
What’s missing is the ability to represent Denver in a way that isn’t ephemeral, nor accessible only to sighted users. What’s missing is the ability to represent and render the coordinate space of the Earth and things on Earth in a standard way that is shared by everyone. What’s missing is maps and locations in HTML, implemented and supported by Web browser engines, for everyone!
A tree has fallen in a forest. Did it make a sound?
In my next post, I’ll explore what we’re doing in the Maps for HTML Community Group to change the status quo. See you then, I hope!
26 September 2022
8:00
Lutra consulting: Crowdfunding: Point cloud processing in QGIS and 3D data enhancements
sur Planet OSGeo

We are pleased to announce a new crowdfunding campaign to introduce point cloud processing to QGIS! Similar to the previous crowdfunding campaigns, we have teamed up with North Road and Hobu.

Point cloud data and raster shading in QGIS.

In the last couple of years, we added point cloud data to QGIS, developed profile tool, improved 3D map navigation and many more features related to 3D data.

The new processing tools will allow you to create terrain/contours from your point cloud data, handle and manage large datasets and several other processing algorithms. In addition, we intend to allow you to embed profiles in your print layouts, export to other formats (e.g. DXF, CSV) and more improvements to the elevation profile tool. For more details see the crowdfunding page.

To pledge to this crowdfunding campaign, simply fill in the form. We will start the work as soon as the target fund is raised.
21 September 2022
3:59
Sean Gillies: Superior tech notes
sur Planet OSGeo

One of the cool things about blogging is that there aren't a lot of rules. I had some thoughts about racing at Superior that I wasn't able to weave into my previous post, so I'm just making a new post about technical aspects of the race. What I wore, what I carried, and what I ate.

I brought rain gear and extra clothing to Minnesota, and used it on Friday. But when the forecasts converged on dry and mild for Saturday, I left that gear out of my pack and drop bags. I sent a pair of shoes (Evo Speedgoats) and socks to the Cramer Road aid station at 27 miles and a spare headlamp to the Sawbill aid station at 40 miles. No other non-consumable items. I didn't use the spare Speedgoats. My feet were still feeling okay at 27 miles. In hindsight, it would have been better to have sent completely different shoes to Sawbill. A pair with a different fit, like my Nikes, would have been lovely to change into at 40 miles.

I wore the same clothing all day. Smartwool socks. A very light tech top from Patagonia. Venerable capilene boxer briefs from REI and slightly ratty, but lucky, Vuori Banks shorts. I trust these to be non-chaffing at home and they came through for me again. My Gnar Runners Boco tech trucker was on my head until sundown, after which I intermittently wore a capilene beanie. I wore my nylon windbreaker (Patagonia Houdini) for the last seven miles. With clear skies, the air cooled quickly, but never got very cold. I left my wool gloves in my pack. I wore almost everything I packed and didn't need anything more. I'm going to have to retire some of these items soon. Plastic clothing lasts a long time, but not forever.

I carried everything in my trusty Ultimate Directions Mountain Vest (4.0). It weighs almost nothing, is breathable, and fits well whether lightly or heavily loaded. I brought a small first aid kit, but didn't use it. Nor did I use my sunglasses or small stick of sunscreen. For hydration, I carried three 16-ounce soft bottles. One was mostly a spare. It was never very warm, and I never carried more than two full bottles at a time between aid stations.

I brought light hiking poles to Minnesota, the ones I used at the Never Summer 100k last year. They're very helpful on muddy trails and on technical descents in the dark. I left them in my room at the lodge on race day and didn't regret it. I would have used them in the last hour of the race if I'd been carrying them, but they wouldn't have improved my time or saved my feet.

Shoes... I do think that my Speedgoats weren't adequately broken in. The heel and toe areas were a bit stiff. I did appreciate the famous cushion and traction. They're a good choice for the Superior Hiking Trail. It's a super rugged trail, so you need some combination of cushion, armor, or dancer's feet. I ran for miles with a guy who was wearing the Speedgoat 5, which I have worn for up to 20 miles, but no further, and he loved them. I might see about switching over.

Fuel is the last technical detail to cover. I drank a lot of Tailwind solution. 400 calories worth at six of the 7 aid stations. I stashed pre-measured amounts in my drop bags to pick up along the way. I sucked down 4 packets of GU and ate three Stinger waffles and one bag of Stinger chews. I drank 8-10 ounces of Coke, one of my go-to calorie sources, at every aid station. I was able to eat plenty of solid food all day long. From pancakes and sausage in the morning, to mashed potatoes and chicken noodle soup in the evening. Mid-day I got tired of aid station food and that's when I went for the chews and gels. I did a much better job fueling than I did at last year's Never Summer, where I bonked badly in the last 10 miles.

What about crewing? I didn't have a planned crew. My friend David Bitner, a devoted Superior runner and pacer, met me at mile 27 to pump me up and help me get set for the second half. Outside of that, I found my own groups as I went. 50 miles, in my experience, is not so long that I need help. I would love to have some crew help on a 100 mile race and a pacer to help me flow quickly through aid stations.

That's all the technical notes for the race. I went into it with a B fitness level, extra pounds, a little uncertainty about my heart, but with experience at this race distance to lean on. I flunked my shoe choice, but did everything else right, enjoyed tons of support, and had a great time.
20 September 2022
14:51
GeoSolutions: GeoNode Release 4 is out
sur Planet OSGeo

You must be logged into the site to view this content.
7:48
Marco Bernasocchi: How we build QField for many platforms – A look behind the curtain
sur Planet OSGeo
In the past year, the build system behind QField has been ported to vcpkg, a modern C++ dependency management system. It has been a great success for QField and considerably helped to streamline efforts, improve the development experience and to guarantee an outstanding stability of the application. In this blog post we will look at the history of building QGIS based applications for mobile systems and how it has become what it is today.

When Marco Bernasocchi (CEO of OPENGIS.ch and chair of QGIS.org) started working on QGIS for Android in Google Summer of Code a decade ago, the main job was to also build all QGIS dependencies for Android. This includes well-known libraries like proj and gdal and less-known ones like libxml2 or iconv. Each of them has its particularities and specific build flags. Working on this appears to be an endless iterative trial-and-error journey where you hope each day that eventually you will see the QGIS splash screen on your Android phone while all you see are endless lines of code and compiler errors.

As we know nowadays QGIS for Android has eventually seen the sunlight and its achievements are still the base for QGIS-based mobile apps like QField.

Sometime later we decided to modernize the build infrastructure into OSGeo4A a set of scripts where each dependency was built with a “recipe”. Modularized this way, it was easier to maintain, and general build code common for all libraries could be isolated. It was good enough to help drive QField for a couple of years, and a copy of it is still in use as the base for nowadays QGIS builds for macOS.

When we decided to make QField also available on other platforms like iOS, Windows and macOS we quickly realized that duplicating build chains scales really bad and maintaining this is an immense effort we wanted to avoid. There are a couple of existing C++ dependency management systems, none of which convinced us ultimately. Lucky for us a mail on the QGIS mailing list mentioned a new one called vcpkg which looked very promising.

A couple of days later we had a build for Windows and later in the same year for macOS. With many dependencies already available in modern versions. Cheers.

What’s left to do than just enable it for Android, and all our problems are suddenly solved? Alas, it’s not so easy. Cross-compiling is always a bit trickier. And so we started another journey to improve the situation. After a while, we had a working build chain based on vcpkg for Android in our R&D labs. Interestingly, this added a couple of features just because the community around vcpkg had already added them. For example using COG-based raster data via HTTP was suddenly working (for the record: thanks to the availability of curl which we never took care of adding ourselves in OSGeo4A).

Soon after we also wanted to try building for iOS with vcpkg, which after a few attempts also was successful, and even managed to resolve some weird crashes and other issues we had experienced with the old buildchain.

The main benefit was that we could upgrade the QGIS base libraries in one single place for every platform, in an isolated branch without playing the Jenga game on each upgrade.

The only unfinished business we still had was that support for iOS and Android was still available only in our own vcpkg fork.

So the last few weeks and months we have been working closely with upstream to bring building for Android and iOS up to the same level as desktop platforms. The relevant parts are now in a clean state.

Advantages of this approach:
- • Mutualized efforts on all the base libraries, also with programmers outside the geoverse
- • A vibrant community that ensures a noticeably fast upgrade of libraries
- • A clean dependency management system
- • A consistent set of dependency versions (gdal, geos, libpq, …) across all platforms
- • A clean caching system that will only recompile reverse dependencies on updates
- • We can upgrade a dependency in an isolated branch and only release it when it works on all platforms
- • We can optimize the code for a given set of dependency versions and if a bug is fixed in a certain dependency version, we are sure we can ship this fix on all platforms promptly
- • We maintain the QField source code as well as dependency versions in a single repository, what makes development more streamlined
Big thanks go to Alexander Neumann and Kai Pastor who both stand out for doing things the right and future-proof way.

As always, things come at a price, there was a steep learning curve involved, and some edge cases require attention. However, we are thrilled by the simplification this has brought us.

If you are maintaining a customized fork of QField, it is now a good time to start upgrading to vcpkg, since OSGeo4A has been archived and will no longer be maintained. The developer documentation of QField has been updated with relevant instructions.

If you have time to test the new build system, we will be happy to read about your experiences with it.
19 September 2022
11:00
CARTO Blog: Databricks support for H3 in collaboration with CARTO
sur Planet OSGeo

Over the past few months we have been working with Databricks to add built-in support for H3, and this added functionality was released recently. Native support for H3 mean...
16 September 2022
11:14
gvSIG Team: Geoportal del Reino de Redonda
sur Planet OSGeo
Hace unos días falleció Javier Marías, considerado uno de los mejores escritores que ha dado la literatura de finales del siglo XX y principios del siglo XXI y, sin lugar a dudas, un monarca ejemplar. Precisamente este verano, leyendo sobre reinos ficticios, se me ocurrió que en algún rato libre (de esos que el proyecto gvSIG deja pocos), debería crear el geoportal del Reino de Redonda.

Un reino de apenas tres kilómetros cuadrados, una pequeña isla que al contrario de lo que nos diría la imaginación no tiene ni playas ni palmeras. Sin embargo, esta aparentemente aburrida roca sita en el mar Caribe alberga una maravillosa historia para los amantes de la literatura.

Fue Matthew Dowdy Shiell el que allá por 1865, cuando nació su primer hijo, compró la isla y quiso convertirla en un reino ficticio que no fuera ni más, ni menos, que el citado islote. Para ello, parece ser, solicitó a la reina Victoria el título de reino, que le fue concedido con una única condición: que nunca supusiera un peligro para los intereses de los británicos.

Matthew Dowdy Shiell traspasó el reinado a su hijo, el escritor Matthew Phipps Shiel (sí, con una “l” menos que el padre), conocido en el mundo de la literatura como M.P. Shiel y en el Reino de Redonda como Felipe I. Además de ser un escritor bastante prolifico cultivando el género fantástico y de ciencia ficción, reinó desde 1880 a 1947, designando de paso a los primeros duques del reino, honor que recayó en personajes como H.G. Wells, Dylan Thomas o Henry Miller.

Felipe I abdicó en el poeta Terence Ian Fytton Armstrong, conocido en el mundo de la literatura como John Gawsworth y tomando el nombre de Juan I para su papel de monarca. Con la típica vida bohemia de un escritor maldito, regada por el alcohol y los problemas económicos, llegó a vender títulos nobiliarios por unas pocas libras. Con 58 años murió a consecuencia de una úlcera. Su reinado tuvo lugar desde 1947 a 1970.

Su sucesor fue el editor y también escritor John Wynne-Tyson, que para eso de ser rey se decidió por el nombre de Juan II. Su reinado duró hasta 1997, año en que decidió que la persona más adecuada para ocupar el trono era un escritor español, Javier Marías.

Javier Marías, republicano confeso, reinó con el nombre de Rey Xavier hasta su reciente fallecimiento, el pasado 11 de septiembre de 2022. Su último rey ha sido, sin duda, el que ha llevado a Redonda a sus cotas más altas de popularidad, designó a no pocos artistas e intelectuales como miembros de la corte, creó un sello propio de literatura fantástica que lleva el nombre del reino, difundió su existencia en algunos de sus escritos y creó el premio literario del Reino de Redonda.

Como todo reino que se precie ha habido disputas por el trono y ahí tenemos a Arthur John Roberts, William Leonard Gates, Bob Williamson y Michael Howorth. Y, por si os lo preguntáis, al contrario que en el caso de la monarquía inglesa… todavía no se ha proclamado el sucesor del Rey Xavier.

Hecha esta breve cronología del Reino de Redonda, os comparto los pasos que he realizado para crear el geoportal con gvSIG Online, ya sabéis, la solución en software libre para implantar Infraestructuras de Datos Espaciales. Todo el proceso me ha llevado poco más de una hora y para ello he usado un gvSIG Online que tenemos en la Asociación gvSIG para “jugar a nuestras cosas”; ni tan siquiera es la penúltima versión del software, pero ya sabéis en casa de herrero cuchillo de palo.
- Lo primero que hice anoche fue descargar cartografía de la zona del proyecto OpenStreetMap y, a partir de ahí, seleccionar las geometrías correspondientes a la Isla de Redonda para generar una nueva capa.
- Esa capa la repliqué para generar capas que mostraran los dominios de cada uno de los reinados y que, básicamente, han sido siempre los mismos. Un reino que ha sabido defender sus fronteras y, al mismo tiempo, tampoco ha tenido la necesidad de ampliarlas.
- Usando la herramienta de georreferenciación y posteriormente la de asignar proyección de gvSIG Desktop, ubiqué uno de los pocos mapas manuscritos que hay del Reino de Redonda, disponible en la web de The Redondan Foundation. Al ser un mapa dibujado no es sencillo hacerlo coincidir con sus coordenadas reales, pero creo que ha quedado medianamente bien.
- También con gvSIG Desktop generé una nueva capa de puntos para dibujar los principales puntos de interés de la isla.
- Ya en gvSIG Online publiqué todas esas capas y generé un geoportal que las contuviera.
Claro, se podría adornar y completar mucho más, pero como pequeño homenaje creo que es suficiente. No sé si esto me convierte en cartógrafo oficial del Reino de Redonda, pero al menos espero que os haya despertado la curiosidad.

El enlace a la Infraestructura de Datos Espaciales de Redonda lo tenéis aquí:

[https:]]
15 September 2022
11:16
OTB Team: OTB release 8.1.0
sur Planet OSGeo

Dear OTB community, We are happy to announce that OTB version 8.1.0 has been released! Ready to use binary packages are available on the package page of the website: OTB-8.1.0-Darwin64.run (Mac OS) OTB-8.1.0-Linux64.run (Linux) OTB-8.1.0-Win64.zip (Windows 64 bits) You can also use the official docker image It is also possible to checkout the branch with git: git clone [https:] […]
2:00
GeoServer Team: GeoServer 2.20.6 Released
sur Planet OSGeo
We are happy to announce GeoServer 2.20.6 release is available with downloads (bin, war, windows), along with docs and extensions.

This is the last planned maintenance release for the 2.20.x series, please consider upgrading to the 2.21.x series. This release was made in conjunction with GeoTools 26.6 and GeoWebCache 1.20.4.
Improvements and Fixes
- It’s now possible to use the REST API to reset caches for a single store or a single layer.
- GeoFence role filtering was improved.
- OSHI was updated to allow gathering OS statistics on Apple M2 as well.
- Assorted small improvements to the status page.
- An infinite recursion in GWC transparent integration with WMS was spotted and fixed (affected vector tiles and layers with a meta-tiling factor of 1, when the “TILED” parameter was turned off).
- The GWC module was split so that its REST API can be excluded (for completely headless installs).
For the full list of fixes and improvements, see 2.20.6 release notes.
About GeoServer 2.20
Additional information on GeoServer 2.20 series:
Release notes: (2.20.5 | 2.20.4 | 2.20.3 | 2.20.2 | 2.20.1 | 2.20.0 | 2.20-RC )
14 September 2022
15:48
GeoTools Team: GeoTools 26.6 released
sur Planet OSGeo

The GeoTools team is pleased to share the availability GeoTools 26.6 : geotools-26.6-bin.zip geotools-26.6-doc.zip geotools-26.6-userguide.zip geotools-26.6-project.zip This release is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.20.6Fixes and improvementsBugGEOT-7186 SRID of geometries in columns w/o SRID constraint not detected properlyGEOT-7182
13 September 2022
17:38
Sean Gillies: Superior 50
sur Planet OSGeo

Last weekend I traveled to Minnesota's North Shore to run the Superior 50: 52 miles through the North Shore Highlands and Sawtooth Mountains on the Superior Hiking Trail. On the Thursday before the race I flew into Duluth and drove a rental car 90 miles up Highway 61 to a lodge at the Lutsen Mountains Resort, the finish line for the event. Friday I met David Bitner and his partner Marin at Tettegouche State Park for lunch and some easy hiking on the cliffs next to Lake Superior. Marin would be running the Moose Marathon (the last 26.2 miles of the 50 and 100 mile course) on Saturday and Bitner, a 100 mile finisher in 2019, would be pacing a 100 mile runner overnight. After a few hours with them, I drove north again to Grand Marais to wander around and find a pre-race dinner, and then back to the lodge to sleep before Saturday's early start.

Finland, MN, 5:00 a.m.

The 50 mile race began at 5:15 a.m. in Finland, Minnesota. A school bus took me from the finish to the start, leaving the resort at 4:15. Friday's clouds and rain were gone and the 50 mile race kicked off in calm and cool conditions under a full moon.

Somewhere on the Superior Hiking Trail.

The Superior Hiking Trail, or SHT, is wild, rugged, and challenging. I estimate that a quarter of the 50 mile course was fairly runnable. The rest was steep, or overgrown, or root-bound, or all of the above. You have to watch your feet, closely. On the other hand, I didn't need sunscreen, because we were traveling under the canopy of the boreal forest, with only small breaks at river and road crossings and rocky summits.

My plan was to take it easy in the first third of the course and, if I felt good, pick up the pace in the second third and try to sustain it through the final 17 miles. I settled into the tail end of the pack and stayed there until just before the Crosby-Manitou aid station (mile 12). During this part of the race I was briefly in a small train with Courtney Dauwalter (two time UTMB winner and winner of this year's Hardrock 100) and her mom, which was fun. They say never meet your heroes, but the Dauwalters were friendly and gracious. At the aid station I got a small cup of coffee, a big pancake and a sausage patty, and really began to enjoy the race.

Feeling good at the Cramer Road aid station, 27 miles in. Photo by David Bitner.

I felt great at 17 miles. My heart was behaving properly. My legs felt good. The trail conditions, considering Friday's rain, and weather were much better than I'd expected. I found some good company and longer stretches of runnable trail at this point did my fastest running of the day all the way into the Sugarloaf aid station at mile 21. I kept going steadily, passing two packs of runners on the way to the Cramer Road aid station.

My favorite place on the trail was the Temperance River Gorge. The river's name is, according to Bitner, a pun: there is no sand bar where it reaches Lake Superior. I took a bunch of photos of swimming holes just past the race's Temperance aid station. Not much further downstream the gorge narrows and deepens dramatically. I didn't take any photos there, but you can easily find them online. It's a real wonder of nature.

Temperance River Gorge, looking downstream. 34 miles.

Temperance River Gorge, looking upstream.

In hindsight, I might have neglected to eat enough after Cramer Road. I was feeling sluggish on the 1,200 foot climb up from the Temperance River to Carlton Peak. My ambitions of finishing before the sun went down were starting to look unrealistic. The trail near the summit was steep and rocky, not unlike the approaches to Arthur's Rock or Horsetooth. I saw Columbines and raspberries (flowers and fruit long gone), which also reminded me of home.

Carlton Peak, 38 miles.

Near the Sawbill-Britton aid station I began to catch up to slower 100 mile runners. Some of them were suffering. Some were perfectly executing their plans to beat all the aid station cut-off times and finish in just under 38 hours.

Around mile 40, my feet began to literally fall apart. I'm not sure whether my shoes (Speedgoat 4s with ~25 miles of wear) were inadequately broken in or I hadn't toughened up my feet enough in training. I only ran 20 miles once this year before Superior, whereas I ran 20, 25, and 30 miles before Quad Rock last year. My heels and toes blistered, and in trying to spare them on downhills, I absorbed more force in my quads than I otherwise would. The last 7 miles were a slow, painful slog, much of it well after dark. All the people I passed between miles 21 and 40 caught up to me and left me behind. Going uphill felt better than going downhill. But I finished! Good company helped. I ran the last 3 miles with a woman from Littleton, Colorado. We'd run some of the first few pre-dawn miles together and had some laughs about the rest of the day.

My official time: 15:36:21. This was an extremely well-run event and I can see why people keep coming back for more. Thank you, Superior volunteers and friendly runners. Thank you, Bitner and Marin, for lunch and crewing at the 27 mile mark. My biggest thanks are to my family, for putting up with my obsession and letting me off the hook for chores so I can sleep in during blocks of high training volume. I couldn't have finished without your support.

I just now found a link to the race director's recap in my inbox. It is here.
11:00
CARTO Blog: CARTO Driving Sustainability Impact Worldwide on Google Cloud
sur Planet OSGeo

When CARTO was founded in 2012, the main areas of focus were conservation and biodiversity projects. Fast forward exactly 10 years and CARTO is proud to be one of the leadi...
10 September 2022
2:00
PostGIS Development: PostGIS 3.3.1
sur Planet OSGeo

The PostGIS Team is pleased to release PostGIS 3.3.1.

This is a bug fix release to address an issue compiling against PostgreSQL 15 Beta 4.

Best served with PostgreSQL 15 Beta 4.
09 September 2022
19:56
Jackie Ng: MapGuide dev diary: It is done!
sur Planet OSGeo
In the previous installment, we had gotten a test MapGuide installation with bundled PHP 8.1 up and running, and we were able to successfully produce a PHP error when hitting the Site Administrator.
This PHP error referenced previously was a milestone because it meant that our PHP 8.1 setup (FastCGI on Apache via mod_fcgid) was working, our PHP code was actually running and so the actual errors is the result of the vast swaths of our current PHP web tier applications needing to be migrated across to work against this new PHP 8.1 binding for the MapGuide API.
And so for the next few months I did just that, not just for PHP, but also for Java and .net. You can consider this post to be a preview of what you'll need to do yourself if you want to migrate your PHP/Java/.net MapGuide applications to MGOS 4.0.
PHP Migration Overview
The PHP binding was the one I expect to be the most work because besides finally supporting PHP 8.1, the major feature of this new PHP binding is that constants.php is no longer required! This is because with vanilla SWIG we now can bake all the constants of the MapGuide API into the PHP binding extension itself! So I expect a lot of "include 'constants.php'" references needing to be removed.
Once all the constants.php references are removed, we found the prime issue with this new PHP binding. PHP didn't like some of our C++ classes had overloaded methods whose signatures did not exist in the parent class. This manifested in the form of fatal PHP errors like the following:
PHP Fatal error: Declaration of MgCoordinateSystemMeasure::GetDistance(MgCoordinate|float|null $arg1, MgCoordinate|float|null $arg2, float $arg3, float $arg4): float must be compatible with MgMeasure::GetDistance(?MgCoordinate $arg1, ?MgCoordinate $arg2): float in Unknown on line 0
In this case, our MgMeasure class has a GetDistance method of the following signature:
double GetDistance(MgCoordinate* coord1, MgCoordinate* coord2)
In the derived MgCoordinateSystemMeasure, it has a new overload of GetDistance that has this signature:
double GetDistance(double x1, double y1, double x2, double y2)
However, when this converted to PHP proxy classes by SWIG, PHP doesn't like this class setup because under its inheritance model, it is expecting the GetDistance overload with 4 double parameters to also exist in the base MgMeasure class. This is not the case, and thus PHP throws the above fatal error.
To workaround this problem, we had to use the SWIG %rename directive to rename the conflicting overload signature in MgCoordinateSystemMeasure in PHP to the following:
double GetDistanceSimple(double x1, double y1, double x2, double y2)
With this rename, there is no longer a signature conflict in the generated proxy class and PHP no longer throws a fatal error. Fortunately, only 2 classes in the MapGuide API have this problem, so the amount of method renaming is minimal.
Once this issue was addressed, I tried firing up the PHP implementation of the AJAX viewer and I got an interactive map! Everything seemed to be working until I tried to generate a map plot, and found my second problem. I was getting PHP fatal errors like this:
PHP Fatal error: Uncaught TypeError: No matching function for overloaded 'MgRenderingService_RenderMap' in quickplotgeneratepicture.php:115
Fortunately, this one was easier to explain and fix. In PHP 8.1 (maybe even earlier in the PHP 7.x series), the type checking became more stricter which meant int parameters must take integers, double parameters must take doubles, etc, etc, you couldn't pass ints as doubles or vice versa, and for a method like RenderMap of MgRenderingService, there are lots of overloads that take many different combinations of int and double parameters.
Our map plotting code was passing in strings where int/double parameters were expected. In PHP 5.6 this was allowed because the type checking was evidently more lax. Now such cases cause the above PHP fatal error. This was easy enough to fix, we just use the intval and doubleval functions to make sure ints are being passed into int parameters and doubles are being passed into double parameters.
And with that, the rest of the changes involving fixing up our exception handling code due to a major change with how MapGuide applications should be handling exceptions from the MapGuide API. As part of this SWIG binding work, we've flattened the MapGuide exception hierarchy into a single MgException class, and introduced a new exception code property to allow handling MapGuide exceptions on a case-by-case basis.
So if you were handling specific MapGuide exceptions like this:
1
2
3
4
5
6
7
8
try
{
//Some code that could throw
}
catch (MgUnauthorizedAccessException $e)
{
...
}
You would now rewrite them like this:
1
2
3
4
5
6
7
8
9
10
try
{
//Some code that could throw
}
catch (MgException $e)
{
if ($e->GetExceptionCode() == MgExceptionCodes::MgUnauthorizedAccessException) {
...
}
}
The reason for flattening the exception hierarchy was:
- To make wrapping exceptions simpler (we now only need to wrap the sole MgException class in SWIG) and not have to handle exception class inheritance chains in a consistent manner across all 3 language bindings.
- Most of the example MapGuide API code pretty much only caught MgException anyways and rarely catches any of its derived exception classes (and I imagine that this is the case in your MapGuide applications as well). Any code that cared to handle specific exception cases, we can just include the relevant sub-classification as a property of MgException itself as the above code example shows.
Once this final change was made, the AJAX viewer was fully functional. Porting Fusion to PHP 8 was a similar process.

Java Migration Overview
This migration I expect to be a cakewalk because although this binding is now also being generated by vanilla SWIG, it is 99% identical to the existing MapGuideJavaApiEx.jar that we have been generating and shipping for many releases of MapGuide.
So all I expect is just to:
- Fix up references to MapGuideJavaApiEx and rename them to MapGuideJavaApi
- Update exception handling blocks to take action based on the captured exception code in the caught MgException instead of catching for specific subclasses of MgException
- Replace MapGuideApiEx.jar with MapGuideApi.jar (we're using the old jar name for the new binding) in our MG installation (and effectively, going back full circle to the way things were for Java in MapGuide)
And ... it went just exactly what I said above! This was by far the easiest migration effort of the lot.
.net Migration Overview
This migration was the one I had been dreading the most. Not because I feared this binding was going to be fragile, because we already had an exhaustive test suite which this binding passed with flying colors.
But rather, I had been dreading this one because all of our .net code that is going to use this binding (AJAX viewer, code samples, etc) are all legacy pre-historic aspx webforms and I wasn't sure if such code would accept the brand new .net development story I had planned for it.
Consider the current .net development story.
1. You would reference the 5 OSGeo.MapGuide.* assemblies from mapviewernet/bin in your MapGuide application.
2. You would then have to manually copy the remaining dlls from mapviewernet/bin to your MapGuide application's output directory so that the .net MapGuide API binding doesn't fail due to missing native dll dependencies
The alternative to this is to use the NuGet package, which make this story more seamless, but the process to build this NuGet package was a bespoke affair, with hand-crafted powershell scripts that trigger on nuget package installation to set up the necessary project build events to copy the native dlls needed by the OSGeo.MapGuide.* assemblies to the right location. Such functionality is tightly-coupled to Visual Studio, so if you were installing this NuGet package and building your MapGuide application outside of Visual Studio, none of the required post-build events would fire and the result is a broken MapGuide .net application because the native dll dependencies were not being copied to your application's output directory.
For this new .net binding, we build each OSGeo.MapGuide.* assembly as a separate SDK-style csproj project files. This new csproj file format has several benefits:
- You don't have to reference individual C# source files that need to be compiled. Any C# source fil in the same directory as the csproj file is implied to be compiled as part of the project. This is great because it means we can run SWIG to generate the .cs files straight into the project and build that project straight away afterwards.
- This csproj file format supports NuGet packages as first-class project output
- The NuGet packages produced have first-class support for native dependencies. This is the real killer feature because it means in terms of packaging, we just have to include these native dlls in a well known location and they will be bundled up automatically as part of NuGet package creation. Such a package when consumed will have its native dependencies automatically copied to the right place and loaded from the right spot without any custom post-build events to set this stuff up!
- And finally, it means instead of targeting .net Framework, we can target netstandard2.0
What does netstandard2.0 support imply? It implies your MapGuide application using these packages can work on all of these platforms. Now practically speaking, despite now being netstandard2.0 packages, these packages will only work on platforms where the underlying OS is Windows and (maybe) Linux as those are the platforms where we can actually compile the underlying supporting native libraries needed by these nuget packages. So no Mac OSX, no Xamarin, etc.
In practical terms, it means you are no longer shackled to legacy .net framework for building MapGuide .net applications. You can now use .net core from its earliest netstandard2.0-supported iterations all the way to the latest .net 6.0 (as of this post).
That's great and all, but going back to the original issue: Can the current suite of aspx webforms code accept this new way of consuming the .net MapGuide API and come along for the ride? I hope so! Because the alternative is to rewrite all of this code with more modern .net web technologies (razor pages maybe?), and while such a rewrite has merit and probably warranted, it is not warranted right now because that would add many more months of dev work to my already time-poor schedule. We have bigger fish to fry! We just hope this current codebase will cooperate with our new .net packaging paradigm with minimal effort.
So let's start with the basic facts.
- MapGuide's .net integration requires IIS and .net framework to already be installed
- We can assume that for the purpose of being able to use this netstandard2.0 library, that the installed .net framework version must .net framework 4.8. Building your own MapGuide applications for .net core and .net 5.0+ is something you can opt-in to, but it is not something to be demanded by our existing .net web tier code.
With these facts established we have our first hurdle, and it is one of setup/deployment.
The AJAX viewer and sample code have no Visual Studio solution/project files! How do these things ever get built?
The AJAX viewer for .net is a series of raw .aspx files, will be "compiled" to .net assemblies on first request to IIS. As part of this compilation, it will check its respective "bin" directory for any references. That's why the mapviewernet/bin has the OSGeo.MapGuide.* assemblies in there because that is what is being referenced when the .aspx files get compiled. The .net sample code also follows the same pattern.
So we have a bunch of folders of .aspx files and we need to get the correct set of dlls from inside our brand new shiny nuget packages into these folders. How would we go about this without needing to disruptively set up solution/project files for them?
Here's my approach. We setup a stub SDK-style project that targets net4.8 and references the 5 OSGeo.MapGuide.* nuget packages produced from our new .net binding project setup.
As part of the main build, we perform a framework-dependent publish of this project. Because of the first-class native dependency support, the publish output of this project would be the project's assembly, the 5 OSGeo.MapGuide.* assemblies and (importantly) all of their native dll dependencies in one single output directory. Once we done the framework-dependent publish, we can then copy all the dll files in this publish output folder (except for the stub project) into the bin directory of our AJAX viewer and sample directories.
It turns out this approach does result in a functional .net AJAX viewer and code samples. What was needed in addition to using a stub project to setup the required dll file list, is that the .net AJAX viewer and code samples need a web.config file that references the netstandard assembly due to our OSGeo.MapGuide.* assemblies now target netstandard2.0
Is this a complete and utter hack? Totally!
But this approach gives us a functional .net AJAX viewer and code samples. Considering the alternative solutions and my current timelines, this is a workable approach and sometimes ...

So that was the ugly setup/deployment aspect, but what about the code itself? Well that was relatively simple. Like PHP and Java before it, we only needed to fix up the exception handling code to match to our new pattern of checking for specific exception codes in the caught MgException to handle for certain error cases.
Getting this to work on Linux
With the bindings now all being generated by vanilla SWIG and all working on Windows, it was a case of getting the build system fully working again on Linux with these new bindings and updated web tier components.
Fortunately, on the binding front, most of the CMake configurations added in the initial phases of this work only needed minor adjustments, so the bulk of the work was actually building PHP 8.1 and integrating this into the Apache [httpd] server, which we are also building from source and updating our various [httpd] config file templates to work with this new version of PHP.
Where we stand now
We now finally have MapGuide API bindings generated with vanilla, unmodified SWIG that work on both Windows and Linux. This has been a long and arduous journey and I can finally see the light at the end of this tunnel!
A new RFC has been posted for PSC discussion/voting. I hope there isn't strong opposition/dissent on these changes, because I truly believe that this work is absolutely necessary for MapGuide going forward. Newer versions of .net/Java/PHP will always get released and inevitably we will need our MapGuide API bindings to work on these newer versions. Our current infrastructure to keep up with newer .net/Java/PHP versions is just not maintainable or tenable.
If/when this RFC is adopted, the long overdue Preview 4 release should drop not too long after!
12:11
Marco Bernasocchi: Corso QGIS di base Bellinzona, 19.10/26.10.2022
sur Planet OSGeo
Iscrizione
Il corso dura 2 giorni (9:00 – 17:00) e costa 990 CHF a persona (compreso il pranzo e il certificato). Un insegnante per un massimo di 6 partecipanti e 2 insegnanti da 7 a 12 partecipanti.
Descrizione
Alla fine di questo corso, i partecipanti conosceranno le principali funzioni di QGIS Desktop (software GIS open source) e saranno in grado di importare e analizzare dati, creare una mappa con layout professionale ed inserire oggetti con attributi e geometrie vettoriali.
Programma giorno 1
- Introduzione
- Informazioni sul progetto QGIS
- Panoramica dell’interfaccia utente
- Plugins
- Fonti di dati, formati di dati e servizi web
- Gestione dei dati nel progetto
- Configurazione dei formulari
- Simbologia, etichettatura
Programma giorno 2
- Espressioni semplici
- Selezione e filtro
- Tabella degli attributi, calcolatore di campo, campi virtuali
- Layer temporanei
- Digitalizzazione e modifica della geometria e degli attributi
- Introduzione Strumenti di Processing
- Analisi semplici di dati vettoriali
- Layout con il compositore di stampe
Preconoscenze
Conoscenza di base di GIS (es. Il termine “layer”) e database (es. Il termine “data type” con intero / numero / data / stringa / booleano).
Certificazione
Questo corso è organizzato da un’organizzazione riconosciuta da QGIS . La certificazione dei partecipanti è inclusa nel prezzo del corso.
Software
Installazione di QGIS per Windows, macOS o Linux https://download.qgis.org
- Utiliziamo l’ultima versione LTR disponibile.
- Nessun plugin deve essere precedentemente installato.
12:10
Marco Bernasocchi: Cours QGIS de base Lausanne, 26.10/28.10.2022
sur Planet OSGeo
Inscription
Le cours est sur 2 jours (9:00 – 17:00) et coûte 990 CHF par personne (déjeuner et certificat inclus). Un enseignant pour un maximum de 6 personnes et 2 enseignants pour 7 à 12 personnes.
Description
À l’issue de ce cours, les participants connaîtront les principales fonctions de QGIS Desktop, logiciel open source SIG et seront capables d’importer et d’analyser des données, de créer une carte avec une mise en page professionnelle et de saisir des objets avec des attributs et des géométries vectorielles.
Programme jour 1
- Introduction
- À propos du projet QGIS
- Présentation de l’interface utilisateur
- Extensions
- Sources de données, formats de données et services web
- Gérer les données dans le projet
- Configuration du formulaire d’attributs
- Symbologie et etiquettes
Programme jour 2
- Expressions simples
- Sélection et filtres
- Table d’attributs, calculateur de champs, champs virtuels
- Couches temporaires
- Saisie et édition des géométries et attributs
- Introduction outils de traitements
- Analyse simple de données vecteurs
- Mise en page avec le composeur d’impression
Connaissances préalables
Connaissance de base des SIG (par exemple, le terme “couche”) et des bases de données (par exemple, le terme “type de données” avec nombre entier/nombre/date/chaîne/booléen).
Certification
Ce cours est organisé par un organisme reconnu par QGIS. La certification des participants est incluse dans le prix du cours.
Logiciel
Installation de QGIS pour Windows, macOS ou Linux [https:]]
- Nous utilisons la dernière version LTR disponible.
- Aucun plugin ne doit être préalablement installé.
12:08
Marco Bernasocchi: New QGIS Courses dates Autumn 2022
sur Planet OSGeo
We published our new dates for this autumns QGIS online courses.
- German:
  - QGIS_Einsteigerkurs, Zürich 27.10./03.11.2022, next course spring 2023
- French:
  - Cours_de_base, 26./28.10.2022 Lausanne, next course spring 2023
- Italian:
  - Corso_di_base, Bellinzona 19./26.10.2022, next course spring 2023
The courses last two days (9:00 a.m. – 5:00 p.m.) and cost 990 CHF per person. As in our in-person courses, we limit our instructor to participant ratio to a maximum of 6 participants for one instructor and two instructors for 7 to 12 participants.

Subsribe now
08 September 2022
7:00
Marco Bernasocchi: 24th Contributors QGIS Meeting in Firenze 2022
sur Planet OSGeo

The international community of QGIS contributors got together in person from 18 to 22 August in parallel to OpenStreetMap State of The Map event and right before the FOSS4G. So there was a lot of open source geo power concentrated in the beautiful city of Florence in those days. It was my first participation and all I knew was that it’s supposed to be an unconference. This means, there is no strict schedule but space and opportunity for everyone to present their work or team up to discuss and hack on specific tasks to bring the QGIS project to the next level.
Introduction and first discussions
We were a group of six OPENGIS.ch members arriving mostly on Thursday, spending the day shopping and moving into our city apartment. In the evening we went to a Bisteccheria to eat the famous Fiorentina steak. It was big and delicious as was the food in general. Though, I am eating vegetarian since to compensate. On Friday we went to the Campus to meet the other contributors. After a warm welcome by the organizer, Rossella and our CEO and QGIS chair Marco Bernasocchi we did an introduction round where everyone mentioned their first QGIS version ever used. At this point, I became aware of the knowledge and experience I was sharing the room with. Besides this, I noticed that there was another company attending with several members, namely Tim Sutton’s Kartoza, which is also contributing a lot to QGIS. The first discussion was about QGIS funding model, vision, communication and on the new website in planning. This discussion then moved into some smaller groups including most of the long term contributors. I was looking around, physically and virtually, and tried to process all the new inputs and to better understand the whole QGIS world. Besides, I noticed my colleague Ivan having problems with compiling QGIS after upgrading to Ubuntu 22.04 which then motivated my other colleague Clemens to implement a docker container to do the compilation. Nevertheless, I postponed my Ubuntu upgrade. That evening we went out all together to have a beer or two and play some pool sessions and table football. Finally, the OPENGIS.ch crew navigated back home pairing a high-precision GNSS sensor with a mobile device running OpenStreetMap in QField. We arrived back home safely and super precise.
First tasks and coffee breaks
There was catering in the main hall covering breakfast, lunch and coffee breaks. It never took long after grabbing a cup of coffee to find yourself in a conversation with either fellow contributors or OpenStreetMap folks. I chatted with a mapper from Japan about mobile apps, an engineer from Colombia about travelling and a freelancer from the Netherlands about GDAL, to name 3 coffees out of many.
QGIS plugins website
After some coffee, Matthias Kuhn, our CTO and high-ranking QGIS contributor, asked me whether I could improve some ugly parts of QGIS plugins website. So I had my first task which I started working on immediately. The task was to make the site more useful on mobile devices which would be achieved by collapsing some unimportant information and even removing other parts. I noticed some quirks in the development workflow, so I also added some pre-commit hooks to the dev setup. Dimas Ciputra from Kartoza helped me finalize the improvements and merge them into master branch on github.
QGIS website downloads section
Regis Haubourg asked to help simplify the QGIS Downloads for Windows section on the main QGIS website. We played around in the browser dev tools until we thought the section looked about right. I then checked out the github repo and started implementing the changes. I need to say the tech stack is not quite easy to develop with currently, but there is a complete rework in planning. Anyway, following the pull request on github a lively discussion started which is ongoing by the time of writing. And this is a good thing and shows how much thought goes into this project.
Presentations
There were many interesting and sometimes spontaneous presentations which always involved lively discussions. Amy Burness from Kartoza presented new styling capabilities for QGIS, Tobias Schmetzer from the Bavarian Center for Applied Energy Research presented the geo data processing and pointed out issues he encountered using QGIS on this and Etienne Trimaille from 3liz talked about qgis-plugins-ci, just to name a few.
Amazing community
On Saturday evening a bus showed up at the campus and took us on a trip up to the hills. After quite a long ride we arrived at a restaurant high up with mind-blowing view of the city. I forgot how many rounds of Tuscan food were served, but it was delicious throughout. An amazing evening with fruitful conversations and many laughs.

The weather was nice and hot, the beers cold, the Tuscan food delicious and the contributors were not only popular Github avatars but really nice people. Thank you QGIS.
05 September 2022
18:41
Sean Gillies: Superior training week twenty-three recap
sur Planet OSGeo
I did less running last week, but it was high quality running. Plenty of technical, hilly single track and strides. Sunday I went for an hour long bike ride with Ruth instead of running.
- 4 hours, 9 minutes (running)
- 19.0 miles
- 3,097 ft D+
Friday I stopped by the top of Arthur's Rock for a view over Horsetooth Reservoir and the plains. This Saturday I'll be getting views of Lake Superior.

Arthur's Rock has a rock
15:26
Le blog de Geomatys: Geomatys is ASPIRING with ESA
sur Planet OSGeo
A little update on Geomatys’ expansion into geospatial health applications…
European Space Agency’s ASPIRE with ESA program
Geomatys has been named lauréat of an ASPIRE with ESA business development grant to help put together all the elements we have been working towards over the past two years to make the wealth of tele-epidemiology and infectious disease ecology knowledge more widely available for managing health risks. With the summer we’ve all just experienced, it’s no secret that our changing climate means we can no longer rely on the patterns of the past or gradual changes that can be mitigated “petit-à-petit”. Preparedness requires a more nimble approach combined with deeper knowledge of the underlying processes that drive risk.

Our project is gaining momentum!

We have hired experts in infectious disease epidemiology and modeling and will soon welcome a marketing and business development specialist. We are on our way towards producing a platform to make information curated from academic results and geospatial data technologies accessible to decision makers in need of timely evidence-based assessments of the current and future risks posed by a growing list of infectious diseases.

Our team has grown!

In June, we had the pleasure of welcoming Dr. Sarah Kada, an infectious disease modeler, who just completed 2.5 years of postdoctoral work in the Dengue Unit of the US CDC, where she also helped with the COVID-19 response. A master already of * many * things, Sarah is learning the ins-and-outs of industry and the world of geospatial data infrastructures.

For more information, please do not hesitate to get in touch!
- Dr Jessie Abbate, PhD
  Research Scientist, Project Lead, Business Developer
  jessica.abbate [at] geomatys.com
- Dr Sarah Kada, PhD
  Research Scientist, Business Developer
  sarah.kada [at] geomatys.com
12:42
GeoSolutions: GeoSolutions presentations from FOSS4G 2022
sur Planet OSGeo

You must be logged into the site to view this content.
9:05
longwayaround.org.uk: Web Mercator OS Vector Tile API in OpenLayers - Take #2
sur Planet OSGeo

This is an update to my previous post on the same subject.

Thanks to some feedback from Andreas Hocevar and a pull request I made to ol-mapbox-style adding a Vector Tile layer of Ordnance Survey data from the OS Data Hub to an OpenLayers map in Web Mercator is a …
31 August 2022

20:46

QGIS Blog: Plugin Update August 2022

sur Planet OSGeo

30 August 2022
11:00
CARTO Blog: Spatial Data Scientist of the Year Award 2022
sur Planet OSGeo

At this year’s upcoming Spatial Data Science Conference New York we’ll be announcing the third winner of the Spatial Data Scientist of the Year award in person.
7:23
Marco Bernasocchi: Writing a feature-based processing algorithm at the example of M-value interpolation
sur Planet OSGeo

This content is restricted to members only. Please login or register for access. Username or Password should be not be empty Username or Email Address Password Remember Me Lost Password
29 August 2022
5:38
Sean Gillies: Superior training week twenty-two recap
sur Planet OSGeo
I got some running-is-a-part-time-job kind of numbers this week.
- 14 hours, 32 minutes
- 60.4 miles
- 10,656 ft D+
I ran every day except Monday and hills every day but Thursday, when I did an easy run by the river.

Osprey at the Cache La Poudre River

Two weeks ago I wrote:

I want to get ~110 miles and 15,000 ft of climbing in over the next two weeks.

I pretty much did it. 103 miles and almost 18,000 ft of climbing. My training is finally coming together and none too soon, with my one race of the year less than two weeks away.

Today I went back to RMNP to beat the heat and had a great long run on the loop I did in June, but in the other direction and without snow. I weathered some afternoon rain and hail, for the first time on a long run, and at the end of the day dealt with a herd of elk at the trailhead where I had parked. I'm comfortable being close to mule deer, but adult elk are big and can mess you up! The smart thing to do is wait for them to move along, or go around, giving them a wide berth. In about two weeks, male elk will begin competing for mates and it will become more dangerous to be out in the meadows with them.

Elk at Rocky Mountain National Park
28 August 2022
10:58
Adam Steer: FOSS4G 2022, Tromsø edition
sur Planet OSGeo

This last few days I’ve been dialing into FOSS4G 2022 from Tromsø, northern Norway. It’s the first time I’ve checked in to one since 2019! It wasn’t possible to attend in person this time, so I’m really happy that an online option was part of the package. And, as much as I really wanted to… Read More »FOSS4G 2022, Tromsø edition
27 August 2022
2:00
PostGIS Development: PostGIS 3.3.0 Released
sur Planet OSGeo

The PostGIS Team is pleased to release PostGIS 3.3.0.
26 August 2022
2:00
SourcePole: FOSS4G 2022 Florence
sur Planet OSGeo

FOSS4G is the annual global event of free and open source geographic technologies and open geospatial data hosted by OSGeo. In 2022 it took place in Firenze with over 1300 participants, 402 talks and 44 workshops.
25 August 2022
2:00
PostGIS Development: Upgrading postgis_sfcgal to 3.1 or higher
sur Planet OSGeo
As of PostGIS 3.1, the PostGIS sfcgal support library is no longer part of the postgis core library, but instead spun off into a new library postgis_sfcgal-3.

This change is not an issue for people doing regular, soft-upgrades from a PostGIS < 3.1 compiled with SFCGAL to a PostGIS >= 3.1 with SFCGAL using ALTER EXTENSION postgis_sfcgal UPDATE; or SELECT postgis_extensions_upgrade();. However if you are using pg_upgrade, you might get errors like postgis-3 does not contain function postgis_sfcgal_version() (which is part of the postgis_sfcgal extension).

The three main reasons for this break were:
- We wanted postgis-3 library to have the same exposed functions regardless if you are compiling with SFCGAL or not. This change was planned in PostGIS 3.0, but only the backend switching plumbing was removed and not the complete detachment.
- It makes it possible for packagers to offer postgis_sfcgal (perhaps as a separate package), without requiring other users who just want postgis to have to have boost and CGAL.
- In the past postgis_sfcgal and postgis extensions were hooked together at the hip in the same underlying library, because their were a few functions overlapping in name such as ST_3DIntersects and ST_Intersects. Trying to explain to people how this whole thing worked, to switch the backend to sfcgal if they wanted extended 3D functionality, not to mention the added annoyance GUC backend of notices during upgrade was more of a pain than it was worth. So moving forward, we will not be reusing function names between the two extensions, and will have only non-overlapping function names.
0:19
Martin Davis: Validating Polygonal Coverages in JTS
sur Planet OSGeo
The previous post discussed polygonal coverages and outlined the plan to support them in the JTS Topology Suite. This post presents the first step of the plan: algorithms to validate polygonal coverages. This capability is essential, since coverage algorithms rely on valid input to provide correct results. And as will be seen below, coverage validity is usually not obvious, and cannot be taken for granted.
As described previously, a polygonal coverage is a set of polygons which fulfils a specific set of geometric conditions. Specifically, a set of polygons is coverage-valid if and only if it satisfies the following conditions:
- Non-Overlapping - polygon interiors do not intersect
- Edge-Matched (also called Vector-Clean and Fully-Noded) - the shared boundaries of adjacent polygons has the same set of vertices in both polygons
The Non-Overlapping condition ensures that no point is covered by more than one polygon. The Edge-Matched condition ensures that coverage topology is stable under transformations such as reprojection, simplification and precision reduction (since even if vertices are coincident with a line segment in the original dataset, this is very unlikely to be the case when the data is transformed). An invalid coverage which violates both (L) Non-Overlapping and (R) Edge-Matched conditions (note the different vertices in the shared boundary of the right-hand pair)
Note that these rules allow a polygonal coverage to cover disjoint areas. They also allow internal gaps to occur between polygons. Gaps may be intentional holes, or unwanted narrow gaps caused by mismatched boundaries of otherwise adjacent polygons. The difference is purely one of size. In the same way, unwanted narrow "gores" may occur in valid coverages. Detecting undesirable gaps and gores will be discussed further in a subsequent post. Computing Coverage ValidationCoverage validity is a global property of a set of polygons, but it can be evaluated in a local and piecewise fashion. To confirm a coverage is valid, it is sufficient to check every polygon against each adjacent (intersecting) polygon to determine if any of the following invalid situations occur:
- Interiors Overlap:
- Edges do not Match:
If neither of these situations are present, then the target polygon is coverage-valid with respect to the adjacent polygon. If all polygons are coverage-valid against every adjacent polygon then the coverage as a whole is valid.
For a given polygon it is more efficient to check all adjacent polygons together, since this allows faster checking of valid polygon boundary segments. When validation is used on datasets which are already clean, or mostly so, this improves the overall performance of the algorithm.
Evaluating coverage validity in a piecewise way allows the validation process to be parallelized easily, and executed incrementally if required.JTS Coverage ValidationValidation of a single coverage polygon is provided by the JTS CoveragePolygonValidator class. If a polygon is coverage-invalid due to one or more of the above situations, the class computes the portion(s) of the polygon boundary which cause the failure(s). This allows the locations and number of invalidities to be determined and visualized.
The class CoverageValidator computes coverage-validity for an entire set of polygons. It reports the invalid locations for all polygons which are not coverage-valid (if any).
Using spatial indexing makes checking coverage validity quite performant. For example, a coverage containing 91,384 polygons with 10,474,336 vertices took only 6.4 seconds to validate. In this case the coverage is nearly valid, since only one invalid polygon was found. The invalid boundary linework returned by CoverageValidator allows easily visualizing the location of the issue.
A polygonal dataset of 91,384 polygons, containing a single coverage-invalid polygon
The invalid polygon is a tiny sliver, with a single vertex lying a very small distance inside an adjacent polygon. The discrepancy is only visible using the JTS TestBuilder Reveal Topology mode.
The size of the discrepancy is very small. The vertex causing the overlap is only 0.0000000001 units away from being valid:
[921] POLYGON(632)[922:4] POLYGON(5)Ring-CW Vert[921:0 514] POINT ( 960703.3910000008 884733.1892000008 )Ring-CW Vert[922:4:0 3] POINT ( 960703.3910000008 884733.1893000007 )
This illustrates the importance of having fast, robust automated validity checking for polygonal coverages, and providing information about the exact location of errors.Real-world testingWith coverage validation now available in JTS, it's interesting to apply it to publicly available datasets which (should) have coverage topology. It is surprising how many contain validity errors. Here are a few examples:
Source City of Vancouver
Dataset Zoning Districts

This dataset contains 1,498 polygons with 57,632 vertices. There are 379 errors identified, which mainly consist of very small discrepancies between vertices of adjacent polygons.Example of a discrepant vertex in a polygon

Source British Ordnance Survey OpenData

Dataset Boundary-Line

File unitary_electoral_division_region.shp

This dataset contains 1,178 polygons with 2,174,787 vertices. There are 51 errors identified, which mainly consist of slight discrepancies between vertices of adjacent polygons. (Note that this does not include gaps, which are not detected by CoverageValidator. There are about 100 gaps in the dataset as well.)An example of overlapping polygons in the Electoral Division dataset

Source Hamburg Open Data Platform

Dataset VerwaltungsEinheit (Administrative Units)

The dataset (slightly reduced) contains 7 polygons with 18,254 vertices. Coverage validation produces 64 error locations. The errors are generally small vertex discrepancies producing overlaps. Gaps exist as well, but are not detected by the default CoverageValidator usage.An example of overlapping polygons (and a gap) in the VerwaltungsEinheit dataset

As always, this code will be ported to GEOS. A further goal is to provide this capability in PostGIS, since there are likely many datasets which could benefit from this checking. The piecewise implementation of the algorithm should mesh well with the nature of SQL query execution.
And of course the next logical step is to provide the ability to fix errors detected by coverage validation. This is a research project for the near term.
UPDATE: my colleague Paul Ramsey pointed out that he has already ported this code to GEOS. Now for some performance testing!
24 August 2022
11:00
CARTO Blog: CARTO’s Ultimate Guide to Spatial Joins & Predicates with SQL
sur Planet OSGeo

If you’re a Spatial Data Scientist there’s probably one operation type you’ll be performing all the time; maybe more than anything else. The Spatial Join. Spatial Joins are...
23 August 2022
16:06
Jackie Ng: MapGuide Site Administrator XSS security fix available
sur Planet OSGeo
A security fix is now available for MapGuide Open Source.
This fix mitigates several XSS vulnerabilities reported in the MapGuide Site Administrator tool.
Download the fix here
To apply, simply extract the zip contents to the www/mapadmin folder of your MapGuide installation and overwrite all existing files.
This fix can be applied to the following versions of MapGuide Open Source:
- 2.6.1
- 3.0.0
- 3.1.0
- 3.1.1
- 3.1.2
- Any preview release of 4.0.0
Special thanks to Eitan Shav of mend.io who found and reported this vulnerability
2:00
SourcePole: Untainting Exim vdom alias lookups
sur Planet OSGeo

What to do on Warning: Tainted filename for search '/etc/exim4/virtual/some.domain?
22 August 2022
16:54
Sean Gillies: Superior training week twenty-one recap
sur Planet OSGeo
This was my biggest week since the end of June. A busy family calendar made it hard to get more time on the trail.
- 9 hours, 40 minutes
- 42.8 miles
- 7,303 ft D+
The Superior trail race is less than three weeks away. I'm planning to run quite a bit this week, do some fine tuning for a week, and then have a short one week taper.
2:00
GeoServer Team: GeoServer 2.22-M0 Milestone Release
sur Planet OSGeo
GeoServer 2.22-M0 release is now available with downloads (bin, war, windows), along with docs, extensions, and data directory.

This is a milestone release previewing the GeoServer 2.22.x series for FOSS4G attendees.

Thanks to Jody Garnett and Ian Turton for making this release.
Docker image
This release is also available as an official Docker image:
```
docker pull docker.osgeo.org/geoserver:2.22-M0
docker run -it -p 80:8080 docker.osgeo.org/geoserver:2.22-M0
```
Welcome Page Improvements
The welcome page has been improved with the ability to:
- Select workspace to browse workspace web services
- Select layer and layergroup for layer specific web services
GeoPackage Sample data
The sample data directory now includes a small geopackage generated from Natural Earth data.

About GeoServer 2.22
Release notes: ( 2.22-M0 )
2:00
PostGIS Development: PostGIS 3.3.0rc2
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.3.0rc2! Best Served with PostgreSQL 15 beta3 ,GEOS 3.11.0 , and SFCGAL 1.4.1

Lower versions of the aforementioned dependencies will not have all new features.

This release supports PostgreSQL 11-15.

3.3.0rc2
This release is a release candidate of a major release, it includes bug fixes since PostGIS 3.2.3.
18 August 2022
10:31
gvSIG Team: 18as Jornadas Internacionales gvSIG + GeoLIBERO 2022 (presentación)
sur Planet OSGeo

Decía Oscar Wilde que un mapamundi que no incluya los territorios de la utopía no vale la pena mirarlo, pues cuando la Humanidad mira a lo lejos tierras mejores, siempre zarpa hacia ellas. El progreso, decía el escritor, es la realización de las utopías.

Este año son las 18as Jornadas Internacionales de gvSIG, un proyecto que en sus inicios fue tachado de utópico, de irrealizable, y que dieciocho años después está más activo que nunca. Tras dos años en los que el evento tuvo que realizarse en modalidad virtual, regresa a la presencialidad, en València, la ciudad que se ha convertido por derecho propio en uno de los centros de referencia de la geomática, la ciencia y tecnología aplicada a la gestión territorial.

Volvemos de la mejor manera posible, uniendo esfuerzos con la Red GeoLIBERO, impulsada por CYTED Programa Iberoamericano de Ciencia y Tecnología para el Desarrollo. Una red que aúna a algunas de las principales entidades y personas del ámbito de la investigación en el área de la geomática libre. Coordinadores de los distintos grupos de investigación de GeoLIBERO, de toda Iberoamérica, presentarán sus trabajos en el marco de las Jornadas.

Impulsando la economía del conocimiento, lema del evento, destaca uno de los ejes principales del proyecto gvSIG. Los últimos tiempos están haciéndonos más conscientes de la necesidad de ser independientes en sectores críticos como la energía, la sanidad, la defensa y, por supuesto, la tecnología. Soberanía tecnológica, uno de los lemas de gvSIG, y que debe ir intrínsecamente relacionado con la soberanía económica.

Es necesario, hoy más que nunca, impulsar los proyectos que apuestan por nuevos modelos de negocio, basados en la colaboración, la solidaridad y el conocimiento compartido. Es el momento de romper definitivamente con la dependencia tecnológica, con modelos que no generan economía y suponen gasto. El momento de mantener y reforzar tecnologías que se asientan sobre los conceptos de cooperación y sostenibilidad. Es el momento de gvSIG y la geomática libre.
2:00
PostGIS Development: PostGIS 3.2.3, 3.1.7, 3.0.7, 2.5.8 Released
sur Planet OSGeo

The PostGIS development team is pleased to provide bug fix and performance enhancements 3.2.3, 3.1.7, 3.0.7, 2.5.8 for the 3.2, 3.1, 3.0, 2.5 stable branches.
16 August 2022
6:58
Marco Bernasocchi: A New Trick up QField’s Sleeve: Animated Maps
sur Planet OSGeo

Marco Bernasocchi: A New Trick up QField’s Sleeve: Animated Maps
14 August 2022
22:45
Sean Gillies: Busy
sur Planet OSGeo

I'm solo parenting next week while Ruth is traveling. Between work, running, and the first week of school for the kids, I'm going to be busy. Apologies in advance for delayed replies to emails and open source project issues.
20:33
Sean Gillies: Superior training week twenty recap
sur Planet OSGeo
Week twenty was supposed to be a rest week. I took it pretty easy and did just one long high-altitude run on Friday. From the Bear Lake Road Park and Ride lot in Rocky Mountain National Park, I ran past Bierstadt Lake, up to Flattop Mountain (12,324 ft), Ptarmigan Pass, and back. 16 miles and 4,000 ft of elevation gain in all. I saw moose grazing in Bierstadt Lake, elk at Ptarmigan Pass, and pika all over the FLattop Mountain trail. This run dominated my numbers for the week.
- 7 hours, 3 minutes
- 26.1 miles
- 5,020 ft D+
Moose in Bierstadt Lake

Tonahutu Trail at Ptarmigan Pass

Odessa Lake, Lake Helene, Two Rivers Lake (left to right)

I want to get ~110 miles and 15,000 ft of climbing in over the next two weeks. I hope weather and my health continue to stay good.
18:50
Free and Open Source GIS Ramblings: Forget label buffers! Better maps with selective label masks in QGIS
sur Planet OSGeo

Cartographers use all kind of tricks to make their maps look deceptively simple. Yet, anyone who has ever tried to reproduce a cartographer’s design using only automatic GIS styling and labeling knows that the devil is in the details.

This post was motivated by Mika Hall’s retro map style.

New print designs on the way: these are some snippets from a project I began last year to map the provinces of Spain in a retro style, which I've decided to revisit this summer.
Prints will be available later in the year! pic.twitter.com/gUJirBFv0x
— Mike Hall (@thisismikehall) July 22, 2022

There are a lot of things going on in this design but I want to draw your attention to the labels – and particularly their background:
Detail of Mike’s map (c) Mike Hall. You can see that the rail lines stop right before they would touch the A in Valencia (or any other letters in the surrounding labels).
This kind of effect cannot be achieved by good old label buffers because no matter which color we choose for the buffer, there will always be cases when the chosen color is not ideal, for example, when some labels are on land and some over water:
Ordinary label buffers are not always ideal.
Label masks to the rescue!
Selective label masks enable more advanced designs.
Here’s how it’s done:

Selective masking has actually been around since QGIS 3.12. There are two things we need to take care of when setting up label masks:

1. First we need to enable masks in the label settings for all labels we want to mask (for example the city labels). The mask tab is conveniently located right next to the label buffer tab:

2. Then we can go to the layers we want to apply the masks to (for example the railroads layer). Here we can configure which symbol layers should be affected by which mask:

Note: The order of steps is important here since the “Mask sources” list will be empty as long as we don’t have any label masks enabled and there is currently no help text explaining this fact.

I’m also using label masks to keep the inside of the large city markers (the ones with a star inside a circle) clear of visual clutter. In short, I’m putting a circle-shaped character, such as ?, over the city location:
In the text tab, we can specify our one-character label and – later on – set the label opacity to zero. To ensure that the label stays in place, pick the center placement in “Offset from Point” mode.
Once we are happy with the size and placement of this label, we can then reduce the label’s opacity to 0, enable masks, and configure the railroads layer to use this mask.

As a general rule of thumb, it makes sense to apply the masks to dark background features such as the railways, rivers, and lake outlines in our map design:
Resulting map with label masks applied to multiple labels including city and marine area labels masking out railway lines and ferry connections as well as rivers and lake outlines.
If you have never used label masks before, I strongly encourage you to give them a try next time you work on a map for public consumption because they provide this little extra touch that is often missing from GIS maps.

Happy QGISing! Make maps not war.
13 August 2022
20:41
Sean Gillies: Superior training week nineteen recap
sur Planet OSGeo
I spent most of week nineteen on the hot and humid coast of North Carolina. I did three hour-long barefoot runs on the beach, some bodyweight strength training, and three hour-long surfing lessons. Back at home on the weekend, I did one long run at Horsetooth Open Space. Two trips to the summit from the parking lot. That one run accounted for 3,900 ft of my week's elevation gain. There aren't any hills on Hatteras Island. Here are the numbers for the week.
- 7 hours, 16 minutes
- 29.5 miles
- 3,973 ft D+
12 August 2022
16:00
Free and Open Source GIS Ramblings: MovingPandas v0.11 released!
sur Planet OSGeo
The latest v0.11 release is now available from conda-forge.

This release contains some really cool new algorithms:
- New minimum and Hausdorff distance measures #37
- New functions to add a timedelta column and get the trajectory sampling interval #233
As always, all tutorials are available from the movingpandas-examples repository and on MyBinder:

The new distance measures are covered in tutorial #11:
Computing distances between trajectories, as illustrated in tutorial #11
Computing distances between a trajectory and other geometry objects, as illustrated in tutorial #11
But don’t miss the great features covered by the other notebooks, such as outlier cleaning and smoothing:
Trajectory cleaning and smoothing, as illustrated in tutorial #10
If you have questions about using MovingPandas or just want to discuss new ideas, you’re welcome to join our discussion forum.
11:00
CARTO Blog: How to create Google Street View pop-ups with CARTO
sur Planet OSGeo

Did you know it’s now been over 15 years since Google Street View was launched? It’s been a truly revolutionary technology, allowing users to immerse themselves in places a...
09 August 2022
0:45
iCarto Blog: Geolocation with GPS in Ionic
sur Planet OSGeo
When we talk about geolocation we refer to the ability of a device to obtain the geographical position in which it is located. To do this, you can use the WiFi access point to which you are connected, the mobile phone tower to which you are linked (in the case of phones or other mobile devices that have a SIM card) or through GPS technology. when you have it. Even these different options can be combined with each other to improve the precision that each of them offers us separately.

In mobile devices, this ability to obtain geolocation greatly opens up the range of applications that can be developed, some examples may be the creation of Apps to inventory information, including the geographical position of each element, store routes or get information about what we have nearby, etc. The possibilities are almost endless.

Recently, at iCarto, we had the need to develop a mobile application with which to collect information on the route followed to collect wild mushrooms. We are committed to developing this application using web technologies adapted to create mobile applications, specifically using the framework Ionic with ReactJS. In this project we had some particular need related to precision and the possibility of collecting route points even if the application was in the background and the device was being used for something else. That made us look at different geolocation plugins available for Ionic. In this article we want to share this analysis, as well as some of the conclusions and learnings along the way.

When working with technologies to develop a mobile application, by default we can use the W3C Geolocation API that browsers implement. However, the use of a specific geolocation plugin is recommended, which we can activate if we use Cordova to package the mobile application, or in our particular case Capacitor, the tool provided by Ionic. It is a good practice in general, since in this way we ensure that we will have the functionality available regardless of the version of the browser that the mobile device has. Let’s remember that when using this type of technology, in the end our application, on the mobile device, is running inside a web browser. But it is also that in our particular case it was mandatory, because we needed specific functionalities, which the geolocation API does not offer, such as support to continue obtaining the location when the application is in the background.
Cordova vs. Capacitor
Before going into the analysis of geolocation plugins, it is good to stop and review the two main alternatives for packaging mobile applications when we work with web technologies for their development.

Apache Cordova was one of the first mobile application development environments using web technologies, CSS, HTML, and JavaScript, instead of using platform-specific APIs. This has its advantages and disadvantages, which we are not going to talk about now, since it would take several posts. The Ionic project started out using Cordova as an application packaging tool as well, but more recently it came out with its own, Capacitor. On the project website they tell us the reason for this change and what advantages Capacitor brings.

One of the advantages of Capacitor is that it is fully compatible with Cordova, and therefore we can use plugins that are available for the latter even if they do not exist in Capacitor, or even if there is an equivalent version we can use the one from * Cordova* if we are interested for any reason. This, for example, allowed us to expand the range of plugins to review.

Precisely because Cordova has been available for much longer, the number of plugins that we can find, both official and developed by the community, is much greater today than in the case of Capacitor, which despite also having quite a few plugins developed by their community, in addition to official, due to their youth they are still less.
Geolocation plugins
Both Cordova and Capacitor have a default geolocation plugin, based on the browser API. They are easy-to-use plugins, which are available without having to add anything and that basically allow us to obtain the coordinates of the position in which the mobile device is located. Its API gives us two functions:
- getCurrentPosition: Gives us the coordinates when we call it.
- watchPosition: Allows us to connect to a watcher that returns the coordinates of the position every time there is a change, that is, every time we move.
In none of the cases can coordinates be obtained when the application is in background, one of the requirements that our application did have, for example, since when collecting a long route, it was necessary to be able to use the phone at the same time to other tasks, without stopping recording the route.

Luckily, thanks to the community we have more options available. In our case, we tried two other plugins that allow geolocation to work in background.
- BackgroundGeolocation by Capacitor-community: It is the latest plugin with support for working with geolocation in background, specific to Capacitor and with support for TypeScript.
- Cordova Plugin Background Geolocation: The classic plugin used in Cordova environments when background geolocation is needed. The last release is 3 years ago, although it still works fine on recent versions of Android.
Within the tests we did with these two plugins, in both we achieved sufficient precision for the needs of the project, in most cases of a few meters. The plugin options allow us to play with various parameters to optimize the needs of precision of the coordinates that are obtained with the battery life of the device, for example.

Although the plugin for Capacitor is more current, the reality, at least in our case, is that we had problems with more modern mobiles, from Android 10, however it seemed to work without problem in older versions. The Cordova plugin however behaved well from the start on both older and more modern mobiles. For this and other small details we ended up deciding on the latter for our project.
Some problems detected along the way
Once the plugin was selected and despite having done a fairly exhaustive analysis and various tests, during development we still had to solve some problems. The first of them has to do with the abstraction layers that some manufacturers introduce on Android to customize their devices. It is a fairly well-known topic and is well documented on the Internet. The problems are usually related to battery management, looking for battery savings, what some of these customizations do and what caused our background service to stop. On the Don’t kill my app! website, most of these cases are documented and how to configure the device to prevent battery saving management from canceling this type of process.

Another problem that we had that was not so easy to identify and solve has to do with Android version 10. What happened is that once the application was put in background, points continued to be collected, but after a certain time they stopped collecting, approximately 30 seconds. Upon retrieving the application and having the main focus on the system, then the collection of points continued as if nothing had happened. It was clear that this problem was not the same as the previous one, since the application did not die due to battery management. The real issue is related to the new permission management introduced in Android 10 that allows you to choose whether a permission is granted always or only when the app is in use. This second option is the one that causes problems, since only when the application is in use actually means when the application is visible on the screen, in the foreground, and not when it is running in the background.

Our solution was to explicitly add the andorid:foregroundServiceType=”location” option to the AndroidManifest.xml. In this way we indicate that our app is a location service and always needs access to GPS. The complete line in the AndroidManifest.xml would look like this:
```
< service android:enabled="true" android:exported="false" android:foregroundServiceType="location" android:name="com.marianhello.bgloc.service.LocationServiceImpl" />
```
You also need to explicitly grant ACCESS_BACKGROUND_LOCATION permission as detailed in the documentation.
Final considerations
When choosing a plugin, as well as any development software or library in general, the functionalities it offers us are as important as its evolution and maintenance. In our case, we bet on a plugin that has not been active in its repository for some time, this implies that it is not maintained and future improvements are not expected. On the other hand, the one that fit in these criteria did not offer us the functionality we needed. Perhaps it is an extreme case that we found and that is why we made that decision. In any case, our recommendation is to always take into account the activity of the repository of a solution, seeing that it is and will continue to be maintained over time, that there is a community around it and that it is a safe bet. When this is not possible, you have to consider other things to make the choice and even if it were possible, try to create your own solution.

La entrada Geolocation with GPS in Ionic se publicó primero en iCarto.
08 August 2022
11:00
CARTO Blog: Using Location Intelligence to combat The Great Resignation in Logistics
sur Planet OSGeo

The Great Resignation, The Big Quit or The Big Reshuffle? The employment landscape has been given many names since early 2021, but they all have one thing in common. They a...
2:00
PostGIS Development: PostGIS 3.3.0rc1
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.3.0rc1! Best Served with PostgreSQL 15 beta2 ,GEOS 3.11.0 , and SFCGAL 1.4.1

Lower versions of the aforementioned dependencies will not have all new features.

This release supports PostgreSQL 11-15.

3.3.0rc1
This release is a release candidate of a major release, it includes bug fixes since PostGIS 3.2.2 and new features.
03 August 2022
21:23
GeoTools Team: GeoTools 27.1 Released
sur Planet OSGeo

The GeoTools team is pleased to share the availability GeoTools 27.1 : geotools-27.1-bin.zip geotools-27.1-doc.zip geotools-27.1-userguide.zip geotools-27.1-project.zip Improvements and fixes in this release Bug: GEOT-7182 TransformFeatureSource can lose paging information while transforming query GEOT-7170
19:44
Sean Gillies: Vacation
sur Planet OSGeo

I'm on vacation until Monday, August 8. I hope that you are, too. Apologies in advance for slow response to emails, DMs, and GitHub mentions.
11:00
CARTO Blog: Venue Suitability Analysis for the Eurovision Song Contest with CARTO
sur Planet OSGeo

On the 26th July it was announced that the United Kingdom would be hosting 2023’s Eurovision Song Contest. No fewer than 13 cities are expected to bid for the honor of host...
02 August 2022
18:06
GeoSolutions: GeoSolutions presence at FOSS4G 2022 in Florence
sur Planet OSGeo

You must be logged into the site to view this content.
16:33
Jackie Ng: Announcing: MapGuide Maestro 6.0m11
sur Planet OSGeo

In the interest of getting back into the habit of releasing things again and to line up authoring expectations/experience for another upcoming MapGuide Open Source 4.0 preview release, here's a long overdue release of MapGuide Maestro. Here's a summary of what's changed since the last release (Wow! It really has been 4 years since the last one?)
MapGuide Open Source 4.0 authoring supportThis release of Maestro takes advantage of features/capabilities introduced in the upcoming MapGuide Open Source 4.0. For all these demonstrated features, we assume you have the current Preview 3 release of MGOS 4.0 installed or newer.
A new Layer Definition resource template based on the v4.0.0 schema is now available.

What features/capabilities does this offer? A new toggle option to determine if QUERYMAPFEATURES requests that hit this layer should include bounding box information or not. When bounding box data is not included, client-side viewer tools like zooming to selection will not work due to the lack of this information.

The WMS metadata UI now has support for exposing or hiding the geometry field data from WMS GetFeatureInfo responses.

The basic label style editor finally has the missing support for editing advanced placement settings

MapGuide Open Source 4.0 introduced bulk coordinate transformation capabilities in the mapagent and Maestro will now take advantage of this feature for places in the UI that require transforming coordinates, such as setting the map extents for example

MapGuide Open Source 4.0 now also removes the restriction that you cannot CREATERUNTIMEMAP or MgMap.Create() a Map Definition that links to a XYZ tileset, so the Map Definition editor will no longer throw this warning and block you from linking to a XYZ tile set definition if you are connected to a MGOS 4.0 instance.

Notable UI ChangesYour published WFS and WMS layers are now visible as top-level nodes in the Site Explorer! This allows for quick visual verification that you have correctly applied the appropriate WFS/WMS publishing metadata to your Feature Source or Layer Definition.

These new nodes aren't just for show. For the published WMS layers, there are context menu actions to follow back to the source Layer Definition or for the more exciting option, the ability to preview this WMS layer through the new OpenLayers-driven content representation for WMS layers

The local map viewer component (used for local map previews) now has a panel to show selection attributes

MgCooker is no more. Replaced with MgTileSeederThe venerable MgCooker tool for pre-seeding tilesets in MapGuide has been removed. MgTileSeeder is now the full replacement for MgCooker and is capable of more things than MgCooker (like being a generic XYZ tileset seeder). All existing Maestro UI integrations with the MgCooker tool have also been removed as a result.Maestro API package is now SourceLink-enabledIf you use the Maestro API to build your own MapGuide client applications, the Maestro API nuget package is now built with SourceLink support meaning that when you go to a definition of any class/type of the Maestro API, you will now see the full source code of that class/type instead of the class/type outline from inferred .net metadata.
Similarly, when debugging you can now step into the source code for any method in the Maestro API!

To take advantage of SourceLink requires some small Visual Studio settings changes, which are covered in detail here.Maestro is now a self-contained .net 6.0 windows applicationAside from being able to take advantage of the new capabilities and performance improvements of .net 6.0, the other upside of this move is that this means that you no longer have to download/install the .net Framework first before installing Maestro. Being a self-contained application means that the support files needed to run a .net 6.0 application are now included with the installer itself.

Download MapGuide Maestro
3:24
Sean Gillies: Superior training week eighteen recap
sur Planet OSGeo
I continue to feel fine and finished a hard hill interval workout and some tempo running in week 18. Saturday was a travel day but I did get in a long run out here on Hatteras Island island yesterday. The training volume for the week is a little lower than I planned, but that's okay. I'm happy to be at the seaside with with my family.
- 7 hours, 21 minutes
- 36.9 miles
- 3,071 ft D+
01 August 2022
2:00
GeoServer Team: GeoServer 2.21.1 Release
sur Planet OSGeo
GeoServer 2.21.1 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of the GeoServer 2.21.x series, made in conjunction with GeoTools 27.1 and GeoWebCache 1.21.1.

Thanks to Jody Garnett (GeoCat) for making this release.
Server Status
The server status page has been cleaned up with a few quality of life improvements:
- Units supplied for numbers, such as “7 threads” or “30,000 ms”
- Number of items held in the resource cache is shown, so there is visual feed back when using Clear button.
- Documentation has been updated to cover all the status field descriptions and document the available actions
For more information see Server Status page.

JVM Console
A new JVM Console tab has been added to the server status page allowing a summary of memory use to be reviewed and downloaded, and a summary of active threads to be reviewed and downloaded.

For more information see JVM Console.

Workspace headers for proxy url
A checkbox Use headers for Proxy URL has been added to the workspace page.

This setting an individual workspace use headers for proxy URL (even when the default in global settings has been disabled).
Improvements and Fixes
Improvement:

GEOS-10580 Server status page improvements for status, modules and docs

GEOS-10521 Allow GetFeatureInfo over raster layers to identify both original raster and transformed vectors

GEOS-10514 Better capture catalog configuration issues: layergroup with a misconfigured layer

GEOS-10501 GetMap: support auth headers forwarding to remote SLD urls

GEOS-10495 Request Logger Memory Buffer Limits

GEOS-10489 Add options to LDAP Role Service to configure prefixes and enforce capitalization

GEOS-10464 Improve logging and check for NPEs and other issues in Importer Module

Bug:

GEOS-10584 Enabling logging of request body results in stream closed errors in tomcat environment

GEOS-10570 Deleting a style in a Hazelcast cluster renames the styles directory

GEOS-10553 Importer replace fails with schema mismatch

GEOS-10548 GeoFence layer group handling is inconsistent

GEOS-10546 Invalid time expressions used in WCS 2.0 subset return a code 200 with generic exception

GEOS-10545 Layer Group cache not initialized

GEOS-10539 DescribeLayer typeName is no longer workspace qualified

GEOS-10535 WFS Update request throw NPE on bad namespace

GEOS-10534 a badly formed delete transaction will get a NPE instead of an informative error message

GEOS-10533 Review startup logging INFO and WARN updates

GEOS-10526 Parallel REST API calls failures

GEOS-10522 REST API Failure in @ExceptionHandler No input String specified

GEOS-10518 Partial RELINQUISH_LOG4J_CONTROL regression with WildFly

GEOS-10516 WMS GetCapabilities dimension representations ignores the end attribute

GEOS-10496 Using the REST API to purge NetCDF granules causes a seemingly infinite loop

GEOS-10487 Custom logging configuration not respecting log location setting

GEOS-10468 (virtually) Impossible to turn off “Enable All Statistics” in > Server status > System Status

Tasks:

GEOS-10588 Build structure gs-sec-oauth2-core is duplicated in the reactor

GEOS-10585 Upgrade to Jetty from 9.4.44 to 9.4.48

GEOS-10579 Bump oshi-core from 6.2.0 to 6.2.1

GEOS-10562 Bump oshi-core from 5.8.6 to 6.2.0

GEOS-10551 Refactor commons [httpclient] usage in the WPS module

GEOS-10532 FreemarkerTemplateManager API changes for easier subclassing

GEOS-10529 Use Awaitility to replace waits for condition in tests

GEOS-10525 Centralize and simplify management of common test dependencies
About GeoServer 2.21
Additional information on GeoServer 2.21 series:
Release notes: ( 2.21.1 | 2.21.0 | 2.21-RC )
27 July 2022
11:00
CARTO Blog: Sistema.bio's Story: Optimizing field operations with CARTO
sur Planet OSGeo

The Circular Economy is a cornerstone of sustainability. It’s defined as a model of production and consumption where the lifecycle of materials and products is extended. Th...
26 July 2022
8:00
Lutra consulting: Mergin Maps in MapScaping podcast
sur Planet OSGeo

We talked about Mergin Maps in the MapScaping podcast: QGIS Offline And In The Field

Peter Petrik was a guest in the episode of QGIS Offline And In The Field. He talked with Daniel O’Donohue about collection of spatial data in the field.

Mergin Maps is a field data collection app based on QGIS. It makes field work easy with its simple interface and cloud-based sync. Available on Android, iOS and Windows.
25 July 2022
15:20
Fernando Quadro: Workshop Gratuito: Banco de dados espacial e publicação de mapas na internet
sur Planet OSGeo

Prezados leitores,

A Geocursos irá realizar um workshop que visa apresentar como criar seu banco de dados, importar seus shapefiles e ao final publicá-los em um servidor de mapas.

O evento será 100% online, gratuito e acontecerá nos dias 29, 30, 31 de agosto e 01 de setembro as 20h (horário de Brasília).

As inscrições estão abertas e devem ser realizadas em [https:]]

Veja a programação do Workshop:

Aula 01 (29/AGOSTO): Saiba como criar seu primeiro banco de dados.

Aula 02 (30/AGOSTO): Saiba como importar seus shapefiles para o banco de dados.

Aula 03 (31/AGOSTO): Saiba como publicar seus dados geoespaciais com o GeoServer.

Aula Bônus (01/SETEMBRO): A partir de uma modelagem vamos criar a estrutura de tabelas de um WebGIS.

Ficou com alguma dúvida?
Basta entrar em contato pelo e-mail: workshops@geocursos.com.br

Temos certeza de que será um evento de muito aprendizado!
Nos vemos no Workshop!
24 July 2022
22:23
Sean Gillies: Superior training week seventeen recap
sur Planet OSGeo
After 3 weeks of little training, I'm back at it in week 17. 5 trail runs with plenty of hills.
- 8 hours, 35 minutes
- 38 miles
- 7,493 ft D+
I spent 2:30 riding 30 miles on my bike on top of that. About half riding to and from Pineridge Open Space, but also did a longer ride on Saturday instead of running. I'm going to try to run 55 miles next week and 65 in week 19. That's down quite a bit from my peak volume in the past two years.
18:14
Martin Davis: Polygonal Coverages and Operations in JTS
sur Planet OSGeo
An important concept in spatial data modelling is that of a coverage. A coverage models a two-dimensional region in which every point has a value out of a range (which may be defined over one or a set of attributes). Coverages can be represented in both of the main physical spatial data models: raster and vector. In the raster data model a coverage is represented by a grid of cells with varying values. In the vector data model a coverage is a set of non-overlapping polygons (which usually, but not always, cover a contiguous area).
This post is about the vector data coverage model, which is termed (naturally) a polygonal coverage. These are used to model regions which are occupied by discrete sub-regions with varying sets of attribute values. The sub-regions are modelled by simple polygons. The coverage may contain gaps between polygons, and may cover multiple disjoint areas. The essential characteristics are:
- polygon interiors do not overlap
- the common boundary of adjacent polygons has the same set of vertices in both polygons.
There are many types of data which are naturally modelled by polygonal coverages. Classic examples include:
- Man-made boundaries
- Natural boundaries
A polygonal coverage of regions of FranceTopological and Discrete Polygonal Coverages
There are two ways to represent polygonal coverages: as a topological data structure, or as a set of discrete polygons. A coverage topology consists of linked faces, edges and nodes. The edges between two nodes form the shared boundary between two faces. The coverage polygons can be reconstituted from the edges delimiting each face. The discrete polygon representation is simpler, and aligns better with the OGC Simple Features model. It is simply a collection of polygons which satisfy the coverage validity criteria given above.Most common spatial data formats support only a discrete polygon model, and many coverage datasets are provided in this form. However, the lack of inherent topology means that datasets must be carefully constructed to ensure they have valid coverage topology. In fact, many available datasets contain coverage invalidities. A current focus of JTS development is to provide algorithms to detect this situation and provide the locations where the polygons fail to form a valid coverage.Polygonal Coverage Operations
Operations which can be performed on polygonal coverages include:
- Validation - check that a set of discrete polygons forms a valid coverage
- Gap Detection - check if a polygonal coverage contains narrow gaps (using a given distance tolerance)
- Cleaning - fix errors such as gaps, overlaps and slivers in a polygonal dataset to ensure that it forms a clean, valid coverage
- Simplification - simplify (generalize) polygon boundary linework, ensuring coverage topology is preserved
- Precision Reduction - reduce precision of polygon coordinates, ensuring coverage topology is preserved
- Union - merge all or portions of the coverage polygons into a single polygon (or multipolygon, if the input contains disjoint regions)
- Overlay - compute the intersection of two coverages, producing a coverage of resultant polygons
Implementing polygonal coverage operations is a current focus for development in the JTS Topology Suite. Since most operations require a valid coverage as input, the first goal is to provide Coverage Validation. Cleaning and Simplification are priority targets as well. Coverage Union is already available, as is Overlay (in a slightly sub-optimal way). In addition, a Topology data structure will be provided to support the edge-node representation. (Yes, the Topology Suite will provide topology at last!). Stay tuned for further blog posts as functionality is rolled out.
As usual, the coverage algorithms developed in JTS will be ported to GEOS, and will thus be available to downstream projects like PostGIS.
5:07
Sean Gillies: Modern broadband
sur Planet OSGeo

This week I became a Fort Collins municipal internet utility customer. 1 Gbps up and down for $60 a month.

Buh-bye coaxial cable

I called the cable company on Tuesday to cancel and was told that they were going to refund me $25 in the process of squaring up my account. Sweet! Then today I got an email announcing my next month's bill. The cable company is terrible at their business. I wonder how many times I will have to cancel my account before it sticks?

This is a great upgrade. The house my family was renting in France got fiber in 2017. I'm just saying.
23 July 2022
23:36
Sean Gillies: Superior training weeks fourteen, fifteen, and sixteen recap
sur Planet OSGeo
I had some health troubles during weeks 14-16 and got very little training done while feeling generally crappy and worried. On June 16 (end of week 13) I went for a 20 mile run in the hills and struggled on the climbs. I was unusually out of breath and after I finished I was a bit dizzy. The next day I was mildly feverish and I continued to have an elevated temperature and noticeable lethargy during my run on Tuesday, the 28th. I took a COVID test and it was negative. On the 29th I went out for an interval workout and quit after my warmup. I felt dizzy, achy, without energy, and was seeing a heart rate on my Garmin watch that conflicted with what I was feeling: anomalously low at times. I took another COVID test, again negative. Friday, July 1, I had a virtual visit with my doctor, who recommended a PCR test for flu and COVID and some blood work. The PCR test was negative and the lab report said I was normal on all counts. About this time I became aware of twitching in my chest, which I noticed most when I was laying down before falling asleep, or in the middle of the night. At first I chalked this up to anxiety, but after several days of no relief and some very confusing heart rate measurements on my run on July 5 (after which I joked "Getting confusing HR signals from my watch. Either it or I am about to die.") I got a live, in-person visit with my doctor and a ECG, which revealed premature atrial and ventricular complexes (PACs and PVCs). My heart really was malfunctioning.

I got fitted with a wearable ECG to collect more data and had a generally crappy week of heart twitches, poor sleep, anxiety, and no running while waiting to get a echo scan of my heart and a consultation with a cardiologist. In week 16 (starting July 11), I began to feel a little better. I found that I could hike and run at a super easy pace and not feel terrible, so I began to treat it like an ordinary recovery week (every 4th week of my training blocks are recovery weeks). On July 14 I drove to the UC Health hospital in Greeley, which has some extra capacity, and got an echo scan (sonogram) of my heart. The initial assessment said that I had an enlarged right ventricle. That didn't sound good. My heart palpitations continued to subside, but I still had five stressful days of waiting before my cardiology appointment on Tuesday of this week (week 17). The cardiologist disagreed with the initial assessment of my echo scan and didn't recommend any other scans. I don't have an enlarged ventricle. Other than the PACs and PVCs, which continue to diminish, my heart is in good shape. I had a treadmill stress test on Friday and passed. We measured only a few PVCs during the test.

This week I started running a little harder and have been feeling fine. It seems like I only had a temporary episode of premature contractions that were likely triggered by an unknown virus. My watch's measurement of my heart rate is back to normal, too. Neither it, nor I am going to die soon.

Here are the numbers for weeks 14-16.

Week 14:
- 3 hours, 11 minutes
- 15.1 miles
- 3,428 ft D+
Week 15:
- 1 hour, 57 minutes
- 9.6 miles
- 1,056 ft D+
Week 16:
- 3 hours, 45 minutes
- 18.1 miles
- 1,631 ft D+
I had been aiming for 120 miles of running and 20,000 feet of climbing in weeks 14 and 15 and got nowhere near that. I missed two big weeks of training, but I'm trying not to sweat about that. I've had enough worrying in the past three weeks, I don't need to add worry about training to my problems. I'm still on track to run the Superior 50 in 7 weeks.
2:00
PostGIS Development: PostGIS 3.2.2
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.2.2! This release works for PostgreSQL 9.6-15.

3.2.2
This release is a bug fix release, addressing issues found in the previous 3.2 releases.
21 July 2022
11:00
CARTO Blog: From PostgreSQL to the Cloud: Setting up a Spatial Data Infrastructure in BigQuery
sur Planet OSGeo

PostgreSQL is one of the most popular open source relational database systems available with + 30 years in development, 1,500,000 lines of submitted code and more than 650 ...
20 July 2022
14:50
PostGIS Development: PostGIS 3.1.6
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.1.6! This release works for PostgreSQL 9.6-14.

3.1.6
This release is a bug fix release, addressing issues found in the previous 3.1 releases.
2:00
PostGIS Development: PostGIS 3.0.6
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.0.6. This release works for PostgreSQL 9.5-13.

3.0.6
19 July 2022
14:43
PostGIS Development: PostGIS 2.5.7
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 2.5.7!

2.5.7
This release is a bug fix release, addressing issues found in the previous 2.5 releases.
11:00
CARTO Blog: COVID, mapped: The analytics behind an epidemic
sur Planet OSGeo

One of the defining elements of the COVID epidemic has been how quickly the situation seems to change. One moment things feel positive with the number of infections slowing...
13 July 2022
16:37
GeoSolutions: GeoNode Release 4.0-RC1
sur Planet OSGeo

You must be logged into the site to view this content.
11:00
CARTO Blog: Retail Centre Data Exploration
sur Planet OSGeo

Introduction If we asked you to picture a UK Retail Centre, what would come to mind? A bustling city centre boulevard or a quaint village high street? A sprawling out-of-to...
2:00
EOX' blog: How EO expertise powers agri-monitoring decisions (Part 3)
sur Planet OSGeo

This blog post is the third part of a multi-post series. Introduction The first and second parts of this blog post series introduced the Area Monitoring System (AMS) and the EO-WIDGET project. Furthermore, it covered user interface components, APIs (Application Programming Interface) and backend ser ...
2:00
PostGIS Development: PostGIS 3.3.0beta2
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.3.0beta2! Best Served with PostgreSQL 15 Beta2 ,GEOS 3.11.0 , and SFCGAL 1.4.1

Lower versions of the aforementioned dependencies will not have all new features.

This release supports PostgreSQL 11-15.

3.3.0beta2
This release is a beta of a major release, it includes bug fixes since PostGIS 3.2.1 and new features.
09 July 2022
20:58
Free and Open Source GIS Ramblings: Official Austrian basemap and cadastre vector tiles
sur Planet OSGeo
The BEV (Austrian Bundesamt für Eich- und Vermessungswesen) has recently published the Austrian cadastre as open data:

#BundesamtfuerEichundVermessungswesen presents the online service of the #austrian #cadastre! That is HUGE news for the #geospatial #geoinfomatics community! #GISalzburg22 @GI_Salzburg pic.twitter.com/XT69l5KXRn
— Johannes Scholz (@Joe_GISc) July 6, 2022
The URLs for vector tiles and styles can be found on [https:]] under Guide – External
The vector tile URL is:
```
https://kataster.bev.gv.at/tiles/{kataster | symbole}/{z}/{x}/{y}.pbf
```
There are 4 different style variations:
```
https://kataster.bev.gv.at/styles/{kataster | symbole}/style_{vermv | ortho | basic | gis}.json
```
When configuring the vector tiles in QGIS, we specify the desired tile and style URLs, for example:

For example, this is the “gis” style:

And this is the “basic” style:

The second vector tile source I want to mention is basemap.at. It has been around for a while, however, early versions suffered from a couple of issues that have now been resolved.

The basemap.at project provides extensive documentation on how to use the dataset in QGIS and other GIS, including manuals and sample projects:

Here’s the basic configuration: make sure to set the max zoom level to 16, otherwise, the map will not be rendered when you zoom in too far.

The level of detail is pretty impressive, even if it cannot quite keep up with the basemap raster tiles:

Vector tile details at Resselpark, Vienna Raster basemap details at Resselpark, Vienna
08 July 2022
11:00
CARTO Blog: Super Charged Site Selection for Electric Vehicles
sur Planet OSGeo

Electric vehicles are becoming one of the true success stories in sustainable transport, both environmentally and commercially. Their popularity has grown exponentially, wi...
07 July 2022
11:00
CARTO Blog: What's New in CARTO - Q2 2022
sur Planet OSGeo

As we approach the midpoint of the year, it is time for us to share with you some of the exciting new enhancements we have developed for the most recent release of the CART...
06 July 2022
23:30
iCarto Blog: Sub-basin delimitation process using QGIS
sur Planet OSGeo
This article is part of our series on Delimitation of hydrographic sub-basins using QGIS and a DEM:
1. Delimitation of hydrographic sub-basins using QGIS and a DEM
2. Digital elevation models for hydrological studies
3. Technical criteria for the delimitation of sub-basins
4. Sub-basin delimitation process using QGIS (This post)
In this article we are going to explain the process to delimit the river sub-basins of a certain region using QGIS and a DEM. In this case the region is the entire Republic of Mozambique.

The starting data we need is a mosaic of Digital Elevation Models (DEMs) of the entire area and the watershed layer. As we commented in the previous articles of the series, we will use the NASADEM HGT mosaics (here we explain how to download them) and the basin layer elaborated by GEAMA.
Create single DEM (Mosaic)
The first step is the union of the DEM mosaics to create a single DEM for all of Mozambique.

QGIS provides us with different options for joining raster files. In this case we are going to use the tool “Merge”. To do this, select “Raster” from the menu, display the “Miscellaneous” options and click “Merge”.

In the pop-up window we add all the input layers, that is, all the DEMs downloaded from the web of the area in which we are going to work. We give a path and a name for the output file, check the option “Open the output file after running the algorithm” and execute.
DEM reprojection
The merged DEM is in the WGS 84 Geographic Coordinate System (EPSG:4326). We reproject the DEM to a Projected Coordinate System. In our case to WGS 84 / UTM zone 37S (EPSG:32737). To reproject the DEM from the menu we select “Raster”, then “Projections” and “Warp (reproject)”.

In the input layer we select the combined DEM and indicate both the source CRS and the target CRS. We also indicate a path and a name for the output file and run the algorithm.
DEM clipping
To reduce the processing computation of the algorithms that we will use in the following steps, we will now clip the DEM per each river basin. Another reason for making these cuts is the difference in sizes and shapes of the basins that we are going to analyze. Better results will be obtained by analyzing each basin separately in order to adjust the parameters of the algorithms to each particular case instead of using the same parameters for all of Mozambique.

We create the masks for each basin from the basins layer. In the following image you can see the DEM in the background, in white the administrative limit of Mozambique and in blue the mask of the Lurio river basin.

Next, we clip the DEM with each created mask. To clip the DEM, in the main menu we select “Raster”, then “Extraction” and “Clip Raster by Mask Layer”.

In the pop-up window we select the reprojected DEM on the input layer and the basin mask on the mask layer. Also, so that the crop fits exactly to the edge of the basin and so that no black area is visible, we will specify a value for “no data”, for example -9999. Finally, we mark the following two options:
- Match the extent of the clipped raster to the extent of the mask layer.
- Keep resolution of input raster.
We specify the path and name for the output file and run the algorithm.

Perform this process for all basins. Batch processing can be used for this instead of doing it one by one.
Filling depressions
Although the latest versions of the DEMs are already processed with different corrections and gap filling, they may still contain artifacts such as depressions. Artifacts must be removed before using a DEM in hydrologic analysis. There are several algorithms for filling gaps (GDAL, GRASS, SAGA, …). The incorporation of the GRASS hydrological toolset in QGIS is very useful. We will therefore use the GRASS algorithm both for this step and for others that we will see later.

To fill depressions we wil use the processing toolboox, if it is not visible on the right side of the QGIS window, it can be enabled from the main menu, by select “Processing” and “Toolbox”.

In the toolbox find or type the following algorithm: r.fill.dir. In the dialog window select as input (Elevation) the clipped DEM and uncheck Flow direction and Problem areas. We are only interested in obtaining the DEM without depressions. Indicate the path and name for the output file and execute.

This geoprocess can take a long time to finish depending on the size of the raster and the power of the computer. Perform this geoprocess for all basins. Batch processing can be used for this instead of doing it one by one.
Drainage direction, accumulated flow, stream segments and sub-basins
Now that we have a corrected DEM, the next step is to calculate the drainage directions, accumulated flow, stream segments and sub-basins. To do this we look for the following algorithm in the toolbox: r.watershed

In the dialog window we select the corrected raster of the basin and establish the most appropriate “Minimum size of exterior watershed basin” for each case.

Because of the wide difference between the size of some basins and others, it is necessary to play with the “Minimum size of exterior watershed basin” to obtain the optimal results for each of them.

An average size can be obtained by reviewing the characteristics of the raster. The pixel size of the raster is 30x30m, so the “Minimum size of exterior watershed basin” must be at least 333,333.33 pixels, approximating 300,000 pixels.

But, in many cases, it is decided to establish 100,000 or less to solve some problems detected in some flat areas or mouths. Also check the following two options:
- Enable Single Flow Direction (D8) flow
- Allow only horizontal and vertical flow of water
Also check the boxes that can be seen in the following image, in addition to indicating the paths and names of the output files and execute the algorithm.

We thus obtain for each basin:
- Accumulated flow
- Drainage direction
- Sub-basins
- Stream segments
The only layer we are going to work on is the sub-basin layer, the rest are calculated to serve as support for small manual adjustments that we will make later.
Transform to vector layer
Once we have the sub-basins layer, the next step is to transform this raster layer into a vector layer. To do this we are going to look for the following geoprocess in the toolbox: r.to.vect. In the window, select the sub-basins layer as the input raster layer.

Also select these options and run:
- Feature type: area
- Smooth corners of area features
- v.out.ogr output type: area
Review and manual adjustments
Once we have the vector layer of sub-basins we have to review the result, join the necessary polygons to have only the sub-basins that meet the agreed criteria mentioned in the previous article and make small manual corrections where necessary.

The union of the polygons is also necessary because the algorithm creates sub-basins of tributaries that are not direct to the main river, that is, tributaries of a tributary of the main river. In this way we solve the problem.

These algorithms work well in sloping areas, but in flat areas they can give undesirable results, and it is necessary to review them. For example, in coastal areas with very flat basins, a more detailed review and adjustments to sub-basin boundaries were required based on other information such as drainage directions, rivers, etc.
Smoothing and simplification
When vectorizing a raster, the edges of the polygons are generated following the shape of the pixels, for this reason it is necessary to smooth them.

This leads to another problem, which is that smoothing creates many vertices that make the layer size increase quite a bit. To avoid this, after smoothing you can also do a simplification.

Choosing the appropriate parameters, smoothing and simplification are carried out without practically losing definition in the delimitation of the sub-basins. In the image below you can see the edges of the sub-basins before and after (red) smoothing and simplifying.
Sub-basins merge
Since we have created a sub-basin layer for each basin, we perform a vector layer union to create a single sub-basin layer for the entire country: mergevectorlayers.

In the dialog window we select all the sub-basin layers for input layers, we specify the Coordinate Reference System, the path and the name of the output file and we execute.
Geometric and topological checks and corrections
Once we have the desired sub-basin layer, overlaps, duplicates, gaps, invalid geometries, etc. must be checked and corrected.

This can be done with plugins (Manage and install plugins)
- Geometry Checker
- Topology Checker
Modify attribute table as needed
In addition to the geometry of the sub-basins, we must also add the desired attributes and order the attribute table as desired. Some examples of useful attributes in a sub-basin layer are the name of the river, the area, length of the main river or the basin to which it belongs.
Final Results
Following these steps we obtain our layer of sub-basins.

With this article we close our series on the delimitation of sub-basins. Did you find them interesting? Do you use other techniques? Need help? Get in touch with us or write to us on Twitter.

La entrada Sub-basin delimitation process using QGIS se publicó primero en iCarto.
05 July 2022
15:26
GeoSolutions: Envitia is joining our partnership program
sur Planet OSGeo

You must be logged into the site to view this content.
11:00
CARTO Blog: Using Spatial Analysis for 5G Rollout
sur Planet OSGeo

5G has been the talk of the town (okay, world) for years. Afterall, from a bird’s eye view, who wouldn’t be excited to regularly experience faster downloads and less latenc...
04 July 2022
2:00
Ian Turton's Blog: Some interesting books I've read recently
sur Planet OSGeo

Interesting Books
This is a short post to let you know about some interesting books I’ve recently finished that you might find interesting.
The Atlas of Unusual Borders
Or to give it its full title The Atlas of Unusual Borders: Discover intriguing boundaries, territories and geographical curiosities by Zoran Nikolic. I blame Barry Rowlingson who threw a link to it into a twitter discussion on borders, so I had to buy it. And, to be honest I’m very happy I did, it is an atlas of “interesting” border enclaves and other geographic oddities. So if like me you’ve ever wondered why Belgium has some many enclaves (and exclaves, and counter-enclaves) (or you just wondered what those are) this is the book that you need in your library. It also answers questions such as which capital city is a ghost town too? Plymouth, Montserrat to save you trying to look it up. This is a fascinating book with nearly every page leading to a “I didn’t know that”. My only minor quibble with it is the colour scheme of the maps, I really struggle with maps where the land is blue and the sea is grey, and with the highlights as yellow it is probably not a book for anyone with blue/yellow colour blindness.
git commit murder and git sync murder
This pair of books by Michael Warren Lucas, are murder mysteries set at technical conferences. If you have ever been to an open source conference (such as FOSS4G) then you will recognise many of the characters in these books. In the first book set at the (fictional) BSDNorth conference our hero Dale Whitehead sets out to give a technical talk but is sidetracked by the death of his room mate (and the weight of his laptop bag, which he seems to never get around to clearing out). I found this a very believable account of free software development, technical conferences and Unix hackers, though while I may have considered killing a user I’ve never actually done it!

git sync murder sees Dale forced to attend another conference despite his promise to himself to never leave his apartment ever again. Once again, things quickly spin out of his control and that laptop bag is no lighter than last time. I loved both these books and can thoroughly recommend them if you are at all into whodunits.

Finally, if you enjoy conferences/convention books then I’ll throw in Charlie Stross’ Dechlorinating the Moderator which I read in his collected Toast volume which reports from a futuristic 2018 Particulate 7: HiNRG & B-OND conference, for a fun short story.
03 July 2022
2:00
PostGIS Development: PostGIS 3.3.0beta1
sur Planet OSGeo
The PostGIS Team is pleased to release PostGIS 3.3.0beta1! Best Served with PostgreSQL 15 Beta2 and GEOS 3.11.0.

This release supports PostgreSQL 11-15.

3.3.0beta1
This release is a beta of a major release, it includes bug fixes since PostGIS 3.2.1 and new features.
02 July 2022
22:33
Sean Gillies: Korean-style sloppy joe
sur Planet OSGeo

I had leftover ground beef and lamb from making burgers last night and turned that into no-recipe Korean-style sloppy joes for lunch on the deck with Ruth and Bea. I started by making a generous sofrito of onion, celery, yellow bell pepper, garlic, and ginger in a cast-iron skillet. When that had softened and started to color, I pushed it to one side and browned the meat (half a pound of beef, half a pound of lamb), stirring all of it together when the meat had cooked through and crisped a bit. For the sauce, I stirred in three tablespoons of vegetarian oyster sauce, a splash of black vinegar, a teaspoon of sesame oil, a quarter cup of gochujang, a teaspoon of salt, a tablespoon of sugar, half a teaspoon of black pepper, and half a cup of water. When it had reduced, I checked the salt, added a bit more, and then spooned it onto toasted buns. Sesame seeds, green onion (from my garden), and cucumbers dressed with rice wine vinegar provided the finishing touch.

Sloppy joe on a toasted brioche bun with quick pickles and watermelon

I like the traditional sloppy joe, too. But I like it even more with ginger and sesame oil. The mild, sweet funkiness of gochujang goes very well with lamb.
01 July 2022
11:34
GeoTools Team: GeoTools 26.5 released
sur Planet OSGeo

The GeoTools team is pleased to share the availability GeoTools 26.5 : geotools-26.5-bin.zip geotools-26.5-doc.zip geotools-26.5-userguide.zip geotools-26.5-project.zip This release is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.20.5Fixes and improvementsGrid aggregation in the ElasticSearch community module has been improvedFix aggregate queries
11:00
CARTO Blog: Analyzing Sentiment & Footfall in Post-COVID Berlin
sur Planet OSGeo

The Data Appeal Company’s Hannah Babineau - International Partnerships and Marketing Manager - guest blogs for CARTO!
2:00
GeoServer Team: GeoServer 2.20.5 Released
sur Planet OSGeo
We are happy to announce GeoServer 2.20.5 release is available with downloads (bin, war, windows), along with docs and extensions.

This is a maintenance release of the 2.20.x series recommended for production systems. This release was made in conjunction with GeoTools 26.5 and GeoWebCache 1.20.3.
Improvements and Fixes
- The request logger is now configurable from the UI (form the “Global settings” panel),
- Importer improvements to support REPLACE mode on raster layers (in addition to the existing support for vector ones).
- The KML-PPIO module has graduated to extension (allows KML encoding of feature collections in WPS processes). It’s now included in the WPS plugin download.
- WPS fetching of remote inputs can be disabled.
- Allow controlling usage of headers in proxy base URL expansion at the workspace level.
For the full list of fixes and improvements, see 2.20.5 release notes.
About GeoServer 2.20
Additional information on GeoServer 2.20 series:
Release notes: ( 2.20.2 | 2.20.1 | 2.20.0 | 2.20-RC )
29 June 2022
12:41
Stefano Costa: An updated IOSA website
sur Planet OSGeo

Today marks the 18th anniversary of IOSA, Internet and Open Source in Archaeology, the project/working group that I got started with Giovanni Luca Pesce in 2004. Luca Bianconi would join a few years later and give a substantial contribution to the development of the oldest active software project under the IOSA umbrella, Total Open Station.

It seems an appropriate time to announce that the iosa.it website is now available with a revamped look, and has become the single container for all content previously available in separate websites, such as the Quantitative Archaeology Wiki.

There will be no substantial improvements to the website, but I consider it a “living archive” so I’m going to add more content as I find it and have the time to organize it properly.

Please find it at [https:]] as usual, and browse like it’s 2004 again.
11:00
CARTO Blog: Cost of Living Crisis: Location Intelligence for Energy Efficiency
sur Planet OSGeo

Read any news website in 2022 and there’s one phrase you can’t escape; the “cost of living crisis.” In the UK, living costs have been rising at their fastest rate in 30 yea...
10:17
iCarto Blog: Technical criteria for the delimitation of sub-basins
sur Planet OSGeo
This article is part of our series on Delimitation of hydrographic sub-basins using QGIS and a DEM:
1. Delimitation of hydrographic sub-basins using QGIS and a DEM
2. Digital elevation models for hydrological studies
3. Technical criteria for the delimitation of sub-basins (This post)
4. Sub-basin delimitation process using QGIS
To delimit the hydrographic sub-basins of a country, it is necessary to establish a series of criteria that allow uniform results to be obtained throughout the study area.
Basic criteria
In this case, the following basic criteria were agreed with the Regional Water Administrations (ARAs):
- Sub-basins are not delimited in basins with an area of less than 3500 km2.
- Only the areas of the direct tributaries of the main river, which have a length equal to or greater than 55 km, are delimited as sub-basins.
- Only the areas of the direct tributaries of the main river that have an area equal to or greater than 300 km2are delimited as sub-basins.
Other criteria
In addition to the sub-basins resulting from the application of the basic criteria, the following areas were delimited for each river basin:
- Source area of the main river. In the case of transboundary rivers, that is, rivers that cross two or more states, the source may be outside the study area. In the case of Mozambique, there are several examples in which the source of the main river of the river basin is in another country (Zambezi, Limpopo, Incomati…). In these cases this area was not delimited.
- Area of the mouth of the main river.
- Area that includes the rest of the sub-basins, which do not meet the basic criteria, normally attached to the bed of the main river.
Exceptions
It was decided to delimit some sub-basins that did not meet the previous basic criteria and that we will call exceptions because they are sub-basins considered of great hydrological importance by the ARAs. An example of this is the delimitation of the sub-basins of the Umbelúzi River. Although the area of this basin is less than 3500 km2, it is of great hydrological importance because it contains a high percentage of large farms, with a very high demand for water.

In the next article, the last of the series, we will see how to do the whole process using QGIS.

La entrada Technical criteria for the delimitation of sub-basins se publicó primero en iCarto.
28 June 2022
18:10
GeoSolutions: OGC Disaster Pilot and GeoSolutions – Powering decision makers with the right information
sur Planet OSGeo

You must be logged into the site to view this content.
27 June 2022
11:00
CARTO Blog: How Yale Climate Connections Uses Spatial Visualization for Community Engagement
sur Planet OSGeo

What is the first thing that you do when you open a web map? For most of us, we scroll and scroll until we’re zoomed right in to exactly where we live to find out what’s ha...
5:56
Sean Gillies: Superior training week thirteen recap
sur Planet OSGeo
Week thirteen was my biggest week yet. I did a non-hilly speed workout on the dirt trails of Pineridge Natural Area, an uphill workout on Towers Trail, a tempo run at Maxwell, and two long runs on the weekend. I didn't feel great Friday, Saturday, or Sunday, but exceptionally nice running weather helped me survive the weekend miles.
- 12 hours, 15 minutes
- 57.0 miles
- 7,664 ft D+
I didn't take any photos during my runs this week. I'll try to do better this week.
24 June 2022
15:40
QGIS Blog: QGIS 3.26 Buenos Aires is released!
sur Planet OSGeo

We are pleased to announce the release of QGIS 3.26 ‘Buenos Aires’!

Installers for all supported operating systems are already out. QGIS 3.26 comes with tons of new features, as you can see in our visual changelog. QGIS 3.26 Buenos Aires is named after last year’s FOSS4G host city.

We would like to thank the developers, documenters, testers and all the many folks out there who volunteer their time and effort (or fund people to do so). From the QGIS community we hope you enjoy this release! If you wish to donate time, money or otherwise get involved in making QGIS more awesome, please wander along to qgis.org and lend a hand!

QGIS is supported by donors and sustaining members. A current list of donors who have made financial contributions large and small to the project can be seen on our donors list. If you would like to become a sustaining member, please visit our page for sustaining members for details. Your support helps us fund our six monthly developer meetings, maintain project infrastructure and fund bug fixing efforts.

QGIS is Free software and you are under no obligation to pay anything to use it – in fact we want to encourage people far and wide to use it regardless of what your financial or social status is – we believe empowering people with spatial decision making tools will result in a better society for all of humanity.
23 June 2022
22:56
longwayaround.org.uk: Web Mercator OS Vector Tile API in OpenLayers
sur Planet OSGeo

Adding a Vector Tile layer of Ordnance Survey data from the OS Data Hub to an OpenLayers map in Web Mercator is a little more work than expected as the JSON style document and associated JSON source document include paths for the default British National Grid tiles. The following is …

Skip to page: 1 2 3 ... 19

← Open Geospatial Consortium (OGC) Parcell'air →

Communauté	Ressources	L'emploi	Le marché	L'association	Fils RSS
Forum Blogs Wiki Planet Carte des membres Sites amis	Agenda Biblio Netvibes Fiches AMO-CNIG Paris PCGIS Téléchargements	Offres d'emploi Banque de CV Carte des CV Formations Démarche Métiers	Geo-Entreprises Geo-Communiqué Appels d'offres	L'association Qui sommes-nous ? Nous aider Bienfaiteurs Partenaires Historique Statuts	Tout le site Job Géomatique Services GeoBlogs ...	Faire un don Mentions légales

Source	British Ordnance Survey OpenData
Dataset	Boundary-Line
File	unitary_electoral_division_region.shp

Source	Hamburg Open Data Platform
Dataset	VerwaltungsEinheit (Administrative Units)

Source	City of Vancouver
Dataset	Zoning Districts

Le portail francophone de la géomatique

Feeds

Planet OSGeo