Prompt for the WindLayerApp

Please create a React-JS application for the WindLayerModule. The application  has to offer the following views for the user interface: 
    1. BalloonModelView 
    2. DeploymentDisasterEventView 
    3. DisasterEventView 
    4. WindLayerView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The BalloonModelView must contain the following fields: 
    - name: Description   type: STRING 
    - name: DesignLifetimeDays   type: INT 
    - name: EnvelopeMaterial   type: STRING 
    - name: MaxAltitudeKm   type: STRING 
    - name: MaxSpeedMbitPerSec   type: STRING 
    - name: MinAltitudeKm   type: STRING 
    - name: Name   type: STRING 
An existing BalloonModel entity should be loaded from the relative URL: 
    "/WindLayerService/balloonmodel/{id}"   (HTTP-GET) 
If a new BalloonModel entity has been created, the new entity should be posted to the relative URL: 
    "/WindLayerService/balloonmodel"   (HTTP-POST) 
If an existing BalloonModel entity has been updated, the modified entity should be sent to the relative URL: 
    "/WindLayerService/balloonmodel/{id}"   (HTTP-PUT) 
If an existing BalloonModel entity has to be deleted, the following relative URL should be called: 
    "/WindLayerService/balloonmodel/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BalloonFlight columns: 
    - column: BalloonModel 
    - column: AverageSpeedKmh 
    - column: Project 
    - column: MinAltitudeKm 
    - column: LaunchDateTime 
    - column: MaxAltitudeKm 
    - column: Status 
    - column: TerminationDateTime 
    - column: LaunchSite 
The table should have the title "BalloonFlights" und the data must be loaded from the server with the following relative URL: 
    "/ProjectService/balloonflight/balloonmodel/{id}"

2. The DeploymentDisasterEventView must contain the following fields: 
    - name: DisasterEvent   type: DisasterEvent 
    - name: ServiceDeployment   type: ServiceDeployment 
The data source for the [DisasterEvent] select control should be loaded from the relative URL: 
    "/WindLayerService/disasterevent"   (HTTP-GET) 
The data source for the [ServiceDeployment] select control should be loaded from the relative URL: 
    "/ServiceDeploymentService/servicedeployment"   (HTTP-GET) 
An existing DeploymentDisasterEvent entity should be loaded from the relative URL: 
    "/WindLayerService/deploymentdisasterevent/{id}"   (HTTP-GET) 
If a new DeploymentDisasterEvent entity has been created, the new entity should be posted to the relative URL: 
    "/WindLayerService/deploymentdisasterevent"   (HTTP-POST) 
If an existing DeploymentDisasterEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/WindLayerService/deploymentdisasterevent/{id}"   (HTTP-PUT) 
If an existing DeploymentDisasterEvent entity has to be deleted, the following relative URL should be called: 
    "/WindLayerService/deploymentdisasterevent/{id}"   (HTTP-DELETE)

3. The DisasterEventView must contain the following fields: 
    - name: Country   type: Country 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: EventType   type: STRING 
    - name: Name   type: STRING 
    - name: Region   type: Region 
    - name: StartDate   type: DATE 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
The data source for the [Region] select control should be loaded from the relative URL: 
    "/RegionService/region"   (HTTP-GET) 
An existing DisasterEvent entity should be loaded from the relative URL: 
    "/WindLayerService/disasterevent/{id}"   (HTTP-GET) 
If a new DisasterEvent entity has been created, the new entity should be posted to the relative URL: 
    "/WindLayerService/disasterevent"   (HTTP-POST) 
If an existing DisasterEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/WindLayerService/disasterevent/{id}"   (HTTP-PUT) 
If an existing DisasterEvent entity has to be deleted, the following relative URL should be called: 
    "/WindLayerService/disasterevent/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following DeploymentDisasterEvent columns: 
    - column: DisasterEvent 
    - column: ServiceDeployment 
The table should have the title "DeploymentDisasterEvents" und the data must be loaded from the server with the following relative URL: 
    "/WindLayerService/deploymentdisasterevent/disasterevent/{id}"

4. The WindLayerView must contain the following fields: 
    - name: AltitudeKm   type: STRING 
    - name: DataSource   type: STRING 
    - name: DirectionDegrees   type: STRING 
    - name: SpeedMps   type: STRING 
An existing WindLayer entity should be loaded from the relative URL: 
    "/WindLayerService/windlayer/{id}"   (HTTP-GET) 
If a new WindLayer entity has been created, the new entity should be posted to the relative URL: 
    "/WindLayerService/windlayer"   (HTTP-POST) 
If an existing WindLayer entity has been updated, the modified entity should be sent to the relative URL: 
    "/WindLayerService/windlayer/{id}"   (HTTP-PUT) 
If an existing WindLayer entity has to be deleted, the following relative URL should be called: 
    "/WindLayerService/windlayer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BalloonFlightWindLayer columns: 
    - column: WindLayer 
    - column: AssociationType 
    - column: RelevanceScore 
    - column: BalloonFlight 
The table should have the title "BalloonFlightWindLayers" und the data must be loaded from the server with the following relative URL: 
    "/ProjectService/balloonflightwindlayer/windlayer/{id}"