-
Notifications
You must be signed in to change notification settings - Fork 448
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
VariableBuffer result polygon has incorrect hole #998
Comments
The example geometry as WKT:
|
@Alison-97 hopefully the fix in #1014 solves your issue. Can I ask what you are using VariableBuffer for? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I am encountering an issue with the Variable Buffer class. Specifically, I am working with an open LineString. Given that the LineString is open and does not intersect itself, the buffer operation should yield a simple polygon without any interior rings (holes). However, in the current implementation, the resulting polygon contains an unnecessary interior ring. This is causing a disruption in the order of the resulting polygon coordinates.
Steps to Reproduce
Here's the .Net code to reproduce the issue:
This is a plot of the inner line coordinates.
![image](https://private-user-images.githubusercontent.com/97237245/260374376-8e03f5d1-3052-48f2-91ea-9ec544f951db.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxODU1NzUsIm5iZiI6MTczOTE4NTI3NSwicGF0aCI6Ii85NzIzNzI0NS8yNjAzNzQzNzYtOGUwM2Y1ZDEtMzA1Mi00OGYyLTkxZWEtOWVjNTQ0Zjk1MWRiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDExMDExNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNlMWYyOTRiMzI1MWJjODZiODZlNTZlNzcwNWI0ODBhZjc2ZjI0ZjQyZmFiZmUyY2QyNDA0MjVmNTQ4OTYyMmEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.n5YJlSj2Xknsw5YyVXQ3vDg_uwe43stp2pKrZcuwCm4)
The text was updated successfully, but these errors were encountered: