Presentation is loading. Please wait.

Presentation is loading. Please wait.

Table of Contents Introduction Example Value Proposition Architecture

Similar presentations


Presentation on theme: "Table of Contents Introduction Example Value Proposition Architecture"— Presentation transcript:

1

2 Table of Contents Introduction Example Value Proposition Architecture
Licensing and Installation

3 Introduction Address Geocode: The only on-premise worldwide geocoder
Is an addition to Address Verif Adds a latitude/longitude coordinates to addresses Covers all 240+ countries The only on-premise worldwide geocoder Keeps all operations within your company network Provides rooftop-level geocoding in 120 countries Geocoded addresses are automatically verified

4 Better Accuracy: Verify and Geocode Together
Bahia Blanca 4142 Villa Devoto C1419BAL ARG Unverified address data Bahía Blanca 4194 Villa Devoto C1419BAL Buenos Aires “Loqated” – with Loqate geocode Unverified addresses often have incomplete or inaccurate information. Thus, the geocodes aren’t always accurate. The combination of Address Verify (to verify) and Address Geocode (to geocode) results in accurate geocodes. In this case, the unverified address says Villa Devoto. One might assume that’s a city name. After the verification process, the address is found to be within Buenos Aires. In this case, the unverified address was missing the city name.

5 Value Proposition Avoid using multiple geocoders for multiple countries Simplify integration and field mapping Single worldwide geocoder integrated with Address Verify Dramatically improves analytics by using geocodes to show relative locations and clusters Verified addresses increase data utilization and accuracy Improved analytics Reduces total cost of ownership (TCO) through easy implementation and updating Fast and responsive software support and data acquisition Easy integration of geocoding into customer applications

6 P4 The GeoAccuracy Code 1. Verification Status 2. Geocoding Level
Transparent assessment of the geocode’s accuracy, and how it was computed Helps you determine if a geocode is accurate enough to use P4 1. Verification Status P: Point A single geocode was found matching the input address I: Interpolated A geocode was able to be interpolated from the input addresses location in a range A: Average Multiple candidate geocodes were found to match the input address, and an average of these was returned U: Unable to geocode A geocode was not able to be generated for the input address 2. Geocoding Level 4: Premise 3: Thoroughfare 2: Locality 1: AdministrativeArea 0: None Our GeoAccuracy code tells you how precise each geocode is, and how it was the computed. It’s made of two parts: The Verification Status and the Geocoding Level. We will explain the Verification status in more detail in the next slides. The geocoding level follows the same scheme as the Address Verification Code: a GL of 4 is a rooftop assigned to a specific building or rooftop. 3 is the geocode for a street 2 is the code for a city or town And 1 is for a state, department, prefecture, etc. P4 GAC means that the geocode has been verified to the point status and premise level geocoding. This is the most precise address verification that can be achieved.

7 Functional Architecture (Overview)
Modules Components Local API Cloud API C++ COUNTRY PARSE Address Verify REST SOAP ATOM MATCH Address Powersearch QUERY Address Geocode FORMAT This is a top level view of the Loqate architecture. At the left are the modules that perform most of the work: Parse divides the address into the correct fields, Match compares the field data to our reference data and corrects it, Format puts the output in the correct format for each country. In the middle are the components or Loqate solutions: Address Verify, Address Powersearch, and Address Geocode. Each of those solutions fills a specific function, yet they all rely on the modules that run underneath. The highest level of the architecture comprises the various APIs that connect the Loqate products to other applications. INDEX

8 Functional Architecture (Address Verify)
Modules Components Local API Cloud API C++ Address Verify COUNTRY PARSE REST SOAP ATOM MATCH Address Powersearch QUERY Address Geocode FORMAT Address Geocode appends latitude-longitude coordinates to validated addresses INDEX

9 Functional Architecture (Address Geocode)
LATITUDE/LONGITUDE (DECIMAL) GEOCODE ACCURACY CODE GEODISTANCE POINT MATCH INTERPOLATE/ AVERAGE Address Geocode uses the Address Verify output addresses as its input When an input address has an exact match in the reference data, we have a point match If there is no exact match, but we have multiple other addresses in the vicinity, a geocode will be computed for the input based on the geocodes of these adjacent addresses Each geocode is returned with two measures of accuracy: The GeoAccuracy Code (GAC) which we explained earlier, and the Geodistance. The Geodistance is the radius of the circle within which the geocode is located. The smaller the Geodistance, the more accurate the Geocode. Additional reading: VERIFY OUTPUT REFERENCE DATA ADDRESS

10 Loqate Eco-system Address Powersearch Address Verify Address Geocode
Instantaneous autocomplete Customer experience Address Verify Data quality Back End Large volume Address Geocode Mapping enablement Improved analytics Loqate’s address verification suite seeks to improve business throughout the pipeline. Three solutions are currently available. Address Powersearch targets user-facing applications to make address data entry a fast, intuitive, and accurate process. Address Verify verifies large batches of address data at a time to improve all business processes that rely on them. Address Geocode will takes verified address data, add geocodes and interface to a large range of mapping and analytics applications.

11 Licensing and Installation
Address Geocode is an addition to Address Verify. On-premise: You will need the Address Verify data pack for each country you wish to geocode Cloud: Address Geocode consumes the same amount of credits as Address Verify. However, it must always be accompanied by an Address Verify call.

12 About Loqate Loqate was founded in 2009
First product launched in Summer 2010 Founders – seasoned market veterans CEO founded Global Address in 1999 CTO was Chief Architect of Global Address Customer focused, flexible and responsive

13 AGDKV

14 GeoAccuracy Codes: Visualized
Point: The unique address 11 Main Street is confirmed to exist It is within 21 meters (68 feet) of a point in the global knowledge repository

15 GeoAccuracy Codes: Visualized
Interpolated: 13 Main Street does not have a match in the reference DB. However two addresses on the same street exist, on either side of it The engine assumes that 13 lies on a vector between them, less than 21 meters away from one or the other

16 GeoAccuracy Codes: Visualized
Average: 12 Main Street does not have a match in the reference DB. There are multiple reference points around it, but it is not assumed to lie on a direct vector between two adjacent points. 12 Main Street is assumed to be in the resulting polygon The engine returns the point but decreases its Geocoding level, and the polygon’s diagonal distance


Download ppt "Table of Contents Introduction Example Value Proposition Architecture"

Similar presentations


Ads by Google