HasSubPremise field, which is available in US PDH data. For the full set of address fields, see Address Fields.
Field values
How HasSubPremise interacts with AVC
The value of HasSubPremise should always be interpreted alongside the AVC code. The table below summarises the common combinations.
Scenarios
The following scenarios illustrate how theHasSubPremise flag behaves for different verification outcomes.
Scenario 1: Verified premise level property that contains sub premises
The property has been verified to premise level, so the AVC is
V4. It also contains one or more sub premises, so HasSubPremise is set to Yes.
Scenario 2: Verified sub premise level property
The property has been verified as a sub premise, so the AVC is
V5. A sub premise cannot itself contain further sub premises, so HasSubPremise is set to No.
Scenario 3: Verified premise level property with incorrect sub premise data
The property has been verified to premise level (AVC
V4) because the supplied sub premise information was incorrect. The premise does contain sub premises, so HasSubPremise is set to Yes.
Scenario 4: Verified premise level property with no sub premises
The property has been verified to premise level (AVC
V4) and contains no sub premises, so HasSubPremise is set to No.
Scenario 5: Ambiguous sub premise level property
The AVC code of
A5 means there is more than one close reference data match at sub premise level. Because this is a sub premise level record, the sub premise does not contain further sub premises, so HasSubPremise is set to No.
Scenario 6: No sub premise information
The property was only verified to the thoroughfare (street) level, so no sub premise information is available and
HasSubPremise is returned blank.