Error 32771 importing .zfs files into Navisworks 2016 & 2017

Error 32771 importing .zfs files into Navisworks 2016 & 2017

Anonymous
Not applicable
705 Views
4 Replies
Message 1 of 5

Error 32771 importing .zfs files into Navisworks 2016 & 2017

Anonymous
Not applicable

Hi Everyone,

 

I am attempting to import a .zfs scan file into Navisworks Manage 2016 or 2017. When I select the file for Import, I get error 32771 which says that the file is corrupt(it isn't - we have successfully imported it into Recap, FME and Global Mapper with no issue). Any ideas of how I can resolve this?

 

 

0 Likes
706 Views
4 Replies
Replies (4)
Message 2 of 5

Patrick_Aps_9121
Advisor
Advisor

Because of Recap, the Navisworks file readers for a lot of LaserScans do not get updated any more.

If it is only one scan, and you have imported into Recap, attach the RCS file from the Recap Support folder in Navisworks.

If it is a Recap Project, attach the RCP file in Navisworks.

0 Likes
Message 3 of 5

Anonymous
Not applicable

I have done that so that I could get my client working. When you scan the list of directly imported scan data types, .zfs is on the list - if .zfs isn't actually directly importable into Navisworks, then it should be removed from the list. Thanks for the reply though, but I guess for the time being, I will use Recap to prepare the Navisworks file.

 

0 Likes
Message 4 of 5

Patrick_Aps_9121
Advisor
Advisor

I presume that you can import ZFS directly into Navisworks if the file format is old enough. Just like DWG and all other formats, the file format evolves in time. But with laserscans, everything evolves very fast. Newer scanners so newer file formats and Navisworks is leaping behind.

 

If you use the publish function, you even can include the whole Laserscan into the NWD, but the NWD file then can grow up to 10 GB or larger.

Message 5 of 5

dgorsman
Consultant
Consultant

That's one of the reasons for ReCap - everything pointcloud is now in one development silo.  Instead of a bunch of different groups scrambling trying to keep up, there's just one and they take care of that for all the products, allowing the other product teams to put their resources towards their own core features.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


0 Likes