The purpose of this document is to provide guidance for rating within the German market. As such, these guidelines should be considered supplemental to the Global Guidelines for each mode.
Correct ratings will be the result of thorough Guidelines knowledge combined with efficient research, and good research is based on the use of official sources.
There are two main types of official sources which should be used for different components of the results: business sources and governmental sources. Important: if there are no official sources available, make sure to rate Relevance as if the POI exists and Data as Can’t Verify (GL 4.2).
Valid business sources are either websites or social media pages claimed by a business. These are very important sources for evaluation of POI results. They are used to verify:
The main governmental sources are the websites of:
Geodateninfrastruktur Deutschland) are used for verifying address existence, street and locality names (but beware of valid sub-localities within localities) and Pins. In the rare cases that these maps do not give clear evidence of the location of a given address, street imagery, if available, can assist.
Some trades, such as pharmacists or solicitors, can have websites with details on individual members. These can be used to verify POI existence if other sources are lacking, and only if the information is confirmed as recent.
Other commercial map sources can be used to evaluate missing closer results in case of Category queries (for example ‘restaurant’) but each needs to be individually verified as existing via their official websites or claimed social media pages. Other commercial map sources, or other non-official sources, should never be used to verify POI existence or details.
Essential Component? | Components | ||||||||
POI Name | Street # | Street Name | Sub- Locality | Locality | Postal Code | State | Country | ||
Result Types | Business / POI | Yes | Yes | Yes | No*** | Yes | MS: Yes | No | Optional within Germany and in AC |
AC: No | |||||||||
Full Address | Not applicable | MS: Yes | Optional for results within Germany | ||||||
AC: No | |||||||||
Street | Not applicable | No* | |||||||
Sub-Locality | Not applicable | Yes | No** | Yes* | |||||
Locality | Not applicable | No | |||||||
Region/State | Not applicable | No | Yes | ||||||
Country | Not applicable | Yes |
No* | Postal code must be correct when returned. |
No** | Postal code is required if there is a single postal code for the (sub-)locality. |
No*** | Sub-Locality must be correct when returned. |
Yes* | State is not required for Designated Cities (Berlin, Bremen, Hamburg) |
Features without Expected Address and Transit POis | See Global Guidelines |
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.
Query | Result | Name Rating |
[Die Buhne] | Buhne DorfstraBe 26a 16761 Hennigsdorf | Partially Correct: the business name is missing the article ‘Die’. |
Business results in Germany can sometimes include the name of the owner.
Query | Result | Name Rating |
[Autohaus und Tankstelle Mensing] | Autohaus und Tankstelle Mensing, Inhaber Gerd Mensing, Burgstemmer StraBe 3, 31171 Nordstemmen | Partially Correct: the business name can still be recognized, but the owner name doesn’t need to be displayed. |
Business results in Germany can also include part of the corporate name in the official business name.
Query | Result | Name Rating |
[Hoffner] | Hoffner Mobelgesellschaft GmbH & Co. KG, Markische Spitze 13, 12681 Berlin | Partially Correct: the business name can still be recognized, but the corporate info doesn’t need to be displayed. |
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.
Query | Result | Name Rating |
[Brienner Strasse, 80333 München] | Brienner StraBe, 80333 München | Correct: result matches the query 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.
Query | Result | Name Rating |
[Hotel Bareiss] | Hotel BareiB, Hermine-Bareiss- Weg, 72270 Baiersbronn | Partially Correct: the correct business name is ‘Hotel Bareiss’ and we should not accept the spelling with ‘B‘. |
One thing we see often in the German 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 “Magdeburg” in front of 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.
Query | Result | Relevance Rating |
[Magdeburg Bahnhofstr. 69 39104 Magdeburg, Deutschland] | Magdeburg Hbf, Bahnhofstr. 69 39104 Magdeburg, Deutschland | Navigational: Result matches the intent, we return the main train station, which can also stand as “Magdeburg”. |
Bahnhofstr. 69 39104 Magdeburg, Deutschland | Bad: Result is just the address, which doesn’t satisfy the user intent. |
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.
Query String | Possible Suggestion | Explanation |
[Bru] (with a fresh viewport (VP) over part of Germany and Belgium) | Bruessel, Belgien | Match: The query string does not contain the Umlaut but the suggestion should still be considered a match. It is a major city in Belgium and with the VP location, we can consider this a likely match. |
Brüssel, Belgien |
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.
Query String | Possible Suggestion | Explanation |
[Tü] (VP over Baden- Württemberg) | Tuttlingen, Baden- Württemberg, Deutschland | No Match: The query string contains an Umlaut while the suggestion does not. There are possible suggestions that contain 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 |
[Ülz] | Uelzen, Niedersachsen, Deutschland | Match: The query string contains a diacritic 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. | ||
[Got] | GoethestraBe, Berlin |
4.3 Postal Codes and (Sub-)Localities
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 villages that share a postal code with other localities, but are independent. As long as the locality only has one postal code, it needs to be returned.
Result Address | Standard Address | Rating |
Heiningen Baden-Württemberg Deutschland | 73092 Heiningen Deutschland | Incorrect – Postal Code: The locality has a single postal code, which we should return in our result. |
Koln Nordrhein-Westfalen Deutschland | Koln Deutschland | Correct: Koln has multiple postal codes, so it is correct to not return one in our result. |
66705 Beckingen Saarland Deutschland | 66701 Beckingen Deutschland | Incorrect – Postal Code: We display the incorrect postal code for the locality. |
Sub-Localities
For sub-localities (e.g., Stadtteil, Gemeindeteil), 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. In some cases, settlements or areas are not listed on the postal website. These should be treated as sub-localities.
Result Address | Standard Address | Rating |
Babelsberg-Nord Potsdam Brandenburg Deutschland | Babelsberg-Nord 14482 Potsdam Deutschland | Incorrect – Postal Code: The locality has a single postal code, which we should return with the larger locality in our result. |
Musberg 70771 Leinfelden- Echterdingen Baden-Württemberg Deutschland | Musberg 70771 Leinfelden- Echterdingen Deutschland | Correct: Musberg is a smaller village within Leinfelden-Echterdingen. We need to include the postal code for the larger locality. |
Eppendorf Deutschland | Eppendorf Hamburg Deutschland | Incorrect – Locality: We should include the larger locality, as Eppendorf is part of Hamburg, with multiple postal codes. |
Klein Beuchow Brandenburg Deutschland | Klein Beuchow, 03222 Lübbenau Deutschland | Incorrect – Locality, Postal Code: We should include the larger locality, as Klein-Beuchow is part of Lübbenau, and include the postal code, since Lübbenau only has a single postal code. |
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.
Result Address | Standard Address | Address Rating |
76275 Ettlingen, Karlsruhe | 76275 Ettlingen | Correct w/ formatting issue: Ettlingen is a city in the district Karlsruhe. The district is a correct but unnecessary address |
component in unexpected format and is not part of the standard address format. |
A shown postal district should be considered to be a valid address component if the address is still correct
Result Address | Standard Address | Address Rating |
Am Krahenberg 29 Konradshohe 13505 Berlin Deutschland | Am Krahenberg 29 13505 Berlin Deutschland | Correct: The postal district Konradshohe is a valid non-standard address component. |
Use the Sub-Locality Checkbox when present to report issues regarding Sub-Localities. If the checkbox is not present, continue using “Country specific issue”.
Result Address | Standard Address | Address Rating |
Am Krahenberg 29 Westend 13505 Berlin Deutschland | Am Krahenberg 29 13505 Berlin Deutschland | Incorrect – Sub-Locality: The postal district Westend is an incorrect non- standard address component. |
State should be considered to be a mandatory non-standard address component for (sub- )locality results.
Result Address | Standard Address | Address Rating |
Bergheim Nordrhein-Westfalen Deutschland | Bergheim Deutschland | Correct: The state Nordrhein-Westfalen is a correct non-standard address component. |
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 Germany, 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.