RIEGL VZ600i

[dhirota]

Not too much news from anywhere on the Riegl VZ600i. Still have not received my demo data sets, maybe this coming week.

RIEGL-SPAR-JAPAN.jpg

I have been invited to see the first demonstration of the VZ600i in the USA January 11,12,13 in Florida. I decided that the 12 hour one-way flight and the US$4,000 round trip airline ticket was too much to handle before the Geoweek demonstration that Riegl will be conducting of the VZ600i. I decided to post this in the event that some folks near Orlando, FL, who might not be attending GeoWeek, would like to see the VZ600i in action. They should contact Riegl USA for an appointment.

[dhirota]

I never received my VZ600i demo scans. I would like to see it working perfectly in 4 days at GeoWeek.

Here is a question for you, how fast do you think the scanner pictured below can rotate and still capture accurate point clouds?

VZ600i.jpg

I have an answer, but I will let you know in 4 days when I see it.

[gsisman]

I am not sure why there are "headaches" from users about files sizes from their scans. I have not heard/seen these comments from the many NavVis users that I personally know, considering that we own a NavVis M6 and VLX, which have scans, images, and other file types as part of the database. The NavVis raw files are larger than their finished files which have the dynamic objects and repetitive points removed (we normally post-process to a 5mm grid). There have been positive comments from LSF viewers on the color and clarity of NavVis finished scan files.

I think you may have misunderstood me here. As I've written on a number of occasions, NavVis are ahead of the field here in that they've successfully addressed the scan size issue through rationalizing (as opposed to simply decimating) the point cloud is such a way as to remove the bloated size we see in some point clouds. My point was that other manufacturers should be applying similar techniques. With a static scanner capturing millions of points per second we see a massive number of redundant points close to the setup position in order to get the desired density further away. Where these points are coplanar and not adjacent a change in the surface, most can be eliminated. Simply decimating by comparison removes points we'd like to keep. The NavVis solution goes further in terms of introducing extra calculated points further away to provide a uniform Cartesian density, where a TLS gives points at uniform horizontal and vertical angles and other mobile scanning systems give points at uniform angle and distance (assuming constant velocity). Given this new Riegl scanner can capture points at 2.2mhz it would clearly benefit from similar techniques to rationalize the density.

Edit: For an example of the 'headaches' relating to large data, see the following very recent thread. This seems to be a rather common theme over the past few years.

This one unique thing about NavVis makes it a very good option for Cloud to mesh software or SaaS operations. There is very good uniformity in the mesh along with greatly reducing the number of necessary points and the size of the files. This becomes a bigger issue for agencies/companies storing an entire library of reference scans/3D data (particularly off site) for documentation, asset management and long-term design projects. (Although shuttling between Low-cost static BLOB storage and active dynamic storage can help)

[dhirota]

I never received my VZ600i demo scans. I would like to see it working perfectly in 4 days at GeoWeek.

Here is a question for you, how fast do you think the scanner pictured below can rotate and still capture accurate point clouds?

VZ600i.jpg

I have an answer, but I will let you know in 4 days when I see it.

It has been another month, and I have still not received my demo scans, but hopefully something will happen in another month (if one is patient, occasionally good things sometimes happen).

I unfortunately could not stay for the VZ600i demonstration at GeoWeek, so I did not see it in kinematic mode rotating in RADAR mode in 3sec. I have seen a VZ400i in kinematic mode rotating 360 degrees in 3 seconds.

We completed a simple VZ400i project at a resort along the beach front walkway last week. We processed the scans using Riegl RiScan Pro version 17.0 with an internal filter that retained all the returns (10 using a VZ600i). Although we used a VZ400i, a VZ600i would result with a similar effect of the visualizing the landscape as shown in the image below in RGB (first return, followed in RED for the multiple returns of the buildings + distant coconut trees embedded in the dense tropical vegetation). This can be visualized of the total tree detail located in the center/lower third of the image next to the beach walkway.

RESORT-VZ400i.jpg

In this project, we were trying to locate the buildings along the beach without disturbing guests in their US$2K to $20K per night accommodations. The trick here is to finish the scans early in the morning while guests are still in bed, we used RTK for registration (so did not require physical/surveyed targets). Total field time (less than you think) for 22 scan positions (VZ400i=45seconds, VZ600i=30seconds per scan position including color RGB imaging).

[dhirota]

For those that might not be familiar with Riegl scanners being part of robotic systems, here is an example I posted many years ago.

viewtopic.php?p=44399#p44399


For those that not have ventured into what Riegl has to offer with their VZi scanning systems, pictured below is the Riegl "ROS driver" to use with their VZi systems.

ROS2-RIEGL-VZi.jpg

It appears to be using Ubuntu-Linux-ROS which is similar to our NavVIS-Ubuntu-ROS system.