This is something that worked for me recently and thought I'd pass it along.
A while back, I used the scan surface feature of the S6 to collect a bunch of reflectorless shots on a large rock outcrop that is in the roadway prism of a scheduled construction project.
We hadn't done it before so it was a bit of an experiment. Anyway, I collected about 8400 points in relatively short order, basically 3 seconds per shot on this thing. I used a 0.6 m x 0.6 m (2'x2') grid. From 6 setups, in 16 data sets.
I processed them in Microstation V8i and Geopak, and found it was bogging things down so I needed a way to remove a bunch of points. So I decided I wanted to
get rid of every other point. To delete in the navigator it's 3 clicks each to delete a point. 12000 clicks. And I couldn't think of a way to sort and power select.
So my work around was this.
I listed all my point groups from my data sets, then went into excel. I made a point list by starting out with 8001, then 8003, 8005 (for example) then used the auto fill feature to finish listing all the odd points
in the data set. Then put in a N E and Elev of 10000 10000 100 for each point, and stored this as a .csv file. Then I imported these point into my gpk/ navigator. and it over-wrote all the odd numbered points.
Next I sorted the navigator by elevation so all my points with an elev of 100 were adjacent.- opened the power selector and selected by elevation range max 100 min 100- which selected all the odd numbered points again.
then delete- sure? yes and it deleted all the odd- worked very slick. 🙂
I used groups of 2400, 1100 and 1100 when I over wrote and deleted and it still bogged the machine down - but it eventually worked thru it all. I'm not sure if it would have made it if I'd done all the points at once.:-|
That surprises me that Microstation is crawling with the 8000 points.
I still use Microstation SE and I have a file that is over 24,000 points now and it runs just about as fast as a smaller file.
I also use Eagle Point.
Something else must be hogging up the file. I suspect it is not a cad problem, but a memory shortage.
Randy