Matching to the Landmark Auxiliary file - GeoTAX_Premium - 7 - 7.7

GeoTAX Premium for Windows, UNIX/Linux, and z/OS

Product type
Software
Portfolio
Verify
Product family
Geo Addressing
Product
GeoTAX Premium
Version
7.7
Language
English
Product name
GeoTAX Premium
Title
GeoTAX Premium for Windows, UNIX/Linux, and z/OS
Copyright
2023
First publish date
1998
ft:lastEdition
2023-10-19
ft:lastPublication
2023-10-19T16:49:54.924301

This section provides information on the matching performed by GeoTAX to the Landmark Auxiliary file, and contains the following topics:

Matching overview

GeoTAX performs the following steps when matching an input address to a Landmark Auxiliary file.

  1. GeoTAX determines if there is a Landmark Auxiliary file present. If more than one Landmark Auxiliary file is present, GeoTAX attempts to match against the first file. GeoTAX ignores any additional Landmark Auxiliary files for matching, regardless if GeoTAX found a match to the first auxiliary file.

    Note: If a record within the Landmark Auxiliary files is invalid, GeoTAX returns a message indicating the auxiliary file has an invalid record. GeoTAX continues to process input addresses against the Landmark Auxiliary file, but will not match to the invalid auxiliary file record.

  2. If the Landmark Auxiliary file is present, GeoTAX first attempts to match to it. If more than one type of auxiliary file is present, the search order is:

    • Landmark Auxiliary file

    • User Auxiliary file

    • State-supplied file

    • GeoTAX Auxiliary file

    Note: GeoTAX only matches your input address to your Landmark Auxiliary file if there is an exact match. Therefore, your input address list should be as clean as possible; free of misspellings and incomplete addresses.
  3. If GeoTAX finds an exact record match to the Landmark Auxiliary file, it standardizes the match to USPS regulations and returns the output of the auxiliary file match.

Note: You cannot update the Landmark Auxiliary file while GeoTAX is running. If you want to update the auxiliary file, you need to terminate GeoTAX before attempting to replace or edit the file.

Record type matching rules

When attempting a match against the Landmark Auxiliary file, GeoTAX abides by the following rules:

Street record match

  • The input house number must fall within or be equal to the low or high house number values of the auxiliary record.

  • The input house number must agree with the parity of the auxiliary record.

  • The input ZIP Code must exactly match the ZIP Code of the auxiliary record.

Landmark record match

  • The input data must contain both a ZIP Code and address line, and they must exactly match the values on the auxiliary record.

  • The input address cannot have any other data, such as a house number, unit number, or Private Mail Box (PMB).

Note: GeoTAX only matches the ZIP Code against the auxiliary file. GeoTAX does not verify that the ZIP Code of the input address record is correct for the city and state. You should validate this information in your input address before processing against the auxiliary file.

Unavailable GeoTAX features and functions

The following contains the features and functions that do not apply when GeoTAX makes a Landmark Auxiliary file match. GeoTAX does not match to:

  • two-line addresses

  • multi-line addresses

  • intersection addresses

  • dual addresses

Landmark Auxiliary match output

Several standard GeoTAX outputs do not apply to a Landmark Auxiliary match since GeoTAX matches to an exact auxiliary match and does not perform any additional validation for the match.

GeoTAX provides special match codes and location code values for auxiliary matches. See Status codes overview for more information.

When GeoTAX finds a match to a Landmark Auxiliary file, the default output follows the following conventions:

  • GeoTAX formats the output of the auxiliary file match as a street-style address.

  • GeoTAX follows the casing setting you indicate by the casing function. GeoTAX does not maintain the casing in the auxiliary file for mixed cased values. For example, GeoTAX returns O’Donnell as ODONNELL or Odonnell depending on the setting of the casing function.

Note: GeoTAX does not change the casing for the User Data field.
  • GeoTAX removes spaces at the beginning and ending of fields in the auxiliary file.

Note: GeoTAX does not remove spaces for the User Data field.