Every Software Engineer needs a hobby – to this end I have been toying with an idea for the last while.<\/p>\n
There are many machine vision and computer vision applications that capture images from cameras and store them on disk. These applications can generate so many images that working with them can be quite difficult. For example consider an application that acquires from two cameras each acquiring at 30 frames per second – this application will save 216K images per hour, a 5 hour run would generate 1 million images!<\/p>\n
Very often the images will be stored on a file system (local or networked) in some sort of hierarchical directory structure. Using a file system is a very efficient way of storing images, database systems (Relational or NoSQL) don’t offer many advantages and indeed can have associated disadvantages.<\/p>\n
But how can we effectively work with so many images, we have possibly millions of images sitting in a set of directories, how can we interact with them and efficiently and query them based on attributes that are interest to us so the we can perform more analysis?<\/p>\n
For example consider this set of (contrived) image queries:<\/p>\n
Give me all of the images:<\/p>\n
+ from camera 1
\n + from camera 1 acquired on Sunday between 13:00 and 13:10
\n + whose file size > 1MB
\n + acquired within 100 meters of this GPS location
\n + that have an average brightness > 63 Grey levels<\/p>\n
Some people have attacked this image query problem by using a relational database to store image meta-data, if designed well this can allow for efficient image retrieval, however it seems to me that a schema-less approach is a better fit for images with dynamic attributes and I like the idea of not being tied down to any particular database technology and all of the baggage that comes with it.<\/p>\n
So my idea is to start out on the road of implementing (for fun) a simple image indexing system for rather large sets of images, it will have an associated tool set, API and maybe even a query language in the future.<\/p>\n
The system will:<\/p>\n
Allow indexing of large numbers of images in arbitrary hierarchical directory structures<\/p>\n
Index images based on standard attributes such as:<\/p>\n
+ Acquisition Date\/Time
\n + Name
\n + Source (e.g. camera)
\n + Type
\n + Size
\n + Bit Depth
\n + Exif Data, e.g.:
\n –> Location
\n –> Author
\n –> Acquisition parameters (aperture, exposure time etc.)
\n + Etc.<\/p>\n
Index images optionally based on Computer Vision metrics, e.g.
\n + Brightness
\n + Sharpness
\n + Etc.<\/p>\n
Allow users to define their own attributes for indexing, e.g.:
\n + Define image attributes based on an OpenCV algorithm
\n + Define attributes based on the contents of the image fie name. <\/p>\n
The system will:<\/p>\n
+ Have no dependencies on technologies such as Database systems etc.
\n + Be cross platform<\/p>\n
To get the ball rolling and so that we can say the first sod has been turned, here is some (naive) python which scans a directory tree of images and creates a flat CSV file of the image name, path and size:<\/p>\n
\r\n#!\/usr\/bin\/python\r\n\r\nimport argparse\r\nimport fnmatch\r\nimport os\r\nimport time\r\n\r\nparser = argparse.ArgumentParser()\r\nparser.add_argument(\"-p\", \"--path\", help=\"The root path to the images directory tree\")\r\nargs = parser.parse_args()\r\n\r\npath = args.path\r\n\r\nprint 'looking in ' + path\r\n\r\nii = 0\r\n\r\nstart = time.time()\r\n\r\nwith open('%s\/.flat' % path, 'w') as out:\r\n for root, _, filenames in os.walk(path):\r\n for name in fnmatch.filter(filenames, '*.jpg'):\r\n p = os.path.relpath(root, path)\r\n (mode, ino, dev, nlink, uid, gid, size, atime, mtime, ctime) = os.stat(os.path.join(root, name))\r\n f = {'name': name, 'path': p, 'size': size}\r\n out.write(\"i,%s,%s,%d\\n\" % (name, p, size))\r\n ii += 1\r\n if ii % 1000 == 0:\r\n print \"Reading %d\" % ii\r\n\r\n\r\nduration = time.time() - start\r\n\r\nprint '%d images indexed in %d seconds, %d images\/s' % (ii, duration, ii \/ duration)\r\n\r\n<\/pre>\nRun it like this:<\/p>\n
\r\nscanner.py --path \"images\\Run1\\ccm17\"\r\n<\/pre>\nOnce the directory tree has been walked and the CSV file generated we can use the following script to query images:<\/p>\n
\r\n#!\/usr\/bin\/python\r\n\r\nimport argparse\r\nimport os\r\nimport csv\r\n\r\nparser = argparse.ArgumentParser()\r\nparser.add_argument(\"-p\", \"--path\", help=\"The root path to the images directory tree\")\r\nparser.add_argument(\"-w\", \"--where\", help=\"The where value\")\r\nargs = parser.parse_args()\r\n\r\npath = args.path\r\n\r\nprint 'looking in ' + path\r\n\r\ncode = compile(args.where, '', 'eval')\r\n\r\nimages = []\r\n\r\nindex = (os.path.join(path, '.flat'))\r\njindex = (os.path.join(path, '.flat.json'))\r\n\r\nprint('opening index' + index)\r\n\r\nclass Image:\r\n def __init__(self, name, size, path):\r\n self.name = name\r\n self.size = size\r\n self.path = path\r\n\r\nwith open(index) as csvfile:\r\n spamreader = csv.reader(csvfile, delimiter=',', quotechar='|')\r\n for row in spamreader:\r\n images.append(Image(row[1], row[3], row[2]))\r\n\r\nprint 'index loaded'\r\n\r\nfor image in images:\r\n if eval(code):\r\n print('%s %s' % (image.name, image.size))\r\n\r\n<\/pre>\nThis allows us to run queries like this:<\/p>\n
\r\nselect.py --path \"images\\Run1\\ccm17\" --where \"'_43' in image.name and image.size > 76000\"\r\n<\/pre>\nThis will quickly list the images whose file size > 76000 bytes and whose name contains ‘_43’<\/p>\n
This is a really simple first step but it does demonstrate how even a flat ‘index’ of attributes can be of great use.<\/p>\n
Next Step:<\/p>\n
+ Add more image attributes to the CSV file<\/p>\n","protected":false},"excerpt":{"rendered":"
Every Software Engineer needs a hobby – to this end I have been toying with an idea for the last while. There are many machine vision and computer vision applications that capture images from cameras and store them on disk. These applications can generate so many images that working with them can be quite difficult. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[301,1],"tags":[293,361,78],"class_list":["post-2128","post","type-post","status-publish","format-standard","hentry","category-by-kevin-godden","category-uncategorized","tag-computer-vision","tag-image-storage","tag-machine-vision"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t