Although the served version of MapInfo is installed, when MapInfo is run the dialog for activation asks for the serial number and access code as for a node-locked licence, instead of the licence server name and port number.

This issue is caused by registry keys in HKEY_USERS pointing to the node-locked licence that are conflicting with registry keys in HKEY_LOCAL_MACHINE pointing to the concurrent licence.

To fix this issue:

1. Ensure that if a node-locked licence was activated it has been transferred back to Pitney Bowes, then close MapInfo.
2. Open Registry Editor and go to Edit > Find and search for MINWES.
3. Back up the registry using File > Export.
4. Remove the folder in HKEY_USERS that contains this key for the affected version e.g. HKEY_USERS\{UserID}\Software\MapInfo\MapInfo\Professional\1250.
5. Run MapInfo to check it is now using the concurrent licence.

!table
!version 1000
!charset WindowsLatin1

Definition Table
  Type ODBC
begin_metadata
"\IsReadOnly" = "FALSE"
"\MapInfo" = ""
"\MapInfo\TableID" = "2e88f9e5-7d4c-4645-b824-4ef6b5102c9e"
"\DATALINK" = ""
"\DATALINK\Query" = "Select *  From ""myDatabase"".""dbo"".""myTableOrView"""
"\DATALINK\ConnectionString" = "Description=aDescription;DRIVER=SQL Server;SERVER=myServer;Trusted_Connection=Yes;APP=MapInfo Professional®;WSID=blah;DATABASE=myDatabase"
"\DATALINK\ToolKit" = "ODBC"
"\CACHE" = "OFF"
"\MBRSEARCH" = "ON"
end_metadata

In order to resolve this, MapInfo introduced a 1 mm accuracy projection, which can be found under Projection... when you create a table or save a copy of an existing table. However, this is not a default option, so even when saving a copy of data already in the 1 mm precision projection MapInfo will automatically default to the standard projection. This makes it very easy to accidentally reduce the quality of your data if you forget to actively select the 1 mm precision projection.

Fortunately there is a relatively simple way to ensure that MapInfo always defaults to the 1 mm projection:

• Navigate to the MapInfo folder under program files (e.g. C:\Program Files (x86)\MapInfo\Professional).
• Locate the MAPINFOW.PRJ file.
• Backup the MAPINFOW.PRJ file, in case you make a mistake.
• Open the MAPINFOW.PRJ file in a text editor (e.g. notepad).
• Search for ‘British’, which will find a section of text that looks like this:

"--- British Coordinate Systems ---"
"British National Grid\p27700", 8, 79, 7, -2, 49, 0.9996012717, 400000, -100000
"British National Grid (1 mm accuracy)", 2008, 79, 7, -2, 49,0.9996012717, 400000, -100000, 0, 0, 2000000, 2000000
"British OSGRS80 Grid", 8, 33, 7, -2, 49, 0.9996012717, 400000, -100000

• Move the third line of this text up one so that it becomes the second:

"--- British Coordinate Systems ---"
"British National Grid (1 mm accuracy)", 2008, 79, 7, -2, 49,0.9996012717, 400000, -100000, 0, 0, 2000000, 2000000
"British National Grid\p27700", 8, 79, 7, -2, 49, 0.9996012717, 400000, -100000
"British OSGRS80 Grid", 8, 33, 7, -2, 49, 0.9996012717, 400000, -100000

This change moves the 1 mm accuracy projection to the top of the Category Members selector under the British Coordinate Systems Category in the Choose Projection dialogue box of MapInfo, automatically making it the default option (as shown in the picture). If you want to use the standard projection then you just need to select 'British National Grid [EPSG: 27700]' from the dialogue instead.

This typically occurs when an Administrator installs MapInfo Professional and then logs off the machine without running the program at least once (it is the first run as admin that installs these files). The easiest solution is to have the user go to the MapInfo\Professional\AddUser folder (for example C:\Program Files (x86)\MapInfo\Professional\AddUser) and run the "MapInfo Professional User.msi" file found there and then re-start MapInfo Professional.

• If you have our ArcGIS Maplink product (or ArcSquirrel) then loading data in using this into a temporary SQL table is probably best as it will do a reasonable amount of checking.
• MapInfo has its own SQL loader tool ("Easy Loader" - find it in the Tool Manager)
• If you are just using open source you can use OGR2OGR

ogr2ogr -overwrite -f "MSSQLSpatial" "MSSQL:server=MyServer;database=MyDatabase;Trusted_Connection=yes;" "C:\Temp\MyShapeFile.shp" -a_srs "EPSG:27700"

Once the data is in SQL there can still be issues:

Incorrect SRID

• Make sure you specified the correct SRID when the data was loaded (if you didn’t specify it – it may well be 0). You can check this with the SQL: SELECT geom.STSrid from SitesGeom Where geom.STSrid <> 27700

Invalid ring

• You may also have invalid ring geometries – a good post on this is http://blogs.msdn.com/b/edkatibah/archive/2008/08/19/working-with-invalid-data-and-the-sql-server-2008-geography-data-type-part-1b.aspx but the key SQL command is:

UPDATE foo SET geom = geom.STUnion(geom.STStartPoint());

Invalid geometries

UPDATE foo SET geom = geom.MakeValid()

SRID not imported

Import geometry data into temp SQL table (e.g. foo) – with tempGeom column

Then try to populate a geometry column from the WKB of the validated column:

ALTER TABLE foo ADD geomFinal geometry;

SET geomFinal = geometry::STGeomFromWKB(geomTemp.STAsBinary(), 27700)

http://www.ordnancesurvey.co.uk/oswebsite/products/geo-referencing.html

These are available as *.tfw "world files" for ArcGIS^®, or *.tab files for MapInfo Professional^®

We have written a custom MapBasic app for this purpose: for ESDM staff this is located in 3rdPartyApps\TABs_from_ECW [this being a pretty dumb place for it, as it is not a 3rdPartyApp, Ed]. Instructions are in the text file in the zip.

If you are not Exegesis staff, and find yourself in this situation, please contact us for help.

We have written a custom MapBasic app for this purpose: this is located in 3rdPartyApps\TABs_from_ECW.

Instructions are in the text file in the zip.

If you are not exeGesIS staff, and find yourself in this situation, please contact us for help.