Feedback on Routes (Gustavo's idea)

[ZihRah]

A button will be added to report if there where any problems with the route. It will be placed at to parts: next to the itinerary and at the top of the app. After clicking on the button you'll be directed to a new window with options (Not available, changed & others). Below of the options is a text field: . Then you chose one of the options and fill in the text. At the end you send the text.

[GustavoTCh]

To create buttons in next pages.

[GustavoTCh]

Data structure for reporting routes:

{
    "idDevice": "46948961561564",
    "transportCode": "sdsad",
    "typeRoute": "FULL_ROUTE-PARTIAL_ROUTE",
    "state": "NOT_AVAILABLE-CHANGED-OTHERS",
    "userLocation?": {
        "lat": 156156,
        "lng": -1561
    },
    "description?": ".....",
    "phone?": "+67 838444",
    "segment": {
        "start": {
            "lat": 156156,
            "lng": -1561
        },
        "end": {
            "lat": 156156,
            "lng": -1561
        }
    }
}

[GustavoTCh]

@ZihRah, @EOVN and I have a new idea for the FullRoute report.

To generate more specific data, it is possible to allow users to draw boxes on the map to further report errors on an entire route.

[GustavoTCh]

Data structure for reporting routes(V2):

enum TYPEROUTE {
    FULL_ROUTE = 'FULL_ROUTE',
    PARTIAL_ROUTE = 'PARTIAL_ROUTE'
}

enum STATE {
    NOT_AVAILABLE = 'NOT_AVAILABLE',
    CHANGED = 'CHANGED',
    OTHERS = 'OTHERS'
}

type POSITION = {
    lat: number
    lng: number
}

type SEGMENT = {
    start: POSITION
    end: POSITION
}

type FeedBack = {
    _id?: string
    idDevice: string
    idEdition: string
    transportCode: string
    typeRoute: TYPEROUTE
    state: STATE
    userLocation?: POSITION
    description?: string
    phone?: string
    segment?: SEGMENT
    segments?: SEGMENT[]
}

type FeedBackId = {
    id?: string
}

export { FeedBack, FeedBackId };

[ZihRah]

Gustavo thinks about including the server Valhalla to match tracked or marked points to the map in an easy way.