OpenTracksApp/OpenTracks
8
113
Fork
You've already forked OpenTracks
21

OSM Dashboard statistics are gone #2255

Closed
opened 2026年01月26日 11:37:27 +01:00 by czarnyckm · 15 comments

Describe the bug
In OSM Dashboard are no longer the statistics present for the tracks shown.
It worked before with the same osm dashboard version, so I think it is open track related

**Describe the bug** In OSM Dashboard are no longer the statistics present for the tracks shown. It worked before with the same osm dashboard version, so I think it is open track related

Thanks for your report. I'll have a look.

Thanks for your report. I'll have a look.

I renamed one column recently (IIRC category). Could that be it?

I renamed one column recently (IIRC category). Could that be it?

Yes, category is used:

Yes, category is used: https://codeberg.org/OpenTracksApp/OSMDashboard/src/commit/da78791470267c8fb2cb5ab7deb2ee88c4e6ba02/src/main/kotlin/de/storchp/opentracks/osmplugin/map/reader/TrackReader.kt#L17

@dennisguse what do we do? Revert OpenTracks or update the protocol version and change the column name in OSMDashboard, too?

@dennisguse what do we do? Revert OpenTracks or update the protocol version and change the column name in OSMDashboard, too?

I will rollback the change + create a new release. This has to wait until reproducible builds are working again for OSMdashboard. And yes, the protocol version should have been incremented as well.

I will rollback the change + create a new release. This has to wait until reproducible builds are working again for OSMdashboard. And yes, the protocol version should have been incremented as well.

Damn. Rolling back is not that easy: I removed and renamed a lot of columns for the tracks table.

  1. ca64f2c749 must be reverted
  2. Migrations from ca64f2c749 cherry-picked
  3. Database version set to 38 (again)
  4. Create a new release

Follow-up:

  1. Re-apply ca64f2c749

  2. Remove workaround //TODO Workaround: Column icon was removed in v4.24.0, but is still required for OSMDashboard v6.4.1.

  3. Increment protocol version

Damn. Rolling back is not that easy: I removed and renamed a lot of columns for the tracks table. 1. ca64f2c749060be81812e35ff986e2d389a2dadf must be reverted 2. Migrations from ca64f2c749060be81812e35ff986e2d389a2dadf cherry-picked 3. Database version set to 38 (again) 4. Create a new release Follow-up: 1. Re-apply ca64f2c749060be81812e35ff986e2d389a2dadf 2. Remove workaround `//TODO Workaround: Column icon was removed in v4.24.0, but is still required for OSMDashboard v6.4.1.` 2. Increment protocol version

Damn downgrading is actual effort as the database change was done before adding temperature (and I was cleaning up a lot).
I will bump the protocol version and create a release.

Damn downgrading is actual effort as the database change was done before adding temperature (and I was cleaning up a lot). I will bump the protocol version and create a release.

Ok, so OSMDashboard has to use the new column name for protocol version 3?

Ok, so OSMDashboard has to use the new column name for protocol version 3?

Actually, all the column names: I renamed the ones in TracksColumns to make it more maintainable.
If we are going down this road: I would also rename the MarkerColumns.

As alternative, I was also looking into creating a separate ContentProvider that maps OpenTracks internal tables to an interface.
I am not sure how much effort this will be.

Actually, all the column names: I renamed the ones in `TracksColumns` to make it more maintainable. If we are going down this road: I would also rename the `MarkerColumns`. As alternative, I was also looking into creating a separate ContentProvider that maps OpenTracks internal tables to an interface. I am not sure how much effort this will be.

I'll implement protocol version 3 in OSMDashboard.

I'll implement protocol version 3 in OSMDashboard.

Support for protocol version 3 should be available in the next nightly build.

Support for protocol version 3 should be available in the next nightly build.

@dennisguse what do you want to change in the MarkerColumns? Then we can put it in v3 as well.

@dennisguse what do you want to change in the MarkerColumns? Then we can put it in v3 as well.

@pstorch Like this: 1369d3ef9f

@pstorch Like this: 1369d3ef9f63e8b03b7dbce273d6700199fb4d9c

Added suport for MarkerColumns V3 in OSMDashboard

Added suport for MarkerColumns V3 in OSMDashboard

Change released with OpenTracks v4.25.1

Fdroid may take some days.

Change released with OpenTracks v4.25.1 Fdroid may take some days.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/com.android.tools.build-gradle-9.x
bugExport#2285
heartrate
dashboard#2265
fit
v4.28.0
v4.27.2
v4.27.1
v4.27.0
v4.26.2
v4.26.1
v4.26.0
v4.25.2
v4.25.1
v4.25.0
v4.24.2
v4.24.1
v4.24.0
v4.23.2
v4.23.1
v4.23.0
v4.22.2
v4.22.1
v4.22.0
v4.21.1
v4.21.0
v4.20.0
v4.19.6
v4.19.5
v4.19.4
v4.19.3
v4.19.2
v4.19.1
v4.19.0
v4.18.0
v4.17.8
v4.17.7
V4.17.6
v4.17.5
v4.17.4
v4.17.3
v4.17.2
v4.17.1
v4.17.0
v4.16.1
v4.16.0
v4.15.0
v4.14.2
v4.14.1
v4.14.0
v4.13.1
v4.13.0
v4.12.5
v4.12.4
v4.12.3
v4.12.2
v4.12.1
v4.12.0
v4.11.3
v4.11.2
v4.11.1
v4.11.0
v4.10.1
v4.10.0
v4.9.9
v4.9.8
v4.9.7
v4.9.6
v4.9.5
v4.9.4
v4.9.3
v4.9.2
v4.9.1
v4.9.0
v4.8.4
v4.8.3
v4.8.2
v4.8.1
v4.8.0
v4.7.1
v4.7.0
v4.6.2
v4.6.1
v4.6.0
v4.5.0
v4.4.0
v4.3.5
v4.3.4
v4.3.3
v4.3.2
v4.3.1
v4.3.0
v4.2.2
v4.2.1
v4.2.0
v4.1.2
v4.1.1
v4.1.0
v4.0.8
v4.0.7
v4.0.6
v4.0.5
v4.0.4
v4.0.3
v4.0.2
v4.0.1
v4.0.0
v3.28.0
v3.27.0
v3.26.1
v3.26.0
v3.25.1
v3.25.0
v3.24.1
v3.24.0
v3.23.0
v3.22.0
v3.21.0
v3.20.2
v3.20.1
v3.20.0
v3.19.1
v3.19.0
v3.18.6
v3.18.5
v3.18.4
v3.18.3
v3.18.2
v3.18.1
v3.18.0
v3.17.3
v3.17.2
v3.17.1
v3.17.0
v3.16.0
v3.15.4
v3.15.3
v3.14.2
v3.15.2
v3.15.1
v3.15.0
v3.14.3
v3.14.1
v3.14.0
v3.13.2
v3.13.1
v3.13.0
v3.12.0
v3.11.1
v3.11.0
v3.10.0
v3.9.5
v3.9.4
v3.9.3
v3.9.2
v3.9.1
v3.9.0
v3.8.1
v3.8.0
v3.7.6
v3.7.5
v3.7.4
v3.7.3
v3.7.2
v3.7.1
v3.7.0
v3.6.2
v3.6.1
v3.6.0
v3.5.0
v3.4.0
v3.3.2
v3.3.1
v3.3.0
v3.2.11
v3.2.10
v3.2.9
v3.2.8
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.0
v3.0.1
v3.0.0
v2.0.0
v2.0.3
v2.0.2
v2.0.6
v2.0.5
v2.0.4
v1.1.16
v1.1.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
v1.1.10
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.21
v1.0.20
v1.0.19
v1.0.18
v1.0.17
v1.0.16
v1.0.15
v1.0.14
v1.0.13
v1.0.12
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
OpenTracksApp/OpenTracks#2255
Reference in a new issue
OpenTracksApp/OpenTracks
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?