aw_area assumes geometry column is named "geometry"

[dblodgett-usgs]

See here: https://github.com/slu-openGIS/areal/blob/master/R/aw_intersect.R#L103

The use of quosures is beyond my tidyverse skill or I'd PR a fix. You need to use sf::st_geometry() to operate on the geometry list column directly or lookup the name with attr(x, "sf_column").

b1 <- sf::st_polygon(list(rbind(c(-1, -1), c(1, -1),
                                c(1, 1), c(-1, 1),
                                c(-1, -1))))
b2 <- b1 + 2
b3 <- b1 + c(-0.2, 2)
b4 <- b1 + c(2.2, 0)
b <- sf::st_sfc(b1, b2, b3, b4)
a1 <- b1 * 0.8
a2 <- a1 + c(1, 2)
a3 <- a1 + c(-1, 2)
a <- sf::st_sfc(a1, a2, a3)

sf::st_crs(b) <- sf::st_crs(a) <- sf::st_crs(5070)

b <- sf::st_sf(geom = b, data.frame(idb = c(1, 2, 3, 4)))
a <- sf::st_sf(geom = a, data.frame(ida = c(1, 2, 3)))

sf::st_agr(a) <- sf::st_agr(b) <- "constant"

aw_intersect(a, b, "area")

attr(a, "sf_column") <- "geometry"
attr(b, "sf_column") <- "geometry"

names(a) <- c("ida", "geometry")
names(b) <- c("idb", "geometry")

aw_intersect(a, b, "area")

[dblodgett-usgs]

Side note, now that I have this handled over in intersectr I've found that areal works great and I use it directly as of: https://github.com/dblodgett-usgs/intersectr/pull/2.

I implemented a little cross-validation with an old java-based system that we use a lot. See the bottom here: https://dblodgett-usgs.github.io/intersectr/dev/articles/prism_demo.html for records of that cross validation.

[chris-prener]

This works great - I'm going to fix the "geometry" column bug next week - an oversight that just didn't occur to me since our columns are always named "geometery"!

Thanks for keeping me in the loop with this @dblodgett-usgs.

[chris-prener]

This is now fixed - thanks @dblodgett-usgs!