- Enables the user to manually correct unmatched addresses, using a powerful gazetteer system.
- Works with partial and badly formatted addresses.
- Allows user to interactively match against multiple data sets.
- Ability to report the problem with the input address and intelligently select one of four gazetteers (premise, street, locality, postcode) enabling the user to locate the correct address.
- Produces reports which detail match rates and categorise non-matched records.
- Builds deduplication keys at address level, individual level and company level enabling the identification of duplicates with AtlasDedupe.
- Returns addresses to British Standard 7666.
- Enhances address records by appending additional data, such as; grid references, Mailsort Codes, salutations and valedictions and Electoral Ward Codes.
- User-friendly setup wizard, steering the user through all steps of the clean process.
- Handles most industry standard database formats using ODBC.
- Ability to work with Master Address Files (MAF) e.g. Geodemographic Data, Business Files,
- Names Data and Ordnance Survey Data.
- Allows the user to lookup on indexed ‘extra data’.
- AtlasClean is the perfect complement to AtlasBatch.
- Reads a database of non-matched addresses and cross-matches them against a Main Address File (MAF) of your choice to ensure optimum accuracy of your data.
- Ensures more accurate data by allowing the user to amend incorrect address elements.
- Stops inaccurate mailings by adding missing address elements.
- Eliminates human error by correcting incorrect address elements.
- Reduces the cost of failed deliveries.
- Minimises the need for a bureau service with Hopewiser
You may have some customers who include ‘vanity’ elements in their address. These are elements that, although they do not appear on the associated PAF record, can be retained by the software. Setting these to be ‘On’ will output only what is on the PAF and drop all vanity data. Setting these ‘Off’ will carry, for example, ‘Holly Cottage’, where this isn’t cited on that PAF record, through to the address label you output.
This implies that you have either selected the wrong type of input file, or that you have selected the Delimited Text File type, and not set the field delimiter correctly.
This is where you select the output/generated fields you are looking to include in your output. For example, if you are looking to include an address label (the dimensions of which are specified in the Preferences), you would select the Address Label item by single-clicking, then click Add. You would then get the Address Label items as defined added to the selected window on the right.
It is here where you declare the input fields pertinent to the run being undertaken. Any ‘required’ fields (ones that are not appended with ‘(opt)’ in the Input Mappings panel) should be associated with a relevant input datafile field. Typically, the input address fields are linked to AddressLine1, AddressLine2, etc. Input personal names, if you are outputting, say, NameKey, should be ‘linked’ to NameLine1/2/3.
It is here where you must specify what you want to see in your output file, and in what order. Fields from the left hand side of the Output Mappings window are added as required. Selected fields can then be reordered if necessary through the arrows to the side of this window.
Output label settings can be manipulated through the Settings|Preferences|Label parameters. For example, if you want to fix a company name to output address line 1, and have the town, county, and postcode in the last three lines respectively within a 7 line output address label, you would select the Fixed PAF Organisation option, set the Output Lines value to be 7, and set the Label Format item to Fixed Town.
This could be down to a few things, the main one being that the input fields haven’t been mapped correctly. Check the input mappings and ensure you have mapped all available input address fields effectively linking them to AddressLine1-10. Ensure there is no non-address data in these fields as this can often corrupt address matching.
We receive PAF data monthly, despatching this quarterly to the majority of our client base. Please check that you are utilising the current/last release made to you and update if necessary. It may be that the missing address is a recent addition to the PAF. It could also be that this is a ‘new build’ that doesn’t yet feature on the raw PAF we receive. All such enquiries should be directed to the Royal Mail Address Management Centre email@example.com.
The PCStatus indicates the success level of an attempt to match an input address, usually to the PAF. This will be 00 where the input record was validated against the PAF. Any other status here denotes a record that has not been fully matched. For details of what each returned status code means, you can refer to the output report (View|Coding Statistics from the menu) where the counts for each are displayed along with a brief description, or refer to the appendix in the documentation for all possible return values and a fuller description of their meaning.
If the software omits the resident’s name, it could be because the Name List (vroll) file hasn’t been purchased (this is an optional extra – please ask your Hopewiser account manager) or that the NameList file path wasn’t correctly specified within the Settings|Preferences|File Paths window.
It could be that the desired field is dependent on other criteria not being met. For example, if you do not achieve an address match (PCStatus is not 00) for a record, you will not have an output DPS, but you will have an output AddressKey.
Output field names and their use and possible outputs are detailed in the appendices of the softwares accompanying documentation. The documentation can be retrieved from the Help|Contents product menu option.
This implies that, on trying to run your addressing process, you have selected to output a data field which requires the provision of an input field that you have not yet specified. For example, trying to create an output NameKey without specifying the input personal name (from which the NameKey is derived).
For further details on AtlasClean and how to best utilise the software, please refer to the PDF documentation within the application installation directory. If you have any questions not covered by these documents, please contact Hopewiser technical support department on 0161 924 2801.