These APIs are used to start & exit CoPilot. It also used to start and shutdown messaging.
|Determines whether the messaging layer has been initialized by a call to Msg_StartUp(). In most scenarios, this should be the first API called, as this will determine if CoPilot is already initiated and connected.
|Starts up messaging communications using user.cfg [ConnectionInfo1] file for connection parameters.
|Determines if the application layer is actually connected to the CoPilot application. Use this API to check that the application communication is established, once Msg_Startup has been called.
|The call to Launch CoPilot, this offers a simple launch with options to show/hide.
|Launch CoPilot including show/hide mode but with advance option to define the window parameter CoPilot will run within.
|Send message for CoPilot to exit properly if messaging is connected. If messaging is not connected, it will close the CoPilot process forcefully.
|It will retrieve the CoPilot window handle.
|Send message to CoPilot to exit the application properly. If it is not possible to close the application properly, CoPilot will not exit. We recommend to use ALK_ExitCoPilot rather than this API.
|Shuts down the messaging communications between the two application. This function must be the last function before the client application exits.
These APIs are used to set the callback based on message type. It also used to provide queue functionalities if platform does not support callback.
|Set a callback function for a particular message type. Used in conjunction with subscription-based messages. We recommend using Msg_UpdateOptions instead of Msg_SetCallback.
|Updates the options for different ALK messages. Primarily used for setting callback function. We recommend to use Msg_UpdateOptions instead of Msg_SetCallback.
|Subscribe to event-based notification of real-time information from the CoPilot application.
|Unsubscribe to event-based notification of real-time information from the CoPilot application.
These APIs are used to delete the parser previously allocated when sending data to CoPilot.
|Delete a previously-allocated message buffer handle and free associated resources.
The below APIs are used to activate/deactivate and query license status.
|This function use to activate the license by passing the product key. Response of the activation is being send by Msg_ID_LicenseResponse.
|This function use to deactivate the license by passing the product key. Response of the deactivation is being send by Msg_ID_LicenseResponse.
|This function use to retrieve the license information associated with given product key.
|This function is helper function to decode the response received in context of Msg_ActivateLicense and Msg_DeactivateLicense. This function is also use when CoPilot send the notification regarding license when CoPilot start up.
|This function is helper function to decode the response received in context of Msg_LicenseStatus.
|This API will be used following Msg_ActivateLicense to determine which map region CoPilot is currently locked to for licensing purposes, or to determine that a map region has not yet been selected. This should be used following the activation of a major region license, for instance, UK, France or DACH. It is not required if you have a PAN region license as there is no selection necessary.
|This API will be used following Msg_ActivateLicense to determine a list of the available map data regions with the current license. This should be used following the activation of a major region license, for instance, UK, France or DACH. It is not required if you have a PAN region license as there is no selection necessary.
|This API can be used to specify the map region CoPilot will use, on the condition that the current license allows for that region as determined by Msg_GetAllowedMapRegions. Once a region has been set it can not be changed.
|This API can be used to interpret the data received from Msg_GetCurrentMapRegion(), Msg_GetAllowedMapRegions(), Msg_SetLockedMapRegion(). This will provide the action code related to the callback and indicate which API the response you have received relates to.
|This API can be used to interpret the data received from Msg_GetCurrentMapRegion(), Msg_GetAllowedMapRegions(), Msg_SetLockedMapRegion(). This will provide the action code related to the callback and indicate the status of the response you have received.
|This API can be used to determine the number of regions that are included in a response from a call to either Msg_GetCurrentMapRegion(), Msg_GetAllowedMapRegions () or Msg_SetLockedMapRegion(). Use this API alongside Msg_ParseMapRegionResponseRegionInfo() to extract more detailed information about each region that was included in the response.
|This API can be used to extract the map region info included in a response from a call to either Msg_GetCurrentMapRegion()Msg_GetAllowedMapRegions or Msg_SetLockedMapRegion(). Use this API alongside Msg_ParseMapRegionResponseNumberOfRegions() to extract more detailed information about each region that was included in the response.
These APIs are used to send the destinations to the CoPilot application, including waypoint, as well as retrieving current stop information.
|Allocate a trip message buffer and return its buffer handle. This needs to be included in every new trip to be sent to CoPilot. This defines the options for how the trip is to be added.
|Add a stop to a previously allocated trip message buffer, all individual stops need to be added. To be used when House number and Street Address need to be defined separately. We recommend client application uses Msg_TripAddStopWithHouseNum instead of Msg_TripAddStop.
|Send a new trip itinerary (list of stops) to the application. This is used following Msg_TripLoad and Msg_TripAddStopWithHouseNum.
|This is the first API to be used if you want to receive all of the details of the currently loaded Trip. Decodes and retrieves the message ID from a trip message buffer.
|This is the second step to be used if you want to receive details of the currently loaded Trip. This provides header information including the total number of stops.
|Used in conjunction with Msg_Trip* APIs, returns itinerary stop list information from a Msg_ID_Trip message, returning all individual stop details. We recommend to use Msg_tripGetStopWaypointInfo instead of Msg_TripGetStopInfo.
|Used in conjunction with Msg_Trip* APIs, returns itinerary stop list information from a Msg_ID_Trip message, returning all individual stop details including Waypoints. We recommend to use Msg_tripGetStopWaypointInfo instead of Msg_TripGetStopInfo.
|Sends the request to CoPilot to get the list of stops in CoPilot’s itinerary, to be followed by Msg_TripGet* APIs. We recommend to use Msg_SendStopInfoRequest instead of Msg_SendTripStopInfoRequest.
|Sends the request to CoPilot to get the list of stops in CoPilot’s itinerary, to be followed by Msg_Trip* APIs. Includes information on Waypoints. We recommend to use Msg_SendStopInfoRequest instead of Msg_SendTripStopInfoRequest.
|Used in conjunction with Msg_TripLoad with the parameter Msg_ACTOPT_RETMULTIMATCH. Returns the message ID to be used with Msg_MultiStopGet* APIs.
|Used in conjunction with Msg_TripLoad with the parameter Msg_ACTOPT_RETMULTIMATCH. Returns the header information including the number of stops.
|Used in conjunction with Msg_TripLoad with the parameter Msg_ACTOPT_RETMULTIMATCH. Returns the individual stop details.
These APIs are used to geocode the stop to latitude/longitude as well reverse geocoded from latitude/longitude to stop.
|Request to CoPilot providing a latitude/longitude for an address.
|Request to reverse geocode and provide the address closest to the given latitude and longitude.
|Retrieves and decodes the address information from a Msg_ID_ReverseGeocode message. To be used in conjunction with Msg_RequestReverseGeocode.
These APIs are used to do typeahead search for address. By using these APIs, customers can implement a very similar address entry experience as the one in CoPilot.
|Request a search of City and Postcodes based upon provided prefix. This API gives same results like user type in CoPilot.
|Following Msg_SearchCityAndPostcode this will request a search for a street based upon provided criteria including partial name.
|Following Msg_SearchStreet returns complete street name this API will return all multiple matches for the street and house number.
|Requests to retrieve more search results (city, postcode or street) based upon last request, used when more results are available than max results provided.
|Required to retrieve results following a city, street or postcode search. Decodes and retrieves the message ID from a search message buffer.
|Required to retrieve results following a city, street or postcode search. Retrieves the search address details from given search.
|Required to retrieve results following a city, street or postcode search. Retrieves the search identifier, search count and error codes.
|Once the city, postcode or street search completed this API should be used to remove the cache results from the memory and stop searching.
These APIs are used to provide POI search functionality. User can search the POI based on current location, on the route and at location within specified radius.
|Request a search of POIs based upon a series of criteria including by category, location, on a route etc.
|Sends a request to retrieve more POIs based upon last request criteria provided in Msg_SearchPOIEx.
|Required to retrieve results following Msg_SearchPOIEx and Msg_RequestMorePOI. Decodes and retrieves the message ID from a POI search message buffer.
|Required to retrieve results following Msg_SearchPOIEx and Msg_RequestMorePOI. Decodes and retrieves the POI count and error codes.
|Required to retrieve results following Msg_SearchPOIEx and Msg_RequestMorePOI. Returns the POI details for the selected result.
|Once the POI search is completed this API should be used to remove the cached results from memory and stop searching POIs.
The below APIs are used to set/get the favorites to/from CoPilot.
|Set the request to CoPilot to add the given favorites including home, work and others.
|Sends the request to CoPilot to to retrieve favorites. To be followed by Msg_FavoritesStopParse, Msg_FavoritesStopGetHeader, Msg_FavoritesStopGetDetails to retrieve favorite stop details.
|This is the helper function to retrieve the favorite stops requested using Msg_SendFavoritesStopRequest. Returns the parser ID to be used with Msg_FavoritesStopGetHeader and Msg_FavoritesStopGetDetails.
|This is the helper function to retrieve the favorite stops requested using Msg_SendFavoritesStopRequest. Returns the header information including the number of stops and any error.
|This is the helper function to retrieve the favorite stops requested using Msg_SendFavoritesStopRequest. Returns the individual stop details.
These APIs are used to add and delete custom POI categories dynamically to CoPilot.
|Request to add the Image Drawer category. It accepts the series of lat/longs, image name and category name.
|Use to delete specific Image Drawer category.
|Use to delete all user defined Image Drawer categories.
|Use to add a callback function to receive events when a map image drawn by Msg_DrawImageAtCoordinates is touched on the screen.
|The function type of the callback function to be passed into Msg_AddMapImageClickedHandler
These APIs are used to retrieve and set different type of settings in CoPilot. These APIs are also used to retrieve acknowledgement of the message sent to CoPilot. Additionally they are also used to retrieve map data list, itinerary, eta/distance etc.
|Sends a generic data message Msg_ID_GenericData to CoPilot. It will use to set/get the settings and request some generic operation.
|Decodes and retrieves requested information through Msg_ID_GenericData.
|Returns result for geocoding success, including error codes for destination details that have failed to geocode. To be used following Msg_SendTrip.
|Use this function to toggle a stop to a waypoint and vice versa.
|CoPilot itinerary cleared.
|Use this function in conjunction with Msg_SearchCityAndPostcode to set the number of results returned.
|Use this function in conjunction with Msg_SearchCity / Msg_SearchPostcode/Msg_SearchCityAndPostcode to set the number of results returned.
|To be used in conjunction with Msg_SearchPOIEx, to clear the CoPilot cache memory. We recommend that you use Msg_ClearPOIResults.
|To be used in conjunction with Msg_SearchCityAndPostcode, to clear the CoPilot cache memory. We recommend that you use Msg_ClearSearchResults.
|To be used in conjunction with Msg_ID_GuidanceMap to provide the map image once.
|This API enables the client application to zoom in and out of the map image.
|CoPilot in 3D mode will automatically zoom in and out of the map details based upon vehicle speed. Autozoom is currently switched on by default, until the user touches the zoom buttons, this then switches off the autozoom. Use this function to re-enable the autozoom.
|Returns the current value set within CoPilot for distance measurement.
|Sets Mute / Un-Mute value for all audio alerts within CoPilot including speech.
|Retrieves the current status Mute / Un-Mute value for audio alerts within CoPilot.
|CoPilot will play the last spoken instruction.
|This will change the volume setting within CoPilot. This will also set device volume.
|This identifier enables CoPilot to send an event notification to the client application to provide a pre-notification of a navigational audio alert
|Changes the current view mode within CoPilot.
|Changes the current heading setting within the view, north up or heading up.
|Extends the 2D view to include current or last known position and next stop within the stop list.
|Changes the setting of day and night mode within CoPilot.
|Enables the client application to lock the menu within CoPilot, so that the user is not able to access menu options. Often used in conjunction with monitoring vehicle movement to enhance driver safety. To monitor vehicle movement use Msg_SendGPSPositionRequest.
|Controls the Soft Input Panel within Operating System, allows this to be removed to stop users returning to the OS.
|Provides the ability to disable / enable GPS within CoPilot.
|Re-open GPS port to be used in after Msg_SendNMEA if you want to re-use the default GPS port.
|Ability to avoid Ferries.
|To be used in conjunction with Msg_ID_WindowMode, Msg_ID_ResizeCoPilot and subscribe/unsubscribe Msg_ID_GUIDANCEMAP return when the function has completed.
|Toggles the screen orientation between Portrait and Landscape
|If the hardware requires more memory you can call this to free up all cache memory of CoPilot.
|Sets the backlight status.
|Controls the setting for truck warning and alerts.
|Provides the ability to amend the cost associated with u-turns.
|Provides the ability to display or remove POIs from the screen.
|Use this to enable / disable truck alerts from the CoPilot application and to provide them only to the client application.
|This will ensure that all trip information is deleted each time CoPilot is exited.
|CoPilot automatically moves the position to the current GPS location. To disable this and allow the user to drag the map and view other locations. It is usually required when using Msg_SetMapPan and Msg_ZoomToStop.
|This message provides acknowledgement for Msg_IDT_LOADPROFILE message. Client can load the profile using Msg_SendGenericTextData with identifier (Msg_IDT_LOADPROFILE) and this message will provide acknowledgement
|This message provides acknowledgement for Msg_SetFavoritesStopInfo API. Following is the success and failure code.
|This message provides notification when CoPilot is hidden. This is a notification only message and will be sent by CoPilot when the user presses the hide button.
|Is the first message to be used in conjunction with Msg_GenericInformation* APIs. Requests information from CoPilot, Msg_ID_GenericInformation. Used to set/get the settings and request generic operation.
|Decodes and retrieves the message ID from a generic information message buffer.
|Decodes and retrieves the header information (item counts, message id etc.) from a generic information message buffer.
|Decodes and retrieves the request specific information from a generic information message buffer.
|Returns information on the map data region.
|Returns ID, name and ISO code for the map data countries within the region – this does not represent the installed country information.
|Returns name and abbreviation for the map data states within the region – this does not represent the installed country information
|Returns ID and name for the POI categories.
|Returns information to the client application providing the itinerary of turn instructions and street names to the next destination.
|Provides the complete ETA and distance for all destinations. This should be the first request for ETA and distance. For one destination or one off ETA/Dist, need to use Msg_IDT_ETADIST.
|Provides the ETA and distance for the next destination, and should be used for all subsequent requests for ETA and distance. We recommend using Msg_GetTurnDistances instead of Msg_IDT_COMPLETE_ETADIST.
|Returns the ID and name for all languages and voices available.
|Returns the ID and name of the current language and voice selected.
|Returns the latitude, longitude, address error, place error and stop name for successfully geocoded stops. If the destination passed has failed to geocode this will return the error code and stop name.
|Provides the CoPilot version number.
|Returns CoPilot memory usage information.
|Enables the ability to change the current settings for POI categories being displayed on screen to the end user.
|Creates a generic message with a particular ID to be sent from client application to CoPilot to change the current settings for language, voice, lane assist and POI categories to be displayed.
|Encodes the information and adds it to the Msg ID returned from the Msg_CreateGenericInformation.
|Enable and disable the speed limit display in CoPilot
|Enables the ability to change the current language and voice set within CoPilot.
|Enables the ability to change the current setting to show or not show the Lane Assist information.
|Suspends navigation in CoPilot. Guidance will stop and the current position will not be updated, but the GPS receiver will continue to run in the background.
|Sends a generic message with a particular ID to be sent from client application to CoPilot to change the current settings for language, voice, lane assist and POI categories to be displayed.
These APIs are used to set/get the CoPilot settings stored in user.cfg. Different types of settings can be set/retrieved using one of the following APIs.
|In order to configure CoPilot settings, they are saved as a file in user.cfg – contained in the program files/copilot folder. This API is used to set the integer or boolean variables values. For Boolean use 0 or 1.
|In order to configure CoPilot settings, they are saved a file in user.cfg – contained in program files/copilot folder. This API is used to set the string variables value.
|In order to configure CoPilot settings, they are saved as a file in user.cfg – contained in program files/copilot folder. This API is used to retrieve the integer or boolean variables values.
|In order to configure CoPilot settings they are saved in a file in user.cfg – contained in program files/copilot folder. This API is used to retrieve the string variables value.
|This is used to add a callback to receive the messages from CoPilot when setting or getting the values using Msg_ConfigSetIntVal, Msg_ConfigSetStrVal, Msg_ConfigGetIntVal, Msg_ConfigGetStrVal
|This is the definition of the callback function for receiving a response from CoPilot when using Msg_ConfigSetIntVal, Msg_ConfigSetStrVal, Msg_ConfigGetIntVal, Msg_ConfigGetStrVal
These APIs are used to retrieve version number of CoPilot, POI, Data and City.
|This is used to request the version information from CoPilot.
|Decode the version information received from CoPilot in response to a Msg_RequestVersionInfo() call. The response contains version information for CoPilot, Data, City and POIs. Msg_UpdateOptions() should be used to establish a callback for message ID Msg_ID_VersionInfo in order to receive the response from CoPilot.
These APIs are used to retrieve GPS position information from CoPilot. It also provides functionality to send NMEA message to CoPilot.
|Request current position information from CoPilot. Including the current lat/long, vehicle speed and heading.
|Decode and retrieve the current position information from CoPilot. Including the current lat/long, vehicle speed and heading.
|Sends an NMEA-formatted message to the CoPilot application. Used to provide GPS information into CoPilot via the client application.
These APIs are used to set and retrieve the vehicle profile. These APIs are also useful to subscribe for turn distances, turn instruction, different routing events, speed limit event, country border event etc.
These APIs are used to set and retrieve the truck profile which includes height, width & weight of the truck, hazmat restriction, speed and avoid/favour for type of road etc.
|Truck alerts are provided to inform the drivers of hazards on the road ahead, including sharp curves, steep hills, cross winds etc. Use this to receive these alerts via the client application as it decodes truck alert message from the message buffer received through subscription of Msg_ID_TruckAlert.
|Provides event based routing information through subscription of Msg_ID_RoutingEvent. The routing information includes: Route Calculation Progress, destination reached event, GPS signal loss, waypoint passed, destination changed event, restricted road event.
|Used to monitor when a route calculation has started.
|Monitors route calculation is in progress.
|Used to monitor route calculation has finished.
|Driver has reached their destination.
|CoPilot has detected that there is no GPS signal.
|CoPilot has detected that GPS signal has returned.
|CoPilot is determining the current position.
|There are no destinations within the CoPilot itinerary.
|CoPilot is searching for a GPS signal.
|One of the waypoints in CoPilot itinerary has been passed.
|CoPilot itinerary changed – used to monitor itinerary changes linked with destination passed, waypoint passed, new destination added.
|Reports if the destination set is on restricted route.
|Route contain restricted road.
|Route calculation has failed.
|Distance Unit Changed
|This notification is being sent when user is X miles/kms (based on the unit selected in CoPilot) away from the destination. User can configure the X distance by following of the 2 ways.
|This provide notification to SDK if RouteSync provided route is not match with planned route by CoPilot.
|This provide notification to SDK on completion of route sync route calculation.
|This provides traffic delay notification in minutes if traffic is found on the route.
|Provides turn distance information received through a subscription to Msg_ID_TurnDist. Turn information includes next and second turn distances.
|Returns turn instruction information received through a subscription to Msg_ID_TurnInstructions. Information includes turn image, street information and street class information. We recommend using Msg_GetTurnInstructionsEx instead of Msg_GetTurnInstructions.
|Decode and retrieve the country border crossing information contained in a message buffer received through a subscription to Msg_ID_CountryBorderEvent
|Decode and retrieve the Over-SpeedLimit and Current- SpeedLimit information received when subscribing for Msg_ID_OverSpeedLimitEvent or Msg_ID_CurrentSpeedLimitEvent
|Event alerts for current and overspeed notification
These APIs are used to control the GUI of CoPilot as well as provide shared maps functionalities. They are also used to resize CoPilot, Panning the map inside CoPilot and to customize the info bar.
|Change the application window’s show state, including hide and topmost options.
|CoPilot will zoom to a given location on the map. This is not added as destination, but used to mark/search an area not the current location.
|Request to resize CoPilot window after CoPilot is already launched. (V9 and Above).
|Request to show a specific page within CoPilot. This can be used to hide specific options until no other option available, for example destination entry menu.
|Shows the Menu page.
|Passes a new destination saved within CoPilot as the Home address. If no home address is set, it will display address entry to add Home address.
|Shows the Recent history of destinations entered.
|Shows the Favorite list of user destinations.
|Shows the address entry wizard screens.
|Starts a demo trip running.
|Shows the Routing menu within CoPilot.
|Shows the routing profile menu screens within CoPilot.
|Shows the Plan Edit Trip screens.
|Displays the Legal Warning.
|Calculate and Show Route.
|Display the POI dialog box.
|Display the No Map data warning for entered latitude/longitude.
|Stop the route demo.
|If the client application also contains a mapping application. this API will help to match the CoPilot location and zoom level to the inbuilt map – providing the user with smooth switching of maps. It is used to request the device projection coordination. This response is received as Msg_ID_DevProjCoordinate. The user needs to setup a callback function using Msg_UpdateCallback to receive and process the message with message id Msg_ID_DevProjCoordinate.
|This API is used to parse the message with message id Msg_ID_DevProjCoordinate.
These APIs are used to control the map update feature in CoPilot. It allows the user to start/pause/stop new map data from the server as well allows the user to switch map data.
|This API is used to receive the notification sent by CoPilot while processing the requests sent using the Msg_MapUpdate. The parameter is callback function of type MsgHandlerMapUpdate that will be called when the notification is received from CoPilot. The Client Application will need to write its implementation of the callback function of the type “MsgHandlerMapUpdate”.
|This API is used to receive the notification sent by CoPilot while processing the requests sent using the Msg_MapUpdate.
|This is designed to be used for the specific version map update process for CoPilot. This API can be used to download and update to a specific version(denoted by a quarter and year) of map data.
|This is designed to be used for the specific version map update process CoPilot. This API can be used to download and update to a specific version(denoted by a quarter and year) of map data.
|This is designed to retrieve the currently installed or licensed list of maps on CoPilot
|This API is used to receive the notification sent by CoPilot while processing the requests sent using the Msg_MapActionRequestSpecific, Msg_MapActionRequestGeneric, or Msg_MapActionRequestDataList APIs.
|This API is used to receive the current download status generated by CoPilot while processing the download requests sent using the Msg_MapActionRequestSpecific, Msg_MapActionRequestGeneric, or Msg_MapActionRequestDataList APIs.
These APIs are used to work with RouteSync functionalities.
|CoPilot is able to receive a route planned via a third-party application passed into CoPilot via latitude/longitude values. These locations will be used to generate the matching route /roads already planned. This is used to send a raw flex message from the SDK to CoPilot. Client Application cannot generate messages to be sent. Currently Only RouteSync Object received from PC*MILER can be used with this.
|This APIs used to set the callback for RouteSync message which allowed client application to monitor when and where user left the prescribed route, join the route and total out of route mileage.
|CoPilot is able to receive managed routes using JSON. These locations will be used to generate the matching route /roads already planned, handle response events from CoPilot on a per event basis. Each event will have its own callback function.
|This APIs used to set the callback for RouteSync managed message which allowed client application to monitor when CoPilot receive the Routesync data.
|Provides lat/long coordinates from the input file that is not included on the route generated by CoPilot. These details are provided through subscription of Msg_ID_RouteSyncPointsOff.
The below APIs are used to enable CoPilot TTS voice to read strings passed into it from third party applications.
|This API is used to send the request to CoPilot to speak the TTS message. For this to work, CoPilot should have TTS voices selected.
|This API is used to set callback to receive notifications when requesting a TTS message to be played by CoPilot.
|Function definition of the callback function when setting a callback using Msg_TTSRequestCallback.
Below are the APIs user for the advanced optimization calculations which can be made by CoPilot
|User can pass the route header information by using this function. This is the first function needs to call before passing the stops, this defines driver start time, start location and end location.
|This function will pass the destination address details; including open and close window time and the onsite wait time. This function needs to be called for each destination.
|This function will pass the destination address details; including open and close window time and the onsite wait time (same as ALK_SendRouteStop), in addition, the blocking window open and close time. A blocking time means, do not reach this destination between these two times. For example a shop is open between 9am to 5 but closes 12pm to 1pm for lunch.
|This function will pass the destination address details; including open and close window time and the onsite wait time (same as ALK_SendRouteStop), in addition, a second window open and close time. A second time window is when you provide two positive destination reached time. For example a shop is open between 9am to 12pm and 1pm to 5pm.
|After passing route header and destination details, call this function to start the Optimization and/or ETA calculation process.
|This call will stop the ETA calculation process at an appropriate time.
Below APIs are used to draw polygons and retrieve geofence events based upon drivers entering or exiting defined zones
|This API is used to import Polygon Sets from an XML file. See note 2 for an example input file and note 3 for a description of the fields available for these objects.
|This API is used to delete polygons. It can delete all polygons, a specific polygon set, or a specific polygon or polygons within a specific set.
|This API is used to set a value of a polygon set after it has been imported.
|This API is used to set a value of a polygon after it has been imported.
|This API is used to get a value of a property of a polygon set after it has been imported.
|This API is used to get a value of a property of a polygon after it has been imported.
|Decode and retrieve the information contained in a message buffer received through a subscription to Msg_ID_GeofenceEvent. These events occur when the users current position enters or leaves a geofence containing flags to send messages
|Decode and retrieve the information contained in a message buffer received through a subscription to Msg_ID_GeofenceRoutingEvent. This event is triggered when a new route is created which passes through any geofences with the “RouteThroughEvent” property set.