Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rosm-project/rosm_pbf_sqlite_dumper
OSM PBF to SQLite dumper, written in Rust
https://github.com/rosm-project/rosm_pbf_sqlite_dumper
openstreetmap osm rust sqlite
Last synced: 4 days ago
JSON representation
OSM PBF to SQLite dumper, written in Rust
- Host: GitHub
- URL: https://github.com/rosm-project/rosm_pbf_sqlite_dumper
- Owner: rosm-project
- License: mit
- Created: 2020-05-01T08:45:54.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-03-31T12:12:31.000Z (8 months ago)
- Last Synced: 2024-03-31T13:24:45.996Z (8 months ago)
- Topics: openstreetmap, osm, rust, sqlite
- Language: Rust
- Homepage:
- Size: 37.1 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# rosm_pbf_sqlite_dumper
A simple command line tool for creating SQLite dumps from [OpenStreetMap PBF](https://wiki.openstreetmap.org/wiki/PBF_Format) files.
## Usage
The tool has a single, optional command line argument, which is the path to the configuration TOML file. The default value is `config.toml` .
## Configuration
The configuration is a TOML file, where the root object may contain the following keys:
- `input_pbf`: Path of the input PBF.
- `output_db`: Path of the output SQLite database.
- `overwrite_output`: If `true` and the given output file already exists, it'll be removed first. Default is `false`.
- `skip_tag_keys`: Array of node/way/relation tags which will be skipped.For table-specific configuration the table's name should be used as the key, and the value must be a `TableConfiguration` object, containing:
- `skip`: If `true` the given table will be skipped. Default is `false`.
- `create_index_on`: Array of column list strings (columns separated by commas) to create indices for on the given table.See `examples/config.toml` for an example configuration file.
## Output
The resulting SQLite database has the following tables (depending on configuration):
- `header`: Contents of the input PBF's header block, encoded as key/value pairs.
- `nodes`: Nodes, described by IDs and latitude/longitude pairs.
- `ways`: Ways, described by IDs.
- `way_refs`: Nodes belonging to ways.
- `relations`: Relations, described by IDs.
- `relation_members`: Nodes, ways, relations belonging to relations and their roles.- `node/way/relation_tags`: Key/value pairs for nodes/ways/relations.
- `node/way/relation_info`: Other info for nodes/ways/relations (version, timestamp, user, etc.).