William.Hatheway
Well-known member
When downloading scientific datasets, knowing the compressed file size is only half of the information users need. Download pages should clearly display both the compressed download size and the expected decompressed disk-space requirement.
This is especially important for large modeling systems, where users may be working on laptops, teaching computers, virtual machines, shared servers, or research workstations with limited storage.
The WRF Preprocessing System geographical data page provides a good example of why this matters. The highest-resolution mandatory WPS geographical dataset is approximately 2.6 GB compressed but about 29 GB once uncompressed. That is a dramatic difference. A user who sees only a 2.6 GB download might reasonably assume that having 10 or 15 GB of free disk space is sufficient, only to discover during extraction that the dataset requires far more space.
This becomes even more important because users often need additional space beyond the final extracted dataset. During installation and extraction, they may temporarily have both the compressed archive and the decompressed files on disk. In this example, that means the practical storage requirement can exceed 30 GB before the archive is deleted. Add WRF, WPS, meteorological input data, model output, libraries, and other geographical datasets, and storage requirements can grow very quickly.
Providing both numbers is a small documentation improvement that can prevent failed extractions, full disks, interrupted installations, and unnecessary frustration. Scientific software should make computing requirements as transparent as possible.
Clearly stating “Download size” and “Disk space after extraction” gives users the information they need to plan ahead, particularly students, researchers, and users working with limited computing resources.