Latest Contributions by GlenColgate1

The following code shows our attempt to add all locators found in our Portal (Enterprise 11.3) to the active project in ArcGIS Pro (3.3.1). public async void AddLocators(MapView mapView, CancelableProgressorSource progress) { await QueuedTask.Run(async () => { var portal = ArcGISPortalManager.Current.GetActivePortal(); PortalQueryParameters query = PortalQueryParameters.CreateForItemsOfType(PortalItemType.GeocodingService); LocatorManager lm = mapView.LocatorManager; do { PortalQueryResultSet<PortalItem> portalResults = await ArcGISPortalExtensions.SearchForContentAsync(portal, query); if (portalResults.Results.Count <= 0) break; progress.Max =(uint) portalResults.Results.Count; foreach (var item in portalResults.Results.OfType<PortalItem>()) { await lm.AddLocatorAsync(item.Path); progress.Progressor.Value += 1; } query = portalResults.NextQueryParameters; } while (query != null); }, progress.Progressor); }   The code completes successfully with one issue... The results shown in the catalog pane have two rows for every locator found. (attached file is a screenshot showing the results in catalog pane.) The first row has a path ending in GeocodeServer (ex. https://<host>/<context>/rest/services/Locators/Locator_AllFeaturesGISID/GeocodeServer). This version of the locator is what I would consider more correct as its path matches what we see in Rest Service Directory. But it is not functional in ArcPro. The second row has the service name repeated at the end (ex. https://<host>/<context>/rest/services/Locators/Locator_AllFeaturesGISID/GeocodeServer/Locator_AllFeaturesGISID). This locator is functional in ArcPro and matches the path of a locator the was manually added to the project using pro's Add Locator tool/command. Anyone care to take a stab at what might be causing the weird results? ... View more

When new features are created in GIS to represent future facilities, they are introduced to the Utility Network with "Approved" lifecycle status value. This status distinguishes these features from the rest of the network as they are not yet in service or possibly not even constructed. This is an important stage of the construction process and these new features should be available to edit, analyze and map along with all of the other features. Their inclusion is presenting us a problem building our subnetworks in a way that allows us to include/exclude approved features. Adding approved features as a condition barrier, then connecting approved to active lines will prevent traversability when trying to build the subnetwork. If we don't include approved as a condition barrier they are returned in subnetwork tracing.  This makes the result incorrect since the new approved features should not affect the network until the features are active in the field and provided an "In Service" status in our GIS. Our idea is to allow the network to IGNORE features of a designated condition (lifecycle state = "Approved") and let the remainder of the utility network to function as if they do not yet exist. ... View more

In ArcGIS Pro 2.8.1 we are trying to create a replica using arcpy.management.CreateReplica(). The replica is present in both database and arcpy.management.SynchronizeChanges() completes without error. The edits applied to each database is not making across the replica sync into the other database. We have reviewed the prepare-data-for-replication.htm page for possible clues as to what might be going wrong but have yet to find the culprit. Questions: Is the difference in database geometry type (SDO_GEOMETRY in Oracle vs ST_GEOMETRY in PostgreSQL ) causing the replica to ignore/discard data edits? What other gotchas could be hiding in our schema/data that would cause an ArcPro replica to appear normal but fail to pass edits between databases? Thanks, G ... View more

By all documentation that I can find ArcPro should refresh the data in a map after running a custom geoprocessing tool. This has not been my experience so far. I have tried to make this tool several different ways. The edit completes successfully, but does not show in the map unless I refresh the map view in the versioning tools. Some think that the automatic refresh will be triggered if the tool has a derived output. Others have said that it will be triggered after the arcpy.da.Editor operation is closed as long as we are working in the "CURRENT" but not sure what that means in determining a workspace. The example below incorporated all of the documented recommendations without success. All we want is a simple tool that updates a select number of attributes on an existing layer and saves them inside of the current version (shown in the map without additional action by user). Any recommendations appreciated. Built with ArcPro 2.6.2 using the New Script wizard with a single input param and a single derived output param: # Import system modules import arcpy # Set the parameters InputIDF = arcpy.GetParameterAsText(0) #Process: Start Edit prev_workspace = arcpy.env.workspace arcpy.env.workspace = arcpy.Describe('GPS').Path edit = arcpy.da.Editor(arcpy.env.workspace) edit.startEditing(False,True) edit.startOperation() arcpy.SelectLayerByAttribute_management('GPS', 'CLEAR_SELECTION') with arcpy.da.UpdateCursor('GPS',['IDFEATURE','QAPNTUSE'],'IDFEATURE={}'.format(InputIDF)) as cursor: for row in cursor: row[0] = None row[1] = 5 cursor.updateRow(row) del cursor # Cleanup edit.stopOperation() edit.stopEditing(True) arcpy.ClearWorkspaceCache_management() arcpy.env.workspace = prev_workspace # Set layer as output param p = arcpy.mp.ArcGISProject("CURRENT") m = p.listMaps()[0] l = m.listLayers('GPS')[0] arcpy.SetParameter(1, l)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

We would find it much easier to use the Assignee filter list if it was ordered by worker lastname. Currently it appears to be ordered by objectid (order the user was added to project). ... View more