Latest Contributions by AlanDodson

I am having considerable frustration with updating metadata via scripting. I have an enterprise geodatabase with many feature datasets. Inside each feature dataset are many feature classes. All feature datasets and feature classes have metadata, which I need to update. There are 3 sources for my metadata (dynamically-defined items via scripting, synchronized properties, and a template) and I cannot get them to play nice with each other when it comes to displaying the extents of feature classes. Dynamically-defined items include the fd / fc title, summary, description and tags. Synchronized properties are extents, feature classes, fields, crs, etc. The template contains the credits, contact information (a few times), and other information - stuff that doesn't change regardless of what feature dataset or feature class is being shown. The most logical flow (in my head) is reflected in my current order of operations: Import template Update dynamically-defined items Synchronize With that flow, I've tried each of the metadata_sync_option choices; when using 'ALWAYS' everything syncs correctly for feature datasets, and everything syncs correctly EXCEPT Extent for feature classes. How can I get the Extents of feature classes to be properly shown? When I click the Synchronize button everything is perfect, but I need to do this via scripting. I've tried saving the metadata between steps, I've tried syncing before importing the template, after importing the template.... No joy.   Here is a minimal example of my code import arcpy import os from arcpy import metadata as md sde_connection = arcpy.GetParameterAsText(0) metadata_template_path = arcpy.GetParameterAsText(1) arcpy.env.workspace = sde_connection fds_list = arcpy.ListDatasets(feature_type='Feature') for fds in fds_list: fds_path = os.path.join(sde_connection, fds) fds_md = md.Metadata(fds_path) if not fds_md.isReadOnly: fds_md.importMetadata(metadata_template_path) # Here I add the metadata that is dynamically generated (title, summary, tags, etc) fds_md.synchronize(metadata_sync_option='ALWAYS') fds_md.save() else: arcpy.AddWarning(f"Metadata for {fds} is read-only") arcpy.env.workspace = fds_path fc_list = [] fc_list = arcpy.ListFeatureClasses() for fc in fc_list: fc_path = os.path.join(sde_connection, fds, fc) fc_md = md.Metadata(fc_path) if not fc_md.isReadOnly: fc_md.importMetadata(metadata_template_path) # Here I add the metadata that is dynamically generated (title, summary, tags, etc) fds_md.synchronize(metadata_sync_option='ALWAYS') fc_md.save() else: arcpy.AddWarning(f"Metadata for {fds}\{fc} is read-only") # reset workspace arcpy.env.workspace = sde_connection   ... View more

I have a fairly simple problem, and I've tried everything I can think of to fix it. I am using a data access update cursor in a larger script to update the value of one field, and if the other field is Null I want to delete the record. The update part works fine, but the delete part does not.  My input data is an annotation feature class created by ArcMap (turn on labels, right-click layer, create annotation). Nothing fancy or complex. The annotation expression is stored in a field named TextString. If no annotation is created for the feature, the field is Null (as a default, all annotation classes created by ArcMap are nullable). When you look at it the attribute table it appears as <Null>.  I cannot use a where clause in this case because of the first update. The following example should work as far as I can tell, but doesn't.  with arcpy.da.UpdateCursor (in_table="RoadsAnno", field_names=["Status","TextString"]) as cursor: for row in cursor: row[0] = 0 cursor.updateRow(row) if row[1] is None: cursor.deleteRow() del cursor, row‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ (I also tried replacing "if row[1] is None:" with "if row[1] == None:" but no joy.  "is None:" is the most proper way to write this according to my Python resources, though "==  None:" still works (in other situations) So I then tried the following: with arcpy.da.UpdateCursor (in_table="RoadsAnno", field_names=["Status","TextString"]) as cursor: for row in cursor: row[0] = 0 cursor.updateRow(row) if row[1] is None or row[1] =="" or row[1] == "<Null>": cursor.deleteRow()‍‍‍‍‍‍ del cursor, row‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I figured one of those statements would catch the Null value, but it did not. I then changed the value of a previously Null row in the RoadsAnno feature class to read "DeleteMe" (not in quotes) and ran the following just to test if the cursor was picking up the right field: with arcpy.da.UpdateCursor (in_table="RoadsAnno", field_names=["Status","TextString"]) as cursor: for row in cursor: row[0] = 0 cursor.updateRow(row) if row[1] is None or row[1] =="DeleteMe" or row[1] == "<Null>": cursor.deleteRow()‍‍‍‍‍‍ del cursor, row‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The row containing the TextString attribute "DeleteMe" was deleted. So what's happening with the Null value? Would anyone be able to help with this? Why doesn't the cursor recognize the Null value in the field?  Maybe Arc creates Null values with unseen characters or something that need to be stripped?   EDIT:  Do I have to put the updateRow statement after the deleteRow statement?  Maybe the cursor is moving to the next row with the update and never gets the chance to delete?  Although that wasn't the case for the "DeleteMe" example so perhaps this line of thought is not correct. ... View more

I have some simple ArcPy script tool validator code that is giving me grief. I am using desktop at 10.3.1. I'm open to whatever help can be offered to get this to work as intended. I have two parameters for my script tool. The first is the type of product to be created, the second is the scale of the product. Digital Map / No scale required are the default values defined in the Tool Validator code. If it is a paper product, the user selects the appropriate scale from the drop-down list. The problem I can't solve is that if the user changes the value in parameter 0 to paper map, the list of scales becomes available but the value is still the default ("No scale required") so an error is thrown because that option is not in the scale list. The error clears when I select the scale from the list, but I want only those choices available and obviously don't want the error to appear at all. Likewise if I then change parameter 0 back to Digital Map the "No scale required" value appears but the error message is thrown again because that value is not in the scale list, which is somehow still appearing. There is no way to clear the error at this point. I'd really appreciate help with how to get these different combinations to appear and change as intended without any errors. If they pick Paper, only the scales appear. If they switch back to Digital, only the "No scale required" value appears. And so on. I can't guarantee the user's behaviour so I'd like for it to be bulletproof. import arcpy class ToolValidator(object): def __init__(self): self.params = arcpy.GetParameterInfo() def initializeParameters(self): # Define the list of product types the user can choose from self.params[0].filter.list = ["Digital Map", "Paper Map"] self.params[0].value = "Digital Map" return def updateParameters(self): if self.params[0].value == "Digital Map": self.params[1].value = "No scale required" if self.params[0].value == "Paper Map": self.params[1].filter.list = ["1:10,000", "1:25,000"] return def updateMessages(self): return‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more