3 ms·
Some things to think about... 1. Maybe there's no good reason for the files to be so large; for example, maybe the maps are at an extremely high resolution tha
by makecheck 15y ago
Some things to think about...
1. Maybe there's no good reason for the files to be so large; for example, maybe the maps are at an extremely high resolution that will never actually be viewable at the original level of detail on an iPad. Should some effort be spent up front to create iPad-sized versions of each page of the PDFs? This type of thing could be automated with the right software, e.g. something that goes from page to page, scales everything down to 30% and writes a new PDF (and you'd want that, so that modified versions could be shrunk in a push-button way).
2. Look at on-the-fly compression/decompression. The device could hold compressed versions of each file that are decompressed on demand by an app.
Smaller files would not only allow the device to store potentially everything, but it would make any transfers/syncs that much faster.
- jessica_moyer 15y agoThey actually are fairly small files but the number of permits available to certain users will be monumental. Each file may be 5 to 40MB but some users have access to thousands of permits. -Jessica
- makecheck 15y agoI guess option 1 isn't worth investing in, then. But compression (option 2) could still help considerably, even for files of a few megabytes. I imagine it wouldn't be easy to change what's in the files, but a 3rd option would be to look at what they may have in common. For instance, if the user needs 1000 files that all have a very similar first page, there may be some way to avoid making 1000 copies of that information.