Latest Contributions by DeanAnderson2

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  ... View more

I am working with a new taxlot dataset that requires building the fabric from just polygons (which is new to me).  I am following the documented recommendation to use "SimplifyByStraightLinesAndCircularArcs" (without it I end up creating WAY to many lines).  In some cases the conversion converts lines to curves that I do not think should be converted and it is a problem.  I have changed the parameters for max_offset,  max_arc_angle_step, min_arc_angle, and min_vertex_count to MANY alternatives. Some of the silly (see below) and some push the options to extremes.  But the changes do not seem to impact the outcome. For example, you would think a max offset of .01 would mean lines would not deviate from the original by more the .01 (or so).  But that is not the case and it appears I get offsets close to .1.        arcpy.edit.SimplifyByStraightLinesAndCircularArcs(         in_features=OutClassTxLtPly,         max_offset="0.01 Feet",         fitting_type="FIT_TO_VERTICES",         circular_arcs="CREATE",         max_arc_angle_step=2,         min_vertex_count=4,         min_radius=None,         max_radius=None,         min_arc_angle=2,         closed_ends="PRESERVE",         anchor_points=None     ) The taxlot dataset I am converting is pretty typical and contains rural and urban maps.  My question is...  Is there a best practice or are there recommended options (besides using the defaults) for running this tool on parcels to create an optimal result ???      ... View more

I have an issue with cleaning up after my conversion process. I am using 2.9X ArcPro.  I have many multi-part taxlots in ArcMap and need these to persist in ArcPro/Fabric.  I have good line attributes and want to build my taxlot parcel polygons from my good line attributes. (I understand the limitations of this and address it in my conversion process) Here is the part of my process that is generating the problem.  Convert ArcMap taxlotlines to ArcPro Fabric Taxlot_lines (works as expected - uses esri tool etc...) Split the arcmap taxlot polygons into multipart ArcPro polygons  (works as expected)  Generate points (polygon centroids) from the new multi-part ArcPro polygons (works as expected)  Create New ArcPro Polygons for converted ArcPro Taxlot_lines & New Points (works as expected)  Use Dissolve (or pairwise dissolve) to re-created multi-part polygons (Problem - Dissolve generates a small number  number of tiny slivers - see below).  Dissolve has no tolerance and it does not matter what option I use. Dissolve just seems to do this.   The rest of my process works as expected     Question: What is the best way to get rid of these slivers in 2.9?   When I build parcels from my polygons the slivers at duplicate lines or "near duplicate lines" in my taxlot_lines feature class.  My fabric has less then 20,000 polygons.   Due to upgrade issues with servers my folks will NOT be able to upgrade to 3.x / 11.x for quite some time.  ... View more