throbber
Spatially Enhancing Business Data with
`Geocoding Solutions
`
`A MapInfo White Paper
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 001
`
`

`

`Geocoding Solutions
`
`2
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 002
`
`

`

`Geocoding Solutions
`
`3
`
`Contents
`
`Overview…………………………………….…………………………………4
`Three Geocoding Approaches…………….……………………………….4
`Geocoding on the Desktop.................................................................5
`Client/Server Geocoding ....................................................................5
`Server-only Geocoding.......................................................................7
`Important Geocoding Features................................ ............................. 8
`Batch or Interactive Processing..........................................................8
`Accuracy Levels .................................................................................9
`Intelligent Data Cleaning ....................................................................9
`Reliable Matching...............................................................................9
`MapMarker: The MapInfo Geocoding Solution…………………...……11
`Customizable Programming Interface .............................................. 11
`MapMarker Accuracy Level Options................................................. 12
`Current, Refreshed Base Data ......................................................... 13
`Conclusions ................................ ................................ ......................... 13
`Glossary of Terms…………………………………………………………..14
`About MapInfo................................ ................................ ...... Back Cover
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 003
`
`

`

`Geocoding Solutions
`
`4
`
`Overview
`
`• • Use geography to
`uncover hidden
`relationships
`among business
`data
`
`• • Street address-
`level geocoding
`meets the spatial
`enhancement
`needs of most
`businesses
`
`Using geography and maps to illustrate geographic relationships among business data is
`important for businesses that want to maximize the hidden potential of their data.
`Mapping and spatial analysis reveals the trends, patterns and opportunities that otherwise
`are lost when sifting through huge databases of information. In order to take advantage
`of the power of mapping and spatial analysis, data must first be enhanced through
`geocoding.
`Geocoding is the process of assigning latitude and longitude coordinates to data. Most
`business data contains a geographic component such as an address or a ZIP Code(cid:226) , and
`a geocoder simply codifies that component to allow spatial analysis or visual display of
`the information on a map.
`Geocoders, like most business software solutions, come in various formats—each with
`numerous capabilities and differing levels of effectiveness. Some are stand-alone
`solutions that allow businesses to geocode large database files, while others come
`included in mapping packages and are ideal for the individual analyst working with local
`data. Most businesses that want to exploit the spatial attributes of their business data will
`find that street-address level geocoding meets their needs. Others may need to geocode
`to less specific levels, such as state boundaries, county boundaries or ZIP Code centroid.
`All geocoders, regardless of how they are packaged, allow users to exploit the spatial
`component of their data, so organizations that are considering a geocoding investment
`must evaluate what type of geocoding approach best fits their infrastructure and which
`geocoding features address their business needs.
`
`Three Approaches to Address Geocoding
`
`When considering the implementation of a geocoding solution, a business must choose a
`geocoder that allows them to leverage the way they already do business rather than one
`that requires them to adapt to new processes. This paper presents three distinct
`geocoding approaches. A business can choose to implement one or
`all of the following geocoding methods, which are differentiated by whether the
`geocoding engine is provided via a server or resides on the desktop, as determined by
`specific spatial enhancement needs.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 004
`
`

`

`Geocoding Solutions
`
`5
`
`Geocoding on the Desktop
`
`• • Geocoders can
`come included in
`end-user mapping
`applications
`or can be
`implemented
`as stand-alone
`solutions
`
`Traditional desktop mapping applications, such as market analysis or site selection
`applications, rely on an end-user geocoding scenario—whether it is bundled into the
`application or a stand-alone solution—where all work is done on the individual
`computer. Users determine which data is to be geocoded by choosing the desired
`data table, and the geocoder assigns latitude and longitude coordinates to those
`records for placement on a map in the mapping application. The user stores the
`geocoded table on the desktop for future reference and use.
`
`Geocoding Engine
`Geocoding Engine
`
`Geocoding requests
`
`Geocoded Data
`
`Geocoders that are included in mapping packages often require that data be
`translated into a specific format before it is geocoded, but the process can be
`unwieldy for organizations that rely on
`prior investments in large databases. A
`stand-alone solution is more practical
`for businesses that want to geocode
`large volumes of data. Businesses that
`want to geocode their pre-existing
`databases should consider a stand-alone
`geocoding package that features open
`database connectivity (ODBC), so users
`can easily geocode large volumes of pre-
`existing data without first having to
`translate their data into another format.
`Users of this type of geocoding approach
`can geocode data in batch mode for quick
`processing or in interactive mode to
`leverage the user’s localized knowledge of a specific geographic area. When operating
`interactively, the geocoder requests the user’s input for hard-to-match addresses in order
`to increase the hit rate—the chance that the records are matched to the correct
`geographic areas on a map.
`
`Geocoder Interface
`
`Desktop Computer
`
`In the stand-alone geocoding scenario, all work is done on the individual
`computer, where all software, data and geocoded records are stored.
`
`Client/Server Geocoding
`In the client/server geocoding approach, the geocoding work is done by a server, rather
`than the standalone geocoder or mapping application on the desktop. Requests of the
`server are made via a “thin client”, such as an OCX (embedded object), Active X
`application, or any application created in an integrated development environment. This
`approach allows geocoding to be distributed to several users throughout an organization
`without having to purchase or program a geocoding or mapping application for each
`user. Geocoding is an adjunct function to the application with which the user is actually
`working—the primary client application is programmed to access the geocoding
`function when it recognizes a geographic component (i.e., an address).
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 005
`
`

`

`Geocoding Solutions
`
`6
`
`• • Client/Server
`Geocoding
`implementations
`allow enterprise-
`wide information
`sharing for the
`ideal network
`solution
`
`Client Computer running
`Visual Basic Application
`
`Client Computer running
`PowerBuilder Application
`
`Client Computer running
`C Program
`
`OLE Automation API
`OLE Automation API
`
`OLE Automation API
`OLE Automation API
`
`Geocoding OCX
`Geocoding OCX
`
`Geocoding OCX
`Geocoding OCX
`
`This approach is ideal for an Intranet/Internet geocoding solution, allowing several users
`access to data simultaneously. A Web browser or custom-designed interface facilitates
`communication between the users and the geocoding server. For instance, an
`Emergency 911 application is designed to allow operators to visualize address locations
`when fielding emergency calls, but the location of the caller must be geocoded before it
`appears on a map. In the client/server approach, the information is automatically
`geocoded by the server when the caller’s location is typed into the desktop computer.
`The client/server approach
`places control over address-
`based data and any resulting
`geocoded results into the
`hands of developers. A
`developer who wants to
`provide a user with a
`specific geocoding function
`using an OCX, for example,
`can determine exactly what
`the application does once it
`geocodes a record. Since an
`OCX supports an OLE
`automation interface, the
`programmer can design it to
`automatically pass the
`record to the geocoding
`server when data is entered
`into the system by the user,
`pass the geocoded
`information back to the
`OCX, and display the
`information
`on a map at a specific
`Developers can choose to implement geocoding as a client/server solution, depending upon
`predetermined zoom level.
`their organizations’ level of needs. A flexible API allows programmatic control over geocoding
`In the above example, the
`functionality.
`911 operator would simply type in an address location and would receive a map
`display of the area, based on predetermined criteria programmed by the
`application developer.
`
`RPC over TCP/IP
`
`RPC API
`RPC API
`
`Geocoding Server
`Geocoding Server
`
`C API
`C API
`
`Geocoding Engine
`Geocoding Engine
`
`Server Computer
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 006
`
`

`

`Geocoding Solutions
`
`7
`
`• • Server-only
`Geocoding
`automatically
`attaches spatial
`data to
`information from
`several disparate
`sources
`
`When operating in a server implementation, geocoding software and data, as well as add-
`on data such as demographics, can be maintained and updated with no effect on the
`individual user. The client/server approach to geocoding is easy for developers to set up
`and allows more centralized programmatic control.
`
`Server-only Geocoding
`In the server-only approach, geocoding is integrated into the business data-entry process.
`The user enters or updates records through a corporate database that are then
`automatically geocoded by the server, with no user interaction. Whenever a user enters a
`record that contains an address, it is geocoded by the server and stored in the database.
`This server-only approach is accomplished using an embedded module that is
`programmed to recognize any records entered by the user containing a geographic
`component, query the geocoding server, and assign coordinates to the information. This
`implementation differs from the client/server approach in that there is no client
`application. That is, the user does not receive any geocoded information back from the
`server to a desktop application. This approach can be thought of as “application
`neutral”; many different types of applications could simultaneously enter or update rows
`in the database—even in the same data table—and every input would be automatically
`geocoded. The data is simply entered into the corporate database as a row, where it is
`then automatically assigned geographic coordinates. It is accessed and managed as any
`other corporate data would be—it has simply been appended to reflect its spatial
`component.
`
`Data containing
`geographic
`components
`
`Geocoding module
`Geocoding module
`
`Database
`
`GUI
`
`Data
`
`Server computer
`
`Input data
`
`Input data
`
`Input data
`
`In a server-only implementation, the embedded geocoding module detects input data
`containing geographic components (e.g., address or ZIP Code) and geocodes it before
`storing it in the corporate database
`
`In situations that require
`geocoding of one row of records
`at a time, such as point-of-sale
`(POS) geocoding of customer
`addresses, this approach is the
`most practical. It is the preferred
`method for businesses that want
`to distribute geocoding capability
`to several clients throughout an
`organization, such as
`POS registers, without
`compromising data integrity.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 007
`
`

`

`Geocoding Solutions
`
`8
`
`Batch geocoding is an important feature in this approach as it is in the end-user
`approach: before specifying that every insert or update be geocoded, a business would
`likely want to batch geocode its existing records. An ODBC server implementation of
`geocoding would allow a business to add a spatial column to
`all of its core data in one step on the server.
`
`Important Geocoding Features
`
`When considering a geocoding solution, a business must consider which geocoding
`approach will best fit its data analysis needs. Cost, ease of development and
`implementation, and customizability are all important aspects to take into account. In
`addition there are several vital features that a geocoder should offer, regardless of the
`approach an organization decides to take.
`
`Batch or Interactive Processing
`Users should be given the option to geocode large batches of data in one step or
`interactively. In batch mode, a geocoder will assign spatial coordinates to groups
`of records according to
`predetermined criteria, such as street-
`level address or ZIP Code centroid.
`The user sets the default criteria, and
`the geocoder does all the work. In
`interactive mode, the geocoder asks
`for the user’s input to geocode hard-
`to-match addresses. Interactive
`processing may be more time-
`consuming, but, by notifying the user
`whenever it fails to match a record,
`the geocoder working in interactive
`processing mode improves the hit
`rate to ensure that all business
`records are properly placed on a map.
`
`Users can choose whether to geocode in batch mode or interactively, and decide
`whether to match records to street address or ZIP Code level.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 008
`
`

`

`Geocoding Solutions
`
`9
`
`• • Options increase
`match accuracy
`by letting the
`user determine
`the desired level
`of geocoding
`
`• • A comprehensive
`and current
`address
`dictionary allows
`the geocoder to
`clean dirty data
`and correct data-
`entry errors
`
`• • Frequent updates
`of base data
`improve address
`matching
`reliability
`
`Accuracy Levels
`Of course, it is important that a geocoder be accurate, but some geocoding instances do
`not require exact street-level address matching. A geocoder using TIGER data, for
`example, can locate geographic positions to within 167 feet, but this level of accuracy
`may not always be necessary. In market analysis applications, for instance, where
`demographic information could be aggregated to a generalized geographic area, a user
`may not need to map exact addresses. To ensure accuracy to the proper geographic level
`(i.e., street address, ZIP+4, ZIP Code, etc.), a geocoder should offer its users the ability
`to choose the desired level of accuracy. The wider the geographic area chosen by the
`user, the higher the hit rate will be. In any geographic analysis scenario, a geocoder that
`attaches US Census information to the various aggregate levels of data allows for
`demographic analysis at US Census levels.
`
`Intelligent Data Cleaning
`Data containing errors—called “bad” or “dirty” data—can present problems for some
`geocoders. Errors can result from various causes, such as poor reporting of information
`or typos in the data entry process. For instance, a record could be erroneously input as
`“1 Maine Street” instead of “1 Main Street”. A geocoder that cleans data intelligently
`would first check its address dictionary to see if there is indeed a Maine Street and/or a
`Main Street, then check for actual addresses before assigning coordinates to the record.
`The geocoder may find, for instance, that Maine Street does not exist, but there is a Main
`Street. The address would then be geocoded to the proper place. Clean address data is
`vital in any direct mail operation, such as billing and marketing, and a good geocoder will
`clean the data to meet CASS-certification standards, so it is deliverable according to
`USPS standards and eligible for volume discount postage pricing.
`The same intelligence would correct improper information such as the use of “Av.”
`instead of “Ave.”, or “Rd.” instead of “Ave.”, etc. An intelligent geocoder will not only
`correct typos, but will also decipher alternative spellings (e.g., Foxborough/Foxboro) and
`names (e.g., Manhattan/New York City), eliminate extraneous words, and search for
`correct ZIP Codes where numbers may have been transposed or omitted.
`
`Reliable Matching
`The process of comparing and matching entered records to a geographic profile is based
`on statistical probability, so a good geocoder matches input data to actual address
`information based on the probability that what is entered into the system represents a
`real-world location. This can be especially difficult in areas that are experiencing high
`growth and development. The geocoder, then, must be equipped with current,
`comprehensive address data—the same type of data used by the USPS, which updates its
`data monthly. The quality of the geocoder’s base data and the frequency with which it is
`updated is a major variable in the quality of a geocoding package.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 009
`
`

`

`Geocoding Solutions
`
`10
`
`Intelligent data cleaning and interactive processing minimize false positive matches by checking
`input records against an address dictionary and requesting user input for hard-to-match
`addresses.
`
`Though no geocoder can match 100% of addresses, complete and updated data
`minimizes the chance that
`an input record would be
`matched to an incorrect
`location—called a false
`positive match—which often
`occurs when an address
`dictionary is incomplete or
`outdated. In the previous
`example, Maine St. could
`be a newly constructed
`street, but a geocoder with
`an incomplete or outdated
`address dictionary trying to
`match the entry “1 Maine
`St.” could return a false
`positive match of “1 Main
`St.” even though both
`streets exist in the area.
`That is, the geocoder
`reflects a match, though an
`incorrect one. If the
`address dictionary had been
`updated, the record would
`
`have been plotted to the correct address.
`If no exact match can be found, a good geocoder will conduct a “fuzzy” search, where
`nearby localities will be searched to see if the address exists in a neighboring town or
`similar ZIP Code area. For instance, in the example above, if neither Main St. nor Maine
`St. existed in the prescribed ZIP Code area, the geocoder will look in nearby ZIP Codes
`for a match. The intelligent matching process improves the hit rate of the geocoder; that
`is, the more reliable the address dictionary, the higher probability that the address will be
`mapped.
`A geocoder should also allow users to choose whether to use a built-in address dictionary
`or their own data. A user may have perfect up-to-date address information about their
`localized area which would prove more reliable than
`US Census or USPS data. For instance, a user of a one-hour delivery application
`attempting to deliver a package to 1 Maine St. in the above example may not find Maine
`St. in the geocoder’s address dictionary, but may find it in their own updated data. The
`user who cannot choose between the address dictionary and their own data would not be
`able to geocode to the correct location, thereby decreasing the chance of delivering the
`package on time. Similarly, the geocoder’s address dictionary should be extensible. That is,
`the user should be able to insert such street additions as well as update name changes in
`the address dictionary without having to wait for update releases.
`
`• • Fuzzy searches
`increase the
`geocoder’s hit
`rate
`
`• • An extensible
`address
`dictionary allows
`users to update
`base data with
`new or revised
`information
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 010
`
`

`

`Geocoding Solutions
`
`11
`
`MapMarker – The MapInfo Geocoding Solution
`
`MapMarker is the premier geocoding solution from MapInfo that includes all the
`important features and functions of a complete geocoder. MapMarker is available as a
`Windows DLL or UNIX(cid:226) Shared Library, and can run on Windows(cid:226) 95, Windows NT(cid:226)
`and Sun(cid:226) platforms.
`
`Web Browser
`
`Web Server
`Web Server
`
`MapMarker OCX
`MapMarker OCX
`
`CGI Program Instance
`CGI Program Instance
`
`MapMarker OCX
`MapMarker OCX
`
`CGI Program Instance
`
`MapMarker OCX
`MapMarker OCX
`
`CGI Program Instance
`CGI Program Instance
`
`Customizable Programming Interface
`MapMarker offers a flexible application programming interface (API) for custom
`development that allows programmers to create a geocoding solution that fits individual
`business needs. For a specific
`desktop geocoding solution, the
`MapMarker C API allows developers
`to create a client program for full
`control over geocoding functionality.
`MapMarker v3.0 supports ODBC, so
`business users can geocode and store
`data tables on the desktop directly
`from their Oracle(cid:226) , MS Access,
`Sybase(cid:226) or Informix(cid:226) database. And
`with batch or interactive processing,
`the user
`can choose whether to geocode
`thousands of records in one pass
`or one record at a time.
`MapMarker can also be set up to
`operate as an enterprise network or
`Internet/intranet application.
`
`MapMarker Geocoding Engine
`MapMarker Geocoding Engine
`
`MapMarker Server
`MapMarker Server
`
`MapMarker can be implemented as an OCX to allow a true Internet/intranet
`geocoding solution
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 011
`
`

`

`Geocoding Solutions
`
`12
`
`• • Flexible API
`allows
`development of
`custom stand-
`alone,
`client/server or
`server-only
`geocoding
`solutions
`
`MapMarker is available as an OCX, so it can communicate via an OLE Automation
`API. This way it works as an object embedded in a client program created using any
`integrated development environment, such as PowerBuilder, Visual Basic or Delphi. The
`MapMarker OCX allows more client flexibility while decreasing set-up time and cost by
`allowing developers to create a solution using familiar programming languages. In
`addition, the MapMarker OCX can often be used straight out of the box, precluding the
`need for any programming at all.
`For a server implementation, the geocoding power of MapMarker is available as the
`MapInfo Geocoding DataBlade module, which allows businesses to geocode all their
`data stored on the INFORMIX-Universal Server. With the MapInfo Geocoding
`DataBlade module, developers can incorporate the geocoding process as a standard part
`of their data entry process, speeding up the geocoding process. Geocoded data is also
`stored on the INFORMIX-Universal Server, and managed along with the rest of a
`business’ core data.
`
`MapMarker Accuracy Level Options
`MapMarker matches data to street address, ZIP+4 or ZIP Code level, depending upon
`specific business needs. Complete with display maps, MapMarker uses current US
`Census information and refreshed TIGER data to geocode business data to user-
`specified criteria. MapMarker
`Plus is enhanced with Business
`Location Research (BLR)
`street-level data for
`applications requiring extreme
`accuracy, such as overnight
`routing. For applications
`where street-level matching is
`not necessary, such as market
`analysis applications,
`MapMarker ZIP+4 is the
`perfect choice for spotting
`aggregate data trends.
`
`MapMarker matches records to street address, ZIP+4 and ZIP Code levels for accurate
`geocoding. Geocoded points can then be placed on a map and analyzed spatially.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 012
`
`

`

`Geocoding Solutions
`
`13
`
`• • Bi-monthly
`updates of the
`MapMarker
`address
`dictionary
`ensures data is
`always accurate
`
`Conclusions
`
`• • MapMarker is the
`complete
`geocoding
`solution from
`MapInfo
`Corporation
`
`Current, Refreshed Base Data
`MapMarker offers a refreshed address dictionary, so business data will be geocoded
`using 1996 USPS data and ZIP+4 locations from Geographic Data Technologies
`(GDT). With the MapMarker Maintenance program, data will be updated on a bi-
`monthly basis to keep up with USPS changes and to ensure CASS-certification of
`addresses in corporate databases.
`
`Geocoding is the first step in the spatial enhancement of business data. A geocoding
`solution can be implemented as a desktop, client/server or server-only solution,
`depending upon the specific needs of a business. MapMarker from MapInfo
`Corporation is the complete geocoding solution that offers businesses the flexibility of
`each of these implementations while allowing the user to geocode large files of data in
`batch mode or interactively. The MapMarker extensible address dictionary is refreshed
`bi-monthly, providing current data for improved accuracy. With options like MapMarker
`ZIP+4 and MapMarker Plus, users needing various types and levels of geocoding are
`assured of the most complete, reliable geocoding solution on the market.
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 013
`
`

`

`Geocoding Solutions
`
`14
`
`Glossary of Terms
`
`• Address dictionary: the base data set containing USPS address information used
`in a geocoding solution
`
`• Batch processing: in geocoding, assigning coordinates to all records in large data
`files in one pass
`
`• Dirty data: data containing errors (e.g., misspellings, omissions, transposed
`numbers, etc.)
`
`• Extensible address dictionary: allows insertion and storage of new, revised and
`updated address information
`
`• False positive: input record matched to an incorrect location
`
`• Fuzzy search: in geocoding, searching nearby localities for unmatched addresses
`
`• Geocoding: the process of attaching longitude and latitude coordinates to data;
`spatial enhancement
`
`• Hit rate: the percentage of input records matched to a geographic location
`
`•
`
`•
`
`Interactive processing: in geocoding, assigning coordinates to hard-to-match
`individual records based on user-defined criteria
`
`Intelligent data cleaning: in the address matching process, the act of comparing
`input data to an address dictionary in order to minimize unmatched and false
`positive matches
`
`• Matching: in geocoding, the process of comparing input records to a geographic
`profile and assigning to a geographic location
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 014
`
`

`

`Geocoding Solutions
`
`15
`
`About MapInfo
`
`MapInfo Corporation, headquartered in Troy, New York, is the worldwide leader in
`business mapping solutions. The company’s products are available on desktop systems,
`servers, network systems including the Internet and intranets, and as the mapping object
`in Microsoft Office. Nearly 200,000 users in virtually every industry use MapInfo
`software to organize, manage, visualize and analyze information for decision-making.
`The software has been translated into 18 languages and is sold in 58 countries through
`multiple distribution channels. MapInfo Corporation is on the World Wide Web at
`http://www.mapinfo.com.
`
`HEADQUARTERS
`MapInfo Corporation
`One Global View
`Troy, New York 12180-8399
`U.S.A.
`
`
`
` 518.285.6000
`Tel:
` 518.285.6060
`Fax:
` 1.800.327.8627
`Sales:
`Federal Sales: 1.800.619.2333
`Sales Fax:
` 518.285.6070
`Cust. Support: 1.800.552.2511
`http://www.mapinfo.com
`
`EUROPEAN
`MapInfo Limited
`Contennial Court
`Easthampstead Road
`Bracknell
`Berkshire RG12 1YQ
`England
`
`Tel: 44.1344.482888
`Fax: 44.1344.482777
`
` GERMANY
`
` MapInfo GmbH
` Auf der Krautweide 32
` 65812 Bad Soden
`
` Germany
`
`
` Tel: 49.6196.67000
` Fax: 49.6196.670011
`
`
`JAPAN
`MapInfo (Japan) Corporation
`Suite 405
`
`AIOS Gotanda Building
`1-10-7 Higashi-Gotanda
`Shinagawa-Ku
`
`Tokyo141
`Japan
`
`
`
`
`
`Tel: 81.3.3440.8610
`Fax: 81.3.3440.8620
`
`AUSTRALIA
`MapInfo Australia Pty Ltd
`Level 4
`170 Pacific Highway
`Greenwich NSW 2065
`Australia
`
`Tel: 61.2.437.6255
`Fax: 61.2.439.1773
`
`All rights reserved. MapInfo, MapMarker and the MapInfo logo are registered trademarks of MapInfo Corporation in the United States. All
`other marks, trademarks and registered trademarks are the property of their respective holders.
` 81088 2/97
`
`(cid:211) 1997 MapInfo Corporation
`
`1.800.327.8627
`
`WhatsApp LLC
`Exhibit 1020
`Page 015
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket