File structure

File structure

Previous Top Next

When a network is created from a GIS file (SHP, TAB, MIF or CGF format), several binary files are created on disk, which together define the topological network. This gives a short description of the content of the various files:

Filename	Mandatory	Encrypted	Explanation
Attribute.bin		X	Attributes of links
Coord.bin	X	X	Coordinates of all nodes
Coord3.bin		X	Coordinates of the rest of the vertices
Dist.bin	X	X	Length of all links in the network
Hierarchy.bin		X	Hierarchy attribute (new from v. 2.29)
Index.bin			Index for conversion between link id (1, 2, 3..) and external id.
Limit?.bin		X	Information about limits on links such as max heights etc. (new from v. 2.19)
Link.bin	X	X	Information about link-node relationship ("topology")
Node.bin	X	X	Information about link-node relationship ("topology") and coordinate clause
Roadname??.bin			List of possible road names (new from v.2.24)
Roadnumber??.bin		X	Index into roadname.bin (new from v.2.24)
Spatialindex.bin			Spatial index of both links and nodes (new from v. 2.17)
Turn?.bin			Turn restrictions
Turn2_?.bin			Turn restrictions (new from v. 2.33)

If you drop coord3.bin, these functions will not be possible to call:

·	AddNodes property <> 0

·	Coordinate2location

·	Location2coordinate

IsoLink2

IsoLink4

·	All RouteFile functions

·	Direction2

NWexport

·	TurnStandard

Limit.bin files are required to implement functions such as limiting a route to sections of sufficient width, weight etc.

If you set the EncryptionKey property, files marked as such in the table will be encrypted during creation and decrypted during load.

If you drop spatialindex.bin, these function will not be possible to call:

·	Coordinate2location

·	Coordinate2node

·	Overpasses

See also NWload, NWcreate, AttributeCreate2, LimitCreate, HierarchyCreate2 and RoadNameCreate2.

File coord2.bin is obsolete and should be replaced by coord3.bin