Help with site model urgent for deadline

[Nicola Bird]

Hi All, 

I need emergency assistance. I have a deadline for Monday and I've added incorrect data in my site model. I usually build interior models and have limited experience with site models. I’ve spent a few hrs in putting all the site data, but I accidentally entered the measurements incorrectly. Instead of using millimetres (e.g., 29760 i've done what it said on the survey and put all the data in as 297.60), the site model is very flat. 

As a result, the site model appears completely flat and inaccurate. Is there a quick way to remove decimal points from the data for hundreds of data points without manually correcting each one?

Would anyone be able to guide me on how to correct the data or resize the model before Monday morning? This is urgent I’d really appreciate any help!

Thanks Nicola 

[E|FA]

I don't know how to change the data itself, but I have a different thought:

1. Isolate all of the data points (3D loci?) by putting them in their own layer and/or class and hiding everything else.
2. Group them
3. View them in section
4. Draw lines at the highest and lowest elevations you need (e.g. 29760) 
5. Resize (stretch) the group to align with the top & bottom lines.  

I think this would adjust the elevations appropriately, but I might be missing something.  Good luck.

Edited March 1 by E|FA

[Tom W.]

Alternatively I think @michaelk has a worksheet script that allows you to edit the Z height of objects but I don't know if you can add a multiplier in the database header...?

[HebHeb]

Unfortunately, I don't know the English terms... The German translation is sometimes quite... let's say "special."

"Datenbank ändert Objektstildarstellung..."
 

But my understanding is:

You have an existing site model with "wrong locus points."
Go into the site model.
You could add a database for all locus points there, writing the existing height inside a field (for example a class based mapping inside data manager mapping).
Afterwards, you could change the Z height of each point with the "database changes object appearance" (Datenbank ändert Objektdarstellung).
There, you can choose the database field and set it to Z height (you might put them to value 0 first, otherwise it might stack on top...). This operator also has a scale option (in your case, 1000).

If you are talking about site modifiers, there might be other workarounds... (My guess was you are talking about locus, survey points, or 3D polys to create an existing model.)

Edited March 1 by HebHeb

[Tom W.]

1 hour ago, HebHeb said:

Unfortunately, I don't know the English terms... The German translation is sometimes quite... let's say "special."

"Datenbank ändert Objektstildarstellung..."
 

But my understanding is:

You have an existing site model with "wrong locus points."
Go into the site model.
You could add a database for all locus points there, writing the existing height inside a field (for example a class based mapping inside data manager mapping).
Afterwards, you could change the Z height of each point with the "database changes object appearance" (Datenbank ändert Objektdarstellung).
There, you can choose the database field and set it to Z height (you might put them to value 0 first, otherwise it might stack on top...). This operator also has a scale option (in your case, 1000).

 

@HebHeb I am not familiar with the Database Changes Object Appearance/Datenbank ändert Objektdarstellung command: would you have time to post a simple sample file...? When you say 'add a database' do you mean create a Worksheet or are you talking about an external database...? Thank you!

[HebHeb]

Hope this helps...

When the data is inside the database field, there are plenty of options on how to proceed further. Here is just an example

example.vwx

[Tom W.]

Aha I see thank you! You are using the 'Modify by Record...' command:

 

 

This is very very cool thank you for sharing!

 

[HebHeb]

Actually, I did know this, but speaking about databases (Datenbanken) every day... sometimes you forget just because it sounds too logical. And then the research is almost impossible; neither Google nor any LLM knows what I mean, that i meant "records" instead od datbases...
 

Sorry for the confusion. I would literally die for a UI where you can switch between languages... It's so bad that the local version differs, and in our case, we even have modules/plugins we couldn't live without...

[Jeff Prince]

8 hours ago, Nicola Bird said:

Hi All, 

I need emergency assistance. I have a deadline for Monday and I've added incorrect data in my site model. I usually build interior models and have limited experience with site models. I’ve spent a few hrs in putting all the site data, but I accidentally entered the measurements incorrectly. Instead of using millimetres (e.g., 29760 i've done what it said on the survey and put all the data in as 297.60), the site model is very flat. 

As a result, the site model appears completely flat and inaccurate. Is there a quick way to remove decimal points from the data for hundreds of data points without manually correcting each one?

Would anyone be able to guide me on how to correct the data or resize the model before Monday morning? This is urgent I’d really appreciate any help!

Thanks Nicola 

Let’s ignore your current VWX file for a moment.  Before you started entering data, how was it given to you?  Did the surveyor provide a spread sheet with all their point data?  Did they give you a text based points file?  If either of those is the case, the solution will be much easier by simply using the “import survey file” command than editing the existing points.

[P Retondo]

If your site data is 3d loci, just select all and Scale (x 100 or x 1000, or whatever your unit conversion factor is).  Scale Objects should be under the Modify menu.

Edited March 1 by P Retondo

[Jeff Prince]

52 minutes ago, P Retondo said:

If your site data is 3d loci, just select all and Scale (x 100 or x 1000, or whatever your unit conversion factor is).  Scale Objects should be under the Modify menu.

 

I'm guessing you haven't actually tried that trick in VWX 🙂

[P Retondo]

1 hour ago, Jeff Prince said:

 

I'm guessing you haven't actually tried that trick in VWX 🙂

 

Ha!  You're right, I was out and about in San Francisco, and just winged it.  But . . . just tried it, and it works.

 

What you are looking at is an extrude with loci at the corners, duplicated and changed to red, then scaled x 2.  Works equally well with loci alone.

 

Edited March 2 by P Retondo

[E|FA]

Looks like that scales in all directions.  My understanding of the OP is that they need to scale in the vertical axis only.

[Jeff Prince]

2 hours ago, P Retondo said:

 

Ha!  You're right, I was out and about in San Francisco, and just winged it.  But . . . just tried it, and it works.

 

What you are looking at is an extrude with loci at the corners, duplicated and changed to red, then scaled x 2.  Works equally well with loci alone.

 

That’s doesn’t solve the OP’s problem though, the change is constrained to the  Z axis only, which VWx excludes as a scale option.  That can be overcome by changing your POV or rotating your collection of points along the x axis, but that’s rather silly for a pro level program.

[Tom W.]

Scaling objects asymmetrically using Y Scaling Factor in Front/etc view is a perfectly good option in my opinion. Similar to @E|FA's manually scaling a Group.

[P Retondo]

3 hours ago, Jeff Prince said:

That’s doesn’t solve the OP’s problem though, the change is constrained to the  Z axis only, which VWx excludes as a scale option.  That can be overcome by changing your POV or rotating your collection of points along the x axis, but that’s rather silly for a pro level program.

I’m not sure the problem was clearly defined, but in my experience creating a site model from survey data, you have a set of NEZ data points, and import them.  If your units are wrong, they will be off in all 3 dimensions.  You can re-import, run a macro, or scale the objects to fix that.

[Jeff Prince]

9 hours ago, Tom W. said:

Scaling objects asymmetrically using Y Scaling Factor in Front/etc view is a perfectly good option in my opinion. Similar to @E|FA's manually scaling a Group.

Scaling constrained to Z should be an option in the scale menu like any other decent 3D package. Rotating your view to do so is counterintuitive.

[Tom W.]

11 minutes ago, Jeff Prince said:

Scaling constrained to Z should be an option in the scale menu like any other decent 3D package.

 

Not gonna argue with that. You can do it with symbols after all.

 

Anyway, getting close to the Monday deadline so hopefully one of these solutions did the trick... 🙂

[P Retondo]

7 hours ago, Jeff Prince said:

Scaling constrained to Z should be an option in the scale menu like any other decent 3D package. Rotating your view to do so is counterintuitive.

 

Are you suggesting adding the z axis to the asymmetric scaling option?  That sounds like a great idea, useful in many other situations.

[Jeff Prince]

1 hour ago, P Retondo said:

 

Are you suggesting adding the z axis to the asymmetric scaling option?  That sounds like a great idea, useful in many other situations.

Heck yeah, it’s common in every modeling program I’ve used.  It would be nice to be able to apply the same logic to 3D loci.

 

@Nicola Bird did you end up solving your issue?  If so, what did you do?

Edited March 3 by Jeff Prince

[Jonathan Pickup]

I would have imported  the 3-D loci again into a new blank file, then copied them from their into the source subjects of the site model. 

[Tom W.]

I think the points were added manually, that's the problem:

 

On 3/1/2025 at 4:25 AM, Nicola Bird said:

I’ve spent a few hrs in putting all the site data, but I accidentally entered the measurements incorrectly.

 

 

 

[Jonathan Pickup]

1 hour ago, Tom W. said:

I think the points were added manually, that's the problem:

 

 

 

 

in that case, I use stake objects so you can see the elevations as you enter them. 

[Tom W.]

21 minutes ago, Jonathan Pickup said:

in that case, I use stake objects so you can see the elevations as you enter them. 

 

I think she thought she was using the correct unit at time of entry so that might not have helped

[P Retondo]

Well, if she created them manually it took a long time to do what can be done in seconds by importing the points from a .txt or .csv file.  

[Tom W.]

Maybe only had a 2D survey to work off (+ didn't know there are ways to convert text into 3D points)