Data

Tools

Indexes

Applications

Experiments

Open Sustainable Technology

A curated list of open technology projects to sustain a stable climate, energy supply, biodiversity and natural resources.

WaterwayMap

River Basins from OpenStreetMap.
https://github.com/amandasaurus/waterwaymap.org

Category: Hydrosphere
Sub Category: Ocean and Hydrology Data Access

Keywords

data-visualization geo geospatial openstreetmap openstreetmap-data osm osm-data river-network-analysis river-networks topology water watershed

Last synced: about 14 hours ago
JSON representation

Repository metadata

WaterwayMap.org | River Basins from OpenStreetMap

README.md

WaterwayMap.org

See the website.

map of europe with all the river basins higlighted

News & Updates on the OSM Town Mapstodon.

News & Posts

Who's using mapping with this?

OSM Tagging Discussions from this tool

Loops

Loops in waterways are detected and shown on:
WaterwayMap.org/loops.

End Points

Points at which waterways end are shown on: WaterwayMap.org/ends.

Where things turn into streams

To detect places where waterways (e.g. rivers) flow into a stream, a GeoJSON file of those is generated: data.waterwaymap.org/planet-waterway-stream-ends.geojson.gz (~ 2 MiB compressed). It can be loaded into JOSM to find errors.

It was asked for in issue 52, with the code in commit 4730275.

Statistics

Loops

A CSV file of statistics of loops is generated and available for download at
data.waterwaymap.org/waterwaymap.org_loops_stats.csv. See the
osm-lump-ways documentation on the CSV stats
file
for documentation.

It is used by @[email protected] for a
mastodon account summarizing stats:
@[email protected]
feed

End Points

A CSV statistics file of end points, is also generated dails and downloadable at
data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst.

See the osm-lump-ways
documentation
for file format.

Related Projects

Other websites

If you like WaterwayMap.org, you might like the following other websites:

FAQ

What do the colours mean?

The colours are randomly assigned, and based on the final destination of the
river. Everything that flows into the same point, gets the same colour. If you
click the settings, you can change the number of colours. This can be useful to
try to differentiate 2 different river networks.

Does thickness represent flow rate?

The thickness of the lines is based on how many kilometres of river are
upstream of that segment. The flow rate of a river is based on many things,
such as the width of a river, and obviously changes a lot based on rainfall! I
only use OpenStreetMap data, which rarely has width, and wouldn't have
real-time data about the amount of water flowing through a point! What it does
show (“how many waterways in total are upstream of here?”) will probably
correlate with the flow rate, and is probably good enough for making a map, but
you shouldn't use to see if your house is going to flood!

If a natural waterway runs through a lake, is it possible to show all the branches as connected waterways?

Currently, the only way to do this is map a waterway though the water body.
There is currently no other way to do it. The OSM community is a little
uncertain if this is always a good idea. There is a community
discussion.
There is a new tag
waterway=flowline
as possible tag to use for these ways through waterbodies.

I did try to add a map view which would include the edges of waterbodies,
e.g.
but that didn't work as well, because it only uses ways not relations, so
many water bodies weren't included.

However, the latest new feature, the River Directory, could benefit from relation
support. So I might add that.
cf..

Copyright

Copyright MIT or Apache-2.0, 2017→2024 Amanda McCann [email protected]

Initially this project was called osm-river-basins.

Owner metadata

GitHub Events

Total
Last Year

Committers metadata

Last synced: 5 days ago

Total Commits: 562
Total Committers: 9
Avg Commits per committer: 62.444
Development Distribution Score (DDS): 0.041

Commits in past year: 179
Committers in past year: 5
Avg Commits per committer in past year: 35.8
Development Distribution Score (DDS) in past year: 0.039

Name Email Commits
Amanda McCann a****a@t****g 539
mxdanger 3****r 13
Quincy Morgan 2****a 4
yvecai 5****i 1
limex g****h@g****m 1
kaleidoscopica r****3@y****m 1
Matt Whilden 1****n 1
Jesse Weinstein j****e@w****g 1
Douglas Gardner d****s@c****h 1

Committer domains:

Issue and Pull Request metadata

Last synced: 1 day ago

Total issues: 77
Total pull requests: 13
Average time to close issues: 27 days
Average time to close pull requests: 11 days
Total issue authors: 48
Total pull request authors: 8
Average comments per issue: 2.31
Average comments per pull request: 1.46
Merged pull request: 11
Bot issues: 0
Bot pull requests: 0

Past year issues: 36
Past year pull requests: 4
Past year average time to close issues: 15 days
Past year average time to close pull requests: 3 days
Past year issue authors: 24
Past year pull request authors: 4
Past year average comments per issue: 3.19
Past year average comments per pull request: 1.5
Past year merged pull request: 4
Past year bot issues: 0
Past year bot pull requests: 0

More stats: https://issues.ecosyste.ms/repositories/lookup?url=https://github.com/amandasaurus/waterwaymap.org

Top Issue Authors

  • angoca (7)
  • watmildon (4)
  • mxdanger (3)
  • EwenH (3)
  • JLZIMMERMANN (3)
  • mcliquid (3)
  • matozoid (3)
  • scarapella (3)
  • danieldegroot2 (2)
  • limex (2)
  • matkoniecz (2)
  • Janjko (2)
  • deevroman (2)
  • JesseWeinstein (2)
  • daganzdaanda (2)

Top Pull Request Authors

  • mxdanger (5)
  • quincylvania (2)
  • JesseWeinstein (1)
  • watmildon (1)
  • limex (1)
  • kaleidoscopica (1)
  • yvecai (1)
  • zuzak (1)

Top Issue Labels

  • enhancement (1)

Top Pull Request Labels

Score: 6.628041376179533