5 unstable releases
0.3.3 | May 23, 2023 |
---|---|
0.3.2 | Apr 10, 2023 |
0.2.0 | Apr 1, 2023 |
0.1.0 | Mar 27, 2023 |
#147 in Geospatial
245KB
2.5K
SLoC
osm-pbf
Read and write the PBF format for Open Street Map (OSM).
Functionality
Reading
There are two steps to reading the PBF format: parsing and decoding. Parsing builds fileblocks out of the raw data. Decoding converts fileblocks into the OSM elements that they contain.
Writing
Similarly, there are two steps to writing the PBF format: encoding and serialization. Encoding converts OSM elements into fileblocks. This crate does not support encoding yet. Serialization flattens fileblocks into raw data.
Execution
This crate is written with async I/O for use with tokio.
Parallelism
The code is serial in nature but it's possible to parallelize encoding/decoding since fileblocks are independent in PBF.
Read parallelization example:
- Call
get_osm_pbf_locations
to get a stream of fileblock locations - Call
parse_osm_pbf_at_location
for each location independently - Process blocks as desired
Write parallelization example:
- Split your blocks into chunks
- Call
write_osm_pbf
for each chunk independently with an in-memory vector as the writer - As each call completes, write them to their final destination (i.e. a file)
Compression
There is a feature for each supported compression algorithm:
Name | Default Feature | Supported |
---|---|---|
Zlib | ✅ | ✅ |
Zstd | ❌ | ✅ |
Lzma | ❌ | ✅ |
Lz4 | ❌ | ❌ |
Bzip2 | ❌ | ❌ |
Lz4 support is not available yet. Bzip2 has been deprecated for years so it is not supported.
There isn't any fine-grained control over encoding but feel free to file an issue if you are interested.
Dependencies
~5–13MB
~149K SLoC