Currently a save to disk is only done when an observation is created/edited, or tracklogging ends. It could be that there is a long period between observation and it might be a good idea to flush to disk. This will minimize the amount of data loss should something bad happen.
Currently a save to disk is only done when an observation is created/edited, or tracklogging ends. It could be that there is a long period between observation and it might be a good idea to flush to disk. This will minimize the amount of data loss should something bad happen.