Guidelines to Improve Prediction Accuracy
In order to get the most accurate prediction of address components, your input address strings should adhere to these patterns.
Guidelines for United Kingdom Addresses
- Avoid non-address components
- Presence of non-address components in the input string might lead to wrong prediction. Remove such components before feeding the string for prediction.
- Maintain a sequence in address components
- The address components should be placed in this order: .
- Remove redundant address components
- The input address string should not have repeated address components, such as two different organization names or repetitive name of an organization in one string.
- Follow single-token organization names with organization type
- A single-token organization name should be followed by the type of the organization, such as Ltd, Inc, and Reg. In the example below, Ardian is a single-token organization name. In this case, the organization name is not followed by the type "Limited," and the results may be inaccurate.
Limitations in United Kingdom Addresses
An address string of any of these kind is susceptible to getting inaccurately predicted by the address parser. Watch out for these in your address strings.
- Presence of another address component as name of the organization
- If the name of the organization includes any other address component, such as Floor, Flat, and House, the prediction accuracy may be affected.
- Organization name having numbers
- If an organization name has numbers, it is susceptible to getting erroneously predicted.
Guidelines for German Addresses
- Avoid non-address components
- Presence of non-address components in the input string might lead to wrong prediction. Remove such components before feeding the string for prediction.
- Maintain a sequence in address components
- The address components should be placed in this order: .
- Remove redundant address components
- The input address string should not have repeated address components, such as two different organization names or repetitive name of an organization in one string.
- Ensure address number and street name are included
- Your address string needs to have address number and street name. Missing out these essential address components will impact the accuracy of the result.
- Do not have merged components in address strings
- Merged address components result in incorrect prediction.
- Avoid addressee name in the string
- Address name in the string results in incorrect prediction for the German addresses.
- Do not have bracketed "()" address component
- Including any of your address components inside brackets "()" will leave it unparsed.