The idea would be to use the already existing column "LRUDs". My suggestion is not to create classical LRDUs from the Magic LRDUs feature selecting the 4 columuns. The idea is to define 4 splays as LRDUs. then LRDUs can be based on their actual length, azimut and inclinaison and match what the surveyor thought would be the best measurements to render the cave volume. I'm sure this would improve the Volume display, primarily in side-way slanted galeries, as classical LRDUs only works well in tubic galeries or pits.
sounds like a good option. I guess this could be applied to "profile" as well as if all splays are displayed, the profile can be far away from the results we are looking for.
what do you think of my second option... pickable LRDU?
As you know, I do loads of splays to the point where LRUDs are pretty much meaningless to me. However, I still acquire LRUDs just after my station to station shoots, because they improve flagging a station change in a massive amount of data lines in case Topodroid missed an change of station (i.e. 3 similars shoots). I also acquire them to make sure I have the LRUDs I want in case I go for a simplified version of the volume. Splays acquisition strategy can be very different from LRUDs. I always have many splays that reach walls far beyond the next/previous stations or even several stations. This allow me to enhance the characterisation of the volume as well as ensuring that the data are consistent. By doing this, magic LRUDs become an awkward tool to use as it will use all the splays, and not only the one likely to be LRUDs.
I see 2 improvements that could be made:
1 - magic LRDUs only use splays within 4 cones (Left, Right, Up, Down) based on the LRUDs mode selected (0,1,2,3,-1,-2,-3) for its axis direction and a setting defining the cone angle (+/- 15-20° by default?). Any splays out of these cone volumes should be disregarded for LRDUs calculation. [[File:LRDUs1.png|none|auto]]
2 - add an option in the LRUDs mode column to define which splays to use as LRUDs (L,R,U,D). This could improve the volume rendering, as it would provide slope and direction to selected LRDUs. [[File:LRDUs3.png|none|auto]] [[File:LRDUs2.png|none|auto]]
Thanks for your inputs! I found the issue: the file had 2 caves with same ID... . Problem solved with paste issue as well. To avoid this to happen, maybe there should be a test on cave ID uniqueness when entering or editing the cave ID.
looks like there is an issue with data paste. When pasting the data (after copy or cut), the line are inserted at the very top of the table instead of below the selected line.
It appears that Excel reimport does seems to work anymore. Changes made in Excel are not reimported although the changes have been saved and I have checked the CaveRenderPro.xls... changes are actually there.
Thanks for implementing this feature. This is great... really! I love it!
As a reminder for everyone, you can become an editor for OpenStreetMap project - OpenTopoMap being a layout of OSM - and that will give you the ability to improve the maps in your caving area(s)... obviously following OSM editor rules, but this is powerful :)
I have one issue but I guess this is because of my (very) low speed Internet... still hook up to the very end of an ADSL line here (they swear : optic fiber is coming... soon!). Anyway, I struggle to get the tiles downloaded.
Also, here is a few extra things that would be great to add if possible : - Graphical scale - UTM grid - True North arrow - Copyright feature for the survey data. Maybe this could be added in Settings: text box to let the user defines what the data/drawing copyright is.
That was it. Last update installation seems to have wiped out username, password together with setting max lines value back to default (500). I normaly have it set to 1500. Problem solved
A new auto-adjustment issue appeared with v10.4.1. same symptom as before: some caves are adjusted... my big one isn't anymore. I have tried removing the double branches from the ref point, but it doesn't change anything, so it doesn't look like the previous issue. Removing the refcave links doesn't change anything either.
no, the "jump" I see is when in visualizaion tab the filter is active, and I go in drawings tab then the shots and splays are shifted. It is obvious if you look the bottom right part of the survey in the following screenshots:
Drawings tab, no filter enabled. [[File:Capture d?e?cran 2024-01-27 a? 10.01.54.jpg]]
Drawing tab, filter still enabled in Vizualization but not in Drawings tab... drawings and shots/splays don't match anymore. [[File:Capture d?e?cran 2024-01-27 a? 10.04.37.jpg]]
Filtering in Vizualization tab should'nt affect filtering in Drawings.
I guess the issue lies within the adjustment. It looks like in vizualisation tab, adjustment in only applied to the filtered data, right? But in drawings, adjustement is applied to all data. However, when filtering is enabled in Vizualisation, then it looks like the adjustment in Drawings tab only apply to whaterever is filtered in Vizualisation tab.... make sense?
In CRP, when a shot has RefPassage/RefStation = Passage/Station, then it is considered as a Ref point (=entrance or a junction station between 2 caves if you have filled in the RefCave column) if 1.0 is inside the cave, you should name it 1.0x 1.0 otherwise CRP will consider the station as the entrance. and to have your entrance placed at the actual location defined in the bottom right box (lat/long/alt), let's say it is station 1.5, you'll need to have a line with 1.5 1.5. Attached an example of a survey done from the end of a cave to the entrance. [[File:Capture d?e?cran 2024-01-22 a? 14.20.55.jpg|none|auto]]
Sorry, I don't speak/write/read German... so it will be English or French (Google Translate is our best friend).
I have edited your file so it should be OK but I recommend you do it again for training 🙂
It might be misleading but in the information box "Hohlendaten", as the "Deklinaiton" and "Änderung" are not used in any calculation. After filling the "Datum", the "Deklinaiton" and "Änderung" are given but only for information (and only if you are connected to Internet) . This feature will only help you finding the correct declination data for a specific date, that's all. As I mentioned on the forum, you have to define the survey instrument :
Go to Datei tab > Geräte > right click > Neu. Then fill the new line in with required data (device ID (your choice but as to be numerical), device name, date, declination, variation, etc.)
I have set the Geräte based on the 1st of January of each year. But you could enter any date, as long as the data are correct for that date.
Then in Daten tab, in you have to fill the Gerät column with the correct device IDs. To make this quick, select the lines using the same "Gerät" ID - lines should be highlighted - then in Werte box (top), in Spalte dropdown menu select Gerät, then in the box to the right type de GerÄt ID and click "Ersetzen". Done... then you can do the other line.
I have used the year as device ID... simple and easy 🙂
Presuming this isn't a software issue (I might be wrong), could it be because you only defined one Instrument for the entire data set? e.g. applying magnetic variation to 2020 data based on 1989 magnetic declinaison + magnetic variation would not be right as magnetic variation doesn't apply for a too long period of time.
To avoid this I define an Instrument for every year. [[File:Capture d?e?cran 2024-01-19 a? 11.50.17.jpg]]
In the data table, I assign to the data the "Instrument of the year". [[File:Capture d?e?cran 2024-01-19 a? 11.51.26.jpg]]
I noticed a bug with filtering and adjustement (maybe?)
0 - Select cave with loops (maybe you can use my file, cave 01/001) 1 - go to Visualization tab. Make sure no Filtering type is selected in the filter dropdown list 2 - go to Drawings tab (Plan mode), no Filtering applied, and check how the drawing fits or not the splays displayed. 3 - go back to Visualization. apply Filter with Passage (e.g. 20220726,20220725,20230403) 4 - go back to Drawings (Plan mode), no Filtering applied, and check how the drawing fits or not the splays displayed.