Hi
There is an huge bugg whithin xml surface model import.
Example files:
Tunnel in dxf referens (or import, the same result)
The same information in surface xml and imported to microstation is not good (bugg)
Lok at the sides of the tunnel in image, these are totally wrong.
Microstaion version:
Version:10.17.01.58
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 OtoHere 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
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#666138Why 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.
The Surface landxml format is great but it is old format, It is better to pusch the IFC people to evolve this issue (they don´t think very "big" (outside the bulding box) yet)). As i wrote before is Bentley a great design software but if we talk about the whole life cycle of an projekt is bentley not a good choice.
Please no. IFC is not suited for such things and file sizes are big. We already have issues with BIM people requesting reality models in IFC and then wondering why can't open them.
Tom said:we talk about the whole life cycle of an projekt is bentley not a good choice.
Theoretically and for marketing standpoint it is ideal choice but there are some stopping points which doesn't allow us to get there. For example there is IFC export from OpenRoads, great until you try it and found out that custom 3D line styles do not export correctly. If such issues would be promptly fixed then no doubt about choice.Same for this issue with LandXML where Bentley takes a stance that it is for DTM only and so most likely will not implement TIN mesh as lack bigger picture why it is actually needed.
Hi OtoI agree in total what you wrote.
I found some other email for LandXML organization and resent the question regarding TunnelXML. Let's see.
At least FME allows such input as LandXML surface:
Surface