Google Maps Engine - This resource is too large to be accessed via this API call -


We have Google Maps Engine accounts. I've recently uploaded a size file that contains approximately 179,000 features < / P>

Find the exact figures for the table

  • Feature number: 178 56
  • Bad feature number: 0
  • Vertex Count multi-polygon number: 102

I am trying to execute an intersect query as the following

  • Polygon count : 17 9 58
  • >

    "{tableid} / features?

      error: {Errors: [{domain: "useLimits", where it is thrown to the following error: <{domain: "useLimits", "{error: SUBSCRIBE} Cause: "Beyond the boundary", the message: "This resource is too large to be transmitted through this API call."}], Code: 403, Message: "This resource is too big to reach through this API call "}  

    To ensure that I am using the author correctly, I change the table id. And I can do the same query in another table with 1500 records. I get the appropriate results

    Question

    1. If I use the access token properly using the Google OAuth client Ready, do I still need an API key to access the private keyboard?
    2. Does Google Maps Engine support queries for features in the table with more than 100K records? I read Google error for this error and Maps Engine boundaries at the following URL [It is said that the dynamic ability for feature requests is not supported if more than 100K. Is this limit applicable only for every second (QPS) or any request?
    3. Any suggestions for using search queries for high volume of GIS data?

    Thanks in advance for your help.

    1. No API key is used only to reach public tables is.

    2. The GME API limits are detailed on:

    3. The examples of how the Intersects function can be found on the following:

    If there is anything special that requires extra help, do not be afraid to raise the support case:


    Comments

    Popular posts from this blog

    import - Python ImportError: No module named wmi -

    Editing Python Class in Shell and SQLAlchemy -

    c# - MySQL Parameterized Select Query joining tables issue -