a. Research the “user’s query” with location intent- Utilize search engines and map applications. These tools will allow you to research possible suggestions, businesses, or POIs that are near the location intent.
c.
Common Mistake 1: Demoting Addresses, when there are no real- world closer results.
Guideline Section: 8.1.1 Address Does not Exist
Query: [2373 chestnut] user located within Fresh Viewport
Correct Relevance Rating: Excellent
Explanation: Query [2373 chestnut] The first step in AC evaluation, is to determine if the result matches the suggestion. The following suggestion of “2373 Chestnut Street, San Francisco, CA” matches the query of [2373 Chestnut], in addition it is located near the user’s location in the fresh viewport. At first glance, we may be inclined to demote based on distance, as it appears that there are closer results. In this, particular case all other pins point to addresses that do not exist in the real world. Per section 8.1.1, “When assessing the distance for valid, existing address suggestions, they should be evaluated only in relation to other existing addressing, including any potential unreturned valid suggestion. Relevance is EXCELLENT.
Common Mistake 2: Utilizing Business/Closed for Addresses that do not exist.
Guideline Section: 6.2.1 Address Does Not Exist
Query: [24 Pembroke Street Oxford OX1 1BP]
Address Accuracy rating: Incorrect – Address Does Not Exist.
Explanation: When checking addresses always use the official postal tool and web research before rating. The Royal Mail address finder confirms there is no number 24 located on Pembroke Street, Oxford so this address does not exist.
Address accuracy should be rated as Incorrect – Address Does Not Exist. Many analysts select Business Closed/Does Not Exist, this should only be used for POI/Business Type Suggestions.
Common Mistake 3: Not Matching the Query String
Guideline Section: 4.1. Matching the Query String
Query: [1-5 Ea] with user inside fresh viewport over London Result: [1-5 West Street, London WC2H 9NQ]
Explanation: Per section 4.1. Matching the Query String, when the suggestion does not match the query string and would be considered useless to the user, it is to be rated Bad. In this case the query is for 1-5 Ea (a likely completion being 1-5 East Street). The resulting suggestion for 1-5 West Street does not match the final portion of the string and is to be rated Bad. In addition, there is no indication this may have been misspelled as there is no similarity between the final portion of the query string and the result.
Common Mistake 4: Omitting all possible suggestions for Query String
Guideline Section: Section 2.1 User query string.
Query: [te] with user inside fresh viewport over London
Explanation: For the query [te] we want to research the location intent, to ensure that they are valid real-world suggestions. For this query string for example, possible nearby results include Tesco, Tesco Pharmacy, tea rooms, tenpin bowling and more, all within a short distance of the location intent, so these all would be valid due to match the general query [te]. Please keep in mind, when approaching autocomplete tasks, we are asked how well the suggestion matches the query terms. Please note, there are times when we may need to consider spelling mistakes, please see below.
Common Mistake 5: Evaluating a suggestion near location intent, and not taking into account user may have misspelled word.
Guideline Section: 4.1.5 Spell Correction
Query: [10 mq] with user inside fresh viewport over Liverpool Result: 10 Mathew St, Liverpool L2 6RE
Explanation: Per section 4.1.5. Spell Correction, when the user query contains a possible typo and the result address contains a string that is one-letter different and in the same vicinity as the key typed, i.e. A and Q on the keyboard, then the result has possible relevance. In this case, the address 10 Mathew St, Liverpool is valid and is the location of the famous Cavern Club. Since there is a direct match nearby, this spell corrected result is considered secondary intent as the user has likely mistyped Q instead of A, and so the correct Relevance rating is Good.
