-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 08 May 2004 12:43 pm, Helge Hielscher wrote:
> On Sat, 08 May 2004 14:02:32 -0400, h121 wrote:
> > Short:
> > I'm looking for a front-end tool to help me process
> > (qualify and classify / catalog) about 10,000 scanned images.
> You may want to have a look at KimDaBa.
I second the recommendation. A little more information:
KimDaBa uses an XML file to store all of the image metadata. While this
solution isn't ideal for huge image databases, because it has to load the
entire metadata database into RAM to get reasonable performance, it will be
just fine with only 10,000 images (I have about 7,000 images in mine). Once
all of the metadata is in XML format, you can write a little code to put it
in any other format you like.
KimDaBa supports arbitrary classification schemes. Basically, you define a
set of categories (you called them dimensions), and the values for each
category. The image classification window is customizable, so you can
arrange the defined categories for convenience. Though it may not be
applicable for your application, you can also define groups within a
category. Groups contain values or other groups.
After images are categorized, you can drill down pretty much any way you like.
Selecting one criterion, then another, then another, until you've identified
the set of images you want, or at least narrowed it down far enough to make a
manual search reasonable.
KimDaBa will also allow you to "mark up" images, rotating them, drawing on
them, etc., but all of the modifications are stored as metadata, without
modifying the actual image file. When you display the photo with KimDaBa,
the markup is visible, the image is rotated, etc.
KimDaBa reads date/time and rotation data from EXIF, if available.
One thing KimDaBa does not do (AFAIK) well is provide convenient ways to zoom
in. Also, it's a bit slow to display each image. I think this is because it
just uses the KDE image code to decompress and display images, and it isn't
terribly fast. In a KDE photo manipulation tool I wrote, I had to resort to
trading off some RAM to cache the last few and the next few images. I think
JPEG decoding time was the biggest part of the problem, but frankly didn't
look into it that much after I found an acceptable solution.
Also, it sound like you might need something more flexible than KimDaBa's HTML
generation for the final image database.
One other plus, the primary author, Jasper Pedersen, is generally quite
responsive, so if you can make a case that some need of yours is likely to be
shared by others, he's likely to add your requested feature, and quickly.
The code is reasonably clean also, so if you're a C++ programmer you can
always look into adding whatever bits you need yourself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
Gimp-user mailing list