1 Introduction

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

In regard to address expectations, these guidelines cover all languages in the Swiss market

 

2 Address Components

 

 

 

 

 

 

 

 

 

 

 

 

.2.1 Address Expectations for Results

Essential component

Components

POI Name

Street #

Street Name

SubLocality

Locality

Postal Code

Region/State

Country

Result Types

Business / POI

Yes

Yes

Yes

No

Yes

MS: Yes

AC: No

 

No

Optional within Switzerland and in AC

Full Address

Not applicable

MS: Yes

AC: No

Street

Not applicable

No

Optional for results within Switzerland

Sub-Locality

Not applicable

Yes

No

.

Locality

Not applicable

Region/State

Not applicable

Yes

Country

Not applicable

Yes

1.2Language issues
1.2.1Official languages

Switzerland has four national languages: German, French, Italian and Romansh. The language of an address result should match the official language of the result location. For example, an address in Basel should always be in German, while an address in Lausanne should always be in French. Addresses in bilingual areas might have two official names – both are considered equally correct.

1.2.2Dialects

In Swiss German speaking regions, it is possible for official street names to be in Swiss German dialect, for example Mettlengässli. Street names with Swiss German dialects that are listed officially are considered correct and should not be demoted.

1.2.3Umlauts

Within Switzerland, localities whose names begin with an Umlaut should use the alternative umlaut spellings: AE, OE and UE.

Query

Result

Explanation

[Ütikon]

Uetikon, Schweiz

Correct: Ü is a valid variation for UE, but the official name starts with Ue.

[Uetikon]

Ütikon, Schweiz

Partially Correct: the official name starts with Ue and Ü is not commonly used at the beginning of the word

1.2.4Special Character ‘ß’ (Eszett)

In Swiss German, the letter ß is not used. Therefore, the street type ‘Straße’, spelled with the letter ß, is considered incorrect spelling. The correct spelling is “Strasse” or “Str”. If the street type uses the ‘Straße’ spelling, the Address Accuracy should be rated Incorrect: Street Name.

1.3Localities and sub-localities
1.3.1Localities: Ortschaft vs Gemeinde

Switzerland has two types of entities on the locality level: Gemeinden and Ortschaften. Gemeinden are the lowest level of administrative sub-divisions while Ortschaften are the postal localities. In many cases, the Orschaft has the same boundaries and name as the Gemeinde but in some cases, a Gemeinde has more than one Ortschaft. Smaller entities within these localities are considered sub-localities.

An online list with Ortschaften and Gemeinden in Switzerland can be found on the website of the Swiss Land Registry Services (Cadastre) or the correct Ortschaft can be found on the post code (PLZ) search page of the Swiss postal services website.

The locality component in Switzerland address and street results should always be the Ortschaft. If the Gemeinde is returned, and this is different from the Ortschaft, address accuracy should be rated Incorrect – Locality

 

Result Address                                                         Standard Address                                                                        Rating

Kirchweg 16 5314 Böttstein

Kirchweg 16 5314 Kleindöttingen

Incorrect – Locality: The locality returned is the Gemeinde for this address, the correct Ortschaft is Kleindöttingen

Kirchweg 16 5314

Kleindöttingen

Kirchweg 16 5314

Kleindöttingen

Correct: Kleindöttingen is the Ortschaft for this address

 

1.3.2Postal codes for locality and sub-locality results

Postal codes are not expected for locality or sub-locality results. If we do show the locality with a postal code, even if correct, the address accuracy should be rated Incorrect – Other.

Result Address

Standard Address

Rating

Grindelwald Schweiz

Grindelwald Schweiz

Correct: Even though the locality has a single postal code, it should not be returned in our result.

Zürich

Schweiz

Zürich

Schweiz

Correct: Zürich has multiple postal codes, so it is correct to not return one in our result.

Wettstein 4058 Basel Schweiz

Wettstein Basel Schweiz

Incorrect – Other: Even though the sub-locality is covered by a single postal code, which we should not return it.

2.4 Canton abbreviations

Some Ortschaften and Gemeinden are distinguished from others by additional abbreviations of the Canton they are in. If they are present in the official sources listed above, they should be part of the result. The abbreviations, when present, should be ion brackets. When the Canton abbreviation is missing, or present when not next to the names in the official sources rate Incorrect – Locality.

 

Result Address

Standard Address

Rating

Bremgarten (AG) Schweiz

Bremgarten (AG) Schweiz

Correct: This locality requires the abbreviation for the Canton of Aargau

Aesch

Schweiz

Aesch (BL) Schweiz

Incorrect: This locality requires the abbreviation of the Canton of Basel

Bubendorf (BL) Schweiz

Bubendorf Schweiz

Incorrect: This locality does not require a Canton abbreviation according to official sources

3 Business/POI Results

1.1Language issues

For business and POI results, the names should generally be in the language of the market.

For example, both ‘Die Post’ in German and ‘La Poste’ in French are official names of the Swiss postal service, but since the market de_CH indicates the language is German the name should be returned as ‘Die Post’. A result with the name ‘La Poste’ would get the Name Accuracy rating Partially Correct.

However, if the query is in a language other than German and the result matches this language there should be no demotion.

Official names are always considered correct regardless of the test language. The restaurant chain ‘Marché’ is never translated as ‘Markt’ and so it should always appear as ‘Marché’ regardless of the market language.

Query

Result

Rating

[Post]

Die Post, Kramgasse 1, 3011 Bern

Correct: Result matches test and query language

[Post]

La poste, Poststrasse 6, 9200 Gossau

Partially Correct: Result does not match test or query language, but the French name is also officially used by the Swiss Postal Service.

[hotels]

Grand Hotel Les Trois Rois, Blumenrain 8, 4001 Basel

Correct: Result does not match the query or test language; however, the official name of this hotel is in French and will be considered correct, regardless of the test language.

1.2Name Accuracy for Business POIs

Business results can sometimes include the name of the owner or part of the corporate name in the official business name. 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.

Query

Result

Address Rating

[Café Bahnhof Kerzers]

Restaurant Club Café Bahnhof, Inh. Berno Donatina

Bahnhofplatz 16 3210 Kerzers

Partially Correct: the business name can still be recognized, but the owner name doesn’t need to be displayed.

4Rating Expectations
4.1Transit Results
4.1.1S-Bahn stations

S-Bahn station results, the commuter transit networks around urban areas, are considered as equivalent to regular train stations. They are regarded as valid matches for ‘train’-related queries and not demoted for Relevance.

4.1.2Platforms

Platforms where passenger on and off-board trains are considered as stations even if there are no buildings present. They should be considered valid matches for ‘station’ queries and the classification ‘Bahnhof’ is considered correct.

4.2AutoComplete-specific (Umlauts)

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 our suggestion contains the Umlaut mark and the query does not, still consider it a match after considering the location and prominence.

Query String

Possible Suggestion

Explanation

[Zu]

(with a fresh viewport (VP) over central Switzerland)

Zuerich, Schweiz

Match: The query string does not contain the Umlaut but the suggestion should still be considered a match. It is a very well known city in Switzerland and with the VP location, we can consider this a prominent match.

Zürich, Schweiz

If the Umlaut is included in the query string, consider suggestions that contain the Umlaut to be the likeliest match. Since the user took the time to type this, 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 the mark is a common misspelling.

Query String

Possible Suggestion

Explanation

[]

(VP over

Switzerland)

Zug, Schweiz

No Match: The query string contains an Umlaut while the suggestion does not. There is at least one prominent possible suggestion that contains the Umlaut therefore this suggestion should not be considered a match.

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.

Query String

Possible Suggestion Explanation

[Göt]

(small VP over

Stäfa)

Goethestraße, Stäfa Schweiz

Match: The query string contains a diacritical accent while the suggestion does not. However, this can be a common misspelling for this city/street. Consider such common misspellings when deciding if the suggestion is a possible match or not. Relevance will further be based on distance and prominence.

5Routing

Routing is generally a bit harder in Switzerland, since sometimes there is no street level imagery available to confirm the ground truth. It then needs an extra step of research to confirm a (newly built) roundabout, a pedestrian only area etc.

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

5.1U-Turns

There is no clear-cut rule in Switzerland on how to deal with U-turns. The best way to rate such a suggested step is to evaluate the road, through satellite imagery and street imagery, where available.

In general, a U-turn is not possible 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 we would need to 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, it is safe to say that the U-turn is impossible.

5.2Against Traffic/Physically Impossible

In Switzerland there are many one-way streets and also blocked off streets with barriers or bollards. While it sometimes is hard to see in only satellite imagery, we should do our best in researching the access to a street.

Sometimes the blue line misaligns with the satellite imagery. Do not judge Against Traffic, if the route seems to be turning onto the wrong lane. Take a look at the vector

layer and rate accordingly. A user will likely never zoom in closely on the satellite layer and take the wrong lane based on the imagery.

5.3Mountain ranges/Tunnels

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.

 

Leave a Reply

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

Related Post