# Jobs concepts
The following topics provide foundational knowledge and best practices for using the Amazon Location Service Jobs API. These concepts are essential for effectively implementing Jobs features within your application.
**Topics**
+ [Jobs terminology](jobs-terminology.md)
+ [Job lifecycle](job-lifecycle.md)
+ [Input and output formats](input-output-formats.md)
+ [IAM Execution roles](execution-roles.md)
+ [Error handling](error-handling.md)
+ [Address validation](address-validation-concepts.md)
# Jobs terminology
This section provides essential definitions to understand core concepts within Amazon Location Service Jobs, such as job states, data formats, and processing features.
**Job**
A batch processing operation that performs a specific action on large datasets stored in Amazon S3. Jobs process data asynchronously and return results to a designated output location.
**Job lifecycle**
The sequence of states a job transitions through from creation to completion, including Pending, Running, Completed, Failed, Cancelling, and Cancelled states.
**Execution role**
An IAM role that grants Amazon Location permission to access your Amazon S3 buckets on your behalf. The role must have read permissions for input buckets and write permissions for output buckets.
**Apache Parquet**
A columnar storage file format used for input and output data in Jobs. Parquet provides efficient data compression and encoding schemes for handling complex data in bulk.
**Input schema**
The required structure and field definitions for input data files. Each job action type has a specific schema that input files must conform to.
**Record-level error**
An error that affects individual records within a job. These errors are included in the output file with `ErrorType` and `ErrorMessage` fields, allowing valid records to be processed while identifying problematic ones.
# Job lifecycle
Jobs progress through the following states:
Pending
New jobs begin in this state while waiting for processing resources.
Running
The job has started and is actively processing data.
Completed
The job has finished successfully and results are available in your designated Amazon S3 output location.
Failed
The job enters this state if errors occur during processing. You can obtain error details using the `GetJob` operation.
Cancelling
The job enters this state temporarily when you explicitly cancel it using the `CancelJob` operation.
Cancelled
The job enters this state when the `CancelJob` operation finishes stopping the job.
# Input and output formats
Jobs require input data in [Apache Parquet](https://parquet.apache.org/docs/overview/) format stored in Amazon S3. Your input files must conform to a specific schema corresponding to the action you want to perform. The service writes results back to Amazon S3 in Parquet format, preserving all original input data and adding results from the processed action.
Input files have a limitation of 10 GB per file, and 1 GB per Parquet row-group within the file.
For more information, see [How to prepare input data](https://docs.aws.amazon.com/location/latest/developerguide/preparing-input-data.html) and [How to retrieve results](https://docs.aws.amazon.com/location/latest/developerguide/retrieving-results.html).
# IAM Execution roles
Jobs API operations use an AWS Identity and Access Management (IAM) role to access your Amazon S3 buckets securely. The role you specify in your API requests using the `ExecutionRoleArn` parameter must have permissions to read from your input bucket and write to your output bucket. Amazon Location Service assumes this role on your behalf when running jobs, ensuring secure access to your data without requiring long-term credentials.
For more information, see [Configure IAM permissions](https://docs.aws.amazon.com/location/latest/developerguide/configure-iam-role-policy-credentials.html).
# Error handling
Jobs handle errors at both the job level and individual record level. Job-level errors prevent the entire job from completing and are reported through the job status. These include authentication failures, permission issues, and service errors.
Record-level errors affect individual records and are included in the output file with `ErrorType` and `ErrorMessage` fields, allowing you to identify and address problematic records while still processing valid ones. Common record-level errors include invalid input values or missing required fields.
# Address validation
Address validation jobs process address data to verify and standardize addresses. The service supports both free-form address lines and structured address components, and can optionally enhance results with geographic coordinates and country-specific postal attributes.
Address validation supports addresses from the following countries: Australia, Canada, United Kingdom, and United States.
## Address validation features
Address validation provides the following features for verifying and enhancing address data:
**Address standardization**
Address validation verifies that an address exists and is deliverable by checking it against authoritative address datasets. Address standardization formats addresses according to official postal standards, such as consistent abbreviations, capitalization, and punctuation. It also corrects errors such as spelling mistakes and adds missing address components such as postal codes and street names.
**Enhanced validation**
Address validation jobs support optional additional features that enhance validation results:
+ **Position** — Returns geographic coordinates (longitude and latitude) for validated addresses, enabling you to map addresses or perform geographic analysis. This feature is only available in the United States, Canada, and Australia, and incurs additional costs.
+ **CountrySpecificAttributes** — Provides postal system information specific to each country. For example, US addresses receive USPS data such as delivery point codes and carrier route information, while Australian addresses receive Australia Post identifiers.
For more information about pricing, see [Jobs pricing](jobs-pricing.md).
## Address validation use cases
**Healthcare systems and insurers**
Validate patient and provider addresses for claims processing, care coordination, and regulatory reporting requirements.
**Financial services and insurance carriers**
Standardize customer addresses to support identity verification workflows, risk assessment, and fraud prevention.
**Retail and e-commerce operations**
Clean customer databases to reduce shipping failures, improve delivery rates, and optimize fulfillment costs.
**Transportation and logistics providers**
Validate delivery addresses for route optimization and reduce failed deliveries across last-mile operations.
**Data migration and database maintenance**
Perform one-time database cleanup during system transitions and regularly validate address records to maintain data quality.
**Analytics, reporting, and entity resolution**
Standardize addresses for location-based analytics, demographic analysis, and Customer Relationship Management (CRM) database cleanup through entity resolution workflows.
## Input schema
Address validation jobs require input data with a specific schema. The schema supports both free-form address lines and structured address components, allowing you to submit addresses in the format that best matches your data.
The input schema includes the following fields:
Id
An optional identifier to give to this input record. If provided, it is mirrored in the output file as `Input_Id` to help you correlate output records with their corresponding inputs.
Address lines
Use `AddressLines_1` through `AddressLines_5` for free-form addresses. Enter single-line inputs in `AddressLines_1`. Order multi-line inputs according to regional postal rules, as they would appear on mail.
AddressComponents\$1Country
The alpha-2, alpha-3 character code, or full name of the country where the address is located.
AddressComponents\$1Region
The region of the input address, such as state, province, or territory.
AddressComponents\$1SubRegion
The sub-region of the input address, such as county.
AddressComponents\$1Locality
The locality of the input address, such as city or town.
AddressComponents\$1PostalCode
The postal code of the input address.
AddressComponents\$1Street
The street name of the input address.
AddressComponents\$1AddressNumber
The address or house number of the input address.
AddressComponents\$1Unit
The unit of the input address.
AddressComponents\$1UnitDesignator
The unit designator or type of the input address, such as Apt, Suite, or \$1.
**Note**
When combining both AddressLines and AddressComponents in a request, enter first-line address components (AddressNumber, Street, Unit, and UnitDesignator) in AddressLines. Enter last-line components (Locality, Region, SubRegion, Country, and PostalCode) through AddressComponents.
### Sample Python script to create input data
The following Python script creates a sample Parquet file with address data:
```
import pyarrow as pa
import pyarrow.parquet as pq
data = [
{
"Id": "record-001",
"AddressLines_1": "Pike Place",
"AddressLines_2": "Apartment 4B",
"AddressLines_3": None,
"AddressLines_4": None,
"AddressLines_5": None,
"AddressComponents_Country": "USA",
"AddressComponents_Region": None,
"AddressComponents_SubRegion": None,
"AddressComponents_Locality": None,
"AddressComponents_PostalCode": "98101",
"AddressComponents_Street": None,
"AddressComponents_AddressNumber": None,
"AddressComponents_Unit": None,
"AddressComponents_UnitDesignator": None
},
{
"Id": "record-002",
"AddressLines_1": "2901 E Madison St",
"AddressLines_2": None,
"AddressLines_3": None,
"AddressLines_4": None,
"AddressLines_5": None,
"AddressComponents_Country": "USA",
"AddressComponents_Region": None,
"AddressComponents_SubRegion": None,
"AddressComponents_Locality": None,
"AddressComponents_PostalCode": "98112",
"AddressComponents_Street": None,
"AddressComponents_AddressNumber": None,
"AddressComponents_Unit": None,
"AddressComponents_UnitDesignator": None
}
]
schema = pa.schema([
("Id", pa.string()),
("AddressLines_1", pa.string()),
("AddressLines_2", pa.string()),
("AddressLines_3", pa.string()),
("AddressLines_4", pa.string()),
("AddressLines_5", pa.string()),
("AddressComponents_Country", pa.string()),
("AddressComponents_Region", pa.string()),
("AddressComponents_SubRegion", pa.string()),
("AddressComponents_Locality", pa.string()),
("AddressComponents_PostalCode", pa.string()),
("AddressComponents_Street", pa.string()),
("AddressComponents_AddressNumber", pa.string()),
("AddressComponents_Unit", pa.string()),
("AddressComponents_UnitDesignator", pa.string())
])
table = pa.Table.from_pylist(data, schema=schema)
pq.write_table(table, 'addresses.parquet')
```
For file size limits, see [Prepare input data](preparing-input-data.md).
## Output schema
Address validation jobs produce output that includes standardized address components, validation results, and optional additional feature data. The following sections describe the address validation-specific output fields.
For general output schema information and how to retrieve results, see [Retrieve job results](retrieving-results.md).
### Output address fields
Standardized address components with an `Output_` prefix, formatted according to regional postal rules.
#### Complete list of output address fields
Output\$1AddressId
A unique identifier for the returned address.
Output\$1AddressLines\$11
The first line of the complete returned address written on multiple lines, as it should appear on a piece of mail. It is formatted according to the regional postal rules.
Output\$1AddressLines\$12
The second line of the complete returned address written on multiple lines, as it should appear on a piece of mail. It is formatted according to the regional postal rules.
Output\$1AddressLines\$13
The third line of the complete returned address written on multiple lines, as it should appear on a piece of mail. It is formatted according to the regional postal rules.
Output\$1AddressLines\$14
The fourth line of the complete returned address written on multiple lines, as it should appear on a piece of mail. It is formatted according to the regional postal rules.
Output\$1AddressLines\$15
The fifth line of the complete returned address written on multiple lines, as it should appear on a piece of mail. It is formatted according to the regional postal rules.
Output\$1Address\$1Label
The assembled address built out of the address components, according to the regional postal rules.
Output\$1Address\$1Country\$1Code2
Alpha-2 character code of the country.
Output\$1Address\$1Country\$1Code3
Alpha-3 character code of the country.
Output\$1Address\$1Country\$1Name
Full name of the country.
Output\$1Address\$1Region\$1Code
Abbreviated code for the region.
Output\$1Address\$1Region\$1Name
Full name for the region.
Output\$1Address\$1SubRegion\$1Code
Abbreviated code for the sub-region.
Output\$1Address\$1SubRegion\$1Name
Full name for the sub-region.
Output\$1Address\$1Locality
The locality component of the address, such as city or town.
Output\$1Address\$1PostalCode
The full postal code component of the address.
Output\$1Address\$1PostalCodeDetails\$1Base
The base segment of the postal code.
Output\$1Address\$1PostalCodeDetails\$1Extension
The extension or add-on segment of the postal code.
Output\$1Address\$1Street
The full street component of the address.
Output\$1Address\$1StreetComponents\$1BaseName
Base name part of the street name.
Output\$1Address\$1StreetComponents\$1Prefix
Directional identifier that precedes, but is not included in, the base name of a road.
Output\$1Address\$1StreetComponents\$1Suffix
Directional identifier that follows, but is not included in, the base name of a road.
Output\$1Address\$1StreetComponents\$1Type
Street type part of the street name such as `ST`, `AVE`, `BLVD`.
Output\$1Address\$1StreetComponents\$1TypePlacement
Defines if the street type is before or after the base name. (`BeforeBaseName` or `AfterBaseName`)
Output\$1Address\$1AddressNumber
The address or house number component of the address.
Output\$1Address\$1SecondaryAddressComponents\$1Unit\$1Number
The alphanumeric identifier of the unit secondary address component.
Output\$1Address\$1SecondaryAddressComponents\$1Unit\$1Designator
The designator of the unit secondary address component, as it appears in the address label.
Output\$1Address\$1SecondaryAddressComponents\$1Floor\$1Number
The alphanumeric identifier of the floor secondary address component.
Output\$1Address\$1SecondaryAddressComponents\$1Floor\$1Designator
The designator of the floor secondary address component, as it appears in the address label.
### Address metadata
Metadata about the address and delivery characteristics.
Output\$1AddressMetadata\$1DeliveryIndicators\$1Mailable
Indicates whether an address is mailable. Values: `true`/`false`
Output\$1AddressMetadata\$1DeliveryIndicators\$1Locatable
Indicates whether an address is locatable. Values: `true`/`false`
### Validation results
Overall validation quality metrics for the address.
Output\$1ValidationResults\$1ValidationGranularity
Indicates the overall level of granularity that the returned address was validated to. Values:
+ `Premise` – All components to the address number level were validated
+ `Street` – All components to the street level were validated
+ `LocalityAndPostalCode` – Locality, PostalCode, and Country were validated
+ `Locality` – Locality and Country were validated
Output\$1ValidationResults\$1MatchConfidence
Indicates the overall confidence level in the address match performed during the address validation process. Values: `High`, `MediumHigh`, `Medium`, `MediumLow`, `Low`
Output\$1ValidationResults\$1MatchConfidenceScore
Provides a precise score for the match confidence. Ranges from 0 - 1.0, with 1.0 indicating a perfect match.
### Component validation status
For each address component, two fields indicate validation results:
+ `Status` fields indicate the validation status: `Validated` or `Unconfirmed`
+ `StatusDetail` fields provide additional detail about the validation status:
+ `NotFound` – Component was not found or empty.
+ `StandardizedNoMatch` – Component was parsed and standardized, but not identified in reference data.
+ `OutOfRange` – Component was not identified, reference data suggests the component is out of range or unknown.
+ `Corrected` – Component was corrected using reference data.
+ `Exact` – Component was validated without changes.
+ `Alias` – Component was validated using reference data alias.
+ `Appended` – Component was appended using reference data.
#### Component validation field pairs
Output\$1ValidationResults\$1Components\$1Address\$1Country\$1Status
Validation status for the country component.
Output\$1ValidationResults\$1Components\$1Address\$1Country\$1StatusDetail
Detailed validation status for the country component.
Output\$1ValidationResults\$1Components\$1Address\$1Region\$1Status
Validation status for the region component.
Output\$1ValidationResults\$1Components\$1Address\$1Region\$1StatusDetail
Detailed validation status for the region component.
Output\$1ValidationResults\$1Components\$1Address\$1Locality\$1Status
Validation status for the locality component.
Output\$1ValidationResults\$1Components\$1Address\$1Locality\$1StatusDetail
Detailed validation status for the locality component.
Output\$1ValidationResults\$1Components\$1Address\$1Street\$1Status
Validation status for the street component.
Output\$1ValidationResults\$1Components\$1Address\$1Street\$1StatusDetail
Detailed validation status for the street component.
Output\$1ValidationResults\$1Components\$1Address\$1AddressNumber\$1Status
Validation status for the address number component.
Output\$1ValidationResults\$1Components\$1Address\$1AddressNumber\$1StatusDetail
Detailed validation status for the address number component.
Output\$1ValidationResults\$1Components\$1Address\$1PostalCodeDetails\$1Base\$1Status
Validation status for the postal code base component.
Output\$1ValidationResults\$1Components\$1Address\$1PostalCodeDetails\$1Base\$1StatusDetail
Detailed validation status for the postal code base component.
Output\$1ValidationResults\$1Components\$1Address\$1PostalCodeDetails\$1Extension\$1Status
Validation status for the postal code extension component.
Output\$1ValidationResults\$1Components\$1Address\$1PostalCodeDetails\$1Extension\$1StatusDetail
Detailed validation status for the postal code extension component.
Output\$1ValidationResults\$1Components\$1Address\$1SecondaryAddressComponents\$1Unit\$1Status
Validation status for the unit component.
Output\$1ValidationResults\$1Components\$1Address\$1SecondaryAddressComponents\$1Unit\$1StatusDetail
Detailed validation status for the unit component.
Output\$1ValidationResults\$1Components\$1Address\$1SecondaryAddressComponents\$1Floor\$1Status
Validation status for the floor component.
Output\$1ValidationResults\$1Components\$1Address\$1SecondaryAddressComponents\$1Floor\$1StatusDetail
Detailed validation status for the floor component.
### Additional feature output
If you requested additional features when starting the job, the output includes:
#### Position
Geographic coordinates in World Geodetic System (WGS 84) format.
Output\$1Position\$1Longitude
The longitude coordinate in World Geodetic System (WGS 84) format.
Output\$1Position\$1Latitude
The latitude coordinate in World Geodetic System (WGS 84) format.
#### Country-specific attributes
Country-specific postal and census data. The available fields vary by country.
##### Australia
##### AustraliaPost
Output\$1CountrySpecificAttributes\$1AUS\$1AustraliaPost\$1DeliveryPointIdentifier
An eight-digit code developed by Australia Post which enables each delivery point in Australia to be uniquely identified.
##### Census
Output\$1CountrySpecificAttributes\$1AUS\$1Census\$1MeshBlockId
Mesh Blocks are the smallest geographic areas defined by the ABS and form the building blocks for the larger regions of the Australian Statistical Geography Standard (ASGS). They broadly identify land use such as residential, commercial, primary production and parks.
##### Gnaf
Output\$1CountrySpecificAttributes\$1AUS\$1Gnaf\$1AddressClass
The address class, which is constructed using a combination of address elements. Values include: `A` (Alias), `P` (Principal), `PP` (Principal Primary), `PS` (Principal Secondary), `AP` (Alias Primary), `AS` (Alias Secondary).
Output\$1CountrySpecificAttributes\$1AUS\$1Gnaf\$1GnafPid
The Persistent Identifier is unique to the real world feature this record represents. The Persistent Identifier (PID) is a 14-character alphanumeric string uniquely identifying each G-NAF address.
Output\$1CountrySpecificAttributes\$1AUS\$1Gnaf\$1LegalParcelId
This field within G-NAF is designed to hold a unique identifier for the land parcel associated with a specific address. Parcel ID, representing the Lot on Plan description. Used by government agencies. Format varies.
Output\$1CountrySpecificAttributes\$1AUS\$1Gnaf\$1StatisticalArea1
Geographic areas built from whole Mesh Blocks. Whole SA1s aggregate to form Statistical Areas Level 2 (SA2s). Statistical Area Level 1 (SA1) field representing a geographic area used in the Census. Seven-digit unique code.
##### Canada
##### CanadaPost
Output\$1CountrySpecificAttributes\$1CAN\$1CanadaPost\$1BuildingType
A code that denotes whether the building is a business building or an apartment building. Valid values are: `1` = Residential, `2` = Commercial.
Output\$1CountrySpecificAttributes\$1CAN\$1CanadaPost\$1RecordType
Defines the type of record in the Address Lookup and the Text Lookup files. Values include: `A1` (High-rise building), `B1` (Large Volume Receiver), `C1` (Government Address), `D2` (LVR Served by Lock Box), `E2` (Government Served by Lock Box), `F2` (LVR Served by General Delivery), `11` (Street), `21` (Street served by route), `32` (PO Box).
##### Census
Output\$1CountrySpecificAttributes\$1CAN\$1Census\$1DisseminationArea
Uniquely identifies a dissemination area. It is composed of the two-digit province or territory code, the two-digit census division code and the four-digit dissemination area code.
Output\$1CountrySpecificAttributes\$1CAN\$1Census\$1Division
Uniquely identifies a census division. The first two digits of the CDuid identify the province or territory (PR).
Output\$1CountrySpecificAttributes\$1CAN\$1Census\$1MetropolitanArea
Formed by one or more adjacent municipalities centered on a population centre (known as the core).
Output\$1CountrySpecificAttributes\$1CAN\$1Census\$1Subdivision
Uniquely identifies a census subdivision in the country. The province/territory, census division, and census subdivision (municipality) codes combine to represent the Standard Geographical Classification (SGC).
Output\$1CountrySpecificAttributes\$1CAN\$1Census\$1Tract
Identifies a census tract within a CMA/CA. To uniquely identify each census tract in its corresponding census metropolitan area or tracted census agglomeration, the three-digit CMA/CA code must precede the census tract 'name.'
##### United States
##### USPS
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1CarrierRoute
A group of mailing addresses within a ZIP code that the USPS groups together to make the mail delivery process more efficient. In the same way that ZIP codes divide up the country into different areas carrier routes divide up those ZIP codes.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1DefaultFlag
Indicated the record processed obtained a match to a highrise, rural route or street default record in the ZIP \$1 4 product. `Y` - The default flag indicator is set, `N` or Blank - Acceptable.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1DeliveryPoint\$1Barcode
2-digit delivery point of the house/box.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1DeliveryPoint\$1CheckDigit
A number that is added to the sum of the other digits in the DPBC to yield a number that is a multiple of ten.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1Elot\$1AscendingDescendingFlag
The ascending/descending code indicates the approximate delivery order within the sequence number.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1Elot\$1SequenceNumber
Enhanced Line of Travel (eLOT) sequence number to help mailers sort mailings in a way that aligns with the carrier's delivery path. Indicates the first occurrence of delivery made to the add-on range within the carrier route.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1NonDeliverableRecord
Field on the Stage I file indicates the address test question is a valid match to a record on the ZIP \$1 4® Product. However, the match is made to a non-deliverable (ND) type record. `Y` - Record is an ND type, Blank - Record is not an ND type.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1PoBoxOnlyFlag
There is a portion of the City State product that contains PO Box Only Delivery Zones. The file layout utilizes `P` as the Copyright Detail Code which is different from the existing ZIP. Classification code `P` located in the thirteenth (13) position of the City State detail record that indicates there are PO Box and other types of deliveries to the community. These zones have no other form of postal delivery.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1RecordType
Type of the address record that matches the input address such as Firm (`F`) General Delivery (`G`) Highrise (`H`) P.O. Box (`P`) Rural Route (`R`) or Street Record (`S`).
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1RuralRouteDefault
Indicates a rural route match. `Y` - the address matched to a rural route record. `N` or blank - the address did not match to a rural route record.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1Urbanization
Puerto Rican urbanization name.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1ZipValid
True/false flag that indicates a valid zip code. Indicates whether the address record can be added to Form 3553. Five-digit validation requires that the last line values of city state and ZIP Code correspond to each other.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1Zip10
10-digit ZIP Code (ZIP \$1 4) with dash separator.
Output\$1CountrySpecificAttributes\$1USA\$1Usps\$1Zip9
9-digit ZIP Code (ZIP \$1 4).
##### Census
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1BlockId
2020 Census Block ID.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1CombinedStatisticalArea\$1Number
Combined Statistical Area (CSA) number.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1CombinedStatisticalArea\$1Name
Combined Statistical Area (CSA) name.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1CoreBasedStatisticalArea\$1Number
Core Based Statistical Area (CBSA) number.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1CoreBasedStatisticalArea\$1Name
The name of the Core Based Statistical Area (CBSA) in which the address is located.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1CountyFipsCode
The county FIPS code.
Output\$1CountrySpecificAttributes\$1USA\$1Census\$1MetropolitanAreaFlag
Indicates whether the Core Based Statistical Area (CBSA) in which the address is located is a metropolitan area or a micropolitan area (`Y`/`N`).
##### United Kingdom
##### RoyalMail
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1SubBuilding
The sub-building name and/or identifier of the address.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1ThoroughfareName
The base name of the street or thoroughfare of the address.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1DependentThoroughfareName
The double dependent thoroughfare of the address. This is used when there are named thoroughfares within other named thoroughfares.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1DependentLocality
The dependent locality of the address. This is used when there are thoroughfares with the same or similar names within a locality.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1DoubleDependentLocality
The double dependent locality of the address. This is used when there are multiple thoroughfares with the same or similar names within a dependent locality.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1OrganizationName
The name of the organization registered at the address.
Output\$1CountrySpecificAttributes\$1GBR\$1RoyalMail\$1Udprn
The Unique Delivery Point Reference Number (UDPRN) is a unique, 8-digit code assigned by Royal Mail to addresses within the UK.