You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GSAK import: trackable names keep GSAK's leading <BR> tag #1331
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
Import a GSAK database that has caches with trackables.
Open a cache that has trackables and go to the Trackables tab.
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
lignumaqua commentedon Nov 17, 2026
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.
nagisml commentedon Nov 17, 2026
@AgreeDK pls assign
Strip GSAK's leading <BR> from trackable names
github-actions commentedon Nov 18, 2026
@nagisml This has been completed in PR #1332 and will be included in the next beta release. 🎉