Austria – Country Specific Guidelines

1 Introduction

The purpose of this document is to provide guidance for rating within the Austrian market. As such, these guidelines should be considered supplemental to the Global Guidelines for each mode.

2 Address Components Overview

.

It is not expected that stairway/entrance and door numbers for addresses within Austria (especially Vienna) are returned. As long as the street name and street number are correct, there should be no demotion. If the query includes additional info, it is sufficient to only return the street number as long as that street number points to one building. If the building block is incorrect, address accuracy should be rated Incorrect – Unit Number.

Generally, if the business name can still be recognized, the rating should be Partially Correct. If the business name can’t be recognized, the rating should be Incorrect.

When articles that are part of official business names are incorrect or missing, the name should be considered Partially Correct.

.

Business results in Austria can sometimes include the name of the owner.

.

Business results in Austria can also include part of the corporate name in the official business name.

.

Queries with the alternative spelling ‘ss’ are considered a valid variation for the special character B. If the query contains the alternative spelling ’ss’, a result that matches the query and contains B will be considered a match and should not be demoted.

.

If a business name contains ’ss’ we should not accept the spelling with ’B’ and vice versa. Therefore, the rating should be Partially Correct.

Search in Austria requires one to judge both distance and user intent in their ratings. Major metropolitan areas in Austria are very dense and users in this market are expected to travel smaller distances than in rural areas. Likewise, rural areas should be more accepting of larger distances.

One thing we see often in the Austrian market is that (main) train stations are queried with a full address. This is not always easy to spot, but can be identified based on how the query looks. The example below lists “Linz” in front a fully formatted address, which indicates that the user is very likely looking for the train station. This is similar to the “Gary Danko” example in the Global Guidelines (10.6.1. Non-Chain Businesses). When there is an extra component in front of a full address, we need to investigate a bit further to see if the intent is a possible POI at or close to the queried address.

.

The first step in determining Relevance is to determine if the suggestion is a match to the query. Umlauts can influence whether or not a suggestion can be considered a match.

Users will sometimes drop the Umlaut while they type for the sake of efficiency. If the query does not contain the Umlaut mark and our suggestion does, it is still a match after considering the location and prominence.

.

If the Umlaut is included in the query string, consider suggestions that contain the Umlaut to be the most likely intent. Suggestions that do not contain the Umlaut should generally not be considered matches. Exceptions to this would be if there are no possible matching suggestions that contain the Umlaut or if including diacritics is a common misspelling.

.

Consider possible common misspellings when deciding if a suggestion is a match based on the presence or absence of an Umlaut in the query string.

Localities

There are different result expectations for postal codes. We differentiate between localities with only a single postal code and ones with multiple ones. If the query is for a locality, which has only one postal code, we need to return the postal code in the result. If we do not show the locality with the correct postal code, the address accuracy should be rated Incorrect – Postal Code.

This also applies to smaller, independent villages that share a postal code with other localities. As long as the locality only has one postal code, it needs to be returned.

Sub-Localities

.

For sub-localities (or neighborhoods in larger cities), we also require the postal code to be included in the result. We need to return the name of the sub-locality and the associated postal code with the larger locality.

.

Results can have non-standard address components that are not part of the standard address format like neighborhood, administrative district or region. To verify the correct format for an address, the official postal service of the test locale should be used as a reference.

If an extra address component that is not part of the standard address format is included in the result address and the address is still correct, consider that component as redundant and rate address accuracy Correct with formatting issue. A short comment describing the issue should be added to the rating.

.

A shown postal district should be considered to be a valid non-standard address component if the address is still correct.

Use the Sub-Locality Checkbox when present to report issues regarding Sub-Localities.

If the checkbox is not present, continue using “Country specific issue”.

State should be considered to be a mandatory non-standard address component for (sub-)locality results.

Generally, there is a lack of street level imagery available, especially in rural areas, to confirm the ground truth, so extra research steps might be needed.

Newspaper articles or published articles on city websites are a good way to confirm a step, as well as pictures of businesses (e.g., 360° imageries) around the questionable area. We can consider those valid sources and should provide a link to the source in the comment section.

There is no clear-cut U-turn rule in Austria, so evaluate the road using satellite imagery and street imagery if available.

In general, a U-turn is not allowed when there is no designated left-turn lane. The car would block cars coming up behind them and create an unsafe situation.

If it is a smaller street with lesser traffic and/or no designated lanes, evaluate the width of the road and if a U-turn could be performed in one turn. If this is not possible and the user would have to reverse half way through in order to perform the U-turn, check for forbidding signs and consider the U-turn unsafe.

Often a route has to cross a mountain range – either by tunnel or a car train. Consider this when a blue line just seems to run off a street into the landscape.