Hi Jochen, in Perspective/orthogonal projection, I noticed that sometimes there is a slight offset between the annonced inclinaison angle and the actual display. I haven't been able to reproduced how I get this offset but it does happen from time to time. [[File:Screenshot 2025-05-26 114235.png|none|auto]]
I'm asking again just in case it would be now possible with newer version of java package... Could we now get the splays colored using colorscale from Z coulor at station altitude to Z coulour at the end of splay altitude. Still looking forward for improvement... if it is still not possible, then so be it... till mext time :)
Hi Jochen, Did you had a chance to look further into this? I think one filter feature should be enough instead of the existing 2: Visualization & Drawings. It would improve the experience to have only one filter feature to deal with. At the moment, the most efficient filter is in my opinion the Visualization one (full colorscale span applied to filtered shots).
You can export to drawing layer the followings : - The survey shoots and stations (but no LRDUs, Volumes or Splays), - Cave title - Stations NUMBER, DEPTH, TITLE, INFO, MATERIAL and TASKS (but not the ones assigned to splays) - Survey shoot colour (as defined in Layout e.g. depth, adjustment, surveyor)
In order to do this 1 - In Layout, select what and how you want to display 2 - In Drawings tab : create a new/blank layer (Drawings). This is to avoid mixing them with your own drawings. 3 - In Drawings tab : in Survey shots, enable "Display", then click on the "Transfer" icon right next to it.
You should get a prompt to confirm you really want to do this... and that should be it...
Definitly better than it was before but one problem remains. I draw sinter pool with wavy line, and if a wave has a slightly "sharp" angle, then the dashed line behaviour isn't good and give stranger render : the dashed line crosses the plain line. Same behaviour is observered with entrance double-line and show clearly the issue. [[File:Screenshot 2025-04-13 181747.png|none|auto]] Is there something that can be done to prevent this? using a buffer instead of an offset?
Hi Jochen, I find the sinter pool double line doesn't give a very good result. In my opinion: - the separation between the plaine line and the dashed line is far to wide - the dash length and inter-dash space are too large. - the dashes are not a dashed line but tangent dash to the plain line, which produces ugly results with bending lines
Attached some examples in red = sinter pool double line. in black = plain line + 1/2 dashed line which is better but still improvable using 1/4 dashed line I guess. [[File:Screenshot 2025-04-01 191032.png|none|auto]]
Do you mean keeping only the filter feature in Visualisation to set filtering for every tabs (visualisation, drawing, elements, etc) and get the colorscale applied to the filtered data? I think this would be a good idea.
Hi Jochen, this is primarily when Drawing/Elements that I need the altitude colorscale to be applied to the filtered data. With many splays, ti is a lot of data often overlaying and it would be very useful to have the colors scale always applied to the filtered/displayed data and not the whole set of data... that would be great! Surveying in Laos at the moment :)
Hi Jochen, I guess I mentioned this issue a while ago but still see the issue. When Data are filtered by level... or other mean of filtering, the full range of color (red to purple) isn't applied. instead a short range of color (i.e blue to green) is applied... this can be annoying as having the full colour scale help segregating data level.
Never used Sexytopo. However looking into the import format available into CRP, I see Sexytopo (*.txt). If this doesn't work maybe there is a bug that Jochen could fix. Otherwise, CRP can import Therion *.th files. And I'm sure Sexytopo exports survey to *.th format (you might find *th2 file but these are not survey data files).
Great news. You're right I forgot about the rotation. One of the differences between Geographic and UTM is that the vertical axis is the true north using Geographic mode vs grid north using UTM mode. The exact rotation from true north to UTM grid north is found in the Cave data frame (bottow left) in the box Meridian, but I think the rotation tool as steps of 1 degree. So you might have to adjust parts of your drawings after dragging them back in there new location.
Switching from Geographic to UTM is as simple as clicking on the UTM icon next to Geographic icon in the Calculate tab... This said, if you have done some Plan drawings while using Geographic "projection", you won't see them anymore when zooming onto your displayed data. There are not gone, but all your Plan drawings will found around X=0, Y=0 as the cave ref point in Geographic "projection" is X=0, Y=0... far away from your cave ref point in UTM coordinates. To bring your drawings to the correct UTM location, first under Drawings tab, enable the Grid display. You should now see the UTM grid and coordinates under the Elements tab. Zoom out until you have both X=0,Y=0 (where your Geographic drawings live) and your cave data displayed in the UTM projection on the same screen. Select all the drawing elements at once and drag them toward the UTM cave ref point. Zoom in and drag them again, closer to your data.... Do it again and again, until you can drag them to overlay nicely your survey data.
This would be the same "issue" if you decide to switch the depth ref Entrance/Sea level.
Jorchen, would it be possible to add Azimuth and Inclinaison as data provided with de Distance tool? This can be a very useful information when digging straight through the wall between two adjacent chambers.
I also had an error message when I tried to import CRP generated *.kml files into QGIS and this was caused by slight format issue. *.kml files output by CRP don't follow exactly the structure/format of a *.kml file generated by Google Earth. However, the generated *.kml files are readable by Google Earth, so a way around to correct any format issues is to open the file in Google Earth and save/overwrite the file from there. Then the format glitches should be corrected and you should have no issues importing your files in third part software/apps.