Yesterday, I realized, that all types of Google Maps are labeld with "For development purposes only".
How can this be avoided? Is there any workaround?
STEPS TO REPRODUCE
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
In the meantime, I found following discussion:
this morning I wanted to modify the geolocalisation of my latest
pictures , and when I opened the tools I got the error message : "this
page didn’t load google maps correctly" and the map is displaied with
the watermark "for development purpose only"
when I look at the solutions, seems we have to regenerate some API key ,
but not sure if it is applicable to this case
I'm using 7.2RC (I'm not sure I already used the geolocalisation with
this version since I installed it, but I was using it regurlaly with
thanks for any suggestion to fix it.
For the use of the Google Maps Java Script API, Google provides a project with free access worth $ 200 free of charge. This corresponds to 28,000 dynamic Google Maps views per month. We exceeded that limit this month. From March 1st, the Google Maps map will work again. We have already taken steps to reduce unnecessary Google Maps calls. In the future, the maps in the digiKam sidebar will always start with the Marble maps. Google Maps must be selected in the sidebar every time it is started, if required.
We don't have any other option than an open source project, a larger volume would have to be bought from Google every month.
Thank you for your clarification!
*** Bug 433746 has been marked as a duplicate of this bug. ***
(In reply to Maik Qualmann from comment #2)
> From March 1st, the Google Maps map will work again.
Is there another issue with Google Maps or why does the label still appear?
Yes, our access to Google Maps already existed before 2018, until then it was not necessary to store a payment option. Google requires that a payment option is stored, credit card, PayPal or the like, even if there are no monthly payments. Without a valid payment option, access to Google Maps will be prevented.
So... Could you please clarify what this will mean for the future use of Google Maps with digikam?
May be, as Jeffrey’s “Geoencoding Support” Plugin for Lightroom, it might be required to add the ability for the user to add his own google key for the use of the map.
The generic use of the developer key for all users will bring this "max requests used" issue up very soon as the user base grows.
Stetting the default to open street map / Marble globe is a good idea and one step to reduce the request towards google. But it might not be the ultimate solution. My default is Open Street Map, but for finding the right location I often need the birds view from the top.
I do not know if other services can offer similar things (sattelite view).
(In reply to info from comment #8)
> May be, as Jeffrey’s “Geoencoding Support” Plugin for Lightroom, it might be
> required to add the ability for the user to add his own google key for the
> use of the map.
Indeed? Can you enter your own key in the program? We have already thought about it. But I can't imagine that Google would find that okay.
Otherwise, don't get impatient, we're working hard to add a billing account.
If anyone has experience adding and verifying a PayPal billing account, please contact us.
For the future, we will have to set a daily limit and Google Maps will probably not always be available on a daily basis.
(In reply to Maik Qualmann from comment #9)
> Indeed? Can you enter your own key in the program? We have already thought
> about it. But I can't imagine that Google would find that okay.
Yes it is possible as he had the same issue with too many access requests.
And I do not think google can do something about it.
May be the Bing map can be used in non profit mode
*** Bug 435137 has been marked as a duplicate of this bug. ***
*** Bug 440503 has been marked as a duplicate of this bug. ***
Just take a look to this project from Github :
There is a demo where you can add layer on map view (Backgroup Maps), including... GoogleMap and Bing. And it work as well...
Interesting no ?
Hmm, an interesting solution. After a quick look, I see that the tiles are loaded directly past the Google API, the user agent string is changed, etc. I cannot imagine that Google would agree to this.
yes, i see also this kind of deal with Google API.
Did you look the Bing Map backend too ?
The same goes for the Bing backend. I actually plan to start with Bing, but the way via the official API. Maybe it would be something for GSoC-2022 as well. Bing has a pricing model for non-profit organizations.
yes agree, this can be a project for next GSoC
*** Bug 442130 has been marked as a duplicate of this bug. ***
*** Bug 447677 has been marked as a duplicate of this bug. ***
Hi Maik and happy new year for you and your familly.
Look my screen shot from MacOS and Subsurface Qt application:
It uses a special QtPosition plugin to support google maps very well. Where is the magic here ?
bash-3.2$ ls -al
drwxr-xr-x@ 9 gilles admin 288 19 nov 18:32 .
drwxr-xr-x@ 12 gilles admin 384 19 nov 18:32 ..
-rwxr-xr-x@ 1 gilles admin 239968 19 nov 18:32 libqtgeoservices_esri.dylib
-rwxr-xr-x@ 1 gilles admin 306000 19 nov 18:32 libqtgeoservices_googlemaps.dylib <= !!!!!!!!!!
-rwxr-xr-x@ 1 gilles admin 75472 19 nov 18:32 libqtgeoservices_itemsoverlay.dylib
-rwxr-xr-x@ 1 gilles admin 464976 19 nov 18:32 libqtgeoservices_mapbox.dylib
-rwxr-xr-x@ 1 gilles admin 6269856 19 nov 18:32 libqtgeoservices_mapboxgl.dylib
-rwxr-xr-x@ 1 gilles admin 467552 19 nov 18:32 libqtgeoservices_nokia.dylib
-rwxr-xr-x@ 1 gilles admin 325232 19 nov 18:32 libqtgeoservices_osm.dylib
QtPositioning offers access to mapbox, osm etc. The Google Maps plugin comes from here:
After a quick look, I see that it loads tiles directly from the Google server, bypassing the API. This is a violation of Google's Terms of Service:
I don't know if we should do it, I don't think so.
So, it's the same mechanism than https://github.com/AmonRaNet/QGeoView ...
Perhaps we can post a message in github Subsurface issue section about this problem to see what's the team will respond...
Issue created in github :
We will seen...
We have receive a response from Subsurface team : https://github.com/subsurface/subsurface/issues/3367#issuecomment-1006003655
As you take a closed look in source code using GoogleMaps in Subsurface, please ask more questions for the details.
Following the response of subsurface team, which have a similar use of GoogleMaps than digiKam, it sound like Google don't care about the open source use of direct data access. So, i think it safe to use the same way than Subsurface to render the googlemaps view in digiKam...
Hmm, I'm sure it's not desired by Google. However, we must be able to display markers and images on the map. Also we need to be able to show tracks. We also need to be able to get the current position on the map. All this is only possible with the java script API...