Rating for Relevance

According to section 1.3.3. Result Relevance rating, the relevance rating will take into consideration user intent as well as distance/prominence. Relevance is always rated independently of any data (name, address, or pin) inaccuracies under the assumption that the result exists and is correct.

Relevance ratings can be given starting from Navigational (if applicable) to Bad.

Remember that for any rating below good, we need to select either User intent issue or Distance

Prominence issue. And please don’t forget that leaving a comment is mandatory.

Steps for Rating Relevance

1.First, we need to understand the user’s intent. To do this we need to use research and local knowledge and the information provided such as the user viewport, location and viewport age. We also need to decide what the location intent is for the query. Is there an implicit or explicit location modifier? We can use official resources like a businesses’ official websites, national postal service websites, and government websites to confirm the user intent.
2.Decide what query type it is. Is it an address query, POI, Business, or Category query?
3.Finally, we can review the result of the query to understand if it would satisfy the users intent. By doing this we would need to use the information we have gathered from the first step and use real world research to determine the relevance of the result that is returned.

 

2.3.2. Implicit Location

If the user’s location intent is not expressly stated in the query, for example [chinese] or [479 margarita ave], use the user location, viewport location, and viewport age to determine the area of expected results.

Viewport

User

Location Intent

Fresh

Inside Viewport

When the user is within a fresh viewport, take the user location as location intent. Results are generally expected in or near the viewport, and results inside the area cannot be rated Bad because of distanee alone.

Outside

Viewport

Results are expected in or near the viewport area. All relevant results inside the viewport are eligible for; a rating of Excellent. If no results can be found in or near the viewport, consider the user location a secondary location intent.

Missing

When the user is missing, the viewport is the location intent.

Stale

Inside Viewport

When the viewport is stale, consider only the user location as location intent.

Outside

Viewport

Missing

Use the stale viewport as location intent wtlen the user location is missing.

Viewport Age Missing

Present or

Missing

Consider the viewport fresh when tfle viewport age is missing.

Missing entirely

Present

The user location sets the location intent when the viewport is not present.

Missing

When the user location and viewport are missing, the test locale becomes the location intent with a strong focus on prominent results.

5.1.8. Lack of Connection

Previously the guidelines contained the concept of ‘Associated Entities’. The concept of Associated Entities has been removed and no longer applies. This means that a result cannot satisfy user intent only because of its containment relationship with the POI/business in the query. Therefore, according to the guideline section 5.1.8. Lack of Connection, If the result does not satisfy the user intent either because there is no relationship between the query and the result or because the connection between the query and the result will not be immediately obvious to the user, rate the relevance Bad. The relevancy rating for this result is therefore Bad.

User Query

Result

Type of Connection

Description

[airport]

Santa Cruz Boardwalk Santa Cruz

None

Does not satisfy user intent: Research shows th at there is no connection between the query and the re:suit. Rate Bad.

[Raging Waters 2333 South White Rd San Jose]

2333 South White Rd

San Jose

None

Does not satisfy userintent: Result is for the correct address, 1:JUtdoe; not include the business named in the query, sc) users will have no way of know ing if this is truly connected to the business or not. Rate Bad.

[Raging Waters]

2333 South White Rd

San Jose

None

Does not satisfy user intent: Query is the name of a business and result is for the correct address, but does not include the business name. Users will have no way of knowing whether or not this address is connected to the business they asked for. Rate Bad.

[valley fair mall]

Macy’s 2801 Stevens Creek Blvd, Santa Clara,

None

Does not satisfy user intent: Result is for a store, not a mall. This store is insidethe requested mal1, but users Willi nave no way of knowing this simply frc>m looking at the result. Rate Bad

[macy’s]

Westfield Valley Fair 2855 Stevens Creek Blvd, Santa Clara,

None

Does n<Jt satisfy user intent: Result is for a mall, not a store. This mall contains the requested store, but users will have no way of knowing this. Rate Bad.

Example 1

Viewport Center: 51.767580, -8.613280 User Location: 51.770116, -8.656872 Before evaluating the suggestions, you will need to understand what the user wanted to find when they made the query. To determine user intent, use a combination of your own research and local knowledge plus the information provided in the rating interface, such as user location, user viewport and viewport age.

This query is for an eircode, the user is tyring to find out the address and maybe business associated with this eircode. According to eircode.ie this eircode is for Unit 7-10, North Link Business Park, Mallow Road, Cork.

Location and Real-World Results

The result is for a business, Wood 10, with an address with a partial eircode, Mallow Road, Cork, T23, Ireland.

Name should be rated Correct because it’s matching the one on the offical Facebook page:https://www.facebook.com/thewood10/

The address should be Boland House, Mallow Road, Cork, according to the official Facebook page:https://www.facebook.com/thewood10/

We cannot verify pin because we don’t have the exact address or full Eircode.

Wrong is also accepted because of the pin drop on the Facebook page.

 

 

Example 2

Viewport Center: 53.640474, -6.722065 User Location: 53.167863, -6.143081

Understanding User Intent. Before evaluating the suggestions, you will need to understand what the user wanted to find when they made the query. The query is a chain business. The VP is stale, so user’s location is the location intent. This result is the closest one to the user – Excellent. GL. 2.3.2. Implicit Location, 12.4. How do I know what the location intent is when user is outside/inside a stale viewport?

Location and Real-World Results

 

 

Example 3 –

Viewport Center: 54.079997, -6.907436 User Location: 54.052730, -6.855470 Before evaluating the

 suggestions, you will need to understand what the user wanted to find when they made the query. To determine user intent, use

 a combination of your own research and local knowledge plus the information provided in the rating interface, such as user location, user viewport and viewport age.

This query is for an eircode, the user is tyring to find out the address and maybe business associated with this eircode. According to eircode.ie this eircode is for Tullyrain, Shantonagh, Co Monaghan.

As we can see the Pin is dropped in front of the house and should be rated Approximate

.

.

.

.

 

 

 

 

Location and Real-World Results

Pin is dropped in front of the house and should be rated Approximate

 

..

Example 4 –

Viewport Center: 53.348877, -6.387254

User Location: 53.327640, -6.218260

Understanding User Intent. Before evaluating the suggestions, you will need to understand what the user wanted to find when they made the query. The query is a chain business. The viewport is fresh, and the user is not in it results – we expect results in the fresh viewport.

This result is too far from the viewport and there are so many closer options – Bad/Acceptable. GL 5.11 Rating for User -Inside and Outside Viewport

.Location and Real-World Research

..

SanllThe address is the same on the website, however, eircode.ie says this eircode has been deactivated. The correct address according to eircode.ie is Unit 5, Greegcourt, Parnell Street, Dublin 1, D01 C7K6, Ireland. Aa a result the address should be rated Incorrect.

.

.

 

.

Example 5 –

Viewport Center: 51.906160, -8.473118

User Location: 51.907543, -8.472868

The user has issued a query for an address. The viewport in Cork city is Fresh and user is located not far away. Results closest to the Viewport will be eligible for ratings beginning at Excellent and will be demoted from Good to Bad based on their distance from there.

Having established the user intent, we can now research the query to see if there are matching results.

 

Location and Real-World Research

We can see that the closest Castle Street is not far away in Cork City centre. This is the most likely target of the
query. Zooming in closer we see that
the pin for 27 Castle Street is not on a specific building but is in the middle of the street. This often indicates
that the queried result does not exist.

Research is now required to determine of number 27 exists or not. Using resources such as anpost.ie or eircode.ie we can search the address to determine it’s validity.

Searching with An Post’s Check Address function we see that no matching result is returned. Returning to our TryRating results we see that the result we are asked to rate is 26 Castle Street. The result we are rating is 26 Castle Street. This address is on the Castle Street that is closest to the fresh viewport. A full address with Eircode is returned. We must now research this address to see if it exists. We can search either with the address or the Eircode.

 

Searching the Eircode on eircode.ie returns the result address of 26 Castle Street, Cork verifying it’s existence. This is the closest matching result to the query. Section 10.3 of the Search Guidelines – Query address does not exist – tells us that the closest matching result that does exist is eligible for a rating of Excellent.

 

Example 6 –

Viewport Center: 53.341815, -6.249828 User Location: 53.341370, -6.245730

The viewport is fresh, and the user is located inside the FVP. Search guidelines section 2.3.2 tells us in this situation that the user is location intent. The query intent is for a train station.

The user is in Dublin City center. Searching a map application, we see there are several results available in the

Looking closer at the map we can see that not all of these are train stations, and most are Luas (Tram) stops.

Pearse, Tara Street & Grand Canal Dock are the 3 closest train stations to the user.

Location and Real-World Research

We are being asked to rate is the result for Tara Street Station.

Considering the location of the user we see that Pearse Street is the closest station to the user and that Tara Street and Grand Canal Dock are equidistant from the user.

This result is eligible for a rating of GOOD as 1 other station is closer to the user. See Search Guidelines 5.16.1 Transit Queries

The result address is just the locality. Address is rated Correct as per Search Guidelines section 8.3.2.1. Minimum Address Component

.

 

 

 

 

 

 

 

Example 7 – Incorrect Postal Code

Viewport Center:52.648257, -8.578696 User Location: 52.668460, -8.591310

The user has issued a query for a chain business – Supermac’s – with an explicit location modifier “Castletroy” . We see from guideline section 2.3.1 that when an explicit location modifier like “near me” or “nearest” the user is telling us exactly where they would like to see results. In this case the specified locality and not the user or viewport location is considered the primary location intent. Branches of this chain restaurant in the queried locality will be eligible for a rating of Navigational if there is only 1 or rated from Excellent to Bad depending on location and distance to the queried locality.

 

 

 

Location and Real-World Research

Having established the user intent we can now research the query to see if there are matching results. Research on the Supermac Store Locator page https://supermacs.ie/locations/

Example 8 –

Viewport Center:

User Location:

The user has issued a query for a chain business – Bank of Ireland There is no location modifier so location intent is implicit. We look for the viewport age and user location. This is a Fresh viewport and the user is inside the fresh viewport. Search guideline 2.3.2 tells us in this situation that results are expected close to the user. Researching on the Bank of Ireland branch locator page https://www.bankofireland.com/br anch-locator/ we can see that there are several branches of the bank in the Cork City area.

Location and Real-World Research

The result we are rating in this case is the branch at 32 South Mall. Other results are closer to the user and are valid results appearing on the Bank of Ireland map also. The result is one of a cluster of results in Cork city center. We can see from the branch locator page that this is the second closest result to the user and is eligible for a rating of Good. See the Guidelines section 5.11 for rating results where the user is inside the FVP.

.

Example 9 –

Viewport Center: 53.275157, -9.044747

User Location: 53.283690, -8.986820

We are being asked to rate the result for a car park in the city center of Galway. When we check the Address data component, we can see that the address is missing the required Eircode and considered Incorrect.

The Address should be Fairgreen House, Fairgreen Road, Galway, H91 AXK8, Ireland

FAIRGREEN HOUSE

FAIRGREEN ROAD

GALWAY

H91AXK8

Example 10 –

Viewport Center: 52.342247, -6.485869

User Location: 52.294920, -6.503910

For this task, we can see that the user has queried for an implicit intent: “Restaurants” in Wexford city with a fresh viewport age. We can already see the viewport lies around Wexford and the user is outside of it. It is very important to know now, that the viewport age is fresh, because in this case the viewport is our primary location intent: GL Section 5.4 Distance “Fresh viewport, user outside” example.

Now that we have determined the user intent, we need to check, if the result presented satisfies it and the provided details are correct. Also, we need to clarify if the POI is valid. For this, we need to use our official resources. To confirm validity, name, category and address, we use the result “Ferrycarrig Hotel” official website: https://www.ferrycarrighotel.ie/

 

Location and Real-World Research

In this case, we need to check this result fits to the queried “restaurants” category. We can see from the URL the result does not satisfy the query’s primary users’ intent of ‘restaurants’ because it’s a hotel. Even though the hotel has a couple of dining options and indeed it is in the viewport, since the result is for the hotel entity and relevance should be rated as bad.

 

Viewport Center: 53.341815, -6.249828 User Location: 53.341370, -6.245730

Example 11 –

For this task, we can see that the user has queried for an implicit intent: “Train Stations” in Dublin c

ity center with a fresh viewport age. We can already see the relatively small viewport lies in Dublin city center and the user is inside of it. That means the user is our location intent and all ratings should be based on the user`s location: GL Section 5.4

The query intent is for a train station.

Research shows this is the second closer to the user and is rated Good. 5.16.1 Transit Queries

 

 

 

Location and Real-World Research

To confirm validity, name, category and address, we use the result “Dublin Connolly” station`s (Irish Railway) official website:

https://www.irishrail.ie/en-ie/station/dublin-connolly

We can see from the website the name is correct but the category is incorrect. Our POI`s correct category should be “train station”. Therefore, Name should be rated as “Incorrect” due to See GL section 6.3.1. Correct Category.

General Information

Location

5 minutes walk from city centre.

Station Address

Dublin Connolly AmSens Street

Dublin 1

Eircode

DOI V6V6

Station: +353 (0)1 703 2358 or +353 (0)1 703 2359

 

Example 12 –

The result “parking” was provided with an address and therefore a pin we can find, which exact POI this is. Address and Pin are pointing to “Fairgreen House” and a parking area, which belongs to Fairgreen House, called “City Park @ City Centre @ Fairgreen Road” on our research map: https://bit.ly/3w8tzoi

As mentioned above, when checking the address, we need to study the Country Specific Guidelines for Ireland and use this together with the GL section 7 Address Accuracy.

Location and Real-World Research

In this case, to confirm the address of the parking lot, we use the https://finder.eircode.ie/ If we type in “Fairgreen House”, we can see, it is also marked as a parking a lot and the address is provided.

We can see the Pin lands on the car park`s rooftop, therefore the rating is Perfect https://bit.ly/3kN4XvZ

.

 

Leave a Reply

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

Related Post