geotrax aggregate¶
Stage 3: merge georeferenced results across drones/flights.
usage: geotrax aggregate [-h] [--output-folder OUTPUT_FOLDER] [--cfg CFG] [--set KEY=VALUE]
[--log-path LOG_PATH] [--verbose]
input
Aggregate georeferenced tracking results
Positional arguments¶
| Argument | Value | Config key | Description |
|---|---|---|---|
input |
Path to the PROCESSED folder of georeferenced results. |
Optional arguments¶
| Argument | Value | Config key | Description |
|---|---|---|---|
--output-folder, -of |
OUTPUT_FOLDER |
Path to the output folder for aggregated results. If not provided, a 'DATASET' folder is created next to the PROCESSED folder. | |
--cfg, -c |
CFG |
Pipeline config: a bundled preset name (default, confident, lenient, stable) or a path to a custom config file. Run 'geotrax config show' to list presets or 'geotrax config copy' to customize. | |
--set, -st |
KEY=VALUE |
Override a pipeline config value for this run; repeat for more than one, e.g. --set conf=0.35 --set iou=0.6. KEY is a dotted path ('ultralytics.conf') or any unambiguous tail of one ('conf'); an ambiguous or unknown key is an error that lists the candidates. VALUE is read with YAML rules, so true/null/0.35/[0,1,2] all mean what they do in the config file. Use the dedicated flag instead where one exists (it validates its input); passing both for the same key is an error. | |
--log-path, -lp |
LOG_PATH |
Where to write detailed logs: a directory (an auto-named <stage><timestamp><pid>.log file is created inside it, so concurrent or later runs never share a file) or a full file path ending in .log or .txt (any other new path is created as a directory). Defaults to a platform-specific log directory. | |
--verbose, -v |
Also show INFO messages on the console (default: warnings and key notices only). |