Field 360...aligment woes

[Jonny5isAlive]

Running the latest version of the app which includes "quick link" et al.

RTC running FW v 1.2.

Scanning roadways. Scans approximately 60 ft apart. Medium res.

"Quick link" makes bad links. Not aligned, badly placed.

"Optimize" throws seemingly good initial alignments out of whack, and obviously misaligned.

It appears best course of action is to manually link in app, skipping "optimize", going straight to "create link".

Anyone have similar experiences/thoughts on this?

Thanks!



Sent from my SM-N950U using Tapatalk

[gsisman]

Running the latest version of the app which includes "quick link" et al.

RTC running FW v 1.2.

Scanning roadways. Scans approximately 60 ft apart. Medium res.

"Quick link" makes bad links. Not aligned, badly placed.

"Optimize" throws seemingly good initial alignments out of whack, and obviously misaligned.

It appears best course of action is to manually link in app, skipping "optimize", going straight to "create link".

Anyone have similar experiences/thoughts on this?

Thanks!



Sent from my SM-N950U using Tapatalk

We've done quite a few flat non-geometric scans with the RTC. It doesn't do well with NO visually adjusted scans when there aren't any definitive geometric shapes/surfaces to help the cloud to cloud.
We did one day of the new Firmware, however, your Cloud to cloud registration (how Field 360 works)- works excellent when there are taller vertical objects to help the cloud to cloud. Poles ,towers, steel skeleton structures with small surface areas make it difficult.
I just visually got it close both vertically and horizontal and then CREATED a LINK. Get that tight C2C by editing the link in Register 360. That's our workflow. We don't have Cyclone Register

[Jonny5isAlive]

Thanks for your reply.

Are you skipping "optimize" as well?

Have you experienced "optimize" throwing fairly well placed scans out of alignment?

Again, yes this does match your scenario where there are minimal vertical geometric services available in the scene.

Sent from my SM-N950U using Tapatalk

[Scan-Ninja]

It is never recommended to try to do cloud to cloud (That's what registrer 360 field is try to do) for roadway type projects. Use targets, don't try to link out in the field. Bring the data in, use targets, then cloud to cloud.

[ericguizzetti]

It is never recommended to try to do cloud to cloud (That's what registrer 360 field is try to do) for roadway type projects. Use targets, don't try to link out in the field. Bring the data in, use targets, then cloud to cloud.

Let's say that maybe someday you can Link target to target on the ipad???!!?!!?!?

When I scan horizontal with the RTC I just try to find as much geometry as possible. You can always make your own as well.

[gsisman]

It is never recommended to try to do cloud to cloud (That's what registrer 360 field is try to do) for roadway type projects. Use targets, don't try to link out in the field. Bring the data in, use targets, then cloud to cloud.

Let's say that maybe someday you can Link target to target on the ipad???!!?!!?!?

When I scan horizontal with the RTC I just try to find as much geometry as possible. You can always make your own as well.

We have done successful cloud to cloud (at least initial C2C) in very flat areas it just isn't reliable without some vertical faces to allow you to visually see objects on the iPAD. Also the denser the scan the better. On one project I was going for far spread scans 70-80 feet and using high res mode so I could target using corners of overhead Light pole lamps in a large parking lot. This was a targetless job in some portions, but targets were necessary in any corridor without buildings in the scan perimeter