#waterwaymaporg — Public Fediverse posts

@amapanda
Love the #waterwaymaporg! Turns out to be very useful for bike route planning (besides watersports ofc)

One feature I'm missing, or not finding, is to get information on the rivers (name, etc.) when clicking or interacting with the objects.

#WaterwayMapOrg data has been updated, and the daily data updates should be back working.

Sorry for the interruption! Thanks to all the people who reminded me to look at it :)

@hareldan for #WaterwayMapOrg I produce several X0 GiB GeoJSON files. (Well I make GeoJSONSeq which #tippecanoe can parse).

I gotta say, GeoJSON is good for writers, because it's just text...

@BUnicycling Hmmm. For #WaterwayMapOrg, i look at role `main_stream` so it doesn't matter whether they have a side channel or millrace role or not...

@jtwcornell91 #WaterwayMapOrg (default map) does pay attention to canals in some ways, such as locks. That's how OSMers map them in a main river.
WWM will also pay attention to OSM River Relations. So if "a river" is partially a canal, you can add that canal to the river relation, and WWM will treat it as a river.

@amapanda

Love it!

It has been a while since I last visited your #WaterwayMapOrg site.

I see changes that I'll need to make in order to include some large diversions in this area.

I haven't edited OSM waterways yet, so this is now my New Year's resolution.

Water. The lifeline of our world.

Data is beautiful …

https://waterwaymap.org/

#waterwaymaporg

#WaterwayMapOrg goes global!
(I upgraded #MapLibre, and I turned on Globe View)
https://waterwaymap.org/

RE: https://en.osm.town/@openstreetmap/115728789533649601

Thanks to the OpenStreetMap Foundation for paying for the hosting costs for #WaterwayMapOrg for the next year! 😊😊😊

@pierzen I haven't changed anything on #WaterwayMapOrg. It works for me OK on Firefox v140 on debian trixie....

@pierzen Canada is a mess on #WaterwayMapOrg. Yes, all the loops. But so many rivers not connected up.

Reality (and therefore #OpenStreetMap) is fully of edge cases. Usually when parsing OSM data, you can ignore those, or flatten them down.

The ““““fun”””” with #WaterwayMapOrg is that if that edge case occurs say... in a weird side channel of Mississippi, then you can't just ignore everything upstream (or downstream (depending)) of that point. Cause that's a large chunk of north america.

My current #WaterwayMapOrg is re-working the “How are River A & B related? Tributary? Side Channel? etc“.

Fitting OSM data into a small number of categories... what could possibly go wrong? 😈

Updates on #WaterwayMapOrg should be working again.

Sorry for the lack of updates. Some weird shell/makefile path error. I've hit it with a big hammer.

I spent ages refactoring #WaterwayMapOrg code to produce debugging data to try to track down why WWM had the Missouri & Mississippi rivers separated by a weird fake river.

Turns out there was a loop in #OpenStreetMap Data.

Fix the input data, you fix the output data. 🙄🤦🏻‍♀️