You should add the feature to export isobath contours as an MBTILES output. This file is becoming the defacto standard for capable mobile device apps. You already have the capability to export side-scan to mbtile, why not contours as well?

Also, you should have an option to perform a "What you see is what you get (WYSIWYG)" colors export. First time I did an export of a KMZ file, I spent a ton of time honing the colors to exactly how I wanted them, using depth scale settings, etc. Then when I go to export, none of that mattered. I can get around it now by editing the exported KML code to get the exact color palette I want, but it shouldn't be necessary. Why have all the color palette options and depth scale configurations when they don't matter for exports?

MBTiles map image export is coming in the next major release.

Regarding your second point - that sounds strange. You should get WYSIWYG colours for KML/Z output. I'd be interested to see what you go instead, and how that relates to your RM map?

Great news on the MBTILE outputs, thank you! I will try to follow-up with exactly what I mean about WYSIWYG differences.

Example of WYSIWG differences. What you see in RM for color selections. What you see in the Google Earth Preset Style Vector output. Seems the preset style GE Shaded Relief comes out correctly.

Thanks - I understand the problem now. This is indeed a problem within RM, where the specified depth range is not being applied to the SR.

Just to reiterate (since you said SR in your last post), the GE Shaded Relief preset does come out correctly. It is the GE Vector preset that does not work as expected. Thanks!

Any chance this will be fixed in the next maintenance release? i'm kind of on hold until this gets fixed, because I rely on the preset vector output files as inputs to the next step in my process. Thanks for any info.