Hi Jochen,

I did a survey using regular shots and backsight shots. Importing data as csv from Topodroid gives the pair of shots as 2 different lines. I noticed this is causing some issues with Section view when using Auto adjustement. Even if both shots are defined with the same direction, the shot length and angle get skewed. I had to desactivate the backsight shots to be able to display the shots as expected.
Worth looking into this issue.

Cheers
Thomas

Yes I tried to set both shots to -1... and as far as I can tell it didn't work.
I'll get back to you with a sample as soon as I can... maybe next week.

I PM'd you a sample file. What is seen in Profile should be very close to what is seen in Section... but it is not close.
This is the profile:


This is the section after import


This is the section after I changed manually the backsight shot direction


This is the section after I changed the backsight shot direction using the "Replace" feature : Direction <->



I finally managed to get it as I wanted but this was with a lot of tweaking and it shouldn't be that complicated. I think backsight shots should be identified and marked as such and the combo regular and backsight shots should behave as one block (e.g. change of direction.)

Further more on the issue(s) caused by backshots not being identified as such: the cave length isn't correct as all backsight shots are counted.
CRP should identify backshots and deal properly with them.

Hi Jochen,
Thanks for all the recent implementations... unfortunately I’ve been away from home and computers for a while, and didn’t had a chance to test the latest versions. I let you know as soon as I can.

Hi Jochen,

I tested the shot/backsight shot import. As far as I can tell, it works as expected: the couples of shots seem to be identified and merged. However, I really don't like the fact that the raw data (i.e. shot and backsight shot) are processed and removed from the data table. I do backsight shots to be able to assess the quality of the shots and to reduce the error related to the DistoX calibration (e.g. difting) and/or magnetic errors. If the shot/backsight shot are merged during the import, then we loose the possibility to QC the data (in the table and in the views) and to decide wether the couple is OK to merge or to reject one of the 2 shots (if not both).

I'd rather see a solution identifying the backsight shot in the data table with linked behaviours (i.e. direction 1/-1, direction <->) and let the auto-adjustement merging the couples of shots.

Hi Jochen,

Are you planning to look into other options ?
If this is to stay like it is, can you please at least add a step in the import process to accept or reject the shot/backsight shot merging option? As it is, I'd rather deal with the regular/backsight shots couples in the table rather than loosing the raw data.

The painful method I have used to get things right :
Basic correction:
1 - Change direct shot direction using "Direction <->". this correctly set the splay direction as somehow the splays get the opposite direction they should get during the import (that was before the merging version).
2 - Manually revert the direct shot direction, so direct shot and splays directions are consistent.
3 - Set the backsight shot to the opposite direction as of the direct shot.

It gets a bit more complicated when I want to flip the overall direction...

an alternative would be to merge the shots and to keep both direct and backsight shot in the table but disabled. So it would be possible to run the QC check in CRP and decide what to keep...