Skip to content

Releases: Freika/dawarich

0.24.0-rc

08 Feb 11:12
1491286
Compare
Choose a tag to compare
0.24.0-rc Pre-release
Pre-release

Points speed units

Dawarich expects speed to be sent in meters per second. It's already known that OwnTracks and GPSLogger (in some configurations) are sending speed in kilometers per hour.

In GPSLogger it's easily fixable: if you previously had "vel": "%SPD_KMH", change it to "vel": "%SPD", like it's described in the docs.

In OwnTracks it's a bit more complicated. You can't change the speed unit in the settings, so Dawarich will expect speed in kilometers per hour and will convert it to meters per second. Nothing is needed to be done from your side.

Now, we need to fix existing points with speed in kilometers per hour. The following guide assumes that you have been tracking your location exclusively with speed in kilometers per hour. If you have been using both speed units (say, were tracking with OwnTracks in kilometers per hour and with GPSLogger in meters per second), you need to decide what to do with points that have speed in kilometers per hour, as there is no easy way to distinguish them from points with speed in meters per second.

To convert speed in kilometers per hour to meters per second in your points, follow these steps:

  1. Enter Dawarich console
  2. Run points = Point.where(import_id: nil).where.not(velocity: [nil, "0"]).where("velocity NOT LIKE '%.%'"). This will return all tracked (not imported) points.
  3. Run
points.update_all("velocity = CAST(ROUND(CAST((CAST(velocity AS FLOAT) * 1000 / 3600) AS NUMERIC), 1) AS TEXT)")

This will convert speed in kilometers per hour to meters per second and round it to 1 decimal place.

If you have been using both speed units, but you know the dates where you were tracking with speed in kilometers per hour, on the second step of the instruction above, you can add time range to the query to convert speed in kilometers per hour to meters per second only for a specific period of time. Resulting query will look like this:

start_at = DateTime.new(2025, 1, 1, 0, 0, 0).in_time_zone(Time.current.time_zone).to_i
end_at = DateTime.new(2025, 1, 31, 23, 59, 59).in_time_zone(Time.current.time_zone).to_i
points = Point.where(import_id: nil).where.not(velocity: [nil, "0"]).where("timestamp BETWEEN ? AND ?", start_at, end_at).where("velocity NOT LIKE '%.%'")

This will select points tracked between January 1st and January 31st 2025. Then just use step 3 to convert speed in kilometers per hour to meters per second.

Changed

  • Speed for points, that are sent to Dawarich via POST /api/v1/owntracks/points endpoint, will now be converted to meters per second, if topic param is sent. The official GPSLogger instructions are assuming user won't be sending topic param, so this shouldn't affect you if you're using GPSLogger.

Fixed

  • After deleting one point from the map, other points can now be deleted as well. #723 #678
  • Fixed a bug where export file was not being deleted from the server after it was deleted. #808
  • After an area was drawn on the map, a popup is now being shown to allow user to provide a name and save the area. #740
  • Garmin GPX files with empty tracks are now being imported correctly. #827

Added

  • X-Dawarich-Version header to the GET /api/v1/health endpoint response. #800

💙 This release is supported by Steven B., James Manolios, chenrik, aldumil, Arne Schwarck, derpderpington, Chippie, dint, jhalpern, Lex Fradski, Schlufo, cyberswan.at, craftyklaus, JMyrng and Jonah B. on Patreon 💙

What's Changed

New Contributors

Full Changelog: 0.23.6...0.24.0-rc

0.23.6

06 Feb 18:46
ca32d6e
Compare
Choose a tag to compare

⚠️This release contains breaking changes ⚠️

postgis/postgis:14-3.5

In your docker-compose.yml change image for postgres:

dawarich_db:
-   image: postgres:14.2-alpine
+   image: postgis/postgis:14-3.5-alpine
    shm_size: 1G
    container_name: dawarich_db

If you're on an ARM system and already updated your postgres to 17, use ghcr.io/baosystems/postgis:17-3.5 image instead of postgis/postgis:14-3.5-alpine. Depending on which postgres version you're using, you can select a fitting docker image to replace your old one here: https://github.com/ImreSamu/docker-postgis?tab=readme-ov-file#recommended-versions-for-new-users

Added

  • Enabled Postgis extension for PostgreSQL.
  • Trips are now store their paths in the database independently of the points.
  • Trips are now being rendered on the map using their precalculated paths instead of list of coordinates.

Changed

  • Ruby version was updated to 3.4.1.
  • Requesting photos on the Map page now uses the start and end dates from the URL params. #589

💙 This release is supported by Steven B., James Manolios, chenrik, aldumil, Arne Schwarck, derpderpington, Chippie, dint, jhalpern, Lex Fradski, Schlufo, cyberswan.at, craftyklaus, JMyrng and Jonah B. on Patreon 💙

What's Changed

Full Changelog: 0.23.5...0.23.6

0.23.6-rc49

06 Feb 17:06
Compare
Choose a tag to compare
0.23.6-rc49 Pre-release
Pre-release

0.23.6-rc48

06 Feb 17:01
Compare
Choose a tag to compare
0.23.6-rc48 Pre-release
Pre-release

0.23.6-rc47

05 Feb 22:20
Compare
Choose a tag to compare
0.23.6-rc47 Pre-release
Pre-release

0.23.6-rc46

05 Feb 21:41
Compare
Choose a tag to compare
0.23.6-rc46 Pre-release
Pre-release

0.23.6-rc45

05 Feb 21:05
Compare
Choose a tag to compare
0.23.6-rc45 Pre-release
Pre-release

0.23.6-rc44

05 Feb 20:58
Compare
Choose a tag to compare
0.23.6-rc44 Pre-release
Pre-release

0.23.6-rc43

05 Feb 20:24
Compare
Choose a tag to compare
0.23.6-rc43 Pre-release
Pre-release

0.23.6-rc42

05 Feb 19:49
Compare
Choose a tag to compare
0.23.6-rc42 Pre-release
Pre-release