No subject
Wed Apr 17 13:17:15 BST 2019
Exif.GPSInfo.GPSImgDirection Rational Indicates the direction of the image
when it was captured. The range of values is from 0.00 to 359.99.
Second, storage format: Is a double floating point number ok?
yes, certainly...
> (I.e. to fully specify the position of an image in space,
> > horizontal and vertical FOV have to be known, which
> > can be obtained from the lense properties.
> > and three angles for the direction and the two possible directions
> > to tilt a camera in space.
> > This can then be used to create photoverlays with googleearth
> >
> >
> http://code.google.com/apis/kml/documentation/kml_tags_beta1.html#photoover
> >lay or make use of gipfel
> > http://www.ecademix.com/JohannesHofmann/gipfel.html
> >
> > - not sure about this one:
> >
> > Without giving it too much thought, I think a date may be a useful
> field
> > to store too (thinking ahead to comments pulled in from external
> sources.
> >
> > I'd go for a table along the following lines:
> > imageid INTEGER
> > date DATETIME (optional)
>
> Date is in the comments table now.
>
> > lang TEXT (optional)
> > source TEXT (optional)
> > author TEXT (optional)
> > comment TEXT
> >
> > - Another thing which may be important to store in the database is
> > information concerning movies:
> > length, frame number of the thumnail used, ....
>
> -> I want to concentrate and specialize in images. I hope to get such info
> from strigi/nepomuk
>
> >
> > Generell points:
> > - Only include displayable files in the database:
> > http://bugs.kde.org/show_bug.cgi?id=145743
>
> This should already be implemented in trunk.
>
> >
> > - Action lists:
> > http://bugs.kde.org/show_bug.cgi?id=125387
> > http://bugs.kde.org/show_bug.cgi?id=103350
> > (presumably some more bugs ...)
>
> Later, as said above.
>
Marcel, Standard Exif + Makernotes + standard IPTC tags are listed and
described at this url :
http://www.exiv2.org/metadata.html
Supported Xmp tags are not yet listed in this page. Look into this file for
details :
http://dev.robotbattle.com/~cvsuser/cgi-bin/ns_viewcvs.cgi/exiv2/trunk/src/properties.cpp?rev=1251&view=auto
Gilles
------=_Part_39638_21665422.1191833996038
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">2007/10/7, Marcel Wiesweg <<a href="mailto:marcel.wiesweg at gmx.de">marcel.wiesweg at gmx.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Hi Marcel,<br>><br>> I went through all the messages in this thread<br>> and tried to compare with your DBSCHEMA.ODS<br>> <a href="http://websvn.kde.org/trunk/extragear/graphics/digikam/DBSCHEMA.ODS?view=lo">
http://websvn.kde.org/trunk/extragear/graphics/digikam/DBSCHEMA.ODS?view=lo</a><br>><br><br>Arnd the reply is late but your message did not go unnoticed ;-)<br>Rather it reached me just in time for my holidays.<br><br>
><br>> I have found a few points which are not listed<br>> (very likely on purpose ;-), but let me still mention them here<br>> (note that this list partially contains verbatim copies<br>><br>> >from the original messages):
<br>><br>> - Table Tags:<br>> - comments for tags<br>> (This would for example allow to provide additional information<br>> about a person, or animal, or landscape, ...<br>> I.e., something which would not make sense to
<br>> add to the comment of each of the corresponding<br>> images, because it is just the same/generally applicable)<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=149372">http://bugs.kde.org/show_bug.cgi?id=149372
</a><br><br>I have not changed anything in tabs and albums so far. All the other ideas<br>like grouping, stored actions etc. have to wait I fear if we want to get out<br>digikam 0.10 in a timely manner.</blockquote><div><br>
agree.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">At least, currently I am struggling to get everything right for image-specific
<br>fields in the db.<br><br>> - additional boolean flag: visible/hidden<br>> (i.e. all images tagged by a tag marked<br>> hidden are not shown, i.e. private images etc.)<br><br>Same as above.<br><br>>
<br>> - Grouping of images<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=121310">http://bugs.kde.org/show_bug.cgi?id=121310</a><br>> (Coming from panoramae, or bracketed shots for HDR).<br>> Within a group it should be possible to select
<br>> which images are visible (i.e also more than one).<br>><br>> This would also allow to group JPG and RAWs together<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=147427">http://bugs.kde.org/show_bug.cgi?id=147427
</a><br><br>Yes I want that. but see above.<br><br>><br>> - And what about to Tag Album as well (to replace "collection"<br>> properties?) :<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=133011">
http://bugs.kde.org/show_bug.cgi?id=133011</a><br><br>idem<br><br>><br>> - ImageInformation or ImageMetadata (?):<br>> - technical quality tags<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=128333">http://bugs.kde.org/show_bug.cgi?id=128333
</a><br><br>Seems to me this needs quite a bit of research still<br><br>><br>> - Associate a region in an image with a tag:<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=146337">http://bugs.kde.org/show_bug.cgi?id=146337
</a><br>><br>> Note that such a region should not be a property of a tag,<br>> but a property of an image. Example:<br>> If there are several persons on one image, one can<br>> first add the Person's names as tags to that image (as right now).
<br>> In addition, one may mark the region of the face<br>> and associate it with the tag.<br>> Image:<br>> Tags: - Name1<br>> - Name2<br>> - Name3<br>> Regions: - Region1 --> Tag Name1
<br>> - Region2 --> Tag Name2<br>><br>> Not sure how to put this in the database scheme ...<br>> To specify the region: the simplest are rectangles,<br>> but one should also think of more complicated shapes
<br>> (circle, ellipse, general svg paths) in the longer run.<br>> So it might be good to keep this in mind already when setting<br>> up the database scheme.<br><br>Yes. At least points. Later!<br><br>><br>
> - Table ImageMetadata:<br>> - lens type (focal range in 35mm equivalent is available in Makernotes)<br><br>This is from Makernote?</blockquote><div><br>focal Length info, is avaialble from standard Exif :<br><br>
==> Exif.Photo.FocalLength Rational The actual focal length of the lens, in mm. Conversion is not made to the focal length of a 35 mm film camera.<br><br>==> Exif.Photo.FocalLengthIn35mmFilm Short This tag indicates the equivalent focal length assuming a 35mm film camera, in mm. A value of 0 means the focal length is unknown. Note that this tag differs from the <FocalLength> tag.
</div><br>but _not_ lens type witch is stored by Makernotes. Problem is than all camera maker use a dedicaced way to provide this info. For ex.:<br><br>==> Exif.Nikon3.LensType Byte Lens type<br>==> Exif.Minolta.LensID
Long <br>==> Exif.CanonCs.Lens Short 'long' and 'short' focal length of lens (in 'focal units') and 'focal units' per mm<br><br>In other words, this will be infernal to get this info easily. But... Xmp provide has a tag to simplify this task :
<br><br>==> Xmp.Aux.Lens Text A description of the lens used to take the photograph. For example, "70-200 mm f/2.8-4.0"<br><br>This will be the ultimate solution... when we will have implemented in Exiv2 core (not libkexiv2) a wrapper to import Exif (and Iptc) to Xmp ( and vis-versa)
<br><br>This is not yet done, but it's planed. This is why i recommend to delay all Makernotes informations extraction dedicaced to fill the new DB contents.<br><br>Note : XMP support all standard Exif/Iptc tags as well (more and better), but not Makernotes in standard. Yes, in this case all metadata will be duplicated but Xmp will become the full replacement of Exif and Iptc.
<br><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> - focus mode<br><br>= MeteringMode or ExposureProgram?<br>We'll have both in db
<br><br>> - macro<br><br>We will have SubjectDistanceRange<br><br>> - stabilization</blockquote><div><br>==> Makernote. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> - focus point (can be quite camera dependent)</blockquote><div><br>==> Makernote. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> <a href="http://bugs.kde.org/show_bug.cgi?id=138704">http://bugs.kde.org/show_bug.cgi?id=138704</a><br>> - panorama mode</blockquote><div><br>==> Makernote. </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What is this? Any exif keys?<br><br><br>> - perhaps few original informations from pictures taken from camera as<br>> org. size, org. date, org. filename, cmaera serial number, UUID of<br>> media, etc. to perform detection of already downloaded pictures for
<br>> camera gui. This way is under discussion...<br><br>Yes! This is in the works<br><br>><br>> - Table GPS data<br>> - orientation (compass)<br>> - tilt (nb of degrees with regard to horizontal)<br>
> - roll<br><br>From where do I get these values? Can these be mapped to Exif GPS data? Or<br>where do you get this information from?</blockquote><div><br>From standard Exif :<br><br>Exif.GPSInfo.GPSImgDirection Rational Indicates the direction of the image when it was captured. The range of values is from
0.00 to 359.99.<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Second, storage format: Is a double floating point number ok?
</blockquote><div><br>yes, certainly...<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> (I.e. to fully specify the position of an image in space,
<br>> horizontal and vertical FOV have to be known, which<br>> can be obtained from the lense properties.<br>> and three angles for the direction and the two possible directions<br>> to tilt a camera in space.
<br>> This can then be used to create photoverlays with googleearth<br>><br>> <a href="http://code.google.com/apis/kml/documentation/kml_tags_beta1.html#photoover">http://code.google.com/apis/kml/documentation/kml_tags_beta1.html#photoover
</a><br>>lay or make use of gipfel<br>> <a href="http://www.ecademix.com/JohannesHofmann/gipfel.html">http://www.ecademix.com/JohannesHofmann/gipfel.html</a><br>><br>> - not sure about this one:<br>><br>
> Without giving it too much thought, I think a date may be a useful field<br>> to store too (thinking ahead to comments pulled in from external sources.<br>><br>> I'd go for a table along the following lines:
<br>> imageid INTEGER<br>> date DATETIME (optional)<br><br>Date is in the comments table now.<br><br>> lang TEXT (optional)<br>> source TEXT (optional)<br>> author TEXT (optional)<br>> comment TEXT
<br>><br>> - Another thing which may be important to store in the database is<br>> information concerning movies:<br>> length, frame number of the thumnail used, ....<br><br>-> I want to concentrate and specialize in images. I hope to get such info
<br>from strigi/nepomuk<br><br>><br>> Generell points:<br>> - Only include displayable files in the database:<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=145743">http://bugs.kde.org/show_bug.cgi?id=145743
</a><br><br>This should already be implemented in trunk.<br><br>><br>> - Action lists:<br>> <a href="http://bugs.kde.org/show_bug.cgi?id=125387">http://bugs.kde.org/show_bug.cgi?id=125387</a><br>> <a href="http://bugs.kde.org/show_bug.cgi?id=103350">
http://bugs.kde.org/show_bug.cgi?id=103350</a><br>> (presumably some more bugs ...)<br><br>Later, as said above.<br></blockquote></div><br>Marcel, Standard Exif + Makernotes + standard IPTC tags are listed and described at this url :
<br><br><a href="http://www.exiv2.org/metadata.html">http://www.exiv2.org/metadata.html</a><br><br>Supported Xmp tags are not yet listed in this page. Look into this file for details :<br><br><a href="http://dev.robotbattle.com/~cvsuser/cgi-bin/ns_viewcvs.cgi/exiv2/trunk/src/properties.cpp?rev=1251&view=auto">
http://dev.robotbattle.com/~cvsuser/cgi-bin/ns_viewcvs.cgi/exiv2/trunk/src/properties.cpp?rev=1251&view=auto</a><br><br>Gilles<br><br><br>
------=_Part_39638_21665422.1191833996038--
More information about the Digikam-devel
mailing list