How to Use MultiNet Shapefile and OSL
Parent topic: How to Use MultiNet Shapefile and OSL

How to Use Toll Information

All relevant information for tolls can be found in the MultiNet Shapefiles in the figure below. OA09 (special charge) is used for display purposes only.

Figure: Toll Information Data Model

Definitions

Follow the links below for definitions of each file involved in lane and toll information. All Shapefile file definitions are found in the Data Content - Shapefile and OSL section of this user guide.

nw; ln; ll; ld; le; li; lt; lf; sl; lp, pm rs, pi, piea, oa09.

The use of all the Shapefile tables related to toll information is not necessary to understand the basics of lane change locations, toll location, and toll information.

Data View

A generic Shapefile view of a highway or motorway containing network, lane, toll location, toll information and toll payment method is shown below.

Figure: Sample Data With Sample Toll and Lane Information

See figure later in this section for a graphic rendering of this example.

Lane Table Showing Change of 3 Lanes to 7

The ln table indicates that in the Lane Connectivity Relationship (9860), lane 1 breaks out into lanes 1, 2 and 3 (1/1, 1/2, 1/3); lane 2 becomes lane 4 (2/4); and lane 3 breaks out to lanes 5, 6, and 7 (3/5, 3/6, 3/7) at this point.
Table 1. LN Connectivity Information Table
ID FEATTYP FROMTO JNCTID
xxxxxxxxxxx1111 9860 1/1 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 1/2 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 1/3 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 2/4 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 3/5 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 3/6 yyyyyyyyyyyyyyy
xxxxxxxxxxx1111 9860 3/7 yyyyyyyyyyyyyyy
Note: JNCTID indicates Junction where the ln point is located.
The lp table links the ln "FROMTO" lane assignments to the transportation elements in sequence.
Table 2. lp Lane Connectivity Path Table:
ID SEQNR TRPELID TRPELTY
xxxxxxxxxxx1111 1 xxxxxxxxxxxxxx1 4110
xxxxxxxxxxx1111 2 xxxxxxxxxxxxxx2 4110
The ll table indicates the type of lane dividers that are on a road element.
  • If the divider types differ per lane, there will be additional SEQNR numbers per ID.
  • The divider type (DIVIDERTYP) on road element xxxxxxxxxxxxxx2 is "single solid line" (3).
  • The divider type on road element xxxxxxxxxxxxxx2 is valid (VALIDITY) for all lanes except the far right lane (R1111110).
  • The divider type (DIVIDERTYP) on road element xxxxxxxxxxxxxx3 is "toll booth" (15).
  • The divider type on road element xxxxxxxxxxxxxx3 is valid (VALIDITY) for all lanes except the far right lane (R1111110).
Table 3. ll Lane Divider Information
ID SEQNR DIVIDERTYP VALIDITY
xxxxxxxxxxxxxx2 1 3 R1111110
xxxxxxxxxxxxxx3 1 15 R1111110

Toll Plaza 7375

Note: Only fields relevant to the example are shown in the tables below.
The pi table indicates that this point of interest is a toll plaza (7375). The CLTRPELID field is the link to the closest transportation element ID (xxxxxxxxxxxxxx3).
Table 4. pi Table
ID FEATTYP NAME CLTRPELID
xxxxxxxxxxxx123 7375 Toll Plaza xxxxxxxxxxxx123
The piea table indicates the validity direction (7V) is "positive" (2).
Table 5. piea Table
ID FEATTYP ATTTYP ATTVALUE
xxxxxxxxxxxx123 7375 7V 2
The nw table is linked to the pi CLTRPELID field.
  • The TOLLRD field indicates that the toll is in both directions (B).
  • ONEWAY indicates that the road is a oneway in the From-To direction (FT).
  • LANES indicates the number of lanes (7) on this road element.
Table 6. nw Table
ID TOLLRD ONEWAY LANES
xxxxxxxxxxxxxx3 B FT 7
The pm table carries the same IDs as the nw table when there is a toll road. The pm table identifies the type of toll payment available for each lane. Payment code is a bitmask in order to make multiple payment identifiers available as a single coded number.
  • Payment method (PAYMENT) is variable (64) electronic toll collection (16) (64 +16 = 80) in the far right lane (R0000001).
  • Payment method (PAYMENT) is variable (64) electronic toll collection (16) and cash (1) (64 +16+1 = 81) in all lanes but the far right lane (R1111110).
Table 7. pm Table
ID SEQNR PAYMENT VALIDITY
xxxxxxxxxxxxxx3 1 80 R0000001
xxxxxxxxxxxxxx3 2 81 R1111110

Figure: Graphic Rendering of Data Example

See earlier figure for the Data Example of this rendering.

Refer to the MultiNet Shapefile, MultiNet Code Overview and MultiNet Data Specifications for detailed information on tables, features and attributes.

Parent topic: How to Use MultiNet Shapefile and OSL