The new version of Global Mapper has been announced, in its 13 version for both 32 and 64 bits. Although this is a program that is questioned by its GIS capabilities, its simplicity which has made it very popular, especially by the management of three-dimensional models and ability to import and export between different formats.
There are many changes, I will try to summarize those that have caught my attention and which I consider to be significant, but for frequent users of the program there is much more.
- The most striking change is the support data sets of an ESRI Geodatabase. With this the program approaches an interesting niche, where ArcMap users have stored a good amount of data but are limited in having to buy extensions such as 3D Analyisis, which in turn to make a simple thing must be given Half turn of heating to the court. Using GlobalMapper 13, users could generate in seconds Digital models and return them back to the geodatabase without losing all the data analysis and construction capabilities in what ESRI does have more to offer.
- In the export has added the ability to send an ASTER DEM to SRTM HGT format, which although it is a conventional raw format, Americans use it a lot for its potential before the indexing of quadrants. Additionally you can already export to .00t format of Vulcan 3D TIN.
- To add to the many formats already supported by Global Mapper, it has now included support for SegY format, a standard used in the geophysical area, also for LEM format, which is the DEM simulation used by the Japanese and NMGF used more in aeronautics.
- In the case of the export of images within a kmz file, it is now possible to specify the quality of the jpg, which will reduce the size to taste. It also now supports when the kmz brings .gif files
- You can export images to ERDAS .img format, popularized by ESRI users.
- In the case of DGN files, it has improved the fact that some polygons came unfilled after they could not interpret the multiple geometries that for a long time Microstation internally managed as shared cells. It also corrected the error that happened with some curves that smart They did not have much.
- When downloading layers served via WCS, now you have no problems if they are in a different projection than Google Earth (lat / long / WGS84)
- In the case of Open Street Maps XML files, they have improved the problem that was hanging when there was a lot of data. The same has happened with the clouds of Lidar LAS points (which are always many), where they have optimized the use of memory.
- For the export of DWG and DXF files, a problem that had been labels With more than 31 characters (go, these are no longer labels).
- Now supports geoPDF without previously reported limitations.
Improvements in analysis
- Union of tables. It can already be done join Between the tables of different layers by means of a common attribute, quite basic but incredibly did not exist.
- Copy and calculation of data in the tables. We have now created the ability to perform mathematical operations between the data of one column, to be stored in another as would be for example, the calculation of an area in different unit of measure by multiplying it by a factor; the same function also serves as a copy and paste between tables, since it is a multiplication operation per unit, which would generate the same value.
- In the handling of digital models, new surfaces can be generated from an existing one, specific points and even from attributes of a table associated to a surface. With this, more than one model can be stored within the same attribute table, without this meaning that they are two and facilitating operations like cut / fill without doing operations outside the same table.
- Now the data search, has the option to be made over the current view and not over the entire layer.
- You can synchronize a display so that the same area is seen in Google Earth, although you can not do it in reverse, similar to one of the 6 things that it does Microstation In this regard.
- In layer management, it is now possible with more interaction to move a raster layer to go transparent or behind a layer of vectors, something that until 12 versions was still old in the obsolete layers panel.
- In the case of data served online by Intermap, high resolution can now be obtained, since it no longer downloads the data as local but in a stream It refreshes as it zooms. In the case of loading NOAA data, you can download Geoid binary grid shift files.
- Many other enhancements will be seen along the way, especially with capabilities that have been given to the right mouse button and use of the keyboard both to build and edit data.
- In the case of GPS data with the NMEA protocol, the $ DPGGA statement option has been added.
Improvements in data construction
- There is significant improvement in this part, although it remains a great weakness. In this case, the management of Snaps, the Nearest Is now maintained in the editing layer as a priority in the presence of other layers or geometries not selected.
- Also, deflection-based polygons and polygon edges can now be built more easily by means of the 3 points method.
- Additionally a submenu in the line construction, when you have a selection of points, can suggest the creation of lines from the closest point, which would simplify the digitization of a traverse from points captured with a GPS.
- You can do transformations with something more agile, as is the case of moving a layer. It is usually a bad practice but useful when the geodetic precision is insignificant before the usefulness of the data, to give an example:
Many times we have a layer in NAD27 or PSAD 56 and to move it to WGS84 what we do is move it a known vector. It will not be the recommended practice, but to stick to existing data or when it does not affect the local context ... it's worth it.
- There is now a Datum called “NAD83”, apart from the “D_North_American_1983”, after ESRI in primitive versions of ArcView confused some of the sebum with the butter and made .prj files generated with archaic versions not compatible with this projection. Something similar happens to Microstation, when you want to believe that the NAD27 used by Gringos Americans in many parts of the continent was a symbol of initiation.
- Something similar they have done with a provisional Datum called South American Datum 1956 (PSAD56), to make compatible with errors with data generated in Mapinfo.
- Now, when importing generic data from an ASCII file, there is support for formats of degrees, minutes and seconds with decimal, as well as degrees and minutes with decimal (without seconds). Incredible as it may seem, it supports fractions, like instead of saying 0.25 using 1 / 4