Street and City names/nl: Difference between revisions View history

Street and City names/nl
(Updating to match new version of source page)
(Updating to match new version of source page)
Line 4: Line 4:




<div lang="en" dir="ltr" class="mw-content-ltr">
* For most [[Road types|road types]] both <i>Street</i> and <i>City</i> name should be specified. Check the  [[Road types|road types]] for examples.
* For most [[Road types|road types]] both <i>Street</i> and <i>City</i> name should be specified. Check the  [[Road types|road types]] for examples.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
* Specify <i>Street</i> and optional <i>City name</i> in case of [[Ramp|Ramps]]
* Specify <i>Street</i> and optional <i>City name</i> in case of [[Ramp|Ramps]]
* Specify only <i>Street</i> for [[Freeway|Freeways]].  
* Specify only <i>Street</i> for [[Freeway|Freeways]].  
* Specify only a <i>City</i> name for [[Runway/Taxiway|Runways]] but also for [[Roundabout|Roundabouts]].
* Specify only a <i>City</i> name for [[Runway/Taxiway|Runways]].
* Specify <i>City name</i> and optional <i>Street</i> for [[Parking Lot Road|Parking Lot Roads]].
* Specify <i>City name</i> and optional <i>Street</i> for [[Parking Lot Road|Parking Lot Roads]] and for [[Roundabout|Roundabouts]].
</div>




<div lang="en" dir="ltr" class="mw-content-ltr">
==City names==
==City names==
Citynames of BeLux are locked and can be consulted.  
Citynames of BeLux are locked and can be consulted.  
* For Belgium this can be found via the list in GoogleDoc [https://docs.google.com/spreadsheets/d/1sczAFxO5slNqjdFgnNRcGLHuXBIL6JFRprUFopS5WsE/pub?single=true&gid=1&output=html Official Waze citynames for Belgium].
* For Belgium this can be found via the list in GoogleDoc [https://docs.google.com/spreadsheets/d/1sczAFxO5slNqjdFgnNRcGLHuXBIL6JFRprUFopS5WsE/pub?single=true&gid=1&output=html Official Waze citynames for Belgium].
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Some situations are unclear, for example a city divided in two. We refer to the Wallon city of Geest-Gérompont-Petit-Rosière. We input the city as one city. Stick to the names in the list. Adding a new City name, non existent on the list, will result in an error when you try to save in [[Waze Map Editor|WME]].
Some situations are unclear, for example a city divided in two. We refer to the Wallon city of Geest-Gérompont-Petit-Rosière. We input the city as one city. Stick to the names in the list. Adding a new City name, non existent on the list, will result in an error when you try to save in [[Waze Map Editor|WME]].
</div>




<div lang="en" dir="ltr" class="mw-content-ltr">
== Street names ==
== Street names ==
All segments should get a City name, and most segments also get a Street name. When entering the Street name, we use the Street name in the official language of the area. For the cities in the bilingual Region of Brussels, we use the French version. As a reference, you can find the official language in the City names list.
All segments should get a City name, and most segments also get a Street name. When entering the Street name, we use the Street name in the official language of the area. For the cities in the bilingual Region of Brussels, we use the French version. In multi-lingual areas, use alternate names to allow searches in the other languages.  As a reference, you can find the official language in the City names list.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
As there is a City name and Street name, it's possible there is also a road number. This road number should be positioned before the Streetname. Some examples:
As there is a City name and Street name, it's possible there is also a road number. This road number should be positioned before the Streetname. Some examples:
* N200 - S103 - Haarlemmerweg
* N200 - S103 - Haarlemmerweg
* N68 - E421 - Route d'Eupen
* N68 - E421 - Route d'Eupen
* N451 - Kieldrechtsebaan
* N451 - Kieldrechtsebaan
</div>


=== Streets with 2 names (left and right) ===
<div lang="en" dir="ltr" class="mw-content-ltr">
* Don't combine both street names, this lead to false search results.
== Private Roads ==
* Use the name of the side with the most houses.  
If a street name is looked up without a house number, you will get a location centrally on the combination of the segments with that name. We don't want this to result in a location in a dead end "private" road.<br>
* Ad the other name as an alternative name.
Therefore don't use a street name on private roads (Driveway to 1 or more places). Instead use RPP (with entry point) to locate those places.<br>
* Use [[Residential Place|Residential Point Place (RPP)]] for the house numbers on the side of the alternate street name.
By using an RPP, you still get the correct location when searching with street name and house number. <br>
Always check whether a segment has an "official" street name. In Flanders this can be done via GRB or Wegenregister. For Wallonia use PICC [[Tools|(OpenMaps)]]
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
== Streets with 2 names (left and right) ==
* Don't combine both street names in the (main) address entry field, this may significantly disrupt search results!
* So use the name of the side with the most houses in the (main) address entry field.
* Add the other name in the alternative name of address entry field.
* Use [[Residential Place|Residential Point Place (RPP)]] for the house numbers on the side of the alternative street name.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
==== Split segment (left, right) ====
==== Split segment (left, right) ====
Previously, a segment was split to assign both street names. However, this can cause errors in the ETA and it gives a messy map. This method is therefore currently not recommended and should certainly not be applied on roads of the type [[Primary Street|Primary street]] or higher.
Previously, a segment was split to assign both street names. However, this can cause errors in the ETA and it gives a messy map. This method is therefore currently not recommended and should certainly not be applied on roads of the type [[Primary Street|Primary street]] or higher.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
==== Double name ====
==== Double name ====
It is not recommended to give a segment a double name "leftstreet - rightstreet".
It is not recommended to give a segment a double name "leftstreet - rightstreet".
Line 42: Line 67:
* The synchronization with the search results of Google maps is disrupted
* The synchronization with the search results of Google maps is disrupted
* You must use [[Residential Place|Residential Point Place (RPP)]] on both sides of the street
* You must use [[Residential Place|Residential Point Place (RPP)]] on both sides of the street
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
==Pronounciation==
==Pronounciation==
Remarks on the pronounciation of street names in the [[Text to speak]] navigation:  
Remarks on the pronounciation of street names in the [[Text to speak]] navigation:  
Line 48: Line 75:
* Abbreviated titles like ''Prof'' and ''Dr'' should be spelled with a period after the abbreviated title, like ''Prof.'' and ''Dr.'' to get the pronounciation right.
* Abbreviated titles like ''Prof'' and ''Dr'' should be spelled with a period after the abbreviated title, like ''Prof.'' and ''Dr.'' to get the pronounciation right.
* If the offical Street name differs from the correct pronounciated Street name the official Street name should be defined as alternative name.<br />
* If the offical Street name differs from the correct pronounciated Street name the official Street name should be defined as alternative name.<br />
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
==Routing==
==Routing==
There can be a problem with navigating to a fully defined destination - [[House numbers|house number]] present or [[Residential Place]] defined - when there is closeby a segment with a matching Alternative Street name. For a complete description and the solution of this problem see [[Routing to matching Alternative Street names]]. <br />
There can be a problem with navigating to a fully defined destination - [[House numbers|house number]] present or [[Residential Place]] defined - when there is closeby a segment with a matching Alternative Street name. For a complete description and the solution of this problem see [[Routing to matching Alternative Street names]]. <br />
</div>
   
   


<div lang="en" dir="ltr" class="mw-content-ltr">
See for house numbers the [[House numbers|House numbers page]]
See for house numbers the [[House numbers|House numbers page]]
</div>


   
   
{{Bottomline}}
{{Bottomline}}
[[Category:Road attributes{{#translation:}}]]
[[Category:Road attributes{{#translation:}}]]

Revision as of 10:10, 16 August 2023

We are currently updating the pages to include all regionally different guidelines. If you find inconsistencies, please refer to the English page. Thank you!
Other languages:


  • For most road types both Street and City name should be specified. Check the road types for examples.


City names

Citynames of BeLux are locked and can be consulted.

Some situations are unclear, for example a city divided in two. We refer to the Wallon city of Geest-Gérompont-Petit-Rosière. We input the city as one city. Stick to the names in the list. Adding a new City name, non existent on the list, will result in an error when you try to save in WME.


Street names

All segments should get a City name, and most segments also get a Street name. When entering the Street name, we use the Street name in the official language of the area. For the cities in the bilingual Region of Brussels, we use the French version. In multi-lingual areas, use alternate names to allow searches in the other languages. As a reference, you can find the official language in the City names list.

As there is a City name and Street name, it's possible there is also a road number. This road number should be positioned before the Streetname. Some examples:

  • N200 - S103 - Haarlemmerweg
  • N68 - E421 - Route d'Eupen
  • N451 - Kieldrechtsebaan

Private Roads

If a street name is looked up without a house number, you will get a location centrally on the combination of the segments with that name. We don't want this to result in a location in a dead end "private" road.
Therefore don't use a street name on private roads (Driveway to 1 or more places). Instead use RPP (with entry point) to locate those places.
By using an RPP, you still get the correct location when searching with street name and house number.
Always check whether a segment has an "official" street name. In Flanders this can be done via GRB or Wegenregister. For Wallonia use PICC (OpenMaps)

Streets with 2 names (left and right)

  • Don't combine both street names in the (main) address entry field, this may significantly disrupt search results!
  • So use the name of the side with the most houses in the (main) address entry field.
  • Add the other name in the alternative name of address entry field.
  • Use Residential Point Place (RPP) for the house numbers on the side of the alternative street name.

Split segment (left, right)

Previously, a segment was split to assign both street names. However, this can cause errors in the ETA and it gives a messy map. This method is therefore currently not recommended and should certainly not be applied on roads of the type Primary street or higher.

Double name

It is not recommended to give a segment a double name "leftstreet - rightstreet".

  • The name gets to long to show in the app.
  • This can cause problems when looking up.
  • The synchronization with the search results of Google maps is disrupted
  • You must use Residential Point Place (RPP) on both sides of the street

Pronounciation

Remarks on the pronounciation of street names in the Text to speak navigation:

  • The primary Street is used.
  • Abbreviated titles like Prof and Dr should be spelled with a period after the abbreviated title, like Prof. and Dr. to get the pronounciation right.
  • If the offical Street name differs from the correct pronounciated Street name the official Street name should be defined as alternative name.

Routing

There can be a problem with navigating to a fully defined destination - house number present or Residential Place defined - when there is closeby a segment with a matching Alternative Street name. For a complete description and the solution of this problem see Routing to matching Alternative Street names.


See for house numbers the House numbers page




  Hoofdpagina | Index