Store track points independently from their tracks #3

New Issue

vdv · 2022-09-25T17:03:27Z

vdv commented

2022-09-25 17:03:27 +00:00

To allow to add new points without having to update the update the tracks and also make it easier to query.

Also, since GPX files can include several tracks and/or routes, we should name top level objects "gpx(es)" rather than tracks (and their container object gpx-docs).

To allow to add new points without having to update the update the tracks and also make it easier to query. Also, since GPX files can include several tracks and/or routes, we should name top level objects "gpx(es)" rather than tracks (and their container object gpx-docs).

vdv self-assigned this 2022-09-25 17:03:35 +00:00

vdv referenced this issue from a commit

2022-09-25 23:47:35 +00:00

Starting to refactor to store track points independently from their tracks (WIP) (#3)

vdv referenced this issue from a commit

2022-09-26 19:50:01 +00:00

Storing track points independently from their tracks (#3). Also adding some basic tests for gpx database operations.

vdv closed this issue

2022-09-26 19:50:33 +00:00

Sign in to join this conversation.