Have you ever ran an address in our ACE and/or one of our other address correction / standardization applications and received output which was totally unlike what you were expecting? For example, did your input address contain a Rural Route (RR) which on output was converted to an actual street name? Or your input primary range on output was changed significantly? Finally, was your input street name changed on output? If you have had these issues in the past and could not figure out the reason, most likely it is due to a LACSLink conversion.
What is LACSLink or Locatable Address Correction Systems? LACSLink is used in address processing to automatically convert addresses which have been changed by local governments. One common change includes "911" conversions which make it more easy for police, fire, ambulance, and postal services to locate rural addresses. The actual delivery point remains the same and the occupants of the residence have not moved, but the address itself has been changed.
How do you identify a record converted by LACSLink? LACSLink converted addresses will have a LACSLink return code of either "A" or "92". In order to retrieve those codes you will need to post the appropriate output component in your address standardization/correction software. For example, in our ACE software, you would want to use the ap.LACSL_Ret (jobfile) or ACE_LACSL_RET (Library) component when processing your job.
So the next time you have an address which you do not believe to be correct and/or is looking like one of the examples I described above, try posting the appropriate LACSLink output component in your ACE and/or other address standardization software. I am confident that in my experience, most times there is a LACSLink conversion involved and is the reason for the change.