Answer questions about OSM data like:
- “What's the longest Main Street?”
- “How far can I drive on unpaved roads in this region?”
- “How long is the M1 motorway?”
- “Are these rivers connected?”
- “What's the river drainage basins?”
Generate river drainage basins
osm-lump-ways -i path/to/region-latest.osm.pbf -o region-rivers.geojson -f waterway=river
To group based on the river's name:
osm-lump-ways -i path/to/region-latest.osm.pbf -o region-rivers.geojson -f waterway=river -g name
To find long streets and assemble them into connected (Multi)LineStrings:
osm-lump-ways -i path/to/region-latest.osm.pbf -o long-streets.geojson -f highway -g name
cargo install osm-lump-ways
OSM linear features (eg roads, rivers, walls) are stored as way
object. The OSM tagging
model often requires one feature to
be mapped as many different ways. osm-lump-ways will assemble them all together.
Run with --help to see all options.
There are 2 ways to select which OSM ways will be used. All relations are currently ignored.
key/∃keyway has this tag~key_regex/∃~key_regexThere is a key, which matches this regex.∄keyway does not has this keykey=valueway has this key and this valuekey≠valueway either doesn't have this key, or if it does, it's not equal to valuekey∈value1,value2,…way has this key and the value is one of thesekey∉value1,value2,…way either doesn't have this key, or if it does, it's not one of these valueskey~regexway has this key and the value matches this regex.F1∨F2∨F3…logical OR of the other tag filters F1, F2, …F1∧F2∧F3…logical AND of the other tag filters F1, F2, …
The popular regex crate is used for
matching. Regexes, and string comparison, are case sensitive. Add (?i) at
start of regex to switch to case insensitive (e.g. name~(?i).* street)
Regexes match the whole value, name~[Ss]treet will match Street or
street, but not Main Street North nor Main Street. Use
name~.*[Ss]treet.* to match all.
The -f/--tag-filter can be specified one or more times, and an OSM object
is only included if it matches all defined filter's, i.e. a logical
AND of all filters.
-f highway: Only ways with ahighwaytag are included-f highway -f name: Only ways with ahighwayandnametag are included.-f highway -f ∄name: Only ways with ahighwayand without anametag are included.
The -F/--tag-filter-func takes a single ordered list of tag filters (separated by ;),
and includes (with →T), or excludes (with →F), the OSM object based
on the first filter function which matches. A bare T or F applies to all.
Example: We want to include all waterways. But not waterway=canal. But we
want a waterway=canal iff it also has a lock=yes tag.
-F "waterway=canal∧lock=yes→T; waterway=canal→F; waterway→T; F
Here, a “frame” of a grouping is a shortest path through 2 points in the grouped together ways. This can be useful for waterways to find where a big group is connected.
--output-frames FILENAME.geojsons will save these features to a file.
GeoJSONSeq output format only.
- WaterwayMap.org
- Longest O'Connell Street in Ireland
- Road most split in UK&Irl
- Die Bahnhofstrassen in jeder Schweizer Sprachregion (german language only)
- Your project here!
This software isn't finished, here's what I'd like to add. Feel free to send a patch.
- All tags need to be specified in advance to join on. Perhaps add something to match all possible tags? (inspired by this q). (“Group by all tags the same” might do it)
TBC
Copyright 2023, MIT/Apache2.0. Source code is on Github
(osm-lump-ways).
The output data file(s) are a Derived Database of the OpenStreetMap database, and hence under the ODbL 1.0 licence, the same as the OpenStreetMap copyright, and contains data © OpenStreetMap contributors