Latest Contributions by James_Whitacre

@DougBrowning I tried to be very clear about the severity of this bug...hopefully they continue to listen. Were you using ArcGIS Pro 3.0 or 2.9.x? I have since moved on from the project where I was dealing with this issue and it hasn't resurfaced (yet!!) in any new projects... ... View more

@jessneuner, I never found a resolution, but I have not really had further issues with this recently and I have not had any users have significant issues with this issue. It could be related to some Windows and ArcGIS Pro updates, as we have updated lots of software since I first posted about this issue. I can't recall the Windows version we updated to, but we are now on ArcGIS Pro 2.9.3. Hope that helps. ... View more

@MichaelVolzNo. My organization uses VMware Horizon VDI as the primary way to use ArcGIS Pro as we are a distributed workforce across many offices and we are not authorized to telework (at the moment), which also means that this is our normal use of ArcGIS. Most of us do not have physical desktops, only laptops. While our laptops are capable of running ArcGIS Pro, they are not spec'd to handle many of our advanced ArcGIS Pro workflows and needs. Part of what I am looking for with my questions here is guidance on how to adjust the VDI settings or ways to set up ArcGIS Pro, if possible. And if any of that can't be done, then I will seek to influence Esri or VMware to make their products work better together. ... View more

Quick update on this... I was able to go to https://<web server hostname>/arcgis/rest/adminservices/<service name./FeatureServer/refresh (<web server hostname. was my ArcGIS Online REST URL) to restore everything to normal...but, this was a bit scary... ... View more

This is clearly still an issue/bug. Additionally, when I changed the owner for a hosted feature layer and associated views, I keep getting: Unable to add layer [layer name] Unable to establish a secure HTTPS connection to the layer. The layer, [layer name], cannot be added to the map. Now the maps that use the main hosted feature layer don't work, but the views work just fine...makes not sense. Any help on this issue would be much appreciated. ... View more

THIS IS A SERIOUS ISSUE THAT ESRI NEEDS TO ADDRESS ASAP!!! ESRI PLEASE ADDRESS AND SOLVE THIS ISSUE!! I am also seeing this issue. I am not working in Survey123, but I am working with an ArcGIS Online feature service using a one-to-many relationship between point feature layer (key field: GlobalID) and polygon feature layer (key field: GUID), which is how Esri suggests creating relationships. I don't want to get into the details of my use case because it is a bit complicated and I can't yet share my code, but here is the basic pseudo-workflow in Python (Note: 'feature layer'=ArcGIS Online; 'feature class'=file GDB: Copy the selected point feature layer to the local scratch GDB as a feature class. (Note: Yes this is needed...too many details to explain why...no comments on this please) Use a arcpy.da.SearchCursor to extract the field values from the point feature class that will be populated to the polygon feature class, including the GlobalID. (Note: I think it is at this point that the GlobalID is converted from lowercase alpha chars in the feature layer to UPPERCASE alpha chars in the feature class. It also appears that the GlobalID field is converted to a string Python data type by the cursor.) Series of arcpy geoprocessing tools to create the feature class polygons in the scratch GDB. A GUID field is created in this step and calculated from the search cursor GlobalID of the point feature class. I also add '.lower()' to the GlobalID string. It calculates, but is still UPPERCASE alpha chars. Feature class polygons are appended to the polygon feature layer. Polygon feature layer GlobalIDs and GUID values retain UPPERCASE alpha chars. So what happens to the relationship? When selecting the point features in the feature layer, the polygons do NOT show up as related. BUT! When I select a polygon from the feature layer, the point feature shows up in the relationship! Super weird...lowercase-to-UPPERCASE does NOT work, but UPPERCASE-to-lowercase does work!?!?!? So, here are my questions... WTH is going on? Why are the AGO feature layers able to accept both lowercase and UPPERCASE GUID values, but file GDB feature classes only seem to accept UPPERCASE? Why does the relationship work one way, but not the other? Is this issue at the OS/Windows level with how it deals with UUIDs? Why does the GlobalID come out as a string datatype instead of a UUID or other class or byte-type? Do joins between GlobalIDs and GUIDs act like strings? If so why? At any rate, all of this seems like some major design flaws that need to be fixed or tightened up. If Esri is going to tell us to use the GlobalID-to-GUID relationship key structure, these field-types and value-types need to be very strict. I thought they were...clearly I am WRONG! Sorry for the rant, but this could derail a major project I have been working on for some time and this may require that I go all the way back to my GDB schema design and rework all of my Python code, and I do not want to do that.   EDIT: So, a workaround I discovered (that will NOT require me to go back to square one!) is to calculate the GUID field in the polygon AGO feature layer so that the values are lowercase (e.g. !GUID_Field!.lower()). While this will work, I still stand by my comments above, and I would hope that any programmer would agree that this is a flaw and that this extra step is asinine. EDIT: Now the Append tool is refusing to append the GlobalID to the GUID field so the relationship can be made. This has really turned into a massive CF (sorry for the foul reference, but there is no other better descriptor...). Esri, any feedback here?? Please? ... View more

Thanks @OwenGeo, I will now sleep better tonight! I will bookmark the article as well. ... View more

@JoshuaBixby I am working with ArcGIS Pro 2.7, and I am not working with raster datasets in the memory space in this case. The 'temp_feature' variable is a feature class that is the input points for the Viewshed 2 tool. ... View more

Reviving this conversation... I just had an issue where I was using: temp_features = r'in_memory\Features_Temp' Then I was updating code for ArcGIS Pro and changed it to: temp_features = r'memory\Features_Temp' The temp_features are being run through Viewshed 2 Tool. When run using 'in_memory\', everything works as expected. But when run through 'memory\', the tool fails with an '010471: No observers found in analysis extent.' error. Any ideas why this may be? Thanks. ... View more

Also, having a sound when averaging a point is complete would be helpful. Vote this up guys!! ... View more

Also, having a sound when averaging a point is complete would be helpful. Vote this up guys!! ... View more

I am having this same issue when I choose Closest to Average Height for the Point Selection Method. I am also using 3D Thinning Dimension. After clicking run, the 000426: Out Of Memory.—ArcGIS Pro | Documentation error presented immediately. Running ArcGIS Pro 2.6.1 and working with Pix4D photogrammetry-derived LAS files version 1.2. ... View more

I tried the prescribed work around and I am still getting the error. The bug report referenced above indicates a modified date for the date of this post, September 28, 2020, when accessed on the same date. Not sure what that means, but clearly there seems to be other issues with this bug.  ... View more