Select to view content in your preferred language

Applying Odd/Even logic when matching to house number range in Point Address Locator

385
2
05-17-2026 09:39 PM
Status: Open
Labels (1)
ToyotaT18
Regular Contributor

When creating a Locator with a 'Point Address' role, there is an option to allow for address point reference records which cover an address number range, ie 'House Number From' and 'House Number To'.

When using the created Locator, a searched address number may be matched to these ranges. For example, a search for '46 SMITH ST' may match to a reference address record of '44-48 SMITH ST', since the searched number falls within the range.

In regions such as Australia and the US, addresses are usually arranged so that Odd numbers are on one side of the street, and Even numbers on the other side. This means that a house number range should only include numbers of one type (odd or even). For example, range 44-48 should include the numbers 44, 46, and 48 only. It should NOT include 45 or 47.

Currently, ArcGIS Pro allows for matches within the range, but does not apply the logic of odd/even matching. When a match is made in this way, the reported match score is 100.0, and the search process appears to halt.

In cases where two ranges exist, eg 44-48 and 45-49, a search for 45 may match (incorrectly) to range 44-48, with a match score of 100.0, and with no other suggested match nominations. This places the record '45' on the incorrect side of the street, and in the incorrect location.

It is suggested Esri implement this odd/even logic for matches to house number ranges in Point Address Locators.

2 Comments
ShanaBritt

@ToyotaT18 When you built the Point Address role locator did you also map the Parity field? The behavior you described is caused by either not mapping the Parity field when building the locator or the parity value for the feature is 3, which means both odd and even values are possible for particular a PointAddress range. The Parity locator role field is described in the following topic and lists the supported values for the field, https://doc.esri.com/en/arcgis-pro/latest/help/data/geocoding/locator-role-fields.html. 

To resolve the problem, map the Parity field and use the correct parity values for odd and even ranges and try not use parity value of 3 for house number ranges. 

Even = 1

Odd = 2

Mixed = 3

ToyotaT18

Ah I think that's it, the 'parity' field in my data was a bit inconsistent. I had tried applying it but got the same result for one of the specific examples I was looking at, which I now realise was due to an 'M' parity type (various other values in there too).

I re-calculated a new parity field with only 'E' or 'O' values (Even/Odd), based on the first house number. And yes now the locator is behaving better, only allowing the geocode when it matches correctly.

Thank you @ShanaBritt for your help with this. Solved!