high sierra – to change the date based on exif data since export from Mac Photos shows date of export using exiftool

I used the following to change the Date Created to the actual date the photo was taken because exporting from Photos showed the date of export.
“for file in *; do SetFile -d “$(exiftool -p ‘$CreateDate’ -d ‘%m/%d/%Y %H:%M:%S’ “$file”)” “$file”; done”

I got the following warning:
“Warning: (minor) Adjusted MakerNotes base by 46 – IMG_1369.JPG” — what does this mean?

I found the above suggestion at this thread:
Export from Mac Photos app while keeping date created data?

Also what is the cmd to change “Date Modifed” using exiftool?

Thanks.

applescript – Add exif creation time with correct timezone (TZD) to filename

Hi i have a problem renaming a lot of photo and images files. I use a shellscript in automator to rename them by EXIF date and time. But the time is given by UTC and im living in europe with +0100 in vinter and +0200 in the summer.

Example: a picture from 2020-06-30 taken at 22:22:30
is named “2020-06-30 20/22/30 IMG_0001.jpg
instead of. “2020-06-30 22/22/30 IMG_0001.jpg

im using the script:

#/bin/zsh
for f in "$@"
do
    filedate=$(mdls $f | grep kMDItemContentCreationDate -m 1 | awk '{print $3, $4}');
    filename=$f:t
    filepath=$f:h
    mv $filepath/{"$filename","$filedate $filename"}
done

Can i somehow just add +0200 or +0100 to the “filedate…$4” and how?(and then manually order when the number of houser in the name is over 24) or is there a smarter way to ad time zone designator(TZD) to the script? I have not used script before so im completely new to all this. Hopw someone can help me.

focal length – How to estimate pixels per degree for an image from a camera phone using EXIF data?

I assume this is a still frame from a video, because 16:9 is a common video ratio. In order to maintain constant frame size, “digital zooming” needs to be reinterpolated. Thus, yes, you need to account for the “zoom ratio” by factoring in 1.4 times the focal length.

However, your calculations are off, because a “1/3.1-inch” sensor is not actually 1/3.1″ in dimension. This is understandably very confusing, but it is merely a nomenclature referring to old circular 1″ video tubes, which had a useful diagonal of about 16 mm, far from the actual 25.4 mm in an actual inch. See also, Why is a 1″ sensor actually 13.2 × 8.8mm?

It took a little bit of Google searching, but I found the Sony Experia XA (Sony F3115) has a Sony EXMOR IMX258 sensor. Wikipedia’s EXMOR article says the sensor is a 1/3.06″ format, with a diagonal of 5.867 mm, and a pixel pitch of 1.12 µm. At 3.5 mm (the lens focal length), a 1.12 µm pixel subtends atan(0.00112 / (3.5 * 1.4)) = 0.0131°. Or if you prefer, 1/0.0131 = 76.4°/pixel at the center of the image. This distinction is important because near the edges, a 1.12 µm distance subtends a smaller angle — this is the nature of the tangent function.

A 400-pixel region subtends an arc of 2 * atan((0.00112 * 400 / 2) / (3.5 * 1.4)) = 5.23°

Normally, a very useful reference is Wikipedia’s table of sensor format and sizes. Unfortunately, it doesn’t list a 1/3.06″ sensor. It does list a 1/3.09″ Sony EXMOR IMX351 sensor, which is fairly close though.

exif – Rotated images on PHP Mpdf

I have a lot of photos on a web and we show them on a PDF that was created with Mpdf in PHP from an HTML source.

Here's an example:

    $mpdf = new MpdfMpdf(('tempDir' => $MPDF_TEMP_DIR));
    $html = "";
    $mpdf->WriteHTML($html);
    $mpdf->Output();

The problem is that in some cases the photos are rotated 90 degrees (exif rotation on some Samsung smartphones) and we cannot display them properly.

I'm sorry about my english =)

Software – Is there hope for Exif TimeZoneOffset as standard?

@mattdm: According to the MWG specification, the treatment of metadata data (Original DateTime, Digitalized DateTime, DateTime) should result in both XMP and EXIF ​​being updated.

However, the correct handling of metadata is a nightmare in most cases, especially because there are many providers who do not meet official specifications when writing metadata.

Daminion does not take the EXIF ​​TimeZoneOffset tag into account. However, take into account the XMP time zone information, because the XMP specification formats date / time values ​​according to the Date and Time (W3C) document. In this standard, a time zone identifier is required if time information is available. So if there is an XMP block in an image along with the time information, you can extract the time zone information from XMP. If there is no XMP block and non-standard EXIF ​​TimeZone information is missing, you can try to find TimeZone in the EXIF: GPS block.