Redbex MappRover usually works in offline mode, i.e. it does not require to have direct network access to the Redbex Application Server at most times. This allows you to use MappRover in places where no network connection is available.

Data exchange between MappRover and the Redbex Application Server is done via data synchronization. The synchronization process detects data changes within MappRover as well as data changes on the Application Server and uploads or downloads this changed data. As with every data synchronization process there may be conflicts during synchronization (e.g. when the same data was changed in MappRover and on the Application Server since the last synchronization). In this cases the synchronization will ask the user for his input to resolve these conflicts.

MappRover operates on base data that you cannot create within the application but which is only loaded from the Application Server during synchronization, therefore it is necessary to synchronize MappRover with the Application Server at least once before starting to work with MappRover

As a general rule we recommend to synchronize data often (depending on how much data is changed on the Application Server and on the MappRover). This will reduce the number of conflicts and will decrease the time for one synchronization run.

The list of available workspaces and the construction areas within those workspaces (including all mapping events, mapping objects etc.) are implemented as two separate synchronization processes. This enables you to selectively only synchronize data in selected workspaces and therefore save local storage space and minimize synchronization time.