Open stepps00 opened 7 years ago
Not sure why this is happening. Might be a tokenization thing. It should be in there but will need to investigate further:
I'm wary of exposing the colloquial
names by default (there's a lot of noise around places that call themselves "Paris of the ...", but generally more names are better :)
The purpose of the names_all
field is precisely to expose this stuff.
Colloqual is already exposed in “alt” (versus “names”).
On Wed, Jun 21, 2017 at 3:27 PM, Aaron Straup Cope <notifications@github.com
wrote:
The purpose of the names_all field is precisely to expose this stuff.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/whosonfirst/whosonfirst-www-api/issues/48#issuecomment-310223045, or mute the thread https://github.com/notifications/unsubscribe-auth/AA0EO9wtrlIA7JtzHBTr4CIiNMENVmvhks5sGZjDgaJpZM4OBUyh .
The names
(or names_all
) field has always been one-stop shopping for all the possible combinations.
The "names" parameter in the
whosonfirst.places.search
method doesn't seem to be returning all name values for records. One example is San Francisco.San Francisco has a
name:eng_x_colloquial
value of "Bay Area", but it is not returned when called through the API. I'm having the same issue with values in thename:eng_x_unknown
property.Method:
Reponse: