imaging/getting-started-with-image-streams.md

@@ -72,15 +72,36 @@ Try to output only image headers:
 Byte order as on your system architecture, e.g. little endian on x86 and big endian on ARM.
 
 Outputting number of rows, columns, and image type with each image may look redundant and inefficient. It is not for the following reasons:
-- 20 bytes is small overhead on large images
-- by outputting image size and type, each image record is self-contained
+- 20 bytes is a small overhead on images, which typically are large
+- by having image size and type, each image record is self-contained
 - each image can be of different size and type (see examples in **image files and file lists** section below)
 - header is optional (see examples in **\<image\>** section below)
 ### \<image\>
+The image part of the **snark** image format is simply an uncompressed binary image representation.
+
+## image filters
 ...
 
 ## image files and file lists
+single image, from/to ...
+
+supported formats including gz ...
+
+input image lists ...
+
+output image lists ...
+
+combining both ...
+
+## videos
+...
+
+# **cv-calc**: more image manipulations
+...
+
+# converting images from/to csv
 ...
 
-# potentially unmaintained documentation at other repository fork:
-See [https://github.com/acfr/snark/wiki/get-started-with-image-data]
\ No newline at end of file
+# links to more (potentially unmaintained) documentation elsewhere:
+- [https://github.com/acfr/snark/wiki/get-started-with-image-data]
+- [ACFR software blog](https://confluence.acfr.usyd.edu.au/display/ACFRSoft)
\ No newline at end of file