Read-Only Support for Spatial Objects in SQL Server with Z and M Values
Spatial data that is stored in SQL Server Spatial Geometry and Geography field types may have Z and M values. MapInfo Pro cannot edit this type of spatial data and ignores the Z and M values, so you must view these tables as read-only in MapInfo Pro. If you edit this type of spatial data in MapInfo Pro, saving the table back to the original SQL Server Spatial table does not preserve the original Z and M values.
The MapInfo_MapCatalog has the following spatial types for tables with Z and M values:
20 - Geometry read-only support of objects with Z/M values.
21 - Geography read-only support of objects with Z/M values
Supported SQL Server ODBC Data Types
These are the ODBC data types that MapInfo Pro supports:
- SQL_BIT
- SQL_TINYINT
- SQL_SMALLINT
- SQL_INTEGER:
- SQL_REAL
- SQL_BIGINT
- SQL_DECIMAL
- SQL_DOUBLE
- SQL_FLOAT
- SQL_NUMERIC
- SQL_BINARY
- SQL_LONGVARBINARY
- SQL_VARBINARY
- SQL_LONGVARCHAR
- SQL_DATE
- SQL_TYPE_DATE
- SQL_TIMESTAMP
- SQL_TYPE_TIMESTAMP
- SQL_TIME
- SQL_TYPE_TIME
- SQL_CHAR
- SQL_VARCHAR