Skip to content
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
This repository was archived by the owner on Apr 19, 2026. It is now read-only.

How to prevent OVER_QUERY_LIMIT with google-map-search and input #387

Description

@ammopt

Hello.
I'm trying Polymer for the first time and developing a simple view like so:

<paper-input value="{{input}}"></paper-input>
<google-map-search map="{{map}}" query="{{input}}" results="{{results}}"></google-map-search> .....

It kind of works: the map updates the markers based on the results from the input typed in the paper-input element.
However, if I type too fast, I noticed the error on the console:
Cannot read property 'map' of null

After a while I found out it's returning OVER_QUERY_LIMIT status from Places Service. Is there a correct way to prevent this? Thanks!

Activity

  1. chenster commented on Aug 28, 2017

    @chenster

    Have you tried getAddress from https://stackoverflow.com/a/11825245/3915432? It delays your sending query to Google to prevent reaching the query limits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions