[b][/b]
[i][/i]
[u][/u]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
haenseln
verwirrt
ausruf
augen verdrehen
verrueckter teufel
boese oder sehr veraergert
weinend oder sehr traurig
verlegen
pfeil
veraergert
lachend
fetzig
erschuettert
idee
ueberrascht
traurig
zwinkern
laecheln
Uebergluecklich
neutral
mr. green
computerfreak
extremer computerfreak
frage
smile2
spook
alien
zunge
rose
shy
clown
devil
death
sick
heart
frage
blush
frown
crazy
hmm
laugh
mund
oh
rolling_eyes
oh2
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
Droniste
Beiträge: 148 | Zuletzt Online: 22.10.2021
Name
Thomas
Homepage
Wohnort
Toulouse, France
Registriert am:
30.03.2020
Geschlecht
männlich
    • Droniste hat einen neuen Beitrag "coordinates system stability issue" geschrieben. 18.10.2021

      Did you manage to reproduce this issue?

    • Droniste hat einen neuen Beitrag "Backsight shoot, Section view and Auto-adjust." geschrieben. 18.10.2021

      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.

    • Droniste hat einen neuen Beitrag "Some suggestions for improvement" geschrieben. 18.10.2021

      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.

    • Droniste hat einen neuen Beitrag "Some suggestions for improvement" geschrieben. 18.10.2021

      dashed water lines: great thanks!

    • Droniste hat einen neuen Beitrag "Some suggestions for improvement" geschrieben. 18.10.2021

      Filter by ID is a good idea.
      Would it be possible to add the ID# in the bottom information toolbar?

    • Droniste hat einen neuen Beitrag "Some suggestions for improvement" geschrieben. 18.10.2021

      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é".

    • Droniste hat einen neuen Beitrag "Backsight shoot, Section view and Auto-adjust." geschrieben. 10.10.2021

      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.

    • Droniste hat einen neuen Beitrag "Google map layer when drawing" geschrieben. 31.08.2021

      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?

    • Droniste hat einen neuen Beitrag "Importing elevation line as DEM in CRP." geschrieben. 31.08.2021

      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).

    • Droniste hat einen neuen Beitrag "display problem: Survey shots and splays are not overlayed correctly " geschrieben. 04.08.2021

      I think this is a very good option to enhance the Volume mode, but it would be great to solve the overlapping issue in all other modes.

    • Droniste hat einen neuen Beitrag "Backsight shoot, Section view and Auto-adjust." geschrieben. 04.08.2021

      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.)

Empfänger
Droniste
Betreff:


Text:
{[userbook_noactive]}


Xobor Forum Software © Xobor
Datenschutz