The API key is correct. web access (http) is allowed on the API consol. Might it be due to https: now being invoked rather than http. My site was updated to https access. In Google's API management, I even registered https:///www.bronord.com as an attempt to fix this.
I'm lost! The API path to showing maps with jAlbum is a rat's nest of complexity! Either that or my ole brain has withered and is close to death.
Please don't blame jAlbum for this rat's nest. This is all down to Google.
In any event, maybe this will help. Attached are the settings for the API Key that I use on my demo pages. Note all of the entries, including the wildcarding on the domain name, the fact that no protocol (http vs https) is required, and the mysterious "API Restrictions" choice at the bottom - that one is not the same as restricting the key to your domain.
At least you can find the API console. I finally bookmarked mine, because I had a hell of time finding it a while back. Gee, Google, great user interface.
Your advice led me to the answer . . . after I re-found the "restrictions" page. The attached shows the additions that I made, with possible redundancies, but I kept adding until it worked. And, that fixed the issue with other albums, e.g., City Gate in Innsbruck.
Should I write directly to the boss and tell him to give you a raise?
It is not clear to me where jAlbum picks map info from. Some of my images have GPS data, some do not. Even tho some sub-albums have some images with GPS data, the do not have folder maps generated. (Some images had GPS data because they were taken with a Google phone. Others were with a camera w/o GPS data - no GPS sensor.) Not a big deal if I turn-off the option. Just trying to understand jAlbum.
That's a "Tiger thing." The jAlbum core makes the GPS coordinates available to the skin for any image that contains them. What the skin does with them after that is up to the skin developer.
In theory, Tiger should show a map with markers for all of the images in that folder that have GPS info in them, and in my quick test, that's what happens. It doesn't search into subfolders for GPS-tagged images, however - it's looking for GPS in the images at the current level.