20060827

A find method, no matter what type of find it is, always returns the results in the form of the FindResults instance, which tells you how many matches are found for your find query along with the actual location matches.

For example, if you are searching for a place and your search yields 200 matches, you can request to return only the top 10 results.

Along the same lines, you can also request a range of results starting with any valid index (such as from 21 to 30), which is very useful if you are displaying the search results from multiple pages (the typical pagination feature for displaying data).
同样。。。分页显示

Using this field, you can filter out the low-confidence results below the specified ThresholdScore.

Using the FindOptions object, you can tailor the results returned by the find method according to your application's needs.

How do all the entities and entity relationships defined in MapPoint Web Service help you? The short answer is that you can issue smarter and more focused find queries to find things that suit your needs.

Entities are used to issue queries with limited geographic context (such as all states within the United States).

If you take the United States, for example, the country region information is organized as follows:

Even though your threshold score is 0 and there are 500 returned results requested, by assigning specific entity type, the find is narrowed down to 9 results from the original 32 results.

An example of such implementation would be to provide a browse functionality where your customers can select a country first, a state second, a county third, and then find all cities within that county without hitting any maximum result count issues, since you are confining your query to a smaller, limited geographic area.

The FindAddressSpecification also exposes the Options field so that you can control the behavior of the locations returned by this method using the FindOptions class; the FindOptions behavior that we have looked at in the Find method still holds true for this method except that you can only get a maximum of 100 results instead of 500.

The combined size of all your data sources cannot exceed 2 gigabytes.

Keep in mind that the HTTP session is kept alive during this asynchronous operation behind the scenes--this pattern is asynchronous at your application thread level but not at the HTTP communication level.

One of the advantages of working with web services is that you can invoke methods over the wire using XML, but due to the remote nature of this method and XML's inherent behavior to bloat the packet size, it may pose performance and end user experience issues.

Because the XML bloats the size of the request and response packet, this could cost your application users a lot of money.

the entity ID of the United States narrows your search to the United States