10.3.4.1
When splitting a Street at an administrative boundary, take a copy of the coordinates and pass them onto the bordering LHA.
10.3.4.2
When receiving coordinate information on Streets crossing an administrative boundary, check the Street exists in your gazetteer and check that the coordinates provided coincide with the administrative boundary in the same location.
10.3.4.3
Download a copy of the neighbouring LHA’s data to edge match and check there are no coordinate differences where the Streets must match. This must be undertaken in conjunction with the neighbouring LHA Authority Street Custodian
10.3.4.4
Try to ensure the neighbouring LHA uses the same version of the administrative boundary data, see Section 10.3.2.
10.3.4.5
If a Street crosses an administrative boundary more than once along its length, ensure that all the crossing point coordinates are sent to the adjoining LHA, as each point must correspond in each LSG.
10.3.4.6
Authority administrative boundaries often weave across a Street several times as opposed to falling either side of a Street. This results in a Street crossing into a neighbouring authority in several places. To avoid creating large quantities of USRNs for the same Street, a non-continuous street, is created by each LHA involved, holding only ESUs for the sections of Street that reside within their own LHA.
10.3.4.7
Where administrative boundaries cross a Street at multiple points, create a single USRN with ESUs that cover only the sections of Street which reside within the LHA. This results in a series of ESUs that do not appear to be linked up in the LSG. These do, however, form a complete Street in the NSG when combined with the neighbouring LHAs geometry.
10.3.4.8
Where a boundary runs along the centreline of a classified unnumbered Road (“C” Road) the two neighbouring authorities need to consult with each other concerning which number to use.