-
Notifications
You must be signed in to change notification settings - Fork 32
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 correlation between zoom, precision, + human-readable placename in docs #98
Labels
Comments
@ebarry does this make sense to you? |
Yes, this makes sense, and you're talking about for the wiki, right? |
Both the wiki and the README file could feature this :-)
wiki maybe at https://publiclab.org/wiki/location-privacy
…On Mon, Oct 30, 2017 at 6:51 PM, Liz Barry ***@***.***> wrote:
Yes, this makes sense, and you're talking about for the wiki, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ_QYBQXeGdh2ZuYo0AYsfU9edYOtks5sxlMMgaJpZM4QL88E>
.
|
4 tasks
Related to #134 |
@jywarren Should we start with this as well? |
That would be GREAT -- and also adding a link from the location input pop-up to this page so that people can easily find it! |
@jywarren Where do you think we should put that link? In a button? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should clarify the exact correlation between zoom and precision and human-readable placename.
See how in the README, we walk through the relationship between precision and decimal places and zoom level; we could do the same (with a table of what precisions relate to what human readable location "scales" like city, state, country) for this.
We should probably start by making a table which lays out the available human readable place names, so we can propose appropriate precision values for each.
So something like:
x0.0
x0.0
x.0
0.x
0.0x
0.00x
The text was updated successfully, but these errors were encountered: