Height map too large for heightfield file node? (Map attatched) – March 11, 2023 at 11:58PM

Here is the height map (https://drive.google.com/file/d/1vGBOdf1UHkKq5PA8D7pxEPa9J2v4qFmb/view?usp=sharing). I merged some Yosemite lidar data together into a single png (about 1.6 gigabytes). When I try to open it in COPS, it seems like it gets 60% of the way there after 3 hours, but then it just stops making progress. The same thing happens with the heightfield file node. It pushes my ram to 32 gigabytes out of 64. I also have a bigtiff version of the file I’d rather use, but it is nearly 72 gigabytes so it seems too big to load into ram. I don’t want to do any lossy compression to keep the data accurate. Is there a standard workflow for dealing with massive images?