C++ framework for working with OSM data files
http://osmcode.org/libosmium/
Osmium is a C++ framework for working with OSM data files. Osmium can read
OSM data in XML or binary format (PBF) and can call different handlers for
each OSM object.
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout Application:Geo/libosmium && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
libosmium-2.17.1.tar.gz | 0000517423 505 KB | |
libosmium.changes | 0000007227 7.06 KB | |
libosmium.spec | 0000002554 2.49 KB | |
signal.diff | 0000001503 1.47 KB |
Revision 10 (latest revision is 11)
Predrag Ivanović (predivan)
accepted
request 934256
from
Predrag Ivanović (predivan)
(revision 10)
- Update to 2.17.1 * Add `osmium_tags_filter` example showing use of tags filter. * Add `Writer::set_header()` function to set header after constructing. * Various improvements in PBF file reading make it slightly faster and less CPU intensive. * Since 2.17.0 Osmium will, when reading files, tell the kernel using `fadvise` that it can remove pages from the buffer cache that are not needed any more. This is usually beneficial, because the memory can be used for something else. But if you are reading the same OSM file multiple times at the same time or in short succession, it might be better to keep those buffer pages. In that case you can set the environment variable `OSMIUM_CLEAN_PAGE_CACHE_AFTER_READ` to `no` and Osmium will not call `fadvise`. Set it to `yes` or anything else (or not set it at all) to get the default behaviour. * If the macro `OSMIUM_DEFINE_EXPORT` is defined, all exception classes used by Osmium will get "tagged as exported" using `__declspec(dllexport)` when using MSVC or `__attribute__ ((visibility("default")))` on other compilers. This is needed in PyOsmium. * Fix integer parser. IDs in OPL files can now be anything between -2^63 and 2^63-1. - Add signal.patch from @kukuk to deal with catch test failures on Factory/TW
Comments 0