Street level image classification project type #53
Conversation
This file contains 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.
This enables the MapSwipe web client to handle Mapillary street level image classification projects.
The client uses the Mapillary JS viewer to visualise tasks. Each task is one (panoramic or non-panoramic) Mapillary image. Some of the default interaction components of the Mapillary viewer (direction, sequence, keyboard) are deliberately deactivated in order to prevent the user from navigating to other images within the viewer while on the same task. The street project component reuses option buttons (as used in Validate, Compare, and Media projects) for the user interaction to classify/answer the tasks.
The MapSwipe task is expected to have the Mapillary image id as task id. The task/image id is the only information required by the viewer.
MapSwipe results are written to Firebase with the task id/Mapillary image id as the key and the answer value as value, e.g.
{ "498763468214164": 0, "132383295515501": 1 }.A Mapillary API key/access token needs to be provided through
.env.production.localand.env.development.local.