Welcome to our new forum platform. We realize there is still some work to do and we appreciate your patience. Please let us know if you have any ideas or suggestions: firstname.lastname@example.org
Problem with DWG in Global Mapper 13
I have a problem with a couple of DWG building drawings that I have got from a customer. When opening them in Autodesks own application DWG TrueView 2012 they look fine in wireframe as well as in the shaded or "realistic" view modes.
This is reported by DWG TrueView 2012 when loading:
Opening an AutoCAD 2004 format file.
Autodesk DWG. This file is a TrustedDWG last saved by an Autodesk application
or Autodesk licensed application.
When I load the same files into Global Mapper v13.00 (b101711), the 3D wire frame looks OK. The 3D view toolbar button "Wireframe View" is however stuck in wireframe mode. If I push it it just returns to non-pushed state. I can't get a solid view in 3D. This is a minor problem. The major issue I have is when trying to create an elevation grid from the DWG. For some of the files I get a crash in Global Mapper if "Use 3D Line Features as Constraints (i.e. Breaklines)" is checked. Regardless of settings on the tab "Grid Options" I get very strange looking grids. It looks like the wrong vertices have been connected. E.g. buildings with a flat roof will have what looks like a lot of "needles" going from the bottom to the top instead of a flat roof. Also other parts of the buildings are distorted. I have tried different settings for "No data distance criteria" but I can't get a correct elevation grid for the building. I have studied the generated elevation grid both in Global mapper 3D view and in our own application after having exported the elevation grid as GRIDASCII and then imported it into our own application. The resulting elevation grid looks identical in Global mapper and in our own application so I suspect the grid creation algorithm in Global Mapper messes things up.
I have attached a pdf with screen dumps showing the error.
I have tested both the 32-bit and 64-bit versions of Global mapper with the same result.
Is there a setting I have missed or is this a bug?