Latest Contributions by VinceE

Using Join and Field Calculator works, but would be far too tedious and error prone in my opinion, but that might depend on your jurisdiction's parcel dataset complexity. I would use Python and Search/Update Cursors. More flexible long-term, and avoids having to manually use Field Calculator on a ton of fields. Let's assume "ACCOUNT" is the common field name between the Geometry shapefile and the attribute update table. "PARCEL" is the original geometry table, "PARCEL_TBL" is the published CSV of tabular updates, and "PARCEL_COPY" is the updated version. Note that only the intended rows are modified, and any geometry-specific fields can be left alone during the update. This will not ADD new records--you'd have to write that into the code, or first manually draw in the geometry with an ACCOUNT ID into the geometry shapefile. This script reads through the update table and makes updates where appropriate in a COPY of the geometry table. import arcpy # Overwrite the output copy. Set the working folder (table and shapefiles). arcpy.env.overwriteOutput = True arcpy.env.workspace = r"YOUR_DIRECTORY" # Input datasets. polygon = "PARCEL.shp" table = "PARCEL_TBL.csv" # Unique field. For parcels, assuming ACCOUNT ID or similar. account_fld = 'ACCOUNT' # Read relevant fields from each. Ignore various ObjectID/Geometry-type fields. # Also remove the ACCOUNT ID field, will be added back in for Cursors. poly_flds = [f.name for f in arcpy.ListFields(polygon) if f.type not in ['Geometry', 'OID'] and f.name.lower() not in ['shape_area', 'shape_length' 'shape.starea(), shape.stlength()']] tbl_flds = [f.name for f in arcpy.ListFields(table) if f.name != account_fld] # Get fields that are common to both the Geometry and the Update Table. common_flds = list(set(poly_flds) & set(tbl_flds)) # Read the update table. Use the ACCOUNT ID as a dictionary key. with arcpy.da.SearchCursor(table, [account_fld] + common_flds) as scurs: fc_dict = {row[0]:row[1:] for row in scurs} # Make a copy of the original Geometry shapefile. # This could be modified so that the existing is archived as a backup, and then # the current is updated. poly_copy = f"{polygon.split('.')[0]}_COPY.shp" # If the Account in the Geom shapefile requires updates (based on ACCOUNT ID), # update the row. arcpy.management.CopyFeatures(polygon, poly_copy) with arcpy.da.UpdateCursor(poly_copy, [account_fld] + common_flds) as ucurs: for acct, *row in ucurs: if acct in fc_dict.keys(): print(f"OLD ROW: {[acct, *row]}") ucurs.updateRow([acct, *fc_dict[acct]]) print(f"UPD ROW: {[acct, *fc_dict[acct]]}\n")   ... View more

See another version below. This one will save your points too. It also creates your sampling boxes. There are four different methods you can use (see the "box_rotation" variable in the INPUTS section). Remember to update all the "INPUTS" based on your needs. Should be able to paste the code into the Python window again. Only one version of the transect lines are shown (lines for the 'ANGLE_DIAMOND'-style boxes), but you can see all four styles of the sampling boxes. Some different sizes and distances from the origin points are also shown.   #-----------------------------------------------------------------------------# # IMPORTS import math import os import random import sys from typing import Literal, Union import arcpy #-----------------------------------------------------------------------------# # INPUTS # Full path to the geodatabase where the sampling points are, and where outputs will go. workspace = r"C:TEMP\Random_Sample_Lines.gdb" # Name of the point feature class in the above geodatabase that houses the # sampling points. in_pnt_fc = "_SAMPLE_POINT" # Distance between sampling points (along x and y, not diagonals). # Units match coordinate system. point_spacing = 400 # feet, in my case box_width = 50 box_rotation = 'ANGLE_BOX' # Literal[NORTH_BOX, NORTH_DIAMOND, ANGLE_BOX, ANGLE_DIAMOND] # Name of the output feature class to be created. fc_line = "TRANSECT_LINE" fc_endpoints = "TRANSECT_LINE_ENDPOINTS" # Leave this alone if you are not familiar with the f-string notation. fc_box = f"TRANSECT_{box_rotation}" # -----------------------------------------------------------------------------# # SETTINGS # This just overwrites previous outputs to help with testing. arcpy.env.overwriteOutput = False #-----------------------------------------------------------------------------# # FUNCTIONS def rotate_point(coordinate: tuple[int, int], pivot_point: tuple[int, int], angle: Union[int, float], angle_format: Literal['DEGREES', 'RADIANS']='DEGREES' ) -> tuple[int, int]: """Rotates coordinate values around another point. :coordinate: (x, y) coordinate pair to be rotated :pivot_point: (x, y) coordinate pair around which point will be rotated :angle: angle to rotate the coordinate :angle_format: angle format, RADIANS or DEGREES |(x_prime, y_prime)| rotated point coordinates""" if angle_format == 'DEGREES': angle = math.radians(angle) x, y = coordinate X, Y = pivot_point x_trans = x - X y_trans = y - Y sin = math.sin(angle) cos = math.cos(angle) # Counter-clockwise rotation: x_transprime = cos * x_trans - sin * y_trans y_transprime = sin * x_trans + cos * y_trans x_prime = x_transprime + X y_prime = y_transprime + Y # print(f"XY TRANS: {x_trans:,.0f}, {y_trans:,.0f}\n" # f"XY TRANSPRIME: {x_transprime:,.0f}, {y_transprime:,.0f}\n" # f"XY PRIME: {x_prime:,.0f}, {y_prime:,.0f}\n") return (x_prime, y_prime) def create_box(method: Literal['NORTH_BOX', 'NORTH_DIAMOND', 'ANGLE_BOX', 'ANGLE_DIAMOND'], center_pnt: arcpy.Point, width: Union[int, float], angle: Union[int, float], spat_ref: int) -> arcpy.Polygon: """Create a square box around a given point. Optionally rotate it. :center_pnt: centroid of the square box :width: width of side of box :angle: angle the box should be rotated |box_geom| geometry object representing the box""" angle_dict = {'NORTH_BOX': 45, 'NORTH_DIAMOND': 0, 'ANGLE_BOX': angle + 45, 'ANGLE_DIAMOND': angle} # Distance to move point based on known hypotenuse (1/2 width of box). offset = math.sqrt(2 * ((width / 2) ** 2)) x, y = center_pnt.X, center_pnt.Y Nx, Ny = x, y + offset Ex, Ey = x + offset, y Sx, Sy = x, y - offset Wx, Wy = x - offset, y box_corners = [] for coordinate in [(Nx, Ny), (Ex, Ey), (Sx, Sy), (Wx, Wy), (Nx, Ny)]: box_corners.append(rotate_point(coordinate=coordinate, pivot_point=(x, y), angle=angle_dict[method], angle_format='DEGREES')) pnt_array = arcpy.Array([arcpy.Point(*corner) for corner in box_corners]) box_geom = arcpy.Polygon(pnt_array, spatial_reference=spat_ref) return box_geom #-----------------------------------------------------------------------------# # MAIN in_points = os.path.join(workspace, in_pnt_fc) transect_lines = [] line_enpoint_dict = {} sample_box_dict = {} pnt_desc = arcpy.da.Describe(in_points) pnt_oid_fld = pnt_desc['OIDFieldName'] pnt_spat_ref = pnt_desc['spatialReference'].factoryCode with arcpy.da.SearchCursor(in_points, [pnt_oid_fld, 'SHAPE@XY']) as scurs: for oid, (x, y) in scurs: # Random angle in degrees, 1-360; convert to radians. angle_deg = random.randint(1, 360) angle_rad = math.radians(angle_deg) print(f"POINT {oid}, ANGLE: {angle_deg}") # Get x/y offset of random point on the imaginary circle around each point. start_x = (point_spacing/2) * math.cos(angle_rad) start_y = (point_spacing/2) * math.sin(angle_rad) # Using the sample point coordinate as the starting point, # calculate real-world x and y of both start and end of transect line. start_point = arcpy.Point(x + start_x, y + start_y) end_point = arcpy.Point(x - start_x, y - start_y) # -S/-E suffixes differentiate start/edn boxes. Not currently used, but # documented just in case (also, unique keys are required). sample_box_dict[f'{oid}-S'] = create_box(box_rotation, start_point, box_width, angle_deg, pnt_spat_ref) sample_box_dict[f'{oid}-E'] = create_box(box_rotation, end_point, box_width, angle_deg, pnt_spat_ref) # Create a Polyline Geometry Object. Append dict entry to list. new_line = arcpy.Polyline(arcpy.Array([start_point, end_point])) transect_lines.append({'OID': oid, 'GEOM': new_line, 'ANGLE': angle_deg}) # Save start and end Point Geometry objects to another list. line_enpoint_dict[oid] = (arcpy.PointGeometry(start_point), arcpy.PointGeometry(end_point)) # Create three feature classes. for fc, geom in [(fc_line, 'POLYLINE'), (fc_endpoints, 'POINT'), (fc_box, 'POLYGON')]: arcpy.management.CreateFeatureclass(out_path=workspace, out_name=fc, geometry_type=geom, spatial_reference=pnt_spat_ref) print(f"CREATED FC {fc}") # FC paths. ln_fc = os.path.join(workspace, fc_line) pt_fc = os.path.join(workspace, fc_endpoints) box_fc = os.path.join(workspace, fc_box) # Add fields. for fc in (ln_fc, pt_fc, box_fc): arcpy.management.AddField(fc, 'POINT_OID', 'SHORT') arcpy.management.AddField(ln_fc, 'LINE_ANGLE', 'SHORT') arcpy.management.AddField(pt_fc, 'POINT_TYPE', 'TEXT', field_length=5) print("ALL FIELDS ADDED") # Write transect line features. with arcpy.da.InsertCursor(ln_fc, ['SHAPE@', 'POINT_OID', 'LINE_ANGLE']) as icurs: for feature_dict in transect_lines: icurs.insertRow([feature_dict['GEOM'], feature_dict['OID'], feature_dict['ANGLE']]) print("TRANSECTS WRITTEN") # Write line start and end points. with arcpy.da.InsertCursor(pt_fc, ['SHAPE@', 'POINT_OID', 'POINT_TYPE']) as icurs: for oid, (start_geom, end_geom) in line_enpoint_dict.items(): icurs.insertRow([start_geom, oid, 'START']) icurs.insertRow([end_geom, oid, 'END']) print("ENDPOINTS WRITTEN") # Create Sampling Zones----------------------------------# # Transect Line Oriented with arcpy.da.InsertCursor(box_fc, ['SHAPE@', 'POINT_OID']) as icurs: for oid, geom in sample_box_dict.items(): icurs.insertRow([geom, oid.split('-')[0]]) print("BOXES WRITTEN")   ... View more

Can you expand on what you mean by this, and what you are trying to accomplish? At face value, I'm not sure the request you've been given makes sense. For simplicity, let's say the following are the only two Contingent Value groups allowable for a feature class with four fields: Now let's say I enter in a record for a Crosstrek, Premium, Standard, Red (which is valid). What if I decide I want a CVT, instead of a Standard transmission? There would be no possible way to do that without the partial match option, because selecting CVT is NOT ALLOWABLE with the Premium Trim or the color Red. BUT, the CVT is allowable for the car itself, so it's a "partial match." By selecting CVT, it will either surround the other fields in a red box when they become invalid, or, in this case, default to the ONLY allowable options for the other fields. Basically, I suppose you could eliminate the "partial match" option, but if you got too far into a specific set of values, there would be no way to change anything without erasing the entire record and starting over, because there may ONLY be partial matches available (as in the case above). So, if my understanding of your situation and the way Contingent Values are implemented, it is not possible to do this, and it also would not make sense to simply from a data editing/modifying standpoint. If you want to ensure a specific order of values are entered correctly the first time, and if a user makes a mistake, they have to start the record over entirely, you may need to look into successive Attribute Rule Constraints. ... View more