nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

automated polygon movement?

leifolson

Hi,

I am trying to write a script that takes a single polygon shapefile ( a facility footprint), a grid of planning units, and a landcover shapefile, and, for each planning unit gridcell, shifts the geographic location of the footprint shapefile, and uses the newly located footprint to erase the underlying landcover. What's the best way to iterate through the cells, and aligns the footprint shapefile with the center of the gridcell? Thanks...

Vind meer berichten getagd met

Accepted answers

All comments

markdenil

a nested list is a list nested within another list
(you can nest dictionarys too, and lists within dictionaries and vice versa..)

In this case, you want a list of verticies for the polygon
and each vertex entry is a list of the x and y coordinates.

line this:

theFeatureList = [
    [59.9359664290001, 58.2873293230001],
    [59.9354474180001, 58.292897049],
    [59.9359664290001, 58.2873293230001],
    [15.7361337040001, 69.5741156380001],
    [5.46961326000007, 74.605524862],
    [21.6743239320001, 90.0000000000001],
    [61.6145099540001, 90.0000000000001],
    [74.588779291, 78.7328713650001],
    [74.9956238680001, 62.052243682],
    [59.9359664290001, 58.2873293230001],
    [29.5877337620001, 75.2087581980001],
    [29.5902670670001, 75.2091884760001],
    [29.5877337620001, 75.2087581980001]
    ]

Then, as you loop through the outer list, it returns a llist of xy pairs you can access by index (0 and 1).

Furthermore, if your grid is regular, you needn't make a list of each new anchor point;
you can just increment the offsets.
offsetX = 0, offsetY = 0
draw the first polygon
offsetX += cellSizeX
draw the second

when you finish that row (by counting the steps)
reset offsetX to 0 and increment offsetY += cellSizeY

T__WayneWhitley

I can see that you are appropriately getting the 1st (and only) part, which is an array (or list?) of point objects....makes sense for single-part features I think. You've set a variable before the loop begins for the 1st part (index 0).

So far so good, you feed adjusted point values based on this into another point array to feed into a new polygon geometry.
Great, but what is the purpose of incrementing your index variable? What other geometry could you be referencing? I think this is at least partly where your mistake is.......every time you fetch a new poly geom with the search, you should only have 1 part, correct? (not considering 'holes' - regardless, the 'single part' should come 1st, if I'm not mistaken)

I agree with the others, better structuring and error trapping would be very useful. Hope this helps.

leifolson

ahh, thanks, hadn't known what the # button did. I've corrected my post above.

What do you mean by a 'nested list'?

markdenil

First off: use the '#' button in the Forum reply formatting bar to wrap your code in code tags

you want:
    this

instead of:
this

I would take the original polygon point array and build a nested list of the x,y pairs from it. (featureList)
Then I would make another nested list of the individual squares' origin points. (originList)

One advantage is that it is easy to inspect these lists if things are not coming out right.

Then the insert cursor just gets created once, and you loop through originList.
for each origin in originList, you draw a feature
(one loop through featureList adding the origin x or y to each coordinate)

Your script seems to have nested or overlapping cursors, and you get each origin
(and each feature point? ...reading unformtted code is confusing at the best of times)
directly from the reference fc. That just seems overly complex.

Eschew Complexity.

leifolson

Ha, now I see it. It's hard to read unformatted.

So, it looks like you initially get an array of x,y values for the first part of the polygon with this:

for pnt in inShape.getPart(polyIndex):

Now you need to pull the the individual points from the array that is the first part of the first polygon record in your feature class. Think of multipart features.

yeah, the posting software seems to be dropping the tabs from the code, my apologies.

But the feature im copying is not multipart...

ClayPerry

Ha, now I see it. It's hard to read unformatted.

So, it looks like you initially get an array of x,y values for the first part of the polygon with this:

for pnt in inShape.getPart(polyIndex):

Now you need to pull the the individual points from the array that is the first part of the first polygon record in your feature class. Think of multipart features.

leifolson

I don't see where 'pnt' is defined, so it can't have an attribute 'X'.

its defined in the for loop

for pnt in inShape.getPart(polyIndex):

and i should note that if i add a try: except: routine, some polygons will be written, but not all.

ClayPerry

I don't see where 'pnt' is defined, so it can't have an attribute 'X'.

leifolson

So, i feel like i'm almost there, but im getting this error

Traceback (most recent call last):
** IDLE Internal Exception:
File "C:\Python27\ArcGISx6410.1\lib\idlelib\run.py", line 298, in runcode
exec code in self.locals
File "N:\Projects\120802 CEMA Landscape Simulation Modelling for RMWB\07- Working Products and Drafts\code\trial_run.py", line 51, in <module>
pntObj.X = pnt.X + xoffset
AttributeError: 'NoneType' object has no attribute 'X'

using the following script...
can anyone offer any insight? Thanks!

import arcpy, os

dist = r"N:\Projects\120802 CEMA Landscape Simulation Modelling for RMWB\05- Data\glink_seismic_Buffer_ClipExample.shp"
origin = r"N:\Projects\120802 CEMA Landscape Simulation Modelling for RMWB\05- Data\section_for_clipping_disturbance_features.shp"
sqrs = r"N:\Projects\120802 CEMA Landscape Simulation Modelling for RMWB\05- Data\sections_analysis.shp"
outfolder = r"N:\Projects\120802 CEMA Landscape Simulation Modelling for RMWB\05- Data"
outpoly = r"seismic_tile_example.shp"

try:
    arcpy.Delete_management(outfolder + "/" + outpoly)
except:
    pass

arcpy.CreateFeatureclass_management(outfolder, outpoly, "POLYGON", "", "", "", dist)
distdesc = arcpy.Describe(dist)
distshapefieldname = distdesc.ShapeFieldName
squaredesc = arcpy.Describe(sqrs)
squareshapefieldname = squaredesc.ShapeFieldName

originpoly = arcpy.SearchCursor(origin)
squares = arcpy.SearchCursor(sqrs)
inRows = arcpy.SearchCursor(dist)
outRows = arcpy.InsertCursor(outfolder + "/" + outpoly)

polyarray = arcpy.Array()


origindesc = arcpy.Describe(origin)
originshapefieldname = origindesc.ShapeFieldName
orig = originpoly.next()
originvalue = orig.getValue(originshapefieldname)
origincentroid = originvalue.centroid


for square in squares:

    squarevalue = square.getValue(squareshapefieldname)
    squarecentroid = squarevalue.centroid
    xoffset = squarecentroid.X - origincentroid.X
    yoffset = squarecentroid.Y - origincentroid.Y

    polyIndex = 0
    for inRow in inRows:
        inShape = inRow.shape
        pntObj = arcpy.Point()
        arrayObj = arcpy.Array()
        for pnt in inShape.getPart(polyIndex):
            pntObj.ID = polyIndex
            pntObj.X = pnt.X + xoffset
            pntObj.Y = pnt.Y + yoffset
            arrayObj.add(pntObj)
        outShape = outRows.newRow()
        outShape.shape = arrayObj
        outRows.insertRow(outShape)
        polyIndex += 1

leifolson

thanks, that sounds like it will do the trick, much obliged!

markdenil

Collect the x and y locations of each polygon vertex, in order, as offsets from the lower left corner of the planning unit cell.
Also collect the lower left corner locations for each cell.

Use an Insert Cursor to draw new polygons, vertex by vertex.
For each polygon, use the lower left corner of each cell as the base point, and add the offsets to that for each vertex.

This will give a feature class with all the polygons you want: same shape, different location,
each located relative to the cell in which it lands.

Then do just one erase on the landcover.

This is likely easier than hopping the same polygon around and erasing each time.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.