Open iddqd2d opened 2 years ago
Hi @iddqd2d,
Thanks for the report. I can confirm this is true.
Here's a reverse geocoding query for a location in Paris. The results don't include population:
/v1/reverse?layers=locality&point.lat=48.854&point.lon=2.358
Whereas a forward geocoding query for Paris does return population:
I think this is because coarse reverse geocoding uses the Point-in-Polygon service, which either doesn't include or doesn't return population information. Whereas forward geocoding uses the main Elasticsearch datastore, which does.
I can get the population value for forward geocoding, but not for reverse geocoding:
How can I get the population value for reverse geocoding?