XIO

xWire

Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.

osm2pgsql

osm2pgsql

Happy Birthday osm2pgsql!

Today 20 years ago Jon Burgess committed the first version of osm2pgsql to the repository. Since then osm2pgsql has been improved in many ways by many people. Originally started to enable rendering of OSM data into raster tiles, it has now many more uses. It is still the software behind many of the most important (raster or vector) OSM maps, especially when minutely updates of the data are needed. If you want to know more about the history of the project, our website has an overview. We also…

Release 2.3.1

This is a bugfix release which fixes a segfault that may be encountered when using the new diff expire on tables with multiple expire outputs. It also fixes installation of man pages (thanks @sebastic).

Release 2.3.0

We are happy to announce the release of osm2pgsql version 2.3.0. It contains major changes to the tile expire, a new style tester script and many more changes. Expire Quick and efficient expire and re-rendering of tiles with changed data is important for OSM. Historically osm2pgsql didn’t do a great job figuring out which tiles are affected by some change. Quite some work went into this release to improve that situation. Most importantly polygons are now not expired by bounding box any more but…

NGI0 grant for osm2pgsql

The amount of data in OSM is climbing continually, and therefore the memory and disk requirements of osm2pgsql have risen as well. To address this issue we have applied for and won a grant from the NGI0 Commons Fund. In this project we want to reduce the memory and disk usage of osm2pgsql by implementing more efficient storage formats, specifically for “intermediate” data used while processing, often called the “middle”. We are tentatively calling this CODA, the Compact OpenStreetMap Data…

OSM-Carto switched to flex output

Nearly six years ago we introduced the “flex” output in osm2pgsql version 1.3.0 and then improved it over the years adding more and more functionality. About a month ago OpenStreetMap-Carto, the iconic OSM map style switched to using the “flex” output in version 6.0.0. And now the OSM Foundation has finished their gradual rollout of the new version. So the most important user of osm2pgsql doesn’t need the old “pgsql” output any more. That switch has been eagerly awaited by the osm2pgsql…

Test Your Styles with the New Style Tester

Styles (configurations) for osm2pgsql are written in the Lua programming language. And they are becoming more complex. Users have been asking for a long time for some way of testing those styles to help with writing and debugging the Lua code. We now have a solution for you. We have had tests for osm2pgsql, the software, for a long time. This includes tests that run osm2pgsql with certain inputs and parameters and check that osm2pgsql produces the correct output, including checks that make sure…

Release 2.2.0

We are excited to publish version 2.2.0 of osm2pgsql. This release adds two powerful building blocks that can be used to implement all sorts of new features. The new “Locators” and the “deleted callbacks” features seem simple by themselves, but they can be used as basis for many features that have been requested for years. New Locator feature This release introduces a new feature: Locators. They help with a common problem, namely how to quickly find out in which region an OSM object is. The…

Updated Contributor Docs

Over the last few weeks we have updated and overhauled the “Contributing” section on the osm2pgsql website. We want to make it easier for users and contributors to understand what our plans are for osm2pgsql, what are the open issues and what you can do to help. The new Contributing Overview no longer focuses on coding because there are so many more ways to help the project than with code. Whether you are a user, have ideas on improving the documentation, or want to show your use case,…

Achievement unlocked: Zero Warnings

New code will probably have some errors, the compiler finds some of them and refuses to produce the final program. So far so good. But code also contains lots of issues that are not outright errors, they just look “suspicious” to the compiler in one way or another. Some of them turn out to be actual errors, but sometimes the code is totally okay in the specific context. The compiler can’t tell for sure, so it emits a warning and keeps going. Different compilers and different versions of those…

Release 2.1.1

This is a bug fix release which contains the following: refuse to update database when the flatnode is missing fix regression where writing to tables without a managed id column was not possible

Release 2.1.0

Today we released version 2.1.0, a bugfix and maintenance release. The main visible change is that osm2pgsql now works better together with connection poolers and similar database middleware: prepared statements now use protocol level prepare instead of PREPARE SQL commands and there is a new option to explicitly create a primary key on flex tables. Other fixes and features: check flat node file format for forwards compatibility to prepare for future changes of the flatnode file format fix…