Back to main index

2.1.4   Add a stop-off point to previous destinations list

The .in file

Attributes in [Head] section:

Type: 4
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 a geodez-tupel
[Head]
Type=4
Mode=0
Blocking=0

[StopOffPoint]
Location=8.4417,49.0212
Caption=Remote Control Previous Destination (Geodez)
SearchAddress=1

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

Sample .out file: The stop-off point was added successfully
[Head]
Type=4
TypeDesc=add stop-off point to previous destinations
Mode=0
ModeDesc=try once
Blocking=0
BlockingDesc=not blocking
Timestamp=6099919
Id=6099900
Result=2
ResultDesc=success and request deleted
ExecuteDuration=169557

[StopOffPoint]
Location=8.4417,49.0212
Caption=Remote Control Previous Destination (Geodez)
SearchAddress=1
StopOffPointResult=1
StopOffPointResultDesc=stop-off point added
Location_Mercator=938674,6271433
Location_Geodecimal=+8.441698,+49.021195
Location_Address=D,76131,Karlsruhe/Rintheim,Albert-Nestler-Strasse,


Back to main index Top of page