Latest Contributions by BrittanBattles3

Hello, Working in GeoEvent 10.6.1 I am curious if a workflow can be crafted for GeoEvent Server to ingest .csv files but track the updates via an objectID, similar to how GeoEvent can track incremental updates when polling a feature service? I have an application that will output .csv files into a folder when a database update is complete, but I want to be able to  track incremental updates with an objectID so we aren't mapping duplicate points. Any ideas on how to accomplish this in GeoEvent? I thought about polling a service from the big data store that stores the duplicate points by polling using the incremental update option to filter duplicates, but 2 GE inputs/services/outputs seems redundant and is really slow in our GeoEvent Environment and seems to not poll all features before the input "freezes up". Any ideas? ... View more

Getting the following error below when trying to edit a versioned feature class in an SDE database using a python script tool: Traceback (most recent call last): File "L:\Tools\Models\ReconcilePostCalcFields&RecreateVersions.py", line 32, in <module> for row in cursor: RuntimeError: workspace already in transaction mode Code is below: import arcpy, os # Set workspace workspace = "Database Connections\\Connection to gis-prod.sde" # Set the workspace environment arcpy.env.workspace = workspace # Create Version using SDE credentials arcpy.CreateVersion_management (workspace, "sde.default", "fieldcalcs", "PUBLIC") # Delcare variables ##versionList = arcpy.ListVersions('Database Connections\\Connection to gis-prod.sde') inFeatures = "sde_m.SDE.PARCEL" zip5expression = "!MAIL_ZIP![0:5]" fl = "fl" # Change Workspace to access data via OS Auth. workspace2 = "Database Connections\\SDE_MPL_PROD_OSAUTH.sde" arcpy.env.workspace = workspace2 # Create Feature Layer for editing arcpy.MakeFeatureLayer_management (inFeatures, fl) # Change Version arcpy.ChangeVersion_management (fl,"TRANSACTIONAL", "sde.fieldcalcs") # Start an edit session. Must provide the workspace. edit = arcpy.da.Editor(workspace2) # Edit session is started without an undo/redo stack for versioned data edit.startEditing(False, True) # Start an edit operation edit.startOperation() # Calculate the MAIL_ZIP5 field fields = ['MAIL_ZIP5'] with arcpy.da.UpdateCursor(fl, fields) as cursor: for row in cursor: row[0] = zip5expression cursor.updateRow(row) # Stop the edit operation. edit.stopOperation() # Stop the edit session and save the changes edit.stopEditing(True)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If I comment out the UpdateCursor section, the script runs successfully. I have also tried to reconcile, post and delete the child versions before executing the script with the same failure, all locks on the database are shared locks. I thought by versioning and editing, I could get around any locking issues. Any idea how to get the workspace out of transaction mode to allow editing to the child version created in the script? ... View more