Open
Conversation
This was referenced Jan 22, 2026
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #225 +/- ##
===========================================
+ Coverage 87.41% 87.63% +0.21%
===========================================
Files 205 212 +7
Lines 12458 12946 +488
Branches 1049 1083 +34
===========================================
+ Hits 10890 11345 +455
- Misses 1181 1205 +24
- Partials 387 396 +9 ☔ View full report in Codecov by Sentry. |
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.
This adds project and tutorial creation as well as stats generation for projects of the type Conflation. Conflation allows users to validate building footprints from fAIr or other sources, and compare them against potentially existing OpenStreetMap features.
Conflation projects resemble Validate projects in many ways. The nature of each task changes in the client depending on the presence of buildings in OSM:
The client writes the number of intersecting OSM features together with the task results to Firebase, and, if that number is 1, the OSM id and version number of that building. The backend processes these OSM references and writes them to results and aggregated results exports.
MapSwipe does not commit any changes to OSM at this stage of the implementation. However, the MapSwipe results exports will indicate whether a feature was evaluated against an OSM building footprint, and if so, against which one exactly.
See also changes in: