Comparison of xLocate 2 and PTV Developer Geocoding API

[Bernd Welter]

Hi Jochen,

maybe it is a good idea to compare the two geocoding APIs. Is the following summary correct?

API	xLocate 1	xLocate 2	Developer Geocoding
features	basic features (HERE XSI-1) Single Field Multi Field Reverse findSuggestion POI Search findCombinedTransport	basic features (HERE XSI-2) Single Field Multi Field Reverse combinedTransport : xData2	basic features (HERE / OSM) Single Field Multi Field Reverse plus extended HERE interactive search (Suggestion), not available for OSM places (points of interest)
data	TOMTOM and HERE	HERE only	Here or OSM
hosting	onPremise (??) and Cloud (till 31.6.2026)	on premise and cloud	100% cloud

So using the Developer API enables you to access additional features.
You could also discuss whether a mix between the Developer geocoding and other APIs (for routing, mapping) makes sense...

Here are some GITHUB repos dealing with Developer Geocoding:

• tutorials-interactive-address-search
• clients-geocoding-api
• clients-geocoding-osm-api
• samples-suggestion-by-address

[bocajo]

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 compared with a geocoding request.

• geocoding-places-api/concepts/suggestions-address
• faq-help#transactioncalculation

For the places there is also a nearby and a area search available.

• geocoding-places-api/concepts/places-position
• geocoding-places-api/concepts/places-area

The OSM Geocoding API is a combination of address and places search and is currently still in experimental stage and there is no suggestion search or area search.