Skip to content
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

[Core] Define projection geometry threshold #7364

Closed
wants to merge 9 commits into from

Conversation

loumalouomega
Copy link
Member

Description
Fixes #7337. This PR adds to the IsInside method a projection threshold. In order to not consider projection at all must be defined as 0.0. Is defined 0.0 by default except for the geometries already considering projection, in order to not break current tests/implementations.

Changelog

  • Added ProjectionThreshold to IsInside method in geometries

@loumalouomega
Copy link
Member Author

@philbucher Mapping app is failing, I don't understand as I keep the current tolerances in order to not break code.

@loumalouomega
Copy link
Member Author

@philbucher Mapping app is failing, I don't understand as I keep the current tolerances in order to not break code.

Ping @philbucher

@philbucher
Copy link
Member

Aside from the failing tests I have some serious concerns both regarding the code design as well as the performance
I will post them in the next days after doing some further investigations

@adityaghantasala
Copy link
Member

@loumalouomega as @RiccardoRossi suggesed in the other thread, may be use can make a different function the bin_based_fast_point_locator to use the project functions and not IsInside function ?

@philbucher
Copy link
Member

see #7401

@loumalouomega loumalouomega deleted the core/projection-geometry-threshold branch September 1, 2020 10:00
@loumalouomega
Copy link
Member Author

Closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BinBasedFastPointLocator problems and improvements
3 participants