Yes, applicable end users must use an attribute from the OS Open ID Green List to match the TOIDs, UPRNs or USRNs to their dataset; these attributes are summarised in the bullet points below:
- Feature Geometry (e.g. X, Y coordinates);
- Feature Names (e.g. Address String components);
- All identifiers associated to features (e.g. UDPRN, gssCodes);
- Feature categorisation for OS MasterMap Topography Layer only.
- Any other attribute type identified in the exhaustive ‘OS Open ID Green List’
To be clear, attributes listed on the OS Open ID Green List can be used in matching TOIDs, UPRNs or USRNs as described above, but cannot be made available on the term of the OGL.
Note that the OS Open ID Green List attribution should only be used for matching to another dataset which already has the same attribute present (and which, by way of reminder, must also be one of the four types of dataset described in the section above).
Attributes listed on the OS Open ID Green List can be used in matching TOIDs, UPRNs or USRNs as described above, but cannot be made available on the term of the OGL.
Note that the OS Open ID Green List attribution should only be used for matching to another dataset which already has the same attribute present (and which, by way of reminder, must also be one of the four types of dataset described in the section above).
In addition, nothing in this policy shall permit the end user to (and the end user shall ensure that no sub-licensee shall) re-create, reproduce or represent any attribute from the OS Open ID Green List. For example, it would not be permissible to make available UPRNs with a building number of 1, or UPRNs with a building number of 2, as this would enable reverse engineering of a premium attribute (i.e. the house number).