- 1. What is the Atlas Directory Path?
- 2. What is the MAF Directory?
- 3. What is the Sorted DTF Directory?
- 4. What is the DTF-Xref Directory?
- 5. What is the AddrGen Directory?
- 6. What are Temp Directory 1-3?
- 7. Can I specify different locality names/boundaries to those on the PAF?
- 8. Does AddressLoader handle Data Transfer Format (DTF) 6.3 / 7.3?
- 9. Can I add non-address information to my MAF (Master Address File)?
- 10. What does 'Unable to open files: Paf files are missing' mean?
- 11. Why can I not load a previously saved AddressLoader setup file?
- 12. Can I generate 'change only' DTF files through AddressLoader?
- 13. Is there any way to match misspelt streets to a created MAF?
- 14. Can I create new DTF records through AddressLoader?
- 15. Why is the MAF I have generated missing some address elements I know to be in the raw/DTF file used to create it?
- 16. Why is the MAF I have generated missing addresses I know to be in the raw/DTF file used to create it?
- 17. What does the error 'ERROR: FETCH OWNER TOWN failed:...' mean?
- 18. Can I create street records to where no pertinent premises exist?
- 19. What is the AddressLoader Script Wizard used for?
- 20. How do I set off an AddressLoader run 'out of hours'?
- 21. Further Details
1. What is the Atlas Directory Path?
The Atlas Directory Path defines the directory location of any installed Atlas programs such as AtlasCapture and AtlasBatch. If the location isn't specified, the registry will be used to locate the Atlas Directory.
2. What is the MAF Directory?
The MAF directory defines the location of the output MAF (Master Address File) to be created by AddressLoader. These will be a set of compressed and encrypted files that can be utilised by other Hopewiser software in looking up and validating address data.
3. What is the Sorted DTF Directory?
The Sorted DTF directory defines the directory location of the output sorted DTF file called 'sorted_dtf.txt'. This directory also stores the sort procedure log file called 'sortdtf.log'.
4. What is the DTF-Xref Directory?
The DTF-Xref directory defines the directory location of the output DTF cross reference file. This file will have a fixed name 'dtf_xref.txt'. The report file of the cross reference procedure 'dtf_xref.rpt' is also written to this directory.
5. What is the AddrGen Directory?
The AddrGen directory defines the directory location of the output address file named 'r_out_0'. It also houses a number of log/error files which are created during the address generation process.
6. What are Temp Directory 1-3?
The Temp directories are directory locations used for storing temporary files.
7. Can I specify different locality names/boundaries to those on the PAF?
The PAF files despatched with the Hopewiser software are invariably UK-wide files. If you find that the generic PAF has localities and boundaries that do not fit in with your requirement, you can construct and define your own using the AddressLoader Locality tab. These can even include locality abbreviations and misspellings.
8. Does AddressLoader handle Data Transfer Format (DTF) 6.3 / 7.3?
AddressLoader handles both versions of DTF. You can specify either version as the input into an AddressLoader process, and it will intelligently detect the version and treat accordingly.
9. Can I add non-address information to my MAF (Master Address File)?
Yes. Within the AddressLoader AtlasPrepro process, you can specify a number of 'extra data' fields which are built into the MAF and linked by association to the address data. You can even index on some of these fields (UPRN for example) if you wish.
10. What does 'Unable to open files: Paf files are missing' mean?
This error indicates that, within AtlasPrepro (an AddressLoader sub-program), the Settings|Preferences|File Paths has a 'Atlas3 MAF Path' value which doesn't point to a set of valid MAF (Master Address File) files. (MAF files begin with 'atl', end in 'c' and have no file extension.) This is a requirement because locality information is required in the build.
11. Why can I not load a previously saved AddressLoader setup file?
The reason for this error should be detailed in the error message reported. It is most likely that the input file previously used is no longer where the setup file expects it to be, or the format of the file to be used has changed since the time the setup was saved.
12. Can I generate 'change only' DTF files through AddressLoader?
Yes. The AddressLoader DTFDiff tab will help you here. This will effectively allow you to compare two generations of the same DTF, establish what differs between the two, and create output files which reflect the differences (change, insertion, deletion, status records) that can be submitted to the hub instead of the full updated DTF.
13. Is there any way to match misspelt streets to a created MAF?
Yes. Using the AddressLoader LA Edit facility in the toolbar, you can specify street alternate spellings/aliases which will, when built, provide a 'pointer' to an actual street spelling.
14. Can I create new DTF records through AddressLoader?
Yes. The AddressLoader Record Creator tab is designed specifically for this purpose. Created records comply with the latest Data Transfer Format specifications.
15. Why is the MAF I have generated missing some address elements I know to be in the raw/DTF file used to create it?
It is likely here that you have not correctly/fully mapped the input data fields within the AtlasPrepro step of AddressLoader. If fields aren't mapped as required here, then they will not be transferred/output to the resultant MAF meaning you are missing some address data.
16. Why is the MAF I have generated missing addresses I know to be in the raw/DTF file used to create it?
There could be a number of reasons for this. You should check the output .log and .err files created in the process of performing your MAF build. Select the View Error Log button in the AddressLoader Run screen and check the output from a run for the word 'Error'.
17. What does the error 'ERROR: FETCH OWNER TOWN failed:...' mean?
This usually denotes that the town and district files (dist.dat and town.dat within the AddressLoader \\addload\input\disttwn3 directory) do not properly align with the atlmisc file referenced by the AtlasPrepro Settings|Preferences|File Paths 'Atlas3 MAF Path' item. This is a requirement. If you have your own localities defined, both files will need to be in-line (the town.dat and dist.dat from the Customised Town and District build, and the atlmisc from a previous MAF dataset that made use of these customised data files.
18. Can I create street records to where no pertinent premises exist?
Yes. By utilising the AddressLoader Settings|Preferences|Settings 'Add Street Records' facility. This will create a 'dummy' street record to which you can match premises which do not currently exist in your Master Address File.
19. What is the AddressLoader Script Wizard used for?
The Script Wizard in AddressLoader provides you with a user interface in running a variety of scripts (defined in separate documents in \\Addload\scripts\docs) with a view to manipulating, cleansing, and tailoring AddressLoader related data. These scripts sometimes require that you have freeware software installed on your machine (eg, Perl scripts require that you have Perl installed). Scripts are split into Themes to make them more accessible.
20. How do I set off an AddressLoader run 'out of hours'?
This can be achieved using the following command line entry:
addload -a <setup_name>
The <setup_name> is a pre-defined AddressLoader setup file (.hpw). Only standard AddressLoader runs (incorporating the AddressLoader steps SortDTF, DTF-xref, Addrgen, AtlasPrepro, Load, LoadExact, and Report) can be run in this way. The above command could conceivably be included in a batch command file to be set off overnight when nobody is accessing the data concerned. All the same .log and ,err files will be output as per a normal AddressLoader run.
21. Further Details
For further details on AddressLoader and how to best utilise it, please refer to the PDF documentation within the application installation directory. If you have any questions not covered by this document, please contact Hopewiser technical support department on 0161 924 2801.