PTV Logistics Product Forum

If you want to limit the result to a specific country you must set the countryFilter:
https://developer.myptv.com/en/document ... ionsByText

The geocoder can only geocode them correctly if the data provider specifies the postcode with the coordinates of the postboxes. The quality can vary from country to country.

For vector rendering there is currentlys only the structured_description in English.

Hi Marco
Please take a look at the endpoint of Places by Position:
https://developer.myptv.com/en/document ... s-position

Geocoding API is more or less the same as for xLocate 2. You can find the "Geocoding & Places API Reference" here:
https://developer.myptv.com/en/document ... sByAddress

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 ...

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 ...

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 search. But the ...

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 ...

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": "1100",
"searchOptions ...

Hi Daniel

This is absolutly correct. Currently the reference point of a street segment is the lowest house number in most cases the number 1 If this should be changed we have to discuss this with the Product Management.

Best regards

The xLocate stops searching for streets if all input words can be found as city or district. So Bahnhofstraße finds the 3 results exact and Bahnhofstr finds them as asterisk search. If you searching for Bahnofstraße it is find by fuzzy search.

xLocate is based on the assumption that the first input ...

The algorithm of xLocate2 works completly different from xLocate1. For the xLocate2 the input order doesn't matter and also special characters.
But it sounds that you sometimes don't get the correct results? If this is the case, can you please send as an example?

We did some improvements regarding country and city input but you have to wait for xServer 2.15 which will be released in the next days. If you have not updated the index since your 2.11 installation I also recommend to update it.
On our xServer-Internet test environment you can see and test in ...

Hi Bernd

I think it could be possible to return the housenumber range of a street section if the input range (19-21) is the same as in the data (19-21). But what is expceted if the input range (19-21) is just ein part of the data range (15-29) or is in two ranges (15-19, 21-29)?
In the xLocate 2 we ...