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

delete a POI node option is confusing #99

Closed
danbjoseph opened this issue Nov 15, 2015 · 1 comment
Closed

delete a POI node option is confusing #99

danbjoseph opened this issue Nov 15, 2015 · 1 comment

Comments

@danbjoseph
Copy link
Member

danbjoseph commented Nov 15, 2015

  • If you create a POI in one form. And then select and delete it when OMK is later open for completing another survey. Does anything more happen than it being removed from the OMK map?
  • If you submit data and delete saved/submitted forms. Generated POIs still appear on the OMK map. They are also still deletable.
  • It seems that while filling out one form you can add multiple nodes (and they all persist on the OMK map) but only the one that you step through the tags with and 'Save tag edits to ODK Collect' will be saved into the form and eventually submitted.
  • A user can end up adding a bunch of POIs that show up in OMK but are not actually saved into a form to be submitted?
@dalekunce dalekunce added the POSM label Dec 8, 2015
@hallahan hallahan added the bug label Apr 6, 2016
@hallahan
Copy link
Contributor

hallahan commented Apr 6, 2016

I agree that this button should be taken out. Originally, I was thinking that one could add multiple POIs per response, however, that doesn't really work right with ODK, since you really do only want one element per OSM response in an ODK form.

Also, you are correct that one can't delete POIs that have already been submitted to the server (obviously).

Also, you are correct that the user can currently add a bunch of POIs that show up, but are not actually saved to the XForm Instance XML. They are saved and submitted to the server as media attachments, and this isn't right. This is the cause of bug #115.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants