Latest Contributions by KenGalliher1

Hi @RobertChaney  To recalculate the extents in a feature service (published) parcel fabric, the service needs to be stopped and the geoprocessing tool run on the enterprise geodatabase feature classes. The service can then be started and the new extents should be reflected immediately.  This can be done with a short arcpy script: import arcpy from arcpy import env gdb = r"/path/to/enterprise/geodatabase.sde" env.workspace = gdb fds = "fabric_feature_dataset" for fc in arcpy.ListFeatureClasses(feature_dataset=fds): arcpy.RecalculateFeatureClassExtent_management(fc)   Regarding the "calculating extent" popup, there might be something more going on. I would suggest opening a support case where they can take a look. ... View more

For branch versioned feature classes, the version differences can be found with the REST API. This was implicitly mentioned here with the ArcGIS Pro .NET SDK using the Differences method. Differences—ArcGIS REST APIs | ArcGIS Developers It is also possible to retrieve the differences with the ArcGIS Python API arcgis.features.managers module | ArcGIS API for Python   from arcgis import GIS from arcgis.features._version import VersionManager gis = GIS( "https://server.domain.com/webadaptor/", "user", "password" ) version_manager_url = ("https://server.domain.com/webadaptor/rest/services/FeatureServiceName/VersionManagementServer") version_management_server = VersionManager(version_manager_url , gis) with version_management_server.get("owner.version_name", "read") as version: differnces = version.differences(result_type="features", layers=[15]) ''' Result: { "differences" : [ { "layerId" : long, "inserts" : [ <objectId> ], "updates" : [ <objectId> ], "deletes" : [ <objectId> ] } ], "features" : [ { "layerId" : long, "inserts" : [ { "attributes" : { "OBJECTID" : 581, "SUBTYPE" : 3, . . . "SHAPE.STLength()" : 132.5 }, "geometry" : { "hasZ" : true, "hasM" : true, "paths" : [ . . . ], "success" : <true | false>, '''     ... View more

Hi Dean, Thanks for bringing this up. I am getting mixed results with different methods. I am not able to reproduce the issue using Pro 3.2 or Pro 3.1.4 from the Python Window with an open map (target_map("CURRENT")) or from a script pointing to the map project. Interestingly, I can reproduce it with a Notebook using an open map (target_map("CURRENT")). To make sure we're on the same page, with the sample code above, are you expecting only the parcel fabric to switch to the version? I believe we determined that we had to iterate through all of the feature layers to change their version. This is my map after targeting only the parcel fabric:   UPDATE: I ran the script from the Python window and the parcel fabric and parcel layers all change version. The topology does not:     ... View more

As long as the gisadmin user does not have any elevated permissions you should be able to copy the data. Look out for things like "sysadmin" or "db_owner". Those roles will alter the schema name and cause the error you saw. ... View more

Can you provide the following info:   1. The dbms or gdb type of both the ArcMap data and the Pro data. Is this an enterprise gdb, file gdb or mobile gdb? 2. Is the polygon feature class in a parcel fabric or a simple feature class? 3. How many polygons are being calculated?  ... View more

Hi Ruth, While many Parcel Fabric operations can be performed with Geoprocessing tools by themselves or in a model, many cannot. However, if you are using a published feature service fabric, you have access to all parcel fabric functions either via REST or with the ArcGIS Python API. arcgis.features.managers module | ArcGIS API for Python All parcel fabric tools are available as functions in the Python API including Duplicate and Merge as you mentioned. We have some tutorials for getting started here: Part 1 - Introduction to Parcel Fabric layers | ArcGIS API for Python  Part 2 - Branch Versioning with Parcel Fabric | ArcGIS API for Python Part 3 - Create a New Parcel Record | ArcGIS API for Python Part 4 - Query Parcels | ArcGIS API for Python Part 5 - Merge Parcels | ArcGIS API for Python The set of tutorials includes working with branch versions and creating parcel records with the FeatureServer endpoint. Also, while the tutorials use Notebooks, the code can be used in standard Python scripts. Thanks, Ken ... View more

Great presentation! ... View more

Hi Dean, It would be nice if the Pro Mapping module had a refresh method for a current map or view object. This would make a great enhancement request. We can hack a workaround using a selection and panning to the selection. I see in your UpdateCursor you are updating a specific feature. By using that feature's objectid, we can select it then pan to it. That should redraw the layers and show the edit. # also get a map 'view' from the project view = thisProject.activeView with arcpy.da.UpdateCursor(AnnoLyr, ["MapNumber"], "OBJECTID = 7695") as cursor: for row in cursor: row[0] = MapNumber cursor.updateRow(row) edit.stopOperation() edit.stopEditing(save_changes=True) # select the edited feature then pan to it AnnoLyr.setSelectionSet([7695], "NEW") view.panToExtent(view.getLayerExtent(AnnoLyr), selection_only=True)   Let me know if that helps.   Ken ... View more

I'm glad it's working! And yes, you will have to watch out for that extra slash when building up URLs. I'm not sure if there's a more efficient way to get them. Although it's hard to see in the Python API sample, the trailing slash is in the base_server_url variable. Ken ... View more

Hi Dean. I am seeing some issues using Pro's Python window as well. I'll continue to look into it. In the meantime, can you try the same thing using a Pro Notebook? I am not getting any errors getting the fabric and version manager.     ... View more