-
Notifications
You must be signed in to change notification settings - Fork 22
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
Tagging error with triangles? #43
Comments
Show me the input please, here I can't understand what the problem is. |
And here is the complete data set I used: |
First, your data are probably not what should be used as input in pprepair. There are many disconnected parts, and here I am not sure what I as a human would do to "repair" this dataset. What do you want to obtain in the case above where you have roads/canals (I guess...)? Second, what happens in your first image above is that the empty part gets the value of the triangle in red, because in theory any of the adjacent polygon to a problematic polygon can be used to fix the problematic area. But this is my guess, since I am not sure if I know the meaning of the 2 colours in your image. In brief: I'd first consider if pprepair can fix your problem here. It seems to me that snapping would perhaps be more appropriate for many of the errors that you have. pprepair was created to solve a very specific problem: fix a planar partition, not any GIS datasets. Hope this helps. |
|
|
The polygons with only 3 edges are not tagged properly. Or is it on purpose? I think it is not because these polygons are not reconstructed at the end of the process.
![pprepaire_issue1](https://cloud.githubusercontent.com/assets/11536226/15774511/0b8ea96a-297d-11e6-9fec-b98e05899880.png)
![pprepaire_issue1b](https://cloud.githubusercontent.com/assets/11536226/15774525/1bd7d472-297d-11e6-8153-aee69c4c8123.png)
When I add a new edge to these polygons, it is tagged properly.
After adding an edge:
For now I did this as a temporary workaround and I get the result I want but it is quite suboptimal :)
Regards
The text was updated successfully, but these errors were encountered: