MultiNet Address Points User Guide Topic Map - MTC...

© 2014 TomTom Global Content BV and TomTom North America, Inc. All rights reserved.

TomTom has prepared this document for use by its personnel, licensees, customers, and prospective customers. The information contained herein is strictly confidential, shall remain the property of TomTom and may be used only in accordance with the terms of a valid license agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of TomTom.

TomTom reserves the right to modify or revise all or parts of this document. The products described in this document are furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement.

TomTom North America, Inc. is a wholly-owned subsidiary of TomTom Global Content BV. TomTom®, MultiNet® and the TomTom logo are trademarks of TomTom Global Content BV or its affiliated companies. All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners and are hereby recognized.

U.S. GOVERNMENT RESTRICTED RIGHTS

Use, duplication, reproduction, release, modification, disclosure, or transfer of this commercial product and accompanying documentation is restricted in accordance with FAR 12.212, DFAR 227.7202, and by a license agreement. For the purpose of any public disclosure provision under any federal, state, or local law, it is agreed that the product is a trade secret and a proprietary commercial product and not subject to disclosure. The contractor/manufacturer is TomTom North America, Inc., 11 Lafayette Street, Lebanon, NH 03766. Phone 603.643.0330.

| Contents | 2

(c)2014 TomTom Global Content BV and TomTom North America, Inc. All rights reserved.

Contents

User Guide Change Overview..............................................................................................................................4Introduction........................................................................................................................................................... 4

Intended Audience.................................................................................................................................... 4Navigating Within This Document.......................................................................................................... 4Product Description.................................................................................................................................. 4

Understanding Address Points..............................................................................................................................6General Product Rules..............................................................................................................................6Data Models..............................................................................................................................................7Understanding Address Points in This Product....................................................................................... 7Understanding Relationships in This Product........................................................................................12Understanding Addresses in This Product............................................................................................. 15

Building an Address........................................................................................................................................... 18AT to ATAD - (Anchor Point to Address)............................................................................................18ATAD to ATAC (Address to Address Component Set)........................................................................19ATAD to ATCF - (Address to Component Format)............................................................................. 20ATAC to ATNC (Address Component Set to Name Component)........................................................21

Frequently Asked Questions...............................................................................................................................21Q1: What are some advantages of using the Address Point product?................................................... 21Q2: Do Entry Points have addresses?....................................................................................................22Q3: In some countries, there are only Building and Entry anchor point types. Is this true of all

countries?...........................................................................................................................................22Q4: Can multiple addresses be stored for one location?....................................................................... 22Q5: Can there be multiple anchor points associated with one location?............................................... 22Q6: Why is there a difference between the MultiNet POI 1.8 spatial locations and the MultiNet

Address Point spatial locations for the same address?.....................................................................23Q7: How can the Geocoding Accuracy Levels (GALs) be used in the Address Point product?............24Q8: What is the added value of the Shapefile *atte file?...................................................................... 24Q9: Is there any way to reduce the size of the Address Point product?................................................ 25

If You Need Help...............................................................................................................................................25Correction Policy.................................................................................................................................... 25Customer Support................................................................................................................................... 25Contact Information................................................................................................................................ 25

| MultiNet Address Points User Guide | 4


User Guide Change Overview

Version Date Description of Document Changes

1.0.0 2013.09 Initial Release

1.0.1 2014.09 Migrated document application from FrameMaker to Oxygen

Introduction

Intended Audience

This document was created for a broad range of users, from generalists to specialists. To fully understand MultiNet®

Address Points, the following documents are necessary:

• MultiNet Address Points 1.8 Specification;• MultiNet Address Points 1.8 User Guide;• MultiNet Address Points Product Release Notes.

Navigating Within This Document

For optimal use of the electronic version of this document, please activate the Adobe® PDF bookmarks function.

Hypertext links appear in underlined blue italic text.

References to other documents outside this user guide are not linked.

Product Description

This MultiNet® Address Points product enhances the MultiNet® product by allowing address matching (geocoding)to discrete points rather than to interpolated positions along street edges. In many cases, the resulting geocodedlocation will be superior because it is independent from edge ranges and their associated interpolation error. Eachaddress point is related to a street edge, which allows complete integration with the MultiNet products. Each releaseof MultiNet® Address Points is designed to be used with the MultiNet core data product of the same release.



Figure 1: Examples of Point Type - Building

Typical features of an Address Point contain:

• Unique and stable ID for each point, with the exception of Entry points1;• Address number; street name; locality; postal code; road element ID and side of associated street edge; and• Point types.

Note: In Shapefile format, associations between the *at.* feature table and several additional attributetables are necessary to retrieve all Address Point information. See the Shapefile UML model in theMultiNet Address Points 1.8 Specification for details.

1 In rare situations, an Entry point may have a stable ID.



Format Availability

MultiNet® Address Points is available in the following formats:

• GDF-AS• GDF-AR;• Shapefile; and• Oslfile.

For record layouts and full descriptions of these formats as they relate to this product, see:

• MultiNet Address Points 1.8 Specification.

For general information on these formats as they relate to MultiNet data, see:

• MultiNet GDF-AS Specification;• MultiNet GDF-AR Specification;• MultiNet Oracle (Oslfile) Specification; or• MultiNet Shapefile Specification.

The above documents should be included in your documentation.

Character Set

This product employs the UTF-8 character set. See UTF-8 in this user guide for more details.

Understanding Address Points

General Product Rules

The Geographic Coordinate System

A coordinate system is a reference system used to measure horizontal and vertical distances on a map. A coordinatesystem usually is defined by projection, spheroid of reference, datum, one or more standard parallels and a centralmeridian.

The data in this product uses a "geographic" coordinate system.

PROJECTION

Although not a true map projection, feature location in the "geographic projection" is based on a flat grid of latitudeand longitude coordinates.

DATUM

A datum is the 3-dimensional reference frame that is the basis for the coordinate systems upon which feature locationsare measured on the earth's surface. A datum is defined both by an ellipsoid that approximates the size and shapeof the Earth, and by parameters that specify the ellipsoid's orientation. This product references the World GeodeticSystem 1984 (WGS84) datum, a global datum that is the reference frame used by the Global Positioning System(GPS) satellites.

UNITS

The units of measurement in this product are decimal degrees.

PRECISION

Precision refers to the accuracy of the longitude and latitude degree units. The precision of the longitude and latitudedegrees in this product is seven decimal places (EXAMPLE: 41.4235341).

UTF-8

UTF-8 is the abbreviation for Unicode Transformation Format-8. UTF-8 is a variable-length character encoding forUnicode.



UTF-8 encodes each Unicode character as a variable number of 1 to 4 bytes, where the number of bytes depends onthe integer value assigned to the Unicode character. One byte is needed to encode the 128 US-ASCII characters. Twobytes are needed for characters from Greek, Cyrillic, Armenian, Hebrew, Arabic, Syriac and Thaana alphabets. Threeor four bytes are needed for Chinese and virtually all characters in common use.

The first byte of a multi-byte character sequence indicates the number of bytes in the sequence.

Data Models

All data models shown in this user guide are Shapefile representations.

Understanding Address Points in This Product

Address Points and "Anchor Points"

The term Address Point is actually a concept that refers to an "Anchor Point" (physical location) that is associatedwith an address (which is made up of address components).

Figure 2: Anchor Points

Anchor Point Types

There are seven point types in the Address Points product. All point types, with the exception of type 7 - Entry Point,are assigned globally unique and permanent point IDs.

Table 1: Anchor Point Types

Point Type Code Anchor Point Type Description

2 Address Range An anchor point type that supports an Address thatincludes a range of House Numbers that are onlyinternal to a building.

Note: U.S. and Canada only.

7 Entry Anchor Point type Entry represents either:

• a location on the navigable network based uponthe associated Address of an Anchor Point ofanother type (types 2, 11-15); or

• the location from where the Anchor Point can bereached.

In certain instances, these two locations can bedifferent.



Point Type Code Anchor Point Type Description

11 Address - Parcel Centroid A parcel polygon centroid.

12 Address - Parcel Access A location on the primary access road for aparcel, just immediately off the road Network, buttopologically connected to the road network feature.

13 Address - Parcel AccessDriveway

A point offset in a driveway at a distance from theroad network.

14 Address - Building A location that represents any aspect of a building,structure, monument or residence: i.e., its footprintcentroid; its front door location; or its alternate entryaccess location.

15 Address - Street Frontage A location 20m (meters) (65ft) from the streetcenterline and centered between property boundaries.

Anchor Point TypesAddress Range (2)

Note: U.S. and Canada only

The Anchor Point type Address Range is only available for U.S. and Canada data. It locates a single point thatrepresents a building with a house number range associated with it.

The point is located on a building.

The building must have a name.

In the graphic below, Carson Hall has a house number range of from 6000 to 6199.

Figure 3: Example of Anchor Point Type - Address Range

Entry points are manually entered and are associated with Address Range points. The Entry point represents access tothe most logical street network location.

Note: Address Ranges are entirely independent of any other Anchor Point addresses that are associated withRoad Elements.

Example: Anchor Point of type Address Range (2) that has a building name with an address range of 5200-5999could be located next to an Anchor Point of type Building (14) that has an address of 1209 Main Street.

Entry (7)

All Anchor Point types Entry on the navigable road network are always associated in a relationship with one of theother six point types and are always located on the road network. This relationship is referred to as Feature Associatedwith Anchor Point in the MultiNet Address Points 1.8 Specification document.



Figure 4: Example of an Entry Point (7) and Related Anchor Point Type Address - Building (14)

• Multiple Entry Points can be related to a single Point type;• Entry Points can be of type "Main" (attribute value = 1) or "Minor" (attribute value = 2);• There is a minimum of one "Main" Entry Point for each Point type;• Entry Points created during the production process do not receive a permanent Point ID.

Address - Parcel Centroid (11)

Anchor Point type Address - Parcel Centroid (11) represents a point on an assessor's parcel (tract or lot) polygon. Thex-y point, which comes from multiple sources, is used to determine the parcel centroid.

Figure 5: Example of Anchor Point Type Address - Parcel Centroid

Address - Parcel Access (12)

Anchor Point type Address - Parcel Access (12) represents a point located just off of the primary access road at aperpendicular distance from the main roadway.



Figure 6: Example of Anchor Point Type Address - Parcel Access (12)

Address - Parcel Access Driveway (13)

Anchor Point type Address - Parcel Access Driveway (13) represents a point that represents a location on thedriveway associated with a parcel and is just immediately off the network feature, but topologically connected to thenetwork feature.

Figure 7: Example of Anchor Point Type Address - Parcel Access Driveway (13)

Address - Building (14)

Anchor Point type Address - Building (14) indicates the front door location, alternate entry access location, or anyother aspect of a building, structure, monument or residence. An addressable structure is typically one that receivesmail or has telephone service.

• Usually, a residential address will consist of a single building. In the case of a house with outbuildings (detachedgarages, shed, barns, etc.), only the residence will have a structure point.

• Condominiums and duplexes are represented by multiple points for each building, as appropriate.• Larger buildings, such as apartment complexes, typically receive mail at one address for each building. Individual

apartments are not represented as discrete structure points.



• Shopping malls, industrial complexes and academic or medical center campuses are treated in the same manneras apartment complexes: if one building accepts mail for the entire complex, it is typically represented as onepoint. In cases where addresses are assigned to multiple buildings within one complex, each addressed structure isrepresented by a point.

See the figures here and here below for two examples of Anchor Point type Address - Building (14).

Figure 8: Example of Anchor Point Type Address - Building (14) Identifying Building Polygons

Figure 9: Example of Anchor Point Type Address - Building (14) Identifying an Entrance

Address - Street Frontage (15)

Anchor Point type Address - Street Frontage (15) represents a point that is offset approximately 20m (65ft) fromthe street centerline and centered between property boundaries. Street frontage points generally represent addresslocations more accurately than interpolated ranges.



Figure 10: Example of Point Type Address - Street Frontage (15)

Geocoding Accuracy Level

The Geocoding Accuracy Level represents a level of accuracy based on both the geocoding method applied and howwell the matching process linked the locational information of the Anchor Point to the base information in the map.

There are three geocoding matching processes that are applied in this product:

• Manually Placed - The location of the point was digitized or manually edited.• Forward Geocoded - The location of the point was determined using the addressing information provided with

the point against the addressing information available in the base map.• Reverse Geocoded - The location of the point was provided as a coordinate pair and the addressing information

of the point is used to link the point to the road network.

Please refer to the MultiNet Address Point 1.8 Specification for details of geocoding values and examples of thematching processes.

Understanding Relationships in This Product

There are two relationships associated with the MultiNet Address Points product:

• Anchor Point Along Transportation Element; and• Feature Associated with Anchor Point.



Figure 11: Anchor Point Relationships

Anchor Point Along Transportation Element

The Anchor Point Along Transportation Element relationship links an Anchor Point to a nearby Road Element basedon which side of the road element the point resides, and its relative position from the "From" junction end of the RoadElement.

• In Shapefile, the Relationship that associates points to the road network is the Anchor Point Along TransportationElement table (*atte.*).

• The direction of the road element used to determine the Entry Point position begins at the “From” Junction(F_JNCTID) location.

• In the *atte.* table, the position of the Entry Point along the associated network transportation element isdisplayed as a percentage with an implied precision of 3 decimal places in the REL_POS field.

Figure 12: Anchor Point Along Transportation Element Relationship

Figure 13: Anchor Point Along Transportation Element (*atte.*) Relationship Table Detail• The REL_POS value is 59600 in the *atte.* table above. This describes the feature point’s Entry Point position

along the associated transportation element as being 59.600% of the distance of the road element lengthbeginning at the F_JNCTID location.



The transportation element ID (TRPEL_ID) 11840000013271 is from the ID field of the *nw.* table found in thestandard MultiNet dataset.

This transportation element ID is linked to the Entry Point ID (PNT_ID) 118400073523698 in the *atte.* table.

By association via the *atat.* file, the transportation element ID then appears in the *at.* table as the value in theCLTRPELID field (closest tranportation element).

All Anchor Point types other than Entry Point (Address - Parcel Centroid, Address - Parcel Driveway, Address -Building, Address - Parcel Access, Address- Street Frontage, and for U.S. only: Address Range) require an EntryPoint Anchor Type. The Feature Associated with Anchor Point Relationship is a way to link Anchor Point type“Entry Point” to other Anchor Point features.

See Entry (7) earlier in this document for a graphic example and description.

Also see details on Relationships, UML models, GDF and Shapefile specifics and other topics in the MultiNetAddress Points 1.8 Specification.

Feature Associated with Anchor Point

The Feature Associated with Anchor Point Relationship is a way to link Anchor Point type "Entry Point" to otherAnchor Point features.

Figure 14: Feature Associated with Anchor Point Relationship

In the figure above:

• The blue dot represents a Point of type 11 (ANCH_TYPE = 11), a parcel centroid (See Address - Parcel Centroid(11)).

• It has a unique and permanent point ID (ANCHPNT_ID = 840100038337586);• The point ID (PNT_ID = 118400038337586) is unique and is used as a link to other attribute tables in the dataset;• The entry from the road network to reach the parcel centroid is indicated by another point (PNT_ID =

118400073523698). This point is of type 7 (ANCH_TYPE = 7), an entry point (See Entry (7)).

• In Shapefile, the Relationship that associates the entry points to the feature anchor points is the FeatureAssociated with Anchor Point table (*atat.*).

Figure 15: Feature Associated with Anchor Point (*atat.*) Relationship Table Detail• In the *atat.* table, the T_PNT_ID field contains the ID that represents the Entry Point and the F_PNT_ID

is the feature point it relates to. From the example above: F_PNT_ID = 118400038337586 (Feature Point);T_PNT_ID = 118400073523698 (Entry Point).

Also see details on Relationships, UML models, GDF and Shapefile specifics and other topics in the MultiNetAddress Points 1.8 Specification.



Understanding Addresses in This Product

Having defined anchor points, anchor point types and their relationships to link to entry points and to the MultiNetnetwork, the final piece of the Address Point product is the association of an actual address to these anchor points.

In order to represent a global address, the components of an address are presented in separate records. TomTomprovides information in these records and files to reconstruct these components in order to display addresses properlyfor each country’s address structure(s) and language(s).

• An address component is composed of component "types".• The way the component types are organized (their "scheme") will vary from country to country and sometimes

even within a country.• Each address is presented in at least one language. To aid in making the Address Point product global, an English

language version of the addresses is included in the delivery.

Figure 16: Connecting Addresses to Anchor Points in Shapefile

Address Structure

The following are necessary to build an address in the MultiNet Address Point 1.8 product:



Address (ATAD file in Shapefile): provides the addressing components in a given language that uniquely identifies alocation along the transportation network.

Address Scheme and Meta Information (ATCF file in Shapeflile): defines the complete structure of an Address. Itprovides the details of the Address Scheme implemented for each country including the Address Components labelsin all supported languages and indicates if an address component is mandatory or not.

Address Components (ATAC file in Shapefile): are the components necessary to build a complete Address.

Address Name Components (ATNC file in Shapefile): allows for further parsing of Address Components so theaddress component text can be subtyped (e.g., body, suffix, prefix).

Address Structure Example: Belgian Address Displayed in Dutch

Gretrystraat 531000 BrusselBelgië

Table 2: Example of Assigned Scheme to Belgian Address in Dutch

Scheme AddressComponentType Identifier

AddressComponentLabel

Address Value Row Position

25 5 Straatnaam Gretrystraat 1 1

25 6 Huisnummer 53 1 2

25 4 Postcode 1000 2 1

25 3 Woonplaats Brussel 2 2

25 1 Land België 3 1

Address Structure Example: Multiple Languages

In many countries, the addresses are presented in more than one language. In these cases, there will be separateaddress sets for the same address ID.

An address in Russian Latin:

Leytenanta 35236000 KaliningradRossiya

Table 3: Example of Assigned Scheme to Russian Address in Russian Latin

Scheme AddressComponentType Identifier

AddressComponentLabel

Address Value Row Position

37 5 Nazvaniye ulitsy Leytenanta 1 1

37 6 Nomer doma 35 1 2

37 4 Pochtovyy indeks 236000 2 1

37 3 Nazvaniyegoroda

Kaliningrad 2 2

37 1 Strana Rossiya 3 1

The same address in Russian:



Example of Assigned Scheme to Russian Address in Russian:

Note: Some countries use more than one scheme. This means that there could be different addresscomponents in an address or the components may have different mandatory or not mandatory attribution.

Please refer to the MultiNet Address Points 1.8 Specification for more details.

Names

Street address Names are broken into components in a similar way that Addresses are broken into components:an address name is comprised of component "types". Reconstruction of an address name is also accomplished byidentifying name types and how these types are displayed in the address.

Example: U.S. Name Components

The following address:

415 Columbia Street NEBellingham, WA 98714

would be broken into the following address components:

Table 4: Example of U.S. Address Components

Address ComponentLabel

Address Value Row Position Name ComponentID

Street Number 415 1 1 1001

Street Name Columbia Street NE 1 2 1002

Locality Bellingham 2 1 1003

State WA 2 2 1004

Postal Code 98714 2 3 1005

The street name would then be identified as follows:

Table 5: Example of Example of U.S. Name Components

NameComponent ID

Sequence Name Offset Name Length Name Type Text

1002 1 1 8 Body Columbia

1002 2 10 6 Suffix Street

1002 3 17 2 Post-Directional NE



For a full description of attributes and specifications of name components in this product, please refer to the MultiNetAddress Points 1.8 Specification for more details.

Building an AddressThe following example of building an address is shown using Shapefile files.

AT to ATAD - (Anchor Point to Address)



ATAD to ATAC (Address to Address Component Set)

Note: The ADDRESS_ID 643010010000628 in the atad table has two Address Sets. Each supportedLanguage in the delivery has its own set of address components.

Note: The Address Component Set table (atac) contains the address component text along with the associatedaddress component type for each component.

In the first example above,

• Address component type (COMP_TYPE) "1" = Country = Rossiya;• Address component type (COMP_TYPE) "3" = Place Name = Kaliningrad;• Address component type (COMP_TYPE) "4" = Postal Code = 236000;• Address component type (COMP_TYPE) "5" = Street Name = Leytenanta Yanalova ultsa;• Address component type (COMP_TYPE) "6" = House Number = 35.



ATAD to ATCF - (Address to Component Format)

Note:

• An Address Scheme provides the address formatting information and the labeling of the individual addresscomponents identified by the Address Scheme ID for a given Language Code within a given Country.

Using the row (ROW_NUM) and position (POS_NUM) information in the Component Format table (atcf), andapplying it to the text contained in the Address Component Set table (see ATAC portion of “ATAD to ATAC(Address to Address Component Set)” page), the Latin transcription (RUL) of the Russian address in this examplewould display as:

Leytenanta Yanalova ultsa 35 (Nazvaniye ultsy [Street] Nomer doma [House number])236000 Kaliningrad (Pochtovyy indeks [Postal Code] Nazvaniye goroda [Locality])Rossiya (Strana [Country])



ATAC to ATNC (Address Component Set to Name Component)

The Name Component table describes the text of each name component in terms of its exact position in an addressline and the name type(s) of the component.

The NAME_OFF indicates where the text starts in the address line and NAME_LEN indicates the length of the text.

Example 1: The NAMCOMP_ID of the Componet text Rossiya (16431000113500) uses two entries to identify twoname types (NAME_TYPE):

• 3 = Body;• 6 = Key.

Example 2: The NAMCOMP_ID of the Componet text Leytenanta Yanalova ulitsa (16431000119992) uses fourentries to describe three name types (NAME_TYPE):

• 4 = Suffix (for ulitsa, the text that begins at the 21st character space);• 6 = Key (for Leytenanta, the text that begins at the 1st character space);• 3 = Body (for Leytenanta, the text that begins at the 1st character space);• 7 = Surname (for Yanalova, the text that begins at the 12th character space).

Frequently Asked Questions

Q1: What are some advantages of using the Address Point product?

A:

• The Address Points product delivers a point feature representing an explicit location instead of through aninterpolation along street edges. As these points are derived from approved external sources, they can be expectedto provide more precise and meaningful locations for the objects they represent.



• In general, alpha-numeric house numbers don’t fit well into interpolation algorithms. Use of Address Points forthese cases is useful.

• If interpolated house numbers are not available for a road part, then Address Points could be used, when available,for this road part.

Q2: Do Entry Points have addresses?

A: Entry Points are allowed to have addresses, but the expectation is that they would rarely occur.

Q3: In some countries, there are only Building and Entry anchor point types. Is thistrue of all countries?

A: No. The content of the Address Point product varies from country to country or region to region depending uponsource data availability.

Q4: Can multiple addresses be stored for one location?

A: No. If there are multiple supported languages for an address, there can be multiple record entries for the sameaddress - one per language - but the address represents only one location.

Example: The following represents one and the same address with two sets of Address Components:

French representation:

53 Rue Gretry1000 Bruxelles, Belgique

Dutch representation:

Gretrystraat 531000 Brussel, België

Q5: Can there be multiple anchor points associated with one location?

A: Yes. Each anchor point type (other than Entry point) also has an associated Entry point. See figure below. Ananchor point type can be associated with one or more Entry points.



Figure 17: Bundestag in Berlin, Germany - Parliament Building

The figure above is an overhead view of the parliament building in Germany.

• The red circles represent the anchor point type Building, and• the black circles represent each anchor point’s entry point.

Q6: Why is there a difference between the MultiNet POI 1.8 spatial locations and theMultiNet Address Point spatial locations for the same address?

See example below.



Figure 18: Two Spatial Locations for the Same Address in Two MultiNet Products

A:

• The MultiNet POI 1.8 spatial locations are in most cases based on a geocoding process of interpolating the pointbased on the address range of the street part.

• The MultiNet Address Point product locates the actual physical locations of the address (e.g., building location).

Q7: How can the Geocoding Accuracy Levels (GALs) be used in the Address Pointproduct?

A: GAL levels of anchor point type “7” (Entry Point) carry useful information:

• Entry Point GAL value “1” = Manually placed and representing a highly accurate location.• Entry Point GAL value “99” = Automatically generated in the production process and generally representing a

less accurate location.

A: Some of the newer GAL levels introduced with the MultiNet Address Point 1.7 specification document version1.0.7 can also be of use for all Anchor Point types due to the reverse geocoding methods used:

• A GAL value of 18 (street match - L8 in the spec) indicates that the anchor point and the road element share thesame Street Name, but that the House Number is not within the range on the road element.

• A GAL value of 20 (nearest edge - L10 in the spec) indicates that the road element with the same street name wasnot within the search radius and it is just linked with a nearest edge.

Note: In Shapefile format, GALs are indicated in the GEO_CODE field of the *at file.

Q8: What is the added value of the Shapefile *atte file?

A: In the *at table, there is only one closest transportation element. If an Anchor Point has a relationship with morethan one road element, any of the other road elements than the one will be lost if not for the *atte file. The *atte tablelists all transportation elements to which an Anchor Point is linked.



Figure 19: *atte File Showing All Points Associated with One Transportation Element

Q9: Is there any way to reduce the size of the Address Point product?

A: One way to eliminate some Address Points is to filter out ones that were forward geocoded. These would be GALlevels: L1 - L5, L9 and L99. These GAL levels are interpolated and may have very limited added value for end users.

If You Need Help

Correction Policy

Our geographic data files are made as accurately as possible. If you find a problem, please contact us. All correctionsand problems are noted and examined as soon as possible. TomTom® makes every attempt to include any newinformation in the next product update.

Customer Support

If you have any questions about the files you have purchased, or are having difficulties with them, please callTomTom® Customer Support and have the following information available when you call:

• The product name and version number;• The product format you received;• The TomTom® Order Number (on the Packing Slip).

Contact Information

General Address

TomTom website address: www.tomtom.com/licensing

Global Content BV

E-mail address for Technical Support: [email protected]

TomTom North America, Inc.

E-mail address for Technical Support: [email protected]

Phone: 1-603-443-9260; or 1- 888-556-7160 (toll free US and Canada)

http://www.tomtom.com/licensing

mailto:%[email protected]

mailto:%[email protected]

Date post:	06-Mar-2018
Category:	Documents
Upload:	lynhu
View:	224 times
Download:	4 times

MultiNet Address Points User Guide Topic Map - MTC...

Documents