Possible Surfer CLR Export bug.

ASheldon

Hi, When I create a custom shader, and save it out as a Surfer CLR file, and then initialize a new custom shader from this CLR file, the elevation values are wrong. Opening up the clr in a text editor shows this:

ColorMap 1 1
0.000000 255 255 255
1.999600 0 0 0
2.019596 255 255 255
3.999200 0 0 0
4.019196 255 255 255
5.998800 0 0 0

when it should have been this:

ColorMap 1 1
0.0 255 255 255
100.0 0 0 0
101.0 255 255 255
200.0 0 0 0
201.0 255 255 255
300.0 0 0 0

RGB colour values aren't affected, just the elevations.

any ideas?

ASheldon

.... On second thought, this may be related to a problem I've had previously importing csv files, with many digits (11+) in a value field, e.g 123.45600000, will read the decimal point incorrectly.. perhaps the surfer exporter cant cope with the 10 digits + 1 decimal point in the elevation value?

global_mapper

That is because the Surfer CLR format saves a percentage value rather than an absolute elevation value. You cannot retrieve elevation values from a Surfer CLR file.

Let me know if I can be of further assistance.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

ASheldon

Ah, interesting that would explain it, thankyou for your quick reply.

Then again, I've made a surfer file by hand as follows:

ColorMap 1 1
0.0 255 255 255
100.0 0 0 0
101.0 255 255 255
200.0 0 0 0
201.0 255 255 255
300.0 0 0 0
301.0 255 255 255
400.0 0 0 0
401.0 255 255 255
500.0 0 0 0
501.0 255 255 255
600.0 0 0 0
601.0 255 255 255
700.0 0 0 0
701.0 255 255 255
800.0 0 0 0
801.0 255 255 255
900.0 0 0 0
901.0 255 255 255
1000.0 0 0 0
1001.0 255 255 255
1100.0 0 0 0

and if i initialize a shader with this file, uncheck the 'scale shader to loaded elevation' box, and set the new elevation units to metres.... it loads the colours in at the correct level...

Anyway, thanks for your help.