getRouteOptions
Command
Retrieves current route options
Send this JSON-RPC message in the
BND_MESSAGE extra of an Intent with the action ACTION_RNC_BROADCAST, to BeNav's activity or receiver: see Sending commands.Reads back the routing and display preferences currently in force: how routes are optimised, which road types are allowed, whether traffic is taken into account, the unit system and the map theme.
Mostly used to establish a starting point before changing anything with
setRouteOptions, or to confirm that a configuration pushed earlier is still the one in
effect.
Command#
json
{
"jsonrpc": "2.0",
"method": "getRouteOptions",
"id": "1"
}Response#
Success#
json
{
"jsonrpc": "2.0",
"result": {
"routeMode": "FASTEST",
"crossing": true,
"ferry": true,
"motorway": true,
"sideArrival": false,
"toll": true,
"traffic": false,
"autoReroute": true,
"unpaved": true,
"altRoutes": true,
"units": "METRIC",
"showVehicleProfileName": false,
"showRestrictions": false,
"mapDisplayMode": "LIGHT"
},
"id": "1"
}routeModePossible values [FASTEST|SHORTEST].crossingAllow or disallow border crossing (if possible)ferryFerry allowedmotorwayMotorway allowedsideArrivalArrival on defined destination side or nottollToll roads allowedtrafficTake into account traffic jams during route calculations (if traffic service available)autoRerouteAuto-reroute when traffic information is updated (iftrafficis enabled)unpavedUnpaved roads allowedaltRoutesAlternative routes enabled or disabledunitsPossible values [METRIC|IMPERIAL].showVehicleProfileNameShow vehicle profile's name on the mapshowRestrictionsShow vehicle restrictions on mapmapDisplayModePossible values [LIGHT|DARK|AUTO].
Error#
Generic errors.