Global Mapper v26.0

Combine Terrain no longer outputs non-overlapping area

dominoc
dominoc Global Mapper User
edited November 2009 in Bug Report
Hi

In Global Mapper 10, when combining terrain files with unequal size, the output terrain file will include non-overlapping areas.
But in Global Mapper 11, when combining terrain files with unequal size, the output terrain file will only include overlapping areas.
Is this a bug? How do I get the old behavior back?

thanks

Comments

  • global_mapper
    global_mapper Administrator
    edited November 2009
    What type of combine operation are you doing (i.e. add, subtract, etc.)?

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • dominoc
    dominoc Global Mapper User
    edited November 2009
    I am doing a Maximum operation.
  • global_mapper
    global_mapper Administrator
    edited November 2009
    I took a look and was unable to reproduce your results. In addition, the combine source code hasn't changed since v10. When I combine with a maximum operation with two source files that only partially overlap, I get valid data in the results where either one or both of the source layers had data, not just where both are valid.

    I have placed a new build at http://www.globalmapper.com/global_mapper11.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v11.xx installation folder to give it a try. If you are using the 64-bit version, there is a new build available at http://www.globalmapper.com/global_mapper11_64bit.zip .

    If you still have trouble, can you provide the data that you are trying to combine so that I can check it?

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • tjhb
    tjhb Global Mapper User Trusted User
    edited November 2009
    I wonder what is new in that build, Mike, if you were unable to reproduce the problem.
  • global_mapper
    global_mapper Administrator
    edited November 2009
    There are numerous changes between the official v11.00 release and the new build. It's possible that a change was made to the terrain combining that got into a build that you have, but was backed out before it was checked in so it doesn't show up in the history. Since so many changes are made all the time I always first suggest getting the latest build before investigating further if I can't immediately reproduce the problem.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • dominoc
    dominoc Global Mapper User
    edited November 2009
    Hi Mike

    I have installed the latest build but it is still showing the same behavior. I have attached a zip file with some sample files and screenshots.

    thanks
  • global_mapper
    global_mapper Administrator
    edited November 2009
    Ah, I see the problem. What is happening is that the "All Loaded Data" option for a combine terrain operation now uses the intersection of the bounding boxes of the 2 layers being combined. If you need more than the intersection of the two layers just go to the Bounds tab when setting up the combine operation and choose the 'Global Projection' option. It should be filled in by default with the full bounds of all the loaded elevation layers.

    Let me know if I can be of further assistance.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com

Categories

In this Discussion