Please make sure the setting does not block the URLs below:
https://licensing.loqate.com port 80
https://download.loqate.com port 443
More information of Install Manager can be found at:
Please make sure if the InstallManager is placed and installed in the same directory as Loqate API, e.g., C:/edqav/ 2015Q3.0.7975
We’d like to suggest for you to proceed with offline installation, in which case the license pack and data packs need to be downloaded separately in a machine that has internet connectivity and then copied over to the install machine. More information of the Installation can be found at:
There are 5 ways to get the API version on: http://www.loqate.com/releases/how-to-obtain-version-information/
There are 5 ways to get the data version, please refer to the detailed information at:
We update our reference data on a quarterly basis.
The PostalCode can be retrieved in the query process if other address info is provided, e.g., AdministrativeArea, Locality, Thoroughfare.
We are unable to disclose our data vendors, however, the vendors we obtain the data from are reputable and considered experts in their respective fields.
From a recent test, a block of 200 addresses for a single country will take 4176-4745 ms. A single record on comparison is 254-613ms.
Transactional REST endpoint can accept up to 200 records per request. There are no limits on requests per day, but we recommend sending no more than 3-4 single record requests per second to maintain optimal response times.
We do have a batch API that can accept file uploads – which may be better suited for records of 10K upwards. If running on the transactional service, one-set-of-200-at-a-time would be 5-10 minutes. Processing times on a 10K record file would vary based on country, or countries, but we would expect processing to be performed in minutes (please see https://rewind.everythinglocation.com/api-rest-batch/ for more information).
We offer over 65 countries that have rooftop (or point-level) coverage.
This functionality is available with our new solution, LQT Auto-Complete. We do not provide a Geo/IP look-up solution, but the ability to handle this information if provided. You can see a demo of this at:
Yes. This is also a feature provided in LQT Auto-Complete. Lat/Long can be passed through our reverse geocoding solution and the results can be used in Auto-Complete. It will not be an ‘out of the box’ solution but will involve connecting two solutions together.
Yes, we do provide this service.
Yes, we do provide this service.
PO Boxes are Level 5 – L5 (delivery point). We don’t have a flag for it though, you would need to look at the component value. The current way you are identifying it is if the address verification is correct.
We do have a limited Census Dataset available (see attached documentation).
An older blog post offers more insight: http://support.loqate.com/2014/05/what-happens-in-the-process-of-geocoding/
It explains how each geocode method works with examples. Interpolated geocodes are determined using nearby point data. The low geo-distance results are likely the product of a close set of data points on that street or premise range that allow for a confident/accurate calculation.
Major dataset sources such as UK PAF, USPS, Canada Post, Australia Post will be updated frequently (which usually translates to quarterly or every 4 weeks for PAF/USPS). Minor datasets will refresh less often, but usually no more than 1-2 years. These will mainly be for countries that we don’t have premise-level data for. Data source refreshes are determined on a number of things - data license renewal, priority, availability from data sources.
For NLD, our primary domestic source was last updated with our Q1.1 (February) release using a Q4-dated file. Cloud updates in line with all Loqate data releases, usually two weeks after. If there are breaking changes at an API level, or any impact on load/response times, we’d hold the release.
A related point - our data teams are currently working through a long term project to create a single hierarchical view for all country data sources. We don’t have a revised roadmap handy, but I do know that FIN, CHE are live, and USA, DEU, SWE are all in progress now. Western Europe is a priority, so NLD should be close behind. This means we’ll be able to update data on a more frequent/structured basis.
A curated process for handling our internal reference data. It will enhance our information and match rates and will make our data better than any of our competitors.