|
MakeNetwork
|
Previous Top Next |
| · | DAT (TAB)
|
| · | MID (MIF)
|
| · | DBF 3 (SHP & CGF).
|
| · | Attribute: Link attribute - see details here. You will have to pick a field even if you just want to do simple shortest path calculations with no oneway directions or any other special settings. In that case refer to any field in your dataset with all zero's.
|
| · | Roadname: The name of the road, which will be used in the generation of driving directions. There is no limit on the length of the text and you can even put in some HTML code, if certain street names should be marked (e.g. <B>Main Street</B>) in the final output. This can be used to highlight toll-roads etc. If you don't want to create driving directions, just skip this field. You will still be able to calculate distances and show routes on maps. Text fields for roadname settings should be in ASCII, ANSI or UTF-8 format (use UTF-8 if you want to generate GML2 output). UTF-16 is not supported. You can setup several fields for different languages if you like to. If your client uses UTF-16 (Java and C# do this), you plan to use non-ASCII characters and the array output format, we recommend that you replace those non-ASCII characters with a different sequence that can be replaced on the client side. Such that "å" could be stored as "/aa/" in your roadname field and then a search-and-replace is done in your code.
|
| · | Limit: These fields should hold an integer from 0-255. The integer is a limit in terms of max weight, width, height or whatever may be needed. A special bit pattern mode is also available. You can create 3 such limits at any time and you define how they should be used. 0 means no limit. See details here.
|
| · | Hierarchy: This field should hold a value from 1-5 for use with hierarchical routing. If you are using NavTeq data, use the field func_class. If you use TeleAtlas data, select the field netbclass and tick the box below.
|
| · | External ID: This field can be an external ID, typically an integer with many digits, that is neverchanging and unique across the whole database (field ID in TeleAtlas database, Link_ID in NavTeq database and TOID in ITN database). If you don't need to refer to the external ID in your application just skip the field.
|