Insert Line

The get cursor is used to create and insert series. Once the cursor needs to be created, the insertRow method is always used to insert into the function (or tuple) values ​​that reach a new row. Any field in a tableAnything that is not in the cursor will almost certainly be assigned the field’s fallback value.

Import Arcpy

# Create an insertion cursor in an array
cursor = arcpy.da.InsertCursor("c:/base/data.gdb/roads_lut",
                               ["Street ID", "Distance"])

# Create 25 new lines. Set start row id and individual values ​​globally
for i in the interval (0.25):
   Cursor .insertRow([i, 100])

UpdateRow

This method is now used to update the string to the full current position of the expansion cursor. After returning the row a during the cursor object, you can expand the row as needed and change the updateRow solution by changing this line.

Import Arcpy

# Create an update cursor with an object class
with arcpy.da.UpdateCursor("c:/base/data.gdb/roads",
                           ["road type", "distance"]) as a slider:
    while line at cursor:
        number Updates the values ​​in the long distance field to
 Multiply the street type number by one hundred. Street type: 1, couple, 3 or 4.
       string[1] equals * string[0] 100
        cursor.updateRow(line)

Ringtone Access And Settings

Each field slider uses numeric farms provided by a directory (or tuple) of field names. When a line is swiped away from the cursor, it is presented as a list of field price ranges corresponding to the index position.

In each example below, the number of names, states, and companies is listed in the available position.

Import Arcpy

fc="c:/base/data.gdb/USA/states"

# Use SearchCursor to access name and count status
with arcpy.da.['STATE_NAME', searchcursor(fc, 'POP2000']) as cursor:
    for string in kursore:
        # Access plus outputs row values ​​by service position.
        # say name: string[0]
        # population: string[1]
       print(' has almost all populations of '.Row[1]))

Tokens can now also be used as shortcuts for placing field names. All tables contain an ID segment, which can be multiple depending on the type of data. Simple force classes require a geometry field, usually (but always) without the Shape name. The OID@ token can be used to successfully access a feature ID field because the SHAPE@ token (returning a new geometry object) can be used to access the geometry of an absolute feature class field without first knowing the field names.