This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
thinkgeo.mapsuite.mapsuitegeocoder.dbfmatchingplugin [2015/09/22 08:31] admin |
thinkgeo.mapsuite.mapsuitegeocoder.dbfmatchingplugin [2017/03/16 21:59] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== ThinkGeo.MapSuite.MapSuiteGeocoder.DbfMatchingPlugin ====== | ====== ThinkGeo.MapSuite.MapSuiteGeocoder.DbfMatchingPlugin ====== | ||
+ | |||
+ | {{section>upgrade_map_suite_to_10.0}} | ||
+ | |||
This class encapsulates the matching operations in a DBF dataset. This class provides functions for creating and adding records and matching for DBF index files. The DBF file could contain one key column whose column name starts with "ID_" and additional columns whose column names start with "DT_". Each DBF file should also contain two columns named "BB_CX" and "BB_CY", which represent the longitude and latitude. If there is bounding box information, it should consist of four columns: "BB_ULX", "BB_ULY", "BB_LRX", "BB_LRY" representing upper left X, upper left Y, lower right X and lower right Y. To take advantange of binary searching, records should be sorted before insertion into the DBF file. | This class encapsulates the matching operations in a DBF dataset. This class provides functions for creating and adding records and matching for DBF index files. The DBF file could contain one key column whose column name starts with "ID_" and additional columns whose column names start with "DT_". Each DBF file should also contain two columns named "BB_CX" and "BB_CY", which represent the longitude and latitude. If there is bounding box information, it should consist of four columns: "BB_ULX", "BB_ULY", "BB_LRX", "BB_LRY" representing upper left X, upper left Y, lower right X and lower right Y. To take advantange of binary searching, records should be sorted before insertion into the DBF file. | ||
===== Inheritance Hierarchy ===== | ===== Inheritance Hierarchy ===== |