Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

when I enter a location for a picture, Photos changes it to a different location

When I enter a location for a picture, e.g. "38.007949, -122.487170" in the info panel in Photos, the location that ends up being stored is a different one, sometimes several miles away from what I enter. Every location anywhere in San Rafael, California, gets changed to the location of San Rafael City Hall. Locations in San Francisco, are changed to Twin Peaks in San Francisco.


For me, Photos started behaving this way a couple of days ago (October 2020); previously Photos would just store whatever location I entered. Is anybody else seeing this?


54 replies

Amazing! Brilliant! Thank you so much! Yeeppee!


For those who need to know (I didn't previously), you can add a script to the top menu bar with this: https://support.apple.com/guide/script-editor/access-scripts-using-the-script-menu-scpedt27975/


[EDIT] If any of you know of a more elegant / convenient way of installing & triggering the script, could you share?


I kinda improved your script to better suit my needs on 2 aspects:

  • When selecting several photos in Photos, they will all be set to the same location (therefore asking for lat,long only once), matching the behaviour of the Information pane that we've known.
  • Actually display an alert when there is no photo selected (required a try/catch when using the Scripts menu).


tell application "Photos"
	try
		set selectedImages to (get selection)
		if selectedImages is {} then
			error "Please select an image."
		end if
		set response to display dialog "New location:" default answer "" buttons {"Cancel", "OK"} default button "OK" with icon note
		set newLocationString to text returned of response
		if ((button returned of response) = "OK") and (newLocationString is not "") then
			set AppleScript's text item delimiters to ","
			set theLocList to every text item of newLocationString
			repeat with theImage in selectedImages
				set the location of theImage to theLocList
			end repeat
			display alert "New location set to: " & newLocationString
		end if
	on error errorMsg number errorNumber
		display alert errorMsg buttons {"OK"}
	end try
end tell

Finally I found a stopgap workaround for this -- to use AppleScript like below:


tell application "Photos"
	set selectedImages to (get selection)
	if selectedImages is {} then
		error "Please select an image."
	end if
	repeat with theImage in selectedImages
		set title to the name of theImage
		if not (exists (title)) then
			set title to the filename of theImage
		end if
		set response to display dialog "Edit Location of " & title default answer "" buttons {"Don't Edit", "Edit"} default button "Edit" with icon note
		if (button returned of response) = "Edit" then
			set newLocationString to text returned of response
			if not newLocationString = "" then
				set AppleScript's text item delimiters to ","
				set theLocList to every text item of newLocationString
				set the location of theImage to theLocList
				display alert "New location of " & title & ": " & newLocationString
			end if
		end if
	end repeat
end tell


It appears that this bug was fixed with 11.2.2. You can now enter any lat and long. But now you can't add keywords to photos that don't already have keywords. Sigh...

After updating to MacOS 11.2.3, entering latitude and longitude works for me. Yay!

Entering keywords works, too, sort of. It requires hitting Enter two or three times before any keyword takes hold.

Still unfixed (mad)... I have access to the Feedback Assistant, so I submitted the following 'feedback' (hum... bug report). This feedback is related to the publicly deployed version 11.0.1 (20B50) of macOS (not any beta version), so here I am *not* posting anything that would be considered confidential under the NDA rules of the beta tester agreement articles 5 & 6. However the Feedback ID would seemingly fall under these rules, so I'm afraid I'm not allowed to share it for cross-references.


Unable to set location of Photos with GPS coordinates

Description - Since mid-October 2020 approximately, it is impossible to use GPS coordinates (lat,long) to set the location of photos in the macOS Photos app. The Photos app incorrectly changes the location to the nearest city center instead. This is a regression from previous behaviour which occurs in various macOS versions and was not related to any specific macOS update, pointing instead to the malfunction of some cloud-based geolocation API. Check this discussion thread for confirmation and further examples https://discussions.apple.com/thread/251905264?answerId=253951549022

Very often, travelling locations do *not* have a valid street address or nearby POI, which means GPS coordinates are the only way to place those photos on a map. In such case there is no workaround available and this is a critical bug. Please fix!

Steps to reproduce - Open the macOS Photos app, open a photo, press Cmd-I to get photo information, input GPS coordinates in the Location field - for example 42.250024,11.769321

Expected results - As worked previously, the photo should be placed on the map at the location of the GPS coordinates. In this example: within the Necropoli dei Monterozzi.

Actual results - The photo is placed on the map at the city center of the nearest city, or alternatively at some random location. In this example: the photo is moved on the map to the city center of Tarquinia.

I just tested on several Macs: The same problem persists on the Macs with macOS 10.14.6 Mojave as well, not only on my Mac with macOS 10.15 Catalina. So it seems to be more a problem with Apple's location database than with the current catalina update.

When I assign this place: -54.63698 -67.764359 (Lago Escondido, close to Ushuaia, Argentina), Photos will move the pin into the center of the South Pacific Ocean and change the GPS coordinates accordingly to -24.8915 -136.5752054. That is nearly 30° farther north and 60° farther west. The entered GPS coordinates are discarded and lost, unless I copy them to the description field.

Keep sending feedback to Apple, so it will be fixed, when Big Sur is released. It is strange, that suddenly all my Macs with all system versions, plus the iPhone and the iPad are having problems with the Places in Photos. It looks like the central servers with the location names are causing the problems, not the current Catalina update.


I can confirm this problem. The pin on the tiny location map is in the wrong position, moved to the center of the city.

  • I enter 37.580627 -122.324113
  • and when I read the coordinates back from the photo with AppleScript, they have been changed to 37.547541 -122.314571

And the photos will be exported with the wrong GPS coordinates, many miles off.

This is a disaster.

It seems, we should not use Photos for geocoding, for the time being.


Done a bit more investigation. You can put in the same coordinates numerically and get different results


51.0 0.009800 gives the English channel

However, 51 0.009800 gives "no results"


and

51 0.0098 gives somwhere in Turkey.


I suspect it is not putting the coordinates on a map, and then finding the place - I'm guessing it must have a huge lookup table of places and their coordinates, and is messing up the interpretation of the numbers for the lookup, or the table itself is broken.


Hi, has any of you tried to call Apple Support https://getsupport.apple.com ?


This was in my plans, but I've already spent 1h45 on the phone with them today for another issue... to no avail, and I'm afraid my patience with Apple Support may have been depleted for another 6 months. Still, maybe worth a try wouldn't you think?

This bug is not yet fixed in Photos 6.0 (311.0.130) on macOS Big Sur 11.0.1 (20B29)...

Hi Stephan-S,

Yeah, I know, these seem to go to nirvana - I submit mine via the Feedback Assistant App using a (free) developer account.

Thanks, Joachim

Same irritating bug here, I confirm it's quite recent as GPS coordinates worked OK previously. I submitted feedback too.


Maybe it's linked to the imminent release of macOS 11 Big Sur? If it's not fixed till then, we'll see if the new OS has the same bug (although I'm not too keen to jump early on new releases).

Dear Geo Taggers & Photo Archivers,

Is there an impact / more positive effect, if me mention the Feedback ID in each others Feedback Tickets? I don't know, if this is against Apple's policies, but it might be worth a try. Mine is still showing "Similar Reports: None / Resolution: Open".

Thanks,

Joachim

Still not working properly - but is vastly improved from when this first cropped up in October.


Then I couldn't even put in the locations of Greenwich Observatory in London without it putting the pin in the north sea. Now I've tried that (fine) and a number of offshore locations to the north east of the UK, and it seemed to get them fine.


However I've just tried the location in the screenshots in Chesapeake Bay, and you can see the result...



That is quite an error.


Hello,


I wrote myself an AppleScript app that works similar to the very nice script published here, but additionally writes the location information to the originals of the photos.


This is done by reading the path to the selected photos from the Photos app database of the currently used Photos library, which is usually determined automatically.

If there are several photo libraries, it can happen in a few cases that the currently used Photos library cannot be determined and must be selected manually.


Since I'm not an "identified developer", the app has to be started with a right click on the first start and depending on macOS used additionally selecting it in the Finder, which is explained in the ReadMe.


Maybe this is something for you

kind regards

Sedna


PhotosSetCoordinates



Well this is really odd. I've just put in the coordinates for Greewich London, and Photos has put the pin in the middle of the north sea - about 400 miles away. Seems messed up to me.

The problem still exists with Big Sur.


I also sent feedback to Apple using the Feedback Assistant. Hope they're going to fix it soon, really annoying.

Unfortunately, this bug still isn't fixed. I'm seriously considering moving away from Photos for good. Without working geotagging, it is useless for me.

I just tried this one before posting. Should be on the Croatian Island Krk, but is in the Adria.


45,02784558272772 14,677579043046618

They did not read this thread very well. It is not a *Photos* bug it is an *Apple Maps* bug.

I suspect that has been fixed in the Apple location servers, because it is also now working in Catalina - which hasn't had an update.

The way I understand it, houdahGeo writes latitude and longitude directly into the image files, bypassing the geotagging mechanism built into Photos.


How do you like houdahGeo? Would you recommend using it?

Keith, may I ask you a question? I am also relying heavily on HoudahGeo for entering the metadata before importing photos to Photos. But I am still having HoudahGeo 5. It keeps nagging me to upgrade to version 6. Is the upgrade worth the money? I tested the free trial, but the new features cannot be tested fully. As version 5 is still working well, I would prefer to wait for the Big Sur Release before deciding to upgrade or not.


I have kept upgraded, but haven't really noticed any functional improvements. It always just works.


I have asked them to add the "imports" view from Photos, if available, since that is usually the easiest way to get at the images you recently imported. But they haven't yet taken my suggestion.


TL; DR;

I think you are fine waiting.

How are you able to view the status of your feedback? Whenever I post to Apple Product Feedback https://www.apple.com/feedback/ it goes into some kind of black hole with no way to get updates? Thanks.

[EDIT] And I don’t get any Feedback ID for reference.

Léonie, your Level 10 suggests that you have quite a bit of experience with these forums. Would you happen to know if Apple looks at forum posts that describe bugs, or if bugs are expected to be reported via some other mechanism?


Even worse - I can go as far inland (USA) to longitude -80 (that is almost to Charlston) and it still decides it is the middle of the North Atlantic. If I put the pin directly on Charlston - it gets it right.



I have thousands of images with geotagging, face labels, keywords and sometimes lengthy descriptions, and I can't figure out how to extract the the original-quality pictures and the associated metadata from the app. Re-tagging the entire collection is not a realistic option for me, so I'm stuck with Photos.

Hi - You can export geotags, keywords, descriptions and face labels, by checking "export IPTC as XMP" in the export unmodified originals box.



This creates an XMP sidecar file that most software will recognise when importing. The xmp file must be kept in the same folder as the image file.

In the meantime, I tried to open a couple of Fotos from my Photos library with HoudahGeo as a workaround. In the libraries panel, Photos show up, but when I try to expand this library and view the folder / pictures in the library, nothing happens. I waited for a couple of minutes, but still, nothing showing up. Could this be because I have to many (~130'000) photos in my library? Or because all photos in the library are in folders?

Hi xsedna


Thanks for your script. I tried it today and read the Readme too but I was unable to enter the location in the following format: 46.25406, 7.84488


It accepts the format and tries to process it, but the popup says that it was not successful. Do you have any idea why? It's a vidoe.

Hello


and thanks for the feedback!

By pop-up do you mean the notification that appears after editing? The notification only shows if the GPS data could be written to the originals. The GPS data set in the Photos app can be checked in the Info window.


GPS data can only be written to a few video formats... Apple-Quicktime Movie ("MOV") and MPEG-4 ("mp4").... and theoretically also to the M4V format.With the first two it works, but for m4v videos I have no solution at the moment.


Kind regards

Sedna

I can enter keywords, as long as I do not ry to do it in the recents or Imports album, right after importing. In the recents or Import the focus is immediately moving away from the Info and I am getting a lot of beeping I am adding any ne photos to an album and work from this album, then it is easier.

That's weird; I can't reproduce the problem anymore. The coordinates 38.025923, -122.517199 work fine, and the ones that didn't work were within a hundred feet (30 meters) of that point, but I can't remember the exact numbers.

OK - where is the official bug report page :-)

Thank you. I submitted a bug using the feedback form.

No, DD.mmsssss doesn't work either.

Thank you for the additional info, Keith. Then I'll wait, until I am sure that the next upgrade will work with Big Sur.


That's disappointing. I often take pictures with a camera that doesn't have a built-in GPS; geotagging those photos has become nearly impossible.

Thank you for filing the bug!

The only metadata you can easily export is geotagging, since that has an EXIF field.

It's absolutely better (or the best).

Thank you for improvement.

Sad news.

This isn't fixed on macOS Big Sur 11.2 (Photos.app Version 6.0 (330.0.150))...


AppleScript (code above) is available also in newer version.


I can't enter keywords anywhere, whether looking at the photo in an album or Library.

That makes sense. I was making assumptions.

I spoke too soon. I just encountered another instance o 00004000 f latitude/longitude coordinates being snapped to a different location that is miles away. :-(

Can you post those coordinates here, so I can try them in Catalina?

There are several ways. The quick and easy way is the feedback form. Feedback - Photos - Apple

Or, if you want to file a detailed bug report, with attachments and test samples, you need a free developer account. It is worth it, see: Detailed and Effective Bug Reporting | Apple Support Communities


Or, if you are a Beta tester or seed tester, you can use the Feedback Assistent:


Totally, I have a Foretrex 601 that saves a gpx file. After I import into Photos, I launch HoudahGeo, select the images I want to use, drop the .gpx file into Houdah geo.


In fact, the images I did yesterday had a really screwed up camera clock: Wrong time zone and a lot of drift. In HoudahGeo, I used an image I took of the clock on my Foretrex, and it readjusted all the times for Photos.

masuurikas wrote:

The problem still exists with Big Sur.

It is independent of the system version - it is broken since October in all versions of Photos where I can test it, on Mojave, Catalina, Big Sur. It must have been broken in a central location on Apple's servers.


The Apple developers are looking occasionally at these forums, particularly after a software update. But you cannot rely on them to read each and every post. It is far safer to use the provided feedback tools, if you want to be sure that your bug reports will reach the developer team. You may even get a reply and follow up requests for more details, if you use a developer account.

  • For a quick report use the feedback form. Feedback - Photos - Apple
  • For a detailed report with screenshots and other test protocols and system logs use the feedback assistant from a free developer account or the or a beta tester membership.

How to get a developer account: Detailed and Effective Bug Reporting - Apple Community



It seems to work OK when I use houdahGeo to geocode.

Could it be using DD.mmsssssss?