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

How should we handle mz:is_funky records #513

Open
orangejulius opened this issue Jul 14, 2020 · 1 comment
Open

How should we handle mz:is_funky records #513

orangejulius opened this issue Jul 14, 2020 · 1 comment
Labels

Comments

@orangejulius
Copy link
Member

Who's on First has a property called mz:is_funky which is described as follows:

Used when Mapzen suspects the record is bad or inappropriate but additional confirmation is needed before the feature is deprecated. Records with a 1 value are recommended to be hidden from map display and search unless explicitly asked for by name.

Currently, Pelias does not do anything with this value in either this repository or wof-admin-lookup. Should we?

I feel like we've had this discussion several times before, but it's never been recorded on GitHub as far as I can tell.

There are several different ways we might handle these records:

What's the right approach? Are there other things we might do as well?

@missinglink
Copy link
Member

From the description, it sounds like we should (at minimum) exclude them from wof-admin-lookup.

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

No branches or pull requests

2 participants