XML surface error when importing surface landxmlfile

Do you have any example to share?
If the triangles are already generated in XML then there should be some way how to import it as mesh and not terrain.
LandXML can contain points and triangles it is true.

Hi Oto

Here is an example:

test_moved_XML.zip

And to view the tunnel you can reference this ifc file of the same information as the XML is:

test_moved_IFC.zip

Regards

Tom

Here you go. VBA macro which allows to select a LandXML file for import and imports it as triangles. Beware it is slow to import using VBA so have to wait couple of minutes. Added also a progress bar to at least get some feedback.

As VBA doesn't have API for mesh creation then need to later convert triangles to mesh using mesh tools. 

import-Landxml-mesh.mvba

Here you go. VBA macro which allows to select a LandXML file for import and imports it as triangles. Beware it is slow to import using VBA so have to wait couple of minutes. Added also a progress bar to at least get some feedback.

As VBA doesn't have API for mesh creation then need to later convert triangles to mesh using mesh tools. 

import-Landxml-mesh.mvba

Millions of thanks Oto!

I test your VBA as soon I have the time, what I suspekt when you wrote that is slow is that I probably can´t have it as my day to day workflow BUT you have created something that Bentley should have as an option in XML import function.

Bentley has the new Open tunnel design software but I don´t think that Open Tunnel can take care of "as built" tunnels. It is sad that you can not take care of your whole project cycle with Bentley produkts, you can design but not process "as built" material.

Regards

Tom

PS

The software that I use to handle the "as built" scanned data and from where I exported the test material was from Cyclon 3Dr
Leica Cyclone 3DR | Leica Geosystems (leica-geosystems.com)

Example in file sizes of the scanned/meshed tunnels:

Example size (dxf)

Max size that we allow is 200 mb (dxf):

But there is bigger file sizes that we need to check and plan how to make them smaller

XML file is loading 80% faster to softwares than dxf, xml is also mutch faster to deliver via internet than dxf, so thats is the reason for trying ton use XML as an "workfile format" 

And if there was a way to import xml triangeles as mesh you save more time, to exchange dxf "shapes" to dwg mesh is taking a lot of time when triangel summary is over 400000 and biger than that it tkes hours.

This examples above is skanned lenght from 0-50 m and the largest is about 200m long, take this times 4000m x3 paralell tunnels you can getthe amount of data that we have to handle

All the skanned data needs to be delivered as dwg mesh,, this is our main problem.thT i try to solve inside microstation.

//Tom

Bentley is interpreting that TIN doesn't allow meshes with overhang and converting it to DTM. This is not correct as TIN only means it is triangle mesh not that it is DTM.
https://communities.bentley.com/products/3d_imaging_and_point_cloud_software/f/contextcapture-descartes-pointools-forum/217981/landxml-data-for-sandvik-driller-s-office/666138#666138

Why not use OBJ format? 

Hi Oto

We are using Leica Cyclon 3dr to process scanned tunnels etc. Problem with cyclon is that it isn´t fully a cad software. What the issue has been is the size of the dxf mesh model that exported from cyclon is big in file format, to speed up everythin the surface xml was an option but I need to back on that one also regarding to speed. IFC is what it is, looks nice but need time to evolve as an file format. All other known "model" formats is good but don´t handle large coordinates so vell or some not at all.

so short, Microstation is not the software that can handle my issues, I have to go a long way for processing  scanned tunnel data to be useful in microstation.

//Tom

I reported this to Bentley and got enhancement Filed: Product Backlog Item 1034545: Add the ability to import XML file as a mesh not only as a Terrain

Tom said:

but don´t handle large coordinates

Yeah that I forgot by recommending OBJ format it won't handle large coordinates and Microstation ignores any OBJ sister files to use them. We definitely need LandXML with mesh format. To put last nail in the coffin tried to contact LandXML org for explanation if TIN is only DTM or any mesh, no reply yet.