Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 50 million developers.Sign up
osmium catcommand to clean attributes.
- Allow index types with file name in export command.
- Introduce a generic facility for setting output format options. They can be set on the command line (
-x) or in the
format_optionssection in the config file. Settings can be any OPTION=VALUE type string. There are two new settings: For the geojsonseq format, the option
print_record_separator=falsereplaces the command line option
-rwhich is now deprecated. The
tags_formatoption for the Pg output format allows using the
hstoretype for tags instead of
- Open output file earlier in tags-filter command, so we see it immediately in case this fails.
- When tags-filter is used with
--remove-tags, matching ways got their tags removed if they are also referenced from relations. This was clearly wrong.
- New option
getidcommand. When used the tags of all objects are removed that are not explicitly requested but are only included to complete references.
query-locations-indexcommands. These are used to create, update, query and dump node location indexes on disk. These indexes store the location of nodes, typically to add them to ways and relations later. It is the same format used by osm2pgsql (they call it "flat node store") and by the
- Support for new Spaten export format.
- Add special syntax for
--output-headerto copy header from input. Sometimes it is useful to copy header fields from the input to the output, for instance the
osmosis_replication_timestampfield. This can now be done for some commands (currently only
extract) by using the special syntax
--output-header=OPTION!, i.e. using an exclamation mark instead of setting a value.
- Better checking of coordinates in extract boundary polygons/bboxes.
- Compile with NDEBUG in RelWithDebInfo mode.
- Various code cleanups based on problems found with clang-tidy.
- Updated Catch to version 1.12.2.
- Mark PBF output of extract, renumber, and sort commands as sorted. Uses the new header option
sortingof the libosmium library which is not in a released version yet. This sets the
Sort.Type_then_IDheader property in the PBF file.
- Only check if way is closed after check that it contains nodes.
- Man pages correctly show options starting with double dash and other small man page fixes.
- Allow file-based location index types (
sparse_file_array) that need a file name. Using them was not possible because of an overzealous check that didn't recognize the file name.
fileinfocommand now has an
-toption like some other commands.
fileinfocommand to show internal buffer counts and sizes.
multipassstrategy which reads the input file(s) three times making the sort a bit slower, but also using less memory.
- New option
tags-filtercommand. When used the tags of all objects that are not matching the filter expression but are included as references are removed.
- New option for smart extract strategy:
complete-partial-relations=Xwill complete all relations with at least X percent of their members already in the extract.
- New export format "pg" creates a file in the PostgreSQL COPY text format with the GEOMETRY as WKB and the tags in JSON(B) format. This can be imported into a PostgreSQL/PostGIS database very quickly.
- Show better error message if output directory is missing for
- Several fixes for the
tags-filtercommand which could lead to wrong results.
exportcommand man page.
- Regression: Default for
true. It was before v1.9.0 and it is documented this way.
- Add area matching to
tags-filtercommand can now match "areas" using the "a/" prefix. Areas in this sense are all closed ways with 4 or more nodes and all relations with tag "type=multipolygon" or "type=boundary".
--geometry-typesoption to the
exportcommand allowing you to restrict the geometry types written out.
- Also print out smallest node, way, and relation ID in
- In the
renumbercommand, the start IDs for nodes, ways, and relations can now be set together or separately with the
--start-idoption. Negative IDs are now also allowed. Also there is a new
--show-indexfunction that prints out the ID mappings in the index.
- More tests and updated documentation.
--print-default-configoption to the
exportcommand writing out the default configuration to stdout.
getparentscommand to get the ways used by specified nodes or relations having specified members.
- Newest version of libosmium (2.14.2) and protozoro (1.6.3) are now required.
- Calculation of CRC32 in the fileinfo command is now optional. Calculating the CRC32 is very expensive and going without it makes the program much much faster. Use
-cto enable it. It will also be automatically enabled for JSON output to stay compatible with earlier versions of Osmium which might be used in an automated context (you can disable this with
--no-crc). It is also enabled if
-g data.crc32is specified. If it is enabled we are using the CRC32 implementation from zlib which is faster than the one from boost we used before. This is possible through some changes in libosmium.
- Treat ways with same node end locations as closed in
exportcommand instead of looking at the IDs. This is more consistent with what the libosmium
- In the
exportcommand, the decision whether a way is treated as a linestring or polygon has changed. See the man page for details.
- Create linestring geometries for untagged ways if
--keep-untaggedoption is set. It doesn't matter whether they are closed or not, they are only written out as linestrings.
- Show error for ways with less than 2 nodes if
- Attributes (such as id, version, timestamp, etc.) can appear in the properties of the output with arbitrary configurable names. These could overlap with tag keys which we don't want. This change removes tags with those keys on the assumption that the names chosen for the attributes are sufficiently different (something like "@id") from normal tag keys that this will not happen very often and those tags are useless anyway.
--(no)-progressoption work in
- Support for negative IDs in export command.
- Lots of tests with missing metadata (Thanks to Michael Reichert).
- Add metadata options to the extended output of fileinfo command (Thanks to Michael Reichert).
- Add progress bars to many commands.
--redactoption to the
apply-changescommand to redact (patch) history files. The change files can contain any version of any object which will replace that version of that object from the input. This allows changing the history! This mode is for special use only, for instance to remove copyrighted or private data.
- Needs libosmium 2.14.0.
- Update included
catch.hppto version 1.12.1.
- Removed Makefile. Undocumented and possibly confusing way of building. As documented, use CMake directly instead.
- Allow bbox setting with any two opposing corners, instead of insisting on bottom-left and top-right corner. This affects the changeset-filter and extract commands.
- Allow GeoJSON input file to have a FeatureCollection instead of a Feature. Only the first feature of this collection is used.
- Bug in the derive-changes command if it is used without
--keep-details. A deletion of any type of object was written as a deletion of a node. (Thanks to Michael Reichert.)
- Fix assertion failure in diff command.
- Throw exception instead of using assert to catch broken rings.
- Disable progress bar if STDOUT isn't a tty.
- Show error when there are no extracts specified in extract command.
- Improve STDIN handling in extract command. STDIN can now be used with the
simplestrategy, with other strategies it will give you a nice error message.
- Lots of code cleanups based on
clang-tidywarnings making the code more robust.
- Only install manpage directories, not CMake files. (Thanks Bas Couwenberg.)
- Extended some man pages.
- Allow any OSM file header option with
fileinfo -g. There is no final list of possible options, so any option should be allowed.
- Needs libosmium 2.13.1.
- Specifying extracts in config files was broken. The
extractcommand was not reading config files correctly and all resulting OSM files were empty. Specifying an extract on the command line using
--polygonwas still working.
- Allow zero-length index files in renumber.
exportcommand for exporting OSM data into GeoJSON format. The OSM data model with its nodes, ways, and relations is very different from the data model usually used for geodata with features having point, linestring, or polygon geometries. The export command transforms OSM data into a more usual GIS data model. Nodes will be translated into points and ways into linestrings or polygons (if they are closed ways). Multipolygon and boundary relations will be translated into multipolygons. This transformation is not loss-less, especially information in non-multipolygon, non-boundary relations is lost. All tags are preserved in this process. Note that most GIS formats (such as Shapefiles, etc.) do not support arbitrary tags. Transformation into other GIS formats will need extra steps mapping tags to a limited list of attributes. This is outside the scope of this command.
changeset-filtercommand. Only changesets with bounding boxes overlapping this bounding box are copied to the output.
- Support for the new
flex_memindex type for node location indexes. It is used by default in the
exportcommands. The new man page
osmium-index-typesdocuments this and other available indexes.
- The order of objects in an OSM file expected by some commands as well as the order created by the
sortcommand has changed when negative IDs are involved. (Negative IDs are sometimes used for objects that have not yet been uploaded to the OSM server.) The negative IDs are ordered now before the positive ones, both in order of their absolute value. This is the same ordering as JOSM uses.
- The commands
renumbernow also work with negative object IDs.
- Allow leading spaces in ID files for
- Various error messages and man pages have been clarified.
- Updated minimum libosmium version required to 2.13.0.
- Update version of Catch unit test framework to 1.9.7.
- Libosmium fix: Changesets with more than 2^16 characters in comments now work.
- Libosmium fix: Changeset bounding boxes are now always output to OSM files (any format) if at least one of the corners is defined. This is needed to handle broken data from the main OSM database which contains such cases. This now also works when reading OPL files.