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

Clarify different applications of 'maps' and 'placement-map' in reference table #55

Closed
tinok opened this issue Aug 14, 2015 · 4 comments
Assignees

Comments

@tinok
Copy link
Member

tinok commented Aug 14, 2015

No description provided.

@MartijnR MartijnR self-assigned this Mar 28, 2018
@MartijnR
Copy link
Contributor

MartijnR commented Mar 28, 2018

I tried this out, but I think placement-map may currently be broken in Collect (stuck at Loading Location) and in Enketo it is not used.

However, after seeing getodk/collect#1084, @lognaturel, I understand the functionality to manually add a point may be added to the regular maps appearance (as in Enketo), which would make placement-map an alias of maps. Is that so @lognaturel?

@lognaturel
Copy link
Contributor

placement-map works well for me! It's possible that in the future maps will also allow manual placement if there's enough interest in the change. I think it makes sense to document placement-map for now.

@MartijnR
Copy link
Contributor

MartijnR commented Mar 29, 2018

Ah thanks. It is a caused by using a combination of maps and placement-map (and it's not actually stuck, it just works as a simple geopoint without map). Am filing bug report for Collect.

getodk/collect#2081

@lognaturel
Copy link
Contributor

Ooh, thank you, @MartijnR! 😊

@tinok tinok closed this as completed in 1f96459 Apr 4, 2018
tinok added a commit that referenced this issue Apr 4, 2018
Clarified maps vs placement-map, closes #55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants