This would be of great benefit to the team that I work in as most of the datasets that we use are in 3D. One of our common tasks is to ensure our 3D lines are snapped but currently the method that we are using is long-winded and cumbersome and involves the following steps:
-breaking the lines down into their vertices
-extracting the XYZ values of the start/end vertices
-comparing the XYZ values of the start/end vertices of lines that are supposed to be joined together
-creating new vertices if the XYZ values differ
-joining the vertices up again to recreate the lines
A 3DSnapper and 3DAnchoredSnapper would allow us to do this in a much simpler and more efficient way.
This would significantly benefit organisations that use 3D network data especially in the transport and utilities sectors. In particular, large infrastructure projects in the UK, such as Crossrail and High Speed 2, would benefit from having a 3D Snapper and 3D Anchored Snapper.
Snapper and AnchoredSnapper in 3D would be very helpful for the work I do. Also more clarity in the documentation for all spatial transformers as to weather they work in 3D.
We’re looking for your input as we begin adding 3D support to the Snapper and AnchoredSnapper transformers!
From initial comments in this thread, we understand that 3D support primarily means including Z values alongside XY when snapping. But we want to make sure we fully understand how you expect this to work in practice.
💬 We’d love to hear from you:
What geometry types would you like to snap in 3D? (curves, areas, solids, etc)
What coordinate system would your data be using?
Are there any specific behaviours you expect 3D snapping to support — or avoid?
If you can share your use cases with a sample workflow or data — either in a comment below or via direct message — that would be incredibly helpful as we shape this project.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.