samlearner

8 ms·

1.
by samlearner 3mo ago
Had to over-simplify things a bit on cURL to keep this legible to a general audience, particularly in the first few paragraphs. The idea is that at some point down the stack from your request, libcurl is almost certainly involved (as a depe
2.
by samlearner 3y ago
We're not scrubbing over a pre-rendered animation here. We're using a library called threejs (a WebGL wrapper) in the background figure and adjusting the camera/models in response to scroll position (within a react environmen
3.
by samlearner 3y ago
Hey, I'm one of the graphics journalists/authors on the piece This is not very helpful, but the answers to most of your questions is "it depends" Our team is made up of reporters, designers, and graphics journalists, but
4.
by samlearner 5y ago
Just implemented suggestion (b), sorry for the delay on that. I'm not sure about (a) yet, but will definitely at least add an option to disable autoplay and will consider that.
5.
by samlearner 5y ago
Designing for mobile is hard! I'm sorry! Really limited space to work in controls without covering for too much of the map
6.
by samlearner 5y ago
Ha, I don't want to tell you you're wrong, but having heard from a lot of people on this, I'm not sure this is right. The vast majority of people I hear from seem as or more interested in the flyover than the routing itself.
7.
by samlearner 5y ago
Generally, I've found that if it's active at all (requires a click, reading something, opting-in etc) the vast majority of people will miss it.
8.
by samlearner 5y ago
Working on adding some ability to view upstream paths, but there are a lot of complications with that and it would probably be limited to the US for now. That's the next major item on the to-do list, though.
9.
by samlearner 5y ago
Yeah the tool struggles a lot with engineered features (dams, canals, etc.) and Chicago is really our quintessential example of this (issue documented a little here: https://ksonda.github.io/global-river-runner/ ). The
10.
by samlearner 5y ago
Hey everyone, glad you all are enjoying the project! To address some of the points I'm seeing, it's not perfect right now, which is why we've considered this a beta release. In particular, there are some issues around name co
11.
by samlearner 5y ago
Hey! So the solution I've got in place was actually kind of a compromise solution originally. I had it jump right in at first and people asked to disable autoplay, so I tried completely shutting it off and a lot of people missed that y
12.
by samlearner 5y ago
This should be fixed now!
13.
by samlearner 5y ago
This has been added a stopping feature as of the last update.
14.
by samlearner 5y ago
Hmm ok, there's a fix here and it's probably something to do with a timer and a way to opt out, I'll work on this.
15.
by samlearner 5y ago
That's the form the data came in and when it came time to convert it, I figured it might be better not to.
16.
by samlearner 5y ago
You're the second person to mention this now! The stopping feature stuff is very tricky and not in the original USGS data, but I can block out Chesapeake Bay the same way that I blocked or the Gulf of Mexico
17.
by samlearner 5y ago
Ha I appreciate you sharing the repo, but if someone is interested in finding a longest route, they should probably just go straight to the data source (USGS NHDPlus data/NLDI API)
18.
by samlearner 5y ago
I struggled with this a lot. Originally set that ending overview at the beginning, but was worried that practically a lot of users might miss the main feature. I've heard from a lot of people that they were surprised it went into the 3
19.
by samlearner 5y ago
Hey, thanks for the feedback. I actually struggled on what to do with the cursor, since the map is draggable (when not at min zoom level) prior to a click and the default mapbox cursor is denoting that. On balance, I think you're right