oops66 wrote:Hello,m.Th. wrote:...1. Do you have the formulae? ...
Some are already here (a link into the previous exiftool link- ~/.ExifTool_config ) :
...But about composite data/fields ... it will be IMHO for the future (After the v1.0 MP release)
+1, why not, it's a good idea.I think that we'll have two+one tables:
- metadata1 for most used and most often - high-performance table - mainly the EXIF info
- metadata2 which will act like a L2 cache, mainly for big texts (mainly IPTC info) which aren't so often entered and sought
I checked some formulas - it isn't a problem to have composite fields - in fact is the same thing. We don't need the SQRT. The much bigger problem is to delay a base field which will be needed for calculations, because now it is easy to do the conversion from Meta BLOB (assuming that it has all the data) or even to delete the all uncatalogged files from Images table (the 'Clean files' option from 'Optimize' button) and refill the metadata tables from the disk.
But when this metadata will become important for search / statistical purposes then isn't so nice to delete (and/or upgrade) 10000 photos just because you left out one field.
Istm that one of the most important parameters is Circle of Confusion which is calculated as d/1500 where "d" is the sensor's diagonal in millimeters. Yes, this implies a SQRT but we'll calculate it in C++ and store it in the DB but it is very efficient in storage because we will store it next to camera model (and not for each photo).
Do you know how to calculate it using only EXIF data?
Hint: I think that's something related to FocalPlane values (but I might be wrong).
PS: About the v1.0 - I would see it ASAP. But we must finish the on-disk file management, fix keywords/categories engine and some "Ugly, Cover page & Unfinished" bugs - like
...and others. The ones who will take the 1.0 to not feel 'unsafe' because they have an 'unfinished' / 'in-construction' product.