If you plan to run your analyses on cloud computing, "google drive"
may not be the correct target to put the data into, as you will
probably want it in a compute-oriented filesystem for performance
reasons (which would likely require copying it a second time if you
copied it to "google drive" first).
I don't have experience transferring our data to "google drive". If you can run an interactive instance with a desktop on google's compute infrastructure, and run Aspera inside that, it would avoid needing to use your local machine's internet bandwidth and storage. I don't know much about the tools for mounting "google drive" as a network drive, to avoid needing to allocate a large amount of storage on the interactive compute instance. I assume google cloud computing has something equivalent to AWS S3 ("Cloud Storage", probably?), which is where I would expect to be the right place to store the data for cloud processing, and is probably better integrated into the cloud infrastructure than "google drive".
Unfortunately, we currently do not have non-interactive ways to download the new release of the HCP-YA data. There is an older version of the data (which doesn't have the newer fMRI cleanup, etc) on AWS S3, but we don't currently have an interface for generating the needed API keys, since we shut down ConnectomeDB. We plan to implement these in the near future.
Tim