Three things
Posted: 04 December 2009 05:19 AM   [ Ignore ]
Member
RankRankRank
Total Posts:  66
Joined  2009-10-24

1. It would be nice to have the ability to connect with a line the location readings for a vehicle on a map.  While they may not be totally accurate since its not following the path on a road, it will at least be more telling than a bunch of location dots and which you have guess the routing.

2. Since we can already know the direction of the unit by obtaining readings based on direction change, it would be wonderful to change the simple dots on the screen to arrows showing the direction of the unit

3. On the overview screen, it would be beneficial to have the option to change the “last report” column to “length of status”.  The reason is, if my vehicle has been stopped for say 12 hours, I would rather know that information than knowing it last checked in 12 minutes ago.  I would rather know how long the unit has been moving/stopped total.

Profile
 
 
Posted: 04 December 2009 05:46 AM   [ Ignore ]   [ # 1 ]
Administrator
RankRankRankRank
Total Posts:  249
Joined  2008-12-18

1. We actually tested something like this in the early days but pulled it out. It would be relatively straight-forward to use the GPolyline API to do something like this (http://code.google.com/apis/maps/documentation/reference.html#GPolyline). We really started to run into problems as we had applications that began to report less frequently. In some cases we have devices report every 5 minutes or more and the line becomes a distraction to the user.

2. That’s a good suggestion and there’s already a function called createArrow in main.js that you could utilize. We do store the direction the readings model so it’s just a matter of exposing it to your view. You’ll notice that the arrow icons were originally designed to overlay on top of the existing numbered markers. I’ll mention this to the team and see if we can make it part of core.

3. You could easily get the length of the stop using the latest_stop_event method on the device model. It would look something like device.latest_stop_event.duration. For length of motion this will more complicated. You’ll need to find the oldest reading that is not a stop or maybe use the latest_stop_event’s created_at time plus the duration and calculate length of motion from there. But you’ll also need to factor in idle’s too. It gets hairy. I’m not sure if this would be considered for core, but I can ask.

Profile
 
 
Posted: 04 December 2009 05:49 AM   [ Ignore ]   [ # 2 ]
Member
RankRankRank
Total Posts:  66
Joined  2009-10-24

Thank you for the response and especially so quickly!!

Profile