Latest Contributions by JustinWolff

Okay, I did recognize that i can't use the same cursor, so starting a new cursor ('cursor1') within the exception is now only populating the errors table with actual error records, but there are multiple entries for each error.   import arcpy from arcpy import env import os import usaddress from collections import OrderedDict arcpy.env.overwriteOutput = True # Get input table table = arcpy.GetParameterAsText(0) # Get the field containing the single-line addresses infield = arcpy.GetParameterAsText(1) # Get the output table for errors outErrors = arcpy.GetParameterAsText(2) # List of fields fields = ["addr", "addrNum", "stNm", "zip", "OID@"] with arcpy.da.UpdateCursor(table, fields) as cursor:      for addr, addrNum, stNm, zip, oid in cursor:           try:                parse = usaddress.tag(addr)[0]                addrNum = parse.get("AddressNumber", "")                stNm = parse.get("StreetName", "")                zip = parse.get("ZipCode", "")                cursor.updateRow([addr, addrNum, stNm, zip, oid])           except Exception:                cursor1 = arcpy.da.InsertCursor(outErrors, fields)                for row in (str(oid)):                     cursor1.insertRow([addr, addrNum, stNm, zip, oid])                                     arcpy.AddMessage("Error with record: {}".format(oid))                arcpy.AddMessage("Bad Input Address = : {}".format(addr))‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Need to figure out why it's giving multiple returns now... Justin ... View more

I spent most of the day on this and didn't get too far, but I have something.  I wasn't able to write to a table in the same .gdb as the source address table, but I am writing to a table in a different .gdb.  This isn't a huge deal.  However, using the code below, as soon as the first exception is found, it stops parsing the addresses and populating fields in the source table ('addresses2'), and then populates all remaining records in the errors table ('errors').  So once it finds an exception it doesn't go back to the try. import arcpy from arcpy import env import os import usaddress from collections import OrderedDict arcpy.env.overwriteOutput = True # Get input table table = arcpy.GetParameterAsText(0) # Get the field containing the single-line addresses infield = arcpy.GetParameterAsText(1) # Get the output table for errors outErrors = arcpy.GetParameterAsText(2) # List of fields fields = ["addr", "addrNum", "stNm", "zip", "OID@"] with arcpy.da.UpdateCursor(table, fields) as cursor:      for addr, addrNum, stNm, zip, oid in cursor:           try:                parse = usaddress.tag(addr)[0]                addrNum = parse.get("AddressNumber", "")                stNm = parse.get("StreetName", "")                zip = parse.get("ZipCode", "")                cursor.updateRow([addr, addrNum, stNm, zip, oid])           except Exception:                cursor = arcpy.da.InsertCursor(outErrors, fields)                for row in (str(oid)):                     cursor.insertRow([addr, addrNum, stNm, zip, oid])                                     arcpy.AddMessage("Error with record: {}".format(oid))                arcpy.AddMessage("Bad Input Address = : {}".format(addr))‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Below you can see how record 310 in the addresses2 table is the first exception, which is written to the errors table, but all subsequent records are written as exceptions as well. I feel I'm close, I'm just not sure where to go from here. Thanks Justin ... View more

Joe - Yes, addresses are always funny.  Fortunately the data in question for this client seems decent.  The various needs around our organization keep things interesting; some need to see dots on the map, while others don't care about the location, they just need a clean mailing address. Thanks Justin ... View more

Thanks Josh - that makes sense and works to return the Object ID of the records in question, which is a great start. I'm now going to turn my attention to working on getting those records out into another table. Thanks again Justin ... View more

Yes, the data owner may eventually use some methods like you've suggested for scrubbing their data, but for now our initial task is to help them identify which records (and how many) have issues. Thanks ... View more

I thought I needed the 'continue' in there or it would 'stop' at the first error, but I now realize that's the point of try/except. There is currently no errors generated, it simply returns a text message of "Error" if an address record isn't parsed.  I'd like to get an output of the actual record that cannot be parsed by usaddress.tag. So with that 'continue' removed I now have the following: import arcpy from arcpy import env import os import usaddress from collections import OrderedDict # Get input table through parameter table = arcpy.GetParameterAsText(0) # Get the field containing the single-line addresses through parameter infield = arcpy.GetParameterAsText(1) # List of fields to be updated fields = ["addr", "addrNum", "stNm", "zip"] with arcpy.da.UpdateCursor(table, fields) as cursor:      for addr, addrNum, stNm, zip in cursor:           try:                parse = usaddress.tag(addr)[0]                addrNum = parse.get("AddressNumber", "")                stNm = parse.get("StreetName", "")                zip = parse.get("ZipCode", "")                cursor.updateRow([addr, addrNum, stNm, zip])           except Exception:                arcpy.AddMessage("Error")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Which returns a message of "Error" for each of the two incorrect address records: ... View more

This user is running ArcGIS Desktop v10.4.1, and the upgrade status of one of our .sde connections says "This 10.2.2 Geodatabase matches the ArcGIS release you are currently using, however, database internals such as stored procedures can be upgraded." ... View more

Yes, this user has multiple SDE connections and has been in/out of editing sessions testing multiple processes. ... View more

Thanks Jayanta.  I was approaching this wrong.  I was able to use dissolve and a join to get what I needed. ... View more

Thanks Joe.  I've wanted to avoid adding a new field, and just use the selected, duplicates in a geoprocessing action.  But, a new field may be what it takes. ... View more

Yes, thanks - i meant to put this in Python, not the API ... View more