RIEGL VZ600i

[dhirota]

Tan Nguyen is leaving HNL tomorrow and LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

The last post of the VZ600i kinematic, was not impressive since we just pushed the VZ600i down the street on the dolly.

https://www.laserscanningforum.com/foru ... 93#p107193


With Tan Nguyen helping us, we mounted the VZ600i on the back of a truck and drove approximately 700 meters in each lane on the same street, using the fixed mode in one direction and radar mode (360 degree spin in 3 seconds) in the return. Total scan time approximately 10 minutes including an initial static scan and a concluding final static scan, with the kinematic scans in between.

GOOGLE KINEMATIC ROUTE.jpg

The fixed mode (on the left view) and the radar mode (on the right view) are shown individually using RTK (a requirement for kinematic) to register the kinematic modes with the static start and end scans to generate the trajectory in RiScan Pro processing (extra license cost).

FIXED MODE-RADAR MODE.jpg

Two different point cloud views from the total kinematic scans in both fixed and radar modes.

POINT CLOUD VIEW.jpg

X-RAY VIEW.jpg

Still waiting for the color. It should not be a problem to generate the color images in fixed mode.

It would be difficult to generate scans for this area of these merged point clouds in 10 minutes just with static scans from any TLS on the market today. If this was captured using our standard TLS approach with 10 meter tripod spacing and 60 seconds between scans, the 140 scan positions would take 2 hours and 20 minutes instead of 10 minutes.

Unless there are questions, that is it. There is more information, but I have been requested not to post it.

[landmeterbeuckx]

Tan Nguyen is leaving HNL tomorrow and LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

The last post of the VZ600i kinematic, was not impressive since we just pushed the VZ600i down the street on the dolly.

https://www.laserscanningforum.com/foru ... 93#p107193


With Tan Nguyen helping us, we mounted the VZ600i on the back of a truck and drove approximately 700 meters in each lane on the same street, using the fixed mode in one direction and radar mode (360 degree spin in 3 seconds) in the return. Total scan time approximately 10 minutes including an initial static scan and a concluding final static scan, with the kinematic scans in between.


GOOGLE KINEMATIC ROUTE.jpg


The fixed mode (on the left view) and the radar mode (on the right view) are shown individually using RTK (a requirement for kinematic) to register the kinematic modes with the static start and end scans to generate the trajectory in RiScan Pro processing (extra license cost).


FIXED MODE-RADAR MODE.jpg


Two different point cloud views from the total kinematic scans in both fixed and radar modes.


POINT CLOUD VIEW.jpg


X-RAY VIEW.jpg


Still waiting for the color. It should not be a problem to generate the color images in fixed mode.

It would be difficult to generate scans for this area of these merged point clouds in 10 minutes just with static scans from any TLS on the market today.

Unless there are questions, that is it. There is more information, but I have been requested not to post it.

Looks great Dennis. This kinematic app sure has potential.

But as much as you will post about Riegl and their great gear, loads of people will never understand it's way of doing business and will keep using other gear....

[tnguyen]

That is phenomenal. Curious what the scan time was for the high precision mode, if you completed a 360 degree scan.

using our scan parameters

normal scan (including saving images) = 37.35 seconds

High precision scan (almost complete scan-I think it will only do a sub-scan; no images) = 2mins: 30seconds


Here is the Riegl Chief Wizard for VZ600i that showed us about high precision, Tan Nguyen with me at my home in HNL overlooking Kokohead (Moanalua Bay), the islands of Molokai, Maui, and Lanai; after feeding my raised dove, Buddy and before dinner.


TAN-NGUYEN+DIH.jpg

Always a pleasure hanging out with you Dennis! I look forward to seeing you next year.

[tnguyen]

Tan Nguyen is leaving HNL tomorrow and LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

The last post of the VZ600i kinematic, was not impressive since we just pushed the VZ600i down the street on the dolly.

viewtopic.php?p=107193#p107193


With Tan Nguyen helping us, we mounted the VZ600i on the back of a truck and drove approximately 700 meters in each lane on the same street, using the fixed mode in one direction and radar mode (360 degree spin in 3 seconds) in the return. Total scan time approximately 10 minutes including an initial static scan and a concluding final static scan, with the kinematic scans in between.


GOOGLE KINEMATIC ROUTE.jpg


The fixed mode (on the left view) and the radar mode (on the right view) are shown individually using RTK (a requirement for kinematic) to register the kinematic modes with the static start and end scans to generate the trajectory in RiScan Pro processing (extra license cost).


FIXED MODE-RADAR MODE.jpg


Two different point cloud views from the total kinematic scans in both fixed and radar modes.


POINT CLOUD VIEW.jpg


X-RAY VIEW.jpg


Still waiting for the color. It should not be a problem to generate the color images in fixed mode.

It would be difficult to generate scans for this area of these merged point clouds in 10 minutes just with static scans from any TLS on the market today. If this was captured using our standard TLS approach with 10 meter tripod spacing and 60 seconds between scans, the 140 scan positions would take 2 hours and 20 minutes instead of 10 minutes.

Unless there are questions, that is it. There is more information, but I have been requested not to post it.

Dennis, thank you for sharing this project. The kinematic registration/data turned out very good, especially with multiple pass in two different scan modes (radar and fixed line). The important message here, no additional hardware was required, and it took us less than 30min to mount the scanner on the truck and collect data. Excellent work my friend. I look forward to seeing your next kinematic project.

[gsisman]

Tan Nguyen is leaving HNL tomorrow and LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

The last post of the VZ600i kinematic, was not impressive since we just pushed the VZ600i down the street on the dolly.

viewtopic.php?p=107193#p107193



Still waiting for the color. It should not be a problem to generate the color images in fixed mode.

It would be difficult to generate scans for this area of these merged point clouds in 10 minutes just with static scans from any TLS on the market today. If this was captured using our standard TLS approach with 10 meter tripod spacing and 60 seconds between scans, the 140 scan positions would take 2 hours and 20 minutes instead of 10 minutes.

Unless there are questions, that is it. There is more information, but I have been requested not to post it.

Thanks for the info Dennis- I might hit you up in PM for more info. Good to know other capabilities out there with a cross platform/usage capability
Just curious on the mount you used on the vehicle- you can PM me

[dhirota]

Tan Nguyen is leaving HNL tomorrow and LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

The last post of the VZ600i kinematic, was not impressive since we just pushed the VZ600i down the street on the dolly.

viewtopic.php?p=107193#p107193



Still waiting for the color. It should not be a problem to generate the color images in fixed mode.

It would be difficult to generate scans for this area of these merged point clouds in 10 minutes just with static scans from any TLS on the market today. If this was captured using our standard TLS approach with 10 meter tripod spacing and 60 seconds between scans, the 140 scan positions would take 2 hours and 20 minutes instead of 10 minutes.

Unless there are questions, that is it. There is more information, but I have been requested not to post it.

Thanks for the info Dennis- I might hit you up in PM for more info. Good to know other capabilities out there with a cross platform/usage capability
Just curious on the mount you used on the vehicle- you can PM me

Steve

Please send me an email next week to remind me to call you and tell you what we are doing to mount the VZ600i for vehicle kinematic mount and the US$200 walking kinematic mount I will receive tomorrow.

[smacl]

LSF removed Riegl VZ600i from their portal as a recent popular topic, so this might be my last post for this thread for a while after almost 25,000 views.

Hi Dennis,

To the best of my knowledge (maybe Jason can correct me here) there is no popular recent topics maintained by LSF, just a recent topics list. As posts are added to this thread, it gets bumped up to the top of recent topics. As folks start talking about other stuff in other threads, they get bumped up and older topics drift down the recent topics list.

Shane

[dhirota]

I should have added these few pieces of information that were forgotten in the hurry to generate the composite RECAP PRO.

We used the exported scan position KMZ of each VZ600i project to generate the location of the scanned projects which were dragged into GoogleEarth Pro. The KMZs were easy to generate since we were using RTK for registering each scan position.

6-SCAN POSITION PROJECTS KMZ.jpg

To give you a scale of the field time walking along the street side walks, executing a "stop-and-go" data capture, I took the date-time stamp of the beginning and last scan to compute the project field time. This did not include the travel time from our office to the start location which varied.

The total VZ600i scan time was 666.627 minutes for the 596 scan positions, including scanning (15million points average-maximum range 300 meters), 36 internal images (12Mpixel) captured, and movement from to each new scan position.

This averages out to 67 seconds per scan position. Using our parameters, the actual timed start up to end data store time is 31 seconds.

6-SCAN POSITION PROJECTS KMZ.jpg

Here is something to be thankful about (the day after THANKSGING DAY), when you hear that Riegl will be sending a calibrated SONY alpha7iv camera for me to try out until they figure out how to better compress the 61 Mpixel images that are generated by the SONY alpha7Rv camera that we have mounted on our VZ600i.

The SONY will probably capture 4 images per scan position, instead of the 36 images per scan position from the Riegl internal cameras. This will result in 4X596=2,384 images instead of the 36X596=21,456 images currently stored for the scans in the above screen shot. Hopefully the approximately 90% reduction in image number will result in some reduction in storage space.

[landmeterbeuckx]

I should have added these few pieces of information that were forgotten in the hurry to generate the composite RECAP PRO.

We used the exported scan position KMZ of each VZ600i project to generate the location of the scanned projects which were dragged into GoogleEarth Pro. The KMZs were easy to generate since we were using RTK for registering each scan position.

6-SCAN POSITION PROJECTS KMZ.jpg

To give you a scale of the field time walking along the street side walks, executing a "stop-and-go" data capture, I took the date-time stamp of the beginning and last scan to compute the project field time. This did not include the travel time from our office to the start location which varied.

The total VZ600i scan time was 666.627 minutes for the 596 scan positions, including scanning (15million points average-maximum range 300 meters), 36 internal images (12Mpixel) captured, and movement from to each new scan position.

This averages out to 67 seconds per scan position. Using our parameters, the actual timed start up to end data store time is 31 seconds.

6-SCAN POSITION PROJECTS KMZ.jpg


Here is something to be thankful about (the day after THANKSGING DAY), when you hear that Riegl will be sending a calibrated SONY alpha7iv camera for me to try out until they figure out how to better compress the 61 Mpixel images that are generated by the SONY alpha7Rv camera that we have mounted on our VZ600i.

The SONY will probably capture 4 images per scan position, instead of the 36 images per scan position from the Riegl internal cameras. This will result in 4X596=2,384 images instead of the 36X596=21,456 images currently stored for the scans in the above screen shot. Hopefully the approximately 90% reduction in image number will result in some reduction in storage space.

The advantage of internal camera results in massive amounts of pictures which will slow down all on every system.

Allthough 4 images seems very little with the Sony. Is the angle that large? My nikon D810 with 14/2.8 lens takes 6 images as a minimum for max coverage per scan.

[dhirota]

......

The SONY will probably capture 4 images per scan position, instead of the 36 images per scan position from the Riegl internal cameras. This will result in 4X596=2,384 images instead of the 36X596=21,456 images currently stored for the scans in the above screen shot. Hopefully the approximately 90% reduction in image number will result in some reduction in storage space.

The advantage of internal camera results in massive amounts of pictures which will slow down all on every system.

Allthough 4 images seems very little with the Sony. Is the angle that large? My nikon D810 with 14/2.8 lens takes 6 images as a minimum for max coverage per scan.

Lieven:

You might be right on the number of SONY+Voigtlander 10mm lens images required for the VZ600i. I am only guessing at the 4 since the Voigtlander 10mm lens has a FOV of 130 degrees rectiliner (see below)

VOIGTLANDER 10mm.jpg

VOIGTLANDER 10mm on SONY.jpg

Your Nikon 14mm has a FOV of 114 degrees and you are taking 6 images for a scan position on the VZ400i. It seems that Riegl researched and picked probably the world's best lens for the SONY sensor that they decided to use for their VZ600i.

The SONY alpha 7RV captures a jpg image 9504X6336 = 60,217,344 pixels and a file size of approximately 20 MB depending on the subject matter,
(see below).

VOIGTLANDER 10mm on SONY 20MB jpg 9504X6336 pixels (reduced to 1000X666 pixels for LSF .jpg

So if the calibration for the SONY camera on the VZ600i uses 6 Voigtlander images for each scan position, that would be 6 X 20MB or 120 MB for storage and 6 X 60Mpixels or 360 Mpixels for image density.

Let's compare that with the VZ600i's 3 internal cameras, (see below table)

VZ600i INTERNAL CAMERA.jpg

As you can see there will be less storage required using the external SONY camera, even using 6 images and the number of processing merging images from 36 to maybe 6 images, with slightly less image pixel density. I only used 10 versus 12 VZ600i for averaging the density since it made it easier to average the values.