Elevations in map catalog

Ice Age Mark

Mike,


When I'm exporting GMTED2010 tiles to .gmg format to use in a map catalog, GM prompts me to save in "deci"-units to avoid terracing because the .gmg stores elevations as whole integers. But when I load these files into a map catalog and open it, GM seems to interpret those elevations as whole units, giving an incorrect display. When I export in whole meters, everything is fine. This also brings up a spin-off question. At what resolution do I need to worry about "terracing" and exporting in "deci"-units? (This stuff is only at 7.5 second resolution.) Is something wrong with the map catalog interpreting elevation units, or should I just be exporting as whole elevation units except for very flat, or very high resolution, elevation data? [V 14.1 B011813]


Thanks,


Mark

global_mapper

Mark,

You are just seeing a bug in that particular build as I was updating the map catalogs to support Lidar and messed up the vertical units. So you'll want to use deci- or centi-units if your terrain has that much vertical resolution. A new build will fix the other issue. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper14.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v14.xx installation folder to give it a try. If you are using the 64-bit v14 version there is a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper14_64bit.zip .

Thanks,

Mike
Global Mapper Guru
gmsupport@bluemarblegeo.com
http://www.bluemarblegeo.com/