KEY ASPECTS OF NAVIGATION - Signposts Presenter’s Name Date 11.

KEY ASPECTS OF NAVIGATION- Signposts

Presenter’s Name

Date

1

www.rmsi.com

Definition

Signpost is the database representation of the directional information indicated on signposts

Signposts information is captured to provide additional navigation assistance

The information is captured at a “decision point” in the database

# 2

www.rmsi.com

Description

Signpost Information

Signpost Information is the combination of directional information with

destination information.

Direction Information: Directional info is represented in the composition of a signpost, being a relationship between a first Road Element, a Via Junction and, optional, a couple of in-between components and an end component.

Destination Information: Destination Information is represented by the signpost attributes.

Signpost represents also exit information (exit name, exit number) without

having directional information linked to it on the signpost itself.

# 3

www.rmsi.com

Destination Info on Signpost

Destination Info on Signpost is the database representation of the destination information indicated on signposts.

Types of Destination Info

Destination Info on Signpost concerns a destination related to one direction as indicated on the plate. A destination concerns one of following types:

Exit Number on Sign Exit Name on Sign Route Number on Sign Route Name on Sign Pictogram on Sign Settlement Name on Sign Other Destination on Sign

www.rmsi.com

Destination Info on Signpost

Destination Info on Signpost refers to real destinations and not to additional information mentioned on the signpost. The distance indications are not seen as Destination Info on Signpost as shown in the figure below.

This means that Destination Info on Signpost doesn’t relate to indicated distances, types of routes to be used to reach a destination, …

If the route number, route directional or route name of the road you are driving on is present on a signpost, it is not considered to be Destination Info on Signpost, because it is not a destination.

www.rmsi.com

Exit Number on Sign

Exit Number on Sign is the database representation of each part of the destination information that represents an exit number. Exit Number on Sign refers to an exit number; it does not include the word ‘exit’.

Exit Number on Sign shall be captured for each exit number mentioned on a signpost or if not signposted, captured based on another source or based on the numerical order of the previous and next signposts if captured

as Signpost.

www.rmsi.com

Exit Name on Sign

Exit Name on Sign is the database representation of each part of the

destination information indicated on signposts, that represents an exit name.

Exit Name on Sign refers to an exit name; it does not include the word ‘exit’.

Exit Name on Sign shall be captured for each exit name mentioned on a signpost if captured as Signpost.

www.rmsi.com

Route Number on Sign

Route Number on Sign is the database representation of each part of the destination information indicated on signposts, that represents a route number.

Route Number on Sign represents only the route number that is a destination, not the route number of the road along which the signpost is located.

Route Number on Sign shall be captured for each route number that is a destination mentioned on a signpost if captured as Signpost. This route number has to be present on the last signpost that contains information for that specific direction.

www.rmsi.com

Route Number on Sign

Route numbers that refer to the road on which the sign plate is situated is not considered as Route Number on Sign.

www.rmsi.com

Route Number on Sign

www.rmsi.com

Route Number on Sign

www.rmsi.com

Route Name on Sign

Route Name on Sign is the database representation of each part of the destination information indicated on signposts, that represents a route name.

Route Name on Sign refers to the route name assigned to a particular part of the road network.

A route name can be an official street name, a tourist name for a road (e.g. Route du Soleil), a traffic related name (e.g. Ring), …

Route Name on Sign shall be captured for each route name mentioned on a signpost if captured as Signpost. This route name has to be present on the last signpost that contains information for that specific direction.

www.rmsi.com

Route Name on Sign

Route names that refer to the road on which the sign plate is situated is not considered as Route Name on Sign, see figure.

www.rmsi.com

Pictogram on Sign

Pictogram on Sign is the database representation of each part of the destination information indicated on signposts, that represents a pictogram.

A pictogram is a sign referring to a particular type of facility or accommodation (airport, railway station, …). A particular type of facility or accommodation can be indicated by different (country related) pictograms.

Examples of Pictograms

www.rmsi.com

Pictogram on Sign

Pictogram on Sign does not refer to the textual information associated with the pictogram.

Pictogram on Sign shall be captured for each pictogram indicating one of the facilities (as shown in next slide), mentioned on a signpost if captured as Signpost. This pictogram has to be present on the last signpost that contains information for that specific direction.

www.rmsi.com

Pictogram on Sign

The following Pictograms will be captured

www.rmsi.com

Pictogram on Sign

Destinations that are related to pictograms other than those on previous slide will NOT be captured. Example:

www.rmsi.com

Pictogram on Sign

If the pictogram is captured as Pictogram on Sign, the textual information associated with the pictogram shall be captured as Destination Info on Sign. The type will be different from Pictogram on Sign, see figure.

If the pictogram is NOT captured as Pictogram on Sign, the textual information associated with the pictogram is ALSO NOT captured as Destination Info on Sign except for textual information associated with pictograms indicating a type of route.

www.rmsi.com

Settlement Name on Sign

Settlement Name on Sign is the database representation of each part of the destination information indicated on signposts, that represents a settlement.

Settlement Name on Sign refers to real settlements or a certain area or neighborhood inside a settlement.

www.rmsi.com

Settlement Name on Sign

Settlement Name on Sign shall be captured for each settlement name mentioned on a signpost if captured as Signpost. This settlement name has to be present on the last signpost that contains information for that specific direction.

Settlement Name on Sign does not refer to a destination that is a facility or an area with a special designation referred to by a settlement name. E.g. the text specifying an Industrial area, harbour, airport or railway station is not considered for Settlement Name on Sign.

www.rmsi.com

Other Destination on Sign

Other Destination on Sign is the database representation of each part of the destination information indicated on signposts, that represents other text than exit number, exit name, route number, route name, pictogram or settlement name.

Other Destination on Sign represent all other destinations mentioned on a signpost (industrial areas, amusement parks, hospitals, …).

www.rmsi.com

Other Destination on Sign

Other Destination on Sign shall be captured for each destination that not refers to exit number, exit name, route number, route name, pictogram or settlement, mentioned on a signpost represented if captured as Signpost. The other destination has to be present on the last signpost that contains information for that specific direction.

www.rmsi.com

Destination Set Number

Destination Set Number is the database representation of the position of one functional unit of destination information on a signpost.

Several types of destination information are often mentioned together on a signpost in order to represent a more meaningful unit of information.

Typically this is a combination of a route number and a destination, indicating that this destination can be reached by following this route, or giving information on the direction of this route.

Another example is the combination of a pictogram and a text specifying the considered facility more accurately

www.rmsi.com

Destination Set Number

Destination Set Number represents the position of a set of Destination Information on a signpost, read from left to right and from top to bottom.

In case more than one signpost is involved, the value of Destination Set Number is determined with following priority:

- The order in which the signposts are encountered when traveling

along the road, in case signposts with different information are

posted behind each other (e.g. exit information)

- First the upper left sign plate, then moving downward, then

moving to the right.

Destination Set Number is represented by assigning a numeral to each Destination Info on Signpost indicating the order of the functional unit of destination information as indicated on the plate.

www.rmsi.com

Destination Set Number

Destination Set Number shall be captured for each captured Destination Info on Signpost.

www.rmsi.com

Sequence in Destination Set

Sequence in Destination Set is the database representation of the order of Destination Info on Signpost inside a functional unit of destination information on a signpost.

Sequence in Destination Set represents the numeric value related with the order of Destination Info on Signpost in a functional unit of destination info, identified by Destination Set Number.

Sequence in Destination Set shall be captured for each captured Destination Info on Signpost.

www.rmsi.com

Destination Set - Example

MURRAY BRIDGE and the route number M1 are on the same line of the signpost, So Settlement and Route Number both are captured as one destination set (order).

In this case the Route number M1 applies to more than one settlement and it is positioned centrally on the signpost. All applicable settlements and the route number will be captured as one destination set (order).

www.rmsi.com

Destination Set - Example

For the Left Turn- EAST TAMAR HIGHWAY as order 1- RNR 8 and City as order 2For the Right Turn- EAST TAMAR HIGHWAY as order 1- RNR 8, George Town and Low Head all as order 2 because of the way in which the route number is positioned on the signpost.

For the Left Turn- Capture Aerodrome as order 1 (it is on the top line by itself)-Both route numbers and settlement name Wentworth as order 2 (they are one destination set because they are all on the same line on the signpost)- Adelaide as order 3 (it is on the bottom line by itself)For the Right TurnPictogram (Information Centre) as 1.

www.rmsi.com

Destination Set - Example

Route number as 1

Settlement Sydney as 2

Route Number and Pictogram as set 1

Settlement Sydney as 2

In both the above example MOTORWAY and TOLL informationis not captured Since it’s not giving any destination information

www.rmsi.com

Destination Set - Example

These signs will be treated as a single sign plate. They will be captured in three destination sets.

Pictograms captured as a single destination set. Tourist pictograms captured as a single destination set. All other elements captured as separate destination sets

www.rmsi.com

Connection Information

Connection Information is the database representation of the type of Destination Info on Signpost.

Three types are defined:

- Exit information: destination information that refers to an exit.

- Branch information: a destination that is reached after the

decision Junction (Slip Roads and Parallel Roads are not

taken into account). The destination refers to a characteristic

of the road part after the decision Junction:

- Towards information: a destination that is not yet reached

after the decision Junction (Slip Roads and Parallel Roads

are not taken into account).

Connection Information shall be captured for each captured Destination Info on Signpost.

www.rmsi.com

Connection Information

Exit information is always linked to Exit Number on Sign Exit Name on Sign always

Towards information is always linked to Pictogram on Sign, Settlement Name on Sign Other Destination on Sign always Route Number on Sign Route Name Sign

Branch Information is always linked to Route Number on Sign Route Name Sign

www.rmsi.com

Connection Information

If the road with the signposted Route Number or Route Name is reached after the decision point (excluding slip roads and parallel roads), the Route Number on Sign or Route Name on Sign have Connection Information ‘Branch information’.

In case the road with the signposted Route Number or Route Name is not reached right after the decision point (excluding slip roads and parallel roads), the Route Number on Sign or Route Name on Sign have Connection Information ‘Towards information’.

Example

www.rmsi.com

Connection Information

In case the road with the signposted Route Number or Route Name is reached after several decision points (with several sets of slip roads and parallel roads), the Route Number on Sign or Route Name on Sign have Connection Information ‘Towards information’.

www.rmsi.com

Connection Information - Example

The FRC-A 5.1 is called THE LAKES WAY, so this is captured as “Branch”. The Settlements are captured as “Towards”.

FRC-A 5.1

www.rmsi.com

Connection Information - Example

“Branch” is captured here for EAST TAMAR HIGHWAY and RNR 8 because even though they are not found on the last road edge included in the signpost, there are no decisions junctions in between that edge and an edge that has that route number and name.

www.rmsi.com

Connection Information - Example

Route number 17 is captured as continuation because it is found on both the first and last edges of the signpost.

www.rmsi.com

Connection Information - Example

Single exit destination is captured as an Exit.

If two or more settlements occur with Exit information then they will be captured as Exit Name and not as Settlement. Here also “Murwillumbah” will be captured as Exit name not Settlement name.

www.rmsi.com

Ambiguous Information

Ambiguous Information is the database representation of a part of the destination information on a signpost, is also mentioned on that signpost but related to an other direction.

In case on one or more signposts at an intersection, two times the same information is mentioned, but related with an other direction, the use of this information in certain application may be confusing. Therefore, this information will be indicated with Ambiguous Information.

www.rmsi.com

Ambiguous Information

Ambiguous Information shall be captured for Destination Info on Signpost when for a signpost, there is another signpost having the same first component and a different last component, and on the other signpost, there is an identical Destination info on Signpost.

Information is only ambiguous where there are two or more signposts in the database which use the same first edge and same decision node.

If only one signpost is captured, there is no need to have the information as ambiguous.

If the signposts use different decision nodes, there is also no need to have the information as ambiguous.

www.rmsi.com

Ambiguous Information

Example:Ambiguous information occurs when the same destination info applies

to more than one direction at a decision point.

DALGARNO STREET will be ambiguous because it applies to two different directions starting from same road.

www.rmsi.com

General Capturing Rules

Signpost shall be captured for each signpost located along a freeway or its related Slip Roads or Parallel Roads (Including the Slip Roads that give access to the freeway and start of freeway):

- For each signpost representing destination information combined

with a direction.

- Additionally, for each signpost indicating exit number/name.

Destination information shall be captured for each direction: based upon the destination information on the last signpost of a direction.

Signpost shall only be captured for signposts with a permanent and official nature.

The information is captured at a “decision point” in the database.

www.rmsi.com

General Capturing Rules

Example 1: The signpost nearest to the Decision Point should be captured. Information on preceding signposts should NOT be included

Signpost 3 would be captured in this example as it is nearest to the decision point (intersection of

FRC-A 2 and FRC-A 5.1).

FRC-A 2FRC-A 5.1

Exception (To be followed only if Signpost 3 contains other Destination) : It may be more appropriate to capture information from a signpost that is not the closest to the decision point. If for example, signpost 2 in the diagram contained more information e.g. Settlement and route name information, but signpost 3 only contained information for other destination. This should only be done if the further signpost is still within a reasonable distance of the decision point and there should be no T-Crossing between Signpost 3 and Signpost 2.

www.rmsi.com

General Capturing Rules

Example 2:

In this example only the signpost information from the closest sign (MI, Adelaide) to the intersection is captured. Signposts must not be combined.

www.rmsi.com

General Capturing Rules

In the above case where two signs located at different points share common information and the sign further from the intersection contains unique destination information, then

Signpost 1 is captured for the Left Turn (closer to intersection)Signpost 2 is captured for the straight ahead information

Example 3: Signpost 1

Signpost 2

www.rmsi.com

General Capturing Rules

Example 4:Multiple Signs at one point Where there are multiple signs located at a single point, all relevant information

should be captured in the same top to bottom left to right manner.

www.rmsi.com

General Capturing Rules

Example 5: When there are two separate signposts at the same location only the more

important signpost should be captured. In this case, the official green

signpost giving the route number and settlement name should be captured,

rather than the brown and blue signposts with other destinations. Check with a team leader if unsure about which is the better signpost to capture. Signposts may not be combined and INCA will not allow two separate signposts using the same edges and decision node.

www.rmsi.com

General Capturing Rules

Example 6: Signposts at Slip roads When there is a choice between signposts at location “A” and location

“B”, the signpost from “A” will be captured as it is closer to/before the

crossing.

www.rmsi.com

General Capturing Rules

Example 7: Signposts at Slip roadsRoute number 5 is ambiguous and signpost

includes edge before the slip road.

www.rmsi.com

General Capturing Rules

Example 8: Dual CarriagewaysFrom Dual Carriageways, only the connector is included in the

signpost, not the following edge.

www.rmsi.com

General Capturing Rules

Example 9: Dual CarriagewaysThe exception to this is straight-through signposts; these must include

all the edges. The straight-through signpost heading south includes extra

edges at the beginning because it occurs prior to the slip road.

www.rmsi.com

General Capturing Rules

Example 10 : RoundaboutsAt a roundabout both of these signposts

will be captured

Signpost A

Signpost B Route number is ambiguous because the straight ahead signpost (RNR 1, Launceston, Burnie) will start from the same edge, same decision node. Signposts for all directions shown on this sign will begin from this edge. This signpost includes only the roundabout edge closest to the exit and the edge leaving the roundabout; there is no need for ambiguous information at this point.

www.rmsi.com

General Capturing Rules

Example 11 : Street names As with other street and place names, no names should be abbreviated in the signpost information. For example MT should be entered as MOUNT, ST should be entered as STREET etc.

Street name is captured

Street name is not captured Street name is captured

Street name is captured (in this case due to the shape of the white sign)

www.rmsi.com

General Capturing Rules

Example 12 :All Settlements on this sign are captured with individual destination sets. But the numbers should not be captured.

Internet Search destination/s to verify if this is one destination or two.

www.rmsi.com

General Capturing Rules

Allowed characters in Street names: English names: allowed characters:

- letters (caps and small), numbers and: - & - ‘ - - - . - ( - ) - , - space

www.rmsi.com

General Capturing Rules

Example 11 : Rest AreasInformation that refers exclusively to rest areas (toilets, restaurants, hotel etc)

will not be captured. It will only be captured if information referring to a

destination that is not part of the rest area is present.

www.rmsi.com

General Capturing Rules

Signpost compositionSignpost will always be composed out of Road Elements and a via Junction

Where : the first component is the last Road Element before the decision Junction. the second component is the decision Junction which is the Junction that represents

the first point on the crossing where a decision has to be taken to reach one of all indicated directions mentioned on the plate. The decision (or via) Junction is always the first Junction part of the relationship. The decision Junction depends on the position of the sign and the information it caries, see figure.

www.rmsi.com

General Capturing Rules

the (eventual) in-between components are the Road Element(s) forming the route between the first and the last component.

the last component is the first Road Element after the last decision point on the crossing needed to reach the related destination.

In case of a Signpost representing an exit name or exit number, the Signpost shall always be composed out of exactly two Road Elements, and one Junction

- the first component is the last Road Element before the exit.

- the second component is the Junction where the maneuver to leave the

main road and take the exit is completed (via junction).

- the last component is the first Road Element after the via junction.

www.rmsi.com

General Capturing Rules

Signpost referring to specific lanes When destination information refers to specific lanes, this is considered as

different directional information. Different Signposts will be captured (See Figure).

The last component is the first Road Element after the last decision point on the crossing needed to reach the related destination.

www.rmsi.com

General Capturing Rules

Signpost for exit Information

Signpost shall be captured for exit names and exit numbers in case they are indicated with sign.

Additionally, Signpost shall also be captured for existing exit numbers which are not indicated on a sign, for instance if the exit number is known from another source or from the numerical order of the exit numbers.

For exit names and exit numbers, Signpost will always relate to the exit itself, regardless the position of the sign, see figure.

www.rmsi.com

General Capturing Rules

Last signpost for a specific direction before decision point

Destination Info on Signpost shall be captured for destination information based upon the destination information on the last signpost for the direction that is captured as Signpost, see figure.

www.rmsi.com

General Capturing Rules

Exit information as Destination Information

Destination Info on Signpost shall be captured for exit information (exit number, exit name) in case indicated on a signpost. The position of the signpost doesn’t matter.

Destination Info on Signpost shall also be captured for exit number even if they are not indicated on a signpost but it they are present on another source or if it can be deduced from the numerical order of previous/next exit numbers.

www.rmsi.com

General Capturing Rules

Examples

www.rmsi.com

General Capturing Rules

Examples

www.rmsi.com

General Capturing Rules

Signposts not to be captured: for directional information indicated on signposts exclusively referring to a

rest area, (see Figure) for directional information indicated on signposts located on an

entrance/exit of a rest area. (see Figure) for directional information indicated on signposts indicating alternative or

deviation routes.

www.rmsi.com

General Capturing Rules

Signposts not to be captured: for signposts with a temporary nature shall not be considered: e.g.

information indicating deviations due to road works, a festival, … A signpost shall be considered as official if it is set along a road by an official body or by a private organization involved with the construction, maintenance, … of the road. Quite often signpost are posted for restaurants, pubs, … which do not have an official nature or are not set by official instances, these will not be captured.

if the signpost indicates only the continuation of the Route Number, Route Directional or Route Name of the road you are on, because the Route Number, Route Directional or Route Name is not a destination.

for directional information indicated on signposts indicating routes exclusively meant for vehicle types different from normal passenger cars (e.g. exclusively meant for bicyclists, exclusively meant for trucks, …).

www.rmsi.com

General Capturing Rules

Signposts not to be captured:

Signpost shall not be captured if one of the Road Elements part of the relationship concerns a Stubble, see figure.

Signposts exclusively meant for vehicle types other than passenger cars are not captured. Distance information on signposts are not captured

www.rmsi.com

General Capturing Rules

Examples:

• Signpost information is captured left to right, top to bottom. For example, the following sign is captured as:

“Port Road” – captured Route Name.“City” – captured as Other Destination.“Grand Junction Road” – captured as Route Name.“Semaphore” – Captured as Settlement.Route 1 and Route 20 captured as route number, both in same destination set.

Information on two or more different signposts shall NEVER be combined. When capturing multiple signs they must exist at the same point. If a signpost is separated by a VERTICAL line, it will be treated as two different signposts.

www.rmsi.com

Traffic Sign

Traffic Sign is the database representation of a plate containing

symbols and (possibly) some additional text, expressing a traffic

restriction, recommendation or information. Traffic signs are symbols, which are placed along, beside, or above

a road to guide, warn, and regulate the flow of traffic of road users. They can carry a prohibition, a warning, a recommendation or an obligation or serve an informative function.

Traffic Sign shall be captured for all permanent electronic signs that are designed to carry traffic information, only when they can carry speed limit restrictions.

www.rmsi.com

Examples of Traffic Signs

www.rmsi.com

Traffic Sign

Electronic Signs

Three types of electronic signs can carry speed limit information: signs designed to carry only speed limit information signs designed to carry text signs designed to carry a variety of symbols (see Figure)

www.rmsi.com

Traffic Sign

Electronic sings, which are designed to carry only lane icons (stating that a lane is closed or open), shall not be captured. (see Figure).

Additional rules

- Electronic signs do not have to be ‘activated’ to be captured.

- Only permanent electronic signs will be represented. Non permanent signs

are frequently used at road works.

- A Traffic Sign shall correspond with a location on the road network, not an

existing Junction or Node. Traffic Signs, attached to bridges, shall be

captured 5 meter in front of the bridge.

- If two signs are present one the same location -one on the left and one on

the right side of the road- only one Traffic Sign shall be captured.

www.rmsi.com

Traffic Sign Class

Traffic Sign Class is the database representation of type of a plate containing symbols and (possibly) some additional text, expressing a traffic restriction, recommendation or information.

Traffic Sign Class is an attribute to Traffic Sign indicating the sort of Traffic Sign.

The following category is distinguished:

- Variable Traffic Sign

Traffic Sign Class shall be captured for all captured Traffic Sign.

www.rmsi.com

Questions