Back to main index

2.2.1   Start navigation

The .in file

Attributes in [Head] section:

Type: 100
Allowed Mode: 0 (try once), 1 (try until success)
Allowed Blocking: 0 (non blocking), 1 (blocking)

If you like to start the tracking mode, then simply don't specify the [StartNavigation] section.

Attributes in [StartNavigation] section:

• SearchAddress: Output the location as an address in the .out file. 0=disabled, 1=enabled. This attribute is optional. Default is 0.
  If enabled, the output is given as string formatted like the following:
  D,76131,Karlsruhe,Tullastrasse,1-11|2-20
  The housenumber will be given as ranges separated by the pipe '|' symbol. A range of 0-0 means no housenumber found for this side of the segment. The different ranges will always be sorted from lower to upper.

If you like to start a navigation to a single destination, then specify the location as following:

• Location: The location of the stop-off point. Locations can be entered in 3 formats:
  • Address: country code,zip code,town,street,housenumber
    e.g. D,76131,Karlsruhe,Tullastrasse,1
  • Mercator coordinates: xxxxxx,yyyyyyy
    e.g. 951215,6261940
  • Geodez-Tupel: x.xxxxxxx,y.yyyyyyyy
    e.g. 8.5545,48.9652
• Caption: The caption which appears in the stop-off point list

If you like to start a navigation to multiple destinations, then create an own section for each location:

• [Destination_xx]: Section for the xx-th destination. xx can be a number between 01 and 20 and has to be specified by a two digit number.
  • Location: The location of the stop-off point. Locations can be entered in 3 formats as described above.
  • Caption: The caption which appears in the stop-off point list

Note: Navigation always starts a route from the actual GPS position to the destinations defined in the Location attributes. A navigation can't be started when the application is already navigating or when the options dialog is displayed.
Note: If SearchAddress is enabled, the application tries to find the correct address, if Location is given as mercator or geographical coordinates. The address is written in the .out file as Location_Address attribute. If SearchAddress is disabled, the value of Location_Address attribute will look like ",,,,".
Warning: Finding the address from mercator or geographical coordinates takes a very long time. Therefore the application won't respond during the search!

Sample .in file: This request starts a navigation from the actual GPS position to 3 destinations

[Head] Type=100 Mode=0 Blocking=0 [StartNavigation] SearchAddress=0 [Destination_01] Location=937575,6269540 Caption=RC Navigation Destination 1 [Destination_02] Location=D,76131,Karlsruhe,, Caption=RC Navigation Destination 2 [Destination_03] Location=938625,6271340 Caption=RC Navigation Destination 3

The .out file

Attributes in [StartNavigation] section:

• SearchAddress: The SearchAddress attribute given in the .in file
• StartNavigationResult: Result code

  StartNavigationResult	Description
  -5	navigation not started, canceled by user
  -4	navigation not started, no GPS Fix
  -3	navigation not started; the application is already navigating
  -2	navigation not started; specified location doesn't exist on the map
  -1	navigation not started; location not found - maybe invalid location syntax
  1	navigation started successfully
  2	tracking mode started successfully

• StartNavigationResultDesc: A textual description of StartNavigationResult

When you have started a navigation to a single destination, the following attributes are in the [StartNavigation] section:

• Location: The Location attribute given in the .in file
• Caption: The Caption attribute given in the .in file
• Location_Mercator: Mercator coordinates of the destination stop-off point
• Location_Geodecimal: Geographical coordinates of the destination stop-off point
• Location_Address: Address of the destination stop-off point

When you have started a navigation to multiple destinations, there is an own section [Destination_xx] for each location:

• [Destination_xx]: Section for the xx-th destination.
  • Location: The Location attribute given in the .in file
  • Caption: The Caption attribute given in the .in file
  • Location_Mercator: Mercator coordinates of the destination stop-off point
  • Location_Geodecimal: Geographical coordinates of the destination stop-off point
  • Location_Address: Address of the destination stop-off point

Note: The value of Location_Geodecimal is empty when the location doesn't exist on the map!

Sample .out file: The navigation started succesfully

[Head] Type=100 TypeDesc=start navigation Mode=0 ModeDesc=try once Blocking=0 BlockingDesc=not blocking Timestamp=707864031 Id=707864015 Result=2 ResultDesc=success and request deleted ExecuteDuration=359 [StartNavigation] SearchAddress=0 StartNavigationResult=1 StartNavigationResultDesc=navigation started [Destination_01] Location=937575,6269540 Caption=RC Navigation Destination 1 Location_Mercator=937575,6269540 Location_Geodecimal=+8.431815,+49.010029 Location_Address=,,,, [Destination_02] Location=D,76131,Karlsruhe,, Caption=RC Navigation Destination 2 Location_Mercator=936125,6269405 Location_Geodecimal=+8.418774,+49.009233 Location_Address=D,76131,Karlsruhe,, [Destination_03] Location=938625,6271340 Caption=RC Navigation Destination 3 Location_Mercator=938625,6271340 Location_Geodecimal=+8.441257,+49.020646 Location_Address=,,,,