Tags: mucula/osm2pgsql
Tags
Release 1.3.0 This release introduces the new "flex" output. It allows a more flexible definition of output tables and columns. It also adds a second stage of processing which makes it possible to get information from relations to their members, allowing, for instance, to render tags from bicycle route relations on their member ways. The "flex" output is configured through Lua scripts. The flex output is currently still marked as experimental, because it is new and we want to collect feedback from the community before finalizing the API. But it already works well and users are encouraged to try it out. Some new features are only or will only be available in the flex output and we expect that it will replace the other outputs in the long term. Some features have been marked as deprecated: * The "multi" output will be removed in a future version of osm2pgsql. If you are using the multi output, switch to the flex output now and tell us if you have any problems. * When the input file uses negative OSM object IDs a warning is now generated. Negative IDs never worked correctly for all use cases. Future versions of osm2pgsql will not allow negative IDs at all. Use "osmium renumber" to get rid of the negative IDs. * Input files that are not ordered generate a warning. Future versions of osm2pgsql will not work any more with unordered files. If you have unordered files use "osmium sort" to order them. Further changes: * The pgsql output now looks for lua script relative to the `style.json` file. This is a breaking change. Users might have to change the file names of their lua scripts in the style files. * Use the fmt library for formatting strings now instead of a mixture of `boost::format` and hand-written mechanisms. A version of fmt is included in the contrib directory. * Make PROJ library optional. If the proj library cannot be found by cmake, do not offer the option to use arbitrary projections. Only WGS84 and WebMercator are supported then. * Don't use `ST_GeoHash` for ordering tables by geometry on Postgis >= 2.4. Instead use the default ordering which works better now. * Fix: Always print correct relations count and more correct count per seconds when showing processing stats. * Fix: If a function run in the thread pool throws an exception, this exception was never "collected", it was silently ignored. This meant that some errors, especially in communication with the database, were not detected correctly. * The dependency management, the part of the code which tracks which changes in the OSM data trigger which changes in the outputs, was reorganized making in much cleaner and removing the last remnants of code written to support "old style" multipolygons. * Tests have been moved to the Catch framework, extended and the regression tests have been reorganised, so they can run independently of each other. * A lot of code was cleaned up, modernized, made more robust, and sometimes removed.
Release 1.2.0 This is a bug fix release. Changes include - limit number of buffers queued for COPYing to PostgreSQL to avoid out-of-memory issues when importing data in slim mode without the flatnode option - reduce default number of threads to 4 to avoid running out of PostgreSQL connections - fix import failures when importing large values into int4 columns
Release 1.0.0 This release finally drops support for old-style multipolygons. Doing so allowed a major overhaul of the processing pipeline. Imports are now entirely done in the first processing stage. The second, much slower processing stage is only needed when updating existing databases. Data is entirely streamed into the database using COPY, which reduces the number of database connections needed. Other major changes include - better error handling in Lua backend - process all OSM objects again when extra attributes are requested - enable running tests in pg_virtualenv - add support for configurable Gazetteer style - allow to disable RAM node cache with -C 0
Merge pull request osm2pgsql-dev#948 from lonvia/update-libosmium Update libosmium to 2.15.2 and protozero to 1.6.8
Release 0.96.0 This release fixes a number of bugs introduced with the switch to libosmium and brings a couple of improvements in the build system. Changes include - memory for caches and flatnode storage is freed earlier, leaving more RAM to Postgresql during indexing - extend web Mercator to 89.99 latitude again, reducing broken polygons - skip objects with no tags during initial import, improving performance during first import stage - support LuaJIT for faster processing of Lua tag transforms - update to libosmium 2.14 - windows builds for 32bit are now provided via Appveyor - bug fixes for tile expiry libosmium no longer ships with protozero since version 2.14. So protozero is now seperately included in the contrib/ directory. As with libosmium it is possible to switch to an externally supplied library with cmake.
Release 0.94.0, a new stable branch This is the last release which will support old-style multipolygons. Upgrading to this version requires a reimport for the slim table changes. Major changes since 0.92.0 are - Coordinates are now stored unprojected in slim tables, and an osmium dense file array is used for flat nodes. This dense file array can be read by other libosmium-based programs. - Libosmium is used for geometry building instead of GEOS This offers speed increases, improves code, and avoids relying on a large library for a small portion of its functionality. Other changes are - Tile expiry has been rewritten, fixing bugs, including one that dropped large portions of expiry lists. - Node tags are no longer stored in slim tables, consistent with flat-nodes. THis reduces space required for --slim imports without --flat-nodes. - A default database name of gis is no longer assumed. An explicit -d option is recommended if compatibility with 0.92 and earlier.
PreviousNext