Latest Contributions by MikeQuetel1

The "Create Locator" GP tool will output a locator where the "Match with no zones" option is set to "NO".  This option is not parameterized and the default value is not influenced by the presence or absence of administrative zones in the source data and GP tool configuration. New locators always have this option set to "NO" by default.  This default value of "NO" is contrary to an esri tech support best practice document and results in poor geocoding success when compared with setting the value to "YES". We automate the creation of locators with a model or python script.  In order to significantly improve geocoding success and to follow esri best practices, someone must interactively update each locator and change the "Match with no zones" option from "NO" to "YES".  This must be done for each individual locator as well as repeating the process for any composite locator that they participate in. We would like esri to make this option accessible as a parameter with the "Create Locator" GP tool and if necessary also with the "Create Composite Address Locator", so that output locators do not need to be interactively re-configured in order to follow esri best practices and achieve usable geocoding success.  At minimum, the default should be changed to "YES".     ... View more

Our organization performs silent installs of ArcGIS Pro via powershell script.  These are per-machine installs and the vast majority utilize a concurrent license via an on-prem. license server.  We have some edge cases where we would like to alter the license type of be a named user... for example if a VPN connection is not available to a user. I'm inquiring if there is a supported way of doing this in a scripted fashion, without having to completely uninstall the software and delete registry keys such as "HKCU:\SOFTWARE\ESRI\ArcGISPro" and "HKCU:\SOFTWARE\ESRI\ArcGIS Online For Pro"... then re-install using appropriate MSIEXEC switches to setup the new, default license type. Thanks in advance! MQ ... View more

Hi, I'm polling for JSON and inserting/updating a SQL Server backed feature class.  It's mostly working... I'm getting features into the database, but I just can't seem to handle the booleans  in the JSON correctly.   There is sample data from the feed at the bottom of this post... for example, the "has_kisosk" field is going to be true/false. The input geoevent definition has that field as a bool, and if I write that event directly out to JSON, the value comes across fine. Getting it into the database is the problem.  My database schema is a bit different in terms of field names.  Also, booleans are stored as smallint or bit fields in SQL Server (I'm using smallint). So, my output geoevent defintion has the boolean field as type "short"and I use a field mapper to make that transformation from input to output geoevent defintion. The problem is that all boolean fields come across as null from the output geoevent def.  This is consistent in the database as well as if I write this output geoevent defintion to JSON.  If I make the output geoevent defintion also use type "boolean" then I can see the values in my output JSON, but the feature service records the following in the ArcGIS server log:     Error: The value type is incompatible with the field type. [HAS_KIOSK].     So it seems like booleans aren't being automatically transformed into shorts (or other integer types).  Can anyone provide some pointers on how to handle this? Thanks in advance!       { "data": { "stations": [{ "lat": 45.51898132, "rack_model": "CITY_PILOT_RACK", "legacy_id": "1440914125193298376", "address": "Park Avenue West, Southwest Yamhill Street, Portland", "region_code": "PDX", "name": "SW Yamhill at Director Park", "eightd_station_services": [], "rental_uris": { "android": "https://pdx.lft.to/lastmile_qr_scan", "ios": "https://pdx.lft.to/lastmile_qr_scan" }, "capacity": 20, "eightd_has_key_dispenser": false, "station_id": "1440914125193298376", "lon": -122.6812685, "station_type": "lightweight", "has_kiosk": false, "electric_bike_surcharge_waiver": false, "external_id": "motivate_PDX_1440914125193298376", "dockless_bikes_parking_zone_capacity": 20, "client_station_id": "motivate_PDX_1440914125193298376" }] } }         ... View more

Is there any way to get a better understanding about why group.remove_users() would fail to remove member(s) of a group?  The accounts in question are simply members of the group (not owner or group managers). The group in question actually contains no content and I'm using the owner of the group to connect to portal with the python API.  If I login to portal with the same group owner account, I can interactively remove the user from the group. INFO | 2020-07-27 07:57:38,431 | Begin synchronizing users for group: PBOT (1120) INFO | 2020-07-27 07:57:38,438 | Querying existing membership... INFO | 2020-07-27 07:57:38,938 | Group currently has 233 member(s) INFO | 2020-07-27 07:57:38,970 |  2 user(s) will be removed from group {'notRemoved': ['member1', 'member2']} INFO | 2020-07-27 07:57:39,218 | No users will be added to group ... View more