Skip to content

Commit 3f0dd22

Browse files
authored
Merge pull request #45520 from outinyman/patch-25
Content updates
2 parents 6cbfac8 + 59b52a8 commit 3f0dd22

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/azure-maps/how-to-use-best-practices-for-search.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ To make any calls to the Maps service APIs, you need a Maps account and key. For
2828
> To query the search service, you can use the [Postman app](https://www.getpostman.com/apps) to build REST calls or you can use any API development environment that you prefer.
2929
3030

31-
## Best practices for Geocoding
31+
## Best practices for Geocoding (Address Search)
3232

3333
When you search for a full or partial address using Azure Maps Search Service, it takes your search term and returns the longitude and latitude coordinates of the address. This process is called geocoding. The ability to geocode in a country is dependent upon the road data coverage and the geocoding precision of the geocoding service.
3434

@@ -53,10 +53,12 @@ See [geocoding coverage](https://docs.microsoft.com/azure/azure-maps/geocoding-c
5353

5454

5555
**Fuzzy search parameters**
56+
57+
Azure Maps [Fuzzy Search API](https://docs.microsoft.com/rest/api/maps/search/getsearchfuzzy) is the recommended service to use when you don't know what your user inputs are for a search query. The API combines Point of Interest (POI) search and geocoding into a canonical *single-line search*.
5658

5759
1. The `minFuzzyLevel` and `maxFuzzyLevel`, help return relevant matches even when query parameters do not exactly correspond to the desired information. Most search queries default to `minFuzzyLevel=1` and `maxFuzzyLevel=2` to gain performance and reduce unusual results. Take an example of a search term "restrant", it is matched to "restaurant" when the `maxFuzzyLevel` is set to be 2. The default fuzzy levels can be overridden as per request needs.
5860

59-
2. You can also specify the exact set of result types to be returned by using the `idxSet` parameter. For this purpose you can submit comma-separated list of indexes, the item order does not matter. The following are the supported indexes:
61+
2. You can also prioritize the exact set of result types to be returned by using the `idxSet` parameter. For this purpose, you can submit a comma-separated list of indexes; the item order does not matter. The following indexes are supported:
6062

6163
* `Addr` - **Address Ranges**: For some streets, there are address points that are interpolated from the beginning and end of the street; those points are represented as address ranges.
6264
* `Geo` - **Geographies**: Areas on a map that represent administrative division of a land, that is, country, state, city.
@@ -312,8 +314,11 @@ Points of Interest (POI) Search allows you to request POI results by name, for e
312314

313315
To improve the relevance of the results and the information in the response, Point of Interest (POI) search response includes the brand information that can be used further to parse the response.
314316

317+
You also can submit a comma-separated list of brand names in the request. You can use the list to restrict the results to specific brands by using the `brandSet` parameter. Item order does not matter. When multiple brands are provided, only results that belong to (at least) one of the provided lists are returned.
318+
315319
Let's make a [POI Category Search](https://docs.microsoft.com/rest/api/maps/search/getsearchpoicategory) request for gas stations near Microsoft campus (Redmond, WA). If you observe the response, you can see brand information for each POI returned.
316320

321+
317322
**Sample query:**
318323

319324
```HTTP

0 commit comments

Comments
 (0)