Here’s a screenshot of the tree graph I took. I am making a large tree of all the US presidents, starting with the Adamses, then the other presidents with common New England ancestry, and then the rest.
Nice! If you want to use any of it, I posted a Presidents tree a few years ago. It was an example of using classroom posters of presidents portraits and 1st lady portaits to feed Gramps data for thumbnails.
Maybe you can use the data?
US_Presidents_2022-11-02.gramps
I might do. I’m planning to enter all the data myself, so I can’t guarantee that I’ll use the data.
As you like. I have no ego invested in the dataset.
And comparative merging is one of the weak spots of Gramps. A split view of two similar trees of separate origins does not exist. (The existing tools expect Tree being compared will be forks of one another.)
So comparing trees and importing selectively may actually be more work than building from scratch.
There is a source available through the Internet Archive on the Presidents through Bill Clinton.
Mosley, Charles; Hugh Brogan, “American Presidential Families; Biographical Details and Descendants Tables”, New York : MacMillan and Co., 1993; Internet Archive, 2020
You cannot download the book but it is available to Borrow and use online.
Well, I would like it to be the default. 
But then not sure how to label the button.
Also suggest that when you click on “expand spouses” that button should change to “collapse spouses” instead of being disabled.
Oh yeah. That was when I was having such bad experiences with gpkg archives.
They choked when doing repeated import attempts. (Which I needed to do while trying to write docs.) The import did not like when the media objects already exist. Nor did it do well with relative paths across various OSes.
Was toying with the idea of just using the URL (like GEDCOM does) when discovered that Gramps cannot do that. While it imports a URL from GEDCOM and uses it nicely, the Media Editor refuses to validate edits for a URL paths. (Even when just adding a Date. Very frustrating.)
And I still have not found a good way to document provenance for a media object.
Yes, that is a weak place in all of the Gramps frontends. If you want, just a media.zip file would be useful (if you include the links from the people to them). gramps-web-api needs them separated anyway.
Yes, that is a good idea.