Skip to content

Geotag the samples of each video by that video only - #866

Merged
caglarpir merged 4 commits into
mapillary:mainfrom
caglarpir:geotag-samples-by-their-own-video
Oct 22, 2026
Merged

caglarpir merged 4 commits into
mapillary:mainfrom
caglarpir:geotag-samples-by-their-own-video

Conversation

@caglarpir

Copy link
Copy Markdown
Contributor

Stacked on #865; review the last commit.

Problem

Since #743 (April 2025), GeotagImagesFromVideo geotags every sample by the track of every video it is given, since the samples moved from its constructor to to_description(). With the samples of two videos, each sample came out twice, the second time outside the other video's track, and the check that it returns no more images than it was given failed:

mapillary_tools process SAMPLES --geotag_source gopro_videos --geotag_source_path DIR   # DIR holds two videos
# AssertionError, exit 1

Fix

Geotag the samples of each video by its own track, as before #743.

Verification

  • The command above geotags the 60 samples of the two videos (was a traceback). A single video is unchanged.
  • New unit test. Unit and integration tests, doctests, mypy --python-version 3.9, ruff check, ruff format --check and usort diff are clean.

A misspelled source type, as in --geotag_source foo or gpx,foo, failed
with a ValueError traceback ("'foo' is not a valid SourceType"), and a
JSON source with a key the schema does not know, such as

    {"source": "gpx", "path": "track.gpx"}

failed with a jsonschema ValidationError traceback. Both exited 1, as for
a crash.

They now raise MapillaryBadParameterError (exit code 2), naming the
supported source types and their aliases, or what the schema rejected
("'path' was unexpected"). This covers --geotag_source and
--video_geotag_source in process and video_process, which parse them the
same way.
…r image

A truncated GPX file, or a file that is no GPX at all, given as the GPX
to geotag images from failed the whole run with a RuntimeError traceback
("Error parsing GPX ...: GPXXMLSyntaxException"). A video geotagged from
the same file gets a MapillaryInvalidGPXError in its description. A GPX
path that does not exist failed with a RuntimeError too, and a GPX file
with no timestamped point with an AssertionError. An NMEA file failed
with a traceback in each of these cases, and when a sentence had no time
or date (TypeError), such as the void ones a receiver writes before its
first fix, or when the file had no RMC sentence to give the date
(UnboundLocalError).

Every image now gets a MapillaryInvalidGPXError in the description,
saying what is wrong with the file, and the run exits as for any other
file that fails to process. The file was given to geotag the images
from, so a mistyped path fails them, as it did, rather than leaving
them to the next geotag source without a word.
…is given

The README says that --video_geotag_source applies to videos and
--geotag_source to images. But the default sources were used only when
neither option was given, so with --video_geotag_source alone, images
had no source at all, and went missing from the description file
without a word, as if they had not been there. That includes the frames
video_process samples: `video_process VIDEO --video_geotag_source native`
sampled the frames, then wrote an empty description file and exited 0.

Geotag images by the default sources when only --video_geotag_source is
given, as when neither option is. The videos are still geotagged by
--video_geotag_source alone.
GeotagImagesFromVideo geotagged every sample by the track of every
video it was given, since the samples moved from its constructor to
to_description(). With the samples of two videos, each sample came out
twice, the second time outside the other video's track, and the check
that it returns no more images than it was given failed:
`process SAMPLES --geotag_source gopro_videos --geotag_source_path DIR`
crashed with an AssertionError for a DIR of two videos.

Geotag the samples of each video by its own track, as before.
@meta-cla meta-cla Bot added the cla signed label Oct 22, 2026
@caglarpir
caglarpir merged commit a03e73b into mapillary:main Oct 22, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant