As mentioned in Using correct lastline, when set to True, GS_FIND_CORRECT_LASTLINE corrects elements of the output lastline, providing a good ZIP Code or close match on the soundex even if the address would not match or was non-existent.
The feature works when GS_FIND_ADDRCODE is True and the address does not match a candidate or when GS_FIND_Z_CODE is True and only last line information is input. The match codes returned are similar to Z and Ennn in that the first letter remains the same with the second digit changing.
|
Code |
Description |
|
|---|---|---|
|
Zh |
No address given, but verified the provided ZIP Code. |
|
|
h=0 |
No change in lastline. |
|
|
h=1 |
ZIP Code changed. |
|
|
h=2 |
City changed. |
|
|
h=3 |
City and ZIP Code changed. |
|
|
h=4 |
State changed. |
|
|
h=5 |
State and ZIP Code changed. |
|
|
h=6 |
State and City changed. |
|
|
h=7 |
State, City, and ZIP Code changed. |
|
|
h=8 |
ZIP + 4 changed. |
|
|
h=9 |
ZIP and ZIP + 4 changed. |
|
|
h=A |
City and ZIP + 4 changed. |
|
|
h=B |
City, ZIP, and ZIP + 4 changed. |
|
|
h=C |
State and ZIP + 4 changed. |
|
|
h=D |
State, ZIP, and ZIP + 4 changed. |
|
|
h=E |
State, City, and ZIP + 4 changed. |
|
|
Ehnn |
Indicates an error, or no match. This can occur when the address entered does not exist in the database, or the address is badly formed and cannot be parsed correctly. The second digit of the error code is a hex digit which details the changes that were made to the last line information to correct the lastline. The last two digits of an error code indicate which parts of an address the application could not match to the database. |
|
|
h=0 |
No change in lastline. |
|
|
h=1 |
ZIP Code changed. |
|
|
h=2 |
City changed. |
|
|
h=3 |
City and ZIP Code changed. |
|
|
h=4 |
State changed. |
|
|
h=5 |
State and ZIP Code changed. |
|
|
h=6 |
State and City changed. |
|
|
h=7 |
State, City, and ZIP Code changed. |
|
|
h=8 |
ZIP + 4 changed. |
|
|
h=9 |
ZIP and ZIP + 4 changed. |
|
|
h=A |
City and ZIP + 4 changed. |
|
|
h=B |
City, ZIP, and ZIP + 4 changed. |
|
|
h=C |
State and ZIP + 4 changed. |
|
|
h=D |
State, ZIP, and ZIP + 4 changed. |
|
|
h=E |
State, City, and ZIP + 4 changed. |
|
|
nn=00 |
No match made. |
|
|
nn=01 |
Low level error. |
|
|
nn=02 |
Could not find data file. |
|
|
nn=03 |
Incorrect GSD file signature or version ID. |
|
|
nn=04 |
GSD file out of date. Only occurs in CASS mode. |
|
|
nn=10 |
No city and state or ZIP Code found. |
|
|
nn=11 |
Input ZIP not in the directory. |
|
|
nn=12 |
Input city not in the directory. |
|
|
nn=13 |
Input city not unique in the directory. |
|
|
nn=14 |
Out of licensed area. Only occurs if using Precisely licensing technology. |
|
|
nn=15 |
Record count is depleted and license has expired. |
|
|
nn=20 |
No matching streets found in directory. |
|
|
nn=21 |
No matching cross streets for an intersection match. |
|
|
nn=22 |
No matching segments. |
|
|
nn=23 |
Unresolved match. |
|
|
nn=24 |
No matching segments. (Same as 022.) |
|
|
nn=25 |
Too many possible cross streets for intersection matching. |
|
|
nn=26 |
No address found when attempting a multiline match. |
|
|
nn=27 |
Invalid directional attempted. |
|
|
nn=28 |
Record also matched EWS data, therefore the application denied the match. |
|
|
nn=29 |
No matching range, single street segment found |
|
|
nn=30 |
No matching range, multiple street segments found |