Recap files workflow

[johan.degreef]

We scanned a first site (RTC360) to use the pointcloud inside Inventor, so we created a recap file of the raw data.

What is your workflow to position the pointcloud inside an Inventor assembly?

Do you constrain it directly in the assembly?

Do you create a dummy part to attach the recap file, and constrain the part in your assembly?

What if you use Vault pro, does the recap file goes to the Vault too?

As a new user of 3d scan data I want to know a solid workflow.

many thanks for helping, Johan

[blandb]

We are just getting into this as well. After a scan I bring everything into RECAP. I then try to reset the origin of the recap to be on a building column and at the ground as best I can, then rotate to be normal as best I can. Crop out what is not needed for the project, then create an RCS file. I then place this RCS file into a new part allowing it to just match 000. I place it into a part because I set the bom structure to be reference and I can then use work planes and what not to set elevations or other work geometry as needed. If also given a cad file, I can then place the cad file as a dwg underlay and project what is needed as well..

I'm still learning a good workflow for point clouds, but it seems to be working for us. I just wish after all this, there was a way to place point cloud data into a drawing. Some of our recent scans have no column callouts as it is just structures outside, and trying to find a good way of referencing items seems to be a struggle. I will need to callout out everything via text and lines to get the point across.

[Gabriel_Watson]

I was where you are about 5 years ago and tried my best, but still found this all too clunky. I believe Revit and Navisworks still make the best out of point clouds if your company can leverage those...

Anyways, you are correct to first use Recap or another to edit the raw file, which is so heavy and sometimes consists of multiple files that you will need to combine first. You should be able to place a UCS into a new part that carries that point cloud import, and that's how I would typically start in Inventor. Then, make as many planes and other construction surfaces as needed using the point cloud tools, to reference those later.

Vault should never take files above 500 Mb, especially files that are considered more "raw" like long video files. I think point clouds can be in Vault if they are used very sparingly. Unfortunately that means you will need a network drive to store those (cloud would be too expensive in the long run), and the part that references the cloud data can be checked into Vault.

I will also leave the workflow below that I took some notes on, which was a combined effort from my reseller and Autodesk to provide advice on how to convert those point clouds into something more solid to work with:

- Converting Point Cloud data into Inventor solids/surfaces: Open the RCS/RCP point data in Autodesk ReCap, and save it as PTS extension. Rename the file extension to ASC, and open it with MeshLab (free software). Pick "Filters > Remeshing... > Surface Reconstruction: Ball Pivoting" in MeshLab, and Apply a 0.1 world unit or smaller if possible. Export Mesh as OBJ extension. Open the OBJ file in Inventor and Convert to Base Feature the mesh features. Tips for big data sets:
Filters > Sampling > Poisson-disk Sampling
Filters > Point Set Select Visible Points
Filters > Cleaning & Repairing > Remove Duplicate Vertices
Filters > Cleaning & Repairing > Remove Vertices wrt Quality
Filters > Remeshing Simplification and Reconstruction > Surface Reconstruction: Ball Pivoting (see settings above, experiment till you get the right settings for your worklflow)
"It is advisable to simplify large models by reducing the number of points (Filters > Sampling > Poisson-disk Sampling). First generate normals on the loaded model:
Render > Show vertex normals
Save the file (Export Mesh, .ply) with the option Normals and re-open it
Filters > Point Set > Compute normals for point sets
Consequently, it is possible to generate a 3D grid (mesh) model:
Filters > Point Set > Surface Reconstruction: Poisson
Remember to use the top command bar to switch to the 3D mesh model.
The resulting 3D model can be then saved to a DXF format that can be loaded into any standard 3D CAD application."

[johan.degreef]

@Gabriel_Watson 

Thanks!

We will not need solids from that pointcloud. They are just imported into our assemblies to see if it clashes with some other new designed parts. If I need a solids matching the pointcloud, it will be simple cubes.

[Gabriel_Watson]

Keep in mind that for clash detection (and especially involving other format files, including point clouds), the gold standard is to use Navisworks Manage for the analysis!

[johan.degreef]

@Gabriel_Watson 

So you are saying that I better keep inventor assemblies without pointcloud, and use naviswork instead to combine inventor assembly and pointcloud?

[Gabriel_Watson]

If clash analysis is all you need, sure.
If the purpose of the point cloud is to build some models around it, then bring it into Inventor and create some planes for guidance. But otherwise, I think Navisworks is what I believe can leverage this best.

[johan.degreef]

---

@Gabriel_Watson wrote:
If clash analysis is all you need, sure.
If the purpose of the point cloud is to build some models around it, then bring it into Inventor and create some planes for guidance. But otherwise, I think Navisworks is what I believe can leverage this best.

---

It is kind for both.

[blandb]

I put the PC in the part file, so later I can remove it if I need to, but during the design phase, I use it to help generate other work features. Unfortunately, I do keep the PC attached to the part file and check it into vault eek....

[johan.degreef]

---

@blandb wrote:

I put the PC in the part file, so later I can remove it if I need to, but during the design phase, I use it to help generate other work features. 

---

You can remove a pointcloud too when attached directly into the assembly. and just attach it back again if needed, so what it the + on putting it in a part?

[blandb]

I use a part as my "building" reference part. All columns, work planes, axis, etc, dwg underlays, reference placement sketches, etc will be there. The assy just has the components, and not bloated with work planes etc. The building is brought in incase I need to reference that stuff.

[Gabriel_Watson]

If you need to break the relationship, you don't need to open your whole layout assembly. Just open a part and kill the connection.

[johan.degreef]

@Gabriel_Watson @blandb 

Where do you set an UCS 0,0,0? in the scanner software, in Recap, or you do not set an UCS at all, and leave it with the scanner defaults?

I think the best is to attach the recap file into the part and always have to choose to insert it at origin point, right?

If you have several limitboxes of partscans of the same project, when inserting a few limitboxed parts with origin 0,0,0 , they all fit nicely...

[blandb]

I set the 000 in recap, when you have it open go to:

Then pick and choose where you want the origin to be and what Axis goes which direction you want. You can also, rotate to align. Once this is set, you should just be able to place at 000 inside of INV.

[Gabriel_Watson]

You can set multiple UCS, even if your point cloud is centered. For example, you center a factory floor point cloud, but then set different planes and UCS for where the machinery needs to go. It makes inserting assemblies into it easier. That's one advantage over simply adding the point cloud into a major assembly, because if you insert it into a part you can build all those little work geometries to better organize your layout like a skeleton.