- AtlasLPG is a quick and easy to use reference data build application using LLPG (Local Land and Property Gazetteer) and NLPG (National Land and Property Gazetteer) imported data in DTF (Data Transfer Format).
- Used to import data, highlight potential problems and export address data plus additional information, either for use with the Hopewiser Atlas matching tools or to a simple delimited text file.
- AtlasLPG comes with further tools, allowing the user to create specific Town and Locality files, plus Alternate Street definitions.
- Includes radius searching, and AutoComplete (‘as you type’) address capture.
- Allows users to either import a single Local Land and Property Gazetteer (LLPG) Data Transfer Format (DTF) file set, import multiple file sets, merge file sets from other areas, or import National Land and Property (NLPG) data.
- In addition Change Only Update file sets can be imported to modify existing data previously loaded.
- During the import procedure, the integrity of the data is checked using DTF validation rules and additional Hopewiser sourced validation rules based upon issues previously identified within the NLPG imports.
- A log file is created specifying import problems to help identify and correct any issues.
- A variety of reports can be run on the imported data.
- These include highlighting invalid records, based on the DTF validation rules, identifying address records that would be ignored on export, or addresses that do not match the current Town, Locality and Administrative Area definitions.
- These are useful in correcting data within the imported files.
- The imported data can be exported to a text file, containing address records, or to a Master Address File (MAF).
- Setup options allow the specification of extra data to be output alongside each address and allow indices, based on non-addressable data items, to be included in the MAF.
- The options can also be used to configure which address types to export. For instance, only Approved data could be kept in one MAF, whilst another MAF could be created to contain all Historical and Rejected data.
- Other options prevent the export of Street Records, or only allow Postally Addressable records to be exported.
- The MAF files are used within the Hopewiser Atlas products and can be made to include radius searching, and AutoComplete address search functionality reducing keystrokes needed to enter address data.
- Any issues will be highlighted within an export log. These could be due to either data structure problems or conflicts with the location information.
Town and Locality Edit
- Allows users to edit a predefined set of Towns, Localities, Outcodes and Misspellings, or create a new set, based on data imported by AtlasLPG.
- This can highlight potential issues within the data and allow the user to add known problems and common misspellings so that future matching rates increase and problems are reduced.
Alternate Street Edit
- Allows users to create and maintain a set of Alternate Street definitions from the data imported by AtlasLPG.
- It can highlight potential issues within the data, and allows the user to add Alternate Street names for known problems, increasing future matching rates and allowing the Atlas matching / validation products to learn.
- The initial import process will create Alternate Street names where Street Descriptions exist in different languages (ie, Welsh).
- As AtlasLPG modifies Streets through Change Only Update files, a function is provided to check for updates and automatically amend the Alternate Street definitions.
I get a message 'Input file is a version 7.3 DTF. This version is not supported'. What does this mean?
The raw data being provided as input is not to current Data Transfer Format standards. This affects the import validation, so a DTF version 188.8.131.52 or later gazetteer extract is required.
This is likely down to an incorrect Preferences setting in Settings>Setup Options>Miscellaneous. Here, you can select whether your build utilises TOWN_NAME (from the DTF type 15 record) or POST_TOWN (through the DTF type 24 / 28 record). The Primary town field settings dictates preferences on this score. Values can also be affected by the Data Creation setting in the same panel.
The AtlasLPG software performs validation checking ensuring import data integrity. This can be adapted via the Settings>Setup Options Import and Merge tab settings. Various reporting and error files are created during the course of the build which should help in defining the problem area. Certain settings also allow the intentional dropping of certain DTF record types and classifications. Please refer to the associated user guide for more details.
Shipped with the product are locality files detailing the standard Royal Mail PAF localities and some common misspellings. You can adapt and add to these using the Town and Locality Edit sub-application, and include the likes of Outcode and Administrative Area too. This is a sub-application of AtlasLPG and separately documented accordingly (tledit_ugd.pdf) within the installation folder.
The AtlasLPG sub-application called Alternate Street Edit can provide this functionality so that the entry of a thoroughfare alternative in looking up an address (providing there are no conflicts) can match the official version or spelling. The documentation in the installation folder called streetedit_ugd.pdf gives full details on usage and capability in this regard.
Yes, this is possible through the Extra Data tab within the Settings>Setup Options menu item. This will mean that, having matched the associated address in a processing run, you can append this extra (non address) data adding value and working towards a single customer view.
As AtlasLPG performs extensive validation of inputs to ensure data continuity. The import data has to be in a current DTF format. However, if you require a reference dataset created from other sources (such as a comma separated address file), please contact us as we may be able to help.