I rebuilt a 2017 script that draws your whole Google Drive as a web

G’day all,

Update: took a tip from Reddit and switched the build over to the Drive API. Big drives build heaps quicker now and it saves as it goes, so if Google cuts it off you just hit Build again and it picks up where it left off. The map starts folded up now too so a big drive doesn’t turn into a mess. Click a folder to open it or hit Open it all. If the scroll zoom feels back to front there’s a button to flip it. Cheers to everythingabili on Reddit for the tip and Yagi’s write up on yagisanatode.com. If you grabbed a copy before, make a fresh one from the same link.

Back in 2017 I found Robbie Coombs’ Drive_Mapping script on GitHub and got it working. It draws your Google Drive as a web of dots you can drag around. This year I rebuilt it into a sheet anyone can copy.

Make your own copy here: https://docs.google.com/spreadsheets/d/1q2p7W6vTAa19MEjZv-A8hX2OrFokmJF2satiRKUN7L0/copy

  1. Open your copy and use the Drive Map menu, to the right of Help.
  2. Click Build the map and approve it once. Google warns it hasn’t verified the app. That’s normal, the developer it names is you because the copy is yours.
  3. Click Show the map. Drag a dot and the rest follow, scroll to zoom, click a dot to see what’s inside. There’s a 3D button too.

It only reads your Drive. It never moves, renames, shares or deletes anything, and your map stays in your own copy.

Would love to hear what breaks or what you’d add.

Shout out to @Stephen_Mattison, an old mate from the Google Groups days. Hope you’re well mate.

drive-map-3d-small

New version’s up, see the update at the top of the post. If anyone’s got a big Drive I’d love to know how long the build takes on yours.

This is really cool.

Can you share link to the original GitHub and Yagi’s writeup?

Thanks Both are still up.

Robbie Coombs’ original, the vis.js network that started it all:

Yagi’s writeup on listing a whole Drive tree with the Drive API, which is what the faster build is based on:

Mine reads it in pages of 1000 and writes each page to the sheet before asking for the next, so if Google cuts the run off you click Build again and it carries on where it stopped.

Next version is a fair way past a web. The whole Drive becomes a galaxy, folders are stars and files are planets, and the sheet gets a Findings tab that lists your dead weight, duplicates and everything you’ve shared out with links. I’ll post it here when it’s done.

If you decide to repackage this as a web app, you could use JS to call Google APIs directly. I’ve seen it be a little faster that way. I even wrote a helper library to help with multiple Google API requests that might be of help/use to you.

This is a lovely piece of work, and the galaxy metaphor for the next version sounds rather fun. Writing page by page with resume capability is a thoughtful design choice, since Drive API timeouts are the usual stumbling block. Yagi’s write-up is a solid foundation as well. When the findings tab arrives, that will be the feature people actually use.

Thanks Anchal, appreciate it. For now I’m keeping it as a sheet so anyone can just make a copy and run it on their own Drive without any Cloud project or verification. It reads a normal Drive in one go, so speed hasn’t been a problem yet. If people with really big Drives start hitting the limits I’ll have a proper look at nGFetchALot. Cheers.

@Calverhart @AnchalNigam as promised, the galaxy version’s up, Findings tab and all.