Successor RESULT_LANGUAGE and COUNTRY_CODETYPE?

deals with geocoding and reverse geocoding

Successor RESULT_LANGUAGE and COUNTRY_CODETYPE?

Postby Bernd Welter » Thu Sep 13, 2018 12:48 pm

Hi there,

a partner asked me for some successors of xLocate1 Search Options, especially RESULT_LANGUAGE (triggers to return a hit translated into a specific language, e.g. MUNICH instead of MÜNCHEN) and COUNTRY_CODETYPE (triggers to analyse and return the country code in a specific style, e.g. ISO_2="DE" instead of CODEPLATE="D").

We already identified the proper xLocate2 approach for RESULT_LANGUAGE:
we have to use a request profile and its mapLanguage parameter. Fine.
javascript code
{
"$type": "SearchByTextRequest",
"text": "Springfield",
"requestProfile": {
"mapLanguage": "it"
}
}


We haven't found the successor of COUNTRY_CODETYPE (in xLocate 2.9).
We also would like to see:
  • STREET_HNRPOSITION
  • MAX_RESULT
  • SCORE_TOTALSCORE

Is there already a solution for those?
If not: Will we provide it in a later version?

Best regards,
Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

Bernd at Youtube
User avatar
Bernd Welter
Site Admin
 
Posts: 1157
Joined: Mon Apr 14, 2014 10:28 am

Re: Successor RESULT_LANGUAGE and COUNTRY_CODETYPE?

Postby bocajo » Thu Sep 13, 2018 1:57 pm

Hi

For the most Search Options of xLocate1 we don't have a successor and to be honest we want to as less as possible of these ;)

COUNTRY_CODETYPE - This option is from the input point of view not needed anymore because in xL2 all formats are considered as possible input formats. (xL1 allready works in the same way) If instead of the country name the ISO_2 code is needed as output format then I would suggest to deliver all available formats in the response and the customer can choose what ever it wants.
STREET_HNRPOSITION - If the street input has more than 2 words and house number input field is empty than the xL2 considers every position as a possible house number position.
MAX_RESULT - Currently we have a hard coded max result limitation of 500. And I can imagine that we will get an option simular to MAX_Result. But we have to be sure that the obviously best results are in the top positions and we still working on that ;)
SCORE_TOTALSCORE - I only know this as a result parameter and we also deliver a totalScore in xL2.

Currently it isn't planed to provide these options. But if they are really needed we have to discuss this with the product management.

Best regards, Jochen
Jochen Anderer
Senior Software Engineer
PTV GROUP GERMANY
bocajo
 
Posts: 28
Joined: Tue Mar 01, 2016 3:05 pm

Re: Successor RESULT_LANGUAGE and COUNTRY_CODETYPE?

Postby Bernd Welter » Mon Sep 17, 2018 9:41 am

Hello Jochen,

regarding COUNTRY_CODETYPE :
Quite sure future usecase implementations will require xLocate to return various formats such as ISO2, ISO3 and so on.

If the philosophy of xLocate is to keep the number of parameters low we shall return those formats in one response. Please keep this in mind for future development.

Thanks for your answer,
fast as a shark as usual,
Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

Bernd at Youtube
User avatar
Bernd Welter
Site Admin
 
Posts: 1157
Joined: Mon Apr 14, 2014 10:28 am


Return to PTV xLocateServer