aage.langedrag

Hi @yasin2rayNot sure if you have received an answer to this question but also if I understand you correctly. Here is an overview of how I have extracted all components of the Landscape Area in the same list where the Landscape Area Style is listed. I have entered a copy of the codes I have used in the various columns in the database on row 3. What was important to me was also to list the IFC GUID on all the components. Unfortunately I can't find where this is stored in VW. I can't find any other IFC data on the components either. If anyone has an answer, I would greatly appreciate feedback. Otherwise, you should be able to list other properties of the components in this Worksheet. Also watch this film on YouTube from 2:31 min components in worksheets_v2024.vwx

Had similar problem. Not sure if this applies to your situation. A user had changed the Shaded Options to Textures and not Colors. The Site Model surface was always white. After much trial and testing. Found the error under Shaded Options. Switched back to Colors and everything is "Normal".

Hi @Pat Stanford. Thanks to your previous explanation has helped me. Do you know if it is possible that this important difference could have been programmed into Vectorworks? It would be nice if we who use Vectorworks could get formula examples that correspond to how the program works here in Europe?;) Unnecessary use of a lot of precious time before finding solutions a little randomly in a forum.

@kwik I have not looked in detail at your challenges Knut, but have discovered that to extract m3 I ended up with a formula that calculates the area m2 and times the thickness of the object or the thickness of the material if objects consist of several layers. Got more correct quantities than if I tried to extract m3 from the object. This is on Landscape area and Hardscape objects. not sure if you can use any similar method.

Yes, in Excel, commas (`,`) and semicolons (`;`) are used differently in European and American versions of the program. - **American version:** Functions and formulas use commas (`,`) as separators between arguments. For example: ```excel =SUM(A1, B1, C1) ``` - **European version:** Functions and formulas use semicolons (`;`) as separators between arguments. For example: ```excel =SUM(A1; B1; C1) ``` This is because the European version of Excel often uses a comma as a decimal separator (eg `1.23` instead of `1.23`), while the US version uses a period as a decimal separator. The setting can also be adjusted manually in Excel under regional settings options if you wish to switch between these formats.

Hi, Try replacing IfcGeographicElementType with IfcGeographicElement as Kristian mentions. Or have you managed to find a solution?

All geometry that Landscape architects works with that is to be built should use curves with whole numbers of radius. No curves shall be divided into lines. The problem arises especially in our company when geometry is imported from other software such as dwg. All curves are then divided into countless lines, which is useless and makes the model very difficult to work with. When this happens, I ask those responsible to re-model the geometry in Vectorworks so that all curves and arcs have geometry that can be adjusted and changed. All arcs then only consist of three points, start, middle and end. This is where it is important to further control geometry with Simplification Tolerance. The first image shows geometry that is correct, while image 2 shows precisely the problem that the geometry has come from AutoCAD 2D. Sloppiness and inaccuracies that have worked for drawing production in 2D do not work when we work in 3D and BIM. Geometry must therefore be modeled again or changed so that all curves get the correct shape. Why should we allow mistakes to continue in the first place? 3D and BIM are also helpful in making us more precise and accurate.

Finished setting in VW2024 is probably 0.025. Setting is absolutely essential for the large model in VW to work and not collapse. After much use of this method in my models, I have used this general rule. 0.02 or now 0.025 - Early stage and standard. Then I work in more detail on how you want the object structure to be in the IFC for construction. NB. You have to work your way back and forth with some objects that have complicated geometry in order for the object to display correctly in 3D. Some solid objects in VW sometimes lose 3D geometry and then it helps to change the Simplification tolerance. Thin edges with rough settings mean that the outer and inner side of a curved edge suddenly have overlapping and intersecting geometry, which then becomes incorrect. Therefore, you sometimes have to go down 0.002 on certain objects while the rest can be 0.02. You also need to use setting to let geometry which is important to get right in IFC for build to model, edging of steel, get 0.002 while plant field which only specifies a 3D volume with plants has got 0.02. Very frustrating is that every time you have made changes to a landscape area, the setting is reset to 0. Completely unnecessary, unfortunately, so you have to make the changes again. I have built-in control views that color all objects after setting the simplification tolerance. All objects that have this =0 are red. This helps me quickly spot problems before I export IFC. Large models cannot change many objects at once. You must then select one volume at a time to change. If you have sent the landscape area to a site model that is on different design layers, a new problem. Then you must remember to have the Site model visible before you start making changes to the landscape area, otherwise the object will lose its height and lie down at sea level.

Hi @Scott Campbell, Thanks for the reply where you show the Fence specific parameter. I keep forgetting that I have to look for these under "Expert formula". When I, who believe that I am quite interested in finding solutions, am "unable" to find this, I think that it should have been easier to find these parameters. Why isn't this simple in the "Simple formula" on relevant object types?????? The most relevant properties for all object types should be the properties that are always found. I also cannot see the length of the railing or Fence when I mark the object and look in OIP. Isn't this standard info? I greatly appreciate Vectorworks' great possibilities, but I am equally amazed at how much time I spend looking for very simple features and functions that I believe should have been visible to me without me having to test and search and search for help. When it comes to rounding off the length of the Fence in the example model, this must be an error in the program. I haven't done anything special. I only selected the standard object type from the library so I wonder if the program doesn't understand that the file is set with Units in meters?

How do I get the length of railing and fence as a property in IFC via Data manager. Does not work correctly in current version of v2024. "Lengte()" shows correct for Railing but wrong for Fence when I read this in OIP. 2024-04-15_Railing og Fence hvordan hente ut lengde.vwx

Hi @Scott Campbell I saw that this whole thing was misleading. Have tried to change the heading and be more clear in the original text.

Hi @Scott Campbell. Watch this video and you will see that when I create a grade on Design Layer-2 and snap to Grade on Design Layer-1, the Grades on Design Layer-1 are split up. In many cases, we want to be able to see Grades from a Designlayer and snap to but not split up. 2024-03-11_12-27-21_v2024 - Grades.mp4

Big wish that Grades on different design layers can snap but not connect to Grades on other Design Layers. I work with several alternative solutions on different Design Layers. Very frustrating that Grades on Design Layer-01 connects to Grades on Design Layer-02 and divide that Grades . Suddenly, I have divided the Grades on another design layer. The elevations have also been altered and "destroyed". I wish I could have a setting that says that Grades should only connect with other Grades on the same Design Layer or that I could choose from a list which Design Layers can be connected.

Here is a copy from a discussion on Beta which should also be available to everyone. The case does not contain content affecting Beta. «…..The best thing is to be able to go back to whoever sent the file that is wrong about sending a new file that uses the project's common internal datum. We had this problem before, but in the last 10 years, all projects I have contributed to have more or less got this in place. BIM coordinator in the project ensures that the project has a common internal coordinate point BEFORE the technical engineers start working. In a construction project, it is often the Architect who is responsible for determining an internal coordinate point for the project that is located so that ALL disciplines who contribute to this project must have their objects placed with positive coordinates. The shared internal zero point is then often at the bottom left of the project's boundary. This also becomes our internal zero point in Vectorworks so that IFC files from us and other disciplines match before starting the project. I know that those who use Solideworks also struggle with z-axis orientation, but I have been involved in this in the past. A few weeks ago at the latest and they manage to solve this as well if we make demands. I had to search Google myself to find a solution for them, but the solutions are there. You probably know this, but just want to clarify if others are reading this how important it is that we who use Vectorworks look at the Vectorworks local zero point together with the project's local zero point when we work with IFC. There, Vectorworks has not been clear in its presentations as far as I have been able to see. Therefore, we should look more at buildingSMART's description of the local zero point. Sorry, the document is in Norwegian, but use a translator and you will understand what this is all about. Thought I'd also seen an international document in English but can't find it now…..» bsnp_georeferering_20100415_EN(Google translate).docx

Hi, Not sure if this has been mentioned earlier in this case. ALWAYS open dwg from ArchiCAD in Civil3D/AutoCAD before importing in other programs. In the Nordic countries we use metric units. Architects in millimeters and Landscape architects in metres. Check the unit of the drawing on known dimensions. Most often you see by measuring that the file from Architects delivered from ArchiCAD is then in millimeters. Then comes the fun part. Check "Units", even if the file is drawn in millimeters, the dwg from ArchiCAD ALWAYS comes with "Units=feet". You must change this to millimeters without changing the geometry. Save the file and import this file into Vectorworks.