Specify a numeric field (Geocode Options dialog box) in which MapInfo Pro will write a code indicating which steps were taken to geocode the record or why the record did not match. These codes can be very useful in catching "false positive" matches and in improving the "hit" rate by diagnosing problems and correcting them.
The return code is a three-digit number, with each digit indicating a particular aspect of the geocoding operation.
MapInfo Pro "scores" each record on each aspect and adds the three numbers together to get the result code for that record. For example, a result code of 122 means:
- The address was found in one other boundary: 100
- The exact address range was not found: 20
- Abbreviation file substitutions were made: 2
These tables indicate the significance of each element in the code.
|
<0 |
Not matched |
|
0 |
Not tried |
|
1 |
Exact match |
|
>1 |
Inexact match |
The return codes have been designed so that non-matches will have a negative value and matches will have a positive value. A record which has not been tried will have a return code of zero.
|
1 |
Exact match found |
|
2 |
Abbreviation file applied |
|
3 (-) |
Exact match not found |
|
4 (-) |
No street specified |
|
5 |
User picked a name from the list |
Codes indicating how MapInfo Pro has treated street names appear in the one's place of the result code.
|
00 |
Exact address range and side of street found |
|
10 |
Address range found, but could not determine side of street |
|
20 (+/-) |
Address range not found, but within minimum and maximum ranges |
|
30 (+/-) |
Address range not found, but beyond minimum and maximum ranges |
|
40 (+/-) |
Address range not specified, but matched to minimum range |
|
50 (-) |
Streets do not intersect |
|
60 (-) |
Signifies the row has no object |
|
70 |
User picked an address from the list |
Codes indicating how MapInfo Pro has treated address ranges appear in the ten's place of the result code.
| Refining-Boundary Codes | |
|---|---|
|
100 (+/-) |
Address range found in only one boundary other than specified boundary |
|
200 (-) |
Address range found in more than one boundary other than specified boundary |
|
300 (+/-) |
No boundary specified, but found in only one |
|
400 (-) |
No boundary specified, and found in more than one |
|
500 |
Exact street address found more than once in the specified boundary |
|
600 |
User picked a boundary from the list |
|
1000000 (+/-) |
User typed something new |
Codes indicating how MapInfo Pro has treated refining boundaries appear in the hundred's place of the result code.
Once you have result codes, you need to find out how your records were handled. You can use the following SQL Select statement to find out which result codes appeared in your table and how many records were returned with each code value:
|
Select columns |
Result_Code, count(*) |
|
from tables |
SomeData |
|
group by columns |
Result_Code |
The resulting query table will have a row for each different three-digit result code and a count of how many records had that code. You can then use Select or SQL Select to select all the records with a particular code. You can then browse these various selections and determine how to handle each class of records.
Examples of Geocoding Result Codes
675 User pick street name, address range, and boundary.
101 Exact match found in exactly one boundary other than boundary specified.