Problems in the Valid Elevation Range when altering elevation values of the Elevation Options window

Seti

Hi there,

There seems to be a bug in the Valid Elevation Range" box of the Elevation Options/Alter elevation values box. I am using the latest release of v23.0. The bug is actually double; let me show this in two steps, A and B:

A. The maximum valid elevation and the minimum valid elevation cannot be changed one after the other in order to customize the vertical scale. It seems that two new numbers need to be inserted at the same time before clicking "ok" or "Apply" to have the desired customized scale.

For instance, I have this default range:

Max 80 Min 1

1. I would like to change Min to 2. I do it and apply, this gives:

Max 80 Min 2

2. Now I find that it would be better in this case to change the max to 20. I put 20 as Max and get this:

Max 20 Min 1

3. Min was reset. Since I wanted still Min = 2, I update by entering again 2 for Min. I get this:

Min 2 Max 80

The correct Min is applied, but the correct Max is lost, I am back to the default value.

The only way to get Max 80 and Min 2 is to change them simultaneously, before applying.

B. These two numbers need to be new in their field. For instance, with the same dataset, I am at a stage where I have Min = 10 and Max = 30. If I want to have Min = 10 and Max = 31, I cannot just keep Min = 10 and enter Max = 31 instead of 30. If I do so, I get Max = 31 but the Min is reset to 1 (the default Min). If I want to get Min = 10 and Max = 31, I should for instance proceed this way:

0. (initial stage) Min 10 Max 30

1. I enter Min 9. No need to enter another Max since 30 will be automatically be reset to 80...

2. I enter Min 10 and Max 30

In addition to this, I also encountered a case where the default range was considered to be a customized range. I mean that when clicking on "Restore DEfault Evelvation Range", I got the latest customized range, and the default range could be obtained only by customizing the two Min and Max fields.... everything upside down!

Cheers, daniel

bmg_mike

Daniel,

Can you provide some sample data that demonstrates this? I have tried the workflow with a DEM and cannot reproduce the behavior. I have tried in both the latest 23.0.2 daily build and the 23.1.0 release.

I do the following:

1. Load DEM
2. Go to Alter Elevation Values tab of Options dialog for layer
3. Change Minimum Valid elevation to some value (larger than current minimum)
4. Press Apply
5. Change Maximum valid elevation to some value (smaller than current max but larger than current min)
6. Press Apply
7. The changes are applied as expect, with my Minimum not changing back when I change the maximum

Thanks,

Mike

Global Mapper Guru

Seti

VM_TEST_EPS_G_15.02.2022_eps1-80_No_average_on_slope_0.05deg-lat-lon.zip

Hi Mike,

thanks for trying. Yes it is what I am doing.

I have found this problem with the attached file. It was generated with Matlab.

daniel

bmg_mike

Hi Daniel,

I just tried with your data file and the behavior was fine for me there as well.

Could you perhaps record a short screen video of the behavior or send a couple of screenshots just to make sure there isn't some other unexpected setting I don't have checked? You can either zip it up and post here or email to mikec@bluemarblegeo.com .

Thanks,

Mike

bmg_mike

Or if you could load the file with the settings that you used, then save a workspace and provide the .gmw file that could ensure that I loaded it the same way that you did.

Seti

Mike,

Sharad5_test.zip

Attached is the gmw file. I just removed the other layers from the gmw file which I have been using, keeping the raster only. Many thanks for your help.

daniel

bmg_mike

Daniel,

I have tried with your data and still cannot reproduce an issue. I have attached a PDF with screenshots as I adjust the elevations. Perhaps you can see something there where you are doing a different process than I am.

[NOTE: I keep getting a 403 error trying to attach anything and have asked our IT about this. In the meantime, if you email me at mikec@bluemarblegeo.com I can help you there].

Thanks,

Mike

bmg_mike

Daniel,

Here is the PDF document describing my workflow. I think we have the 403 issue fixed.

Mike

AlterElevationValusIssue.pdf

Seti

Hi Mike,

I have Global Mapper installed at two different sites. I went to my other computer, downloaded the zip file which I sent you, unzipped it and run GM (same version). I did as you did, following the screenshots on the pdf file you sent. . I got the same result. And this is indeed the way I do. It looks fine but... In my next message I will attach a pdf file that illustrates what I am writing below (my connection is not good and I prefer to split). Would you try this:

• Open the gmw file again, and go to the Alter elevation values, you will get your second screenshot of your pdf file, with the elevation range (1.0,40.0)
• Instead of changing 1 to 2, just click on "Reset Default Elevation Range". The new values should be (1.0, 79.999603). This is what I get, which corresponds to the lowest and highest pixel values in the tif file.
• Click "Apply". What I get now is (40, 1.0). The default elevation range which is taken into account here is not the default range for the dataset, instead, it corresponds to saved user preferences.There is a first problem here.
• Now, let's continue to the next step; insert 2.0 as the min value, by replacing 1.0 by 2.0. Apply. 1.0 is changed to 2.0. But I also have 40 changed to 79.999603...
• Insert 40 instead of 79.999603. Apply. 40 is changed to 79.999603, but I also have 2.0 changed to 1.0 at the same time. We are back to the problem which I had mentioned in my first message.

There seems to be two problems: the one which I had mentioned first, and also the resetting to default values which reset to user preferences.

Seti

GM_Sharad5_test_screenshots.pdf

bmg_mike

Ah now I see the issue. It was the 'Restore Default Elevation Range' that I was missing and that was causing the issues.

I have fixed the problems now. Tomorrow's daily build of v23.1.x at https://www.bluemarblegeo.com/products/global-mapper-daily-builds.php will have this fixed.

Thanks,

Mike

Global Mapper Guru

Seti

Thanks Mike! I have downloaded the new build.

I am not yet sure how I can install it, my license is not recognized after installation because I normally need first to install the version I purchased from my local reseller, in another language, to be able to use the EN one. When it is solved I will check and confirm that the problem is solved on my side too. Have a nice week end!

daniel

Seti

It works, thanks Mike!

daniel