apps8os / trafficsense Goto Github PK

At this moment we draw the route in a rect line instead of being through the road.
Problem: We don't know, what are the paths taken from the hsl buses.

Partial_solution: It is possible to draw the path from the road through the Google maps Api, (creates and manipulates through JSONObject).

partial_solution_sources:

http://wptrafficanalyzer.in/blog/drawing-driving-route-directions-between-two-locations-using-google-directions-in-google-map-android-api-v2/

http://stackoverflow.com/questions/14710744/how-to-draw-road-directions-between-two-geocodes-in-android-google-map-v2

Although we had the worker thread in Container attach itself as an Activity, there might still be some gaps if the service takes longer to start.
One such example is LocationOnlyService.

We do not have the walking coordinates it is important the starting and the ending point of walking.
Because the user would like to have the trace route from the map.
At this moment we are getting the coordinates of HSL from the stopCode and the walking does not have stopCode.

Currently our service is able to track a journey if its start time is later than current time (if useWallClock is enabled).
This is especially true for TimeOnlyService which schedules alarm events based on time.
For LocationOnlyService time does not matter but journey start time check is done by TrafficsenseContainer so it is also affected.

The first waypoint is also the last, so no NextWaypoint.
And there is no second last waypoint, so no GetOff.

Time and Date information are stored as Strings in Route, Segment, and Waypoint classes (in TrafficsenseContainer). They should be stored as appropriate Java classes.

At this moment JSON parser just accept the hsl text file on the email with the basic route. If for some reason the user opt for the Advance search on the hsl website (http://www.reittiopas.fi/en/) and add some features like Via linked with the Time minutes (spent at via point) the text format send by email is in a different format and therefore the JSON parser is not able to parse it correctly hence crashes the TrafficSense application.