Skip to content

GSAK import: trackable names keep GSAK's leading <BR> tag #1331

Closed

Description

@nagisml

Description

When caches are imported from a GSAK database, every trackable name starts with a literal <BR>, e.g. <BR>Hedgie 1 instead of Hedgie 1.

GSAK stores CacheMemo.TravelBugs as one line per trackable, and each line starts with an HTML line break:

<BR>And we're back in the car (id = 5836847, ref = TB6QPGA)
<BR>Hedgie 1 (id = 6874668, ref = TB7WHED)
<BR>PLAYBOY (id = 4123470, ref = TB4X6K3)

I assume this is done for visualization purpose but maybe @lignumaqua can confirm if there is an other purpose.

_parse_gsak_trackables() in importer/gsak_importer.py takes everything before the (id = …, ref = …) suffix as the name, so the <BR> ends up in Trackable.name.

Effects

  • The Trackables tab in the cache details shows the text <BR>Hedgie 1 (the name is HTML-escaped, so it is not rendered as a line break).
  • The same trackable imported from a GPX file gets a clean name, so the two sources disagree.
  • Anything that writes trackable names out (exports, macros) includes the tag.

Steps to reproduce

  1. Import a GSAK database that has caches with trackables.
  2. Open a cache that has trackables and go to the Trackables tab.
  3. Every name starts with <BR>.

Expected behaviour

The import removes the leading <BR> (any case, and also <br/> / <br />), so the stored name is just the trackable's name. Other text in the name stays unchanged.

maybe add a converter on first opening of the database (once)

Activity

  1. lignumaqua commented on Nov 17, 2026

    @lignumaqua

    No, no other purpose. I think this is a left over artifact from the very early database engine GSAK used, long before the move to SQLite.

  2. nagisml commented on Nov 17, 2026

    @nagisml
    ContributorAuthor

    @AgreeDK pls assign

  3. added a commit that references this issue on Nov 18, 2026
    1152255
  4. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    @nagisml This has been completed in PR #1332 and will be included in the next beta release. 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions