Defines options for routing tiles endpoint and storage configuration.
Routing tiles are stored on-device and used for map-matching (enhanced location production), offline routing, Electronic Horizon generation, and other.
scheme and host, for example
"https://api.mapbox.com". If empty, the navigator works in the fallback mode all the time (route line following; no full map-matching; no map-matching in free drive).
string built out of
<account>[.<graph>] variables. Account can be
mapbox for default datasets or your username for other. Graph can be left blank if you don't target any custom datasets.
profile of the dataset. One of (driving|driving-traffic|walking|cycling|truck).
version of tiles, chosen automatically if empty
used for persistent configuration and history files storing.
tile store instance. It manages downloads and storage for requests to tile-related API endpoints. For offline/predictive-caching use cases this instance should be the same that is passed to map resource options. When creating the TileStore make sure to call TileStore.setOption with TileStoreOptions.MAPBOX_ACCESS_TOKEN and your token. By default (if
null is provided here), the TileStore will be created with a filePath and NavigationOptions.accessToken.
is the minimum time in days between local version of tiles and latest on the server to consider using the latest version of routing tiles from the server. As updating tiles frequently consumes considerably energy and bandwidth. Note that this only works if tilesVersion is empty.
Builder for RoutingTilesOptions. You must choose a filePath for this to be built successfully.