XYZ / Ruby Script / Struggling with Scaling

Dear all

I do have an xyz file of a rectangle:
2’713’039 / 1’258’209 lower left
2’713’237 / 1’258’357 upper right

And I do have a ruby script from JimHami (thanks!) which to my understanding does the following: It takes xyz file nr. 1, then file nr. 2 and if it is the same x/y with different z it takes the middle of it. This is for the case I need to read in two files. Now I only have 1 file, so I read in twice the same, z-diffs all zero, done.

I believe I input everything correctly (skip first, indicate X / Y min max as well as delta) and can see that the ruby console is working (window / ruby console) - however there is no model resulting OR I can not see it.

I believe it has to do with scaling - anyone an idea how to make this work and get the a nice terrain model out of this?

Thanks, Thomas

swissALTI3D_.txt (218.9 KB)

thomas_merge.rb (5.7 KB)

Not bothering to change the default XY mins and maxs caused an endless loop situation but, after entering the right ones, no problem.


Merge.skp (2.3 MB)

sdmitch - thanks - I am able to exactly reperform. I am pretty convinced it has to do with the model being 2’713’039 / 1’258’209 off the origin. How do “scroll” exactly 2’713’039 to the right (X) and 1’258’209 in Y-direction?

Moving the object then to the origin I believe I know how to - so I think my problem is as simple as FINDING the object that is correctly created.

sdmitch - when you have run the script - what have been the exact steps that you found your model. Did you perform specific scaling procedures?

I didn’t do anything other that click on Zoom Extents to locate surface which is obviously a long way from the model origin.

Modeling geometry at tiny sizes, or overly large sizes, OR things that are far far from the origin is known to cause issues.
The ‘clipping-plane’ being paramount !

After you add the mesh [group?] why not just move it back to the model’s origin ?
You can easily determine the mesh’s minimum XYZ value and then do a translation from that to the ORIGIN on the collection of geometry forming the mesh.
Then the mesh will be logically located and cause fewer issues…

Yes, I know this and will do this. As I know the exact coordinates of lower left this should not be difficult. Waiting as I want to import another dataset that I am waiting for / did not yet achieve to import. Thanks for remark.

Sdmitch - You have been absolutely right. Found the time to reperform again an build a terrain on the same data - all perfect. Zoom Extents brings the model to the screen as the model is far from the origin. Thanks again, Thomas

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.