In this release we have major changes in Reverse Geocoding Management (mainly internally in backend), added new Trip Types (bicycle, train, flight) to timeline and fixed some defects.

New Features

• Implemented better optimized native images for modern CPU and older CPUs. Details are here: https://tess1o.github.io/geopulse/docs/getting-started/deployment/docker-compose#cpu-compatibility-issues
  For older CPUs use images with prefix -native-compat

  geopulse-backend:
    # Comment out the default optimized image:
    # image: tess1o/geopulse-backend:${GEOPULSE_VERSION}-native
    # Use the compatible image instead:
    image: tess1o/geopulse-backend:${GEOPULSE_VERSION}-native-compat

For modern CPU no additional changes are needed.

• Implemented additional trip types: bicycle, train and flight to already existing walk and car. Bicycle, train and flight are optional and disabled by default. User can enable them in UI (Menu -> Timeline Preferences -> Trip Classification).

See how it looks in UI

Documentation: https://tess1o.github.io/geopulse/docs/user-guide/timeline/travel_classification
NOTE: I tried my best to implement proper classification but I don't have real GPS examples and it might not work properly for you. If you don't use bicycle or trains I suggest to keep these options disabled to do not mess up with your timeline. Feel free to report your issues, I will try to check them

• Added flags to enable/disable custom prometheus metrics and fetch interval for them. Documentation: https://tess1o.github.io/geopulse/docs/system-administration/monitoring/prometheus
  Work on Grafana dashboard is in progress.

Bug fixes

• #199 - removed cert-manager.io/cluster-issuer from helm chart

Improvements

I re-implemented Reverse Geocoding data management - see #184. Before this release Reverse Geocoding data was global for all users. However, since users can modify (rename) data received from Reverse Geocoding providers it impacts all other users. Thus, the approach was changes:

1. Already existing data remains global for everyone (even if was already modified)
2. If you rename Reverse Geocoding entity we create a copy with new name and assign it to you only. The original one remains unchanged (can be still used by other users as original value). You now can see only modified version.
3. All following changes (like reconciliation) or next updates to this entity affect only your copy.
4. In Reverse Geocoding Management page you can see only data that is used in your timeline (before this release you could see all data in the system which is confusing and wrong).

It was a big architecture change in backend and I hope my unit tests covered all possible scenarios.