Latest Contributions by Brian_McLeer

In trying to migrate Python Scripts from ArcGIS Desktop Python 2.7.x to ArcGIS Pro 3.x, we email staff if there is a failure on a routine. Below I am running a sync replica routine using ArcGIS Pro, deliberately breaking it on the file path to the database connection string so it will email a failure. Somewhere in migration, it does not like the email code that has been working for years now. Has anyone else had to upgrade email failures from 2.7.x to 3.x in Python? With using the correct file path, the routine was successful. We use Windows Task Scheduler to run Python routines.  I receive the error (server name omitted for security):  try: arcpy.management.SynchronizeChanges(r"C:\Tech_Info\DB_CONX\SERVER\SERVER ParentDatabase user.sde", "ReplicaName", r"C:\Tech_Info\DB_CONX\Server\SERVER ChildDatabase user.sde", "FROM_GEODATABASE1_TO_2", "IN_FAVOR_OF_GDB1", "BY_OBJECT", "RECONCILE ") except Exception as e: arcpy.AddMessage("SynchronizeChanges_management ISGIS.ReplicaName Failed..." +'\n') txtFile.write("SynchronizeChanges_management ISGIS.ReplicaName Failed..." +'\n') txtFile.write (arcpy.GetMessages() + '\n') HOST = "host.server.com" SUBJECT = "Priority: CRITICAL Routine Failure" TO = "email@python.org" FROM = "Routine Failure<failure@python.org>" text = "Routine has failed. Please see log file for detailed information. \n Error Message: \n " + str(e.msg) BODY = string.join(( "From: %s" % FROM, "To: %s" % TO, "Subject: %s" % SUBJECT, "", text ), "\r\n") server = smtplib.SMTP(HOST) server.sendmail(FROM, [TO], BODY) server.quit()‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Environment: ArcGIS Desktop 10.6.1 Below, I am attempting to snap a point feature class to the geometry of an address feature class based on a common 'Master ID' field using a join. The code originally comes from arcgis desktop - Snapping point to point based on attribute? - Geographic Information Systems Stack Exchange  However, this is not moving my points, and the data is clean and does match up.  arcpy.MakeFeatureLayer_management("D:\\WorkSpace\\POI\\Workspace.gdb\\COH_POI", "POI_Layer", "", "", "") arcpy.SelectLayerByAttribute_management("POI_Layer", "NEW_SELECTION", "MASTER_ID IS NOT NULL") pt_on_line = "D:\\WorkSpace\\POI\\Workspace.gdb\\COH_Address" pt_on_line_ID = 'MasterID' # common ID field pt_off_line = "POI_Layer" pt_off_line_ID = 'MASTER_ID' # common ID field pt_on_line_dict = {str(row[0]):row[1] for row in arcpy.da.SearchCursor(pt_on_line,[pt_on_line_ID,"SHAPE@"])} # make dictionary, like {ID:geometry} with arcpy.da.UpdateCursor(pt_off_line,[pt_off_line_ID,"SHAPE@"]) as cursor: for row in cursor: # loop through points row[1] = pt_on_line_dict[str(row[0])] # move point geometry to match point geometry from dictionary cursor.updateRow(row) # update the geometry del cursor, row‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

We are using branch versioning for the first time in an SDE database (SQL Server 2016).  For our existing traditional versioning DBs, we use the recommended compress, rebuild indexes, and analyze datasets in our nightly routines similar to ESRI documentation below. This methodology is not recommended with branch versioning, however.  Is anyone using certain GP tools on a regular basis for database maintenance for an SDE database that uses branch versioning? If so, what methods are you using? Do branch versioned DBs require daily maintenance as traditional versioned DBs require? Enterprise geodatabase maintenance tasks—Manage geodatabases in SQL Server | Documentation  ... View more