Back to main index

2.1.5   Add a stop-off point to the stop-off point list

The .in file

Attributes in [Head] section:

Type: 5
Allowed Mode: 0 (try once)
Allowed Blocking: 0 (non blocking)

Attributes in [StopOffPoint] section:

Note: If SearchAddress is enabled, the application tries to find the correct address, if Location is given as mercator coordinates or geodez-tupel. 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 coordinates or geodez-tupels takes a very long time. Therefore the application won't respond during the search!

Sample .in file: This request adds a stop-off point using mercator coordinates
[Head]
Type=5
Mode=0
Blocking=0

[StopOffPoint]
Location=938625,6271340
Caption=Remote Control stop-off point list (Mercator)
SearchAddress=0

The .out file

Attributes in [StopOffPoint] section:

Note: The attributes Location_Mercator, Location_Geodecimal and Location_Address only appear in the .out file when StopOffPointResult is positive.
Note: The application has to be in navigation mode, otherwise stop-off points can't be added.

Sample .out file: The stop-off point was added successfully
[Head]
Type=5
TypeDesc=add stop-off point to stop-off point list
Mode=0
ModeDesc=try once
Blocking=0
BlockingDesc=not blocking
Timestamp=32298812
Id=32298781
Result=2
ResultDesc=success and request deleted
ExecuteDuration=198

[StopOffPoint]
Location=938625,6271340
Caption=Remote Control stop-off point list (Mercator)
SearchAddress=0
StopOffPointResult=1
StopOffPointResultDesc=stop-off point added
Location_Mercator=938625,6271340
Location_Geodecimal=+8.441257,+49.020646
Location_Address=,,,,


Back to main index Top of page