Finished Geofences

I am pleased to announce that today geo-fence function is finished. Since previous release:

• added notifications for enter/exit event (read more in article)
• added geo-fences information to the mobile UI sidebar
• added device-specific geo-fences (read more in article)
• done couple bug fixes and performance improvements

Wish everybody a great weekend!

Swedish Translation And Minor Ui Bugfix

Github user VentureSWE kindly translated UI to swedish language. Also today's release contains fixes to UI glitches in toolbar when switching between Devices/GeoFences tabs.

Geofences Bugfix

New version with bug-fixes related to new geo-fences functionality was released. Following issues/improvements were done:

• if geo-fence add/edit window is opened then no other action with geo-fences may be performed
• radius/width field is now disabled for 'Polygon' geo-fence since it does not make sense for such zones
• if 'disallow device management by users' is set up in Settings >> Global menu then geo-fence management should still be possible
• by default width of database column that contains geo-fence points was 255, which limits number of points to 7. Now it will be 2048, which allows to hold about 60 points. All existing databases must be updated manually. See this issue for more details.

The functionality is still in beta and any feedback is welcome in issue tracker.

Geofences Beta

Today I am pleased to announce that after about a month of work there is a first usable version of geo-fences function. Please note that for now notifications are not implemented. It is available for testing and any feedback is welcome in issue tracker. What is working now:

• separate tab for 'geo-fences' in left-side panel
• ability to add/edit/delete geo-fences. More details in feature page
• sharing geo-fences between users
• geo-fence calculation for latest device/vehicle positions - popup contains list of geo-fences with colored boxes

Happy geofencing!

Fixed Remote Procedure Call Error In Notification Settings Screen

In yesterday's release it is impossible to open notification settings dialog when user already had them stored in the database. Today's release fixes this issue.

Security Fix, Mobile Ui Script Links Fix And Updated Spanish Translation

In recently released 'read-only' users feature were a major security bug - check was not performed on server side (aspect code wasn't properly invoked). Now it's fixed and covered by unit tests. Upgrade is highly recommended for all users of that function.

Then some ORM mappings were redesigned to reduce workload on the underlying database. Also there were an issue in web UI that produced additional load right after application start, which was fixed too. So for users that have many devices may find both performance improvement and lighter overall server workload.

Next, for ticket #113 all links to scripts were made to either relative or protocol-agnostic. All scripts are now loaded from CloudFlare instead of OpenLayers.

Last change brought to us by github user j5boot - update to spanish translation both in desktop and mobile versions of UI. Thank you!

Updated Portuguese Translation

Github user Antonio Fernandes kindly updated portuguese translation to contain strings for latest added features.

Improved Localization And Read Only Users

Mobile version now supports localization (with same URL parameter ?locale=XX) with language selection.

Desktop version also now has an ability to select language at login screen.

Polish translation was updated (thanks to bigoss and dumar github users).

Then added new feature - ability to mark user read-only.

This release contains changed order of buttons in archive toolbar (was 'Load, Import/Export, Clear', now it's 'Load, Clear and Import/Export') for better user experience (thanks to bigoss github user).

Extended Info In Mobile Ui And Gpx Export Bugfix

Now mobile version prints extended information for latest device position in the sidebar. Also fixed issue in GPX export caused by non-UTF-8 operating system encoding.

Gpx Improvements And Archive Filtering Bug Fix

Now export to GPX contains address, speed, course and power data under extensions node in traccar namespace. Import is aware of them, so now GPX can be used as interchange format between several traccar servers.

Next, all values under extensions will be put into info field of every positions, nested elements like <E1><E2><E3>value</E3></E2></E1> will be combined in a single field with dashes like <E1-E2-E3>value</E1-E2-E3>.

Then, import will update latest position of device if there is no position set up yet, or there is a newer position imported than already existing.

Also import now has several unit tests.

Archive filtering had an issue when 'Disable filter' is checked - 'Hide duplicates' and 'Hide positions with distance less than' were still applied.