(Redirected from Main page/Roads)
- 1 Introduction
- 2 Road types
- 3 Naming Conventions
- 4 Road shields
- 5 Dual Carriageways
- 6 Ramp mapping
- 7 Lay-bys
- 8 Railways
- 9 Ferries
- 10 Bridging segments
|This forms part of UK Editing Best Practice. Please read in conjunction with the USA global page on Road types, which has more specific information about each Road type and their characteristics.|
Using the correct Road type and naming of segments is a key part of mapping in Waze. Road type influence route planning, particularly on long journeys where Waze will prioritise the major Road types. The naming of segments give users a consistent experience and can also influence routing and detour mechanisms.
|Be aware of the WME language setting! This article uses localised names which can be found when using the English (UK) language.|
The following convention should be followed where possible, although it is acknowledged that you may need to deviate from it in some circumstances.
|Waze Road Type||UK Road Types|
|All Motorway & Motorway class A roads (locked to L5) M60 A1(M)|
|A-class roads that are classified as Primary Routes (locked to L4) A4600|
|Non-primary A-class roads A614|
|B-class roads and unclassified roads carrying heavier traffic, often seen on Ordnance Survey maps in yellow or orange. B547|
|Urban Streets, low traffic rural roads|
|DO NOT USE - This Road type is currently not deemed useful for mapping in the UK (See UK forum discussion )|
|Road with no access for the general public, public roads with legal prohibition on through routing in both directions (private road sign, no motor vehicles except for access sign, or a closable gate).|
|Roads within a car park, or other places where we don't want Waze to monitor speed and potentially generate a traffic jam report, in particular petrol station forecourts. Read more on car park mapping on the UK Car Parks page.|
|Unsurfaced road which is often impassable for normal cars and only suitable for 4x4 vehicles.|
Unpaved checkbox - This attribute can be selected for all Road types but should only be applied to Street Road type and below. This checkbox can be applied to segments that cover roads that are unsurfaced or of poor construction but is still passable by a normal car. Users can avoid roads marked with this attribute applied within the App settings. Segments that ford rivers and are usually passable by normal cars should be mapped as a short Street segment covering the area that floods, the unpaved checkbox ticked, and the be named [FORD].
Non-drivable - Walking Trails are a group of non-drivable Road types available in the WME found under the Road menu. User experience can be improved by using these appropriately, you can read more when to use these Road types on the UK Footpaths page.
Primary Route Network
The primary route network (PRN) designates roads between places of traffic importance across the UK, with the aim of providing easily identifiable routes to access the whole of the country. Primary routes are marked green on most road maps and road signs are green with white and yellow text. The WMEOpenData extension for Firefox and Chrome can overlay this data directly within the editor.
Roads with number
Classified road in the UK are known by a single letter and number combination which should be included in the segment name so that Waze instructions include identifying information. When naming dual carriageway segments, the addition of a cardinal direction should be included to ensure clear instructions are given and useful incident reports. The segment should be named in the following format;
- Format: :
<Letter & Number> (<Direction>) - <Name>
- Examples: :
M45 (E)Motorway with cardinal direction
A1(M)Motorway class A Road, note no spaces are used
A7 - Old Dalkeith RdA Road with local name
A2 (W) - Dover RdA Road with cardinal direction and local name
Andover StRoad with local name
- Format: :
The UK has 3 classifications of roads; Motorways (M), A Roads, and B Roads. All other roads are unclassified. You may discover that local authorities maintain a database of roads they manage and use C, D, and U labels. These are internal labels only and should never be shown on public signs, they should not be added to segment names.
When naming Motorway segments, the City field should be set as None, this prevents City name smudge across the map.
Major junctions, particularly on motorways, should be labelled with a landmark. Under no circumstances should the road name or city name fields of a segment be used for naming of a junction.
Ramp names to be short, useful and unambiguous. Names should not include Junction to nor Entry to. Cardinal directions (N, S, E, W) should only be included if they are included on signs and provide clarity. Like other abbreviations, the > character can be used, and is read out as towards, this should be used only if needed. Entry and Exit should be considered equal for the purposes of naming, and should be named to give the most useful instruction to the driver. Ramps should not have a City name, this helps prevent city smudge.
Junctions with numbers
- All segments from numbered junctions should be mapped as Ramps to ensure exit instructions are given
- The name should begin with the exit number and then the name of the road it leads to, ideally without cardinal directions
- When motorways split, short wayfinder ramps should be used so that these names don't appear in the App
- Do not include junction numbers on entry ramps.
- Format: :
J<number> to <simple road name>
- Example: :
J4 to A464
- Format: :
Junctions without numbers
- If a ramp connects directly to exactly 1 other road, then it can be left unnamed, the instructions will naturally take on the name of the next segment
- It may be desirable to name the ramps more simply to remove cardinals or road names
- If the ramp connects to a roundabout, then an unnamed segment will often give optimal instructions. If the routes away from the roundabout are not signed from the main road the ramp should be named to match the exit signs.
<simple road name>
A1 - Great North Road
- Where a ramp forks into two directions, then the ramp names should include cardinals (if signed) or towards a city based on the signage
- If a city name is used only one city from the directional sign is to be used, preferably the one which is listed first
- On the M25, where relevant, directions to Heathrow or Gatwick should take precedence
- If the section of ramp before a fork is particularly short, then the preceding segment can be left unnamed with any junction number written in the forked segments
- This does result in longer announcements, so should be avoided if possible
- Where both directions of a road are connected to a roundabout, then ramps can be disambiguated using > city instead of cardinals, as per the signage.
<simple road name> (<cardinal direction>)
<simple road name> > <city name>
Junction > <city name>if connecting road has no name / number
M62 > Manchester&
M62 > Hull
Roundabout segments should remain unnamed. If the roundabout does have a proper, signposted name, then this can be labelled using an Area Place, with category set to Junction/Intersection, that fills the centre of the roundabout. This only applies to big roundabouts that are larger than 30 metres.
For further advice on editing roundabouts, see Editing Junctions and Roundabouts
Due to the size of most devices it is advantageous to keep on screen text to a minimum. When naming segments the following abbreviations should be used to conserve space. Each will be expanded by the Text-To-Speech (TTS) engine and voice instructions will read aloud the full word, Ave will be read as Avenue, etc.
When naming a segment the first word word in the name should never be abbreviated, nor should names that only include single words (excluding The). Green Street should be written as Green St and The Boulevard be written in full. Multiple abbreviations in the same segment name can be used where appropriate, Aston Boulevard West can be written as Aston Blvd W.
- Should you require TTS to read a letter, such as Car Park E, place a period (.) directly after the letter.
- J, used for road junction numbers, is the only abbreviation that can lead a segment name.
- The period (.) in the abbreviation of Saint is important otherwise it will be read as Street.
Bypass or By-pass?
|Road shields are linked to the street attribute of a segment, this is the full address <Street>+<City>+<County>+<Country>. Setting a shield on 1 segment will set it for all matching segments.|
|It is recommended that you install the [Road Shield Assistant] script to assist with see current road shields and affects of any changes you make.|
Shields on segments
To match with the Road Type convention used in the UK, road shields should be mapped as follows;
- - For use on with 1 or 2 digitals
- - For use on with 3+ digits
- - For use on A-Roads that form part of the Primary Route Network
- - For use on all other A-Roads
- - For use on junction ramps that have signed numbers .
|Changing the shield on a segment will change the shield on all segments with the same name, however far away they may be. Likewise, changing the name of a segment will change the shield if the name matches another.|
Due to the implementation of this feature, extra care must be made when assigning road shields to segments with an identical street attribute when it changes Road Type, the most likely scenario will be A-roads that change from PRN to non-PRN. Mapped Road Types have no influence on the displayed shield.
At this time (May 2021) road shields do not show on the client app for mapped Primary Street road type but but may be added if needed for turn instructions.
Junction shields should not include the letter J.
Shields on turn instructions
Turn arrows now allow editors to set the visual instructions at a turn. Editors should do their best to match the road sign at the turn. The road shield (1st) and corresponding destination name (2nd) in the Visual instructions field, and any additional destination names in the Towards field.
Road numbers within bracketsshould not be included at all as they are not directly off the junction, nor should road numbers be written in the Towards field.
In order to receive the correct turn instructions with road shields on roundabouts make sure to add the turn guidance on the exit turn from the roundabout. The turn guidance from the exit will be copied to the entry one. When adding turn instructions on roundabouts the signage on each exit should take precedence over any approach signs.
Exit signs should only be used when exits have a signed junction number, no J required.
A dual carriageway is a road which has a central reservation to separate the carriageways. This means 1 or more lanes in either direction. A road should be split into 2 one-way segments if any of the following conditions are met:
- The central reservation is wider than 5 metres
- There's a visible gap between average of all GPS traces
- It is split by physical barrier (Concrete, Armco, pedestrian barrier etc)
Pedestrian refuges and painted road separation (cross hatching that can be driven over) should not normally be split. Be aware there are a lot of these that were created as split roads during the UK Base-map import, these usually need merging to be a single two-way road.
Ramp segments should be used when mapping grade-separated junction and at major junctions, such as motorways and dual carriageways. Positioning where Ramps diverge from the main carriageway and merge with it will improve navigation and routing advice.
Ramps leading off a motorway or dual carriageway should be placed to start where;
- The lane begins to divide from the main carriageway (in the case of 3/2/1 markers)
- There is a 0-mile gantry over the carriageway, where the 1 mile, 1/2 mile, etc finishes. This will usually be the last gantry before the actual junction and will be the one without a distance marker on it.
Ramps leading on to a motorway or dual Carriageway should be placed where;
- the road first joins the main carriageway, i.e. just after the chevrons / lane dividers
- Lay-bys should only be included where there is significant separation from the main carriageway (e.g. grass, trees or a physical barrier). Similar to deciding if a road is dual carriageway.
- All segments should be mapped with Road type set toParking Road, with appropriate directions and turns
- The lay-by segment should have it's name set to [P] and have no City name
- Do not map lay-bys with Area Places.
Railway lines should be mapped using theRoad type. They appear in the client, and they keep Wazers on trains from polluting the speed data of nearby roads. Tracks should be drawn as simply as possible - they do not need to be accurate out in the country where no one can see them, a single mapped segment can cover multiple lines common in most stations, and mainlines.
Due to the potential length of railway segments they should be split at County borders to prevent smudging County names on the map.
- Name: No Name
- City: No City
- Type: Railway
- Direction: Two-way
- Level: Ground
- Lock: 3
|You may find railway segments locked to 5 and set to -5 Level. This was the old standard and can be set to the current standard if all road segments along their routes have been correctly mapped with bridges & level crossings.|
Railway segments can be connected to the road network at level crossings, without any risk of Waze routing drivers onto the tracks. The extra granularity of segments at the crossing provides more accurate routing information. All turns should be enabled, no red arrows please.
Railways that are underground or where they pass through tunnels should not be mapped.
Level Crossing Alerts
Level crossing throughout the UK have now been mapped with LCAs. These are alerts similar to cameras and work in the same manner in the client. LCAs should be mapped in the same method as a camera on both sides of the railway line. The LCA should be placed close to the junction of the road and railway segment, aim to be between the barrier (if it has one) and stop line of the crossing.
|You can discuss more about LCAs and get assistance in the dedicated forum post.|
Ferries should be mapped using theRoad Type. This should be connected to the road network at either end and be mapped to follow a single line using the average / approximate route of the ferry service. If the ferry service charges for the crossing, and the vast majority do, it should also have the toll attribute ticked. If the ferry service has a regular schedule, the segment should include Time Based Restrictions to prevent Waze routing through the ferry crossing when no service is running.
Only regular vehicle ferry services be mapped. The UK have mapped the prices for all inland ferry services so you will find the segments locked to L5 to prevent accidental damage. Should you spot an issue or need to edit these segments you should contact a Country Manager / Local Champ for assistance.
Passenger / foot ferries should not be mapped.
When road segments pass over or under another feature (road, river, railway, etc), the segment level should be set to the correct +ve / -ve number. It can be beneficial to split the segment to create a bridge segment. This allows editors to close the shortest possible length of road when a physical bridge is closed for inspections, repairs, or any other reason.
- "older" roads, with properties along them, should be split by segment nodes tight to each side of the physical bridge. This enables Waze to navigate to addresses adjacent to the bridge when the bridge segment is closed.
- "newer" roads, with no properties along them, do not need to be split as the whole segment level can be changed. Such roads, such as bypasses, are always closed junction to junction.