PSP2020 Geotagging stopped working

[Marco73]

Come on Corel, get your act together. If you can't reach agreement with Google, have a look at implementing Open Street Map's Framework. (It might be cheaper to pay Google a few USD than redevelop or lose functionality and customers.)

I'll put my signature under that.

[Andy2011]

juergen deserves a lot of credit for giving me the clues to where to look. Also thanks to Johnc1 for confirming that the search facility issue I had was in the Google settings, not the htm/js code.
Whilst I understand Marco73's reluctance to go down the own key route, is there mileage (or "kilometreage" in certain locations) in putting together a set of setp-by-step instructions to help others through the process of fixing geotagging? At present the information is in this thread but in several posts.
I have been a bit obtuse in places as I didn't want to encourage those without the necessary understanding from messing around in the PSP code. Nor did I want to wave a red rag in front of Corel's bull. With regard to the latter point, a brief scan of the EULA, doesn't show up any prohibition on making alterations to the htm amd js files and Corel's performance is not that of a raging bull - no, it's abominable.
The actual steps to self-fix geotagging are simple:

• 1. prepare
  2. get Google API Key
  3. alter 2 files in the appropriate directories of the PSP program
  4. test

I had most trouble with navigating Google's API settings but others may struggle with gaining access to files in a protected area. Certainly, a single keystroke error can break PSP. (I made one, accidentally omitting a '<' when commenting out the old code and had to kill the PSP process with Task Manager as PSP was in a loop.)
If there is the demand, I could help with assembling the instructions though the Google bit may need input from others - e.g. Google knew my identity and already had credit card details from Google Pay - others may start from a different position.

[Johnc1]

juergen deserves a lot of credit for giving me the clues to where to look. Also thanks to Johnc1 for confirming that the search facility issue I had was in the Google settings, not the htm/js code.
Whilst I understand Marco73's reluctance to go down the own key route, is there mileage (or "kilometreage" in certain locations) in putting together a set of setp-by-step instructions to help others through the process of fixing geotagging? At present the information is in this thread but in several posts.
I have been a bit obtuse in places as I didn't want to encourage those without the necessary understanding from messing around in the PSP code. Nor did I want to wave a red rag in front of Corel's bull. With regard to the latter point, a brief scan of the EULA, doesn't show up any prohibition on making alterations to the htm amd js files and Corel's performance is not that of a raging bull - no, it's abominable.
The actual steps to self-fix geotagging are simple:

• 1. prepare
  2. get Google API Key
  3. alter 2 files in the appropriate directories of the PSP program
  4. test

I had most trouble with navigating Google's API settings but others may struggle with gaining access to files in a protected area. Certainly, a single keystroke error can break PSP. (I made one, accidentally omitting a '<' when commenting out the old code and had to kill the PSP process with Task Manager as PSP was in a loop.)
If there is the demand, I could help with assembling the instructions though the Google bit may need input from others - e.g. Google knew my identity and already had credit card details from Google Pay - others may start from a different position.

Hi Andy, happy to help pulling together a set of instructions
is this one for the mods to comment on....?

[Andy2011]

Hi Andy, happy to help pulling together a set of instructions
is this one for the mods to comment on....?

Yes and yes! With regards to the mods, surely the thread has been noticed now.
If you can PM me, I will try and send you a copy of where I have got to in writing instructions.

[Marco73]

So does Corel read here?

[JoeB]

So does Corel read here?

Once in awhile somebody from Corel seems to check at least some of the topics. But we don't get comments back from them very often, and apparently only if that person realizes that the issue is serious (from Corel's perspective) and if they are actively working on a fix. Otherwise it's quite rare to see a comment from any Corel people.

[Marco73]

That's what I thought ...

[Marco73]

They answered again, but nothing new for the users on this board:

Thank you for contacting our technical support.

We apologize for the inconvenience you are experiencing.

We would like to inform you that the error described has been forwarded. Our developers will work on a solution, but unfortunately we cannot guarantee that this is possible or set a time frame for it.

Thank you for your cooperation!
Have a nice day!

And I guess the translation is: Go f..k yourself and learn to live with it.

[juergen]

juergen deserves a lot of credit for giving me the clues to where to look. Also thanks to Johnc1 for confirming that the search facility issue I had was in the Google settings, not the htm/js code.

Thanx, no problem.
I do not use geotagging directly within PSP, so I only described one possible solution, but did not apply it directly.

Also think of the possibility of simply running a GPS logger on the go.
In order to then automatically tag all photos at home on the computer in one go.
Of course, this is not always helpful (external photos, etc.).
But if I e.g. Hiking or visiting cities etc. usually runs OsmAnd + on the smartphone anyway ...

Useful apps:
https://gpslogger.app/
https://osmand.net/

Useful program at home:
https://geosetter.de/en/main-en/ (similar problem with this software at the moment, but the developer is aware of it)

Regards, Jürgen

[Andy2011]

Thanx, no problem.

Credit where credit's due.
I hadn't used geotagging until recently until I got involved in a project to make a photographic record of our village - a snapshot in time so future generations could see how the locality has changed. A friend & I took over 1,000 pictures in late summer 2019. For some of these I did have a 20 year old GPS receiver with me and used the track log and EXIFtools to write the geotag. My friend had tried linking his camera to his smart phone but apparently the battery drain was excessive.
However, the real value of the location information came apparent when the newly volunteered village archivist found a batch of 78 large black and white prints of the village taken in 1977. They were dated but the locations had not been noted. Some of the places/houses in the prints were easily identified but some were very difficult as trees & hedges had grown, houses extended, new buildings altering the views. One print could only be identified by how a footpath met a road and an unusual set of kerbstones. There is still one print of an unidentified house.
Now the digitised prints have been tagged and a map produced with pins indicating the photos.
Of course there is the usual problem of do you tag the location of the camera or the subject of the photo. The location information needs to be extended by compass bearing etc.

[juergen]

...
Of course there is the usual problem of do you tag the location of the camera or the subject of the photo. The location information needs to be extended by compass bearing etc.

Important point, the more important the purpose of the whole is...

Regards, Jürgen

[Marco73]

The Mails from the support are ridiculous ...

They wrote

The reason for the problem is that last year Google changed the API so that Google Maps can be implemented in any application. However, Internet Explorer was not supported. All versions of PaintShop Pro and earlier versions are affected.

The problem you have is a known problem and unfortunately we have no solution at the moment.
Our developers are trying to find a solution and will come back with a patch as soon as possible.

The number of customers who have the same problem as you have made us aware of this problem and that's why we call it a known problem.
These types of problems can occur as a result of an update of the program or even the operating system.

This type of problem can also appear in old and new versions.
Please be patient until our development team finds a solution.

I answered - again - that I don't even use "Internet Explorer".

Their next answer was:

The problem you have is a known problem and unfortunately we have no solution at the moment.
Our developers are trying to find a solution and will come back with a patch as soon as possible.

The number of customers who have the same problem as you have made us aware of this problem and that's why we call it a known problem.
These types of problems can occur as a result of an update of the program or even the operating system.

This type of problem can also appear in old and new versions.
Please be patient until our development team finds a solution

As I said before: Monkeys drawing cards from a deck with standard answers ...

[Marco73]

Ìs there any change or any new official word to this issue yet?

[Andy2011]

However, a bit of reading makes me wonder if this is an API licensing issue between Corel and Google. Apparently Google hiked the price of access to the mapping data a year ago.
I will be very pleasantly surprised if this gets fixed - I fully expect it to get kicked into the long grass.
One thing is certain, though. If Corel don't reinstate geotagging they will be losing a previously loyal customer.

Two months on and Corel have not come back to me. The grass is getting longer and rougher.

[Marco73]

Two months on and Corel have not come back to me. The grass is getting longer and rougher.

In Germany we have a word for this: "Aussitzen".