VERIFIED SOLUTION i

How to understand features of the MapInfo Pro 16.0.3 patch

Products affected: MapInfo Pro™
On Feb. 27, 2018, PB released the MapInfo Pro 16.0.3 patch here.

From the Release Notes:

This release provides the following new and updated features.


MapInfo Pro

GDA 2020 Support

• Geocentric Datum of Australia (GDA 2020 Datum) #1028 was added in MapInfoPro 16.0.3.

• NTv2 conversion is available for use as preferred method in version 16.0.3 and later.

• Two new grid shift files are installed: GDA94_GDA2020_conformal.gsb and

GDA94_GDA2020_conformal_and_distortion.gsb to support NTv2 conversions for supporting

GDA 2020 Datum.

• MIF\MID and *.WOR files will be versioned 15.0.3 and higher if datum #1028 is used.

• Users of MIPro 15.x will be able to use a custom datum definition based on 7-parameter similarity

transformation published by ICSM.

• NTv2 Transformations will NOT be available for use with MapInfoPro 15.0.3.

For more information, the GDA 2020 technical manual can be found here:

The projection entries below can be added to mapinfow.prj file for use with MapInfo Pro 15.x to support GDA 2020 datum:

For Longitude Latitude systems:

"Longitude / Latitude (Australia GDA 2020)", 1, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0


For Map Grid of Australia:

"--- Map Grid of Australia 2020 (MGA2020) ---"

"MGA2020 Zone 47", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 99, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 48", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 105, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 49", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 111, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 50", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 117, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 51", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 123, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 52", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 129, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 53", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 135, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 54", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 141, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 55", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 147, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 56", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 153, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 57", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 159, 0, 0.9996, 500000, 10000000

"MGA2020 Zone 58", 8, 9999, 0, -0.06155, 0.01087, 0.04019, 0.0394924, 0.0327221, 0.0328979, 0.009994, 0, 7, 165, 0, 0.9996, 500000, 10000000


MapBasic

Changes to Create Text statement

Create Text

[ Into { Window window_id | Variable var_name } ] text_string( x1, y1 ) [ ( x2, y2 ) ][ Font... ]

[ Label Line { Simple | Arrow } ( label_x, label_y ) Pen (pen_expr) ]

[ Spacing { 1.0 | 1.5 | 2.0 } ]

[ Justify { Left | Center | Right } ][ Angle text_angle ]

[ Pen .... ] [ Brush ... ] [ Priority n ] [ Name framename ]

The (x2,y2) coordinates are now optional. (x2, y2) specifies the opposite corner of the rectangular

area which the text will fill. This coordinate is still necessary when creating text in a Map window,

but is optional when creating text in a Layout Designer window.

The x1, y1, x2, and y2 arguments define a rectangular area. When you create text in a Map window, the text fills the rectangular area, which controls the text height; the point size specified in the Font clause is ignored. On a Layout Designer, the (x2, y2) coordinate is optional.
When it is not included,
the text frame created will be sized to fit the extents of the text based on the Font currently being applied. When the (x2, y2) coordinate is included, the text frame is sized based on the dimensions given by both coordinates.
The text may wrap if the size of the frame is too small, or may have extra
space if the size of the frame specified is larger than the extents of the text string.

Support for Legacy Win32 icons in Ribbon controls

You can now use the legacy icons from Win32 versions of MapInfo Professional. Icon resources can be identified using the define or number from Icons.def. A MapBasic example here is setting the icon for a RibonButtonControl to use the legacy Printer icon from Win32: call SetRbnBtnCtrlLargeIcon(button2, New_Uri("pack://legacyorigin:,,,/"& MI_ICON_PRINT & ";Large", 0))

Note: You cannot put Win32 legacy icons within a Gallery control in MapInfo Pro 16.0.3.

 

MapInfo Pro Advanced

MRT Changes

You will experience improved performance while working with MRT (Multi-resolution Tile) rasters.

We have introduced new optimized mode with Random Tile Iterator to optimize reading and writing

of MRT raster tiles. Now, we have also added support for MRT tiles which are not power of 2.

Version Compatibility

In version 16.0.3 the MRR file format has been changed in a way that limits its compatibility with

the previous versions. Consequently, some MRR format rasters created in MapInfo Pro version

16.0.3 may not load properly in previous versions.

Specifically, an MRR created with version 16.0.3 will be incompatible with previous versions if it

contains a classified field and that field applies compression. If the classified field is not compressed

then the MRR will be compatible.

However, an MRR format rasters that contain other field types do not have any compatibility issues.

Note: An MRR format rasters created with previous versions can be loaded into version 16.0.3.

 

UPDATED:  February 27, 2018