OGR Table Properties - MapInfo_Pro - 2023

MapInfo Pro Help

Product type
Software
Portfolio
Locate
Product family
MapInfo
Product
MapInfo > MapInfo Pro
Version
2023
Language
English
Product name
MapInfo Pro
Title
MapInfo Pro Help
First publish date
1985
Last updated
2023-09-12
Published on
2023-09-12T16:39:16.995549
  • Table version 2100
  • Custom table metadata tags
    • "\OGR\DatabasePath" -> Path to dataset relative to .tab
    • "\OGR\TableName" -> Name of table in dataset.
    • "\OGR\Driver" -> Driver used to open table.
    • "\OGR\ConvertUnsupportedObjects" -> Convert un-supported objects.
    • "\OGR\OpenOptions" -> Driver open options
    • "\OGR\LayerCreationOptions" -> Layer creation options for OGR driver.
    • "\OGR\DriverCreationOptions" -> Driver creation options for OGR driver.
    • "\OGR\NoFileTable" -> OGR table with this metadata links to a URL based dataset. Having this token will treat the DatabasePath as a URL. This tag is not added by MapInfo Pro and user need to add on their own.
  • Some OGR table do not support inbuilt styles therefore we have to use global table styles.
  • OGR tables do not always have sequential data; there may be empty rows, rows that start after one (1), and gaps in row IDs. This must be taken into consideration when using MapBasic operations to fetch data from OGR tables. Do not perform operations on OGR tables using rowid.
  • Some OGR format like GML, DXF, GeoJson, TopoJson, CSV etc are slow when used directly. For these formats it's advisable to convert the table into MapInfo Table first.
  • For OGR formats which are sequential, its recommended to turn on caching of objects.
  • When converting OGR table into Native/NativeX commit table statement will always run in background.
  • OGR table does not support create Map, drop Map, changing the table structure.
  • In case OGR table contains points in a column and user want to create points out of that column the either use the OGR options or a VRT table as described here (https://gdal.org/drivers/vector/vrt.html)
  • TableInfo(TAB_INFO_DOMINANT_OBJECT_TYPE) for some OGR table will return TAB_UNKNOWN_OBJECTS even in case of Mappable table. Like in case of CSV OGR table.
  • GDAL OGR does not support UTF-16 character encoding.
  • Formats like GML and DXF will always be saved in a MapInfo Tabe when opening via the UI, to overcome the issues in GDAL.