"totalScore" xServer 2

[mehdi]

Hello Bernd,
One of the client has raised an issue with xServer 2-Cloud regarding their attached query.
We have analysed the situation and informed the client that the value provided for "street" as "TELECABINE VIEUX MOULIN" is incorrect, which is causing the anomaly. If they remove this value from the query, they should receive the correct response from the API regarding the "postalCode".

However, the client insists that even if incorrect information is provided in the query, the xServer should still provide the correct response by considering other accurate information and returning a list of locations sorted by "totalScore" from best to worst. The desired location should be listed at the top.

The query includes the following information:
"postalCode": "73480" (desired postal code)
"city": "LANSLEVILLARD" (desired city)
"street": "TELECABINE VIEUX MOULIN" (incorrect address, which is just the name of the gondola lift station, not street name and cannot even be found on Google)

If you have any remarks or suggestions regarding this case, please let us know so we can respond to the client accordingly.
Thank you.
Best regards,
Mehdi

[Bernd Welter]

Hi Mehdi,

Code: Select all

{
  "Country": "",
  "State": "",
  "Province": "",
  "Locality": "LANSLEVILLARD",
  "Street": "TELECABINE VIEUX MOULIN",
  "HouseNumber": "",
  "PostalCode": "73480",
  "languages": null
}

is a request for an alternative geocoder: The PTV Developer Geocoding&Places OSM API.

Does this look promising?

Bernd

Visualization of the OSM result

Code: Select all

{
  "places": [
    {
      "referencePosition": {
        "latitude": 45.289363,
        "longitude": 6.904852
      },
      "boundingBox": {
        "left": 6.904802,
        "bottom": 45.289313,
        "right": 6.904902,
        "top": 45.289413
      },
      "formattedAddress": "Télécabine Vieux Moulin 2, D 902, L'Envers, Lanslevillard, Val-Cenis, Saint-Jean-de-Maurienne, Savoie, Auvergne-Rhône-Alpes, France métropolitaine, 73480, France",
      "category": "amenity",
      "type": "car_pooling"
    },
    {
      "referencePosition": {
        "latitude": 45.288678,
        "longitude": 6.903597
      },
      "boundingBox": {
        "left": 6.903547,
        "bottom": 45.288628,
        "right": 6.903647,
        "top": 45.288728
      },
      "formattedAddress": "Télécabine Vieux Moulin 1, Rue du Vieux Moulin, L'Envers, Lanslevillard, Val-Cenis, Saint-Jean-de-Maurienne, Savoie, Auvergne-Rhône-Alpes, France métropolitaine, 73480, France",
      "category": "amenity",
      "type": "car_pooling"
    },
    {
      "referencePosition": {
        "latitude": 45.2885832,
        "longitude": 6.9033528
      },
      "boundingBox": {
        "left": 6.9033028,
        "bottom": 45.2885332,
        "right": 6.9034028,
        "top": 45.2886332
      },
      "formattedAddress": "Télécabine Vieux Moulin - Lanslevillard (Val-Cenis), D 902, L'Envers, Lanslevillard, Val-Cenis, Saint-Jean-de-Maurienne, Savoie, Auvergne-Rhône-Alpes, France métropolitaine, 73480, France",
      "category": "highway",
      "type": "bus_stop"
    }
  ]
}

[mehdi]

Hello Bernd,

Thank you for your response. I will suggest to the client to try the PTV Developer option.

Have a great day!

Best regards,

[mehdi]

Hello again Bernd,
client's respond!
"Could you please explain why, in the classic version, when I enter a postal code even if the "street" does not match anything, the result still includes the postal code entered? Is there a way to constrain it to only filter by the postal code?"

Do you have an answer for his question?
thank you again,
best regards,

[Bernd Welter]

Hi Mehdi,

from my latest analysis the input data contains several "noisi" contributions:

• "TELECABINE VIEUX MOULIN" seems to be a business label of an address but not the official part of the postal address. The alternative OSM based geocoder merges postal address and business address data and is therefore successful
• The postal code 73480 is assigned to several districts... I'll need to perform further tests first

[Bernd Welter]

By the way:
Your customer's question seems to be related to the field scores:
Our goal is to provide valid geocoordinates - for a given "input". Even if a specific output element is not of the users expected level.

In your case the user enters a street and therefore probably expects a street level or even more detailed result.
As we can't find his street input we "escalate" to a more rough level based on "alternative" streets.

Last but not least we return the strings which appear in the available data but we comment them with "how good does a single field match with the corresponding input field"?

Please forward the Definition of Scores to the customer... Maybe this helps.

Bernd