Releases: Freika/dawarich
0.4.2
[0.4.2] — 2024-05-29
Changed
- Routes are now being split into separate one. If distance between two consecutive points is more than 500 meters, the route is split into two separate routes. This improves visibility of the routes on the map.
- Background jobs concurrency is increased from 5 to 10 to speed up the processing of the points.
Fixed
- Point data, accepted from OwnTracks and Overland, is now being checked for duplicates. If a point with the same timestamp and coordinates already exists in the database, it will not be saved.
What's Changed
- Bump chartkick from 5.0.6 to 5.0.7 by @dependabot in #48
- Bump webmock from 3.23.0 to 3.23.1 by @dependabot in #47
Full Changelog: 0.4.1...0.4.2
0.4.1
[0.4.1] — 2024-05-25
Added
- Heatmap layer on the map to show the density of points
What's Changed
- Bump rubocop-rails from 2.24.1 to 2.25.0 by @dependabot in #39
- Bump rails from 7.1.3.2 to 7.1.3.3 by @dependabot in #40
Full Changelog: 0.4.0...0.4.1
0.4.0
[0.4.0] — 2024-05-25
BREAKING CHANGES:
/api/v1/points
is still working, but will be deprecated in nearest future. Please use/api/v1/owntracks/points
instead.- All existing points recorded directly to the database via Owntracks or Overland will be attached to the user with id 1.
Added
- Each user now have an api key, which is required to make requests to the API. You can find your api key in your profile settings.
- You can re-generate your api key in your profile settings.
- In your user profile settings you can now see the instructions on how to use the API with your api key for both OwnTracks and Overland.
- Added docs on how to use the API with your api key. Refer to
/api-docs
for more information. POST /api/v1/owntracks/points
endpoint.- Points are now being attached to a user directly, so you can only see your own points and no other users of your applications can see your points.
Changed
/api/v1/overland/batches
endpoint now requires an api key to be passed in the url. You can find your api key in your profile settings.- All existing points recorded directly to the database will be attached to the user with id 1.
- All stats and maps are now being calculated and rendered based on the user's points only.
- Default
TIME_ZONE
environment variable is now set to 'UTC' in thedocker-compose.yml
file.
Fixed
- Fixed a bug where marker on the map was rendering timestamp without considering the timezone.
- Api Key authentication by @Freika in #42
Full Changelog: 0.3.2...0.4.0
0.3.2
[0.3.2] — 2024-05-23
BREAKING CHANGES
In order to import Records.json
from Google Takeout, you need to update your docker-compose.yml: b4116cf#diff-e45e45baeda1c1e73482975a664062aa56f20c03dd9d64a827aba57775bed0d3
Added
- Docker volume for importing Google Takeout data to the application
Changed
- Instruction on how to import Google Takeout data to the application
Full Changelog: 0.3.1...0.3.2
0.3.1
[0.3.1] — 2024-05-23
Added
- Instruction on how to import Google Takeout data to the application
[0.3.0] — 2024-05-23
Added
- Add Points page to display all the points as a table with pagination to allow users to delete points
- Sidekiq web interface to monitor background jobs is now available at
/sidekiq
- Now you can choose a date range of points to be exported
[0.2.6] — 2024-05-23
Fixed
- Stop selecting
raw_data
column during requests toimports
andpoints
tables to improve performance.
Changed
- Rename PointsController to MapController along with all the views and routes
Added
- Add Points page to display all the points as a table with pagination to allow users to delete points
Full Changelog: 0.2.5...0.3.1
0.2.5
Fixed
- Stop ignoring
raw_data
column during requests toimports
andpoints
tables. This was preventing points from being created.
Full Changelog: 0.2.4...0.2.5
0.2.4
Added
- In right sidebar you can now see the total amount of geopoints aside of kilometers traveled
Fixed
- Improved overall performance if the application by ignoring
raw_data
column during requests toimports
andpoints
tables.
Full Changelog: 0.2.3...0.2.4
0.2.3
Added
- Now you can import
records.json
file from your Google Takeout archive, not just Semantic History Location JSON files. The import process is the same as for Semantic History Location JSON files, just select therecords.json
file instead and choose "google_records" as a source.
Full Changelog: 0.2.1...0.2.3
0.2.1
What's Changed in 0.2.1
Added
- Cities, visited by user and listed in right sidebar now also have an active link to a date they were visited
Fixed
- Dark/light theme switcher in navbar is now being saved in user settings, so it persists between sessions
- Bump geocoder from 1.8.2 to 1.8.3 by @dependabot in #29
- Bump pundit from 2.3.1 to 2.3.2 by @dependabot in #35
- Bump dotenv-rails from 3.1.0 to 3.1.2 by @dependabot in #36
- Bump tailwindcss-rails from 2.5.0 to 2.6.0 by @dependabot in #31
Full Changelog: 0.2.0...0.2.1
0.2.0
What's Changed in 0.2.0
BREAKING CHANGES:
This release changes how Dawarich handles a city visit threshold. Previously, the MINIMUM_POINTS_IN_CITY
environment variable was used to determine the minimum number of points in a city to consider it as visited. Now, the MIN_MINUTES_SPENT_IN_CITY
environment variable is used to determine the minimum minutes between two points to consider them as visited the same city.
The logic behind this is the following: if you have a lot of points in a city, it doesn't mean you've spent a lot of time there, especially if your OwnTracks app was in "Move" mode. So, it's better to consider the time spent in a city rather than the number of points.
In your docker-compose.yml file, you need to replace the MINIMUM_POINTS_IN_CITY
environment variable with MIN_MINUTES_SPENT_IN_CITY
. The default value is 60
, in minutes.
- Bump super_diff from 0.11.0 to 0.12.1 by @dependabot in #26
- Bump sidekiq from 7.2.2 to 7.2.4 by @dependabot in #25
- Bump shrine from 3.5.0 to 3.6.0 by @dependabot in #24
- Bump tailwindcss-rails from 2.4.0 to 2.5.0 by @dependabot in #23
- Rework calculation of cities visited by @Freika in #22
Full Changelog: 0.1.9...0.2.0