Prompt for the LocationApp

Please create a React-JS application for the LocationModule. The application  has to offer the following views for the user interface: 
    1. AccidentView 
    2. FlightRouteView 
    3. HangarView 
    4. JobPostingView 
    5. LocationView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The AccidentView must contain the following fields: 
    - name: AccidentType   type: STRING 
    - name: DamageLevel   type: STRING 
    - name: DateTime   type: DATE 
    - name: Description   type: STRING 
    - name: Fatalities   type: INT 
    - name: Injuries   type: INT 
    - name: Location   type: Location 
    - name: Mission   type: Mission 
    - name: Zeppelin   type: Zeppelin 
The data source for the [Zeppelin] select control should be loaded from the relative URL: 
    "/ZeppelinService/zeppelin"   (HTTP-GET) 
The data source for the [Mission] select control should be loaded from the relative URL: 
    "/MissionService/mission"   (HTTP-GET) 
The data source for the [Location] select control should be loaded from the relative URL: 
    "/LocationService/location"   (HTTP-GET) 
An existing Accident entity should be loaded from the relative URL: 
    "/LocationService/accident/{id}"   (HTTP-GET) 
If a new Accident entity has been created, the new entity should be posted to the relative URL: 
    "/LocationService/accident"   (HTTP-POST) 
If an existing Accident entity has been updated, the modified entity should be sent to the relative URL: 
    "/LocationService/accident/{id}"   (HTTP-PUT) 
If an existing Accident entity has to be deleted, the following relative URL should be called: 
    "/LocationService/accident/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Memorial columns: 
    - column: UnveiledOn 
    - column: RelatedAccident 
    - column: Location 
    - column: Name 
    - column: Description 
The table should have the title "Memorials" und the data must be loaded from the server with the following relative URL: 
    "/EngineService/memorial/relatedaccident/{id}"

2. The FlightRouteView must contain the following fields: 
    - name: ArrivalLocation   type: Location 
    - name: DefaultHangar   type: Hangar 
    - name: DepartureLocation   type: Location 
    - name: Description   type: STRING 
    - name: DistanceKm   type: STRING 
    - name: DurationMinutes   type: INT 
    - name: Name   type: STRING 
    - name: Region   type: STRING 
The data source for the [DefaultHangar] select control should be loaded from the relative URL: 
    "/LocationService/hangar"   (HTTP-GET) 
The data source for the [DepartureLocation] select control should be loaded from the relative URL: 
    "/LocationService/location"   (HTTP-GET) 
The data source for the [ArrivalLocation] select control should be loaded from the relative URL: 
    "/LocationService/location"   (HTTP-GET) 
An existing FlightRoute entity should be loaded from the relative URL: 
    "/LocationService/flightroute/{id}"   (HTTP-GET) 
If a new FlightRoute entity has been created, the new entity should be posted to the relative URL: 
    "/LocationService/flightroute"   (HTTP-POST) 
If an existing FlightRoute entity has been updated, the modified entity should be sent to the relative URL: 
    "/LocationService/flightroute/{id}"   (HTTP-PUT) 
If an existing FlightRoute entity has to be deleted, the following relative URL should be called: 
    "/LocationService/flightroute/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Flight columns: 
    - column: FlightRoute 
    - column: FlightNumber 
    - column: ScheduledDeparture 
    - column: ScheduledArrival 
    - column: Zeppelin 
    - column: Status 
The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/flight/flightroute/{id}"

3. The HangarView must contain the following fields: 
    - name: BuiltYear   type: INT 
    - name: Capacity   type: INT 
    - name: HeightMeters   type: STRING 
    - name: LengthMeters   type: STRING 
    - name: Location   type: Location 
    - name: Name   type: STRING 
    - name: WidthMeters   type: STRING 
The data source for the [Location] select control should be loaded from the relative URL: 
    "/LocationService/location"   (HTTP-GET) 
An existing Hangar entity should be loaded from the relative URL: 
    "/LocationService/hangar/{id}"   (HTTP-GET) 
If a new Hangar entity has been created, the new entity should be posted to the relative URL: 
    "/LocationService/hangar"   (HTTP-POST) 
If an existing Hangar entity has been updated, the modified entity should be sent to the relative URL: 
    "/LocationService/hangar/{id}"   (HTTP-PUT) 
If an existing Hangar entity has to be deleted, the following relative URL should be called: 
    "/LocationService/hangar/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Restaurant columns: 
    - column: Description 
    - column: RelatedHangar 
    - column: Name 
    - column: Location 
    - column: Website 
The table should have the title "Restaurants" und the data must be loaded from the server with the following relative URL: 
    "/RestaurantService/restaurant/relatedhangar/{id}" 
Add a HTML table to the view with the following FlightRoute columns: 
    - column: DurationMinutes 
    - column: Description 
    - column: DepartureLocation 
    - column: Name 
    - column: DefaultHangar 
    - column: ArrivalLocation 
    - column: Region 
    - column: DistanceKm 
The table should have the title "FlightRoutes" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/flightroute/defaulthangar/{id}"

4. The JobPostingView must contain the following fields: 
    - name: Department   type: STRING 
    - name: Description   type: STRING 
    - name: EmploymentType   type: STRING 
    - name: ExpiresOn   type: DATE 
    - name: Location   type: Location 
    - name: Organization   type: Organization 
    - name: PostedOn   type: DATE 
    - name: Title   type: STRING 
The data source for the [Organization] select control should be loaded from the relative URL: 
    "/OrganizationService/organization"   (HTTP-GET) 
The data source for the [Location] select control should be loaded from the relative URL: 
    "/LocationService/location"   (HTTP-GET) 
An existing JobPosting entity should be loaded from the relative URL: 
    "/LocationService/jobposting/{id}"   (HTTP-GET) 
If a new JobPosting entity has been created, the new entity should be posted to the relative URL: 
    "/LocationService/jobposting"   (HTTP-POST) 
If an existing JobPosting entity has been updated, the modified entity should be sent to the relative URL: 
    "/LocationService/jobposting/{id}"   (HTTP-PUT) 
If an existing JobPosting entity has to be deleted, the following relative URL should be called: 
    "/LocationService/jobposting/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following JobApplication columns: 
    - column: SubmittedOn 
    - column: ApplicantName 
    - column: Email 
    - column: JobPosting 
    - column: Notes 
    - column: Status 
    - column: Phone 
The table should have the title "JobApplications" und the data must be loaded from the server with the following relative URL: 
    "/PersonService/jobapplication/jobposting/{id}"

5. The LocationView must contain the following fields: 
    - name: Country   type: Country 
    - name: Latitude   type: STRING 
    - name: LocationType   type: STRING 
    - name: Longitude   type: STRING 
    - name: Name   type: STRING 
    - name: Region   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing Location entity should be loaded from the relative URL: 
    "/LocationService/location/{id}"   (HTTP-GET) 
If a new Location entity has been created, the new entity should be posted to the relative URL: 
    "/LocationService/location"   (HTTP-POST) 
If an existing Location entity has been updated, the modified entity should be sent to the relative URL: 
    "/LocationService/location/{id}"   (HTTP-PUT) 
If an existing Location entity has to be deleted, the following relative URL should be called: 
    "/LocationService/location/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Accident columns: 
    - column: Zeppelin 
    - column: Description 
    - column: Fatalities 
    - column: DateTime 
    - column: DamageLevel 
    - column: Location 
    - column: Injuries 
    - column: Mission 
    - column: AccidentType 
The table should have the title "Accidents" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/accident/location/{id}" 
Add a HTML table to the view with the following Restaurant columns: 
    - column: Description 
    - column: RelatedHangar 
    - column: Name 
    - column: Location 
    - column: Website 
The table should have the title "Restaurants" und the data must be loaded from the server with the following relative URL: 
    "/RestaurantService/restaurant/location/{id}" 
Add a HTML table to the view with the following Mission columns: 
    - column: War 
    - column: Description 
    - column: EndDateTime 
    - column: StartDateTime 
    - column: MissionType 
    - column: DestinationLocation 
    - column: OriginLocation 
    - column: Zeppelin 
    - column: Outcome 
    - column: MilitaryBranch 
The table should have the title "Missions" und the data must be loaded from the server with the following relative URL: 
    "/MissionService/mission/destinationlocation/{id}" 
Add a HTML table to the view with the following Mission columns: 
    - column: War 
    - column: Description 
    - column: EndDateTime 
    - column: StartDateTime 
    - column: MissionType 
    - column: DestinationLocation 
    - column: OriginLocation 
    - column: Zeppelin 
    - column: Outcome 
    - column: MilitaryBranch 
The table should have the title "Missions" und the data must be loaded from the server with the following relative URL: 
    "/MissionService/mission/originlocation/{id}" 
Add a HTML table to the view with the following Zeppelin columns: 
    - column: Code 
    - column: ConstructionNumber 
    - column: FirstFlightDate 
    - column: LastFlightDate 
    - column: ZeppelinClass 
    - column: HomeBaseLocation 
    - column: Status 
    - column: Name 
    - column: Operator 
    - column: Notes 
The table should have the title "Zeppelins" und the data must be loaded from the server with the following relative URL: 
    "/ZeppelinService/zeppelin/homebaselocation/{id}" 
Add a HTML table to the view with the following Hangar columns: 
    - column: Capacity 
    - column: Location 
    - column: HeightMeters 
    - column: Name 
    - column: BuiltYear 
    - column: WidthMeters 
    - column: LengthMeters 
The table should have the title "Hangars" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/hangar/location/{id}" 
Add a HTML table to the view with the following Organization columns: 
    - column: OrganizationType 
    - column: HeadquartersLocation 
    - column: Website 
    - column: FoundedOn 
    - column: Name 
The table should have the title "Organizations" und the data must be loaded from the server with the following relative URL: 
    "/OrganizationService/organization/headquarterslocation/{id}" 
Add a HTML table to the view with the following FlightRoute columns: 
    - column: DurationMinutes 
    - column: Description 
    - column: DepartureLocation 
    - column: Name 
    - column: DefaultHangar 
    - column: ArrivalLocation 
    - column: Region 
    - column: DistanceKm 
The table should have the title "FlightRoutes" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/flightroute/arrivallocation/{id}" 
Add a HTML table to the view with the following FlightRoute columns: 
    - column: DurationMinutes 
    - column: Description 
    - column: DepartureLocation 
    - column: Name 
    - column: DefaultHangar 
    - column: ArrivalLocation 
    - column: Region 
    - column: DistanceKm 
The table should have the title "FlightRoutes" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/flightroute/departurelocation/{id}" 
Add a HTML table to the view with the following Event columns: 
    - column: DateTime 
    - column: Name 
    - column: RelatedZeppelin 
    - column: RelatedOrganization 
    - column: Location 
    - column: EventType 
    - column: Description 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/OrganizationService/event/location/{id}" 
Add a HTML table to the view with the following Memorial columns: 
    - column: UnveiledOn 
    - column: RelatedAccident 
    - column: Location 
    - column: Name 
    - column: Description 
The table should have the title "Memorials" und the data must be loaded from the server with the following relative URL: 
    "/EngineService/memorial/location/{id}" 
Add a HTML table to the view with the following JobPosting columns: 
    - column: ExpiresOn 
    - column: Department 
    - column: Title 
    - column: Description 
    - column: Organization 
    - column: PostedOn 
    - column: Location 
    - column: EmploymentType 
The table should have the title "JobPostings" und the data must be loaded from the server with the following relative URL: 
    "/LocationService/jobposting/location/{id}"