new RoutingVehicleProfile(optionsopt)
BeNomad BeMap JavaScript API - RoutingVehicleProfile
Vehicle characteristics that drive access restrictions, toll classes,
energy consumption and emission-zone filtering.
Wire shape mirrors the BeMap server contract (cross-checked against
`bemap-flutter-api/lib/service/routing/model/request/routing_vehicle_profile.dart`):
{ transportMode, maxSpeeds[], routingVehicleFeature, routingEnergyVehicleFeature, routingSpeedPonderations }
Sub-objects are passed through as plain JSON (no validation — unknown keys
flow straight to the server). Their full field shape is documented by the
typedefs at the bottom of this file: `bemap.RoutingMaxSpeed`,
`bemap.RoutingVehicleFeature`, `bemap.RoutingEnergyVehicleFeature`,
`bemap.RoutingSpeedPonderation` (and `bemap.RoutingChargeFeature`, used by
`RoutingRequest.routingChargeFeature`).
Parameters:
| Name |
Type |
Attributes |
Description |
options |
Object
|
<optional>
|
Properties
| Name |
Type |
Attributes |
Description |
transportMode |
String
|
<optional>
|
One of `bemap.TransportMode.*` (CAR, TRUCK, ...).
Server default is CAR (EMERGENCY for TraceRoute). |
maxSpeeds |
Array.<bemap.RoutingMaxSpeed>
|
<optional>
|
Per-class max speeds. |
routingVehicleFeature |
bemap.RoutingVehicleFeature
|
<optional>
|
Physical / legal / toll characteristics. |
routingEnergyVehicleFeature |
bemap.RoutingEnergyVehicleFeature
|
<optional>
|
Energy / EV consumption configuration. |
routingSpeedPonderations |
bemap.RoutingSpeedPonderation
|
<optional>
|
Speed coefficients per road attribute. |
routingEnergyVehicleConnectorTypeIds |
Array.<Number>
|
<optional>
|
EV connector-type IDs the vehicle accepts. |
routingEnergyVehicleRanges |
Array.<Object>
|
<optional>
|
EV range entries (per battery/charge state). |
chargingStationProviderName |
String
|
<optional>
|
Charging-station provider key (EV routing). |
|
- Since:
- Source: