paleolimbot commented on issue #1173: URL: https://github.com/apache/sedona-db/issues/1173#issuecomment-5311163401
> Also, once we collected it as a data frame, we cannot convert it to sf by `sf::st_as_sf()` This is something has always bothered me about sf...there are a lot of good (and considerably faster) ways to materialize a geometry column (wk, geos, sf, s2, geoarrow) and `st_as_sf.data.frame()` recognizes none of them. Of course, the tooling around the others (e.g., for ggplot2) isn't there. My two other gripes with sf is that there's no way to represent geography and the geometry semantics with lon/lat are different (unless sf_use_s2 is false)...also the sticky geometry column makes transformations unpredictable if you're writing generic code against its result. How about a `geometry_ptype` and `geography_ptype` argument for collect that can be set with `options()`? If the option is popular enough we can change the default. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
