Update README.md

README.md

@@ -83,21 +83,22 @@ Nomos_Uni -> 2'466 Tiles
 Nomosv2 -> 5'226 Tiles  
 inaturalist_2019 -> 131'943 Tiles  
 
+My main point here also would be that this dataset, even though still consisting of like 390k tiles, is already a strongly reduced version of these original datasets combined.  
 
-## Files
-
-Files have been named with '{dataset_name}_{index}.png' so that if one of these used datasets were problematic concerning public access, could still be removed in the future form this dataset.  
 
-(Note to myself: Tiles 'inaturalist_2019_65228.png','inaturalist_2019_54615.png','inaturalist_2019_22816.png' removed because of PNG error when checking with [pngcheck](http://www.libpng.org/pub/png/apps/pngcheck.html))
+## Files
 
-## Optimization
+Files have been named with '{dataset_name}_{index}.webp' so that if one of these used datasets were problematic concerning public access, could still be removed in the future form this dataset.  
 
-Then I used [oxipng](https://github.com/shssoichiro/oxipng) ("oxipng --strip safe --alpha *.png") for optimization.  
+I did convert to webp because of file size reduction, because the dataset was originally at around 200GB, when I then used oxipng ("oxipng --strip safe --alpha *.png") for optimization. But lossless webp is just the best option available currently for lossless file size reduction.
+Well, JPEG XL would be the absolute best modern option for lossless compression, but its relatively new as in not everything supports it yet (especially cv2 currently, which we use for training, so would be worthless having them in jpeg xl format at this moment). I will rant here about the decision of one company to disregard browser support of jpeg xl for avif, which is waaay worse (super bad) concerning lossless compression/file size, webp is way older and beats it.  
 
-## WebP conversion
+TODO put paper stuff etc in here about webp / jpeg xl being superior concerning lossless compression
 
-The files have then been converted to lossless webp simply to save storage space locally and for faster uploading/downloading here on huggingface. This reduced size of the dataset by around 50 GB.  
+(Note to myself: Tiles 'inaturalist_2019_65228.png','inaturalist_2019_54615.png','inaturalist_2019_22816.png' removed because of PNG error when checking with [pngcheck](http://www.libpng.org/pub/png/apps/pngcheck.html))
 
 ## Upload
 
-I uploaded the dataset as multi-part zip archive files with a max of 25GB per file, resulting in X archive files.  
+I uploaded the dataset as multi-part zip archive files with a max of 25GB per file, resulting in X archive files.  
+This should work with lfs file size limit, and i chose zip because its such a common format. I could have of course used another format like 7z or zpaq or something.  
+I actually once in the past worked on an archiver called [ShareArchiver](https://github.com/Phhofm/ShareArchiver) where my main idea was, that online shared data (like this dataset) generally gets archived once (by the uploader) but downloaded and extracted maybe a thousand times. So resulting file size (faster download time for those thousand downloads) and extraction speed (those thousand extraction) would be waay more important than compression speed. So the main idea is we are trading archiving time (very long time to archive) of that one person for faster downloads and extraction for all. The design of this archiver was that I chose only highly assymetrical compression algos, where compression times can very slow as long as decompression speed is high, and then it would brute force during compression, meaning of those available highly assymetric compression algos, it would compress each single file with all of them, check the resulting file sizes, and add only the smallest one to the .share archive. Just something from the past I wanted to mention. (one could also use the max flag to just use all of them, meaning also the symmetrical ones, just to brute force the smallest archive file possible (using paq8o etc), but of corse compression time would also be very long, but this flag was more for archiving purposes than online sharing purposes, in a case where store space would be waay more important than either compression or decompression speed.)