Latest Contributions by simoxu

It's proven that the actual differences are in the hosted service and non-hosted service. hosted service works regardless point layer or polygon layer. and I can reproduce the error using REST API. so this may not be a ArcGIS Python API bug. The issue is at a lower level I am afraid. ... View more

It has something to do with query pagination. when I monitor the the REST requests it sent to the server, it sends two requests: 1. get the the count of the records 2. get the actual features with  resultRecordCount paramter sets to the result of the first request. This is very logical and should work, but it doesn't for the feature service directly published to the federated server. if I remove the resultRecordCount parameter in the REST request in the second step. it returns all the features...  ... View more

John Yaist‌ Update: This strange behavior only happens when Feature Service being queried is published to the Federated ArcGIS server directly --  this is my case. I tried to upload the same FGDB zip file to our ArcGIS Portal and publish it there as a hosted service, it works fine.  ... View more

Hi John Yaist‌ Thank you for looking into this. I tried the same code in a 1.7.1 version, it gives me same result. Here is the environment: The geometry of the filter is quite complicated as shown below: val_flayer is the cadastral feature layer. The feature service I am using is for internal use and behind our organisational firewall, which is unfortunate, otherwise,  it would be easy to reproduce the issue.  Thanks ... View more

No worries.  I also tried the same query on a large point layer (the centroids of the features in the original polygon layer), and it works fine. so it happens on polygon layers, I haven't tested polygon lines which I don't use very often.  Hope we can get the attention from a member in the Dev Team? John Yaist‌ ... View more

Hi Joshua The geometry filter is a ploygon that returns all the land parcels that intersect with it. Here is an update on what I've done: I exported JSON of this geometry and tried it in the REST API, it works perfectly. In Python API, the geometry works fine if only IDs, or counts are returned. so my current workaround is to return all the IDs then query the same layer again using the where parameter to return all the features, which works fine, but apparently this is not the ideal way to do it. I also tried this in a standalone script, same issue. So it's not a Jupyter notebook bug either. so far I can pretty much isolate it to ArcGIS Python API. I just need ESRI to confirm my guessing.  I've send ESRI a support request,  and I'll keep this post updated when I hear from them. Cheers Simo ... View more

Yes, I tried that. the query does not return all the features intersecting with the input geometry. This only happens when the geometry filter is being used. there's no problem with the attribute filter using the where parameter. ... View more

Thanks for the response. I tested the same spatial filter in REST API, it seems returning all the records. So it is clear to me the issue is in the python API.  ... View more

An update: ESRI Just confirmed this is a bug for Classic Collector for ArcGIS on iOS. BUG-000100412 : Two related records are created by Collector for ArcGIS when two users with separate devices make offline edits to the same feature, despite the one-to-one (1:1) cardinality. ... View more

Good stuff. But one thing is missing in the new map viewer, and it has been working in the current map view: showing related tables. hope this function will be put back in the final release. ... View more

ArcGIS API for Python does not require a license, but it is built for ArcGIS Portal and ArcGIS Online which are licensed. ArcGIS Pro has ArcGIS API for Python installed along side with Arcpy, which brings much more powerful capacities when dealing with local GIS. ... View more

Just an update in case someone is searching for the answer for the same question. This is a bug confirmed by ESRI. BUG-000126431 : The option to save username and password to connection file is ignored for OGC services in ArcGIS Pro. ... View more

I absolutely agree with Robert about WAB as a platform with responsive design baked in. and it is useful for many in many cases.  I mainly suffered from using the WAB Developer Edition (WAB DE)to develop custom widgets. The reason I use WAB DE is because I am not confident I can architect a sound application framework by myself(maybe also not worth it only for my project), and WAB DE can provide me a framework to start with.  but unfortunately this framework is not documented, only very basic document for how to build a widget ---- but, but the interface provided for the custom widget to communicate with the framework and other widgets (out-of-box widgets and custom widgets ) are ridiculously simple and useless in most of my cases.  If I am provided sufficient interface to use, I won't be tempted to go to the backstage (jimu library) to see how it is implemented. I can read jimu and I did read some modules, but without any documentation I won't say it was as easy and pleasant as reading a romantic novel, if I can read it as easy and pleasant, I may be better off to create my own application framework and claim I am a software architect, lol. Anyway, ESRI does not seem to encourage us to understand the application framework otherwise they will provide some documentation.  Just to show you what I mean, let's take a look at the widget.js of the Measurement widget (I randomly choose this): Without documentation, how can I dream up loading those jimu modules if I want to create widget like Measurement widget?? The so-called WAB API Reference (CSS framework—Web AppBuilder for ArcGIS (Developer Edition) | ArcGIS for Developers )  is so simple and inadequate, that I have to wonder what API, where is it? I was forced to read the jimu source code to learn the application framework, I am sure you will agree this is not the easiest way to learn--- I've learnt other frameworks before. In my view, a framework/API without document is only half baked. I would like to urge ESRI to slow down the new widgets development, and instead change course to support developers with the greater knowledge about framework and APIs, by doing that more useful custom widgets will be created and shared by developers in the ESRI WAB Community. Overall, developers know better what widgets their clients need than ESRI staff working in their office, ESRI staff know their own framework and API much better than anyone else!   ... View more