@lassoan could you please explain your comment at bit further:
Or, you can also make the computation fully robust by computing distance map over an image (rasterize the model and compute signed distance on the image)
I’m working with 3D image data objects in vtk, and extracting surfaces from signed distance fields on the vtkImageData from input polydatas using flying edges from vtk. But my signed distance field comes from vtkImplicitPolyDataDistance. I’d like to make more robust my signed distance computation if I can - could you explain your comment above a bit more so I could try to implement it using existing vtk filters? If possible if you can share code that you would use instead of vtkImplicitPolyDataDistance when operating on a vtkImageData, to get the same end result of a signed distance, that would be fantastic.