Latest Contributions by Sophie_Geldenhuis

Thanks Dan. I have also copied the response from MapInfo Support below.  "The engineers have provided a further update on the issue. They have advised the issue is being caused due to how MIPro versus ESRI stores values in SHP files versus TAB format. MIPRO uses an integer based coordinate system internally where basically the earth is divided into 2 billion discreet intervals (A Large integer value) between -360 and 360 degrees longitude.  This results in an internal default precision of about 4 inches. If you set bounds on the coordsys you are using you decrease the distance that area is divided by 2 billion intervals resulting in a higher internal precision that is capable of being brought down to millimeter level." ... View more

The shift is only small (under 10cms). It is happening with all data (ie client data, our own data and data pulled from external collection apps). I am comparing it to files with GDA 1994 MGA Zone 56 projection. I have been given a bounded coordsys within MapInfo. Otherwise I have not tried anything else.  ... View more