Unwanted conversion of Depth track from 'ft' to 'm'

[EvanBianco]

A user encountered this issue when loading an *.las file with units of 'ft'. Depth values were converted into metres, and no resampling was done. The 'units' of the depth track however was still in ft.

Suggestion: welly shouldn't convert ft to m or vice versa without people being prompted or passing in a keyword flag.

I thought we had dealt with this case, but we might need to make a test file to reproduce it.

[fahdi104]

Hi, seems like someone already reported is issue. I want to raise this again.

For temporary solution, is there anyway to access the depth index?

Also, some LAS may already be in TVD/TVDSS, but Welly always take MD/TVD when plotting. how about we specified the depth index simply as depth or time only?

thanks