PTV Group - Logistics Forum

Posted: **Wed Jan 16, 2019 3:48 pm**

Hey Bernd,

is there any chance to find/suggest addresses (xLocate / findAddress)
by using only CountryCode + The first two digits of a postalcode?

Example/Thought:

Code: Select all

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <findAddress xmlns="http://types.xlocate.xserver.ptvag.com">
      <Address_1 country="D" postCode="48*" city="" city2="" street="" houseNumber="" />
      <ArrayOfSearchOptionBase_2 />
      <ArrayOfSortOption_3 />
      <ArrayOfResultField_4 />
      <CallerContext_5>
        <ns2:wrappedProperties xmlns:ns2="http://baseservices.service.jabba.ptvag.com">
          <ns2:CallerContextProperty value="PTV_MERCATOR" key="CoordFormat" />
          <ns2:CallerContextProperty value="default" key="Profile" />
        </ns2:wrappedProperties>
      </CallerContext_5>
    </findAddress>
  </soap:Body>
</soap:Envelope>

Best regards from Münster
Max

Posted: **Thu Jan 17, 2019 10:26 am**

Hello Max,

this is a contradiction to the definition of geocoding:

To geocode an address means to get a coordinate of a given address.
What you describe is the usecase "extract data" which is not the core feature and also "not wanted".

Therefore we can't push this

If you need an index of the data please get in touch with sales to get an offer for the data itself (via DDS)

Best regards,
Bernd

Posted: **Thu Jan 17, 2019 10:33 am**

Have you already switched of the FrequencyFilter in the native-default.ini?

Posted: **Thu Jan 17, 2019 10:56 am**

Hey there,

absolutely no problem : )
I am not a friend of using inaccurate data, too.

Unfortunately > tenders, inquiries, etc are often based on two-digit zip codes.

But - of course - we can deal with that!
Thanks for the answer; then I will contact sales if necessary.

PS: I can not say it more often > I am thrilled how nice and helpful this forum "lives".

Best regards
Max

Posted: **Thu Feb 21, 2019 10:22 am**

Hello Mr. Beermann,

what we could do is to extract the x/y coordinates out of our POSTCODE 2 Layer Europe (Centroids). Surly those have to be licensed under a specific use case. I could prepare this, but to offer this I need to know more about the usecase.

Regards

Andreas

PTV 405

AD-10 Canillo 1.676.383 42.587.965
AD-20 Encamp 1.641.638 42.529.797
AD-30 Ordino 1.538.383 42.600.152
AD-40 La Massana 1.487.836 42.558.445
AD-50 Andorra la Vieja 1.512.757 42.496.382
AD-60 Sant Julia de Loria 1.490.483 42.466.756
AD-70 Escaldes-Engordany 1.593.115 42.486.791
AL-10 Tirane 19.917.434 41.317.483
AL-15 Kruje 19.747.253 41.503.178
AL-20 Durres 19.521.572 41.423.634
AL-25 Kavaje 19.593.845 4.113.778
AL-30 Elbasan 20.069.669 41.067.902
AL-33 Gramsh 20.246.589 40.856.173
AL-34 Librazhd 20.344.266 4.115.882
AL-35 Peqin 1.978.946 41.069.779

Posted: **Fri Feb 14, 2025 12:51 pm**

Hello again,

just received some similar request these days. The static data approach is still an option, but in the meantime we added a dedicated API into our PTV Developer suite which sounds like it could match the usecase of "support a tender process by offering standard distances":

EWS Road Distance API

It is based on two core functions

Suggest potential reference addresses based on cities, ports or borders. The total reference objects database contains 14'000 objects all over Europe and more than 10'000 just in Germany. The suggestion then returns complete foreign keys for referencing the locations in the second step. Coordinates are not contained at that level

Request:

Code: Select all

{
  "country": "DE",   "locality": "Karlsruhe",   "postalCode": "76131",
  "region": "BEST_QUALITY",  "dataVersion": "LATEST",  "type": "CITY",  "limit": 10
}

Response:

Code: Select all

{
  "suggestions": [
    {      "type": "CITY",      "country": "DE",      "postalCode": "76131",      "locality": "Karlsruhe"    },
    {      "type": "CITY",      "country": "DE",      "postalCode": "76133",      "locality": "Karlsruhe"    },
...
  ]
}

Ask for the reference values from start reference object to destination reference object.

Code: Select all

{
  "requestLocationStart": {
    "type": "CITY",
    "country": "DE",
    "postalCode": "20095",
    "locality": "Hamburg"
  },
  "requestLocationDestination": {
    "type": "CITY",
    "country": "DE",
    "postalCode": "",
    "locality": "Buxtehude"
  },
  "dataVersion": "LATEST",
  "region": "BEST_QUALITY",
  "results": [
    "COORDINATES",
    "TOLL_DISTANCE"
  ]
}

Response:

Code: Select all

{
  "distance": 38000,
  "tollDistance": 37000,
  "start": {    "type": "CITY",    "country": "DE",    "postalCode": "20095",    "locality": "Hamburg",    "latitude": 53.54897,    "longitude": 9.99337  },
  "destination": {    "type": "CITY",    "country": "DE",    "postalCode": "21614",    "locality": "Buxtehude",    "latitude": 53.46758,    "longitude": 9.68122  },
  "dataVersion": "V2025",
  "region": "GERMANY"
}

PTV Group - Logistics Forum

Two Digit / Postal Code

Two Digit / Postal Code

Re: Two Digit / Postal Code

Re: Two Digit / Postal Code

Re: Two Digit / Postal Code

Re: Two Digit / Postal Code

Re: Two Digit / Postal Code