On 6/19/2021 2:52 PM, Andrew Bell wrote:
The X and Y dimensions are assumed to lie on a
plane. All intersection points are also assumed to lie on the
same plane as the polygon. Z values are assigned after the fact.
On Sat, Jun 19, 2
The polygon of a cutline is reprojected into the coordinate system of
the source image, so densification of its contour might have an effect
indeed.
Le 19/06/2021 à 22:27, Metabase Account a écrit :
I might be thinking of this incorrectly, but if they're done in 2D
without any spatial consider
If I already know the column name, is there a better way to access the value
than what I'm currently doing?
For example, currently in order to get the date value of the last row, I am
looping through all columns and confirming that the column name is what I
expect, then using that index to access
I might be thinking of this incorrectly, but if they're done in 2D without
any spatial consideration, inserting additional vertices in between
shouldn't have an effect on behavior right? However it does seem to have an
effect when using operations such as warp with the polygon as the cutline.
On S
These are done in 2D, without regard to the spatial reference.
On Sat, Jun 19, 2021, 11:31 AM Met Bas wrote:
> From my understanding, a square polygon feature would only consists of the
> 5
> vertices of the corners (with the last vertex being the same as the first
> to
> "close" the polygon).
>
>From my understanding, a square polygon feature would only consists of the 5
vertices of the corners (with the last vertex being the same as the first to
"close" the polygon).
If I do an operation depending on a polygon, for example intersections or
clipping a raster, how is the path between the
