Welcome to Frequently Asked Questions
Please find a range of FAQ's for address data, the National Address Gazetteer infrastructure, streets and general questions. This is regularly updated by the Helpdesk team.
If you cannot find that answer to your question then please contact our Helpdesk either via email ([email protected]) or phone 020 7630 4602 between 9.00 and 17.30.
Choose the type of FAQ you would like to view below, or by selecting the categories on the left of the page.
The NSG is the definitive database of streets in England and Wales. It is principally used by Local Authorities streetworks departments to coordinate the work that is being performed on the highway within their administrative area. It aims to minimise disruption and ensure public safety and forms part of the statutory duty of the local authority as defined in the New Roads and Streetworks Act (1991).
The Local Street Gazetteer (LSG) also acts as a Local Authority's definitive dataset of the streets in their administrative areas and contains details on the highway, street or footpath, who is responsible for maintain it, what is it made of and a variety of other information that the Local Authority holds as attribute date. E.g. designations and related legal orders.
Certain other organisation may use NSG data under agreement with a statutory body they are working on behalf of to help deliver their core services. For example contractors to a Highways authority may use NSG data, however the data should be supplied by the eligible organisation. Where these parties require access directly from the NSG certain qualifications must be met and a charge for access would be payable.
Why a new Data Transfer Format - DTF8.1?
The NSG was first introduced through the New Roads and Street Works Act 1991. Since 2001 it has become the definitive dataset for street data within local highway authorities. Although originating from streets works it is now used much more widely and has become the bedrock of many local highway authority's street data usage.
Changes to the structure of the NSG were last made in 2009. This in itself increased the understanding and capture of Additional Street Data (ASD) and since 2009 every type of highway authority in England and Wales has made regular monthly updates to the NSG for use by the works promoter and statutory undertaker communities.
More data and more updates led to more users of the data and today we now have over 60 statutory undertakers downloading data on a monthly basis. We also now have over 150 of the highway authorities downloading data to put into their own street works systems to ensure that the NSG is synchronised when corresponding with any works promoters.
With a doubling of the user base, several improvements and enhancements have been suggested over the years to capture more data that is seen as potentially useful. Not every request could be accepted at this time, but a considerable number have been incorporated to allow the NSG to grow to the next level.
The NSG is also now used much more widely than its' original intention and is used across numerous in-house local highway authority functions, and by a number of central government organisations. It has become the most up-to-date and comprehensive street dataset in England and Wales. However so much more can be attributed to the data and a work plan to capture more data has been put into place. This new DTF8.1 is the data transfer format that underpins those aspirations.
What is included in the new DTF8.1?
Firstly it is a significantly better structure. The enhanced LG geometry file has been grouped to include all things that must form a junction to junction section, so for example, direction of travel and one way streets exceptions. But also a new record has been added to the LG file to better record highway dedication (formally called classifications). It was identified that the previous method was not compatible with what was actually on the ground, and so a new record has been added to allow capture in significantly more detail.
Within the enhanced ASD file there has been allowance for extended capture of data. Information that Local Highway Authorities and utilities have agreed has some usefulness in minimising impact on the public has been included. Some of these have arisen from feedback from the wider community, for example, Emergency services routes. These are all intended to give as much information as possible before works are planned.
Not only is there more ASD, but it is also better structured. For example things that related to the physical construction of the record have been grouped into the construction record. This includes reinstatement, but also details of special surfaces and special construction needs, alongside a variety of newly identified data such as frost heave susceptibility. All of this will give work promoters and statutory undertakers a better understanding of what to expect before and when they arrive on site.
Additional information about specific maintenance responsibility has been provided. Identifying the highways authority who is responsible for a street has not always been straight forward. But the new system will allow for it to be more clearly identified, especially to pick up on the streets that have regional or national bodies responsible for them (e.g. Transport for London (TfL) and Welsh Assembly Government (WAG)
There has finally been extra optional fields to hold additional information on Public Rights of Way (PROW) and their associated obligations (note all streets or paths with PROW obligations are automatically classified as highways and therefore do come under NRSWA) and hold ASD geometry, many people have requested the facility to be able to hold ASD polygons or subsections in a geographic structure. Although this has not been made mandatory, the new DTF8.1 structure allows for this change and for data to start to be captured in a more user friendly way.
What are the Specific Updates to the DTF8.1?
Basic Street Data updates (LG file)
A new Street State code = 5 - Street for addressing purposes only, has been introduced. This is to allow streets that are specifically for addressing purposes only to be captured. These are streets in name only and consist of no tarmac on the ground. One example of these is street named terraces.
Street Classification has changed its name to Highways Dedication and has moved to ESU level as a new record type (17). This provides ESUs at section level of who is allowed access to the network and is managed at a junction to junction level rather than at a whole road level.
Explicit code to identify Public Rights of Way obligations
Explicit code to identify formal national Cycle Routes
Explicit codes to identify quiet routes and physical obstructions
Explicit codes for planning orders and prohibited works
All classification cross references, M, A, B, C, LCR, NCR and Y must now be linked to an ESU through the street type 3 record. Previously this could be done either at ESU level or USRN level.
Structure of ESUs has been updated to contain all coordinates in record type 14.
Direction of travel exceptions have been moved from the record type 65 to a new record type 16.
Additional Street Data Updates (AD file)
Adoption status has been clarified and changed name to maintenance responsibility
New code to allow data to identify where the network is managed by another authority (e.g. Highways Agency)
Reinstatement record has been grouped together with Special Surfaces and Special Construction Needs and been put under a new title of Construction Record
New codes to note Aggregate Abrasion values
New codes to note Polished Stone values
New field to note Frost Heave Susceptibility and Stepped Joint
New Special Designation codes have been added to allow capture of;
Drainage and Flood Risk
Unusual Traffic Layout
Winter Maintenance Routes
HGV Approved Routes
Emergency Services Routes
Special Designation codes = 4, 5, 7, 14 and 15 have been removed.
Special Designation code = 16 - Lane Rental, use clarified as specifically for lane rental
A new Public Rights of Way Record has been added to hold more information about PROW obligations. (Record Type 66)
Geometry for any ASD can now be captured as physical geometry of wither lines or polygons. (Record Type 67)
Source code added to give an indication of where the information comes from
- Removal of need for Metadata file
- Two metadata records have been added. One to each LG and AD file
- Several textural fields extended to allow more information
- Date and time structure rationalised through the document
What changes are there to the OD files?
There are no structural changes to the OD files, however DTF8.1 should only be submitted alongside ETON 6 files or later.
What are the timeframe for moving over to DTF8.1?
From 1st June 2015 DTF8.1 transfer files can be submitted to GeoPlace, all transfer files will be treated as updates and downscaled to DTF7.1 during this time period. In effect the NSG will be dual running and making available, in both the DTF7.1 and DTF8.1 formats. DTF7.1 transfer files will continue to be accepted by GeoPlace until 29th September 2016. From 1st October 2016 onwards ONLY DTF8.1 transfer files will be accepted by GeoPlace. DTF7.1 will only be published until 31st October 2016. From this date if you have not made the transition to the new DTF8.1 format you will need to contact GeoPlace to request the translation service.
It is a BS7666 compliant address database maintained and used by a relevant local authority. As the database is maintained centrally and to a common standard it delivers real efficiencies and improvements in service delivery and interoperability when implemented throughout all parts of an organization. Subsets of the LLPG are supplied to GeoPlace in the form of authority address updates. GeoPlace compiles these within GeoHub, together with a number of other input data sources, to form the basis of the National Address Gazetteer.
There are a number of outputs from GeoHub including data which forms a core part of the AddressBase® range of products, available from Ordnance Survey.
From November 1st 2016 only DTF8.1 files will be published. Therefore all Local Highway Authorities that have not made a successful DTF8.1 submission by Friday October 28th will have their latest DTF7.1 data automatically upscaled (to Pass) to ensure data is published during November. Please note that this may not be fully DTF8.1 compliant due to the complexities of DTF8.1 validations. It will be flagged as a different colour on the download matrix.
If you wish to utilise the Upscale (to Pass) prior to the deadline to make a submission and subsequently avoid falling to BNS within the Improvement Schedules there are two options:
- Provision of updated DTF7.1 to the support desk for upscale (this will allow you to continue with Address synchronicity)
- Upscale of published DTF7.1 data submitted in September
Please be aware that if utilising the Upscale (to pass) facility, you will need to ensure that your authority has reviewed and is happy to submit the files provided. Once submitted your authority is accepting liability for the data, these files will also not be identified separately at the point of download.
After November 1st any request to upscale a Local Highway Authorities data to DTF8.1 will incur a charge. This will be charged per successful submission (maximum 2 submissions per month).
Under DTF8.1 the exception list is removed. Every USRN is required to hold type 61 Interest and type 62 Construction Record information, for those streets your authority does not have maintenance responsibility for and would have previously been on the exception list, specific codes have been created:
Type 61 Interest Record:
STREET_STATUS = 4 - Maintenance responsibility is to another Highway Authority.
NTEREST_TYPE = 8 - All notices.
SWA_ORG_REF_MAINTAINING = 0011, 0012, 0013, 0014, 0016, 0020, 7093 (Dependant on which National/Regional Highway Authority maintains the street).
Type 62 Construction Record:
REINSTATEMENT_TYPE_CODE = 11 - Maintenance responsibility is to another Highway Authority.
Access to the search facility
The search facility is available to all participating DCA authorities. This service is not available to members of the public.
All new requests for logins to the site must be made via the DCA Principal Contact or Authority Address or Street Custodian.
An email needs to be sent with the following information to the helpdesk:
- Full name
- Email address
- Telephone number.
There is no charge for this service.
Access to NSG Upload
Only one login per authority/organisation is permitted for uploading data to the NSG. To find out who has this access in your authority contact the helpdesk.
Access to NSG Download
To request additional access to the NSG download facility an email will need to be sent by the Authority Street Custodian with details of the user requiring this access.
If you are not a local highway authority please go to the Register for Street Services section.
Access to My Annual Improvement Schedule
Access to complete the annual improvement schedule is provided to the Authority Street Custodian only. This is usually available for completion around the end of February each year. Communications are sent out with more details when this is available. You will be able to review what was submitted in the previous years questionnaire through this link.
Passwords are no longer stored in a way that the GeoPlace helpdesk can see. If you have forgotten your password please go to the login page and click on the forgotten password link.
- Enter your username and confirm you are not a robot by checking the box and following the on screen instructions.
- You will get an on screen message informing you that a reset token has been sent to your registered email address.
- Follow the link in the email and enter a new password when prompted. passwords must be at least 8 characters long, they must contain at least one upper, one lower case letter, one number and one of these special character
- Login to the site with your new password.
If you have any problems please fill in the help form, email [email protected] or call 020 7630 4602 to speak to a member of our helpdesk team.
Password are no longer set to expire after 90 days, but if you need to, or wish to change your password please follow the instructions below:
1. Click on the login button in the top right hand corner
2. Go to My Account
3. Go to User Profile on the left hand side menu
4. Click Change password
5. Enter the username, old password and new password
passwords must be at least 8 characters long, they must contain at least one upper, one lower case letter, one number and one of these special character
If you have any problems please fill in the help form, email [email protected] or call 020 7630 4602 to speak to a member of our helpdesk team.
You will be logged out from any services that you have access to after 29 minutes of inactivity as a security precaution to protect you account.
You will be prompted to log back in so please re-input our login details to carry on using the GeoPlace services.
Uploading is a simple process that requires nothing more than a standard browser. To start uploading go to the login located to the top right of the services homepage. Once logged in click on Upload your data (under the streets menu).
Click Add Files and browse to the location of your files.
The files required are:
- XXXX_LG.csv (mandatory)
- XXXX_AD.csv (mandatory)
- XXXX_OD.xml (mandatory)
You can slect and upload multiple files at once.
- Zip archive (Optional: all the above files no file name structure needed)
Once the mandatory files have been uploaded choose whether to submit a live or test submission.
After this, your submission is locked. You will be notified via email once the submission has finished. If unsuccessful, please download the error report, correct the errors and repeat the above process. For more information on the error codes please read the compliance check specifications: DTF 8.1
In order to access the data you must first register as an authorised statutory undertaker or user of the data. This can be done online here: NSG Registration
Alternatively data can be provided on DVD/CDROM which will incur an administrative charge
The Direct Access service was set up as it is increasing evident that much of the work that Local Authorities and Statutory Undertakers undertake was being carried out by other parties under contract. Although technically the NSG data should be obtained from each individual organisation, it was clear that when an company has multiple contracts and is working with multiple organisations, methods of obtaining data are inconsistent, infrequent and in some cases non-existent. The Utility and Contractor community and the HAUC group therefore requested that a process was developed to allow contractors Direct Access to NSG data.
The key requirements of Direct Access are as follows:
1) Must declare the organisation it is downloading data on behalf of.
2) Must only download data where the appropriate Ordnance Survey licenses are in place.
3) Will not be allocated a DfT code to issue street works notices or permit applications in their own right.
When a Contractor downloads data, the transaction will be recorded and reported to the appropriate bodies. At this current time these are:
- the Authority whose data was downloaded,
- the Authority or Organisation that the contractor is working on behalf of GeoPlace LLP
NB that the confirmation of license agreement is subject to audit by Ordnance Survey.
Once agreement is in place the number of users within a single organisation is currently unlimited. Each person will be allocated their own account and is able to download different data as required.
The current annual cost for this Direct Access service is £3200+VAT.
This service is available to any organisation that is using data for street works, Highways maintenance, and traffic management on behalf of either Statutory Undertakers or Highways Authorities. Please note the service offered is for access to NSG data directly. Use of the data is still governed by individual contracts in place with Local Highways Authorities or Statutory Undertakers.
To request this service please send a purchase order, along with details of the Primary contact for the Contractor organisation. On receiving the purchase order we will set up access immediately.
Once you are logged in to the GeoPlace services page, if you have NSG downloader access you will be able to access the download areas from the streets menu.
The downlaod matrix is displayed for all local and regional highways authorities with the options to download Level 3, ASD, ETON and in some cases where appropriate Lane Rental (Kent and TfL) and Combined ASD local data files witht he addition of regional highways authorities data for that area such as TfL, Highways England and Welsh Government.
If you wish to customise this view to display the organisations you download data for, then use the Manage Your Downloads option on the right hand side of the page and select the organisations you wish to download data for. These will then become the only organisations availabel on the download matrix.
If at any time you need to reduce or expand the list this can also be done thorugh the Manage Your Downloads button.
During May 2013 OD File Exchange was introduced, this means to download NSG data a user must have a current OD file held on the NSG website. The OD file must have been made in the previous or current month of the requested download.
This will apply to all Utilities and Local Authorities. This has been implemented following a request from the Highway Authority and Utility Committee (HAUC) to ensure that all OD files are kept up to date and stored centrally on the NSG website. For more information on how to upload a file please see the ‘How do I upload NSG/ASD data?'
Details of all compliance tests conducted by the hub are contained in the DTF8.1 Compliance Check Specification document.
DTF 8.1 Files submitted to the NSG hub are health checked using DTF 8.1 Health Check Specification. This is to assist Custodians in improving the quality of their gazetteers.
A second submission was introduced to encourage authorities to make a successful early submission, but would give them an opportunity to submit any changes that may have occurred to the data during the latter part of the month.
The second submission is a service provided by GeoPlace but is an optional submission. Authorities who submit within the first 10 day working days are given the opportunity to make changes to their data and resubmit before the end of the month, second last work day of the month.
Benefit of a second submission
- Up to date information is published
- Achieve ‘Gold' assessment in the Submission category in the monthly Improvement Schedule
- Allows you to submit any critical changes that may occur late on in the month
- You have a further opportunity to make corrections to the monthly Health Check
If you have made a successful submission within the first 10 working days you will automatically be able to make a second submission through the NSG website using the "second submission" button from the 11th working day.
NSG data is published on the second working day of each month. The published data will contain data submitted by Local Authorities during the previous month.
Statutory Undertakers and Local Authority street works teams should upload the published data on the second working day to ensure consistency between the two datasets.
|NSG Edition||NSG Publication Date|
"whole or part of a highway, road, lane, footpath, square, court, alley or passage"
There are also a number of other statutory definitions of a street which should be referred to in the context of street works and Street Naming and Numbering legislation. The Utilities use the PUSWA Act 1950 definition:
"A street includes any length of highway (other than a waterway) road, lane, footway, alley or passage, any square or court and any length of land laid out as a way whether it is for the time being formed as a way or not, irrespective of whether the highway, road or other thing is a thoroughfare or not."
The New Roads and Street Works Act 1991 defines it as follows:
For England and Wales:
A "street" means the whole or any part of any of the following, irrespective of whether it is a thoroughfare-:
(a) any highway, road, lane, footway, alley or passage.
(b) any square or court and
(c) any land laid out as a way whether it is for the time being formed as a way or not. Where a street passes over a bridge or through a tunnel, references to the street include the bridge or tunnel
A "road" means any way (other than a substitute road made under section 74 (1) of the Roads (Scotland) Act 1984 or a waterway) whether or not there is over it a public right of passage and whether or not it is for the time being formed as a way and the expression includes a square or court and any part of a road.
The Joint Authorities Group(UK) – (JAG(UK)) - represents the organisations responsible for the roads and streets of the United Kingdom. JAG (UK) focuses on the daily operation, the coordination of works for asset or utility network management and other events taking place on the highway. JAG(UK's) member organisations are primarily local authorities and similar bodies whose principal activities are governed by highways, street, road and traffic management legislation.
Their responsibilities include regulation of streets and roads for any purpose, with a view to maintaining public safety, asset integrity and the movement of people and goods. JAG(UK) Support of the local authority streetworks community parallels the work the NSG does with the street data side. Both JAG(UK) and GeoPlace are keen to ensure LHAs work together in the most efficient way possible.
The Highway Authorities and Utilities Committee(UK) (HAUC)(UK)) was established in 1986 by the constituent bodies of the local highway authorities and the utilities to assist the Secretary of State in arriving at proposals for new street works legislation. HAUC UK played a significant role in the drawing up of the New Roads and Street Works Act 1991 (NRSWA), its subsidiary legislation and associated Codes of Practice.
The main aims of HAUC(UK) are:
- To advise the Secretary of State on issues relating to street works legislation
- To provide guidance to practitioners
- To provide a forum for matters of mutual interest in relation to street work
- HAUC(UK) is principally made up of member from JAG (UK)(Joint Authorities Group) and NJUG (National Joint Utilities Group)
The SWA Code or formally known as the Department for Transport (DfT) code, is a 4 digit code that has a 2 character prefix e.g. AB1234.
GeoPlace alongside Highway Authorities and Utilities Committee (HAUC) UK manage the allocation of these codes on behalf of the DfT. The code uniquely identify Street Work Authorities and Statutory undertakers that have a legal right to carry out works in the highway. In order to download National Street Gazetteer (NSG) and/or Associated Street Data (ASD) data from our website you need to have a SWA code assigned to your organisation. These codes are also a key requirement of the EToN noticing process.
Apply for a SWA code Register for an NSG user account or request a SWA code on the NSG Registration.
The Trunk Road Street Gazetteer (TRSG) is the gazetteer that is used by the Highways Agency on all major motorways and trunk roads in the UK. Although built to the same specification and DTF, it is distinctly separate from the NSG. And instead of USRNs is uses a different reference, the TRRN (Trunk Road Referencing Number).
For completeness the NSG still contains the complete network of trunk roads and motorways in the LSG with USRNs, however for noticing purposes Statutory undertakers must use the TRSG where it is available. It is recommend that NSG and TRSG are used in partnership to ensure that all parties understand where their interests start and finish.
Anyone who has interest in a motorway or trunk road and who would like to receive copy notices of any works via EToN, should contact the TRSG Custodian. Details can be obtained via the helpdesk
The system of roads classification is intended to direct motorists towards the most suitable routes for reaching their destination. It does this by identifying roads that are best suited for traffic.
All UK roads (excluding motorways) fall into the following four categories:
- A roads – major roads intended to provide large-scale transport links within or between areas.
- B roads – roads intended to connect different areas, and to feed traffic between A roads and smaller roads on the network.
- Classified unnumbered - smaller roads intended to connect together unclassified roads with A and B roads, and often linking a housing estate or a village to the rest of the network. Similar to ‘minor roads' on an Ordnance Survey map and sometimes known unofficially as C roads.
- Unclassified – local roads intended for local traffic. The vast majority (60%) of roads in the UK fall within this category.
Road classification uses a common system of route numbering, which is centrally administered for England and Wales by the Department for Transport.
The primary route network (PRN) designates roads between places of traffic importance across the UK, with the aim of providing easily identifiable routes to access the whole of the country. Primary routes are marked green on most road maps, as opposed to the more common red of an ordinary A road; and road signs are green with white and yellow text.
From April 2012 Local Authorities are responsible for designating road classifications and the primary route network. GeoPlace are responsible for consolidation of data on behalf of DfT alongside ensuring their inclusion in the NSG
Data Entry Conventions
Under NRSWA code of practice it states that Motorways should be collected by a local authority whether or not it is the street authority for that particular street. In creating a Motorway records one type 2 Street Record must be created for each junction to junction section, slip roads and through section of a Motorway in each direction of travel.
The local highway authority range of USRNs
Each type 2 Street Record must then be cross referenced to the appropriate type 3 Street Record.
The local highway authority range of USRNs should be used for both Type 2 and 3 street records.
You should name the each junction to junction section, slip roads and through section as follows, this direction of travel is also identified in this process
Junction to Junction:
M6 JUNCTION 2 TO JUNCTION 3
M4 JUNCTION 5 TO JUNCTION 4
M6 THROUGH JUNCTION 2 FROM JUNCTION 1
M6 JUNCTION 2 FROM JUNCTION 3 OFF SLIP
The Type 3 USRN must only reflect the legal classification and therefore there should only be one USRN per motorway per authority. Locality should also not be entered and Town Name should reflect the name of the SNN authority this is also applicable to the type 2 streets.
Motorways should not have any Type 62 or 63 ASD recorded against them and should be on the authorities' exception list. You should however enter a record to receive all notices on that street. Further information on why and how to record motorways can be found in Appendix F of the DEC.
There are four statutory Special Designations that if exist should be created, maintained and submitted to the NSG:
- Protected Street.
- Traffic Sensitive Street.
- Special Engineering Difficulty.
- Lane Rental.
The information on how to collect this data is found in NRSWA under ‘Streets subject to special controls' and is usually subject to criteria and consultation.
There are a further optional special designations which can be found in the Data Entry conventions and our guidance is to collect as many you can to provide tighter controls over your network.
A private street needs to be in the NSG. It needs to be captured as any other street and a primary noticing authority set in the Interest record (Type 61). Where the Street Manger is known and is able to receive EToN notices it is possible to include them as a separate category in the OD file.
If however they are not known, the Local Highways Authority has a responsibility to act as the Street Works manager and recieve the Notice. It is recommended a Private Street manger district is set in your OD file as 998, and then all primary notices are sent to that and can be dealt with appropriately.
The Adoption status should be set as 3 - Neither 1, 2, 4 nor 5.
The Reinstatement Record (Type 62) should always be set to 9 – Private street.
There are both advised and mandatory changes required to an authority's LSG in preparation for a Permit Scheme.
Fundamentally you need to ensure the quality and accuracy of your Additional Street Data (ASD) information.
You need to ensure that Interest records correctly reflect what is publicly maintainable within your authority. An authority cannot receive permits on private streets.
Category 0, 1 and 2 streets should be reviewed as they feed into strategically significant streets and the section 74 overrun process
Special Designation Records
Special designations provide tighter control over your highways. Protected Streets, Traffic Sensitivity and Special Engineering Difficulty also feed into the charge rates and should be reviewed as a matter of priority.
In preparing for a Permit Scheme it is essential initially to ensure that your private streets are have a separate district within your OD file. Upon going live the district function of the district used for publicly maintainable streets should be set to 9 to dictate that the USRNs are now subject to permits.
You can find more detail in the permit scheme preparation document released by GeoPlace.
There are three principal pieces of legislation that apply to the Street Naming and Numbering, which are:
UPRNs are integers (numbers) that can be up to 12 digits in length; they can therefore be less than 12 digits long and do not require leading zeros. However some gazetteer database applications will pad UPRNs that are less than 12 digits with zeros. The NLPG Hub strips away all leading zeros and does not pad UPRNs with zeros when supplying data.
PLEASE NOTE - This is not the same UPRN that is requested on Energy Performance Certificate forms. For this reference please contact your energy supplier.
The NLPG (National Land and Property Gazetteer) no longer exists as a product, so if you are a new user of Address Data please contact the Ordnance Survey to inquire about or order AddressBase data. You can find out more information about AddressBase products here.
PSMA members who have been receiving address updates prior to 29th January 2014 now receive NLPG re branded (AddressBase Incremental Change Supply (ABICS)). This data will continue to be supplied in the same frequency and format as it is now, until an acceptable alternative is available.
If you receive an ABICS and require a fresh cut of the same data click here to download the re supply order form.
You can request one refresh of data per financial year at no cost. Otherwise it is £155.00 plus VAT for each subsequent Order made in the same financial year.
It is no longer possible to expand your data coverage, change the frequency of supplies, or place a new order for data, you will need to contact the Ordnance Survey PSMA helpdesk to arrange taking AddressBase data instead.
The Address Search facility is available to all participating DCA authorities, and existing fire and police users. This service is not available to members of the public.
All new requests for logins to the site must be made via the DCA Principal Contact. An email needs to be sent with the following information to the helpdesk:
- Full name
- Email address
- Telephone number.
There is no charge for this service.
Please read GeoPlace's FTP Site User Guide which tells you how to access, upload and download files from the FTP server.
There is a separate username and password for the Address FTP site and the Street FTP site. The passwords stored by GeoPlace are encrypted, so if you do not have this information, and cannot find this internally then please contact the helpdesk who will be able to reset the password for you, the username will always remain the same.
Please bear in mind resetting the password will affect anyone, or any systems using this login information.
Please note: the FTP site is a data transfer facility therefore files are deleted after 3 months.
There are 3 methods you can use to gain access to the FTP server:
- Internet Browser (please note that not all browsers support the file transfer protocol)
- Dedicated FTP client
On the FTP site each authority has been assigned its own home area. Contained within this area are 2 directories; IN and OUT. In order to send (upload) files to the Address hub you should place them in the IN directory. Any files supplied to you will be placed in the OUT directory (in a sub-folder) for you to download.
With an Effective Date of 1st April 2012, it replaces similar arrangements between all councils and the Local Government Information House (LGIH - a subsidiary of the LGA) which have been in place since 2005 (the Mapping Services Agreement (MSA)) expired on the 31st March 2012.
More information on the DCA
Through agreement with Scotland's Improvement Service Company, working on behalf of Scottish Government, the National Address Gazetteer includes Scottish address data.
The National Address Gazetteer is the single source from which the AddressBase® products are developed.
Authority updates are supplied from the LLPG by address contributing authorities to GeoPlace on a regular basis. GeoPlace combined this local intelligence with other national data sources to produce the National Address Gazetteer infrastructure which in turn form the AddressBase range of products, made available through Ordnance Survey.
Ordnance Survey AddressBase® FAQs also contain further information.
Address Contributing Authorities will be entitled to receive the data in exactly the same format (DTF) and frequency as currently*, until an alternative acceptable dataset can be supplied to NLPG equivalent update frequencies (that is, daily). It is envisaged that any such alternative dataset will not be available before October 2014.
All other PSMA members, including street contributing authorities, will need to migrate their address product use by October 2014.
Any questions should be directed to your PSMA Account Manager or the PSMA helpdesk.
*Only available to those Members which, as at 31 March 2011, were in receipt of daily, weekly or monthly updates, as applicable.
Once the records are received from local authorities, GeoPlace undertakes a large data validation exercise testing the incoming LLPG and LSG data against the Data Transfer Format (DTF) and the Data Entry Conventions (DEC) specifications. Both NLPG and NSG are then compared against each other to highlight any street record anomalies.
A series of 500 health checks are also carried out on the two datasets. Further checks are carried out on logical data consistency, classification and address mismatches between the NLPG, Ordnance Survey, Valuation Office Agency and Royal Mail's Postcode Address File (PAF) to form the National Address Gazetteer Database based upon the use of the UPRN and USRN.
By taking data from multiple sources; local authorities, Ordnance Survey, Royal Mail and the Valuation Office Agency and validating it against each other, GeoPlace can be confident that change intelligence on the ground is captured.
In addition to the work carried out ensuring data conformance, GeoPlace works to ensure the product is fit for purpose and meets user requirements from both the public and private sector.
GeoPlace has achieved certification to two industry recognised and highly respected international standards, namely ISO9001 for Quality Management, and ISO/IEC27001 for Information Security. Certification to these standards is part of GeoPlace's drive for quality, accuracy, and security for all the work we do.
The PSMA Helpdesk can be contacted with any questions.
For Government organisations the UPRN is an underpinning linking mechanism that removes error in data exchange and communication, supports citizen service improvement and delivers efficiency gains in operational processes.
For commercial organisations AddressBase provides the link between postal addresses and the UPRN as a means to locate and uniquely reference customers and assets to enable business growth, gain competitive advantage and reduce operational costs.
Case studies can be found on the Ordnance Survey case study locator: www.ordnancesurvey.co.uk/business-and-government/case-studies
- Roles and responsibilities
- Full name
- Job title
- Work address
- Telephone number
- email address
Please note: the passing of any licensed addressing data to a contractor will require the relevant Royal Mail terms being passed on to them. In addition, their use of that data (including the number of users) must also form part of the required annual declaration(s) made for such use. The terms that you need to pass on are available here on the Ordnance Survey website.
1. Passing NLPG data for use by a Contractor: As NLPG usage is licenced to your authority via the PSMA, you will need to agree a PSMA Contractor Licence with your Contractor (advice should be sought from Ordnance Survey if you have any questions). The PSMA Contractor Licence can be found on the Ordnance Survey website.
2. Passing LLPG data for use by a Contractor: The licence for use of any Ordnance Survey/Royal Mail intellectual property contained in your LLPG is provided to your authority through the PSMA as an NLPG Addressing Dataset. Therefore, any onward use by a Contractor of your LLPG, as PSMA NLPG licenced data, will require a PSMA Contractor Licence to be agreed. The PSMA Contractor Licence can be found on the Ordnance Survey website.
3. Outsourcing or sub-contracting the creation, maintenance and provision of Authority Updates to GeoPlace from a Participating Authority:
In the Data Co-operation Agreement (DCA) the licence covering the use of the Supplied Data (defined in the DCA as the: GeoPlace Databases, Ordnance Survey Data, Royal Mail Data and VOA Data) for the creation, maintenance and provision of Authority Updates to GeoPlace is detailed in the main agreement as part of the DCA documentation. This licence is limited to these processes and does not cover any usage of LLPGs and/or LSGs and/or the NLPG and/or the NSG either internally within your Authority or within any sub-contracting arrangement established by your Authority for the use of this data, (see 2) above).
Therefore, in order to licence the Supplied Data as part of the provision of Authority Updates to GeoPlace, to an outsourced LLPG and/or LSG maintenance contractor, you will need to agree the terms (see DCA clauses 2.2, 6.1.4, 21.3 and 21.4) no less onerous than those set out in: a) the Contractor/Agent Licence contained in Schedule 4 of the DCA; and also b) the Royal Mail terms as Appendix 1 to Schedule 4 contained in Schedule 7 of the DCA documentation.
Please note: that if your Authority does enter into a sub-contracting or outsourcing arrangement in order for Authority Updates to be sent to GeoPlace, the name and contact details of the sub-contractor must be sent by email to GeoPlace, to: [email protected] within thirty (30) Working Days of their appointment in accordance with clause 21.4 of the DCA.
4. Passing NSG data for use by a Contractor: Use of NSG data is underpinned by the licence for Ordnance Survey material and intellectual property provided under the PSMA. You will need to agree a PSMA Contractor Licence with your contractor to enable their use of the NSG. The PSMA Contractor Licence can be found on the Ordnance Survey website.
5. Passing LSG data for use by a contractor: Use of LSG data is underpinned by the licence for Ordnance Survey material and intellectual property provided under the PSMA. You will need to agree a PSMA Contractor Licence with your contractor to enable their use of your LSG. The PSMA Contractor Licence can be found on the Ordnance Survey website.
6. Outsourcing or sub-contracting the creation, maintenance and provision of Authority Updates to GeoPlace from a Participating Authority:
In the Data Co-operation Agreement (DCA) the licence covering the use of the Supplied Data (defined in the DCA as the: GeoPlace Databases, Ordnance Survey Data, Royal Mail Data and VOA Data) for the creation, maintenance and provision of Authority Updates to GeoPlace is detailed in the main agreement as part of the DCA documentation. This licence is limited to these processes and does not cover any usage of LLPGs and/or LSGs and/or the NLPG and/or the NSG either internally within your Authority or within any sub-contracting arrangement established by your Authority for the use of this data, (see 5) above). Therefore, in order to licence the Supplied Data as part of the provision of Authority Updates to GeoPlace, to an outsourced LLPG and/or LSG maintenance contractor, you will need to agree the terms (see DCA clauses 2.2, 6.1.4, 21.3 and 21.4) no less onerous than those set out in: a) the Contractor/Agent Licence contained in Schedule 4 of the DCA; and also b) the Royal Mail terms as Appendix 1 to Schedule 4 contained in Schedule 7 of the DCA documentation.
Please note: that if your Authority does enter into a sub-contracting or outsourcing arrangement in order for Authority Updates to be sent to GeoPlace, the name and contact details of the sub-contractor must be sent by email to GeoPlace, to: [email protected]within thirty (30) Working Days of their appointment in accordance with clause 21.4 of the DCA
ESUs should only be split where there is a junction between two or more streets. Where the physical nature of the street does not change, and there is no legal restriction over use of the highway, then all additional information should be dealt with using part street records where possible.
If the physical nature of the street changes, for example, it moves from a carriageway to a pedestrian way, then a split in the ESU can occur.
If a there is a specific legal restriction in who can use the street, for example, the highway dedication changes from a Bridleway to a Street Open to all Vehicles, then a split in the ESU can occur.
An obstruction should be reported when something that physically obstructs a street user from traveling along it from one end to the other. Some examples are; bollards (raising or fixed), gates, plant pots, raised bridge etc. Obstructions can occur on any ESU or at the junction with another ESU (where it would need to be added to both ESUs).
ESUs should only be split at an obstruction where without the obstruction it would still be considered a junction. For example, if that obstruction wasn't there, would the ESU be considered to be continuous?
If travel is not possible from one side of the obstruction to the other by any means, for example, if a there is a continuous brick wall between the two ESUs then this should be considered as separate streets.
Under DTF8.1, Highway Authorities can now submit within their ASD files and type 61 Interest Record requesting all notices on a neighbouring authorities USRN.
The interested authority must not enter the neighbouring authorities USRN in their LG (Streets data file). The type 61 Interest Record requirements are:
USRN: Neighbouring authorities USRN.
SWA_ORG_REF_AUTHORITY: The interested authorities, authority code (not the neighbouring authority).
STREET_STATUS = Blank (The authority that submits and maintains the data will enter this).
INTEREST_TYPE = 8 - All Notices.
DISTRICT_REF_AUTHORITY = Specified OD districts that the notices should go to.
Alternatively authorities can still request that the neighbouring authority enter a type 61 Interest Record requesting all notices on their behalf.
How to record Highways England, Network Rail, TfL and Welsh government maintained streets in DTF 8.1
Whole USRN has maintenance responsibility to Highways England, Network Rail, TfL and Welsh government.
USRNs wholly maintained by Highways England, Network Rail, TfL and Welsh government are required to hold type 61 Interest and type 62 Construction Record information under DTF8.1. Specific codes have been created to reflect this information:
Type 61 Interest Record:
STREET_STATUS = 4 - Maintenance responsibility is to another Highway Authority.
INTEREST_TYPE = 8 - All notices.
SWA_ORG_REF_MAINTAINING = 0011, 0016, 0020, 7093 (Dependant on which National/Regional Highway Authority maintains the street).
Type 62 Construction Record:
REINSTATEMENT_TYPE_CODE = 11 - Maintenance responsibility is to another Highway Authority.
CONSTRUCTION_TYPE = 1. Street Reinstatement.
USRN has part maintenance responsibility to Highways England, Network Rail, TfL and Welsh government.
Where USRNs are partly maintained by Highways England, Network Rail, TfL and Welsh government there should be two Type 61 interest records present.
One should reflect the ownership of the Local Highway Authority with the street being recorded as publicly maintainable. The second record should reflect the guidance set out for whole records above for the section maintained by Highways England, Network Rail, TfL and Welsh government.
It is vital that the part road records match with the data submitted by Highways England, Network Rail, TfL and Welsh government to avoid duplication and conflicting maintenance responsibility.
LG14.008 - A type 14 ESU Coordinates Record must not have the same ESUID, ESU_X_COORD and ESU_Y_COORD as another Record.
This compliance check highlights where there are stacked or duplicated coordinate/vertices on an individual ESU.
Under DTF8.1 the start and end coordinates are taken from the type 13 ESU Record and all coordinates will now come through as part of the type 14 ESU Coordinates Record. Due to this change, a new LG14.008 compliance check has been created. These errors were not reported under DTF7.1 although a similar check did exist (14.8).
To remove these errors a Local Highway Authority will need to edit and delete the stacked vertice/coordinate point or alternatively re-digitise the ESU.
AD62.047 If type 61 Interest Record INTEREST_TYPE = 1 and WHOLE_ROAD = 0 present, a REINSTATEMENT_TYPE_CODE must not be present with WHOLE_ROAD = 1.
This compliance check highlights where there is a USRN with two or more part road Interest Records (Type 61) with an INTEREST_TYPE = 1, but only a whole road REINSTATEMENT_TYPE_CODE record.
This is usually where the USRN is part Maintainable at Public Expense and part Private (Neither 1, 2, 4 nor 5), but only has one REINSTATEMENT_TYPE_CODE record when it must have a REINSTATEMENT_TYPE_CODE record (not 9) to reflect the Maintainable at Public Expense part road interest record and a REINSTATEMENT_TYPE_CODE record = 9 (Private) to correspond with the private (not 9) interest record.
There is an exception to this rule where by a street is part private and part prospectively publically maintainable can have a whole road REINSTATEMENT_TYPE_CODE = 9 (Private) record
LG29.001 & AD69.001 - TER_OF_USE must be present and contain the Highway Authority name for the submitting authority and must contain no more than 60 valid characters.
This compliance check highlights where metadata records are missing from the submission files. An LSG Metadata Record (type 29) and ASD Metadata Record (type 69) are mandatory and must be submitted.
Currently your Trailer (type 99) Record will be reported under these compliance checks to highlight missing records. This will eventually be transferred to a critical error.
For any information on what needs to be entered for your metadata records please refer to the DTF8.1 Specification.
|New Unitary |
|Old Authority Code||New Unitary |
|USRN Start||USRN End||Old Authority |
|Old Authority |
|Old Associated |
|Old Associated |
|0615||Crewe and Nantwich District||9800000||9899999|
|4||Cheshire West and Chester||0645||0665||8600000||8699999||0645||Cheshire||80500000||80599999|
|0620||Ellesmere Port and Neston District||13600000||13699999|
|0635||Vale Royal District||14700000||14799999|
|0820||North Cornwall District||27400000||27499999|
|1305||Chester Le Street District||7000000||709999|
|1340||Wear Valley District||42800000||42899999|
|2915||Blyth Valley District||3200000||3299999|
|2920||Castle Mopeth District||6200000||6299999|
|3210||North Shropshire District||28200000||28299999|
|3220||Shrewsbury and Atcham District||3470000||3479999|
|3225||South Shropshire District||36500000||36599999|
|3910||North Wiltshire District||286000000||28699999|
|3925||West Wiltshire District||43800000||43899999|
Advice on how to record Under Construction streets has been agreed by the DECWG, we have created the below table on how to record Under Construction streets in the NSG.
State code to use
Highway Dedication code to use
STREET_STATUS code to use in type 61 Interest Record
Street pegged out on the ground or work started. No highway dedication
1 - Under Construction
12 - Neither 2,4,6,8,9,10 nor 11
3 - Neither 1, 2, 4 nor 5
Dedicated as highway, whether or not work has started, but not yet open
1 - Under Construction
4 to 11 as appropriate
2 - Prospectively Maintainable at Public Expense
This can be done through the Authority Address or Authority Street Custodian login. Under My Account the menu on the left hand side will have a Users Management and Roles Management section where roles can be added and removed from current users and new users can be added.
Please note, you will not be able to remove the role of Address or Street Custodian from yourself, to do this please complete the help form, email [email protected] or call the GeoPlace helpdesk team on 020 7630 4602.
If you have a login to the services area on the GeoPlace website then you can update your name, phone number and address under My Account and User Profile.
To update your email address please either complete the help form, email [email protected] or call the GeoPlace helpdesk on 020 7630 4602.
On the right hand side of the page is a searching pane.
Firstly, choose the layer you wish to carry out a search on from the 'select layer' drop down menu.
Enter your search criteria which could be a UPRN, postcode, USRN, property name, street name etc and click 'Search'.
The first 10 results will be shown in a table underneath the map window and those 10 results will be displayed on the map.
To view information about your selection you can click on the BLPU point or street on the map and an information pane will appear on the left hand side of the screen with details about that record.
You can zoom to one of the individual results by clicking the 'zoom to' button on the right hand side of the record in the results table, or view information about that record by clicking the 'show details' button in the results table.
Previous results will remain in the window in the form of tabs which can be closed by using the x in the corner of the search table.
The size of the map window can be made smaller by clicking on the five dots that appear either at the bottom or the side of the map window and then dragging them to resize the window. This setting will remain for the remainder of your session and will be reset when you log out.