Geo addressing is Precisely's combination of three processes related to an address: address verification, geocoding, and the creation of a unique, persistent identifier (the PreciselyID). Geo addressing capabilities ensure that addresses found in the business data are verified, standardized, and cleaned for maximum accuracy.
Every address has two aspects: the address itself and where that address is located, the latitude/longitude, or geocode. For businesses, it is critical to get both right. An imprecise geocode or a bad address can increase risk, miss new opportunities, make fraud difficult to detect, and result in failed or repeat deliveries.
Precisely Data Integrity Suite offers different Geo Addressing services that can be used to convert physical addresses into geographic coordinates. These services include address validation, standardization, geocoding, and reverse geocoding.
- Global default:
https://api.cloud.precisely.com - Europe:
https://api.eu1.cloud.precisely.com - Australia:
https://api.au1.cloud.precisely.com - Great Britain:
https://api.gb1.cloud.precisely.com
With the Precisely Geo Addressing API, optimize application speed and manage your data's location by selecting the region where your requests are processed. We currently offer two options:
- US1 (Northern Virginia): This is the default region, ideal for US-based data and ensuring fast performance within the country.
- EU1 (Ireland): For data residing in Europe or requiring compliance with regional regulations, choose this region for secure and compliant processing.
- AU1 (Sydney): For data residing in Australia or requiring compliance with regional regulations, choose this region for secure and compliant processing.
- GB1 (London): For data residing in Great Britain or requiring compliance with regional regulations, choose this region for secure and compliant processing.
This currently extends to all Geo Addressing Services (Geocode, Verify, Address Autocomplete, Reverse Geocode and Lookup API).
New Vintage Management is now available exclusively with a premium dataset subscription,
providing access to both current and previous vintages for enhanced data continuity. The
Vintage Management support is implemented through a custom preference
DATA_VERSION which accepts value in YYYY-MM format. This will help
users to test and validate the new data refresh logic (version N) without impacting
existing integrations running on the current version (N-1) and will facilitate to
migrate to the new features at their own pace, ensuring a smooth transition and avoiding
disruptions to the business logic.
- If no custom preference is specified for
DATA_VERSION, the latest vintage will be used by default. - If the current month and year (e.g., 2024-09) are provided as a custom preference, the latest vintage will be returned.
- If a future month or year is provided in
DATA_VERSION, this will resolve in an error as the future months and years are not supported in theDATA_VERSIONparameter. For example, in September 2024, you cannot specify aDATA_VERSIONgreater than 2024-09. - The New Vintage Management is available exclusively with premium dataset subscription. Any user trying to access multi-vintage data with no access to premium dataset, will receive a 403 Forbidden error due to insufficient permissions.Note: New Vintage Management support is currently limited to the geocode and verify API when using the 'PREMIUM' dataset subscription (OPTION 3).