geotrax export

Export georeferenced trajectories to GIS formats (GeoPackage, GeoJSON).

usage: geotrax export [-h] [--format {gpkg,geojson}] [--geometry {lines,points}]
                      [--crs {wgs84,local}] [--output-folder OUTPUT_FOLDER] [--cfg CFG]
                      [--set KEY=VALUE] [--log-path LOG_PATH] [--verbose]
                      input

Export georeferenced trajectories to GIS formats (GeoPackage, GeoJSON)

Positional arguments

Argument	Value	Config key	Description
input			A georeferenced .csv file, a video file (its georeferenced .csv is looked up in the output folder), or a folder searched recursively for georeferenced and aggregated .csv files.

Optional arguments

Argument	Value	Config key	Description
--format, -f	gpkg | geojson		Output format: gpkg (GeoPackage) or geojson (default: gpkg).
--geometry, -g	lines | points		lines = one LineString per vehicle with summary attributes; points = one Point per trajectory row with every CSV column (default: lines).
--crs, -crs	wgs84 | local		wgs84 = Latitude/Longitude in EPSG:4326; local = Local_X/Local_Y in cfg -> georef -> transformation -> target_crs (default: wgs84).
--output-folder, -of	OUTPUT_FOLDER		Folder for the exported files. Defaults to the folder of each input .csv; for a folder input, the sub-folder layout below it is mirrored.
--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).