Latest Contributions by RichardFairhurst

The expression looks correct, but it will only affect a record with the exact value of "011/12/2014".  I would instead select all records that have the leading zero you don't want and then remove it using the Right() method. For a File Geodatabase feature class the SQL expression for a Select By Attribute query to select records with an extra leading zero in the month should be: DATE_TEXT Like '0__/%' Assuming that selects all records with an extra zero, use this VB Script expression to calculate the field to remove the first character in the string: Right([DATE_TEXT], len([DATE_TEXT) - 1)) ... View more

Change the Spatial Reference to the RI State Plane NAD 1983 projection that your x/y coordinates are based on, since your x/y make no sense in any other projection.  You would have to use lat/long coordinates if you use the GCS_WGS_1984 Spatial Reference. Also set the ID field parameter to your Name field so that each line is assigned the boat being observed. ... View more

The answer is ultimately that this is not something that can be controlled through either labeling engine and there will always be offending labels to any labeling strategy you want using automated labeling.  You have to get as close to what you want and then convert to annotation if your client demands labeling to show the ends of roads and start at a specific road end. The Regular Placement Option gives you the ability to play with the most combinations of parameters.  That option does expose a Label Offset option to control which line end the label starts at, but this option requires every line to be oriented exactly to fit your labeling strategy (i.,e. all north/south lines must start at the south and end at the north or vice versa).  You should combine that with a reduction of units allowed for the Overrun Feature option.  Even if every line in your network is perfectly oriented to fit your ideal labeling strategy the results will have odd placements in numerous areas of your map. ... View more

Yes, lists are the key to what you want to do.  that is why the arcpy.ListFields function returns a list of field objects (not just field names).  With two of these lists from different databases you can create a looping structure that is nearly identical to the code I provided to relate the two lists and perform updates.  The list of field objects can easily be converted to the list of field names used by the cursors. So here is some code that should work for relating two field lists for two different data sources using the ListFields function.  Since the field lists for both the update cursor and insert cursor match you can use the same row object for the updateRow and InsertRow methods: import arcpy     from datetime import datetime as d     startTime = d.now()          #set to folder where features are located     arcpy.env.workspace = r"C:\Users\OWNER\Desktop\Test" #on windows use \ instead of /     arcpy.env.overwriteOutput = True     #---------------------------     #define variables for cursor     #---------------------------     FC = "test"     incidentsFC = "CCAP" FCfields = arcpy.ListFields(FC)  incidentsFCfields = arcpy.ListFields(incidentsFC)  # Create a field list of fields you want to manipulate and not just copy  # All of these fields must be in the incidentsFC  manualFields =  ["FacltyType", "StructType", "Verified", "Status", "StructCat", "APA_CODE", "ACCOUNT", 'SiteStreet', 'SHAPE@X', 'SHAPE@Y']  matchedFields = []  for manualField in manualFields:      matchedFields.append(manualField.upper())  for FCfield in FCfields:      for incidentFCfield in incidentsFCfields:          # if FCfield.name.upper() == incidentFCfield.name.upper() and \          # FCfield.type == incidentFCfield.type and \          # incidentFCfield.editable() and \          # not FCfield.name.upper() in matchedFields:          if FCfield.name.upper() == incidentFCfield.name.upper() and FCfield.type == incidentFCfield.type and incidentFCfield.editable == True and not (FCfield.name.upper() in matchedFields):              matchedFields.append(FCfield.name)              break    parcelsCount = int(arcpy.GetCount_management(FC).getOutput(0))     dsc = arcpy.Describe(FC)         rowInserter = arcpy.da.InsertCursor(incidentsFC, matchedFields)           selection_set = dsc.FIDSet       if len(selection_set) == 0:         print "There are no features selected"            elif parcelsCount >= 1:             with arcpy.da.UpdateCursor(FC, matchedFields) as rows:             for row in rows:                 row[0] = ("Single Family Home")                     row[1] = ("Primary, Private")                     row[2] = ("Yes, GRM, TA")                     row[3] = ("Active")                     row[4] = ("Residential")                     row[5] = ("1110")                 rows.updateRow(row)                        rowInserter.insertRow(row)       del row         del rows         del rowInserter    arcpy.RefreshActiveView()                           try:       print '(Elapsed time: ' + str(d.now() - startTime)[:-3] + ')'      except Exception, e:       # If an error occurred, print line number and error message       import traceback, sys       tb = sys.exc_info()[2]       print "Line %i" % tb.tb_lineno       print e.message ... View more