Trimble Business Center

 View Only
Expand all | Collapse all

XML import works in one BC-HCE and not in 2 others, plus hole in surface

  • 1.  XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 10-31-2018 01:51

    Hi, this is 2 Questions in one. 

    First of all, can someone try to import this .XML and see if it works? We are 2 people running HCE 4.12 and when we import the file BC says the file is damaged and cant be used, on 2 different computers. But on a third computer the import works fine, also running 4.12. 

     

    The second question, when we imported the file the surface got a hole in one place (this happen sometimes with surfaces and i dont know why) and i cant close the hole. I tried to dra a linte around the hole and adeed it to the surface but it did not work. I had to export the surface as a ttm and import it as 3D lines and made a new surface, then it worked! 

     

    Anybody having the same issues?

     

    See you in Vegas!

    Attachment(s)

    zip
    3-5 Ny asfalt.xml.zip   4 KB 1 version


  • 2.  Re: XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 10-31-2018 21:44

    Frederik

    I have taken a look at your Landxml file and we found the following issues

     

    1) In the header, there is a persons name and in that name there is an illegal character for LandXML files which when read causes the LandXML  read to see the data as corrupt and flag it as an issue 0 simply eliminating the character in the file resolves the issue and allows the file to import OK (See Video)

     

    2) After import there is a triangular hole in the surface model - there are also a lot of flags in the surface model. This is because of small point errors between triangles - normally each point that is a connection between multiple triangles will have an identical coordinate - in this file there are a number of points that have slightly different coordinate values that fail our point tolerance check and as a result get flagged as potential surface model errors - the error is at a number of decimal places (beyond 3dp) but still cause the error - if you look at the data some point records in the LandXML are written to one number of decimal places, others to a lesser number of places - this is where the errors come in and because of this one triangle is not created as a result. If you use File Import rather than drag and drop, you get some settings that you can change - import the data as Polyfaces and do not look for holes and the file will import, still flag the errors but will have no surface holes - and you will have linework that you can edit and then form an updated surface.

     

    Hope the video helps

     

    Alan



  • 3.  Re: XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 10-31-2018 21:51

    Video - sorry forgot to attach it

     

    Alan



  • 4.  Re: XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 11-01-2018 00:20

    Hi Alan!

     

    That LandXML file works fine for me. Of cause I get the errors. It always like that when it comes from that softaware.



  • 5.  Re: XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 11-01-2018 03:07

    Thanks! Now i know why it did not work. Peter Gustafsson will upload a video from his computer where he can use drag n drop top import the same file. Strange that it works in his computer. 



  • 6.  Re: XML import works in one BC-HCE and not in 2 others, plus hole in surface

    Posted 11-01-2018 07:10

    I am surprised it works - maybe he has some different settings in his pc that allows the character to get converted or read - but as you saw in the video - the character is the problem that stops it working - normally if it fails in one pc it will fail everywhere

     

    Alan

     

    Sent from my iPhone