-
Notifications
You must be signed in to change notification settings - Fork 374
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
Negative buffer with join-style
mitre
#1047
Comments
But with a non-mitre end-cap? (I kind of wonder what a mitre even means in the case of polygon buffer/unbuffer) |
As far as I know an Regarding |
You specified mitre in your description so I wondered if you were seeing it having an effect. I agree, for polygons it should be a no-op. |
The mitre |
join-style
mitre
Interestingly, this issue only happens with |
Or an interaction with some element of the input that is itself has a size of exactly 2? |
Actually, it more complicated. Other combinations trigger the same error, e.g., here's a few others: for distance in np.round(np.linspace(-0.1, -10.1, 101), 1):
for mitre_limit in np.round(np.linspace(0.1, 5.1, 51), 1):
g = shapely.buffer(poly, join_style="mitre", distance=distance, mitre_limit=mitre_limit)
if g.area < 700000.0:
print(f"> {distance=}, {mitre_limit=}, {g.area:.1f}")
|
I did some random tests with some other mitre limits than 2, and also noticed that it is quite specific. The combinations with other distances leading to the issue is an interesting find indeed... |
Probably not super relevant, but something I forgot to mention... the input polygon is the result of a +5 meter buffer on a polygon, with a mitre limit of 1.5... |
Quite a specific case: for a specific polygon, when I apply a negative buffer (distance -5) with join style mitre (mitre distance 2), a large part of the polygon disappears...
In the image below the input polygon is in blue, the result after applying the negative buffer is in red.
Code to reproduce:
The text was updated successfully, but these errors were encountered: