2008 TomTom International BV, Holanda. TomTom e o logotipo de "duas mos" esto entre as marcas comerciais, aplicativos ou marcas registradas possudas pela TomTom International B.V. Nossa garantia limitada e acordo de licenciamento do usurio final para o software includo se aplicam para este produto; ambos podem ser vistos em www.tomtom.com/legal
Data Source 2008 Tele Atlas N.V. Based upon: Topografische ondergrond Copyright dienst voor het kadaster en de openbare registers, Apeldoorn 2008. Ordnance Survey of Northern Ireland. IGN France.
Swisstopo. BEV, GZ 1368/2008. Geonext/DeAgostini. Norwegian Mapping Authority, Public Roads Administration / Mapsolutions. DAV. This product includes mapping data licensed from Ordnance Survey with the permission of the Controller of Her Majestys Stationery Office. Crown copyright and/or database right 2008. All rights reserved. Licence number 100026920.
Data Source Tele Atlas North America. Inc. All rights reserved. Canadian Data DMTI Spatial. Portions of Canadian map data are reproduced under license from Her Majesty the Queen in Right of Canada with permission from Natural Resource Canada. Point of Interest data by Info USA. Copyright 2008.
Data Source Whereis map data is 2008 Telstra Corporation Limited and its licensors, Whereis is a registered trademark of Telstra Corporation Limited, used under license.
Some images are taken from NASAs Earth Observatory. The purpose of NASAs Earth Observatory is to provide a freely-accessible publication on the Internet where the public can obtain new satellite imagery and scientific information about our home planet. The focus is on Earths climate and environmental change: earthobservatory.nasa.gov/
Text to Speech technology, 2008 Loquendo TTS. All rights reserved. Loquendo is a registered trademark. www.loquendo.com

1.3.2. Installing the Visual Basicspecific parts
The SETUP.EXE program will install the components required for your Pocket PC, but for development, you need to install additional components on your desktop computer. See the section "Desktop Computer" below. If you are upgrading from a previous version of the Navigator SDK, your old.VB files in the Pocket PC will stop working. In that case you need to open the corresponding Visual Basic project files on your desktop computer and regenerate the.VB files in the Pocket PC.
1.3.3. Installing the Visual C++specific parts
The \Sdk\TTNCom\lib\ directory contains the.lib files that an application needs to link against in order to use the SDK, and the directory \Sdk\TTNCom\include\ contains any header file that a program needs to include to be able to use the SDK DLL. No additional installation but unpacking is required.
1.3.4. Points of interests
The SDK contains a set of executables that facilitate creation of customized POI data sets that can be added to the map. These executables are installed simply by unpacking the complete SDK. The executables are stored in subdirectory \SDK\POI\, the chapter Providing your own points of interest to TomTom Navigator explains how to use the executables.

1.3.5. Desktop Computer

In the desktop computer it is required to install a design mode version of TTNControl.ocx so that you are able to add the TomTom Navigator SDK functionality to your eMbedded Visual Basic project. Note that this is needed only during the development phase of your application. The design mode version of 1
1. Installation and Getting Started TTNControl.ocx can be found in the directory \sdk\TTNCom\OcxDesktop\. To install it, just copy it to any suitable place in your hard disk and, if you are installing a new version of the Navigator SDK over an old one, register it with the Windows registry. If you are installing the Navigator SDK for the first time, you neednt register the control explicitly. Assuming your current directory is the directory where you copied TTNControl.ocx, the command line to perform the registration would be:
regsvr32.exe TTNControl.ocx
When you start a new eMbedded Visual Basic project, you need to add the TomTom Navigator SDK ActiveX component to it. To do this, select "Components." from the "Project" menu and, in the "Controls" tab, check the box "TomTom Navigator SDK 2.X." If that box is not present you will need to click on the "Browse." button and search for TTNControl.ocx on your hard disk.

1.4. License

1.4.1. ATTENTION
Use of our software is subject to the TOMTOM BV License and Limited Warranty terms set forth below. If you do not accept these terms, you cannot install our software and you are not entitled to use our software.

1.4.2. LICENSE AGREEMENT

This is a legal agreement between you, the end user, and TOMTOM BV, (TomTom). IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE CDROM/FLOPPY DISK/MEMORY CARD/DOWNLOAD PACKAGE AND THE ACCOMPANYING ITEMS TO THE PLACE YOU OBTAINED THEM FOR A FULL REFUND. BY BREAKING THE SEAL OF THE CDROM/FLOPPY DISK/MEMORY CARD, PRESSING THE "I AGREE" BUTTON FOR A DOWNLOAD, OR BY USING THE SOFTWARE YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. The license agreement is subject to Dutch Law and the District Court of Amsterdam is the only competent court for disputes based on the license agreement or the use of the (licensed) software. 1) GRANT OF LICENSE: This TomTom License Agreement (License) permits you to use one of the TomTom computer programs and the digital (map) data included in the accompanying package acquired with this license (SOFTWARE) on any single computer, provided the SOFTWARE is installed on only one computer at any time and provided the software is combined only with one or more navigation systems. 2) COPYRIGHT: The SOFTWARE is owned by TomTom or its suppliers and is protected by Netherlands Copyright Laws, international treaty provisions, and all other applicable national laws. Therefore, you must treat the SOFTWARE like any other copyrighted material (e.g., a book) except that if the software is not copy protected you may either (a) make one copy of the SOFTWARE solely for backup or archival purposes, or (b) transfer the SOFTWARE to a single medium provided you keep the original solely for backup or archival purposes. You may not copy the Product manual(s) or written materials accompanying the SOFTWARE. You only become the owner of the material data carrier and you do not acquire the ownership of the SOFTWARE. 3) DEPLOYMENT CONDITIONS: Any other product that is developed using the SOFTWARE may include(s) (a) software component(s) of TomTom that were shipped as part of the SOFTWARE. This/These software component(s) are freely distributable components as long as it/they are only shipped as part of an installation package of the product that was developed. Copyright and intellectual property rights of the SOFTWARE and the included component(s) remain with TomTom at all times. This should 2

1.5. Technical Support

For technical support please refer to www.tomtom.com. There you will find the latest versions and documentation of the SDK, Questions & Answers, tips & tricks, addons and tools.
2. Providing your own Points of Interest to TomTom Navigator
It is possible to add new Points of Interest (POI) to TomTom Navigator. This section explains how. Warning:
(1) No information stored in OV2 format, or extracted from files in OV2 format (using whatever means, tools or techniques, based upon either published or selfdiscovered knowledge about the OV2 format), nor any knowledge about the OV2 format itself, may be sold in any form, unless with written permission from the owner of the original (raw) information, used from within any application other than a TomTom product, commercial or otherwise, without explicit written permission from a director of either Palmtop BV or TomTom Inc, unless (a) that application has the sole purpose of providing additional functionality to TomTom Navigator or TomTom Citymaps, and (b) that application only functions on devices on which TomTom Navigator or TomTom Citymaps is installed, and (c) that application is accompanied by a warning similar to this warning. (2) Furthermore, we will not provide support about the format, or any related tools or documentation, we do not guarantee correctness or completeness of the either the format, the tools or the documentation, we hold the right to change or extend the format without notice, we do not guarantee that details of future, changed or extended formats will be made available, we do not guarantee that future, changed or extended formats will be compatible with the current format, we do not promise that we will allow the same things for future, changed or extended formats. (3) Finally, please note that the POI data that is distributed as part of TomTom products is (a) not in OV2 format, (b) expressly not allowed to be accessed in any way whatsoever, and (c) protected by international copyright laws.
2.1. Installing a POI database
A POI database consists of a file with extension OV2 (e.g. Hilton_Hotels.OV2) and, optionally, a companion file with extension BMP (e.g. Hilton_Hotels.BMP) To make such databases visible on a TomTom Navigator map, make sure that: The file(s) are stored in the same directory on your PocketPC where the map data are located. TomTom Navigator (re)opened the map after the OV2 file was put there (if necessary, restart TomTom Navigator). In the POI tab of your TomTom Navigator preferences, make sure "Display POI" option is checkmarked, as well as the POI themselves. Example: to use the database Hilton_Hotels.OV2 in the Germany map, you might do the following: Connect your PocketPC to the PC and start Microsoft ActiveSync. Use the menu option File>Explore to explore the directories on your 4

MAKEOV2 inputfilename [outputfilename]
The input file should be a text file (extension ASC is recommended) that should simply contain lines of text. Any line starting with a semicolon will be ignored. Empty lines will also be ignored. All other lines are expected to represent points of interest. Such a line should specify a longitude, a latitude and a name, seperated by commas. It is recommended that the name is put between double quotes. A name should not contain double quotes. Longitudes and latitudes may be specified either as degrees and fractions of degrees, or in degrees, minutes and seconds. Both colons and singlequote/doublequote notation may be used for minutes and seconds. So, all the following lines are all equivalent:
53.5 , 4 , "Truckers Restaurant La Bamba" 53.5000000 , 4.00000000 , "Truckers Restaurant La Bamba" 5330"00 , 400"00 , "Truckers Restaurant La Bamba" 5330 , 40 , "Truckers Restaurant La Bamba"
53:30:0 , 4 , "Truckers Restaurant La Bamba"

2.4. OV2 File Structure

TomTom Navigator POI files are stored in socalled OV2format, and as a rule have the filenameextension "ov2". This document provides some information about the content of such files. Please note the following legal conditions:
An OV2 file consists of a sequence of variablelength records. Every record starts with a onebyte "type". This type tells you how to process the rest of the record. You should not encounter types other than 0, 1, 2 and 3 if you do, the file is either corrupt or in a different (e.g. a higherversion) format. Coordinates are stored as 4byte integers representing a WGS84 longitude or latitude, multiplied by 100,000 and rounded to the nearest integer. As such, an Xcoordinate should always be a value between 18,000,000 and +18,000,000, and a Ycoordinate should be a value between 9,000,000 and +9,000,000. DELETED RECORD:
1 byte T: type (always 0)
4 bytes L5 bytes L: length of this record in bytes (including the T and L fields) bytes to ignore (content undefined)

SKIPPER RECORD:

1 byte 4 bytes T: type (always 1) Number of bytes in the file, including and starting at this record, that contain data for POI enclosed in the given rectangle X1: longitude coordinate of the west edge of the rectangle Y1: latitude coordinate of the south edge of the rectangle X2: longitude coordinate of the east edge of the rectangle Y2: latitude coordinate of the north edge of the rectangle

bytes bytes bytes bytes

SIMPLE POI RECORD:
1 byte 4 bytes 4 bytes 4 bytes L13 bytes T: type (always 2) L: length of this record in bytes (including the T and L fields) X: longitude coordinate of the POI Y: latitude coordinate of the POI Name: zeroterminated ASCII string specifying the name of the POI

EXTENDED POI RECORD:

P T: type (always 3) L: length of this record in bytes (including the T and L fields) X: longitude coordinate of the POI Y: latitude coordinate of the POI Name: zeroterminated ASCII string specifying the name of the POI Q bytes Unique ID: zeroterminated string specifying the unique ID of the POI LPQ13 bytes Extra data: zeroterminated string, not used yet byte bytes bytes bytes bytes
If you encounter any other type, either the file is corrupt, or the file contains extra (proprietary) records. In either case, you should stop processing immediately. Since there is always the danger that the file is corrupt, you should in fact wonder whether the preceding records read so far were in fact valid.

3. Itinerary files

It is possible to create your own itinerary files outside Navigator, and then use them from within. This section explains the file format. Refer to the C++ API for itineraryrelated APIfunctions.
3.1. Itinerary file format
The file format for itineraries is plain ASCII. an itinerary file consists of lines, each denoting one point in your itinerary. Normally, itinerary files are stored in the following folder:
\My Documents\TomTom Navigator Settings
and have the extension.itn Each line consists of the following fields, terminated by bar characters (|)
3.1.1. Fields in itinerary files
Field Field Field Field Longitude in WGS84 format (in 100 000th of degrees) Latitude in WGS84 format (in 100 000th of degrees) Name of this point in the itinerary Flag
3.1.2. Flags in itinerary lines
The flags in the itinerary lines can be ORed together. Currently, the following flags exist:
0x00 0x01 0x02 0x04 None Itinerary location is enabled Itinerary location is a stopover (as opposed to a passby location) Itinerary location is departure point (Should only be set for the first item in the itinerary file)
Example: \My Documents\TomTom Navigator Settings\Itinerary.itn Heres an example of an itinerary file representing a small itinerary in France:

concatbmpfiles result.tmt icon1.bmp mask1.bmp. iconN.bmp maskN.bmp

4.3. External POI files

To extend the POI capabilities of Navigator, seven types of points of interest have been reserved, with 12
4. Extending the Locationsensitive Menu POI type codes 9993 through 9999. External applications can, therefore, provide Navigator with up to seven additional POI types. The data for the POI of these types has to be packaged in a file placed in the \TomTom\ directory of the Pocket PC. The format of this external POI file is the following:
Index POI data for type 1. POI data for type N
The index has the following structure:
4 bytes 4 bytes. 4 bytes 4 bytes. 4 bytes 4 bytes N = Number of POI types Type code for POI type 1 Type code for POI type N File position of POI data for type 1 File position of POI data for type N Total file size
Where file positions are byte offsets from the start of the file, and all quantities are stored as littleendian integers. The POI data section for an individual POI type has the same structure as the.OV2 files, with the exception that only extended POI records and skipper records can be used, since the unique ID field, used to identify each point of interest to the external application, is not present in a simple POI record. Moreover, each POI type in an external POI file can optionally have a userfriendly name and an icon. The icon must be a.BMP file in the same directory as the external POI file. It is recommended that icons have a size of 22 by 22 pixels. For a POI type to have a userfriendly name and an icon, a special record of type 100 must be present at the beginning of the corresponding POI data section. This type of record consists of the following fields:
1 byte T: type (always 100) 4 bytes L: length of this record in bytes (including the T and L fields) P bytes Name: zeroterminated ASCII string specifying the name of the POI type LP5 bytes Icon: zeroterminated ASCII string specifying the name of the.BMP file
Where the name of the POI type is subdivided into several strings corresponding to different languages:
POINAME|dutch translation|english translation|french translation| italian translation|german translation|spanish translation| US english translation|

Please keep the strings for each language shorter than 25 characters, approximately. You can use the utilities SinglePoi.exe and ZipPoi.exe to associate a name and an icon with each POI type and create the final external POI file from the individual files for each POI type. If we have one.OV2 file for each POI type, named poi.nnnn, where nnnn is the POI type code in four decimal digits (9993 thru 9999), the following command will give it a name and an icon:
singlepoi "name" icon.bmp poi.nnnn
Where name is the userfriendly name of the POI type and icon is the name of the.BMP file to be used as its icon. This has to be done for each poi.nnnn file. NOTE: using SinglePoi.exe is not strictly necessary. The POI type will have a generic name and icon if this step is omitted. 13
4. Extending the Locationsensitive Menu Finally, to package all the POI types into a single external POI file, the following command can be used:

zippoi path result.poi

Where path is the pathname of the directory where the files for the individual POI types are located and result is the desired name of the resulting external POI file. The input files must have a name with the form poi.nnnn.
4.4. Format of the requests to external applications
When the user selects an external command from the locationsensitive menu, Navigator creates a request and sends a notification to the external application. The request is a text file (in the \TomTom\ directory) containing a single line with one of the following possible formats, according to the command type:
REQUEST|cmd name|2|longitude|latitude|
REQUEST|cmd name|4|unique id|
Where cmd name is the command name as given in the.CAP file, longitude and latitude are the WGS84coordinates of an arbitrary location in degrees multiplied by 100,000, and unique id is the unique ID of a point of interest from the external POI file. After the request has been created, a notification is sent to the external application, in the form of a Windows WM_COPYDATA message to the main window of the external application. The lpData member of the COPYDATASTRUCT structure referenced by the LPARAM parameter of the message points to a zeroterminated Unicode string with the pathname of the request file. If the external application is not running, Navigator will try to launch it. The external application should bring itself to the foreground in response to the notification using the SetForegroundWindow API. After the external application has finished processing the WM_COPYDATA message, Navigator deletes the request file.

Command Parameters: aFavorite As Long: index of favorite (base zero) Supported Since: TTN 1.42 Navigates to a specific favorite location. See Also: NavigateToCoordinate, ClearFavorite, SetFavorite, GetFavoriteName, GetFavoriteDescription, GetFavoriteLongitude, GetFavoriteLatitude
5.2.16. Sub ShowCoordinateOnMap( aLongitude As Long, aLatitude As Long)
Command Parameters: aLongitude As Long: longitude specified in WGS84 format (in millionths of degree). aLatitude As Long: latitude specified in WGS84 format (in millionths of degree). Supported Since: TTN 1.42 Centers the map around the given coordinate (zoomed in), specified in WGS84 format (longitude and latitude in millionths of degree). Example:
Sub ShowAmsterdam On Error GoTo ShowAmsterdam_Error Call TTNav.ShowCoordinateOnMap(4860000, 52380000) ShowAmsterdam_Exit: Exit Sub
ShowAmsterdam_Error: MsgBox "Failed to center around a point in Amsterdam" Resume ShowAmsterdam_Exit End Sub
See Also: NavigateToCoordinate
5.2.17. Sub ShowRectangleOnMap( aLongitudeW As Long, aLatitudeS As Long, aLongitudeE As Long, aLatitudeN As Long)
Command Parameters: aLongitudeW As Long: western Longitude specified in WGS84 format (in millionths of degrees) aLatitudeS As Long: southern latitude specified in WGS84 format (in millionths of degrees) aLongitudeE As Long: eastern Longitude specified in WGS84 format (in millionths of degrees) aLatitudeN As Long: northern latitude specified in WGS84 format (in millionths of degrees) Supported since: TTN 3.0 Show the given rectangle of the map. See Also: ShowCoordinateOnMap
5.2.18. Sub SendDirectCommand( aCommand As Long)
Command Parameters: aCommand As Long: code of the command to execute Supported Since: TTN 1.42 Performs one of various commands to change a setting or instruct TomTom Navigator to perform a certain task. The command codes are: 1 SoundOn: Turn spoken voice instructions on (works only when in navigation view) 2 SoundOff: Turn spoken voice instructions off (works only when in navigation view) 3 NightColors: Show map in night colors (works only when in navigation view) 4 DayColors: Show map in day colors (works only when in navigation view) 5 ShowMap: Show map and instructions while driving (works only when in navigation view) 6 HideMap: Only show instructions while driving (works only when in navigation view) 7 Recalculate: Recalculate a route (works only when in navigation view) 8 ShowPOI: Show points of interest on the map 9 HidePOI: Hide points of interest on the map 10 ShowExits: Show the next highway exit sign on screen (works only when in navigation view) 11 HideExits: Hide the next highway exit sign on screen (works only when in navigation view) 12 DisableGuidance: Disable active guidance support (works only when in navigation view) 13 EnableGuidance: Enable active guidance support (works only when in navigation view) 14 ShowCompass: Show compass on screen (works only when in navigation view) 15 HideCompass: Hide compass (works only when in navigation view) 16 GoHome: Navigate to the "Home" favorite (works only when in navigation view) 17 ShowFavorites: Show favorite locations on the map 18 HideFavorites: Hide favorite locations on the map Versions 1.51 and later of TomTom Navigator support also the following direct commands: 19 UnitsKm: set distance units to kilometers 20 UnitsM: set distance units to miles 21 AutoRecalcOn: turn on automatic recalculation of the route 22 AutoRecalcOff: turn off automatic recalculation of the route 19

Sub NavigateToAddress On Error GoTo NavigateToAddress_Error Call TTNav.Geocode("Zwanenburg", "Julianalaan", "12") If TTNav.GeocodeStatus <> 8 Then Call TTNav.NavigateToCoordinate(TTNav.GeocodeLongitude, TTNav.GeocodeLatitude, "Julianalaan, 12") Else MsgBox "Address not found" End If NavigateToAddress_Exit: Exit Sub NavigateToAddress_Error: MsgBox "Failed to navigate to address" Resume NavigateToAddress_Exit

End Sub

5.2.27. Sub GeocodeEx( aCity As String, aStreet As String, aHouseNr As String, aPostcode As String)
Command Parameters: aCity As String: city name. aStreet As String: street name. aHouseNr As String: house number. aPostcode As String: postal code. Supported Since: TTN 2.22 Find the location specified by an address, given by the city name, street name, house number and postal code arguments, and return the coordinates of the found location and its complete city and street names in the corresponding readonly properties of the control. If the street name argument is empty, the function will try to find the center of the city specified by the city name argument. As of version 2.22 of Navigator, the postal code will be only used as a help in trying to find the city. If no location is found with city and street names exactly matching the arguments, then a city and a street will be chosen with names as similar as possible to the given ones. This will be indicated in the geocode status property of the control. The return values are the same as those of Geocode.
5.2.28. Sub GetDataSetInfo( )
Supported Since: TTN 2.0 Obtains information about the currently selected data set. The information is available after this call in the following readonly properties of the control: Property DataSetName As String: name of the data set Property DataSetFlags As Long: explained below The data set flags property can contain the following flags: 1 indicates that the house numbers are written before the street name in addresses 2 indicates leftsided driving
5.2.29. Sub GetRouteInfo( )
Supported Since: TTN 2.0 Obtains information about the current route. The information is available after this call in the following readonly properties of the control: Property RouteStatus As Long: validity of the rest of the fields, as explained below Property RouteDepartureLongitude As Long: endpoint coordinates in millionths of degree (WGS84 format) Property RouteDepartureLatitude As Long: Property RouteDestinationLongitude As Long: Property RouteDestinationLatitude As Long: Property RouteEnclosingLongitudeW As Long: rectangle enclosing the route (coordinates in millionths of degree, WGS84 format) Property RouteEnclosingLatitudeS As Long: 25

5. Communicating with TomTom Navigator from Visual Basic Property RouteEnclosingLongitudeE As Long: Property RouteEnclosingLatitudeN As Long: Property RouteLength As Long: length of the route in meters Property RouteDuration As Long: duration of the route in seconds Property RouteDistanceToDestination As Long: distance from current position to destination in meters Property RouteTimeToDestination As Long: time from current position to destination in seconds The route status property can contain the following flags: 1 the departure point has been set 2 the destination point has been set 4 in the process of calculating a route 8 there is a valid route planned 16 time and distance to destination are available If GetRouteInfo has never been called, RouteStatus will be 0, indicating that the rest of these properties dont contain valid information.
5.2.30. Sub GetRouteCoordinates( aFileName As String)
Command Parameters: aFileName As String: name of the file to store in Supported Since: TTN 3.0 Store the coordinates of a list of points from the current route in the specified file.
5.2.31. Sub UseGFFile( aFilename As String)
Command Parameters: aFilename As String: full name of the GF file Supported Since: TTN 2.0 Instruct Navigator to display a GF file, discarding the previous GF file (if any). See Also: EnableGFRecord
5.2.32. Sub EnableGFRecord( aRecordID As Long, aState As Boolean)
Command Parameters: aRecordID As Long: unique ID of the record to be enabled or disabled aState As Boolean: whether to enable or disable the record Supported Since: TTN 2.0 Enable or disable a record in the current GF file. See Also: UseGFFile
6. Communicating with TomTom Navigator from C++

6.1. Introduction

This SDK allows thirdparty application developers to communicate with TomTom Navigator. The SDK comes with a library that allows external applications to communicate with TomTom Navigator. The first version of TomTom Navigator to fully support this library is 1.42. To use the library, link the executable C++ application with the library "TTNCom.lib" (this library is provided for ARM, MIPS and SH3), and include the header file TTNCom.h. The library contains a class CTomTomNavigatorCom with static methods which can perform the communication request.

6.2.17. INT GetCurrentPositionV01( EGpsStatus & aStatus, TTTnLocationV01 & aLocation)
Command Parameters: EGpsStatus & aStatus: at return, if no error occurred, contains an indication of the quality of the data received. TTTnLocationV01 & aLocation: struct that will be filled with the location information Returns: 0 if successful, nonzero value otherwise. Supported Since: TTN 1.42 Fills the struct passed in with current position information from GPS. Example: It shows how the GetCurrentPosition call can be used to warn when the driver is driving too fast. 31
EGpsStatus status; TTTnLocationV01 loc; INT error = CTomTomNavigatorCom::GetCurrentPositionV01(status, loc); if (error) { ::AfxMessageBox(TEXT("Failed to get the current location")); } else { if (status >= 0 && loc.iSpeedKMh > 120) { ::AfxMessageBox(TEXT("You are driving too fast!")); } }
6.2.18. INT MakePoiVisible( EPoiTypeCode aPoiID, INT aVisibility)
Command Parameters: EPoiTypeCode aPoiID: POI unique type identifier INT aVisibility: whether to show or hide this POI type on the map Returns: 0 if successful, nonzero value otherwise. Supported Since: TTN 1.42 Enable or disable displaying a specific POI type.
6.2.19. INT AddPoi( LPCTSTR aFilename, long aLongitude, long aLatitude, LPCTSTR aName, LPCTSTR anId)
Command Parameters: LPCTSTR aFilename: name of the POI category long aLongitude: longitude specified in WGS84 format (in millionths of degree) long aLatitude: latitude specified in WGS84 format (in millionths of degree) LPCTSTR aName: name of the POI LPCTSTR anId: optional external identifier of the POI Returns: 0 if successful, nonzero value otherwise. Supported Since: TTN 1.51 Add a point of interest to the.OV2 file specified by the POI category argument. The point of interest will have the name and coordinates given by the corresponding arguments. An external identifier string can also be attached to the point of interest. Example: The following example invocation call demonstrates how to create a new point of interest:
INT error = CTomTomNavigatorCom::AddPoi(_T("ATM"), 4749620, 52374810, _T("Postbank"), _T("")); if (error) { ::AfxMessageBox(TEXT("Failed to create the point of interest")); }
See Also: DeleteClosestPoi, DeleteAllPoi, MakeUserPoiVisible, MoveClosestPoi 32

6.3.4. TTTnLocationV01 structure
The TTTnLocationV01 struct contains the following fields: long iLongitude Longitude and latitude in millionths of degree (WGS84 format) long iLatitude int iDirection Direction in degrees: zero is north, continuing in clockwise direction int iSpeedKMh current driving speed in kilometers per hour
6.3.5. EGpsStatus enumeration
Status specifies if the information in this record is recent or not. Status<0 means some error occurred (1 is general), Status>=0 means the data is valid. Currently allowed values are:
KErrGeneral KErrReceiving
6.3.6. TGeocodeInfoV01 structure
The TGeocodeInfoV01 struct contains the following fields: int iStatus Validity of the rest of the fields, as explained below long iLongitude Longitude and latitude in millionths of degree (WGS84 format) long iLatitude TCHAR iCityName[128] Complete city name TCHAR iStreetName[128] Complete street name The status field can contain the following flags: KGeocodeFailure no location found at all, the rest of the fields are invalid KGeocodeCityAmbiguous the given city name was ambiguous, random (possibly wrong) selection made 42
6. Communicating with TomTom Navigator from C++ KGeocodeStreetAmbiguous the given street name was ambiguous, tried to make smart selection KGeocodeHouseNrIgnored the house number was ignored, either because there was no house number data available or because the given house number was not found
6.3.7. TLocationInfoV01 structure
The TLocationInfoV01 struct contains the following fields: int iType The type of the given location TCHAR iStreetName[128] The street name of the given location int iHouseNr1 The first housenumber closest to the given location int iHouseNr2 The second housenumber closest to the given location The type field can be one of the following: KLocationTypeNode the location is a node, i.e. a crossing KLocationTypeRoad the location is a street
6.3.8. EPoiTypeCode enumeration
The Point of Interest types that are supported are: KPoiTypeGovernmentOffice KPoiTypeMountainPeak KPoiTypeOpenParking KPoiTypeParkingGarage KPoiTypePetrolStation KPoiTypeRailwayStation KPoiTypeRestArea KPoiTypeAirport KPoiTypeCarDealer KPoiTypeCasino KPoiTypeChurch KPoiTypeCinema KPoiTypeCityCenter KPoiTypeCompany KPoiTypeConcertHall KPoiTypeCourthouse KPoiTypeCulturalCenter KPoiTypeExhibitionCenter KPoiTypeFerryTerminal KPoiTypeFrontierCrossing KPoiTypeGolfCourse KPoiTypeHospitalPolyclinic KPoiTypeHotelMotel KPoiTypeTouristAttraction KPoiTypeMountainPass KPoiTypeMuseum KPoiTypeOpera KPoiTypePlaceofWorship KPoiTypePostOffice KPoiTypeRentCarFacility KPoiTypeRentCarParking KPoiTypeRestaurant 43

6. Communicating with TomTom Navigator from C++ KQuickCmdFind Find menu KQuickCmdGPSStatus GPS status KQuickCmdMemorizePosition Memorize this position KQuickCmdNavigateTo Navigate to KQuickCmdOriginal Reset to original route KQuickCmdProperties properties menu KQuickCmdShowMap Show the map view KQuickCmdShowNextMotorway Display the next motorway KQuickCmdShowPOI Show POIs on the map KQuickCmdShowSpeed Show speed on the map KQuickCmdSkipNextDriveBy skip the next driveby in the itinerary KQuickCmdSwitchMap switch map KQuickCmdTurn3DViewOn go to #D view KQuickCmdTurnGuidanceOn Use voice guidance KQuickCmdTurnSoundOn switch on the sound KQuickCmdUseDaylightColors switch to daylight colours
Additionally, the following functions are only available to assign to hardware buttons: KQuickCmdDisplayCompassOnMap display a compass on the map KQuickCmdFavorites go to favourites menu KQuickCmdInstructions Show instructions for the route KQuickCmdMap switch to map view KQuickCmdNavigateToAddress Navigate to something KQuickCmdNavigateToFavorite KQuickCmdNavigateToHome KQuickCmdNavigateToPOI KQuickCmdNavigateToRecent KQuickCmdVolumeDown change volume of voice prompts KQuickCmdVolumeUp KQuickCmdZoomMapIn zoom in/out on map KQuickCmdZoomMapOut KHwButtonDefaultFunction For hardware button 14 only: do original function
7. Graphic Information Files
This section explains how to create graphic information files, also called GF files.

7.1. About GF Files

You can provide "graphic information" to TomTom Navigator in the form of a file consisting of variablelength records describing graphic shapes and elements (e.g. representing dynamic situations such as traffic conditions). TomTom Navigator will load and maintain such a file as soon as you pass it the path name of the file, using the routine UseGFFile. When this routine returns, TomTom Navigator will have discarded any previous files, and will have loaded the new file into memory. The caller is thus free to delete or change the file after having called this routine. Calling UseGFFile with an empty name, or with the name of a nonexistent or empty file, in effect "clears" any previously loaded data. For any change in the situation (e.g. the traffic situation) either call EnableGFRecord with the unique id of some record you want enabled or disabled, or call UseGFFile with the name of a new or adjusted file (or with the empty string as filename, which effectively deletes all the current records). Caveats: On general principles, it is recommended that you "refresh" files relating to traffic information every 15 minutes even if there are no changes. On the other hand, there are obvious disadvantages to refreshing files too often, e.g. every few seconds, in terms of power drain, application speed degradation etc. Tips: For some applications, it may be useful to switch between a limited set of predefined, fixed files. For some applications, it may be useful to use a single predefined file, of which records are "enabled" or "disabled" by the simple action of stamping them with an "endofvalidity" in the past resp. the future.