Latest Contributions by DeanAnderson2

‎11-20-2023

Thanks for getting back to me. I am able to iterate thru all the layers. In interating through the list the script I USED to be able to include "Records" (FC/Layer) in the layer list. It now errors out saying that you can no longer do this. Best error message I get is when I use the "Change Version" tool on the "Records" layer. This also errors out in 3.2 (not 3.1X) python scripts. The problem comes when I try to use the python script to use the updateConnectionProperties method on the fabric (TaxlotsPF). When I use this the record is not accessible and if I try to create new record in this new version (because the fabric appears to have been moved) I ONLY see a "blank" menu (no prompts) or anything. I have attached the text script I used. Hope it helps. Again... The script allows me to change the feature classes / layers associated with the fabric (LOTS,PLATS,TAXLOTS,etc) and that all works fine. Changing other (non-fabric) feature classes (to the version) also works fine. The only layer that does not work correctly is the Records layers that is directly associated with the fabric .

‎11-20-2023

As a follow up. When I use the ChangeVersion tool in the python script as follows, all of the feature classes that participate in the record change. Unfortunately, the "TaxlotsPF: Records" feature class does not and remains in the old version. Versionmap = thisProject.listMaps("Map")[0] # same map as before pfLayer = Versionmap.listLayers("TaxlotsPF")[0] # same fabric as before edit = arcpy.da.Editor(WorkSpace) # my workspace edit.startEditing(False, False) edit.startOperation() arcpy.management.ChangeVersion( in_features=pfLayer, version_type="BRANCH", version_name=new_version_fullname, date=None, include_participating="INCLUDE" ) edit.stopOperation() edit.stopEditing(True) The results are.... All feature classes Except Records are transferred to the new eversion (also no error message).

‎11-20-2023

I am using ArcPro 3.2 accessing 11.1 Enterprise (will be upgraded soon to 11.2). I am testing my 3.1x code for creating a version in 3.2. I based my code on the ESRI Post (Part 2 - Branch Version with Parcel Fabric). This code has been working Great in 2.9 thru 3.1x. In 3.2 I can no longer change the version of the "Records" Feature class directly. However, this appears to happen when I change the version of the ParcelFabric that the Records feature class is a member of. Unfortunately, when I do this I can no longer create a new record in the new version. My steps for this test. 1. Create a new version (works great - no problem) 2. Get properties of new version (works great no problem) 3. Change the version manually (problems - Dialogue box is blank but code runs fine and version changes but problems) Code is as follows for changing the version is as follows: Versionmap = thisProject.listMaps("Map")[0] # Map map in my project (thisProject) pfLayer = Versionmap.listLayers("TaxlotsPF")[0] #TaxlotPF is my parcel fabric arcpy.AddMessage("-lyr: " + str(pfLayer.name)) # Just a message updated_props = pfLayer.connectionProperties arcpy.AddMessage(updated_props) # message to check properties arcpy.AddMessage('-----------------------') updated_props["connection_info"]["version"] = new_version_fullname # Props of the new version updated_props["connection_info"]["versionguid"] = new_version_guid pfLayer.updateConnectionProperties(pfLayer.connectionProperties,updated_props,auto_update_joins_and_relates = True, validate=True) new_props = pfLayer.connectionProperties Please let me know if I am doing something wrong ? I have tried several variations of this tool and also tried to use the changeversion tool. None seem to work.

‎10-02-2023

This is so cool. Thanks!

‎09-25-2023

Thanks! Always good to have somebody cleanup my code. Much appreciated.

‎09-25-2023

Better code - Again Thanks ! // Get map number from mapindex polygon layer var fsMapIndex = FeatureSetByName($datastore,"MapIndex",["MapNumber","ORMapNum","County"]) var fsIntersectMap = Intersects(fsMapIndex,$feature) if (fsIntersectMap == null) return {"errorMessage": "No Map Index Feature Found"} var MapNumber = "None" var ORMAPNum = "None" var County = 99 var intersectarea = 0 for (var f in fsIntersectMap){ var newintersectarea = Area(Intersection($feature,f)) if (newintersectarea > intersectarea){ var MapNumber = f.MapNumber var ORMAPNum = f.ORMAPNum var County = f.County intersectarea = newintersectarea} } return { "result": { "attributes" :{ "MapNumber" : MapNumber, "ORMapNum" : ORMAPNum, "County" : County } } }

‎09-25-2023

Thanks - that makes sense. Built this off of old code and was just pretty focused on making the area check work.

‎09-23-2023

The following code uses intersect and gets the largest intersecting polygon to make the assignment. It appears to be an OK workaround. // Get map number from mapindex polygon layer using interesect // Do interesect and county features. var fsMapIndex = FeatureSetByName($datastore,"MapIndex",["MapNumber","ORMapNum","County"]) var fsIntersectMap = Intersects(fsMapIndex,$feature) var MapIndex = first(fsIntersectMap) var intcount = Count(fsIntersectMap) // If no features return error if (MapIndex == null) return {"errorMessage": "No Map Index Feature Found"} if (MapIndex.Mapnumber == null) return {"errorMessage": "MapNumber is empty"} // If count is one then return values if (intcount == 1) return { "result": { "attributes" :{ "MapNumber" : MapIndex.MapNumber, "ORMapNum" : MapIndex.ORMAPNum, "County" : MapIndex.County } } } // if county > 1 (taxlot overlaps mapindex) then // loop thru and keep intersect with largest area. else { var MapNumber = " " var ORMAPNum = " " var County = 0 var intersectarea = 0 for (var f in fsIntersectMap){ var newintersectarea = Area(Intersection($feature,f)) if (newintersectarea > intersectarea){ var MapNumber = f.MapNumber var ORMAPNum = f.ORMAPNum var County = f.County intersectarea = newintersectarea} } return { "result": { "attributes" :{ "MapNumber" : MapNumber, "ORMapNum" : ORMAPNum, "County" : County } } } }

‎08-24-2023

Tim (as usual sorry to be so late in responding) The Max_arc_Angle step is not available if the Fit To Segments option is selected. From the documentation.... "This parameter is not available if the Fit to segments option is specified for the Fitting Type parameter."

‎08-07-2023

I have completed a bit more testing. I created a tool/python script that allows me to select any layer from my active map. Once selected I can then select any field and value to assign to that field (see attached zip that contains tool and python). What I found is that it appears that the errors ONLY occur with ArcPro Fabric Layers and does NOT happen with other layers in the branched version feature service. Perhaps I am calling the service incorrectly for fabric layers? I will report this to technical services. But, please try out the tool. It should operate on any branched version service. If not the code I uses is: Layer = arcpy.GetParameterAsText(0) FieldName = arcpy.GetParameterAsText(5) Value = arcpy.GetParameterAsText(6) thisProject = arcpy.mp.ArcGISProject("CURRENT") Map= thisProject.activeMap MapLayer = Map.listLayers(Layer)[0] MapLayerDataSource = MapLayer.dataSource lastslash = MapLayerDataSource.rfind("/") WorkSpace = MapLayerDataSource[:lastslash] arcpy.AddMessage("WorkSpace: " + WorkSpace) edit = arcpy.da.Editor(WorkSpace) edit.startEditing(with_undo=False, multiuser_mode=True) edit.startOperation() with arcpy.da.UpdateCursor(MapLayer,[FieldName]) as cursor: for row in cursor: if row[0] != None: arcpy.AddMessage(FieldName + ': ' + row[0]) row[0] = Value arcpy.AddMessage('-- ' + FieldName + ': ' + row[0]) cursor.updateRow(row) # End Edit Session edit.stopOperation() edit.stopEditing(save_changes=True) Thanks I would appreciate any second opinion on this problem.

‎08-04-2023

Amir - thanks for checking. This is similar to the issue I reported at the meeting in Redlands (I was using append for that) and BUG-000156383 I worked for a couple of months with user support on the issue and they thought it would be fixed in 11.1. It appears to not be fixed. Tech support had a pretty hard time setting the environment up and then replicating the problem. In addition, the work around reported does not work consistently. I tried to explain that to support but they could not replicate my workaround issues. I developed by own work arounds for my append tool but having the similar issue happen with s simple calculate using update cursor is a whole lot more serious. I was hoping to validate that this is a problem with someone else before again starting the rather complicated interaction with technical support. (explaining the problem, providing them with all of our data, services setup, working with them to customize the tool work in there environment , etc). Again, thanks for checking.

‎08-03-2023

The example fits around the entire script but you can use the same concept using python for each step. At the start of the step record your start time: starttime = datetime.datetime.now() At the end of the step record your endtime and calc the difference. endtime = datetime.datetime.now() timepassed = endtime - starttime

‎08-03-2023

I am pretty explicit when I do python and I write stuff out to a log file for scheduled jobs. I print results as well as write them to a text file. Is a bit redundant but oh well. Below is the code (I did not include the traceback stuff but that is also pretty easy to add... Here is the code.... import arcpy,os,time,datetime,traceback # Log File - makes my log file and records start time logfile = "C:\\GISLogs\\01APImportAnno.txt" arcpy.Delete_management (logfile) logfile = open(logfile, "w") starttime = datetime.datetime.now() logfile.write ('\n' + '\n' + "StartTime:" + str(starttime) + '\n' + '\n') print ("StartTime:" + str(starttime)) CODE GOES HERE # Time stuff and close of log file endtime = datetime.datetime.now() timepassed = endtime - starttime print ("Run Time: " + str(timepassed)) print ( "Start-End Time: " + str(starttime) + "---" + str(endtime)) logfile.write ('\n' + '\n' + "AnnImport Succesful" + '\n' + '\n' ) logfile.write ('\n' + '\n' + "Run Time: " + str(timepassed) + '\n' + '\n' ) logfile.write ('\n' + '\n' + str(starttime) + "---" + str(endtime)) logfile.close()

‎08-03-2023

It has been pointed out to me that this could all be done with an attribute rule and YES it could be. BUT... this problem seems to happen whenever I use the da.editor environment with branched versioning. I selected this example because what cold be simpler then calculating three fields for a selected set of polygons.

‎08-03-2023

This issue or similar ones have been previously been reported to ESRI (Esri Case #03242592) by me. I thought it was fixed at 11.x. This was also reported to this group (with no solution) back in 2019 (arcpy.da.Editor Not Working Properly) I am working on a project to develop best practices for migrating a series of tools that run in an ArcPro/Fabric GDB environment to an ArcPro/Fabric branched version environment (ArcProFabric 3.1+/Enterprise 11.1+). I am running into a consistently inconsistent problem with converting my Scripts/tools. Attached is a zip file the contains a toolbox with the tool (UpdateCogoArea) and associated python script (UpdateCoGoArea.py). For selected taxlots this tool calculates two attributes (TaxlotFeet/TaxlotAcre) from the CalculatedArea field and calculates the MapAcres field from the Shape_Area field. It’s a simple calculation and the three attributes are required for our state standard. Tool Requirements: ActiveBranchVersion, Selected Taxlots (Fabric) with the CalculatedArea field and the three required fields ('TaxlotAcre',"TaxlotFeet",'MapAcre’) all numeric/double. You can run this tool on your data if you add the fields and change the reference to your parcel fabric layer. Options: Within the python script you can change how the tool runs. It can either use the CalculateFields tool or use “arcpy.da.Editor” with an update cursor. (Line 42/43) In the script (useCalcFields = True or False.) Issues: The CalcFields Option works great. I do not set the edit environment etc. The UpdateCusor option causes strange results. When you run it a) the attributes are not updated (however if you open and close the session) they will be. b) if you spatially select the polygons and try to look at the attributes the table will come up with two records selected but you will NOT be able to see them (unless you open and close the project). My Question? Am I referencing the versioned workspace incorrectly? (I display the version and workspace as part of the script messages) Am I using the UpdateCursor with the arcpy.da.Editor incorrectly ? Is there a problem with our services or the software ? To Test: Add the three fields ('TaxlotAcre',"TaxlotFeet",'MapAcre’) to your ParcelFabric parceltype. Edit the UpdateCogoArea script and tool to reference YOUR parcel fabric layer (my layer is called Taxlot) make sure the python script has useCalcFields = false (line 43). This will run the tool using the da.editor and update cursor option. Open the project, select a couple fabric polygons (with calculatedarea populated) and run the tool (messages are below). See if the calcs worked, with the table open spatially select your polygons again – Note if the fields are updated and attributes updated. Close and re-open the project. Does this look and act as expected ? Select the polygons and calculate the three fields equal to zero. Close the project. Edit the python script and change useCalcFields = True and save Open the project. Select the polygons and re-run the tool. Review the results (Everything should operate as expected). For those that do not want to to the test here the two alternative. Again CalculateFields works but UpdateCursor and edit session does not. I have included tool messages for reference after the following code. # -------- This works --------- if useCalcFields: arcpy.management.CalculateFields(mapTaxlotLyr, "Python3",[["TaxlotAcre", "round(!CalculatedArea! / 43560,2)"],["TaxlotFeet", "round(!CalculatedArea!,2)"],["MapAcres", "round(!Shape__Area! / 43560,2)"]]) arcpy.AddMessage('Used CalcFields') sys.exit('Calcone') # ----------- This does NOT work ---------- # get workspace and version thisProject = arcpy.mp.ArcGISProject("CURRENT") Map= thisProject.activeMap mapTaxlotLyr = Map.listLayers("Taxlot")[1] # set data source and version (Not Needed for "CalcFields" but used with edit session) MapLayerDataSource = mapTaxlotLyr.dataSource lastslash = MapLayerDataSource.rfind("/") WorkSpace = MapLayerDataSource[:lastslash] arcpy.AddMessage("WorkSpace: " + WorkSpace) AfterVEq = MapLayerDataSource.rfind("VERSION=") + 8 Version = MapLayerDataSource[AfterVEq:] BeforeVID = Version.rfind(";") Version = Version[:BeforeVID] arcpy.AddMessage ("Version: " + str(Version)) # Do the edit edit = arcpy.da.Editor(WorkSpace) edit.startEditing(with_undo=False, multiuser_mode=True) edit.startOperation() with arcpy.da.UpdateCursor(mapTaxlotLyr,['CalculatedArea','shape__Area','TaxlotAcre',"TaxlotFeet",'MapAcres','Taxlot']) as cursor: for row in cursor: row[2] = 0 row[3] = 0 row[4] = 0 if row[0] != None: row[2] = round(row[0] / 43560,2) row[3] = round(row[0],2) if row[1]!= None: row[4] = round(row[1] / 43560,2) arcpy.AddMessage('Taxlot: ' + row[5]) arcpy.AddMessage('TaxlotAcre: ' + str(row[2])) arcpy.AddMessage('TaxlotFeet: ' + str(row[3])) arcpy.AddMessage('MapAcre: ' + str(row[4])) cursor.updateRow(row) # End Edit Session edit.stopOperation() edit.stopEditing(save_changes=True) Below are my messages referencing the version and versioned workspace... I would VERY much appreciate ANY Help. Thanks

Online Status	Offline
Date Last Visited	‎11-20-2025 11:48 AM

My Ideas

Latest Contributions by DeanAnderson2

Re: Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Re: Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Re: Provide methods to select and manipulate a parcel fabric record using Python or Model Builder.

Re: Arcade within() actually queries the feature it is within

Re: Arcade within() actually queries the feature it is within

Re: Arcade within() actually queries the feature it is within

Re: Arcade within() actually queries the feature it is within

Re: Using SimplifyByStraightLinesAndCircularArcs to help convert taxlot polygons from ArcMap to Fabric (ArcPro Fabric 3.1x)

Re: Problem with arcpy.da.Editor and Update Cursor

Re: Problem with arcpy.da.Editor and Update Cursor

Re: logging script performance

Re: logging script performance

Re: Problem with arcpy.da.Editor and Update Cursor

Problem with arcpy.da.Editor and Update Cursor

Re: Attribute rule not working with merge to updat...

Make the snapping settings per task – optional. So...

Re: Exporting a feature class with a related table...

Re: Exporting a feature class with a related table...

Exporting a feature class with a related table not...

Web AppBuilder Custom Widgets