Bing-Maps-Fleet-Tracker | Bing Maps Fleet Tracker is a tracking solution | Map library

There are two parts to the set-up process:.
Set up the back-end services and administration portal;
Set up the mobile client.
The Bing Maps Fleet Tracker solution consist of 3 major components:. Each of these components can be built and run separately, and each can be replaced with implementations of your own. The backend services are responsible for the collection and processing of location information, the provisioning of tracking devices and assets, dispatching, and report generation. They are made up of an ASP.NET Core 2 service, and two Azure Functions. For more information on building an running the backend services see Backend\README.md. The administration portal is an angular application that exposes the functionalities of the backend to the deployment administrators. It can be used to view reports, track and provision assets, and compare dispatching routes. For more information on building an running the administration portal see Frontend\README.md. The mobile client is an ionic mobile application responsible for collection of asset location information and the forwarding of this information to the backend. It is meant to provide an out of the box background tracking solution but it is not the only way to integrate with Bing Maps Fleet Tracker; any GPS device with an internet connection can be used to provide the background tracking (see Using the Rest APIs). For more information on building and running the mobile client see MobileClient\README.md.
The Backend Services
The Administration Portal
The Mobile Client