Gps coordinates not read correctly from image

[jhmnieuwenhuis]

The attached image has exif gps info of : 52°28'11.676" N 6°27'7.668" E
Converted to decimal this is: 52.469910, 6.452130
I verfied this by pasting this into openstreetmap and it shows the correct location.

But if i upload it as an image in waymark it places it at the center of the displayed map, not at the embedded gps location.

[morehawes]

Hi @jhmnieuwenhuis, thanks for reaching out!

Strange, when I upload the image on my local setup it creates a Marker at the correct 52.469910,6.452130 location.

Do you see anything unusual in the console with Debug Mode enabled? I see the message:

[Waymark Debug] Image location metadata (EXIF) detected!

Media uploads and EXIF meta detection have always been a bit of a friction point because things can vary between environments.

[jhmnieuwenhuis]

When i add a new map and look at the browser console i see: {map_options: {…}, viewer_options: {…}, editor_options: {…}, image_size_names: Array(4), marker_type_defaults: {…}, …} When i add the image to the map, nothing is shown in the browser console Below the map in the Map data window i see : {"type":"FeatureCollection","features":[{"geometry":{"type":"Point","coordinates":[-68.751068,51.383781]},"type":"Feature","properties":{"type":"photo","image_thumbnail_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-150x100.jpg ","image_medium_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-300x200.jpg ","image_large_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-1024x683.jpg ","image_full_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm.jpg "}}]} Strange coordinates... Just noticed something : The images in my media library are uploaded from Lightroom using the lightroom-wordpress plugin from meow apps. If i place the original image that was uploaded to the media library using the meow apps plugin, it places it wrong. If i download that image from the media library to my hard drive and and import it again into the media library and use that image it is placed at the correct location. That is very strange, there should be no difference in the original image in the media library and the downloaded and then upladed again version.... I will investigate further. Regards, Hans Nieuwenhuis Mobiel : 06-53476697

…

On Mon, Jun 15, 2026 at 12:06 AM Joe Hawes ***@***.***> wrote: *morehawes* left a comment (OpenGIS/waymark-wp#73) <#73 (comment)> Hi @jhmnieuwenhuis <https://github.com/jhmnieuwenhuis>, thanks for reaching out! Strange, when I upload the image on my local setup it creates a Marker at the correct 52.469910,6.452130 location. Do you see anything unusual in the console with Debug Mode <https://www.ogis.org/waymark-wp/advanced/debug-mode/> enabled? I see the message: [Waymark Debug] Image location metadata (EXIF) detected! Media uploads and EXIF meta detection have always been a bit of a friction point because things can vary between environments. — Reply to this email directly, view it on GitHub <#73?email_source=notifications&email_token=ADH3QBVCYZE7RV3CL4CD2AL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4703224561>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADH3QBTG76NTYLRZ6REX7RT474OX3AVCNFSNUABFKJSXA33TNF2G64TZHMZDQOJQGYZDIMRVHNEXG43VMU5TINRVGYZTKMZYGYY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ADH3QBXISLHDA6QQQFEWMTT474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ADH3QBRXNOTGHAW3KXNYPPL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[jhmnieuwenhuis]

I investigated further with assistance from claude ai. It came up wth an old threat: https://wordpress.org/support/topic/some-issues-54/ It also described the issue ~: I found the answer, and it confirms it's a WordPress database issue, not a file issue. The key is the first result — a support thread describing your exact symptom. Two things from Waymark's developer (Joe) in that thread: First, the symptom is documented. When you take the image from the media library it is not placed correctly on the map, but if you upload it through the WordPress media uploader within Waymark, it works. That's precisely your case: media-library image lands in the middle of the map, re-uploaded image lands correctly. WordPress Second, the root cause: For Waymark to access them, the coordinates need to be stored as GPSLatitudeNum and GPSLongitudeNum. And the decisive line from the same thread: WordPress doesn't store the location tag in the database — but the image itself still has the coordinates. WordPressWordPress So here's what's actually happening. When you pick an image from the media library, Waymark does not re-parse the JPEG's EXIF off disk. It looks for GPS in the WordPress attachment metadata stored in the database — specifically numeric fields GPSLatitudeNum / GPSLongitudeNum. WordPress core does not populate those by default (core's wp_read_image_metadata() extracts camera, exposure, caption, keywords, etc., but not GPS). They only get written when an image goes through the normal WordPress media-upload pipeline with something that extracts and stores the numeric GPS — which is what happens on your re-upload. Your WP/LR-synced images were created programmatically by the WP-LR plugin, which bypasses that normal pipeline. The JPEG on disk has perfect GPS (your exiftool output proves it — both files are identical), but the database row for that attachment has no GPSLatitudeNum/GPSLongitudeNum. Waymark queries the database, finds nothing, and drops the marker in the center of the map. When you download and re-import, the normal upload path runs, the numeric GPS gets written to the database, and Waymark finds it. That's why two byte-identical files behave differently: the difference isn't in the file, it's in the WordPress postmeta table. So the fix is to populate those numeric GPS fields in the database for your WP-LR images, rather than touch the files at all. A few routes: The cleanest is the one Joe himself points to in that thread — a plugin that extends the media library to read and store GPS as custom fields (he mentions Media Library Assistant for adding the fields). But the most direct fix is a small script that, for each WP-LR attachment, reads the GPS from the file with exif_read_data() and writes GPSLatitudeNum / GPSLongitudeNum into the attachment's _wp_attachment_metadata['image_meta']. That backfills exactly what Waymark looks for, in one pass over your library, without re-uploading anything. Before I write that, one thing worth checking so I target the right field: it would help to confirm how the working (re-imported) image stores its coordinates in the database. Want me to give you a short WP-CLI / PHP snippet to dump _wp_attachment_metadata for both a working and a non-working attachment? Comparing those two will show the exact key name Waymark reads, and then I can write a backfill script that's guaranteed to match. b.t.w. I love this claude ai assistance, it saves me so much time . It is not always right but most of the time it is. I think claude can write a plugin to fix this, i will let you know Regards, Hans Nieuwenhuis Mobiel : 06-53476697 On Mon, Jun 15, 2026 at 8:13 AM Hans Nieuwenhuis ***@***.***> wrote:

…

When i add a new map and look at the browser console i see: {map_options: {…}, viewer_options: {…}, editor_options: {…}, image_size_names: Array(4), marker_type_defaults: {…}, …} When i add the image to the map, nothing is shown in the browser console Below the map in the Map data window i see : {"type":"FeatureCollection","features":[{"geometry":{"type":"Point","coordinates":[-68.751068,51.383781]},"type":"Feature","properties":{"type":"photo","image_thumbnail_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-150x100.jpg ","image_medium_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-300x200.jpg ","image_large_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-1024x683.jpg ","image_full_url":" https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm.jpg "}}]} Strange coordinates... Just noticed something : The images in my media library are uploaded from Lightroom using the lightroom-wordpress plugin from meow apps. If i place the original image that was uploaded to the media library using the meow apps plugin, it places it wrong. If i download that image from the media library to my hard drive and and import it again into the media library and use that image it is placed at the correct location. That is very strange, there should be no difference in the original image in the media library and the downloaded and then upladed again version.... I will investigate further. Regards, Hans Nieuwenhuis Mobiel : 06-53476697 On Mon, Jun 15, 2026 at 12:06 AM Joe Hawes ***@***.***> wrote: > *morehawes* left a comment (OpenGIS/waymark-wp#73) > <#73 (comment)> > > Hi @jhmnieuwenhuis <https://github.com/jhmnieuwenhuis>, thanks for > reaching out! > > Strange, when I upload the image on my local setup it creates a Marker at > the correct 52.469910,6.452130 location. > > Do you see anything unusual in the console with Debug Mode > <https://www.ogis.org/waymark-wp/advanced/debug-mode/> enabled? I see > the message: > > [Waymark Debug] Image location metadata (EXIF) detected! > > Media uploads and EXIF meta detection have always been a bit of a > friction point because things can vary between environments. > > — > Reply to this email directly, view it on GitHub > <#73?email_source=notifications&email_token=ADH3QBVCYZE7RV3CL4CD2AL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4703224561>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADH3QBTG76NTYLRZ6REX7RT474OX3AVCNFSNUABFKJSXA33TNF2G64TZHMZDQOJQGYZDIMRVHNEXG43VMU5TINRVGYZTKMZYGYY2C5QC> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/ADH3QBXISLHDA6QQQFEWMTT474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> > and Android > <https://github.com/notifications/mobile/android/ADH3QBRXNOTGHAW3KXNYPPL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. > Download it today! > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[jhmnieuwenhuis]

It is fixed ( by a workaround) , see attached Php code Regards, Hans Nieuwenhuis Mobiel : 06-53476697 On Mon, Jun 15, 2026 at 8:40 AM Hans Nieuwenhuis ***@***.***> wrote:

I investigated further with assistance from claude ai. It came up wth an old threat: https://wordpress.org/support/topic/some-issues-54/ It also described the issue ~: I found the answer, and it confirms it's a WordPress database issue, not a file issue. The key is the first result — a support thread describing your exact symptom. Two things from Waymark's developer (Joe) in that thread: First, the symptom is documented. When you take the image from the media library it is not placed correctly on the map, but if you upload it through the WordPress media uploader within Waymark, it works. That's precisely your case: media-library image lands in the middle of the map, re-uploaded image lands correctly. WordPress Second, the root cause: For Waymark to access them, the coordinates need to be stored as GPSLatitudeNum and GPSLongitudeNum. And the decisive line from the same thread: WordPress doesn't store the location tag in the database — but the image itself still has the coordinates. WordPressWordPress So here's what's actually happening. When you pick an image from the media library, Waymark does not re-parse the JPEG's EXIF off disk. It looks for GPS in the WordPress attachment metadata stored in the database — specifically numeric fields GPSLatitudeNum / GPSLongitudeNum. WordPress core does not populate those by default (core's wp_read_image_metadata() extracts camera, exposure, caption, keywords, etc., but not GPS). They only get written when an image goes through the normal WordPress media-upload pipeline with something that extracts and stores the numeric GPS — which is what happens on your re-upload. Your WP/LR-synced images were created programmatically by the WP-LR plugin, which bypasses that normal pipeline. The JPEG on disk has perfect GPS (your exiftool output proves it — both files are identical), but the database row for that attachment has no GPSLatitudeNum/GPSLongitudeNum. Waymark queries the database, finds nothing, and drops the marker in the center of the map. When you download and re-import, the normal upload path runs, the numeric GPS gets written to the database, and Waymark finds it. That's why two byte-identical files behave differently: the difference isn't in the file, it's in the WordPress postmeta table. So the fix is to populate those numeric GPS fields in the database for your WP-LR images, rather than touch the files at all. A few routes: The cleanest is the one Joe himself points to in that thread — a plugin that extends the media library to read and store GPS as custom fields (he mentions Media Library Assistant for adding the fields). But the most direct fix is a small script that, for each WP-LR attachment, reads the GPS from the file with exif_read_data() and writes GPSLatitudeNum / GPSLongitudeNum into the attachment's _wp_attachment_metadata['image_meta']. That backfills exactly what Waymark looks for, in one pass over your library, without re-uploading anything. Before I write that, one thing worth checking so I target the right field: it would help to confirm how the working (re-imported) image stores its coordinates in the database. Want me to give you a short WP-CLI / PHP snippet to dump _wp_attachment_metadata for both a working and a non-working attachment? Comparing those two will show the exact key name Waymark reads, and then I can write a backfill script that's guaranteed to match. b.t.w. I love this claude ai assistance, it saves me so much time . It is not always right but most of the time it is. I think claude can write a plugin to fix this, i will let you know Regards, Hans Nieuwenhuis Mobiel : 06-53476697 On Mon, Jun 15, 2026 at 8:13 AM Hans Nieuwenhuis ***@***.***> wrote: > When i add a new map and look at the browser console i see: > > {map_options: {…}, viewer_options: {…}, editor_options: {…}, > image_size_names: Array(4), marker_type_defaults: {…}, …} > > When i add the image to the map, nothing is shown in the browser console > > Below the map in the Map data window i see : > > > {"type":"FeatureCollection","features":[{"geometry":{"type":"Point","coordinates":[-68.751068,51.383781]},"type":"Feature","properties":{"type":"photo","image_thumbnail_url":" > https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-150x100.jpg > ","image_medium_url":" > https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-300x200.jpg > ","image_large_url":" > https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm-1024x683.jpg > ","image_full_url":" > https://landschapoost.nl/wp-content/uploads/2026/06/20260612-r52_0437-tif_wm.jpg > "}}]} > > Strange coordinates... > > Just noticed something : > > The images in my media library are uploaded from Lightroom using the > lightroom-wordpress plugin from meow apps. > > If i place the original image that was uploaded to the media library > using the meow apps plugin, it places it wrong. > If i download that image from the media library to my hard drive and > and import it again into the media library > and use that image it is placed at the correct location. > > That is very strange, there should be no difference in the original image > in the media library and the downloaded and then upladed again version.... > > I will investigate further. > > Regards, > > Hans Nieuwenhuis > Mobiel : 06-53476697 > > > On Mon, Jun 15, 2026 at 12:06 AM Joe Hawes ***@***.***> > wrote: > >> *morehawes* left a comment (OpenGIS/waymark-wp#73) >> <#73 (comment)> >> >> Hi @jhmnieuwenhuis <https://github.com/jhmnieuwenhuis>, thanks for >> reaching out! >> >> Strange, when I upload the image on my local setup it creates a Marker >> at the correct 52.469910,6.452130 location. >> >> Do you see anything unusual in the console with Debug Mode >> <https://www.ogis.org/waymark-wp/advanced/debug-mode/> enabled? I see >> the message: >> >> [Waymark Debug] Image location metadata (EXIF) detected! >> >> Media uploads and EXIF meta detection have always been a bit of a >> friction point because things can vary between environments. >> >> — >> Reply to this email directly, view it on GitHub >> <#73?email_source=notifications&email_token=ADH3QBVCYZE7RV3CL4CD2AL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4703224561>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ADH3QBTG76NTYLRZ6REX7RT474OX3AVCNFSNUABFKJSXA33TNF2G64TZHMZDQOJQGYZDIMRVHNEXG43VMU5TINRVGYZTKMZYGYY2C5QC> >> . >> Triage notifications, keep track of coding agent tasks and review pull >> requests on the go with GitHub Mobile for iOS >> <https://github.com/notifications/mobile/ios/ADH3QBXISLHDA6QQQFEWMTT474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> >> and Android >> <https://github.com/notifications/mobile/android/ADH3QBRXNOTGHAW3KXNYPPL474OX3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQGMZDENBVGYY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. >> Download it today! >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >

<?php // Backfill GPSLatitudeNum/GPSLongitudeNum into image_meta from existing // geo_latitude/geo_longitude, so Waymark can read WP-LR synced images. // Run as a one-time Code Engine snippet (back-end). // --- CONFIG --------------------------------------------------------- $APPLY = true; // false = dry run (no changes). Set true to write. $ONLY_ID = 1; // set to a single attachment ID to test one image, // or 0 to process the whole media library. // -------------------------------------------------------------------- if ( $ONLY_ID ) { $ids = array( (int) $ONLY_ID ); } else { $ids = get_posts( array( 'post_type' => 'attachment', 'post_mime_type' => 'image', 'posts_per_page' => -1, 'fields' => 'ids', ) ); } $updated = 0; $skipped = 0; $lines = array(); foreach ( $ids as $id ) { $meta = wp_get_attachment_metadata( $id ); if ( empty( $meta['image_meta'] ) ) { continue; } $im = $meta['image_meta']; if ( isset( $im['GPSLatitudeNum'], $im['GPSLongitudeNum'] ) ) { $skipped++; continue; } if ( ! isset( $im['geo_latitude'], $im['geo_longitude'] ) || $im['geo_latitude'] === '' || $im['geo_longitude'] === '' ) { continue; } $lat = (float) $im['geo_latitude']; $lng = (float) $im['geo_longitude']; $im['GPSLatitudeNum'] = $lat; $im['GPSLongitudeNum'] = $lng; $im['GPSLatitudeRef'] = $lat >= 0 ? 'N' : 'S'; $im['GPSLongitudeRef'] = $lng >= 0 ? 'E' : 'W'; $meta['image_meta'] = $im; $lines[] = sprintf( '%s #%d %F, %F', $APPLY ? 'UPDATE' : 'DRYRUN', $id, $lat, $lng ); if ( $APPLY ) { wp_update_attachment_metadata( $id, $meta ); } $updated++; } $lines[] = sprintf( '--- %s: %d affected, %d already had GPSNum ---', $APPLY ? 'APPLIED' : 'DRY RUN', $updated, $skipped ); echo "<pre>" . esc_html( implode( "\n", $lines ) ) . "</pre>";

[morehawes]

Hi @jhmnieuwenhuis,

Thanks for the extra detail, however I am not seeing this issue. With Waymark activated, when I:

1. Upload your image to the Media Library and then add to Map
2. Add directly through the Map

Both times it adds the Image to the correct location.

With Waymark activated, it should read the non-standard GPSLatitudeNum / GPSLongitudeNum metadata and store them in the post meta table. You can see these in the database directly, or using a plugin like Media Library Assistant which adds extrac information to the Media Library:

I recommend checking this to see if the EXIF metadata is displayed here after uploading an image with Waymark installed.

Also note that:

By default, WordPress does not store location metadata when you upload a photo, this capability is added by Waymark. Because of this, Waymark can not read the location metadata of photos uploaded to the Media Library while Waymark was not active. So even if location metadata is contained in the original file, Waymark can not access it.

I hope you find that useful.

Joe

[jhmnieuwenhuis]

In my case the images are uploaded to the media library by the wplr-sync plugins. One plugin in Lightroom and one in Wordpress/ So i do not upload these myself in wordpress. See: https://meowapps.com/wplr-sync/ With the help of claude i had a look at the gps data in images uploaded to the media library from within wordpress and images uploaded trough the wplr-sync plugins. I saw that in the wplr-sync ones GPSLatitudeNum / GPSLongitudeNum where empty. Regards, Hans Nieuwenhuis Mobiel : 06-53476697

…

On Mon, Jun 15, 2026 at 5:58 PM Joe Hawes ***@***.***> wrote: *morehawes* left a comment (OpenGIS/waymark-wp#73) <#73 (comment)> Hi @jhmnieuwenhuis <https://github.com/jhmnieuwenhuis>, Thanks for the extra detail, however I am not seeing this issue. With Waymark activated, when I: 1. Upload your image to the Media Library and then add to Map 2. Add directly through the Map Both times it adds the Image to the correct location. With Waymark activated, it should read the non-standard GPSLatitudeNum / GPSLongitudeNum metadata and store them in the post meta table. You can see these in the database directly, or using a plugin like Media Library Assistant <https://wordpress.org/plugins/media-library-assistant/> which adds extrac information to the Media Library: Screenshot.2026-06-15.at.8.52.28.AM.png (view on web) <https://github.com/user-attachments/assets/d25e7458-8e2f-4429-8c59-bee6bc0ec5d8> I recommend checking this to see if the EXIF metadata is displayed here after uploading an image with Waymark installed. Also note that: By default, WordPress does not store location metadata when you upload a photo, this capability is added by Waymark. Because of this, Waymark can not read the location metadata of photos uploaded to the Media Library while Waymark was not active. So even if location metadata is contained in the original file, Waymark can not access it. I hope you find that useful. Joe — Reply to this email directly, view it on GitHub <#73?email_source=notifications&email_token=ADH3QBVP5257REHY54DAQN35AAMKHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQHE3TSMBSGU22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4709790255>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADH3QBXETQ72AZLFZUQ6BYT5AAMKHAVCNFSNUABFKJSXA33TNF2G64TZHMZDQOJQGYZDIMRVHNEXG43VMU5TINRVGYZTKMZYGYY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ADH3QBR4AEKJFGRS4COSLIL5AAMKHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQHE3TSMBSGU22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ADH3QBUKZAG7RSRCRDRJ5KD5AAMKHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZQHE3TSMBSGU22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[morehawes]

Hi @jhmnieuwenhuis,

Waymark should still add the GPS data as long as you are in the WP Admin area, but it looks like there is a compatibility issue.

I am not familiar with that plugin, but I did find this (old) Gist from the author. Using this as a base, I created a version to get the EXIF data in the format that Waymark expects:

<?php

/**
 * Extract GPS EXIF data from uploaded media and save as post meta
 *
 * This gist hooks into Media Library Organizer's wplr_add_media and wplr_update_media
 * actions to automatically extract GPS coordinates from image EXIF data when images
 * are added or updated in galleries.
 *
 * It saves both the raw EXIF GPS data (degrees/minutes/seconds format) and decimal
 * coordinate values that can be used directly with mapping libraries.
 *
 * Based on the approach used by Waymark plugin for extracting GPS EXIF data
 */

add_action("wplr_add_media", 'myapp_update_gps_exif_meta', 10, 2);
add_action("wplr_update_media", 'myapp_update_gps_exif_meta', 10, 2);

function myapp_update_gps_exif_meta($mediaId, $galleryID) {
	// Require the PHP EXIF extension
	if (! function_exists('exif_read_data')) {
		return;
	}

	global $wplr;

	// Get the full image path
	$image = wp_get_attachment_url($mediaId);

	// Read EXIF data from the image
	$exif_data = exif_read_data($image);

	if (is_array($exif_data)) {

		// Extract Latitude data (requires both GPSLatitude and GPSLatitudeRef)
		if (array_key_exists('GPSLatitude', $exif_data) && array_key_exists('GPSLatitudeRef', $exif_data)) {
			// Store raw GPS latitude (array of degrees/minutes/seconds)
			update_post_meta($mediaId, 'GPSLatitude', $exif_data['GPSLatitude']);

			// Store latitude reference (N for North, S for South)
			update_post_meta($mediaId, 'GPSLatitudeRef', $exif_data['GPSLatitudeRef']);

			// Convert to decimal format for easy mapping (e.g., 51.5074)
			$decimal_lat = exif_gps_to_decimal($exif_data['GPSLatitude'], $exif_data['GPSLatitudeRef']);
			update_post_meta($mediaId, 'GPSLatitudeNum', $decimal_lat);
		}

		// Extract Longitude data (requires both GPSLongitude and GPSLongitudeRef)
		if (array_key_exists('GPSLongitude', $exif_data) && array_key_exists('GPSLongitudeRef', $exif_data)) {
			// Store raw GPS longitude (array of degrees/minutes/seconds)
			update_post_meta($mediaId, 'GPSLongitude', $exif_data['GPSLongitude']);

			// Store longitude reference (E for East, W for West)
			update_post_meta($mediaId, 'GPSLongitudeRef', $exif_data['GPSLongitudeRef']);

			// Convert to decimal format for easy mapping (e.g., -0.1278)
			$decimal_lon = exif_gps_to_decimal($exif_data['GPSLongitude'], $exif_data['GPSLongitudeRef']);
			update_post_meta($mediaId, 'GPSLongitudeNum', $decimal_lon);
		}
	}
}

/**
 * Convert GPS coordinates from EXIF format to decimal degrees
 *
 * EXIF GPS data is stored as an array of three rational numbers representing
 * degrees, minutes, and seconds. This function converts that format to a
 * single decimal number that mapping libraries can use.
 *
 * @param array  $coordinate Array of [degrees, minutes, seconds] as strings like "51/1"
 * @param string $hemisphere N, S, E, or W - determines positive/negative sign
 * @return float Decimal coordinate (e.g., 51.5074 or -0.1278)
 */
function exif_gps_to_decimal($coordinate, $hemisphere) {
	// Parse the degrees, minutes, and seconds from EXIF rational format
	// EXIF stores coordinates as "degrees/1", "minutes/1", "seconds/100" etc.
	for ($i = 0; $i < 3; $i++) {
		$part = explode('/', $coordinate[$i]);

		// Handle division by zero
		if (count($part) == 1) {
			$coordinate[$i] = $part[0];
		} else if (count($part) == 2) {
			$coordinate[$i] = floatval($part[0]) / floatval($part[1]);
		} else {
			$coordinate[$i] = 0;
		}
	}

	// Convert DMS (Degrees, Minutes, Seconds) to decimal degrees
	// Formula: decimal = degrees + (minutes/60) + (seconds/3600)
	$decimal = $coordinate[0] + ($coordinate[1] / 60) + ($coordinate[2] / 3600);

	// Apply negative sign for South and West hemispheres
	if ($hemisphere == 'S' || $hemisphere == 'W') {
		$decimal *= -1;
	}

	return $decimal;
}

This is completely untested, but you may find it helpful.

Cheers.

[jhmnieuwenhuis]

Thanks, I also asked the guys from meow if they can make a change to their plugin. Regards , Hans Nieuwenhuis Mobiel : 06-53476697 Op ma 15 jun 2026, 19:49 schreef Joe Hawes ***@***.***>:

…

*morehawes* left a comment (OpenGIS/waymark-wp#73) <#73 (comment)> Hi @jhmnieuwenhuis <https://github.com/jhmnieuwenhuis>, Waymark *should* still add the GPS data as long as you are in the WP Admin area, but it looks like there is a compatibility issue. I am not familiar with that plugin, but I did find this (old) Gist from the author <https://gist.github.com/jordymeow/22a365165c9757ed0014877c3fb4fbac>. Using this as a base, I created a version to get the EXIF data in the format that Waymark expects: <?php /** * Extract GPS EXIF data from uploaded media and save as post meta * * This gist hooks into Media Library Organizer's wplr_add_media and wplr_update_media * actions to automatically extract GPS coordinates from image EXIF data when images * are added or updated in galleries. * * It saves both the raw EXIF GPS data (degrees/minutes/seconds format) and decimal * coordinate values that can be used directly with mapping libraries. * * Based on the approach used by Waymark plugin for extracting GPS EXIF data */ add_action("wplr_add_media", 'myapp_update_gps_exif_meta', 10, 2);add_action("wplr_update_media", 'myapp_update_gps_exif_meta', 10, 2); function myapp_update_gps_exif_meta($mediaId, $galleryID) { // Require the PHP EXIF extension if (! function_exists('exif_read_data')) { return; } global $wplr; // Get the full image path $image = wp_get_attachment_url($mediaId); // Read EXIF data from the image $exif_data = exif_read_data($image); if (is_array($exif_data)) { // Extract Latitude data (requires both GPSLatitude and GPSLatitudeRef) if (array_key_exists('GPSLatitude', $exif_data) && array_key_exists('GPSLatitudeRef', $exif_data)) { // Store raw GPS latitude (array of degrees/minutes/seconds) update_post_meta($mediaId, 'GPSLatitude', $exif_data['GPSLatitude']); // Store latitude reference (N for North, S for South) update_post_meta($mediaId, 'GPSLatitudeRef', $exif_data['GPSLatitudeRef']); // Convert to decimal format for easy mapping (e.g., 51.5074) $decimal_lat = exif_gps_to_decimal($exif_data['GPSLatitude'], $exif_data['GPSLatitudeRef']); update_post_meta($mediaId, 'GPSLatitudeNum', $decimal_lat); } // Extract Longitude data (requires both GPSLongitude and GPSLongitudeRef) if (array_key_exists('GPSLongitude', $exif_data) && array_key_exists('GPSLongitudeRef', $exif_data)) { // Store raw GPS longitude (array of degrees/minutes/seconds) update_post_meta($mediaId, 'GPSLongitude', $exif_data['GPSLongitude']); // Store longitude reference (E for East, W for West) update_post_meta($mediaId, 'GPSLongitudeRef', $exif_data['GPSLongitudeRef']); // Convert to decimal format for easy mapping (e.g., -0.1278) $decimal_lon = exif_gps_to_decimal($exif_data['GPSLongitude'], $exif_data['GPSLongitudeRef']); update_post_meta($mediaId, 'GPSLongitudeNum', $decimal_lon); } } } /** * Convert GPS coordinates from EXIF format to decimal degrees * * EXIF GPS data is stored as an array of three rational numbers representing * degrees, minutes, and seconds. This function converts that format to a * single decimal number that mapping libraries can use. * * @param array $coordinate Array of [degrees, minutes, seconds] as strings like "51/1" * @param string $hemisphere N, S, E, or W - determines positive/negative sign * @return float Decimal coordinate (e.g., 51.5074 or -0.1278) */function exif_gps_to_decimal($coordinate, $hemisphere) { // Parse the degrees, minutes, and seconds from EXIF rational format // EXIF stores coordinates as "degrees/1", "minutes/1", "seconds/100" etc. for ($i = 0; $i < 3; $i++) { $part = explode('/', $coordinate[$i]); // Handle division by zero if (count($part) == 1) { $coordinate[$i] = $part[0]; } else if (count($part) == 2) { $coordinate[$i] = floatval($part[0]) / floatval($part[1]); } else { $coordinate[$i] = 0; } } // Convert DMS (Degrees, Minutes, Seconds) to decimal degrees // Formula: decimal = degrees + (minutes/60) + (seconds/3600) $decimal = $coordinate[0] + ($coordinate[1] / 60) + ($coordinate[2] / 3600); // Apply negative sign for South and West hemispheres if ($hemisphere == 'S' || $hemisphere == 'W') { $decimal *= -1; } return $decimal; } This is *completely untested*, but you may find it helpful. Cheers. — Reply to this email directly, view it on GitHub <#73?email_source=notifications&email_token=ADH3QBVULP2YKJHYQZ6FUC35AAZJZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZRGA3TCMRVGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4710712533>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADH3QBTZ7LEYTCETUWRAD4T5AAZJZAVCNFSNUABFKJSXA33TNF2G64TZHMZDQOJQGYZDIMRVHNEXG43VMU5TINRVGYZTKMZYGYY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ADH3QBTDMCHKKHBX7AC5HWD5AAZJZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZRGA3TCMRVGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ADH3QBU6FB7XPNBRPBQMPCT5AAZJZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZRGA3TCMRVGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>