Unexplained Google Maps Geocoding OVER_QUERY_LIMIT












-3















I have a Perl script that uses Google's geocoding at a slow rate but today I'm hitting the 'OVER_QUERY_LIMIT' error.



I'm fully signed up with billing and well below any budget limits.



In the last 30 days Google says I've made 2,074 Geocoding API requests (with 0.1% errors) and they would be evenly distributed over the 30 days.



I've bumped the quotas up to unlimited, per 100 up to 5,000 (max) and per 100 per user to unlimited and still the error occurs.



The relevant Perl would be:



use Google::GeoCoder::Smart;

my ($resultnum, $error, @results, $returncontent) = $geo->geocode("address" => $g, "key" => "valid_key_hidden", "region" => "au");


Any ideas ?










share|improve this question

























  • Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

    – Corion
    Nov 14 '18 at 10:05











  • Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

    – RobH
    Nov 14 '18 at 11:22


















-3















I have a Perl script that uses Google's geocoding at a slow rate but today I'm hitting the 'OVER_QUERY_LIMIT' error.



I'm fully signed up with billing and well below any budget limits.



In the last 30 days Google says I've made 2,074 Geocoding API requests (with 0.1% errors) and they would be evenly distributed over the 30 days.



I've bumped the quotas up to unlimited, per 100 up to 5,000 (max) and per 100 per user to unlimited and still the error occurs.



The relevant Perl would be:



use Google::GeoCoder::Smart;

my ($resultnum, $error, @results, $returncontent) = $geo->geocode("address" => $g, "key" => "valid_key_hidden", "region" => "au");


Any ideas ?










share|improve this question

























  • Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

    – Corion
    Nov 14 '18 at 10:05











  • Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

    – RobH
    Nov 14 '18 at 11:22
















-3












-3








-3








I have a Perl script that uses Google's geocoding at a slow rate but today I'm hitting the 'OVER_QUERY_LIMIT' error.



I'm fully signed up with billing and well below any budget limits.



In the last 30 days Google says I've made 2,074 Geocoding API requests (with 0.1% errors) and they would be evenly distributed over the 30 days.



I've bumped the quotas up to unlimited, per 100 up to 5,000 (max) and per 100 per user to unlimited and still the error occurs.



The relevant Perl would be:



use Google::GeoCoder::Smart;

my ($resultnum, $error, @results, $returncontent) = $geo->geocode("address" => $g, "key" => "valid_key_hidden", "region" => "au");


Any ideas ?










share|improve this question
















I have a Perl script that uses Google's geocoding at a slow rate but today I'm hitting the 'OVER_QUERY_LIMIT' error.



I'm fully signed up with billing and well below any budget limits.



In the last 30 days Google says I've made 2,074 Geocoding API requests (with 0.1% errors) and they would be evenly distributed over the 30 days.



I've bumped the quotas up to unlimited, per 100 up to 5,000 (max) and per 100 per user to unlimited and still the error occurs.



The relevant Perl would be:



use Google::GeoCoder::Smart;

my ($resultnum, $error, @results, $returncontent) = $geo->geocode("address" => $g, "key" => "valid_key_hidden", "region" => "au");


Any ideas ?







perl google-maps






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '18 at 11:25









wanttobeprofessional

1,03331323




1,03331323










asked Nov 14 '18 at 9:09









RobHRobH

13




13













  • Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

    – Corion
    Nov 14 '18 at 10:05











  • Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

    – RobH
    Nov 14 '18 at 11:22





















  • Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

    – Corion
    Nov 14 '18 at 10:05











  • Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

    – RobH
    Nov 14 '18 at 11:22



















Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

– Corion
Nov 14 '18 at 10:05





Have you looked at the debugging process outlined in developers.google.com/maps/premium/previous-licenses/articles/… ? The 24h limits are checked/reset once a day, so maybe you have to wait 24 hours. Also, maybe change your token just in case it has been leaked.

– Corion
Nov 14 '18 at 10:05













Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

– RobH
Nov 14 '18 at 11:22







Issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it. I've discarded the module in favour of a direct call to the api url.

– RobH
Nov 14 '18 at 11:22














1 Answer
1






active

oldest

votes


















0














The issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it.



I've discarded the module in favour of a direct call to the api url






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53296495%2funexplained-google-maps-geocoding-over-query-limit%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it.



    I've discarded the module in favour of a direct call to the api url






    share|improve this answer




























      0














      The issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it.



      I've discarded the module in favour of a direct call to the api url






      share|improve this answer


























        0












        0








        0







        The issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it.



        I've discarded the module in favour of a direct call to the api url






        share|improve this answer













        The issue was the perl module being used was too old and was hardcoded to use http not https. It also had a parameter for setting the api key, but never sent it.



        I've discarded the module in favour of a direct call to the api url







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 14 '18 at 11:27









        RobHRobH

        13




        13






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53296495%2funexplained-google-maps-geocoding-over-query-limit%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            List item for chat from Array inside array React Native

            Thiostrepton

            Caerphilly