ExifTag.GPSLatitudeRef gets resolved to ExifTagValue.InteroperabilityIndex

[eangelov]

Prerequisites

• [X] I have written a descriptive issue title
• [X] I have verified that I am running the latest version of ImageSharp
• [X] I have verified if the problem exist in both DEBUG and RELEASE mode
• [X] I have searched open and closed issues to ensure it has not already been reported

Description

ExifTag.GPSLatitudeRef when converted to string is resolved as "InteroperabilityIndex"

Steps to Reproduce

using SixLabors.ImageSharp.Metadata.Profiles.Exif;
Console.WriteLine( ExifTag.GPSLatitudeRef );

System Configuration

• Packages:

• Environment (Operating system, version and so on):

• .NET Framework version: .Net 6.0

[dlemstra]

Both ExifTagValue.InteroperabilityIndex and ExifTagValue.GPSLatitudeRef have the same value and it looks like the first value is displayed when the metadata is displayed so this is not an issue. I do wonder if we should remove the ExifTagValue.InteroperabilityIndex value @JimBobSquarePants.

[eangelov]

After doing a quick search in Magick.NET it looks like InteroperabilityIndex is not included in ExifTagValue, removing it looks reasonable.

[JimBobSquarePants]

Removing the value prevents us ever supporting the tag. ExifTagValue should actually be 3 different enums.

https://www.awaresystems.be/imaging/tiff/tifftags/privateifd/interoperability.html

[bjh0]

I came here to make a similar report, and found this issue already open. @dlemstra's comment is not true for me: ExifTagValue.InteroperabilityIndex has the value that I would expect to find in ExifTagValue.GPSLatitudeRef, and ExifTagValue.GPSLatitudeRef has no value at all.

[JimBobSquarePants]

We should split up the enum for V3.

[JimBobSquarePants]

This never made V3 but we should target V4 for this.