Hi @nfored,
I’m not really sure what you’re asking about here, so please clarify if my response doesn’t answer your question.
When using the Ping360 for navigation it’s most common to do 360° scanning, in which case Ping Viewer’s heading integration can get the compass direction from the vehicle telemetry, and use that to auto-rotate the plot so previously scanned directions are maintained (note: this does not consider vehicle translations). You can see that in action here.
Regardless of the sector angle, moving the vehicle while scanning will cause some physical overlap with existing pings or gaps where pings would have occurred if the sonar had been stationary, and there is currently no attempt to compensate for that in terms of how the scanning is done.
When not making use of heading integration, turning the vehicle with the scan direction results in scans that correspond to physically larger angles between ping transducer angles, whereas turning against the scan direction results in pings being squished together into a smaller angular range. Artefacts from these effects (and those from vehicle translations) are exacerbated by fast vehicle movements, long scan ranges, and high angular resolutions, whereas moving the vehicle slowly and scanning a short range results in scans that more closely match what the sonar is intending to scan.