Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no indication of whether a feature/building has already been mapped. #1344

Closed
susmina94 opened this issue Mar 12, 2024 · 2 comments
Closed
Assignees
Labels
enhancement New feature or request priority:critical Blocking current tasks or user workflow

Comments

@susmina94
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
The mappers cannot recognize the buildings that has already been surveyed/mapped. It creates a confusion for the mappers to understand whether they've already mapped those or not because there's no such indication on FMTM or ODK. This can eventually sometimes, cause data redundancy, difficulty in identifying the correct ones.

Describe the solution you'd like
It would be great to see the building change color once they are mapped or a submission has been made using that feature.

This will help the users to understand:

  1. The building has already been mapped
  2. The users also get an insight on how many buildings are left to be mapped
@spwoodcock
Copy link
Member

spwoodcock commented Mar 29, 2024

Related to #1383

This is now possible use Entities.

I propose:

  • We load the Entity info on project detail page via OData endpoint (osm-fieldwork has this).
  • When user clicks start mapping, we update the entity status field to 'IN_PROGRESS` via API and also update their local state to colour the building yellow locally for the user (also useful if mapping offline).
  • All other users that load the Entities will also see a yellow building in progress.
  • When user clicks mapping complete then we update status to 'COMPLETE' and colour green.

On the backend side this is just updating the Entity field.
We should include the status field as a property when the entities are registered (in the default registration form in osm-fieldwork).

Frontend colours can come after.

(Let's start this after #1383 is merged)

@spwoodcock
Copy link
Member

Superseded by #1417

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:critical Blocking current tasks or user workflow
Projects
Development

No branches or pull requests

6 participants