sdl60660 / river-runner Goto Github PK

Might not be an issue on your end at all, but I noticed Israel appears like this:
לארשי
But it should be:
׳שראל

All Hebrew is reading left to right instead of right to left. I cannot confirm the issue affects other RTL languages, but I would assume so.

Lake Atitlán is a very deep, very picturesque lake in the Guatemalan Highlands (think Lake Como, but ringed by several immense volcanoes), the result of a caldera explosion many years ago. It does not drain into the Pacific Ocean (at least not directly).

There are many such basins around the world (https://en.wikipedia.org/wiki/Endorheic_basin).

The application should reflect these flows, if possible, so that a rain drop placed in the Atitlan basin, flows to the lake, and stops there. It would be an incredible update to show the many people living around these lakes or swamps that their water doesn't actually go all that far. Unfortunately, agricultural runoff in the Atitlan basin doesn't "disappear" (does it ever though?). It just flows a few kilometers and builds up in the lake, threatening this unique ecosystem! The same applies to other fragile ecosystems, including desert basins, swamps, etc.

Aside from that, excellent application for teaching!

I'd love a way to just have the route shown without then needing to do the whole 3-d "move along the route" thing.

My drop, from Leeds, jumps out of the river Aire, below Leeds in the UK, and trundles overland for a while between Allerton Bywater and Knottingley.

This may be due to having too few stop features in the dataset, or it's being too liberal about assigning a feature vs. just calling it an "unnamed inland feature". Should be able to add another ~50,000 stopping features if I simplify them.

(see the attachment) For example, in River Runner, the names of various branches of the the South Saskatchewan River and the Saskatchewan River (when the raindrop falls in the headwaters of the Old Man River at 50.11402,-114.70464) are mostly called "St Mary's River" (See the first column.) This is incorrect. The third column shows the correct names at each major confluence. The second column shows the coordinates of each major confluence. The St. Mary's River is a minor tributary entering the Old Man near Lethbridge, Alberta.

Another error is that the Red River of the North ends where it flows into Lake Winnipeg but River Runner has it going through Lake Winnipeg and on to Hudson Bay through what is known as the Nelson River.

What can be done to fix this behaviour? There are many other examples of this kind dependin on where the raindrop fall. River Runner is a great app but it won't be truly great until these bugs are squashed. Is there anything I can do to help?

Tributary Names South Saskatchewan River Basin and Nelson River basin.pdf

Should be able to optimize the way that I'm querying for elevation samples along route and at least reduce client/API load. Fog effect may be helpful, as well: https://www.mapbox.com/blog/mapbox-gl-js-v2-3-0-distance-fog-elevation-querying-and-terrain-performance-improvements

It's sometimes hard to see the blue line while the rest of the screen is moving, and it'd be better if it had thicker line weight.

I tried a trans-boundary basin (Red River ) that flows north into Canada and it hung the app.

Has to do with zoom level differences before/after 3d terrain has loaded

Sections are staying highlighted on the locator minimap after the runner passes them. Seems to be happening in a way it wasn't before the latest changes.

Before I can process what I'm seeing, the run ends at a coastline and resets to show the entire continental US. It's jarring.

To watch the same run again, or to do another run in an area near the first, the user is forced to restart zooming and searching.

Ideally, IMO, when the run is paused, the user should be able to interact with the map; continuing the run moves the view back to following the run. At the end, the run should just stop and remain viewing the end. Maybe an interface element to "run again" which returns the user to the start.

If I click on the mountains in central Idaho, I sometimes get "can't find a flowpath" and sometimes it just spins forever (>30 minutes).

First of all, a fantastic project.

Not sure if this is the right place to report "data" issues, but when selecting San Marcos, TX, it incorrectly reports the San Marcos River (47 km) flowing into Brushy Creek (78 km).

Brushy Creek is a tributary of the San Marcos, joining the San Marcos river just upstream of Stairtown, TX, as you can see on this Topo Map

Very rare and only seems to happen with basically non-existent flowpaths, but need to either add a fix or add error handling to keep it from hanging in search step (see "Pope Valley, CA")

It looks like the poi map data (not the imagery) is sourced from OSM, but you haven't provided attribution as required by OSM's license.

I viewed the page on a mobile browser.

For more information, please see https://www.openstreetmap.org/copyright

I live at the headwaters of the Colorado River. Around 70% of the water in our watershed is pumped through tunnels under the Continental Divide to the east side of the divide. This creates a misconception on the part of people on the Front Range that makes them ignorant about where their water comes from. Anyway this can be fixed to show that the majority of those raindrops in our watershed do not go west.