Latest Contributions by Jay_Gregory

Thank you - you might be right the general use cases might be minimal.  Our primary use case is aviation data - a lot of systems export flight data as lat / long / altitude in CSV format, so easily being able to view this in 3D would be useful.   ... View more

Thanks for the response - this pattern makes sense but seems a little cumbersome -so there is no way to enable this on creating a feature layer from a CSV (which is useful because it infers your schema), and no way to enable it after a feature service has been created? ... View more

100% agree.  ... View more

Thanks - its good to get a read from the community.  There is a lot of text in the file, which is probably why it's taking so long.  A lot of our users don't have Pro, so want to set the understanding of how long things might take.  ... View more

With respect to this specific issue, I found that is occurs whenever you pipe output of a Python script with an arcpy command.  The script will execute fine until it reaches the arcpy command (import arcpy will work though).   So python myarcpyscript.py will execute fine, but python myarcpyscript.py >> myarcpylog.log will terminate ungracefully with Fatal Python error: Py_Initialize: can't initialize sys standard streams    OSError: [WinError 6] Invalid handle. Esri support confirmed this is an issue at 10.9.1 (and maybe earlier), but was fixed at 11.0.   ... View more

Did you ever figure out what was happening? Running into this same issue at 10.9.1 as well. Running script manually works fine but thought crontab receiving the same errors listed by @SiCasley  ... View more

This is a really pesky issue.  I have confirmed that my spatial query should return 1931 records (confirmed with local data via ArcGIS Pro as well as REST query with returnCountOnly set to true).  However, using a utility function that paginates through results using the exceededTransferLimit flag, I get back 2370 results.  My function submits an initial query which returns 1931 results, but the exceededTransferLimit flag is set to true, so it submits a second time with the resultOffset set to 1931 and gets back 439 features with no exceededTransferLimit key (not even set to false - it's just not included in the response) so my final result set is 2370 records instead of 1931.  The python API only returns 1931, so that seems works, but I have users just using Python requests.  Is there something I'm implementing incorrectly? def paginate_queries(query_url:str, params:object, features:list=[])->pd.DataFrame: if len(features)>0: params['resultOffset']=len(features) result = requests.post(query_url, params=params).json() print(f"{len(result['features'])} features returned") newfeatures = features + result['features'] if ('exceededTransferLimit' in result.keys()) and (result['exceededTransferLimit']): return paginate_queries(query_url, params, features=newfeatures) return pd.json_normalize(newfeatures)   ... View more

Oooof - this was a while ago and somewhat annoying.  In our case, we kept the same Portal URLs and just changed the Server context to /server from /arcgis.  So we broke the federation, changed the server context, and refederated.   What happened was every service was republished, and created new Portal items for every Server service.  This didn't pose a ton of problems with MapServices, utility services, etc. on Server - we just had to delete the old items from Portal referencing the old Server URLs.  Also updating any content (feature layers, maps, etc. with new Server urls).  However with hosted feature services from datastore, we lost the (hosted) or (hosted, view) labels in the content explorer, and it was a pain to fix (need to go into the Portal content directory and manually change some things in the json files).  Survey123s and Workforce projects needed some additional remediation, since there are multiple types of linked assets created.  I forget the details on that one because there was only a couple and some users were happy republishing their Surveys.   Hope that helps!  Good luck! ... View more