Latest Contributions by simoxu

Thanks. Clustering function works great using the latest JavaScript API, hope this will come to the native applications eventually.  ... View more

Thanks John Yaist‌, I've been talking with ESRI local support and just urged them to escalate it to ESRI US. ... View more

Thanks. I've contacted ESRI local support for this issue to be escalated. ... View more

Hi John Yaist‌ This is very likely an ArcGIS Python API bug. In the API source code for the query function (layer.py, Line 650), it does not test the exceededTransferLimit property in the response, the code assumes the query always return the specified number of records when possible. This is not the case for spatial filter.... exceededTransferLimit  was introduced in ArcGIS Server 10.3.1, please see the details in the following link 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 through your results until exceededTransferLimit is no longer returned. Query (Feature Service/Layer)—ArcGIS REST API: Services Directory | ArcGIS for Developers  Hope this makes sense. Regards Simo ... View more

Hi Tanu, Thanks for your answer to the question.   If this is an expected behavior, I am just curious why the hosted service in AGOL and ArcGIS portal do not have this issue, as we all know behind the scenes, the same ArcGIS server is doing the heavy lifting. More importantly, this expected ArcGIS server behaviour is causing issue in the APIs (at least I have personally experienced the issue in ArcGIS Python API). I dived into the API source code and found, the code checks for the number of records returned, if it is less than the resultRecordCount or the MaxRecordCount (whichever is less) it will assume all the records has been retrieved and stop querying the service. Many thanks Simo ... View more

I have the similar issue. I found the problem is at the REST API level when querying a ArcGIS Server Map/Feature Service with a spatial filter. If the resultOffset and resultRecordCount are not set, it returns all the matching records, if they are set the query returns wrong number of records. for example, if the resultRecordCount is set to 500, it only returns 36 records with exceededTransferLimit=True. This issue should affect all the other APIs that wraps the REST API, such as Javascript API, Python API, ArcGIS Runtime SDKs... ... View more