Status Message Identifications

Dear Anton,

My thought/opinion would be, either it would be better to have a tag to each row that is a status/non gps message to identify them as non gps messages (Status messages)

or to store these data in a different table.

The reason for which is, one the overall db space increases drastically at a higher rate.
Another reason is, easier for future analytics purpose when only data pretaining to trips would be required (such as start/stop and trip relevant gps data)

Whats your thought on this?

You can detect those by difference in "device time" and "fix time". I don't see how marking those messages or putting them in a separate table would reduce amount of data in the database.

There are multiple scenario's Which I have come across, that would not be in favor of identifying status messages based on difference between device time and fix time.

1. One being both time being the same.
2. Second being, in case of a mobile network lag/delay (The data sent, can be of a previous timestamp) there are times when the mobile data network is completely out and data will be pushed by devices in bulk when network resumes. in such cases the (Server time will be current time stamp and device time could be current device time, and fix time could be the actual fix time)

I agree putting it in a seperate table, wont reduce database size, but it will help admin better manage data such as archive them or delete them.

In my opinion the users who would require status messages, or its values, would not necessarily or might never have the need to use these old data in the future. cuz most things are live values pretaining to device and connectivity so far that I see. (Again its my personal opinion, I am sure there might be others who might want this for some other purposes as well.)

If you just need device status (online/offline), then you can filter all those messages using "filter.duplicate".

Yes I agree... :)