Just wanted to fire off a quick question to think about (I have a few others). These aren't questions off the top of my head, but rather some things I've come across as I've been working with real world things. I'm beginning to assemble the soil data for the US. So far, I have NY, PA, and MD:
it is about 3M areas, but as you know, it has lots of vertices. This file is 22GB in size. The corresponding ESRI geodatabases that make up the individual States is 6GB.
I know that disk space is cheap, but there is a fairly hefty inflation factor for the data sizes.
Do you think there is a need to do something regarding the space that a .map file takes up (perhaps allowing compression like in 8, with the warning that if you want to work fast with really large data, you have to keep the .map uncompressed).
Or, maybe next year, a 4TB drive might actually only cost $50 so who cares? (I got my 4TB drive for $59 on a huge Best Buy sale two weeks ago).