Hello everybody,
I learned from another post, that it might be advisable to switch of phonetic search entirely, because since the search order is Binary->Phonetic->Fuzzy it happens that xLocate finds bad matching in phonetic search whereas fuzzy search would find a better one.
Examples ...
Search found 11 matches
- Mon Nov 20, 2017 12:41 pm
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: Is it possible to change search order (B->P->F) to (B->F->P)
- Replies: 2
- Views: 6557
- Wed Nov 15, 2017 12:29 pm
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: How to use SearchOption STREET_HNRPOSITION
- Replies: 7
- Views: 21864
Re: How to use SearchOption STREET_HNRPOSITION
Hi Jochen,
thanks for your reply.
The question remains, whether this is a bug or a deprecated feature.
Can we get a commitment on this please?
Regards
Metin
thanks for your reply.
The question remains, whether this is a bug or a deprecated feature.
Can we get a commitment on this please?
Regards
Metin
- Wed Nov 15, 2017 10:30 am
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: Functionality of undocumented NamedSearchOptions
- Replies: 2
- Views: 6865
Functionality of undocumented NamedSearchOptions
Hello everybody,
I am looking for ways beyond SEARCH_FUZZY to improve the "hit rate" of xLocate, when adress data is "imperfect".
It looks like native-alternative.xml has a bunch of NamedSearchOptions which sound like they could have an impact.
The following are of particular interest:
1 ...
I am looking for ways beyond SEARCH_FUZZY to improve the "hit rate" of xLocate, when adress data is "imperfect".
It looks like native-alternative.xml has a bunch of NamedSearchOptions which sound like they could have an impact.
The following are of particular interest:
1 ...
- Wed Nov 15, 2017 10:11 am
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: How to use SearchOption STREET_HNRPOSITION
- Replies: 7
- Views: 21864
Re: How to use SearchOption STREET_HNRPOSITION
Hi Jochen,
according to the API-documentation this parameter is NOT marked as deprecated.
Can someone from PTV product management please confirm, if this is the case?
Concerning the question "why do you need it" ...
Data for the street field may contain intentional as well as unintentional ...
according to the API-documentation this parameter is NOT marked as deprecated.
Can someone from PTV product management please confirm, if this is the case?
Concerning the question "why do you need it" ...
Data for the street field may contain intentional as well as unintentional ...
- Thu Nov 02, 2017 9:52 am
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: How to use SearchOption STREET_HNRPOSITION
- Replies: 7
- Views: 21864
Re: How to use SearchOption STREET_HNRPOSITION
Hallo Bernd,
my actual problem occurs when I do NOT want xLocate to search for a HNR at all by specifiying the value 0 (0 - do not search for house numbers).
In this case Detaillevel is HNRINTERPOLATED and get a house number (where does he get that from :? ). That's what's beyond my grasp ...
my actual problem occurs when I do NOT want xLocate to search for a HNR at all by specifiying the value 0 (0 - do not search for house numbers).
In this case Detaillevel is HNRINTERPOLATED and get a house number (where does he get that from :? ). That's what's beyond my grasp ...
- Mon Oct 30, 2017 3:21 pm
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: How to use SearchOption STREET_HNRPOSITION
- Replies: 7
- Views: 21864
How to use SearchOption STREET_HNRPOSITION
Hello everybody,
I am currently dealing with address infomation, which includes house numbers in the street field.
For instance like in the following SOAP call:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3 ...
I am currently dealing with address infomation, which includes house numbers in the street field.
For instance like in the following SOAP call:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3 ...
- Thu Apr 27, 2017 10:51 am
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: Length of street substring crucial for quality of Response
- Replies: 2
- Views: 6868
Length of street substring crucial for quality of Response
Hello everybody,
I discovered an "unexpected" behaviour when calling findAddress() with incomplete street names (i.e. only a substring/subsequence of the real street name is provided).
Depending on the length of the substring the desired result is either found or not. Although I already opened two ...
I discovered an "unexpected" behaviour when calling findAddress() with incomplete street names (i.e. only a substring/subsequence of the real street name is provided).
Depending on the length of the substring the desired result is either found or not. Although I already opened two ...
- Thu Sep 10, 2015 5:57 pm
- Forum: PTV xDimaServer / Developer Matrix Routing API
- Topic: How to use profiles (contraction hierarchies) in createDima
- Replies: 5
- Views: 22113
Re: How to use profiles (contraction hierarchies) in createD
Hello Bernd,
basically yes. Thanks.
Just to make sure ...
1. properties within the specified profile in CallerContextProperty override the properties set for DimaProfile (e.g. speedTable, optimization etc.) ?
2. in the xdima-metin.xml you have the options to specify dimaProfile.car and/or ...
basically yes. Thanks.
Just to make sure ...
1. properties within the specified profile in CallerContextProperty override the properties set for DimaProfile (e.g. speedTable, optimization etc.) ?
2. in the xdima-metin.xml you have the options to specify dimaProfile.car and/or ...
- Thu Sep 10, 2015 4:46 pm
- Forum: PTV xDimaServer / Developer Matrix Routing API
- Topic: How to use profiles (contraction hierarchies) in createDima
- Replies: 5
- Views: 22113
How to use profiles (contraction hierarchies) in createDima
Dear forum users,
I am looking for a way to specify an existing profile upon creation of a new DIMA. Unfortunately I cannot figure out how to do this according to the API documentation. It says the createDima operation takes two parameters:
1. dimaID
2. dimaProfile
The DimaProfile itself ...
I am looking for a way to specify an existing profile upon creation of a new DIMA. Unfortunately I cannot figure out how to do this according to the API documentation. It says the createDima operation takes two parameters:
1. dimaID
2. dimaProfile
The DimaProfile itself ...
- Tue Sep 02, 2014 4:24 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Performance issue calculateRouteInfo with XMLSnippet
- Replies: 1
- Views: 6977
Performance issue calculateRouteInfo with XMLSnippet
Dear forum members,
I recognized that in my environment (1.18.1.0) calling calculateRouteInfo with the additional CallerContextProperty ProfileXMLSnippet lead to an increase of server time compared to specifiying no snippet at all. On the average it took twice as long.
The XMLSnippet I used (see ...
I recognized that in my environment (1.18.1.0) calling calculateRouteInfo with the additional CallerContextProperty ProfileXMLSnippet lead to an increase of server time compared to specifiying no snippet at all. On the average it took twice as long.
The XMLSnippet I used (see ...