PTV Group - Logistics Forum

The current OSM Geocoding API implementation can mainly be used for interactive geocoding by the user. After a batch geocoding process, some addresses my remain that need to geocoded manually. In such cases, OSM can be used as a second data source which can resolve some addresses that PTV Geocoder h...

Hi Bernd Nice overview, here are some additions. The suggestion search is available for both multfield and singlefield input but you need to combine it with the geocoding request. The idea with the suggestion search is that you need fewer geocoding requests and a suggestion search is much cheaper co...

The result list of the xL1 depends on the number of addresses found. If you add the parameter <FrequencyFiltering Value="0" Type="bool"/> in the native-default.xml then you will get results for Country=DK and postCode=1. An astrisk search is not implemented for the xL2 multifield...

Which xLocate version and map version are you using? It would also be helpful to know wether you are using single field or multi field search.

Unfortunately such a parameter does not yet exists for xLocate 2. This must be prioritised by the Product Management but was not rated highly enough.

The feature searching for crossings/intersections has yet not been implemented for xLocate 2.

The total score is mainly used to sort the result list. This applies to both xLocate 1 as for xLocate 2. As Bernd said, the score calculation of xLocate 2 and xLocate 1 differs. There is a technical concept of how the score calculation of xLocate 2 works . I recommend not only using the total score ...

Both approaches have there advantages and disadvantages. The phonetic is not so powerful when two letters are swaped and works only for certain languages like english, french and german. Fuzzy works for all languages and two typos but the first two letters assumes as correct. E.g. xL1 doesn't return...

For this approach I would recommend the single field search of xLocate 2 (SearchByTextRequest). When using this you can enter e.g. "Dresden 0" and all postal codes starting with 0 of Dresden are listed.

Hi Leo This will be a new feature of the xServer 2.17 which is currently planed for end of February. Then it is possible to restrict the single field search on spezific countries. In your case the request could look like this: { "$type": "SearchByTextRequest", "text": &...