-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upcoming sf version will break MODIS (when using s2 for geometries with ellipsoidal coordinates) #110
Comments
Still the case. Please consider using
You can test with s2 (1.0.5) from CRAN, and sf branch |
FYI, MODIS was been removed from CRAN on June 28, 2021 because of these errors. Users can install an archived version with |
... or use |
Dear Edzer,
Thank you for insisting on this! I have been completely out from working on
the MODIS package since quite a while now. I have tried to logon to my
github but it asks me for a 2f auth which I had to reset now. After getting
back the access I will have a look at this!!
Thanks again
Matteo
Am Mi., 30. Juni 2021 um 18:41 Uhr schrieb Edzer Pebesma <
***@***.***>:
… ... or use sf_use_s2(FALSE).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#110 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4F4GUQBHR7H4Q2UXQT6O3TVNCM3ANCNFSM43DMV6QA>
.
|
Great - let me know when you need help! |
@edzer Thanks for the notification! I haven't been following the discussion in quite a while. From what I understand, would it be enough to examine any incoming geometry with |
So to answer my own question, it seems like this approach is not viable. At least, sf::sf_use_s2(TRUE)
data(meuse, package = "sp")
pts = sf::st_as_sf(meuse, coords = c("x", "y"), crs = 28992)
all(sf::st_is_valid(pts))
# TRUE
MODIS::getTile(pts[1, ]) using valid geometries only leads to the same error: Error: Problem with `filter()` input `..1`.
ℹ Input `..1` is `lengths(.predicate(x, y, ...)) > 0`.
x Evaluation error: Found 4 features with invalid spherical geometry.
[13] Loop 0 is not valid: Edge 1 crosses edge 6
[18] Loop 0 is not valid: Edge 0 crosses edge 5
[446] Loop 0 is not valid: Edge 1 crosses edge 4
[451] Loop 0 is not valid: Edge 2 crosses edge 5. Will start investigating with temporarily setting |
Please see r-spatial/sf#1649 - please consider commenting there if you get stuck! (@paleolimbot: another
✖ Loop 0 is not valid: Edge 1 crosses edge 6
)The text was updated successfully, but these errors were encountered: