Goecoding Json property Layers list?

xavbro · November 27, 2023, 8:50pm

Hello, I am using geocoding to obtain coordinates from addresses and I was wondering where I could find a list and documentation about the ‘Layers’ returned in the JSON.

I understand that it returns what was found in the request, but I need a list of layers so I can parse every possible result in the most human way (I also need to translate it into French).

Thank you in advance

amandus · November 28, 2023, 1:33pm

Hi @xavbro,

github.com

pelias/documentation/blob/a10230908229edabc86b86e5fd862ea9f317c984/autocomplete.md#layers

# Search with autocomplete

If you are building an end-user application, you can use the `/autocomplete` endpoint alongside `/search` to enable real-time feedback. This type-ahead functionality helps users find what they are looking for, without requiring them to fully specify their search term. Typically, the user starts typing and a drop-down list appears where they can choose the term from the list below.

To build a query with autocomplete, you need a `text` parameter, representing what a user has typed into your application so far. Optionally, you can specify a geographic point where the search is focused, this will allow users to see more local places in the results.

## User experience guidelines

There are several user experience pitfalls to watch out for when implementing a client-side typeahead solution:

### Requests must be throttled

Since autocomplete requests generally correspond directly to user input, it's important to account for fast typers and throttle requests. Some devices and networks (for example, mobile phones on a slow connection) may respond poorly when too many requests are sent too quickly, so be sure to do some testing on your own. [Learn more in this interactive demo.](http://jsfiddle.net/missinglink/19e2r2we/)

Our testing shows that between 5 and 10 requests per second is the range with the best balance of
resource usage and autocomplete responsiveness.

Many Pelias services also enforce hard per-second rate limits, so setting a client-side throttle can
help you avoid exceeding those limits. It's better to send fewer requests on your own terms than
rely on a server's rate limiting to decide which requests will receive a complete response.

This file has been truncated. show original