It seems like the stability issue is fixed, no more erratic changes, but there's a new issue: My gml contours files are definitely created with UTM coordinates, however, when I select UTM Grid mode, contours and caves are far apart. When I select Geographic, then contours and caves are together. It looks like there's a mix up between UTM Grid and Geographic modes somewhere in the code.
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.
Calculation of path length: Thanks! Do you think it would be possible to highlight the path calculated? in complex network it can be interesting to see what is actually the calculated path.
The new depth and height filters work fine, thanks.
A couple of suggestions - why not having both depth and height as one filter with e.g: 100/-50 ? - filtering by altitude could be also interesting for multi-caves.
The french translation "profondeur"/"hauteur" sounds a bit awkward to me. "hauteur" isn't clear in this context. I suggest to use the combo "dénivelé négative" for depth / "dénivelés positive" for height and if you merge both depth and height in one filter "dénivelé".
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.
Levels: level plan mode vs level section mode. Would it be possible to divide "Level" in 2 columns, levels can be useful for overlaying areas, but the horizontal overlap vs. vertical overlap doesn't follow the same logic (top to bottom vs foreground to background). It would be very helpful to be able to set and filter levels for both types of view (plan vs sections)? maybe Level_Horiz. and Level_Vert.
Filters: when you have numerous spalys, having all that information at one can make make the interpretation difficult (too much info at once) Here is a couple of extra filters than could be helpful: - Filters by Station. When you have numerous splays, it can make life easier to - Filters by Z with +/- range... this would only display splays within a depth range and would allow to focus on specific area. That could help in drawing details.
Elements: Water: brook and streams should have a dashed option. sometime the water disappear in a narrow passage and it is not possible to survey but we're able to guess a water path... this should be dashed.
Data: New automated fields: It could interesting to have a columns with calculated path length from entrance, total negative and positive elevation from entrance (i.e. addition of all negative elevation difference between stations and addition of all positive elevation difference between stations along the caver path). Material filter: Only display rows with Material filled in. That would provide a quick summary/table of the equipment required. This should be displayed with columns Supplementary and the above suggestion
Would it be possible to freeze columns Cave, Ref Passage, Ref Station, Passage, Station? This would improve horizontal scrolling experience... and not getting lost in the dable :)
That's what I've done so far... screenshot in Google map mode with the survey shots displayed then dragged it to the approximate position. Aren't the drawing features referenced in UTMxx?
My user story... I'd like to be able to overlay surface contours with the cave, to highlight the relation between surface and cave(s) in plan mode: proximity with the surface or crossing through a mountain, valley and riverbeds... as well as the topographic relief for cave access. Ideally it should be exportable as a drawing layer (like we can with surevy shoots).
It would be nice to be able to display the satellite images while drawing in plan mode as we can do for sketches... it would help drawing surface features that could be interesting.
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.
I noticed an annoying bug with the cave ref point jumping from UTM ref to Geographical ref (X=0, Y=0) without changing the projection type.
I use UTM and seal level as regular settings. I have some contours imported and displayed in perspective mode.
I managed to reproduced the error and here is the routine that should help you tracking some of the weird behavior:
First ensure Plan mode is selected in Visualisation. then Data> Calculate and go back to Visualisation/Plan mode. you can check the cave position using the grid in Drawings... it should be the correct UTM position. Then select Perspective mode, everything should still be ok and the coutours in the right place. Then go to Data and straight back to Visualisation. The cave position has then jumped to 0,0,0... but not the contours position nor the projection type (still UTM) To get it back to the right position: in visualisation select Plan mode, go to Data > Calculate, then back to Visualisation, then select Perspective.
Is it possible to add a doted line? It's not part of the UIS symbols... however I miss it as UIS drawing standard uses dashed lines for to many features and the plans can get unclear.
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: [[File:Capture d?e?cran 2021-08-03 a? 23.58.44.jpg|none|auto]]
This is the section after import [[File:Capture d?e?cran 2021-08-03 a? 23.58.25.jpg|none|auto]]
This is the section after I changed manually the backsight shot direction [[File:Capture d?e?cran 2021-08-04 a? 00.04.32.jpg]]
This is the section after I changed the backsight shot direction using the "Replace" feature : Direction <-> [[File:Capture d?e?cran 2021-08-04 a? 00.03.19.jpg]]
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.)