Hi, I know. This is a not the first topic about this subject but I have noticed a strange behaviour of my reverse geocondig service.
I reverse geocode 20 point and all works well till the 8th point. Starting from this point I receive a OVER_QUERY_LIMIT with this rule: 3 OVER_QUERY_LIMIT 1 o 2 good result 3 OVER_QUERY_LIMIT 1 or 2 good rsult an so on. Assuming that this is a rate limit problem I switch the delay from 150 ms to 500 ms but I always, sometimes, receive OVER_QUERY_LIMIT error. somebody know what is the rate limit that should be set to avoid the above error? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
