Timeline for sf::st_read() and terra::vect() reading in different extents from the same shapefile
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2022 at 3:58 | comment | added | Robert Hijmans |
What terra did was clearly wrong, IMO. A geometry that is not, does not have an extent.
|
|
| Apr 15, 2022 at 15:41 | comment | added | Spacedman | @JeffreyEvans maybe discuss on r-sig-geo mailing list first? Might get a consensus between sf, terra, and other package authors first. I'll kick it off... | |
| Apr 15, 2022 at 15:25 | vote | accept | Vijay Ramesh | ||
| Apr 15, 2022 at 15:25 | comment | added | Vijay Ramesh | @JeffreyEvans Please go ahead and raise an issue, if you wouldn't mind! | |
| Apr 15, 2022 at 14:39 | comment | added | Jeffrey Evans | Are you planning on pointing this out to the terra or sf developers? This seems like behavior that should follow an excepted standard, on how null geometry is handled when defining that extent and throw a warning about null geometry being present. If you do not want to deal with it, I would be happy to like this post and point out the discrepancy in behavior. Personally, I would prefer to not have a null geometry influence the extent. | |
| Apr 15, 2022 at 14:01 | history | answered | Spacedman | CC BY-SA 4.0 |