Repository navigation
Warn of an ignored --geotag_source_path only when it was given - #917
Merged
caglarpir merged 6 commits intoOct 24, 2026
Merged
Conversation
Since mapillary#898, interval sampling with --geotag_source gpx reads the GPX again for each video, to tell which samples fall outside its track. Sampling 11 BlackVue videos every 30 s against a 163 MB GPX of 498 tracks, video_process took 293 s instead of 161 s before mapillary#898, and printed "Found 498 tracks in the GPX file" 12 times instead of once. The other readers parsed such a file once per video too: distance sampling, in a pool of processes started for each video, and the geotagging stage of videos, in each process of its pool. An NMEA file is read once per process since mapillary#909. Parse a GPX file once per process, and share its tracks among the readers: interval and distance sampling, GPX sync of --geotag_source and --video_geotag_source, and the geotagging stage of images. The tracks are kept by the path and content of the file, so a file that changes is parsed again, and only those of the last four files parsed are kept, in the main process only. The geotagging stage of videos reads a GPX that geotags several videos once, before its pool, as it reads an NMEA file; the GPX of each video is still parsed in the pool. Distance sampling reads its video in its own process, as interval sampling does. GPX sync moves copies of the points. The warnings about the tracks of a file, and about its points before 1980, are given once per file. That video_process run now takes 82 s and prints the warning once. Its 22 samples and their descriptions are the same, and its peak memory is 2.68 GB (2.84 GB on main). On one of the videos it takes 15.9 s instead of 25.3 s, and process 10.1 s with 2.69 GB, as on main. Sampling the 11 videos by distance with the GPX as --video_geotag_source takes 25 s instead of 107 s. process on them, with the GPX as --geotag_source or --video_geotag_source, takes 22 s instead of 26 to 29 s, and its processes peak at 6.4 GB together instead of 14 to 16 GB, as each of them parsed the file. Compared with main on process, video_process and sample_video, with GPX and NMEA sources and with the default sources, on BlackVue, GoPro MAX, Sony and 70mai videos and on images, the descriptions and samples are the same, and only the repeated warnings are gone. mapillary#898 said that with the legacy sources the frames before a late GPS start were kept and geotagged as before: they are kept, and fail as before.
mapillary#901 took every sentence without a checksum for cut short as soon as any other sentence of the file had one. Checksums are optional in NMEA 0183, and logs that mix sentences with and without them read in full before: a log with a checksum on one line only, or on its GGA sentences only, now failed whole as "not a valid NMEA file", and of two logs concatenated, one with checksums and one without, the half without was skipped. A sentence without its checksum is now cut short only when its own fields show it: when it has fewer fields than a complete sentence (11 for RMC, as NMEA 2.0 to 2.2 write it, 12 with the mode of NMEA 2.3 and 13 with the navigational status of NMEA 4.1; 14 for GGA), when the date of an RMC sentence is not 6 digits, or when its time does not parse. A sentence with its checksum ends where the checksum shows, however few fields it has, and one whose checksum does not match is still malformed. The checksums of other sentences no longer count. When no fix of a file can be read, the error now says why, with the first malformed sentence, its line and the reason: "track.nmea is not a valid NMEA file: 2 of its 2 RMC and GGA sentences are malformed, the first on line 1 (checksum does not match: 00 != 47): $GPRMC,...". It said only "not a valid NMEA file". (mapillary#901's message said that pynmea2 reads a time cut to "00052" as 00:00:02; it reads it as 00:05:02.) Checked on a 650-fix log, with the video it belongs to: with a checksum on one line only, with checksums on its GGA sentences only, and as two halves with and without checksums, it gives the track of the original, 650 points over 649 s, with no warning, where it failed twice and gave 325 points. Written GGA first across midnight and ending with an RMC sentence cut inside its date, it still gives the 650 points, and one warning. A log whose sentences are all cut short, which gave a stationary video, fails with the reason. The NMEA logs of a Sony action camera and of an image sequence read the same points as before, and process of the images and the video, video_process by distance and by interval with the NMEA log, and plain process and video_process of other cameras write the same descriptions.
With --video_geotag_source gpx followed by another source, such as --video_geotag_source native, interval and distance samples of a track placed from the GPX lost the handling of mapillary#903. A Sony video without GPS of its own, sampled against a GPX with a 73 s gap at MAPILLARY_TOOLS_MAX_GPX_GAP_SECONDS=60, got positions across the gap for 7 of its 65 interval samples (every 10 s) and 113 of its 1036 distance samples, where gpx alone leaves them out and process fails the video. With --interpolation_use_gpx_start_time, the track was not moved to start at the first interval sample, and the first sample of the Sony video was left out. The interval samples were stamped by the start time or the GPS clock of the video rather than by the GPX where they are: 1 s apart on the Sony video, and 2.9 s on a GoPro MAX timelapse with --interpolation_use_gpx_start_time. mapillary#903 took a track as placed from a file only when every source was a GPX or NMEA file, but the sources are tried in turn, and the one that read the track placed it. factory.process() now tells which source geotagged each file, and sampling decides by it. A track that a GPX or NMEA file placed has its gaps left out, its start moved and its samples stamped by it, whatever the other sources are. A track that the video's own GPS gave, before a GPX or after one that misses the video, is sampled as before. With gpx followed by native or video, and with native followed by gpx on a video without GPS of its own, the samples, descriptions and warnings are now those of gpx alone, on the Sony video and the GoPro MAX timelapse, by interval and by distance, with and without the start time. Unchanged: gpx alone; a BlackVue video that a GPX misses, geotagged by its own GPS after or before the GPX; native before a GPX on the GoPro MAX timelapse; process; and the default sources. With the legacy gopro source or exiftool_xml geotagging the samples, every sample is kept and the descriptions do not change, as before; with exiftool_xml, which reads videos as well, the interval samples are now stamped by the GPX, as they were with gopro.
Since mapillary#902 decodes an NMEA file with errors="replace", so that a byte damaged in a log costs one sentence, a file that is not text at all is decoded whole too, and mapillary#909 reads it whole to hash it. A 1.3 GB video given as the NMEA file of `process --geotag_source nmea` took 30 to 50 s and 4.5 to 8 GB of memory before it failed as "not a valid NMEA file", where it failed in a fraction of a second before mapillary#902; a video of tens of gigabytes could run the machine out of memory. Look at the first 64 KiB of the file first. If they have a NUL byte, or if most of them do not decode as UTF-8, the file is not text: it fails at once, as "not a valid NMEA file: it is not text", without being read further. A text file is read as before, a byte damaged in one of its sentences included. The 1.3 GB video now fails in 4 s (a run without the NMEA file takes 3 s on the same machine) with 64 MB of memory, and a 4.3 GB video in under 2 s. The NMEA logs of a Sony action camera and of an image sequence read the same points as before, a log with a byte that is not text in one sentence geotags the same 106 of its 113 images, and process and video_process with NMEA logs, and of other cameras without them, write the same descriptions.
A time in a gap of more than MAPILLARY_TOOLS_MAX_GPX_GAP_SECONDS (an hour by default) between two fixes of a GPX or NMEA track is outside the track. process (mapillary#899) and interval sampling compared the gaps of a track placed on a video in video seconds, against the limit divided by the rate of the video's clock. The division leaves the two a rounding error apart, so at a rate other than 1 a gap of exactly the limit could count as more than it. On a LabPano video, whose clock runs 1.143 times as fast as its video, a fix exactly an hour before a track that starts 17 seconds into the video was left out, and the track uploaded with the video started at 17.2 s rather than at 0, while interval sampling left out 2 of its 58 samples. With the limit at 60 s, a gap of exactly 60 s inside the video failed it in process, and interval sampling left out 5 of the 58 samples. Judge every gap in GPS seconds: between the GPS times that the points of a GPX or NMEA track keep once placed on the video, or, for points without one, between their times at the rate of the clock; rounded to the millisecond, which no GPS time is recorded more finely than. A gap of more than the limit is one, and a gap of exactly the limit is not, as the geotagging stage judges the gaps of a track for images and as distance sampling judged them already. Checked process, distance sampling and interval sampling of a LabPano, a BlackVue and a GoPro MAX timelapse video, each with GPX tracks made from its own track with a gap of exactly the limit, or half a second more, before the video and inside it, at limits of 3600 and 60 s (54 runs): only the LabPano runs with a gap of exactly the limit change, as above. Gaps half a second over the limit are left out as before, and the BlackVue and timelapse runs do not change. Nor do the 24 runs with real GPX and NMEA tracks of a GoPro MAX, a Sony camera and 70mai dashcams, whose logs have gaps of days.
video_process gives the sources without a source path of their own the video import path, as --geotag_source_path would (mapillary#906). A source with a path of its own keeps it, and video_process warned that "The option --geotag_source_path is ignored for source ...", although no --geotag_source_path was given: on every `video_process DIR OUT --video_geotag_source exiftool_xml`, as exiftool_xml gets the pattern %g.xml with the video import path, and for a source given a path of its own, such as {"source": "gpx", "source_path": ...}. Warn only of a --geotag_source_path that the user gave. A source with a path of its own still ignores it, with the warning, in process and in video_process. Checked process and video_process on a BlackVue video with its ExifTool XML and with a GPX: with exiftool_xml alone, and with a gpx source with a path of its own, video_process no longer warns. With a source with a path of its own and --geotag_source_path, process and video_process warn as before (once, and three times). With exiftool_xml and --geotag_source_path, with exiftool_xml in process, and with the default sources, nothing changes. The descriptions of all 8 runs are those of before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #916; review the last commit.
video_process gives the sources without a source path of their own the
video import path, as --geotag_source_path would (#906). A source with a
path of its own keeps it, and video_process warned that "The option
--geotag_source_path is ignored for source ...", although no
--geotag_source_path was given: on every
video_process DIR OUT --video_geotag_source exiftool_xml, as exiftool_xml gets the pattern%g.xml with the video import path, and for a source given a path of its
own, such as {"source": "gpx", "source_path": ...}.
Warn only of a --geotag_source_path that the user gave. A source with a
path of its own still ignores it, with the warning, in process and in
video_process.
Checked process and video_process on a BlackVue video with its ExifTool
XML and with a GPX: with exiftool_xml alone, and with a gpx source with
a path of its own, video_process no longer warns. With a source with a
path of its own and --geotag_source_path, process and video_process warn
as before (once, and three times). With exiftool_xml and
--geotag_source_path, with exiftool_xml in process, and with the default
sources, nothing changes. The descriptions of all 8 runs are those of
before.
Unit and integration tests, doctests,
mypy --python-version 3.9,ruff check,ruff format --checkandusort diffare clean.