.
I've been playing a bit with the Leica Register 360 and is an interesting workflow but I dont see it doing what Recap was doing, that is to "index" scans. Does someone knows exactly what is this step in Recap software, when importing new scans and after registering them?
What is "indexing" in Recap?
-
- I have made <0 posts
- Posts: 8
- Joined: Thu Nov 01, 2018 5:16 pm
- 5
- Full Name: Thomas Gregor
- Company Details: GENT
- Company Position Title: Mechanical Technical Supervisor
- Country: Canada
- Linkedin Profile: No
Re: What is "indexing" in Recap?
Hi Darius,
According to AutoDesk, Indexing is "The process of structuring a raw scan file so that it can be opened in a CAD product" (https://help.autodesk.com/view/RECAP/20 ... 816B644A48).
According to AutoDesk, Indexing is "The process of structuring a raw scan file so that it can be opened in a CAD product" (https://help.autodesk.com/view/RECAP/20 ... 816B644A48).
- smacl
- Global Moderator
- Posts: 1409
- Joined: Tue Jan 25, 2011 5:12 pm
- 13
- Full Name: Shane MacLaughlin
- Company Details: Atlas Computers Ltd
- Company Position Title: Managing Director
- Country: Ireland
- Linkedin Profile: Yes
- Location: Ireland
- Has thanked: 627 times
- Been thanked: 657 times
- Contact:
Re: What is "indexing" in Recap?
Indexing a point cloud typically involves placing all of the points in an octree or similar spatial structure so that they can be displayed quickly based on your current resolution and searched quickly using various filters.
- Scott.Warren
- V.I.P Member
- Posts: 364
- Joined: Tue Jan 30, 2018 3:14 pm
- 6
- Full Name: Scott Warren
- Company Details: WSP Canada
- Company Position Title: Project Manager - Geomatics Engineer
- Country: Canada
- Linkedin Profile: Yes
- Location: Dartmouth, Nova Scotia, Canada
- Has thanked: 44 times
- Been thanked: 111 times
- Contact:
Re: What is "indexing" in Recap?
My guess would be the 'Indexing' is Recap taking all the point data and organizing it in a way it feels best able to manage the data.
A list of point values in arbitrary order might be good for some applications, but not all. So if you sorted your data based on other criteria, like sorting the data into blocks/chunks, you might be able to work with the data more efficiently. if your data is sorted (indexed) into localized chunks/blocks, you can display the data more efficiently by only loading the chunks (index) of data in your view, and not load/sort through 1 big un-sorted (un-indexed) list of point data.
LAS, E57, PTS, PTG, etc, all sort the data differently, some are sorted by individual scan setup, some separated into blocks/chunks, and some are just a wall of unorganized N,E,El (X,Y,Z) data.
A list of point values in arbitrary order might be good for some applications, but not all. So if you sorted your data based on other criteria, like sorting the data into blocks/chunks, you might be able to work with the data more efficiently. if your data is sorted (indexed) into localized chunks/blocks, you can display the data more efficiently by only loading the chunks (index) of data in your view, and not load/sort through 1 big un-sorted (un-indexed) list of point data.
LAS, E57, PTS, PTG, etc, all sort the data differently, some are sorted by individual scan setup, some separated into blocks/chunks, and some are just a wall of unorganized N,E,El (X,Y,Z) data.