PTV Group - Logistics Forum

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.