Open
Conversation
…e nearly completed groups)
…sm id, osm version) with results
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
3 participants
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 support for the Conflation project type to MapSwipe web. Conflation allows users to validate building footprints from fAIr or other sources, and compare them against potentially existing OpenStreetMap features.
Tasks of conflation projects consist in building footprint geometries. The web app requests all current OSM buildings within the bounding box of all task features in a task group. The nature of each task changes depending on the presence of buildings in OSM:
Together with the results, the web app writes the number of intersecting OSM features to Firebase, and, if that number is 1, the OSM id and version number of that building.
MapSwipe does not commit any changes to OSM at this stage of the implementation.