AtlasBatch is an automatic data cleansing and enhancement tool which can verify and correct large quantities of address data. This can be particularly useful when dealing with large numbers of records. AtlasBatch will read a database of existing addresses and cross-match them against the Australia Post's Postal Address File (PAF) ensuring optimum accuracy of your data, or you can purchase alternative datasets such as the Geocoded National Address File (G-NAF) or NZ Post's GeoPAF.
Verifies existing address records against PAF.
Adds missing address elements to ensure address accuracy.
Ability to work with partial and badly formatted addresses.
Analyses name information, correctly formatting and titling names.
Enhances address information by appending data to your records, for example Delivery Point Identifiers.
Optional enhanced data from Australia Post such as deliverable status and residential/non-residential indicators, and alternatively from the G-NAF, Latitude Longitude, Statistical Areas and Mesh Bock, etc.
Produces reports which detail match rates and categorise non-matched records.
Adds salutations (e.g. Dear Sir) and valedictions (e.g. Yours Faithfully) according to the name.
Additional information can be obtained using AtlasBatch, such as deduplication keys and Barcode Strings (allowing discounts on mailings).
Ability to use Master Address Files (MAF) e.g. Geodemographic Datasets, Business Files, Names Data and Ordnance Survey Data.
Includes a user-friendly setup wizard, steering the user through all steps of the process.
Can handle most industry standard database formats using ODBC.
Returns addresses to British Standard 7666.
Updates on the PAF can be obtained quarterly in order to maintain accuracy.
Eliminates human error by correcting misspelt address elements, ensuring that all information is clean and accurate.
Improves and maintains corporate image by ensuring all addresses on mailing lists are correct.
Increases company efficiency by making employees available for completion of other tasks.
- 1. What are the Settings|Preferences|Coder Return PAF House/District options for?
- 2. Why does the Database Viewer show only a single database field when my file has many?
- 3. What do I need to do within AtlasBatch in the 'Data to Generate' window?
- 4. What do I need to do within AtlasBatch in the 'Input Mappings' window?
- 5. What do I need to do within AtlasBatch in the 'Output Mappings' window?
- 6. Within AtlasBatch, how do I get a particular format of address label output?
- 7. Why do I get fewer matched results than expected?
- 8. Why is an address I know to exist missing from the PAF?
- 9. How can I tell matched/unmatched records apart?
- 10. Why am I not getting a desired field generated and output from my Data To Generate?
- 11. How can I find out what a particular output/generated field means?
- 12. What does 'A required field has not been mapped from the input database' mean?
- 13. Further Details
1. What are the Settings|Preferences|Coder Return PAF House/District options for?
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.
2. Why does the Database Viewer show only a single database field when my file has many?
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.
3. What do I need to do within AtlasBatch in the 'Data to Generate' window?
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.
4. What do I need to do within AtlasBatch in the 'Input Mappings' window?
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.
5. What do I need to do within AtlasBatch in the 'Output Mappings' window?
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.
6. Within AtlasBatch, how do I get a particular format of address label output?
Output label settings can be manipulated through the Settings|Preferences|Label parameters. For example, if you want to produce up to two free format lines of address and then separate Suburb, State and Postcode, set the Label Format item to Fixed Town whilst changing the default Output lines from 7 to 5 (the last 3 lines will always be Suburb, State, Postcode..
7. Why do I get fewer matched results than expected?
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.
8. Why is an address I know to exist missing from the PAF?
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 Hopewiser who will liaise with Australia Post and provide feedback to you once we have received an update.
9. How can I tell matched/unmatched records apart?
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.
10. Why am I not getting a desired field generated and output from my Data To Generate?
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 DPID, but you will have an output AddressKey.
11. How can I find out what a particular output/generated field means?
Output field names and their use and possible outputs are detailed in the appendices of the software's accompanying documentation. The documentation can be retrieved from the Help|Contents product menu option.
12. What does 'A required field has not been mapped from the input database' mean?
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).
13. Further Details
For further details on AtlasBatch 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 03 8610 3300.