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

need to constrain "location precision" calculations #522

Open
paregorios opened this issue Oct 18, 2024 · 0 comments
Open

need to constrain "location precision" calculations #522

paregorios opened this issue Oct 18, 2024 · 0 comments

Comments

@paregorios
Copy link
Member

Pleiades places are given the value of "rough" or "precise" for location precision (see e.g. JSON) depending on whether they have a published location that is not a BAtlas or GANE grid square. This calculation was created before we had connections.

We need to change the logic, or introduce a new calculated field, because places like Rome, which have no Locations of their own, derive their reprPoints from lots of connections that have good locations by calculating a centroid from them. This is an excellent value, and we'd like to be able to surface that fact along with the reprPoint coordinates.

Maybe keep the existing "location precision" and create a new reprPoint quality field.

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

1 participant