Hololens Aircraft Incident Replay -- 2

I need to develop a Microsoft Hololens working prototype for an aviation related project, using the latest versions of tools and SDKs (Unity, VS, MRTU). The deliverable will be a Unity 3D project, which I can build, generate the UWP app and deploy it to Hololens. 1. Scene 1: main inventory - a grid displaying current occurrences from the database (see attachment [login to view URL]). Each occurrence will have a "Replay" button. Clicking Replay will open that occurrence in scene 2. The database connection will be mocked up. For this project, we will use demo data for 5 occurrences, stored in json format. 2. Scene 2 - replay window for an occurrence. The replay window will play the recorded occurrence. There will be a menu for "playing" the event, with buttons for play, stop, forward, rewind. The tool will display the aircraft models (standard free available model for all aircraft) following their trajectories. The portions of trajectories where the conflict is happening are emphasized with a thicker line. For each aircraft involved in an occurrence, the trajectory is built up from points received at each 5 seconds. The transition of the aircraft however should be a smooth one, not jumping from current position to the next one. Each occurrence has a Trajectories collection. Each trajectory belongs to an aircraft and has a collection of Positions. Each Position has the data received from Radar in a certain batch, so each position has a batch number. Furthermore, we have calculated the timeline of the event - Timeline property on the occurrence. It has a collection of Frames, each Frame has a batch number, time to next frame and a time. That's how we correlate each Position with the timeline and we know when to display each aircraft / at what time. You will understand more when you inspect the json of the occurrence. The replay means "playing" the event as it was recorder by the radars. The aircraft must follow their trajectories with a smooth transition from position to position, exactly the same as in the HoloFlight app: [login to view URL] We'll not use a database for now. We'll read all data from json file. I have the C# code (DTO classes) for accessing these files and I will provide them to you. Each aircraft will have a label to display related info: call sign, flight level, speed, heading, etc. The label should follow the aircraft. The info for the label is contained in each Position, see above. All trajectory coordinates will be modeled / translated to Unity coordinates. We need to be very careful to how we transform lat-long coordinates to Unity coordinates, so we can preserve the scale as much as possible, but also don't look 3 stories up to see your aircraft when it's at 30.000 feet. So we need to balance it very fine. A start point can be this one: [login to view URL] There will be several layers available to be displayed: -3D terrain map -airspace sectors configuration. Each sector has a WktString property, maybe we can use this one to draw it. If not, we can use the collection of Points on each Shape. To make it 3D, we'll use MinFlightLevel and MaxFlightLevel to draw bottom and upper limits. So each sector will be a 3D polygone. -vicinity traffic: aircraft which were around, but not involved in the occurrence. Their trajectories are contained in the Trajectories collection, as well. The [login to view URL] property gives us the info we need. 0 = Main 1 = Involved 2 = Neighbouring (vicinity traffic) - not involved. -weather info: I don't have any data for this one. We'll just display some static 3D clouds, just to have the look and feel. I will provide test data for 5 occurrences and airspace configuration, in json, together with C# code to access this data.