at a certain point it would probably help to meaningfully downsample/summarize the data at the larger scales..."semantic zooming"...then you just aren't plotting as many points
agree that using the API is likely the nicer route. you can also apply for a quota increase, I recently applied for youtube API quota increase to 100,000 units and it was approved for my app (https://cmdcolin.github.io/ytshuffle/) I was concerned they wouldn't like that the app downloads so much data but it was approved without much question, they just wanted terms of service prominently displayed to end users
I always like this when the url is always copyable, but in our app, the state can get quite large. We started with base64 encoded gzip of json.stringified app state but just gets quite long. Arguably it could be reduced a little bit, but would still be hundreds-thousands of chars routinely, so we switched to using a little URL shortening service that we wrote on aws lambda+dynamodb
I remember my neighbors dad showing us this on their compaq pc. I can't remember exactly what year it was I would guess it was probably <2004. I think it had a cool 3d visualizer thing with lots of polys but not google earth
this is a random note since I know OP didn't mention RSI, but since you did, I will mention: gotta watch out for putting too much pressure on your elbows with armrests and such. I found this can cause trouble with your pinky finger (sometimes called ulnar tunnel, which is fairly different from carpal tunnel). a post I wrote https://cmdcolin.github.io/posts/2022-07-08-pinky
i've not yet started my ergonomic gadgets journey but just being aware of the elbow->hand connection has helped me
I am not the author of this tool but found it extremely useful. It has caught almost a 100 typos in our codebase in snake_cased and camelCased variable names, in prose in our docs, and it is programming-language agnostic! So awesome. Highly recommend. Easily set up as a github action in CI too
pandoc is interesting because with markdown it currently converts the "alt text" for figures  in markdown->pdf conversion into the figure captions, which is cool but makes me think: it is not alt anymore, anyone should have it
"Software engineering at Google" (O'Reilley) has a lot of "team focused" advice also, it's overall pretty non-technical but generally a good read. Free to read online too https://abseil.io/resources/swe-book