points module and huge coordinates ... problems

[DeepSOIC]

How would you guys cut the first five diggits from the x and y numbers before open the file in FreeCAD points?

It depends. I would probably load the file into a spreadsheet program (excel for example) and subtract something.

In text editor, find-replace can at least cut quite a few digits off.

edit: if th4e file structure is easy, maybe you can parse it with python or numpy, and do the subtraction there.

[wmayer]

You can try this:

Code: Select all

import Points

p=Points.Points()
p.read("problem.asc")
c=p.BoundBox.Center

n=Points.Points()
pts=[i-c for i in p.Points]
n.addPoints(pts)
Points.show(n)

[bernd]

libre office calc is what I have been playing already, but I do not like it because I will have this problem again and again ...

great, thanks guys for all the ideas. I will dig into it once and come back.

bernd

[bernd]

werner, your code works great. Does it mean the problem is in coin, and the read does not make use of coin thus import and move works with huge coordinates too!

[wmayer]

werner, your code works great. Does it mean the problem is in coin, and the read does not make use of coin thus import and move works with huge coordinates too!

Yes the problem is in Coin (or maybe even in OpenGL) because when interacting with the 3d view internally a lot of matrix multiplications are performed and as pointed out by DeepSOIC due to the huge rounding errors the rendered scene starts to jump.

So, the trick is to move the points to get some sensible coordinates.

[bernd]

Would the following be possibe?
- if one opens a pcl with huge coordinates FreeCAD warns the user and asks him if he would like to move the pcl to the coordinate orgin or by a user given vector.
- if yes, I would make an issue as Feature request on mantis and link to this topic.

bernd

[wmayer]

Yes.

[bernd]

issue #3606

[Kunda1]

Issue migrated to Github in issue #5808