gene_lafond's profile

2 Messages


84 Points

Thu, Sep 26, 2019 5:21 PM

Elements 2019 Oranizer Version 17.0 Location Problems

since the upgrade to 2019, new organizer locations are created under a NEW location tree named United States of America, not the existing tree of United States.  Tech support blames a change in the Google API.  BUT tech support cannot merge or migrate the old tree to the new tree.

After an hour and a half with tech support, there is currently no solution except to write this.
Adobe SHOULD be able to manage it's own catalog, or write a small piece of code to transition from the old catalog to the new catalog or merge the old tree to the new tree.
I would like to see this fixed and return this product to excellent.

37 Messages


464 Points

2 y ago

Well, the "google change" occurred after Elements 2018 came out.  Adobe, of course, shrugged its shoulders and told its existing customers, "Tough. If you want locations to work, buy the 2019 version."  Adobe doesn't ever make free fixes to released software.  So, do not hold your breath for Adobe to do anything to fix this problem in your 2019 Elements.
   -a 2018 elements customer



1.3K Messages


20.2K Points

2 y ago

There may be two reasons why the help desk did not give the true reasons of the issue.
First, for them it is obvious that the feature of maps is provided by specialized companies like Google and the inclusion of such features in Adobe softwares is to give access to the databases of those companies by integrating paths to interact with them. This is clearly stated in the license terms, but it appears that some users think that the geographic database is owned and managed by Adobe. There is no worldwide standard in how the location hierarchies are created. Google and the new provider have different hierarchies. That won't change.

The second reason is that Google provided APIs for other editors to connect  to their databases. You are free to connect directly with Google Maps. What do you know about the deals between Adobe and Google? Obviously, Adobe did not agree to a price increase, which made Google cut the links by changing the API. Users found some time later that the feature had been reintroduced... just the time for Adobe to change to another provider (with another map database with different hierarchies). Big companies like Google and Adobe never disclose anything on such discussions. So my personal guess is that Adobe agreed to Google terms for the 'pro' softwares and did not for the Elements 'consumer' one.

Many organizer users have found that they prefer to ignore the locations tab and to use the standard tag custom hierarchies they can create just like in the oldest organizer versions without geotagging.