Skip to content

Comments

fix: respect explicit GPS ref values during write#24

Merged
lodev09 merged 1 commit intomainfrom
fix/gps-ref-write
Feb 9, 2026
Merged

fix: respect explicit GPS ref values during write#24
lodev09 merged 1 commit intomainfrom
fix/gps-ref-write

Conversation

@lodev09
Copy link
Owner

@lodev09 lodev09 commented Feb 9, 2026

Summary

Fixes #12. write() now respects explicit GPSLatitudeRef, GPSLongitudeRef, and GPSAltitudeRef values when provided alongside coordinates, instead of always deriving direction from the sign of the coordinate value.

This fixes the read→write round-trip where GPSLongitudeRef: 'W' with a positive longitude would be incorrectly overwritten to 'E'.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Test Plan

  • Long-press library button in example app to run read→write→verify round-trip
  • Tested on iOS with a photo containing western longitude — GPSLongitudeRef: 'W' preserved correctly

Checklist

  • I tested on iOS
  • I tested on Android
  • I updated the documentation (if needed)

@lodev09 lodev09 merged commit 0b072cd into main Feb 9, 2026
3 checks passed
@lodev09 lodev09 deleted the fix/gps-ref-write branch February 9, 2026 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

writeAsync() does not respect direction of latitude/longitude

1 participant