ASSIGN- UPRN address match application - Revision history

DavidStables: DavidStables moved page UPRN address match application to ASSIGN- UPRN address match application

2021-04-08T11:38:08Z

DavidStables moved page UPRN address match application to ASSIGN- UPRN address match application

← Older revision	Revision as of 11:38, 8 April 2021
(No difference)

DavidStables: /* Match responses */

2021-04-06T16:20:30Z

Match responses

@@ Line 119: / Line 119: @@
 |-
 |Match qualifier
-|See values below
+|See values in match algorithm article
 |The qualifier of the match i.e. whether exact or close etc
 |-
+|
 |-
 |Classification
@@ Line 208: / Line 181: @@
 |-
 |Match pattern
-|see values below
+|see values in article on match algorithm
-|For the purposes of match pattern reporting the 9 main address fields are rationalised to 5. Dependent thoroughfare, dependent locality and locality are merged to street. Whilst town is used as a guide, as it is of little value for matching, it is not included.
+|For the purposes of match pattern reporting the 9 main address fields are rationalised to 5 and the match pattern indicates the approximation of the match and any field manipulation that took polace
 |}
 <br />

DavidStables: /* Match responses */

2021-04-06T12:53:55Z

Match responses

← Older revision		Revision as of 12:53, 6 April 2021
Line 92:		Line 92:

	==== Match responses ====		==== Match responses ====
			Whenever there is a positive match, the response includes the qualifier of the match and the pattern of match,


	The following information is provided when there is a match.		The following information is provided when there is a match.
	{\| class="wikitable"		{\| class="wikitable"

DavidStables: /* Match responses */

2021-04-06T12:52:33Z

Match responses

← Older revision		Revision as of 12:52, 6 April 2021
Line 206:		Line 206:
	\|Match pattern		\|Match pattern
	\|see values below		\|see values below
	\|for each of the main 5 fields (flat, ~~bulding~~, number, street, postcode) indicates the degree to which each field is matched and indicates the degree of manipulation or field swapping. A match pattern is built up by one or more of the phrases below i.e. may be more than one manipulation per field		\|For the purposes of match pattern reporting the 9 main address fields are rationalised to 5. Dependent thoroughfare, dependent locality and locality are merged to street. Whilst town is used as a guide, as it is of little value for matching, it is not included.


			For each of the main 5 fields (flat, building, number, street, postcode) the pattern indicates the degree to which each field is matched and indicates the degree of manipulation or field swapping. A match pattern is built up by one or more of the phrases below i.e. may be more than one manipulation per field.

			Match pattern indicators can be conceptualised as a language grammar with the fields being the subjects, the manipulation of the field being the predicate and the qualifier as the object.

			There are around 12 match terms with around 50 or so theoretical combinations of those terms. For example a candidate field may be dropped to match, and matched as a sibling (ds). Applying these to 5 fields results in the potential of 300 million or so different combinations.

			However, with the algorithms being determined by plausibility, not mathematics, only a number end up being used, usually around 200 or so across 100,000 addresses. further restrictions on the combination occur due to implausibility of some field swaps. For example, post codes are never swapped with streets. Streets are not moved to numbers (as this would have occurred during the initial address formatting algorithm)
	\|-		\|-
	\|		\|&
	\|mapped also to		\|mapped also to
	\|indicates a match using more than one candidate field		\|indicates a match using more than one candidate field
	\|-		\|-
	\|		\|>
	\|moved to		\|moved to
	\|Means that the candidate field was moved to another field to match e.g. number moved to flat		\|Means that the candidate field was moved to another field to match e.g. number moved to flat
	\|-		\|-
	\|		\|<
	\|moved from		\|moved from
	\|Means that the candidate field was moved from another field to match on this field		\|Means that the candidate field was moved from another field to match on this field
	\|-		\|-
	\|		\|f
	\|field merged		\|field merged
	\|when moved from and to, the fields are then merged to match		\|when moved from and to, the fields are then merged to match
	\|-		\|-
	\|		\|i
	\|ABF field ignored		\|ABF field ignored
	\|ABP field was ignored in order to match i.e. the ABP address contained more precise detail than the candidate but was unnecessary in order to match. This usually means that the candidate field is null		\|ABP field was ignored in order to match i.e. the ABP address contained more precise detail than the candidate but was unnecessary in order to match. This usually means that the candidate field is null
	\|-		\|-
	\|		\|d
	\|Candidate field dropped		\|Candidate field dropped
	\|The candidate field was dropped in order to match i.. the candidate address has more precise detail than the authority address . The ABP address would probably be null		\|The candidate field was dropped in order to match i.. the candidate address has more precise detail than the authority address . The ABP address would probably be null
	\|-		\|-
	\|		\|a
	\|Matched as parent		\|Matched as parent
	\|The candidate field matched as being at a higher level than the ABP field, for example flat 6 matching to flat 6a		\|The candidate field matched as being at a higher level than the ABP field, for example flat 6 matching to flat 6a
	\|-		\|-
	\|		\|c
	\|Matched as child		\|Matched as child
	\|The candidate field matched as being at a lower level than the ABP field, for example candidate flat 6a, ABP flat 6		\|The candidate field matched as being at a lower level than the ABP field, for example candidate flat 6a, ABP flat 6
	\|-		\|-
	\|		\|p
	\|Partial match		\|Partial match
	\|he candidate field was partially matched to the ABP field or vice versa) typically 2 out of 3 words		\|he candidate field was partially matched to the ABP field or vice versa) typically 2 out of 3 words
	\|-		\|-
	\|		\|l
	\|Possible spelling error		\|Possible spelling error
	\|The candidate field and ABP field were matched using the Levenshtein distance algorithm taking account of mispellings		\|The candidate field and ABP field were matched using the Levenshtein distance algorithm taking account of mispellings
	\|-		\|-
	\|		\|v
	\|Level based match		\|Level based match
	\|The level of a flat in a building (vertical from the street) was used to create the match e.g. 2b for second floor b		\|The level of a flat in a building (vertical from the street) was used to create the match e.g. 2b for second floor b
	\|-		\|-
	\|		\|e
	\|Equivalent		\|Equivalent
	\|The fields are equivalent, albeit not necessarily spelt the same, using various equivalence lists, word swaps, word drops etc		\|The fields are equivalent, albeit not necessarily spelt the same, using various equivalence lists, word swaps, word drops etc

DavidStables at 10:06, 11 August 2020

2020-08-11T10:06:07Z

← Older revision		Revision as of 10:06, 11 August 2020
Line 2:		Line 2:

	== Background and purpose ==		== Background and purpose ==
	~~The background to the objective of matching addresses and UPRN is as follows:~~

	It is well established that a person's health is significantly affected by their environment in which they live and work.		It is well established that a person's health is significantly affected by their environment in which they live and work.

	People live in flats, houses, or are homeless. People work at home, outside, or in offices or factories.		People live in flats, houses, or are homeless. People work at home, outside, or in offices or factories.

	In order to identify or rectify health issues relating to ~~environments~~ it is ~~necessary~~ to evaluate the affect of location, type of property, and occupancy, on the people who live and work in them.		In order to identify or rectify health issues relating to an environment it is often useful to evaluate the affect of location, type of property, and occupancy, on the people who live and work in them.

	~~In order to measure the effects on health~~ it is necessary to ~~link~~ the ~~health records~~ of people to the ~~properties~~ in ~~which they live and work~~.		To perform that evaluation it is of course necessary to know the characteristics of the people who live or work in the property or at a location. The usual way of recording where someone lives is to enter their address. Within the NHS it is common practice to record addresses as provided by the citizen. In doing so, the address is often recorded in a way that is slightly different from another address entry for the same location in another persons record.

	~~In order~~ to ~~create that link~~ it ~~is necessary~~ to ~~identify~~ the ~~relevant property and~~ the ~~usual way in which~~ a property is ~~identified is via the person's home or work address~~.		This leaves the first problem of working out who lives in the same household. They may have slightly different address entries, and whilst a human can usually see they are the same, a computer cannot. Even when the different addresses are matched, this still leaves a second problem of finding out exactly where the address is.

			If various hand entered addresses were to be matched to the one property it would be possible to determine precisely the characteristics of the people living or working at a particular location and property. This matching is labour intensive and problematic.

	There are problems with using addresses as a way of linking:		There are problems with using addresses as a way of linking:
Line 20:		Line 20:
	# Many properties have more than one address that matches the property. For example the local authority may have one address, whilst the post office may have another.		# Many properties have more than one address that matches the property. For example the local authority may have one address, whilst the post office may have another.

	~~One way of resolving this problem is to assign a property identifier to an actual location and link~~ the ~~various addresses~~ to ~~it. When~~ this ~~is done, then by linking a person's health record to this property identifier, issues relating to the property, location and occupancy can be studied, problems can be acted on, and lives will be saved~~.		Luckily, the Ordnance Survey have helped to solve this problem.

	Unique Property Reference Numbers (UPRNs) are property identifiers for every property in Great Britain. Ordnance Survey provides access to these in a number of products, but their AddressBase Premium product is the most comprehensive database. It is derived from local government's NLPG (National Land and Property Gazetteer) as created and maintained by GeoPlace, Ordnance Survey’s OS MasterMap Address Layer 2 and the Royal Mail’s PAF (Postcode Address File). It adheres to British Standard for addressing BS7666, and every property has its Unique Property Reference Number (UPRN) and geographical co-ordinates. It is updated every 6 weeks.		Unique Property Reference Numbers (UPRNs) are property identifiers for every property in Great Britain. Ordnance Survey provides access to these in a number of products, but their AddressBase Premium product is the most comprehensive database. It is derived from local government's NLPG (National Land and Property Gazetteer) as created and maintained by GeoPlace, Ordnance Survey’s OS MasterMap Address Layer 2 and the Royal Mail’s PAF (Postcode Address File). It adheres to British Standard for addressing BS7666, and every property has its Unique Property Reference Number (UPRN) and geographical co-ordinates. It is updated every 6 weeks.
Line 26:		Line 26:
	Furthermore, there is an assured link between all addresses associated with a property over its life cycle, and from local authority and Royal Mail sources.		Furthermore, there is an assured link between all addresses associated with a property over its life cycle, and from local authority and Royal Mail sources.

	That being the case, if there was a service that matched the address from someone's health record to at least ONE of the addresses supplied by Address Base Premium then the UPRN can be derived and linked to the person~~. This will save lives~~.		That being the case, if there was a service or application that matched the address from someone's health record to at least ONE of the addresses supplied by Address Base Premium then the UPRN can be derived and linked to the person.

	Discovery information ~~model~~ supports the mapping of health related addresses to addresses provided by an authoritative organisation, those addresses being a gold standard for pointing to a UPRN. The matching service provides two subtypes of service:		Discovery information service supports the mapping of health related addresses to addresses provided by an authoritative organisation, those addresses being a gold standard for pointing to a UPRN. The matching service provides two subtypes of service:

	# A Web application that people can use to upload a list of addresses and obtain a list of matched addresses and UPRNs (this article)		# A Web application that people can use to upload a list of addresses and obtain a list of matched addresses and UPRNs (this article)
	#[[UPRN address matching API\|A REST API]] that systems can use to request a matched address and a UPRN for that address		#[[UPRN address matching API\|A REST API]] that systems can use to request a matched address and a UPRN for that address

			The remainder of this article discusses the web application

	== Functionality ==		== Functionality ==
	To access the application the user must either be a user of Discovery, or must create their own account in line with [[Identity Authentication Authorisation#Authentication levels\|level 1 authentication]] process. An authenticated user has authority to access the UPRN match user interface.		To access the application the user must either be a user of Discovery, or must create their own account in line with [[Identity Authentication Authorisation#Authentication levels\|level 1 authentication]] process. An authenticated user has authority to access the UPRN match user interface. In addition to address matching, if the user wishes to have additional data, the user must have rights to access the OS ABP data, usually via the open Government license.

	=== Inputting an address ===		=== Inputting an address ===
	There are two main functions available to the user		There are two main functions available to the user:

	# Enter an address of some kind and attempt to get a match		# Enter an address of some kind and attempt to get a match
	# Upload a list of addresses (between 1 and 100,000) and attempt to get a list of ~~matched entries~~		# Upload a list of addresses (between 1 and 100,000) and attempt to get a list of matches

	An additional flag entered by the user indicates whether to match only on residential properties or include commercial matches.		An additional flag entered by the user indicates whether to match only on residential properties or include commercial matches.

	A match is presented in one of three forms and the user can select either/ or:		A match is presented in one of three forms and the user can select either/ or:
Line 50:		Line 52:
	* CSV file. Suitable for importing into Excel (with a note on converting UPRNs to text) or to a database.		* CSV file. Suitable for importing into Excel (with a note on converting UPRNs to text) or to a database.

	The matching details for an address are described in more detail		The matching details for an address are described in more detail below

	=== Address ~~matching information~~ ===		=== Address match response ===
	The following table explains the information returned following a no match.		The following table explains the information returned following a match attempt.

	The term 'Candidate address' is the address entered by the user or submitted in the file. The 'authority address' is an address provided by the Ordnance survery address based premium and may be a post office address or a local authority address.		The term 'Candidate address' is the address entered by the user or submitted in the file. The 'authority address' is an address provided by the Ordnance survery address based premium and may be a post office address or a local authority address.

DavidStables at 09:48, 11 August 2020

2020-08-11T09:48:12Z

← Older revision		Revision as of 09:48, 11 August 2020
Line 1:		Line 1:
	The UPRN address matching application ~~that allows~~ a user to match ~~one or more addresses from a systems~~ address ~~file~~ to an ~~authoritative~~ address, and ~~to allocate a~~ Unique Property Reference Number (UPRN) ~~for~~ the ~~location of that~~ address.		The UPRN address matching application enables a user to match an address to an "official" address, and in the process also provides the Unique Property Reference Number (UPRN) which has been assigned to the official address.

	== Background and purpose ==		== Background and purpose ==

DavidStables: /* Match responses */

2020-08-11T08:29:04Z

Match responses

@@ Line 156: / Line 156: @@
 |Algorithm
+|
-|the code of the algorithm that ended up with the best match
+|the code of the algorithm that ended up with the best match. For example 1-match1  indicates an exact match
 |-
 |ABPAddress
@@ Line 211: / Line 211: @@
 |-
+|
-|>
+|moved to
 |Means that the candidate field was moved to another field to match e.g. number moved to flat
 |}
 <br />

DavidStables: /* Match responses */

2020-08-11T08:17:26Z

Match responses

← Older revision		Revision as of 08:17, 11 August 2020
Line 97:		Line 97:
	!Description		!Description
	\|-		\|-
	\|style width=~~150px~~; \|Address format		\|style width=100px; \|Address format
	\|style width=~~150~~ px; \|good		\|style width=100 px; \|good
	\|Sufficient characters and if there is a post code it is valid		\|Sufficient characters and if there is a post code it is valid
	\|-		\|-

DavidStables: /* Match responses */

2020-08-11T08:17:08Z

Match responses

← Older revision		Revision as of 08:17, 11 August 2020
Line 97:		Line 97:
	!Description		!Description
	\|-		\|-
	\|Address format		\|style width=150px; \|Address format
	\|good		\|style width=150 px; \|good
	\|Sufficient characters and if there is a post code it is valid		\|Sufficient characters and if there is a post code it is valid
	\|-		\|-
Line 215:		Line 215:
	\|}		\|}
	<br />		<br />

	=== Address matching algorithms ===		=== Address matching algorithms ===
	''main article'' [[UPRN address matching algorithm\|UPRN address matching algorithms]]		''main article'' [[UPRN address matching algorithm\|UPRN address matching algorithms]]

	Address matching is surprisingly difficult, and the algorithms used to match addresses are described in more detail by the [[UPRN address matching algorithm\|UPRN address matching algorithms]] article.		Address matching is surprisingly difficult, and the algorithms used to match addresses are described in more detail by the [[UPRN address matching algorithm\|UPRN address matching algorithms]] article.

DavidStables: /* Match responses */

2020-08-11T08:15:43Z

Match responses

@@ Line 113: / Line 113: @@
 |The unique property reference number provided by the Ordnance survey via the Address Based Premium service
 |-
-|Qualifier
+|Match qualifier
 |Equivalent
 |Deprecated. Now Best match. This means that the algorithm thinks that it has found the equivalent entry as being the correct location. This does not mean it is an exact match, only that it thinks that the user 'candidate address' is the same location as the one that is listed below
@@ Line 155: / Line 159: @@
 |-
 |ABPAddress
+|
-|The Address Base Premium address that match to the candidate address
+|mapped also to
 |}
 <br />