We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment we calculate geometries based on relevant distance. possibly we could just use a snap-function; and use the predictor/evaluator to search for stable resulting geometries? https://shapely.readthedocs.io/en/2.0.3/reference/shapely.snap.html#shapely.snap
This snapping-function gives sometimes unexprected results, so maybe a geometry_util could be added to provide an expected snapping function?
The text was updated successfully, but these errors were encountered:
https://gis.stackexchange.com/questions/203058/why-is-shapelys-snapping-geo-snaps-not-working-as-expected
maybe possibility to write a new snap function based on nearest_points (see link)
Sorry, something went wrong.
https://gis.stackexchange.com/questions/245064/snapping-multiple-nodes-of-a-polygon-to-the-nodes-of-a-line
dieuska
No branches or pull requests
At the moment we calculate geometries based on relevant distance. possibly we could just use a snap-function; and use the predictor/evaluator to search for stable resulting geometries? https://shapely.readthedocs.io/en/2.0.3/reference/shapely.snap.html#shapely.snap
This snapping-function gives sometimes unexprected results, so maybe a geometry_util could be added to provide an expected snapping function?
The text was updated successfully, but these errors were encountered: