Answers can be incomplete
Some questions abstain even when related material exists. Broader responses can include extra passages, repetition or missing conditions. Citations establish where text came from, not that an answer is complete or correct.
PLEASE READ BEFORE TESTING
A useful experiment.
Not a finished product.
GUS is offered as a demo for testing. Bugs, incomplete answers and rough edges remain. Downloading a full package does not mean full product acceptance or reliable advice.
What to watch for.
Maps do not establish access
A route, boundary or mapped ramp does not prove a legal entrance, opening time, gate status, road condition or activity permission. Check the current situation independently.
Scans and tables need checking
OCR can misread values and units, and complex tables or scans can lose structure. Inspect the cited PDF page before using a measurement or critical instruction.
Cold starts can be slow
The measured first geographic Ask still took about 12 seconds after process restart. Local answers depend on device resources. Large imports, copying and first-launch preparation take time.
Platform scope matters
Windows uses static planning rather than live GPS. Android routing is limited to bundled North Georgia coverage. DIY Android, iOS, macOS and Linux downloads are not supplied.
Test backups and updates
The demos have unsigned Windows executables and a debug-signed Android APK. Export and retain your files. Uninstalling Android or clearing storage removes private app data.
CURRENT BUILD NOTES
What changed in North Georgia v53?
The Android map now hides unselected saved tracks, including old lines that used to reappear near Ellijay on zooming out. Opening your saved route still selects its own line. Catalogue reuse and a faster vector reader reduce repeated work without changing the bundled databases, models or ranking rules.
On the test devices, the warm Map page took about 0.3 seconds and Explore about 0.5 seconds. A cold geographic Ask dropped from about 21 to 12 seconds. The Windows card-to-map journey dropped from about 14 to 2 seconds. These are individual measurements, not guarantees for your hardware or every query.
Broader full-answer acceptance remains open. There are still answer-procedure test failures and a historical replay fixture that was unavailable for a wider check. A corrected Android source-navigation test compiled but was not rerun after device authorization ended.
Send testing feedback ↗