Vehicle Tracking Library

[Florence Rocle]

Im not sure if I missed this somewhere, but I'm looking basic vehicle types like cars and trucks to design residential driveways. As I look through the OTB library, I don't seem to find any of those type of vehicles. While I can find some information on line for making custom vehicles, some of the particular questions don't have answers readily available. Anyone have some pointers for getting data and or using library already created? Anyone have some vehicles up for donation?

In Vehicle Tracking 2018 these a collections of realistic vehicles based on dimensions of actual commercially available cars, utility vehicles and vans. They are located in the "North American Vehicles", "European Vehicles" and "Asian Vehicles" libraries. These are examples of common vehicle and can easily be used as a starting point to create new similar vehicles by using the vehicle wizard.

If you are using an earlier version of Vehicle Tracking these vehicles were a separate subscription benefit, and needed to be installed via a download from your subscription account. Go to the product updates page and search for "vehicles" to find the download.

I do not believe you can install VT 2018 on any 2017 product. I have a subscription and network license version and am entitled to three versions back, I have not moved to the new licensing format yet and not sure if this has changed. WHen stating three versions back I can run 2016, 2017 and 2018 version of the product with the Network Lic Manager. If you are on subscription I would ask your reseller if you are entitled to the 2017 version of VT and load that to your enviroment.

No Vehicle Tracking 2018 only runs on AutoCAD 2018 based versions cad, but the extra realistic vehicles for 2017 can be downloaded free of charge if you have a valid subscription for the 2017 version from the product updates page of you subscription center.

The JavaScript Fleet Tracking Library lets you visualize the locationsof vehicles in their fleets in near real time. The library uses theDeliveries APIto allow visualization of delivery vehicles as well as tasks. Like theJavaScript Shipment Tracking Library,it contains a JavaScript map component that is a drop-in replacementfor a standard google.maps.Map entity and data components to connectwith Fleet Engine.

The Fleet Tracking map view component visualizesthe location of vehicles and tasks. If the route for a vehicle is known,the map view component animates that vehicle as it moves along its predicted path.

The delivery vehicle location provider displays a single delivery vehicle'slocation information. It has information on the vehicle location as well as thetasks that were completed by the delivery vehicle.

This section describes the visibility rules for tracked location objectson the map for the Fleet Engine predefined location provider. Custom or derivedlocation providers may change the visibility rules.

The location of task outcomes are displayed with task outcome markers.Tasks with a SUCCEEDED outcome are displayed with successful task markers,while all other tasks are displayed with unsuccessful task markers.

To create the JWT payload, add an additional claim in the authorization sectionwith the keys taskid and deliveryvehicleid and set the valueof each key to *. The token should be created using the Fleet EngineService Super User Cloud IAM role. Note that this grants broad accessto create, read, and modify Fleet Engine entities, and should only be sharedwith trusted users.

You can create an authentication token fetcher to retrieve a token mintedwith the appropriate claims on your servers using a serviceaccount certificate for your project. It is important to only mint tokenson your servers and never share your certificates on any clients. Otherwise,you will compromise the security of your system.

The following example shows how to load the JavaScript Journey Sharinglibrary from a specified URL. The callback parameter executes the initMapfunction after the API loads. The defer attribute lets the browsercontinue rendering the rest of your page while the API loads.

This section shows how to use the JavaScript Fleet Tracking Libraryto follow a delivery vehicle. Make sure toload the library from the callback function specified in the script tagbefore running your code.

After loading the JavaScript Journey Sharing library, initializethe map view and add it to the HTML page. Your page should containa element that holds the map view. The elementis named map_canvas in the example below.

You can retrieve meta information about a task from the deliveryVehicle objectusing the location provider. The meta information includes the ETA andremaining distance before the vehicle's next pickup or dropoff. Changesto the meta information trigger an update event. The following exampleshows how to listen to these change events.

This section shows how to use the JavaScript Journey Sharing libraryto view a delivery fleet. Make sure toload the library from the callback function specified in the script tagbefore running your code.

The JavaScript Fleet Tracking Library predefines a location provider thatfetches multiple vehicles from theFleetEngine Deliveries API.Use yourproject ID as well as as a reference to your token fetcher to instantiate it.

You can retrieve meta information about the fleet from the deliveryVehiclesobject using the location provider. The meta information includes vehicleproperties such as navigation state, remaining distance and custom attributes;seereference documentationfor more details. Change to the meta information trigger an update event. Thefollowing example shows how to listen to these change events.

While viewing a fleet, you can show the route and upcoming tasks for a specificdelivery vehicle. To do this, instantiate both a Delivery Fleet LocationProvider and a Delivery Vehicle Location Provider, and add them both to themap view:

The delivery fleet location provider starts to show delivery vehicles onthe map. Use marker customization to enable the delivery vehicle locationprovider to track a delivery vehicle when its fleet marker has been clicked:

Cloud-based maps stylinglets you create and edit map styles for any of your apps that use Google Mapsfrom the Google Cloud console without requiring any changes to your code.The map styles are saved as map IDs in your Cloud project. Toapply a style to your JavaScript Fleet Tracking map, specify amapIdwhen you create the JourneySharingMapView. The mapId field cannot be changedor added after the JourneySharingMapView has been instantiated. The followingexample shows how to enable a previously created map style with amap ID.

With the JavaScript Fleet Tracking Library, you can customize the look and feelof markers added to the map. You do this by specifying marker customizations,which the Fleet Tracking Library then applies before adding markers to the mapand with every marker update.

The simplest customization is to specify a MarkerOptionsobject that will be applied to all markers of the same type. The changesspecified in the object are applied after each marker has been created,overwriting any default options.

A more advanced option is to specify a customization function. Customizationfunctions allow for styling of the markers based on data, as well as addinginteractivity to markers, such as click handling. Specifically, Fleet Trackingpasses data to the customization function about the type of object the markerrepresents: vehicle, stop, or task. This then allows marker styling to changebased on the current state of the marker element itself; for example, the numberof remaining stops or type of task. You can even join against data from sourcesoutside Fleet Engine and style the marker based on that information.

However, for performance reasons, we recommend filtering with the nativefiltering in the location provider, such asFleetEngineDeliveryFleetLocationProvider.deliveryVehicleFilter.That said, when you need additional filtering functionality, you can applyfiltering using the customization function.

The following example shows how to configure a vehicle marker's styling with a MarkerOptions object. Follow this pattern to customize the styling of anymarker using any of the marker customization parameters listed above.

With the JavaScript Fleet Tracking Library, you can also customize the look andfeel of the followed vehicle's route on the map. The library creates agoogle.maps.Polylineobject for each pair of coordinates in the vehicle's active or remainingpath.You can style the Polyline objects by specifying polyline customizations. Thelibrary then applies these customizations in two situations: before adding theobjects to the map, and when the data used for the objects have changed.

Likewise, you can specify a customization function. Customization functionsallow for individual styling of the objects based on data sent by Fleet Engine.The function can change the styling of each object based on the current vehiclestate; for example, coloring the Polyline object a deeper shade, or makingit thicker when the vehicle is moving slower. You can even join against fromsources outside Fleet Engine and style the Polyline object based on thatinformation.

You can specify the customizations using parameters provided inFleetEngineDeliveryVehicleLocationProviderOptions.You can set customizations for different path states in the vehicle'sjourney--already traveled, actively traveling, or not yet traveled. Theparameters are as follows:

The following example shows how to configure the styling for a Polyline objectwithPolylineOptions.Follow this pattern to customize the styling of any Polyline object using anyof the polyline customizations listed earlier.

The following example shows how to configure the styling for an active Polylineobject using a customization function. Follow this pattern to customize thestyling of any Polyline object using any of the polyline customizationparameters listed earlier.

You can stop the map from automatically fitting the viewport to the vehicleand anticipated route by disabling automatic fitting. The following exampleshows how to disable automatic fitting when you configure the journey sharingmap view.

3a8082e126