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

import population data from geonames #351

Closed
missinglink opened this issue Jun 30, 2016 · 2 comments
Closed

import population data from geonames #351

missinglink opened this issue Jun 30, 2016 · 2 comments

Comments

@missinglink
Copy link
Contributor

copied from #212

some geonames imports/concordances are missing the associated population metadata.

eg:

for the record above I'd expect the WOF record to have a population value of 7556900

I'm not sure about the scale of the problem, I found this when running our acceptance test suite and found that it affects searches for: brooklyn, london, portland, paris etc.

we are using the population data in pelias to score more populous places higher in the results (eg London UK vs. London ON) so it's important that we can get this fixed ASAP.

thanks!

@missinglink
Copy link
Contributor Author

maybe this has been fixed? checking pelias code first

@missinglink
Copy link
Contributor Author

yes, apologies its an import error as per pelias/whosonfirst#106

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

1 participant