Common Mistake 1: Is this a reasonable address?

Per Section 4, all query addresses that have been rated Invalid should be analyzed to see if they are Reasonable. A Reasonable Address must refer to a location that exists in the real world, such as:

a small area on one side of a block (less than 5 rooftops)
an area of one side of a street equal to or smaller than a block
an address/postal code that defines a small area within eyesight
a plaza-like feature, such as a city square or strip mall
a residential complex equal to or less than the size of two blocks, such as an apartment building/community or townhomes
a small area that cannot be further simplified in terms of address components.

Example #1

Query Address: Bayview Ave & York Mills Rd, North York, ON

Some analysts are missing the scenario where the query is for an intersection which does not qualify as a Specific Address; however, it does qualify as a Reasonable address as per the intersection example in section 4 of the guidelines.

This queried intersection is Reasonable as it exists in the real world, and the area is smaller than a block.

 

Example #2

Query Address: Yaletown, Vancouver, BC

Yaletown is a neighbourhood in downtown Vancouver. It is outlined in red on the map. Since this area includes several streets, it can be broken down into more specific address components, so it is Unreasonable.

 

Example #3

Query Address: Washington Ave, Brooklyn, NY

The query address is a road that is Unreasonable as it extends through several blocks, there are over 5 rooftops, and it doesn’t meet the eyesight rule.

Common Mistake 2: Address Accuracy – Street Numbers with extensions

Some analysts are not fully understanding the Country-Specific Guidelines (Section 1.4.1) when rating addresses with Street Numbers that contain a letter in them. It is important to remember that these are considered street numbers rather than unit number indicators.

Per Section 1.4.1, “Street numbers in Canada are usually represented by a single number, however, occasionally a street number can have a suffix by adding on a letter or fraction. If the suffix is incorrect or missing, consider this an issue with the Street number and not the Unit/Apt.”

Also, per the Address Verification Guidelines, Section 7.3.1. Incorrect – Street Number, if the response address contains an incorrect or missing street number and no longer refers to the same unique address as the query address, rate address accuracy as Incorrect – Street Number.

Example

Query Address: 1500A Cumberland St, Cornwall, ON

Response Address: 1500B Cumberland St, Cornwall, ON

The Response Address is rated Incorrect – Street Number as the response has the incorrect extension ‘B,’ referring to a different address than the query address.

Common Mistake 3: Address Accuracy – Unit Number

Some analysts are rating Response Addresses that match most of the query but missing only the unit number as Incorrect when the address is still a valid address.

Per “Section 7.3.2. Incorrect – Unit/Apt,” when the query address contains a unit number and the response address does not, rate:

Correct – if the address is valid without a unit number

Incorrect – Unit/Apt – if the address is invalid without a unit number

Example

Query Address: 101-4256 Portage Rd, Niagara Falls, ON L2E 6A4

Response Address: 4256 Portage Rd, Niagara Falls, ON L2E 6A4

The query address contains a specific unit number while the response address does not – both addresses are valid because either of them point to a specific single-building location. The address, with or without the unit number, points to only one location. In this scenario, the unit number does not have to be in the Response address for it to be Correct.

 

Alternatively, if the query address with a unit number is located in a ‘multi-building residential complex’ (ie. Townhouse complex), the response address is only valid if it has the unit number.

***Note that if a query address does not have a unit number but the response address does, the response address is rated Incorrect – Unit/Apt.

Common Mistake 4: Query Address Validity – Query contains extra information

Per Section 3.2, when the Query Address contains extra information or components, it does not automatically make the query Invalid. If the Query Address can be deemed valid as confirmed by Canada Post even though extra information that isn’t necessary is contained within the query part, the address is still Valid.

Example #1

Query Address: Bell Trinity Square 483 Bay St, Toronto, ON M5G 2C9

This query address contains the name of the business centre. Business names are not considered address components, but query addresses that contain them can still be Valid when it’s a full address that points to one single location.

Example #2

Query Address: 10111 104 Ave NW, Edmonton, AB T5J 0J4 Unit 105

This address is a single building with several units. Unit 105 does not exist in real life at this location, but the address is still Valid without it. In this scenario, a unit number is not needed to differentiate this location from others with the same address as there are no others with this same address. The query address is Valid.

 

Common Mistake 5: Query Address Validity – Query address is no longer valid

Sometimes the Query Address can be confirmed as Invalid through web research even though it is recognized by Canada Post. In this situation, it is likely that a valid address existed in the past, but the address no longer exists in the real world or the street name changed.

Example

Query Address: 955 Rue Amherst, Montréal, QC H2L 3K4

This address is recognized by Canada Post. However, research confirms that the street name was changed, and the address is now ‘955 Rue Atateken, Montréal, QC H2L 3K4.’ This is considered an Invalid query address.

 

Common Mistake 6: Pin Accuracy

Analysts sometimes misunderstand rating Pin Accuracy for Address Verification tasks. In Address Verification, the pin is rated in relation to the Query Address only (when the address is ‘Valid’ or ‘Invalid but Reasonable.’)

Research is required from multiple reliable online resources for accurate pin ratings. Reliable resources can include:

Online map sources with vector and hybrid views
Street-level imagery in maps applications (can also be found on claimed social media sites, user review sites, articles, etc.)
Official venue maps and directories
Government project registries

Reminders:

Always verify pin placement using the layers in the Tryrating tool, not from the source where the coordinates were gathered. You must rate based on what you can see in the Tryrating layers.
When there is a difference between where the pin drops in vector vs satellite layers, use the map layer that is more generous toward the ideal pin location
Use the Half n’ Half Rule to determine Approximate and Next Door pin locations
There is no ‘Next Door’ rating for shared spaces. For example, two buildings in the same

shared parcel can never be rated as next door to one another.

For addresses encompass entire business complexes (such as universities, hospitals, and airports), the entire parcel within the boundaries is rated Perfect. There are no Approximate or Next Door ratings.)

Example #1: Approximate Rating

When the query address is located in a building with multiple street numbers, and the pin falls on the correct building, but not over the correct street number’s location, the pin is rated Approximate. This also applies if the pin lands in the correct property/parcel, but not on the rooftop. For example, if the pin lands on another rooftop within the same parcel or on the parking area, it is also rated Approximate. See Section 6.2. Single Rooftop, “One Building with Multiple Street Numbers in a shared parking lot.

Query Address: 967 Fennell Ave E, Hamilton, ON L8T 1R1

In this example, it can be confirmed through online resources and street-level imagery that the query address belongs to the business located next to where the pin lands, so the pin is Approximate.

Example #2: Wrong Rating

When the Pin falls on the rooftop across the street from the correct location, the pin is rated Wrong.

Query Address: 615 Ellice Ave, Winnipeg, MB R3G 0A4

In this example, it can be confirmed that the pin lands across the street from the query address. Street-level imagery in the maps application shows the street number on the storefront of the indicated building below. The pin is rated Wrong.

 

 

Example #3: Can’t Verify

When there is no imagery available to confirm the correct location of the pin, rate Can’t Verify.

Query Address: 920 Remour Ln, Mt Shasta, CA 96067

In this example, there is no street imagery in the area, so the exact location of this address cannot be determined even though its existence is confirmed by the postal service. All pins dropped within the highlighted area is rated Can’t Verify. All pins outside that area would be rated Wrong. See ‘Section 6.1.5. Can’t Verify’ for these examples (page 32).

Example #4: Pin Accuracy when rating Intersections

When rating Reasonable Addresses, such as Intersections, it is rated using the Campus Rule. The entire area of the intersection is rated as Perfect.

Query Address: Valencia St & Cunningham Pl, San Francisco, CA 94110

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post