I think I found out the reason.
Might be I use Geocoding v.2
And I found the following remark:
This document is intended for developers migrating to version 3 ("v3")
of the Geocoding API. Version 2 ("v2") of the Geocoding API was
officially deprecated on 8 March 2010 and has now been turned down. As
of 9 September 2013 the v2 API will no longer work.
I don't know from where I got the software wicket.contrib.gmap.api
What softwarepackage do you recommend for Google Maps integratiopn
Also the date 9th September might fit to the time when my appklication
stopped to work.
Am 14.09.2013 13:50, schrieb Bas Gooren:
I have no idea, as I have not had this problem myself.
You should call or e-mail google support about this.
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 14-9-2013 11:44, schreef Piratenvisier:
How long am I blocked.
Do I have to do anything, or does the blockage go away after a few days.
Am 12.09.2013 08:55, schrieb Bas Gooren:
Hi,
You're probably hitting a usage limit:
https://developers.google.com/maps/documentation/business/articles/usage_limits?hl=nl#http403
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 12-9-2013 8:41, schreef Piratenvisier:
I am using google maps embeded in my 1.5 wicket application
.
I used the wicket.contrib.gmap modules, which worked fine till now.
Since a few days I get back the error:
Server returned HTTP response code: 403 for URL:
http://maps.google.com/maps/geo?q=30161+Hannover+Eichstra%C3%9Fe+10&output=csv&key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
What has changed ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
