Closed kristofdegrave closed 2 years ago
@airbreather @FObermaier This is a blocking issue for us to use this solution. Is it possible to review my possible solution and provide some feedback on it?
Thanks in advance!
May I ask what your GeometryValidator
does?
It provides a custom implementation for validating the geometry.
GeometryValidator is a callback that gets the geometry and returns if it is valid or not. The result of this function call is stored inside the cached IsValid flag of the SqlGeometry in the database.
This provides for us the developers some more flexibility and allows a custom IsValid functionality for SQL Server, without having to impact the NTS Geometry IsValid Implementation.
I assumed that, but it can't be open-sourced to be usable for others?
I was planning to use your implementation for now, with the SelfTouchingRingFormingHoleValid flag on. This would help us already, and we would be able to investigate further to fine tune the IsValid implementation for SQL Server.
And if we can fine tune it more, we will push the issues and possible solutions back to the community.
That sounds like a plan 👍
So can this get approved then?
Not especially waiting for you, more waiting on the nuget package :)
Thanks!
@FObermaier @airbreather When can this feature get released in a stable nuget package?
@FObermaier @airbreather You have any idea when this can get into a nuget package? We have a production release waiting on this. Thanks!
This allows to override the default IsValid of the NTS Geometry and provide an own strategy. This way you can use the IsValidOp with the option SelfTouchingRingFormingHoleValid flagged. Or just make them all valid following the JTS way. Either way the developer will have more control, and if we would manage to provide a IsValidSqlServerOp, it could be passed this way.