TRAFFIC MANAGEMENT SYSTEM

1. DRIVER : This entity contains information about the drone driver’s registered information with transport authority. It includes information such as allowed drones/UAVs, nature of use, driver user ratings, driving experience etc. This data can help us in analyzing the drivers’ behavior and the sort of incidents s/he may be involved in the future.

2. DRONES/UAVs : This entity contains details about the drones/UAV’s registry details with the transport authority. It includes the details of its make, so that the drone type involved in the incidents can be analyzed. We also store details about where and when the drone/UAV was registered so that we can analyze the drones/UAVs by states and districts. We also analyze the behavior related to the drone/UAV age.

3. MAKE : It stores information about the model of drones/UAVs available in the market. This helps us in analyzing incidents from the perspective of the type and design of the drone/UAV involved.

4. LOCATION : This entity describes locations where one or more incidents has been reported.

We include information about the characteristic of geographies around that location like nearby mountains, hills, plateaus etc

RESPONSE TEAM : This entity contains information about the response team set up, its type and volunteer count and its contact information including location. Whenever an incident is reported the nearest response team can be found using the coordinates of the location and the coordinates of the Response Team station.

The diagram contains the following relationships :

1. INCIDENTS(Drone, Driver, Response Team, Location) : This relationship contains information about an incident reported. The details are the Registration number that was involved, the drone involved and the location where the incident occurred, the response team that was assigned, type of incident(i.e. type of loss or injury), the date, time and the condition of air and weather at that time. If an accident involved multiple drones then multiple entries will exist with same incident id, different registration numbers and driver information.

2. Reach(RESPONSE_TEAM, LOCATION) : This relationship records information about which response team can reach what locations and how much time it takes (delay).

3. IS_OF(MAKE, DRONE/UAV) : This relationship records which DRONE/UAV is of what MAKE.