Overview
Summary
Contact
Donate
Imprint
Prompt for the
GeographicalAreaApp
Please create a React-JS application for the GeographicalAreaModule. The application has to offer the following views for the user interface: 1. AisMessageView 2. AisStationView 3. GeographicalAreaView 4. VesselStatusView 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 AisMessageView must contain the following fields: - name: AisStation type: AisStation - name: MessageType type: STRING - name: NmeaSentence type: STRING - name: RawCourseOverGround type: STRING - name: RawDestination type: STRING - name: RawDraught type: STRING - name: RawEta type: DATE - name: RawHeading type: STRING - name: RawLatitude type: STRING - name: RawLongitude type: STRING - name: RawNavigationalStatus type: STRING - name: RawSpeedOverGround type: STRING - name: ReceivedUtc type: DATE - name: SourceType type: STRING - name: Vessel type: Vessel The data source for the [Vessel] select control should be loaded from the relative URL: "/VesselService/vessel" (HTTP-GET) The data source for the [AisStation] select control should be loaded from the relative URL: "/GeographicalAreaService/aisstation" (HTTP-GET) An existing AisMessage entity should be loaded from the relative URL: "/GeographicalAreaService/aismessage/{id}" (HTTP-GET) If a new AisMessage entity has been created, the new entity should be posted to the relative URL: "/GeographicalAreaService/aismessage" (HTTP-POST) If an existing AisMessage entity has been updated, the modified entity should be sent to the relative URL: "/GeographicalAreaService/aismessage/{id}" (HTTP-PUT) If an existing AisMessage entity has to be deleted, the following relative URL should be called: "/GeographicalAreaService/aismessage/{id}" (HTTP-DELETE) 2. The AisStationView must contain the following fields: - name: ActiveFromUtc type: DATE - name: ActiveToUtc type: DATE - name: Country type: Country - name: ElevationMeters type: STRING - name: IsActive type: BOOL - name: Latitude type: STRING - name: Longitude type: STRING - name: Name type: STRING - name: OwnerUser type: LONG - name: StationCode type: STRING - name: StationType type: STRING The data source for the [Country] select control should be loaded from the relative URL: "/UserAccountService/country" (HTTP-GET) An existing AisStation entity should be loaded from the relative URL: "/GeographicalAreaService/aisstation/{id}" (HTTP-GET) If a new AisStation entity has been created, the new entity should be posted to the relative URL: "/GeographicalAreaService/aisstation" (HTTP-POST) If an existing AisStation entity has been updated, the modified entity should be sent to the relative URL: "/GeographicalAreaService/aisstation/{id}" (HTTP-PUT) If an existing AisStation entity has to be deleted, the following relative URL should be called: "/GeographicalAreaService/aisstation/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PositionReport columns: - column: AisStation - column: IsInterpolated - column: CourseOverGround - column: Vessel - column: EtaUtc - column: Longitude - column: Heading - column: PositionTimeUtc - column: GeographicalArea - column: SpeedOverGround - column: NavigationalStatus - column: PositionAccuracyMeters - column: Latitude - column: DestinationText The table should have the title "PositionReports" und the data must be loaded from the server with the following relative URL: "/VesselService/positionreport/aisstation/{id}" Add a HTML table to the view with the following AisMessage columns: - column: AisStation - column: SourceType - column: RawHeading - column: NmeaSentence - column: Vessel - column: RawEta - column: RawNavigationalStatus - column: RawCourseOverGround - column: ReceivedUtc - column: MessageType - column: RawDraught - column: RawLatitude - column: RawDestination - column: RawLongitude - column: RawSpeedOverGround The table should have the title "AisMessages" und the data must be loaded from the server with the following relative URL: "/GeographicalAreaService/aismessage/aisstation/{id}" 3. The GeographicalAreaView must contain the following fields: - name: AreaType type: STRING - name: Code type: STRING - name: CreatedByUser type: LONG - name: Description type: STRING - name: GeometryWkt type: STRING - name: Name type: STRING - name: ParentArea type: LONG An existing GeographicalArea entity should be loaded from the relative URL: "/GeographicalAreaService/geographicalarea/{id}" (HTTP-GET) If a new GeographicalArea entity has been created, the new entity should be posted to the relative URL: "/GeographicalAreaService/geographicalarea" (HTTP-POST) If an existing GeographicalArea entity has been updated, the modified entity should be sent to the relative URL: "/GeographicalAreaService/geographicalarea/{id}" (HTTP-PUT) If an existing GeographicalArea entity has to be deleted, the following relative URL should be called: "/GeographicalAreaService/geographicalarea/{id}" (HTTP-DELETE) Add a HTML table to the view with the following AlertRule columns: - column: AlertType - column: UserAccount - column: ThresholdSpeed - column: Name - column: CreatedUtc - column: GeographicalArea - column: Vessel - column: Description - column: Port - column: IsActive The table should have the title "AlertRules" und the data must be loaded from the server with the following relative URL: "/PortService/alertrule/geographicalarea/{id}" Add a HTML table to the view with the following AlertEvent columns: - column: Vessel - column: GeographicalArea - column: PositionReport - column: AlertRule - column: EventDescription - column: TriggeredUtc - column: Port The table should have the title "AlertEvents" und the data must be loaded from the server with the following relative URL: "/PortService/alertevent/geographicalarea/{id}" Add a HTML table to the view with the following PositionReport columns: - column: AisStation - column: IsInterpolated - column: CourseOverGround - column: Vessel - column: EtaUtc - column: Longitude - column: Heading - column: PositionTimeUtc - column: GeographicalArea - column: SpeedOverGround - column: NavigationalStatus - column: PositionAccuracyMeters - column: Latitude - column: DestinationText The table should have the title "PositionReports" und the data must be loaded from the server with the following relative URL: "/VesselService/positionreport/geographicalarea/{id}" 4. The VesselStatusView must contain the following fields: - name: Description type: STRING - name: Name type: STRING An existing VesselStatus entity should be loaded from the relative URL: "/GeographicalAreaService/vesselstatus/{id}" (HTTP-GET) If a new VesselStatus entity has been created, the new entity should be posted to the relative URL: "/GeographicalAreaService/vesselstatus" (HTTP-POST) If an existing VesselStatus entity has been updated, the modified entity should be sent to the relative URL: "/GeographicalAreaService/vesselstatus/{id}" (HTTP-PUT) If an existing VesselStatus entity has to be deleted, the following relative URL should be called: "/GeographicalAreaService/vesselstatus/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Vessel columns: - column: BuildYear - column: Beam - column: LengthOverall - column: VesselType - column: Draught - column: CallSign - column: ImoNumber - column: GrossTonnage - column: FlagCountry - column: VesselStatus - column: Name - column: Mmsi - column: Deadweight The table should have the title "Vessels" und the data must be loaded from the server with the following relative URL: "/VesselService/vessel/vesselstatus/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint