Open msalib opened 10 months ago
Ah, but calling densify(30.)
on the inputs prevents the panic. (This is for a zonal summary system where the pixel size is 30, so I don't care about anything less than 30). Does anyone have any guesses as to whether densifying inputs would make intersection reliable?
Hey,
it seems like you also encountered one of the many issues that are still left open with the implementation of BoolOps
in geo
. Please refer to https://github.com/georust/geo/issues/976
Thanks for the example test! 👍
Edit: Oops just noticed you already mentioned that issue. I'd still like to refer to it again for clarity since there are a lot of issues of this kind 😅
Hi, also getting similar errors I believe. Am operating on a large dataset but doesnt always fail in the same place. I get back thread 'main' panicked at 'segment not found in active-vec-set: 8', /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/geo-0.26.0/src/algorithm/sweep/vec_set.rs:22:14
Implemented the failing case as a test in a new implementation here https://github.com/georust/geo/pull/1089/commits/21de0dd42c893a89831e358118c4bcf76815c7de and the test doesn't panic
Like #913 and #976, here's another one: