geocoding - Mappoint - prioritise post code over street name in FindAddressResults() -
We operate a route optimization service, these routes usually include 100+ deliveries in the local area several times a day. There are lots of delivery that can be present in one postcode.
In this way, when we use mappoints to optimize connecting pathpoints and running on postcodes; Streetname / house number
The problem, if you find MapPoints FindAddressResults ()
with a bad streetname but valid postcode function, it does not pay attention to the postcode and find the streetname somewhere else, often tries to call a random Hundreds of miles away in the city.
Now, when we can ask stores to improve the quality of their data - this will never be done reliably.
My question: When FindAddressResults () calls
, unlike this, it is the default behavior which gives priority to streetname to postcode, more postcode than this streetname Is there any way to prioritize
Example Usage (These are written in VB6 (do not ask) - but any examples / information will help):
'#### Geocode using postcode; Streetname set oResults = oMap.FindAddressResults (rsRequest ("Request_Address") ,,, rsRequest ("Request_Postalcode")) If oResults.Count = 0 then '#### nothing was found, postcode using geocode only Set oResults = OMAP. FindAddressResults (,,,, rsRequest ("Request_Postalcode")) end then
The only thing I can do is install a "max distance" var, then think off 1 ( The best match) is the default only search for a postcode - [in the oResults] that over the limit, but that would be the best thing to work with a quickie
Edit 1 -. Just came with this, it looks OK:
set oResults = oMap.FindAddressResults (rsRequest ("Request_Address"), rsRequest ("Request_Postalcode")) if oResults.ResultsQuality & Lt; & Gt; Geoffurst Weltgood then re-transcribed ("request_Address") & amp; "+" & Amp; RsRequest ("Request_Postalcode") and "Not only bad results (" and oResults.ResultsQuality) ", only using postcode .. .." set oResults = oMap.FindAddressResults (,,,, rsRequest ("Request_Postalcode ") Finally, after the
- Query with street address
- Check the results if it's ambiguous / bad, then ...
- ... just the second with a postcode Execute the query
British address Along with FindAddressResults Another way to improve the quality, some different until you get "good" quality results, Call FindAddressResults Each call will vary slightly in the parameters. The British address is beautiful, for example, home The name can be in line 1 (to make road 2); and there may be more than one place ("city" in American language) - such as in a village and city / city address.
Some Testers Run before the analysis data; And find the best performing combinations. Then your call sequence will start with the best combination, the second best, etc. Until no 'good' result is found. If there are no results at the end, then you can try your postcode-only call as a later version.
Comments
Post a Comment