Where Does RTKLIB Store Configs and Outputs?
RTKLIB GUI apps read .conf option files and write solutions, logs, and RINEX wherever you point them, defaulting to the program folder and user chosen outputs.
Last updated
RTKLIB stores almost nothing by itself. Its GUI tools read option files you save and write results where you aim them. The .conf files capture every processing choice for repeatable runs, which matters more than any default path.
Outputs follow the same user placed pattern: solutions, logs, and converted RINEX land in folders you pick per session. That freedom demands discipline. Name outputs by date and station, or months later the files blur together into mystery data.
Where RTKLIB stores this, by platform
RTKLIB .conf option files (user placed)
Option files saved from RTKNAVI, RTKPOST, and siblings. Keep one per setup. Outputs go to user chosen folders, so standardize locations per project.
RTKLIB .conf option files (user placed)
Same user placed layout as Windows for configs and outputs. Script batch runs against saved .conf files for repeatability.
Frequently asked questions
How do I keep RTKLIB settings?
Save the current options from each app to a .conf file before closing, since defaults reset on launch. Keep one .conf per baseline or rover setup. Version upgrades sometimes add options, so re-save after updating.
Where should RTKLIB write outputs?
Point solution and log outputs at an outside folder in each app's settings rather than the program directory. RINEX, NMEA, and solution files accumulate fast during long sessions. Archive by date for multi day campaigns.
Notice an outdated path? Let us know.