User`s guide

PC*MILER-AS400 User’s Guide 46

6.2.1 Stop Validation (VA) Request and Response

The following are field parameters for stop and (for PC*MILER|Streets

users) street address validation. A stop can be a city/state pair separated

by a comma, a ZIP code, a latitude/longitude point or (with optional add-on

modules) a Canadian Postal code or SPLC (Standard Position Location

Codes). PC*MILER|Streets users may include street addresses.

For Cities with multiple ZIP codes, the first city in the returned list is the

central city or default ZIP for that city, with the remaining ZIP codes

returned in numeric order.

When generating potential matches for an address, PC*MILER|Streets

does a “Grid Based” search. This means that the search area may extend

beyond the city limits of the requested city for potential matches. You may

receive back potential matches in a surrounding town. Pick lists are sorted

in confidence order, with the “best” potential match returned first.

For example:

Requesting a pick list by setting REQ-CIT equal to Princeton,NJ;Linden*

would return the following list:

08540 Princeton, NJ, Mercer; 1 Linden Lane

08540 Princeton, NJ, Mercer; 49 Linden Lane

08540 Princeton, NJ, Mercer; 80 Linden Lane

08540 Princeton, NJ, Mercer; 100 Linden Lane

08534 Pennington, NJ, Mercer; Linden & Woodmer

08822 Flemington, NJ, Mercer; 1 Linden Court

08536 Plainsboro, NJ, Mercer; 2 Linden Lane

08536 Plainsboro, NJ, Mercer; 3 Linden Lane

08536 Plainsboro, NJ, Mercer; 4 Linden Lane

NOTE: Grid Based searches are only done with address level lookups

(PC*MILER|Streets only).

Validation requests are important because error reporting in mileage

requests is limited to the first two stops of a trip. If your bad stop is lower

in the list of stops, you will not be told which is the non-valid stop; you will

get a generic “Can’t Run Trip” message. The VA request type can be

used to produce lists of potential matches to partial spellings or ZIP codes.