-
Notifications
You must be signed in to change notification settings - Fork 3
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
constantDensitySampling gives wrong output with MULTIPOLYGONS #26
Comments
To me this looks like the shapefile contains one or more multipart features -- so the
The spurious samples are a degenerate case of As far as a clean way to do this with |
constantDensitySampling
gives wrong output with MULTIPOLYGONS
constantDensitySampling
gives wrong output with MULTIPOLYGONS
I'll add that this seems to work as intended on |
Long-term lets move this over to |
Here is a slightly more obvious depiction of what is going on with MULTIPOLYGON feature input to
|
I had made a nasty mistake:
versus
I was inadvertently duping the geometry -- creating overlapping features that got sampled "correctly". It does seem that depending on the way the multipolygons were generated, the constantDensitySampling results could vary. |
Thanks for testing this. I'll likely return to this after closing some aqp issues. |
1 similar comment
Thanks for testing this. I'll likely return to this after closing some aqp issues. |
constantDensitySampling()
was designed to work withsp
class objects which don't differentiate between POLYGON and MULTIPOLYGON types. Exploding the MULTIPOLYGONS into POLYGONS viasf
is a simple work-around. Long-term, a more robust solution is required, likely switching tosf
-class objects / methods.Not really repeatable, but the basic idea.
The text was updated successfully, but these errors were encountered: