Skip to main content

Max Query Results

Comments

9 comments

  • Craig Carsley

    I would also like to know this.

     

    1
  • Nico Burgerhart

    By default resultRecordCount=500 is added as parameter to the underlying query operation.

    3
  • Craig Carsley

    Is there a way to change that?

     

    0
  • Nico Burgerhart

    I don't know how.

    For an Identify, I know this can be defined by setting the maxResults parameter as an argument to the command, see
    https://developers.vertigisstudio.com/docs/web/api-commands-operations-events/#definition-IdentifyArgs

    0
  • Nico Burgerhart
    { 
      "name": "tasks.identify", 
      "arguments": { 
      "maxResults": 2000 
      } 
    }
    3
  • Craig Carsley

    Thank you! It was the name of the argument parameter that I needed.

    This worked for me:

    0
  • Nico Burgerhart

    For tasks.identify the default maximum number of results is 500 results.

    0
  • Cole McLaughlin

    Looked high and low, and eventually found this thread.  Unfortunately, the codes provided above are incomplete.  Below is the full copyable code for increasing the identify results for each geometry identify tool.

    [

        {

            "name": "sketching.capture-geometry",

            "arguments": {

                "geometryType": [

                    "square"

                ]

            }

        },

        {

            "name": "tasks.identify",

            "arguments": {

                "maxResults": 13000

            }

        },

        "results.display",

        "charts.display",

        "kpi.display"

    ]

        "results.display",

        "charts.display",

        "kpi.display"

    ]

    0
  • Gareth Finney

    I'll piggy back onto this thread and ask if anyone has managed to disable the maxResults/ResultRecordCount setting as this is REALLY slowing down the query being executed. The query smokes along without this setting as a basic REST query, yet when run from VSWeb/Workflow, it includes this default maxResults and our query then slows down to minutes. I'm talking a spatial query on our Parcels layer with millions of polys, so ideally I'd like to turn this off if I can? I've been toying with both Poly and Point - with zero tolerances to speed this thing up, but the underlying issue is this extra maxResults parameter

    0

Please sign in to leave a comment.