Search found 44 matches
- Tue Feb 27, 2024 10:20 am
- Forum: PTV xLocateServer
- Topic: Comparison of xLocate 2 and PTV Developer Geocoding API
- Replies: 1
- Views: 376
Re: Comparison of xLocate 2 and PTV Developer Geocoding API
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...
- Tue Feb 27, 2024 9:50 am
- Forum: PTV xLocateServer
- Topic: Possible to reduce the minimimum length requirements for postcodes?
- Replies: 10
- Views: 556
Re: Possible to reduce the minimimum length requirements for postcodes?
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...
- Mon Feb 26, 2024 2:39 pm
- Forum: PTV xLocateServer
- Topic: Possible to reduce the minimimum length requirements for postcodes?
- Replies: 10
- Views: 556
Re: Possible to reduce the minimimum length requirements for postcodes?
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.
- Thu Feb 01, 2024 9:30 am
- Forum: PTV xLocateServer
- Topic: xLocate - Ergebnis verbessern
- Replies: 11
- Views: 20418
Re: xLocate - Ergebnis verbessern
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.
- Mon Jan 08, 2024 1:46 pm
- Forum: PTV xLocateServer
- Topic: xLocate-V2 - Find coordinates of Crossing
- Replies: 2
- Views: 1135
Re: xLocate-V2 - Find coordinates of Crossing
The feature searching for crossings/intersections has yet not been implemented for xLocate 2.
- Thu Jul 13, 2023 9:09 am
- Forum: PTV xLocateServer
- Topic: Understanding scores xlocate 1 vs xlocate 2/Developer
- Replies: 1
- Views: 4504
Re: Understanding scores xlocate 1 vs xlocate 2/Developer
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 ...
- Tue Jul 05, 2022 4:09 pm
- Forum: PTV xLocateServer
- Topic: xLocate 1 : interest of "PHONETIC" search in French
- Replies: 1
- Views: 6586
Re: xLocate 1 : interest of "PHONETIC" search in French
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...
- Tue Sep 21, 2021 7:34 am
- Forum: PTV xLocateServer
- Topic: Geocoding in Map&Guide differs from xLocate 2
- Replies: 3
- Views: 11502
Re: Geocoding in Map&Guide differs from xLocate 2
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.
- Wed Aug 18, 2021 12:24 pm
- Forum: PTV xServer INTERNET (Admin=OH,SM)
- Topic: Resolving UK addresses with full post code in xLocate Intern
- Replies: 5
- Views: 15811
Re: Resolving UK addresses with full post code in xLocate In
Hi together Bernd explained the behavior of UK post code search in xLocate 1 very good. What I can say is that there is no API parameter to disable the 2 steps. Maybe you can check xLocate 2? Here we integrated the 6/7 digits UK post codes into the search index and the response returns postal code, ...
- Wed Jan 22, 2020 11:45 am
- Forum: PTV xLocateServer
- Topic: xLocate2 – single field : filter by country
- Replies: 3
- Views: 4193
Re: xLocate2 – single field : filter by country
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": &...