L.esri.Query does not use offset and limit functions correctly

Hi, everyone,

sorry for not following the guidelines, but this issue kind of does not fit in them.

When doing a call like this using L.esri.DynamicMapLayer:

var query = this.query()
  .layer(3)
  .intersects(geoJSON)
  .limit(10)
  .offset(0);

query.run();

The returned result is not limited at all and returns all results at once.

When doing a call like this using L.esri.DynamicMapLayer:

var query = this.query()
  .layer(3)
  .intersects(geoJSON);

query.params.resultRecordCount = 10;
query.params.resultOffset = 0;

query.run();

The returned result is limited to 10 elements and I can successfully use resultOffset later on to return all the other results step by step.

I use this service: http://services.geodataonline.no/arcgis/sdk/rest/index.html#/Query_Map_Service_Dynamic_Layer/02ss00000081000000/

And they use at least ArcGIS 10.3 as I understand.

I expected the limit and offset to work the same way as resultRecordCount and resultOffset works right now in terms of returning results.

Can you confirm if this is a bug or am I doing something wrong?

[simoxu001]

Thank you @jgravois for sharing this. I’ve been stumped by this for a week! This unpredictable nature is affecting other APIs as well.

[jgravois]

greetings @theashyster! its been a year and half, but i just found some documentation that attempts to explain the somewhat unpredictable nature of exceededTransferLimit so i thought i’d forward it along.

In some cases when using the resultOffset and resultRecordCount parameters, the exceededTransferLimit property may be included in the query results even though the value specified in the resultRecordCount has not been exceeded. This is due to internal spatial index filtering of the query results. For this reason you should always rely on the exceededTransferLimit property to determine if you should page through results rather than relying on the number of results returned from each page. In some extreme cases zero results can be returned but the exceededTransferLimit property will be returned. In these cases you should continue paging though your results until exceededTransferLimit is no longer returned.

reference: https://developers.arcgis.com/rest/services-reference/query-feature-service-layer-.htm