ReCap Pro Decimation Grid

Discuss all Autodesk ReCap Studio related issues here.
Post Reply
MalteHC
V.I.P Member
V.I.P Member
Posts: 143
Joined: Mon May 05, 2014 11:19 am
Full Name: Malte Holm
Company Details: TLS
Company Position Title: Surveyor
Country: Norway
Linkedin Profile: Yes

ReCap Pro Decimation Grid

Post by MalteHC » Thu Jun 13, 2019 9:56 am

Hi All

I have a e57 registred pointcloud, that i would like, to get into an RCP file.
The e57 is raw, and i want to do a decimation filtering, therefore i do a 50 mm grid decimation, under the import in ReCap.
I assume that this function in recap means, that the distance between points should be 50 mm.
The raw pointcloud is very dense, since its a building scanning.
If i import the cloud is imported raw into ReCap, the size is about 160 gb and if i set the deciamtion Grid to 50 mm, is it about 100 gb.
I would have thought the size should increase significally (like 1/10 of the original size).

Does anyone know how the filter works and what it actually do?

User avatar
caddrafting2013
I have made 100> posts
I have made 100> posts
Posts: 100
Joined: Thu Jun 14, 2018 10:20 am
Full Name: Adam
Company Details: ADB3D Pty Ltd
Company Position Title: Director - Revit and Laser scanning
Country: Australia
Linkedin Profile: Yes
Location: Sydney

Re: ReCap Pro Decimation Grid

Post by caddrafting2013 » Thu Jun 13, 2019 11:30 am

Import it raw - Then export to 50mm decimated to a unified rcp

Can I ask what you will be doing with a 50mm decimated 160gb Pointcloud?


Sent from my iPhone using Tapatalk

MalteHC
V.I.P Member
V.I.P Member
Posts: 143
Joined: Mon May 05, 2014 11:19 am
Full Name: Malte Holm
Company Details: TLS
Company Position Title: Surveyor
Country: Norway
Linkedin Profile: Yes

Re: ReCap Pro Decimation Grid

Post by MalteHC » Thu Jun 13, 2019 11:54 am

But i dont want to unify it, i want to keep it structured.
Its because, there is a lot of different people, working with the same pointcloud. Some want all the small details and got computers, that are capable of handling big data. Others only want to see colums, walls etc. and are working on laptops. Therefore i do a dense scan, since i can filter down the points, but i cant make it more dense.

User avatar
caddrafting2013
I have made 100> posts
I have made 100> posts
Posts: 100
Joined: Thu Jun 14, 2018 10:20 am
Full Name: Adam
Company Details: ADB3D Pty Ltd
Company Position Title: Director - Revit and Laser scanning
Country: Australia
Linkedin Profile: Yes
Location: Sydney

Re: ReCap Pro Decimation Grid

Post by caddrafting2013 » Thu Jun 13, 2019 12:03 pm

Oh I see, Well good luck

That will take some time with Recap if you want to keep it structured


Sent from my iPhone using Tapatalk

mikajahkola
I have made 10-20 posts
I have made 10-20 posts
Posts: 17
Joined: Wed Jul 12, 2017 9:27 pm
Full Name: Mika Jahkola
Company Details: Myymore Oy
Company Position Title: Managing Director
Country: Finland
Linkedin Profile: Yes

Re: ReCap Pro Decimation Grid

Post by mikajahkola » Thu Jun 13, 2019 1:21 pm

I tested the same thing with my data.

I have a small point cloud that consists of 10 scans. They were registered in other software and imported to Recap as structured (gridded) e57 files without decimation. The point density of each scan was 2-3 mm on the average. The resulting recap support file size was 1,6 GB.

Then I imported the same files to Recap with 50 mm decimation grid setting. I measured the point density in Recap and found that Recap had arranged the points of each scan in a more or less regular grid with ca 30-35 mm spacing between points. I don't know the excact point count but from the densities you would expect a ratio of 100:1 (decimated vs non-decimated). However, the recap support file was over 700 MB.

Looking inside the support files I found that the bulk of the data is in .rcc and .rcs files, one per scan.
A typical scan looked like this:
rcs size rcc size
not decimated 52,2 MB 10,0 MB
decimated 1,5 MB 10,0 MB

So the rcs size had shrunk roughly proportional to the point count, but rcc remained the same.

From other posts I found out the the rcs file contains the indexed data and rcc file contains the compressed structured scan data.
If I understand right rcs is your actual point cloud and the rcc file is needed for Realview.
So, if you want to keep the structured data there is a lower limit to the support file size no matter how sparse decimation setting you select.

User avatar
gsisman
V.I.P Member
V.I.P Member
Posts: 233
Joined: Fri Oct 07, 2016 1:51 pm
Full Name: Steve Long
Company Details: Montgomery County DOT _ MD
Company Position Title: Land Survey Supervisor
Country: United States
Skype Name: gsisman1
Linkedin Profile: Yes

Re: ReCap Pro Decimation Grid

Post by gsisman » Thu Jun 13, 2019 4:06 pm

mikajahkola wrote:
Thu Jun 13, 2019 1:21 pm
I tested the same thing with my data.

I have a small point cloud that consists of 10 scans. They were registered in other software and imported to Recap as structured (gridded) e57 files without decimation. The point density of each scan was 2-3 mm on the average. The resulting recap support file size was 1,6 GB.

Then I imported the same files to Recap with 50 mm decimation grid setting. I measured the point density in Recap and found that Recap had arranged the points of each scan in a more or less regular grid with ca 30-35 mm spacing between points. I don't know the excact point count but from the densities you would expect a ratio of 100:1 (decimated vs non-decimated). However, the recap support file was over 700 MB.

Looking inside the support files I found that the bulk of the data is in .rcc and .rcs files, one per scan.
A typical scan looked like this:
rcs size rcc size
not decimated 52,2 MB 10,0 MB
decimated 1,5 MB 10,0 MB

So the rcs size had shrunk roughly proportional to the point count, but rcc remained the same.

From other posts I found out the the rcs file contains the indexed data and rcc file contains the compressed structured scan data.
If I understand right rcs is your actual point cloud and the rcc file is needed for Realview.
So, if you want to keep the structured data there is a lower limit to the support file size no matter how sparse decimation setting you select.
The RCC files I believe support the realview photos as you stated. You can delete them completely if you don't need the photo panorama in realview.
Data exported from Reg 360 v1.6 to E57 does not seem to take these panoramas over anyway. It creates a "Pseudo panorama" that I believe is created from "Blending" the RGB colored scan points together. It seems apparent from the Realview screen captures and very little difference in the Realview whether the RCC files are present or not


RECAP_DATA_STRUCTURE_2019-06-13_0857.png
RECAP_SUPPORT_FOLDER_STRUCTURE_2019-06-13_0900.png
RECAP_UPDATING_CACHE_2019-06-13_0906.png
Structured_setups_&_Mirror_balls_wo_photos_2019-06-13_0912.png
Mirror_ball_view_wo_photos_(RCC_files)_2019-06-13_0914.png
You do not have the required permissions to view the files attached to this post.

MalteHC
V.I.P Member
V.I.P Member
Posts: 143
Joined: Mon May 05, 2014 11:19 am
Full Name: Malte Holm
Company Details: TLS
Company Position Title: Surveyor
Country: Norway
Linkedin Profile: Yes

Re: ReCap Pro Decimation Grid

Post by MalteHC » Thu Jun 13, 2019 4:42 pm

mikajahkola wrote:
Thu Jun 13, 2019 1:21 pm
I tested the same thing with my data.

I have a small point cloud that consists of 10 scans. They were registered in other software and imported to Recap as structured (gridded) e57 files without decimation. The point density of each scan was 2-3 mm on the average. The resulting recap support file size was 1,6 GB.

Then I imported the same files to Recap with 50 mm decimation grid setting. I measured the point density in Recap and found that Recap had arranged the points of each scan in a more or less regular grid with ca 30-35 mm spacing between points. I don't know the excact point count but from the densities you would expect a ratio of 100:1 (decimated vs non-decimated). However, the recap support file was over 700 MB.

Looking inside the support files I found that the bulk of the data is in .rcc and .rcs files, one per scan.
A typical scan looked like this:
rcs size rcc size
not decimated 52,2 MB 10,0 MB
decimated 1,5 MB 10,0 MB

So the rcs size had shrunk roughly proportional to the point count, but rcc remained the same.

From other posts I found out the the rcs file contains the indexed data and rcc file contains the compressed structured scan data.
If I understand right rcs is your actual point cloud and the rcc file is needed for Realview.
So, if you want to keep the structured data there is a lower limit to the support file size no matter how sparse decimation setting you select.
That actually makes perfect sense. For what i know, RCP stands for ReCap Project, RCS for ReCap Scan and RCC i dont know.
But it could be a high detailed panorama and thats also makes good sense, why it gets lighter, if you unify and export the data.

Post Reply

Return to “Autodesk ReCap Studio”