Skip to content

ExifTag.GPSLatitudeRef gets resolved to ExifTagValue.InteroperabilityIndex #1992

Description

@eangelov

Prerequisites

  • I have written a descriptive issue title
  • I have verified that I am running the latest version of ImageSharp
  • I have verified if the problem exist in both DEBUG and RELEASE mode
  • 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"
image
image

Steps to Reproduce

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

System Configuration

  • Packages:
    image

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

  • .NET Framework version: .Net 6.0

Activity

  1. dlemstra commented on Feb 12, 2022

    @dlemstra
    Member

    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.

  2. eangelov commented on Feb 14, 2022

    @eangelov
    Author

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

  3. JimBobSquarePants commented on Mar 8, 2022

    @JimBobSquarePants
    Member

    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

  4. added this to the Future milestone on Mar 15, 2022
  5. bjh0 commented on Nov 6, 2022

    @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.

  6. JimBobSquarePants commented on Nov 7, 2022

    @JimBobSquarePants
    Member

    We should split up the enum for V3.

  7. JimBobSquarePants commented on Sep 27, 2023

    @JimBobSquarePants
    Member

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

  8. JimBobSquarePants commented on Jun 6, 2025

    @JimBobSquarePants
    Member

    I've been re-reviewing this and I don't see now why we cannot remove the tag entry. It's not used anywhere.

    I'll also backport the fix for V3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions