5.3.9.1
Sometimes, Streets have named terraces running next to the main carriageway but not separated from the carriageway. In an LLPG these are recorded as terraced properties as Primary Addressable Objects (PAONs) and Secondary Addressable Objects (SAONs).
5.3.9.3
Figure 8 - Type 1 Street Name (Terrace)
If a named terrace appears to run alongside a carriageway but is separated from the main carriageway, for example by being on a different level, and if there is no access from one to the other then that terrace must be recorded as a type 1 Street.
5.3.9.4
If there is a legacy case where a terrace exists alongside an officially named Street, and the terrace is also an officially named Street, then a type 1 Street may be created for the terrace. For an example, see Figure 8. The type 1 Street for the terrace must also have the following attributes:
- Street STATE = 5 – Street for addressing purposes only (type 11 Street Record). See, Section 9.2
- STREET_STATUS = 5 – Street outside the scope of EToN (type 61 Interest Record). See, Section 14.3
5.3.9.5
If the Authority Address Custodian creates a Street with a Street STATE = 5 – Street for addressing purposes only, and if that Street state code is not available in the Authority Address Custodian’s software, then the Authority Address Custodian must inform the Authority Street Custodian that this Street was created for addressing purposes only. The Authority Street Custodian must then allocate the Street STATE = 5 – Street for addressing purposes only, in the LSG.
5.3.9.6
If a terrace is created as a type 1 Street, the Street alongside which it exists must not be designated as a type 2 Street. This is because if a Street is officially named, the official name applies to the whole width of the Street unless the other side has a different official Street Name.