You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating an issue to track that Vector Zonal Stats currently only primarily supports point geometries.
There is a work-around where you simply convert these non-point geometries into points by getting the centroids. From there you can utilize the VZS feature already. But that might cause some imprecision.
A popular dataset example that doesn't come in the form of points is Ookla, where data is in the form of tiles.
Case 1: AOI Tile is smaller than data tile (Ookla)
For example, if your AOI tiles are 1m x 1m, but Ookla tiles are 30m x 30m, and assuming they are aligned (all AOI tiles are within an Ookla tile), then ideally, the average download speed of the Ookla tile should be attributed to all 900 AOI tiles within it. However, if we convert to point geometries, only one of the AOI tiles will intersect with the Ookla tile centroid and get the right attributes; the rest will be null.
Case 2: AOI Tile is bigger than data tile (Ookla)
In the reverse case where the AOI tile is bigger than the Ookla tile (which is likely the majority case), this should be more tolerable because it is likely that each AOI tile will get multiple Ookla tile centroids anyway, leading to a reasonable approximation.
The text was updated successfully, but these errors were encountered:
Creating an issue to track that Vector Zonal Stats currently only primarily supports point geometries.
There is a work-around where you simply convert these non-point geometries into points by getting the centroids. From there you can utilize the VZS feature already. But that might cause some imprecision.
A popular dataset example that doesn't come in the form of points is Ookla, where data is in the form of tiles.
Case 1: AOI Tile is smaller than data tile (Ookla)
For example, if your AOI tiles are 1m x 1m, but Ookla tiles are 30m x 30m, and assuming they are aligned (all AOI tiles are within an Ookla tile), then ideally, the average download speed of the Ookla tile should be attributed to all 900 AOI tiles within it. However, if we convert to point geometries, only one of the AOI tiles will intersect with the Ookla tile centroid and get the right attributes; the rest will be null.
Case 2: AOI Tile is bigger than data tile (Ookla)
In the reverse case where the AOI tile is bigger than the Ookla tile (which is likely the majority case), this should be more tolerable because it is likely that each AOI tile will get multiple Ookla tile centroids anyway, leading to a reasonable approximation.
The text was updated successfully, but these errors were encountered: