TL;DR: Either “File –> Download” the Google Doc as a web page, or open developer tools and watch for the browser to request the image from Google’s file servers.
The deets Here are two simple ways to get an image out of a Google Doc, at least until Google (maybe inevitably?) adds a “right click-> save image as” feature.
The first way is pretty straightforward, download the Google Doc containing the image files you would like to extract as a web page (File → Download → Web page (.
TL;DR - Here’s a web app to list labelled traffic cam images from the RI DOT website. I used YOLO (You Only Look Once) to detect objects (vehicles) in the images and FastAPI to serve the results to a React app. The displays the cam images and results and uses LeafletJS to display the cameras on a map. The backend is hosted on Railway and the front end on Github Pages.
TL;DR - Here’s a list of shipwrecks plotted on an interactive map, all over the Narragansett Bay and greater New England area.
Motivation At FarSounder I work on the development software of 3D Forward Looking Sonar products. Part of that development process of course includes collecting data from a lot of different situations and running it through some processing algorithms to evaluate performance and make improvements. To that end, we’re often out on the Narragansett Bay collecting data with the system, and always looking for areas in the bay with interesting features that we can use to test and benchmark our algorithms (pilings, super steep shoals, rock piles, piers, etc).
TL;DR: Listen to customers, test your assumptions, follow the data, repeat
I participated in the NSF I-CORPS program quite a while ago now (LA Node, Fall 2016). The goal of the program is to assist scientists with technology transfer. It’s basically a crash course in entrepreneurship for STEM researchers. The program takes place over about 8 weeks and participants interview at least 100 people (customers, competitors, thought leaders, and partners) with the goal of finding product-market fit and determining the feasibility of commercializing the result of their NSF sponsored research project.
TL;DR - Switch raw heap pointers to unique_ptrs when possible. If your heap allocated resource needs multiple owners, use a shared_ptr instead.
I find myself reviewing C++ smart pointer types over and over again. I guess for me, it’s just been one of those things that doesn’t stick, or perhaps I’ve only needed to use them infrequently enough to forget about them. So, here’s a note to myself, and anyone else dying to read about smart pointers in C++.