Functionality - I don't know what's missing. But maybe the problem is that GEOGET is not a clone of GSAK, but a completely independent project that has similar goals but is handled completely differently. So it's possible that what is seemingly missing is somehow simply being done DIFFERENTLY. For example, I don't see the waypoints work anywhere in GSAK (GSAK's term Child waypoints). It's hard enough to explain to GSAK users that they don't need a million different databases and that just one is enough. After all, GSAK is unable to sew a large GPX file and crashes - I haven't encountered a limit in GeoGet so far.
I have in my database, which has a size of about 5 Giga, about 250 thousand final coordinates, which I can process, correct, check (we have an integrated link to checkers), export, and at the same time I have normal data that I upload to the navigation.