envinsa data guide - pitney...

108
Envinsa® 2008.10 DATA GUIDE

Upload: vukhanh

Post on 26-Jun-2019

219 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Envinsa®

2008.10 DATA GUIDE

Page 2: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of MapInfo Corporation, One Global View, Troy, New York 12180-8399.© 2009 Pitney Bowes Software Inc. All rights reserved. MapInfo, the MapInfo logo and Envinsa are trademarks of MapInfo Corporation and/or its affiliates.Corporate Headquarters:Phone: 518 285 6000Fax: 518 285 6070Sales: 800 327 8627Government Sales: 800 619 2333Technical Support: 518 285 7283www.mapinfo.comUK and EMEA Headquarters:Phone: 44 1753 848200Fax: 44 1753 621140 Technical Support: 44 1753 848229 www.mapinfo.co.ukAsia Pacific Headquarters:Phone: 61 2 9437 6255Fax: 61 2 9439 1773Technical Support: 61 7 3844 7744www.mapinfo.com.auContact information for all offices is located at: www.mapinfo.com/contactus.Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark.February 6, 2009

Page 3: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Table of Contents

Chapter 1: Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Data Dependencies by Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Data Component List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Directory Tree Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Chapter 2: Administrative Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14World Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14World Capital Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Country Sub National Boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Country Second Sub National Boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Country Minor Division Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Municipality Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Administrative Boundaries for Multiple Countries . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Chapter 3: Street Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Extended Enhanced Address Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Street Intersections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Priority Implementation of Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Chapter 4: Map Display Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Display World Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Display Administrative Boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Label Municipal Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Display Urban Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Display Boundary Line Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Display A2 Centroid Point Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Display Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Generalized Display Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Highway Shields Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Display Landmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Display Gazetteer Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Railways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Ferries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Page 4: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Water Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Land Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 5: Postal Code Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Postal Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 6: Landmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Landmark Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 7: Gazetteer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Gazetteer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Appendix A: Glossary of Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65General Field Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Field Names that Apply Only to the Enhanced EAL . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Appendix B: miCodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Administrative Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Ferries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Land . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Landmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Railways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Settlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Water . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix C: Map Layer Display Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Layer Names and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98High Map Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Medium Map Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Low Map Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4 Envinsa

Page 5: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

1

Introduction

In this section:

Data Dependencies by Service . . . . . . . . . . . . . . . . . . . . . . .6Data Component List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Directory Tree Composition. . . . . . . . . . . . . . . . . . . . . . . . .10

Page 6: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Data Dependencies by Service

Data Dependencies by Service

The following table outlines the data dependencies that each service has.

* For US data this component is called GeocodeUS.** For US data Driving and Walking data components are combined and called Route data.

Note: The Presentation Service installs with a personal profile manager, called miProfiler. The miProfiler is a demonstration web application that manages profile information.

Service Dependent Data

Coordinate Geometry Service None

Coordinate System Transform Service None

Directory Service DemoData

Find Location Service CountrySub, CountryMinorSub, CountrySecSub, Municipality, PostalCode

Gateway Service None

Location Utility Service CountrySub, CountryMinorSub, CountrySecSub, Municipality, ExtendedStreet, StreetIntersection, Landmark, PostalCode, WorldBoundary, Geocode*

Presentation Service World Boundary, MapDisplay, DemoData

Map Tiling Service WorldBoundary, StreetIntersection, ExtendedStreet, Landmark

Presentation Service World Boundary, MapDisplay, DemoData

Profile Management Service Customer data (LDAP)

Route Service World Boundary, Driving **, Walking **

Web Feature Service DemoData

Web Map Service World Boundary, MapDisplay, DemoData

6 Envinsa

Page 7: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 1: Introduction

Data Component List

The size values provided in this list are for the U.S. and Canada data installed with each service. These values will vary depending on geography (North America versus Europe), and package version (sample data or full data).

Data Components include:

World Country

Description: Country boundaries of the world. This is used to identify distributions to use the World map with enhanced national boundaries to accommodate large scale data precision issues.

Table Name: wlda0

Package File: WorldBoundary.jar

Sample Component ID: WorldBoundary-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Country Minor Subdivision

Description: Minor administrative subdivisions. These are used to refine location.

Examples: • Minor Civil Division (MCD)• Census subdivision

Table Name: wnaa3

Package File: CountryMinorSub.jar

Sample Component ID: CountryMinorSub-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Country Subdivision

Description: First order subnational boundaries. For example, state or province boundaries. These are used to refine location.

Examples: • State• Province• Territory

Table Name: wnaa1

Package File: CountrySub.jar

Sample Component ID: CountrySub-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

2008.10 Data Guide 7

Page 8: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Data Component List

Country Secondary Subdivision

Description: Second order subnational boundaries. For example, county/census boundaries. These are used to refine location.

Examples: • County• Census division

Table name: wnaa2

Package File: CountrySecSub.jar

Sample Component ID: CountrySecSub-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Municipality

Description: City boundaries with inter-city areas. These are used to refine location.

Examples: • Minor Civil Division (MCD)• Census subdivisions

Table Name: wnaa4

Package File: Municipality.jar

Sample Component ID: Municipality-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Extended Street

Description: Street/road segments carrying administrative region and postal code information.The extended street table contains all named and addressed street segments tagged with country subdivision, secondary subdivision, minor subdivision, municipality and postal code information.

Table Name: wna_ex

Package File: ExtendStreet.jar

Sample Component ID: ExtendStreet-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Street Intersection

Description: Intersection points and cross streets. Each street intersection is tagged with up to five street names.

8 Envinsa

Page 9: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 1: Introduction

Table Name: wna_cr

Package File: StreetIntersection.jar

Sample Component ID: StreetIntersection-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Postal Code

Description: Postal code boundaries.

Examples: • Five Digit Zip codes• Forward Sortation Areas (FSA)

Table Name: wnapc

Package File: PostalCode.jar

Sample Component ID: PostalCode-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Landmark

Description: Landmarks and known places (including airports). Named places and prominent locations with names. There are two tables:• Gazetteer table: Contains named places• Landmarks table: Contains airports, buildings, monuments,

schools, recreational facilities, businesses, and institutions.

Table Name: Gazetteer table name – wnagz.Landmarks table name – wnalk.

Package File: Landmark.jar

Sample Component ID: Landmark-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

Routing Driving

Description: Routing roads.

Package File: Routing.Road.jar

Sample Component ID: Routing.Road-Envinsa-MapInfo-0040-0000-00-Data-0000000-0000

Geocoding Data

Description: Geocode data.

Package File: GeocodeXX.jar Note: XX represents the 2-letter country code.

Sample Component ID: Geocode-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000Geocode-Envinsa-MapInfo-0040-0001-00-USData-0000000-0000

2008.10 Data Guide 9

Page 10: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Directory Tree Composition

Directory Tree Composition

Composition of the directory tree for the installation of Envinsa data components.

The general configuration is:

<Envinsa_home>\DataDomain\<geography>

where <Envinsa_home> is the directory where Envinsa is installed.

Sample Directory Tree DistributionThe following is an example of what the directory tree may look like for North America:

DataDomain\CADataDomain\CA\GeocodeCADataDomain\CA\GeocodeCA\dataDataDomain\CA\GeocodeCA\libDataDomain\GlobalDataDomain\Global\GeocodeWorldDataDomain\Global\GeocodeWorld\dataDataDomain\Global\GeocodeWorld\data\<ISO_Country_Code>DataDomain\Global\GeocodeWorld\libDataDomain\Global\WorldBoundaryDataDomain\USDataDomain\US\GeocodeUSDataDomain\US\GeocodeUS\dataDataDomain\US\GeocodeUS\libDataDomain\US_CADataDomain\US_CA\CountryMinorSubDataDomain\US_CA\CountrySecSubDataDomain\US_CA\CountrySubDataDomain\US_CA\ExtendStreetDataDomain\US_CA\ExtendStreet\canDataDomain\US_CA\ExtendStreet\usaDataDomain\US_CA\ExtendStreet\usa\<State_Code>DataDomain\US_CA\Landmark

Map Display

Description: Complete street data and named maps – high, medium, and low resolution.

Package File: MapDisplay1.jar – streetsMapDisplay2.jar – transportMapDisplay3.jar – water

Sample Component ID: MapDisplay-Envinsa-MapInfo-0040-0001-00-Data-0000000-0000

10 Envinsa

Page 11: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 1: Introduction

DataDomain\US_CA\MapDisplayDataDomain\US_CA\MapDisplay\administrativeDataDomain\US_CA\MapDisplay\gazetteerDataDomain\US_CA\MapDisplay\landDataDomain\US_CA\MapDisplay\landmarksDataDomain\US_CA\MapDisplay\mdfDataDomain\US_CA\MapDisplay\mdfClassicDataDomain\US_CA\MapDisplay\shieldsDataDomain\US_CA\MapDisplay\streetsDataDomain\US_CA\MapDisplay\streets\canDataDomain\US_CA\MapDisplay\streets\usaDataDomain\US_CA\MapDisplay\streets\usa\<State_Code>DataDomain\US_CA\MapDisplay\transportationDataDomain\US_CA\MapDisplay\waterDataDomain\US_CA\MunicipalityDataDomain\US_CA\PostalCodeDataDomain\US_CA\Routing.PedestrianDataDomain\US_CA\Routing.Pedestrian\canadaDataDomain\US_CA\Routing.Pedestrian\centralDataDomain\US_CA\Routing.Pedestrian\midwestDataDomain\US_CA\Routing.Pedestrian\northeastDataDomain\US_CA\Routing.Pedestrian\pacificDataDomain\US_CA\Routing.Pedestrian\southDataDomain\US_CA\Routing.RoadDataDomain\US_CA\Routing.Road\canadaDataDomain\US_CA\Routing.Road\centralDataDomain\US_CA\Routing.Road\midwestDataDomain\US_CA\Routing.Road\northeastDataDomain\US_CA\Routing.Road\pacificDataDomain\US_CA\Routing.Road\southDataDomain\US_CA\StreetIntersectionDataDomain\US_CA\StreetIntersection\canDataDomain\US_CA\StreetIntersection\usa

2008.10 Data Guide 11

Page 12: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Directory Tree Composition

12 Envinsa

Page 13: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

2

Administrative Boundaries

Administrative boundaries are the official representation of the administrative hierarchy of a country.

The highest level is the World, which provides the boundaries of all the countries. Beneath this there are four levels of boundaries.

The first is the sub national division of a country. For example, in Australia or the U.S. this is a state; in Canada it is a province.

The next level is the first sub region administrative level of the sub national boundaries. For example, counties, kries, or arrondissements. The next two levels are the sub units of the second level boundaries. These can be townships, unitary authorities, or gemeinde. The first three levels provide a space-filling hierarchy of the geographic region.

The fourth level is municipalities, or urban areas. These are associated with geneinde or municipios that are more properly part of the level three boundaries. Depending on sources, urban areas may be arbitrarily defined highly populated areas or may be official incorporated city boundaries.

In this section:

Table Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . .14World Boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14World Capital Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . .15Country Sub National Boundaries . . . . . . . . . . . . . . . . . . .16Country Second Sub National Boundaries . . . . . . . . . . . .17Country Minor Division Boundaries . . . . . . . . . . . . . . . . . .19Municipality Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Administrative Boundaries for Multiple Countries . . . . . .22

Page 14: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Table Naming Conventions

Table Naming Conventions

This section describes the table naming conventions used in this chapter.

There is no ISO code for the earth (World), so WLD is used as the world code. A distribution is identified by its global hierarchy, starting with the World.

Country ISO codes are from the ISO standard. Individual countries follow Standard ISO three character country codes.

The following table describes non-ISO regions that use mi region codes.

World Boundaries

The world boundary table is a map of the world that has been selectively gridded to enhance locational search. All location services begin by searching a location for the identity of the country within which it is located. The target country of a distribution is modified with coastal areas buffered. This ensures that coordinate locations near shorelines are identified as being within a country.

Table StructureThe structure of the world boundaries table is as follows:

Region Code

World WLD

Europe WEU (W = World, EU = Europe)

Africa WAF (W = World, AF = Africa)

Asia WAS (W = World, AS = Asia)

Australia WAU (W = World, AU = Australia)

North America WNA (W = World, NA = North America)

South America WSA (W = World, SA = South America)

Field Description Type

Name(indexed)

Official country name. Char(45)

14 Envinsa

Page 15: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 2: Administrative Boundaries

Naming ConventionsThe name of the world boundaries table is:

World Capital Locations

There is, in conjunction with the world countries table for Location Utility Services, a non-mappable capital cities table.

Table StructureThe structure of the world capital cities table is as follows:

Name_en(indexed)

Country name in English. Char(45)

Name_fr Country name in French. Char(45)

Name_de Country name in German. Char(45)

A0_ISO(indexed)

ISO Country code. Char(2)

A0_ISO3 3 character ISO country code. Char(3)

SmartLabel Specially formatted version of the contents in the Name field. Char(45)

Priority Label Priority rank. All set to 1. SmallInt

miCode MapInfo internal feature code. Integer

Xcoord Longitude of the country’s capital city. Float

Ycoord Latitude of the country’s capital city. Float

Description Code

wld = Worlda0 = The A0 administrative level.

wlda0.tab

Field Description Type

Name(indexed)

Official country name. Char(45)

Field Description Type

2008.10 Data Guide 15

Page 16: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Country Sub National Boundaries

Naming ConventionsThe world Capital locations table name is:

Country Sub National Boundaries

This is the highest level of division within a country. This is a state in Australia, or a province in Canada.

Table StructureThe structure of the country sub national boundaries table is as follows:

Name_en(indexed)

Country name in English. Char(45)

Name_fr Country name in French. Char(45)

Name_de Country name in German. Char(45)

A0_ISO(indexed)

ISO Country code. Char(2)

A0_ISO3 3 character ISO country code. Char(3)

SmartLabel Specially formatted text of the contents of the Name field. Char(45)

Priority Label Priority rank. All set to 1. SmallInt

miCode MapInfo internal feature code. Integer

Xcoord Longitude of the capital city. Float

Ycoord Latitude of the capital city. Float

Description Code

wld = World p0 = The point locations for the A0 level.

wldp0.tab

Field Description Type

Name(indexed)

Full name. For example, state, province, bundesland. Char(40)

Field Description Type

16 Envinsa

Page 17: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 2: Administrative Boundaries

** Multiple languages are handled by added additional language fields and referencing these fields in the meta-data.xml file.

Naming ConventionsThe table naming convention is:

If a layer is defined by a seamless table, the base tables use a region abbreviation + _a1.tab and the seamless table is:

Country Second Sub National Boundaries

This is the level that makes up the Sub National country division. Some examples, depending on the country, are counties, kries, or arrondissements.

Nm_Lng 2 character ISO language code of the Name field. For example, en. Char(2)

Nm_Abbr(indexed)

Two character abbreviation. Char(2)

Nm_Code Official Code from country census or administrative agency. Char(2)

Name_en** Name of area in English (optional). Char(40)

A0_ISO(indexed)

ISO Country code. Char(2)

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo standard feature code Integer

Xcoord Longitude of sub national region capital Float

Ycoord Latitude of sub national region capital Float

Description Code

Country sub national boundaries <3 char country ISO code or mi region code> + a1.tab

Description Code

Country sub national boundaries <3 char country ISO code or mi region code> + _a1.tab

Field Description Type

2008.10 Data Guide 17

Page 18: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Country Second Sub National Boundaries

Table StructureThe structure of the country second sub national boundaries table is as follows:

** Multiple languages are handled by added additional language fields and referencing these fields in the meta-data.xml file.

Naming ConventionsThe table naming convention is:

Field Description Type

Name(indexed)

Full name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Nm_Abbr Abbreviation. Char(6)

Nm_Code Official code. Char(5)

Name_en** Name of area in English (optional). Char(40)

A1_Name(indexed)

Country sub national boundary full name. Char(25)

A1_Abbr(indexed)

Country sub national boundary two character abbreviation. Char(2)

A1_Code Country sub national boundary code. Char(2)

A0_ISO(indexed)

ISO Country code. Char(2)

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Xcoord Longitude of local administrative center. Float

Ycoord Latitude of local administrative center. Float

Description Code

Country secondary sub national boundaries.

<3 char country ISO code or mi region code> + a2.tab

18 Envinsa

Page 19: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 2: Administrative Boundaries

If a layer is defined by a seamless table, the base tables use a region abbreviation + _a2.tab and the seamless table is:

Country Minor Division Boundaries

The country minor division boundaries make up the country second sub national boundaries. Some examples, depending on the country are towns, communes, or gemeinde.

Table StructureThe structure of the country minor division boundaries table is as follows:

Description Code

Country secondary sub national boundaries.

<3 char country ISO code or mi region code> + _a2.tab

Field Description Type

Name(indexed)

Area full name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Nm_Code Official Code. Char(10)

Name_en** Name of area in English (optional). Char(40)

A2_Name(indexed)

Name of country secondary sub division level boundary within which the area is located.

Char(40)

A2_Abbr 4 character abbreviation for the country secondary sub division level boundary.

Char(6)

A2_Code Official code for country secondary sub division level boundary. Char(5)

A1_Name(indexed)

Country sub national boundary full name. Char(40)

A1_Abbr(indexed)

Country sub national boundary two character abbreviation. Char(2)

A1_Code Country sub national boundary official code. Char(2)

2008.10 Data Guide 19

Page 20: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Municipality Table

** Multiple languages are handled by added additional language fields and referencing these fields in the meta-data.xml file.

Naming ConventionsThe table naming convention is:

If a layer is defined by a seamless table, the base tables use a region abbreviation + _a3.tab and the seamless table is:

Municipality Table

The municipality table is composed of city boundaries with inter-city areas consisting of minor civil divisions or equivalent areas. Some examples, depending on the country, are stadteile, gemeente, and arrondissement.

A0_ISO(indexed)

ISO Country code. Char(2)

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Xcoord Longitude of local administrative center. Float

Ycoord Latitude of local administrative center. Float

Description Code

Country minor administrative boundaries.

<3 char country ISO code or mi region code> + a3.tab

Description Code

Country minor administrative boundaries.

<3 char country ISO code or mi region code> + _a3.tab

Field Description Type

20 Envinsa

Page 21: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 2: Administrative Boundaries

Table StructureThe structure of the municipality table is as follows:

** Multiple languages are handled by added additional language fields and referencing these fields in the meta-data.xml file.

Field Description Type

Name(indexed)

City name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Nm_Code Official Code. Char(7)

Name_en** Name of area in English (optional). Char(40)

A2_Name(indexed)

Name of country secondary subdivision boundary within which the city is located.

Char(40)

A2_Abbr 4 character abbreviation for the country secondary subdivision boundary.

Char(6)

A2_Code Country secondary subdivision boundary official code. Char(5)

A1_Name(indexed)

Country sub national boundary full name. Char(40)

A1_Abbr(indexed)

Country sub national boundary two character abbreviation. Char(2)

A1_Code Country sub national boundary official code. Char(2)

A0_ISO(indexed)

ISO Country code. Char(2)

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Xcoord Longitude of city centroid. Float

Ycoord Latitude of city centroid. Float

2008.10 Data Guide 21

Page 22: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Administrative Boundaries for Multiple Countries

Naming ConventionsThe table naming convention is:

If a layer is defined by a seamless table, the base tables use a region abbreviation + a#.tab and the seamless table is:

Administrative Boundaries for Multiple Countries

The following table outlines the administrative boundaries for specific countries:

Description Code

Municipality boundaries. <3 char country ISO code or mi region code> + a4.tab

Description Code

Municipality boundaries. <3 char country ISO code or mi region code> + _a4.tab

Country A0 A1 A2 A3 A4

Austria Country Bundesland Bezirk Gemeinde Stadteile

Belgium/Luxembourg

Country Gewest Provincie Arrondissement Gemeente

Canada Country Province Census Division

Census Subdivision

Census Subdivision

Denmark Country Amt Kommun N/A N/A

France Country Région Départment Commune Arrondissement

Germany Country Bundesland Kreis Gemeinde Stadteile

Italy Country Regioni Province Comuni N/A

Netherlands Country Provincie Gemeente Woonplaats N/A

Norway Country Fylke Kommune N/A N/A

Portugal Country Regiao Distrito Concelho Freguesia

Spain Country Region Provincia Municipality N/A

Sweden Country Län Kommun N/A

Switzerland Country Canton Bezirk Gemeinde N/A

22 Envinsa

Page 23: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 2: Administrative Boundaries

Great Britain Country Standard Region

County / Unitary Authority

District / Unitary Authority

N/A

United States Country States Counties Towns City/Town

Country A0 A1 A2 A3 A4

2008.10 Data Guide 23

Page 24: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Administrative Boundaries for Multiple Countries

24 Envinsa

Page 25: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

3

Street Data

This section describes data relating to the extended enhanced address layer and street intersections.

In this section:

Extended Enhanced Address Layer . . . . . . . . . . . . . . . . . .26Street Intersections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Page 26: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Extended Enhanced Address Layer

Extended Enhanced Address Layer

The Extended Enhanced Address Layer (XE) table provides additional geographic tags to addressed street segments. The geographic tags added are the post code, municipality, minor subdivision, secondary subdivisions, and primary subdivisions.

Table StructureThe structure of the XE table is as follows:

Field Name Description Data Type

Name(indexed)

Street name in local language. Char(40)

FromLeft Beginning of address range on left side. Integer

ToLeft End of address range on left side. Integer

FromRight Beginning of address range on right side. Integer

ToRight End of address range on right side. Integer

Nm_Lng 2 character ISO language code of the Name field. For example, en for English

Char(2)

Name_xx** Name of street in another local language. Used for multi-language situations (optional).

Char(40)

Nm_Lng_xx** Language code of other local language (optional). Char(2)

PC_Left Post code of addresses on left side (default PC). Char(5)

PC_Right Post code of addresses on right side. Char(5)

A4_Left Name of city bounding on left of street (default name). Char(25)*

A4_Right Name of city bounding on the right of street. Char(25)*

A3_Left Name of A3 admin level on left (default name). Char(25)*

A3_Right Name of A3 admin level of right. Char(25)*

A2_Left Name of A2 admin level of left (default name). Char(25)*

A2_Right Name of A2 admin level of right. Char(25)*

A1_Left Name of A1admin level of left (default name). Char(25)*

A1_Right Name of A1 admin level of right. Char(25)*

26 Envinsa

Page 27: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 3: Street Data

*Actual field size can be configurable to reduce space requirements.** Multiple languages are handled by added additional language fields and referencing these fields in the meta-

data.xml file.

Naming ConventionsThe table naming convention is:

If a layer is defined by a seamless table, the base tables use a region abbreviation + _xe.tab and the seamless table is:

Street Intersections

The Intersections table provides a single table of named crossroads to support reverse geocoding. Any given intersection can have up to five street names that are the full set of the names of all streets that meet at a particular intersection. This table also includes coordinates of the intersection, geography tags, overpass/underpass flag, street priority codes, and attribute duplication information.

Table StructureThe structure of the intersections table is as follows:

A0_ISO ISO Country code. Char(2)

ID GDT Dynamap ID from source. Integer

miCode MapInfo internal feature code. Integer

Description Code

Extended enhanced address layer. <3 char country ISO code or mi region code> + xe.tab

Description Code

Extended enhanced address layer. <3 char country ISO code or mi region code> + _xe.tab

Field Name Description Data Type

Street1 Street name of first logical street that makes up the intersection.

Char(*)

Field Name Description Data Type

2008.10 Data Guide 27

Page 28: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Street Intersections

Char(*) = Character width 30 is the expected minimum although this can be greater depending upon the country.

Naming ConventionsThe table naming convention is:

Street2 Street name of second logical street that makes up the intersection.

Char(*)

Street3 Street name of third logical street that makes up the intersection.

Char(*)

Street4 (optional) Street name of fourth logical street that makes up the intersection.

Char(*)

Street5 (optional) Street name of fifth logical street that makes up the intersection.

Char(*)

X Longitude of the intersection point. Float

Y Latitude of the intersection point. Float

A1_Name Name of first level national sub division. Char(40)

A1_Code Official code for national sub division. Char(2)

A0_ISO ISO Country code. Char(2)

OUPass Flag indicating that some combination of the streets that make up the intersection are overpass/underpass streets.

Logical

Priority Value indicating the relative importance of the street. Lower numbers = lesser importance; Higher numbers = higher importance (this column is described below).

Integer

SameName Flag indicating that all streets segments that make up an intersection have the same name.

Logical

Duplicate Flag indicating that the intersection point is a duplicate (in all pieces of attribution) of other intersections in close proximity. (this column is described below).

Logical

Description Code

Cross street <3 char country ISO code or mi region code> + cr.tab

Field Name Description Data Type

28 Envinsa

Page 29: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 3: Street Data

If a layer is defined by a seamless table, the base tables use a region abbreviation + _cr.tab and the seamless table is:

Priority Implementation of Highways

There are four levels of highways in the North American data and each level receives a value. The intersection priority score defined by the Priority column is the sum of the values of the three highest scored segments that make up the intersection.

• Primary Highways – 4• Secondary Highways – 3• Major Roads – 2• All other roads – 1

For example, an intersection of four local roads would receive a score of four. A three-way intersection of two major roads and a local road would receive a score of five.

Description Code

Cross street <3 char country ISO code or mi region code> + _cr.tab

2008.10 Data Guide 29

Page 30: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Priority Implementation of Highways

30 Envinsa

Page 31: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

4

Map Display Data

The display data described in this section is used only in the Presentation Service.

In this section:

Display World Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . .32Display Administrative Boundaries . . . . . . . . . . . . . . . . . .33Display Urban Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Display Boundary Line Tables. . . . . . . . . . . . . . . . . . . . . . .35Display A2 Centroid Point Table . . . . . . . . . . . . . . . . . . . . .36Display Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Generalized Display Streets. . . . . . . . . . . . . . . . . . . . . . . . .38Highway Shields Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Display Landmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Display Gazetteer Tables . . . . . . . . . . . . . . . . . . . . . . . . . . .41Railways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Ferries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Page 32: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Display World Boundaries

Display World Boundaries

The display world boundaries differ from the world boundaries used by Location Utilities services in that the countries are not gridded, and the target country of a distribution is not included. This table is not gridded so that countries can be stylized using MapXtreme Java's style overrides for very small scale displays without grid lines showing and the target country is replaced by the A1 display boundaries that are not buffered at the coastlines for a high quality display.

Note: This world table is only used by the Presentation Service.

Table StructureThe structure of the world table is as follows:

Naming ConventionsThe name of the world countries table for the Presentation Service is the same as for the Location Utility Services.

The table naming convention is:

Field Description Type

Name Official country name. Char(50)

Nm_Abbr Official or commonly accepted abbreviation of the Name field. Char(2)

Nm_Code ISO country numeric code. Char(4)

Name_en Country name in English. Char(50)

Name_fr Country name in French. Char(50)

Name_de Country name in German. Char(50)

A0_ISO ISO Country code. Char(2)

Priority Label Priority rank. All set to 1. SmallInt

miCode MapInfo internal feature code. Integer

Capital Name of National capital city. Char(20)

Description Code

wld = World a0 = The A0 administrative level.

wlda0.tab

32 Envinsa

Page 33: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Display Administrative Boundaries

Some administrative boundary tables are simplified or modified to enhance performance for the Presentation Service. Linear boundary tables are also created from the administrative boundaries for cosmetic boundary style purposes. There are also points tables created using governmental centers as boundary centroids specifically for label placement.

Table StructureThe structure of the A1 level display boundaries table is as follows:

Naming ConventionsThe table naming convention is as follows where North America is provided as an example:

Field Description Type

Name Official name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Nm_Abbr Official or commonly accepted abbreviation of the Name field. Char(2)

Priority Label Priority rank. All set to 1. SmallInt

SmartLabel Specially formatted version of the contents of Name field. Char(40)

miCode MapInfo internal feature code. Integer

Description Code

wna = World, North Americaa1 = A1 administrative level

wnaa1.tab

2008.10 Data Guide 33

Page 34: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Label Municipal Locations

Label Municipal Locations

This point table is for labelling municpal locations.

Table StructureThe structure of the A4 level municipal points table is as follows:

Naming ConventionsThe table naming convention is as follows where North America is provided as an example:

Display Urban Areas

The urban areas boundaries do not necessarily align with any other boundaries. They are designed for use at small scale display levels only.

Field Description Type

Name Official name. Char(60)

Priority Label Priority rank. All set to 1. SmallInt

SmartLabel Specially formatted version of the contents of Name field. Char(60)

miCode MapInfo internal feature code. Integer

Xcoord Longitude of city centroid. Float

Ycoord Latitude of city centroid. Float

Description Code

wna = World, North Americaa4 = A4 administrative levelp = points

wnaa4p.tab

34 Envinsa

Page 35: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Table StructureThe structure of the urban areas table is as follows:

Naming ConventionsThe table naming convention is:

Display Boundary Line Tables

There are five boundary line tables for Presentation Service support. These tables represent the linear boundary features between international, national and sub-national regions. Using linear features allows enhanced stylization in the map displays.

Table StructureThe structure of the boundary line table for b0 and b1 levels is as follows:

Field Description Type

Name Urban area name. Char(40)

Priority Label Priority rank. All set to 1. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Description Code

ua = Urban areas_l = large scale

wnaua_l.tab

ua = Urban areas_s = small scale

wnaua_s.tab

Field Description Type

Name Descriptive name of boundary type.b0 = International boundary.b1 = State or Province boundary.

Char(40)

miCode MapInfo internal feature code. Integer

2008.10 Data Guide 35

Page 36: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Display A2 Centroid Point Table

Naming ConventionsThe table naming convention is:

Table StructureThe boundary line tables for b2 levels include more information, and are structured as follows:

Naming ConventionsThe table naming convention is:

Display A2 Centroid Point Table

The A2 Centroid Point table shows the preferred labeling location for the second level boundaries. This table is for label control use only within the Presentation Service.

Table StructureThe structure of the A2 centroid point table is as follows:

Description Code

International boundary lines that align with the large scale world boundaries table. wnab0_l.tab

International boundary lines generalized for small scale display. wnab0_s.tab

National boundary lines of the A1 level boundaries. wnab1.tab

Field Description Type

Name Name of state, territory, standard region, bundesland or province Char(40)

miCode MapInfo internal feature code. Integer

Description Code

A2 level boundary lines. wnab2.tab

Field Description Type

Name A2 level boundary name. Char(40)

Nm_Abbr Official or commonly accepted abbreviation of the Name field. Char(6)

36 Envinsa

Page 37: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Naming ConventionsThe table naming convention is:

Display Streets

The display streets are organized by four major street categories and are combined into a single table for each category. To reduce size and enhance quick display, these street tables are chained and slightly generalized. These tables do not have all the attributes of the enhanced EAL (XE) tables.

Table StructureThe structure of the streets table is as follows:

Note: This structure applies to all display street layers: primary highways, motorways, major roads, secondary highways, local roads, and so on.

A0_ISO ISO country code for the country containing the A2 boundary. Char(2)

Priority Label Priority rank. All set to 4. SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Description Code

Second level national boundary centroid table. wnap2.tab

Field Description Type

Name1 Official street name, route number if available. Must use proper text capitalization.

Char(40)

Nm1_Lng 2 character ISO language code of street name, “en”. Must be lower case.

Char(2)

Name2 Alternative street name or copy of Name1 if unavailable. Must use proper text capitalization.

Char(40)

Nm2_Lng 2 character ISO language code of street name, “en”. Must be lower case.

Char(2)

Field Description Type

2008.10 Data Guide 37

Page 38: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Generalized Display Streets

Naming ConventionsThe table naming convention is:

If a layer is defined by a seamless table, the base tables use a region abbreviation + d#.tab and the seamless table is:

Generalized Display Streets

There are three generalized display street tables that are used for medium and small scale displays. The d1, or major highways (Interstates and motorways), table is generalized for medium scale and small scale and the d2 (major roads) table is generalized for small scale displays.

A0_ISO ISO Country code. For example:• United States = US• Canada = CA

Must be upper case

Char(2)

Toll Logical value indicating whether segment is a toll road or not. Logical

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

miCode MapInfo internal feature code. Integer

Description Code

Primary highways <3 char country ISO code or mi region code> + d1.tab

Major roads <3 char country ISO code or mi region code> + d2.tab

Secondary roads <3 char country ISO code or mi region code> + d3.tab

Local roads <3 char country ISO code or mi region code> + d4.tab

Description Code

Primary highways <3 char country ISO code or mi region code> + _d1.tab

Major roads <3 char country ISO code or mi region code> + _d2.tab

Secondary roads <3 char country ISO code or mi region code> + _d3.tab

Local roads <3 char country ISO code or mi region code> + _d4.tab

Field Description Type

38 Envinsa

Page 39: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Table StructureThe structure of all generalized tables is as follows:

Naming ConventionsThe table naming convention is:

Highway Shields Tables

Highway shield symbols are created for major highways and for major and secondary roads. The shield layers are generated for display at three different zoom levels in a map display.

Table StructureThe structure of the highway shields table, and all the shield tables, is as follows:

Field Description Type

Name1 Official Street Name, Route number if available. Must use proper text capitalization.

Char(40)

Description Code

Medium scale Interstate/motorway table. wnad1_m.tab

Small scale Interstate/motorway table. wnad1_s.tab

Small scale major roads table. wnad2_s.tab

Field Description Type

HwyNumber The highway numeric designation without route type indicators, i.e. I87 is 87 and M4 is 4.

Char(10)

A0_ISO ISO Country code. Char(2)

2008.10 Data Guide 39

Page 40: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Display Landmarks

Naming ConventionsThe table naming convention is:

Display Landmarks

The Landmarks table that supports Location Utilities services is simplified for use in the Presentation Service. Unnecessary columns and indices are removed for display.

Table StructureThe structure of the display landmarks table is as follows:

Description Code

Interstate/motorway shields for display 0-5 miles. wnax1.tab

Interstate/motorway shields for display 5-15 miles. wnax2.tab

Interstate/motorway shields for display 15-50 miles. wnax3.tab

Major and secondary shields for display 0-5 miles. wnay1.tab

Major and secondary shields for display 5-15 miles. wnay2.tab

Major and secondary shields for display 15-50 miles. wnay3.tab

Field Description Type

Name(indexed)

Name of the landmark. Char(40)*

Nm_Abbr(indexed)

Landmark abbreviation or airport code. Char(4)

Nm_Code CFCC feature code or blank. Char(4)

A3_Name(indexed)

Name of the A3 administrative level (city, village, town, locale) within which the landmark is located.

Char(40)*

A2_Name(indexed)

Name of the A2 administrative level (county, unitary authority, kreis) within which the landmark is located.

Char(40)*

A2_Abbr Abbreviation for the county or census division. Char(6)

A1_Name(indexed)

Name of the A1 administrative level (state, province, standard region, bundesland) within which the landmark is located.

Char(40)*

40 Envinsa

Page 41: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

* Could be enlarged to fit local requirements

Naming ConventionsThe table naming convention for landmarks display are the same as for the service version.

Display Gazetteer Tables

The single gazetteer table that is used for Location Utilities services is simplified, unindexed and partitioned into seven layers for use in the Presentation Service. The coverage of cities is identical. Each of the seven layers represents city locations based on importance and priority. They are mutually exclusive.

Table StructureThe structure of all the display gazetteer tables is as follows:

A1_Abbr Abbreviation for state, territory, standard region, bundesland, or province.

Char(2)

A0_ISO(indexed)

ISO Country code. For example:• US = US• Canada = CA

Char(2)

SmartLabel Specially formatted text of the contents of the Name field. Char(40)*

Priority Label Priority rank: 1 = lowest, 4 = highest. SmallInt

miCode(indexed)

MapInfo internal feature code. Integer

Description Code

Features of local, regional or national interest.

<3 char country ISO code or mi region code> + lk.tab

Field Description Type

Name Name of the place, county, country or landmark to be searched. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Field Description Type

2008.10 Data Guide 41

Page 42: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Display Gazetteer Tables

Naming ConventionsThe table naming conventions are:

A3_Name Name of the A3 administrative level (city, village, town, locale) within which the named place is located.

Char(40)

A2_Name Name of the country secondary subdivision boundary (county, unitary authority, kreis) within which the named place is located.

Char(40)

A2_Abbr Abbreviation for the county or census division. Char(6)

A1_Name Name of the A1 administrative level (state, territory, province, standard region, bundesland) within which the named place is located.

Char(40)

A1_Abbr Abbreviation for country sub national boundary. Char(2)

A0_ Name Name of the country within which the named place is located. Char(40)

A0_ISO ISO country code. Char(2)

Priority Label Priority rank (unique to gazetteer):1. Top Cities2. Top city in each major urban area3. Top city in each major business area4. Top city in each county5. Top 3 cities in each county6. All cities with TotPop > 0 and not in 1-57. Other: named localities, neighborhoods, etc.

SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Type Type of named place:0 = Unknown type1 = Landmark centroid2 = City, village, town, locale (A3) centroid3 = County, kreis, region (A2) centroid4 = State, territory, province, bundesland (A1) centroid5 = Country (A0) centroidNot currently used by Envinsa. Value can default to 0.

SmallInt

Description Code

All priority 1 cities.Capital cities and larger major cities.

<3 char country ISO code or mi region code> + gz1.tab

Field Description Type

42 Envinsa

Page 43: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Railways

This layer contains railways/railroads as defined by the data provider. This layer contains or may contain:

Table StructureThe structure of the railways table is as follows:

All priority 2 cities.Large regional centers.Major cities in each metropolitan statistical area.

<3 char country ISO code or mi region code> + gz2.tab

All priority 3 cities.Big cities – major cities for state level viewing.

<3 char country ISO code or mi region code> + gz3.tab

All priority 4 cities.Major cities for sub-state level viewing.

<3 char country ISO code or mi region code> + gz4.tab

All priority 5 cities.Cities for county-level viewing.

<3 char country ISO code or mi region code> + gz5.tab

All priority 6 cities.Cities for metropolitan area viewing.

<3 char country ISO code or mi region code> + gz6.tab

All priority 7 cities.Comprehensive city layer. All municipalities regardless of population.

<3 char country ISO code or mi region code> + gz7.tab

• Main Rails• Spurs• Inclined Rails

• Subways• Cable

• Yard• Trolley/Tram

Field Description Type

Name Official name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Description Code

2008.10 Data Guide 43

Page 44: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Ferries

Naming ConventionsThe table naming convention is:

If a seamless table defines a layer, the base tables use a region abbreviation _rw.tab and the seamless table is:

Ferries

This layer contains ferries as defined by the data provider. This layer contains, or may contain:

A0_ISO ISO Country code. Char(2)

Priority Label Priority rank Smallint

miCode MapInfo internal feature code. Integer

Description Code

Railway display, large scale, high detail.

<3 char country ISO code or mi region code> + rw.tab

Medium scale railway display, medium detail.

<3 char country ISO code or mi region code> + rw_m.tab

Description Code

Railway display. <3 char country ISO code or mi region code> +_rw.tab

Medium scale railway display. <3 char country ISO code or mi region code> + _rw_m.tab

• Ferry• Vehicular ferry• Vehicular year round

• Vehicular seasonal• Passenger year round• Passenger seasonal

• Ferry• Rail operated

Field Description Type

44 Envinsa

Page 45: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Table StructureThe structure of the ferries table is as follows:

Naming ConventionsThe table naming convention is:

If a seamless table defines a layer, the base tables use a region abbreviation _fy.tab and the seamless table is:

Water Data

This MapDisplay subcomponent contains water features. Water features consist of region features (polygons) such as lakes and large rivers and linear features such as river centerlines, shorelines, and canals. There are three base tables that compose this subcomponent:

From the water boundary layer there are three derived tables based on scale, large, medium and small, all of which are a subset of the water boundaries table. The large scale is a detailed major water layer, the medium scale is a reduced table, and the small scale

Field Description Type

Name Official name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

A0_ISO ISO country code. Char(2)

Priority Label Priority rank. Smallint

miCode MapInfo internal feature code. Integer

Description Code

Ferry display. <3 char country ISO code or mi region code> + fy.tab

Description Code

Ferry display. <3 char country ISO code or mi region code> + _fy.tab

• Water boundaries • Water rivers • Ocean

2008.10 Data Guide 45

Page 46: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Water Data

table is a greatly reduced table for display of large areas. There is one major rivers table derived from the water rivers table. The ocean table is a solid background water object. This water component contains, or may contain:

Table StructureThe water boundary and water rivers tables have the same table structure. The ocean table contains one rectangular region object and has one field for Name.

Naming ConventionsThe table naming convention is:

• Shoreline• Rivers• Major Rivers• Minor Rivers• Canal• Aquaduct• Pipe/Channel• Ditch• Lake• Major Lake• Minor Lake• Pond• Reservoir• Ocean

• Sea• Bay• Gulf• Sound• Estuary• Glacier• Quarry• Harbor• Strait• Dam• Marsh/swamp• Sump• Undefined

Field Name Description Data Type

Name Official name. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

A0_ISO ISO Country code. Char(2)

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

Priority Label Priority rank. Smallint

miCode MapInfo internal feature code. Integer

Description Code

Water boundaries large scale. <3 char country ISO code or mi region code> + wb_l.tab

Water rivers. <3 char country ISO code or mi region code> + wr.tab

46 Envinsa

Page 47: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

If a seamless table defines a layer, the base tables use a region abbreviation _wb.tab and the seamless table is:

The derivative tables from water boundaries are all subsets of the water boundary table and are designated as major water layers. The layer convention for major water is mw with an extension to designate the scale.

The three derivative major water table naming conventions are:

The derivative water river table follows the same naming convention rule:

The background ocean layer table is called ocean.tab.

Land Use

This layer contains land uses as defined by the data provider consisting of numerous data sources. This layer contains, or may contain:

Description Code

Water boundaries. <3 char country ISO code or mi region code> + _wb.tab

Water rivers. <3 char country ISO code or mi region code> + _wr.tab

Description Code

Water boundaries medium scale. <3 char country ISO code or mi region code> + mw_m.tab

Water boundaries small scale. <3 char country ISO code or mi region code> + mw_s.tab

Description Code

Water rivers medium scale. <3 char country ISO code or mi region code> + wr_m.tab

• Parks• City Parks

National/Regional ParkNational/Regional Marine ParkIndustrialCompany grounds

• Penitentiary• Prison farm• Government grounds• Government center

• Educational institution• Place of worship• Custodial facilities• Hospitals• Orphanage• Correctional facility• Army base• Air Force base• Marine base• Coast Guard base• Commercial grounds

2008.10 Data Guide 47

Page 48: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Land Use

Table StructureThe structure of the land use table is as follows:

Naming ConventionsThe table naming convention is:

If a seamless table defines a landmark layer, the base tables use a region abbreviation _ld.tab and the seamless table is:

• Military• Naval base• Industrial harbor• Institutional grounds• Recreational areas• Amusement park• Zoo grounds• Golf course• Stadium• Cemetery• Educational or religious

• Shopping center• Woodlands• National/Regional forest• Beach/Dunes• Moor/Heathland• Desert/Tundra• Mainland• Island• Atoll• Reef• Sand bar/spit

Field Name Description Data Type

Name Name of the land use. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

A0_ISO ISO Country code. Char(2)

Priority Label Priority rank, 1 = lowest, 4 = highest. Smallint

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode MapInfo internal feature code. Integer

Description Code

Land use. <3 char country ISO code or mi region code> + ld.tab

Medium scale land use display. <3 char country ISO code or mi region code> + ld_m.tab

Small scale land use display. <3 char country ISO code or mi region code> + ld_s.tab

Description Code

Land use. <3 char country ISO code or mi region code> + _ld.tab

48 Envinsa

Page 49: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 4: Map Display Data

Medium scale land use display. <3 char country ISO code or mi region code> + _ld_m.tab

Small scale land use display. <3 char country ISO code or mi region code> + _ld_s.tab

Description Code

2008.10 Data Guide 49

Page 50: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Land Use

50 Envinsa

Page 51: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

5

Postal Code Data

This section describes data related to postal codes.

In this section:

Postal Code Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Page 52: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Postal Code Data

Postal Code Data

The post code table represents postal delivery areas which should align with the street network used in map display and should also be consistent in vintage with MapMarker data for a particular country. The postal boundaries used should be the lowest level (most detailed) postal boundaries available.

• U.S. – 5 digit Zip codes were used.• Canada – Forward Sortation Areas (FSA) were used.

Table StructureThe structure of the post code table is as follows

* Could be enlarged to fit local requirements

Field Description Type

Post_Code(indexed)

Postal code value. Char(5)*

A2_Name(indexed)

Name of country secondary subdivision boundary. Char(40)

A2_Abbr Country secondary subdivision boundary abbreviation. Char(6)

A2_Code Country secondary subdivision boundary code. Char(5)

A1_Name(indexed)

Country sub national boundary name. Char(25)

A1_Abbr(indexed)

Country sub national boundary abbreviation. Char(2)

A1_Code Country sub national boundary code. Char(2)

A0_ISO(indexed)

ISO country code. Char(2)

Priority Label Priority rank, 1 = lowest, 4 = highest. SmallInt

miCode MapInfo internal feature code. Integer

Xcoord Longitude of tract centroid. Float

Ycoord Latitude of tract centroid. Float

52 Envinsa

Page 53: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 5: Postal Code Data

Naming ConventionThe table naming convention is

Description Code

Post code. <3 char country ISO code or mi region code> + pc.tab

2008.10 Data Guide 53

Page 54: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Postal Code Data

54 Envinsa

Page 55: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

6

Landmarks

Landmark data is also referred to as Point of Interest data (POI). This section describes data related to landmarks.

In this section:

Landmark Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Page 56: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Landmark Data

Landmarks are point features of local, regional, or national interest. Landmarks for display are features for which a location and name and feature type are known. These features add to the detail of the display service and enhance locational reference. Possible landmarks are:

Recreational Landmarks

Sports

Public Landmarks

• Tourist attraction• Tourist attraction – building • Museum• Art gallery/Art center• Aquarium• Tourist attraction – monument• Memorial• Tourist attraction – natural• Scenic/panoramic view

• Beach, represented by a point• Mountain peak• Mountain pass• Tourist attraction – historic site• Tourist attraction – other• Winery• Tourist information center• Rest area

• Sport center/stadium• Tennis court• Cricket• Football/soccer• Baseball• Ice skating rink• Hockey• Basketball/Netball• Golf course

• Race course• Rifle range• Water sport• Swimming pool• Yacht basin• Sports club• Health club• Ski resort

• Educational• Kindergarten/nursery school• Elementary/middle/high school• Elementary/middle/high school – catholic• Elementary/middle/high school – private• Elementary/middle/high school – public• Colleges/Universities• Vocational/Trade• Special schools• Library• Child care center• Places of worship – undefined• Church• Baptist church

• Catholic church• Methodist church• Mosque• Synagogue• Buddhist temple• Hindu temple• Health facility – undefined• Hospital/polyclinic• Nursing and personal care• Office/Clinic of medical doctors• Office/Clinic of dentists• Medical/Dental laboratories/services• Ambulance station• Veterinary Clinic/Hospital

56 Envinsa

Page 57: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 6: Landmarks

Unclassified

Table StructureThe structure of the landmark table is as follows:

• All government facilities• City/municipal/local facility• Courts• Embassy/foreign government representa-

tion• Police station/facility• Fire stations• Post office• Post office – main• Post office – minor• Prisons• Military base/defense• Cemetery/Crematorium • Waste disposal/sewerage

• Transportation• Airport – civil• Airport – public• Airport – private• Airport – military• Helipad• Ferry terminal/wharf/jetty/terminal/port• Railway station, undefined• Railway station, underground• Railway station, international• Railway station, national• Railway station, (sub)urban• Bus terminal/depot• Parking – unclassified• Parking garage• Open parking area• Rent-a-car parking

• Cultural/Civic/Community center• Theatre• Opera• Concert hall• Music center• Cinema• Leisure center• Park • Zoo

• Amusement park• Camping ground/Caravan park• Fairgrounds• Night life/Clubs• Casino• Recreational clubs• Convention center• Exhibition center

Field Description Type

Name(indexed)

Name of the landmark. Char(40)*

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

Nm_Abbr(indexed)

Landmark abbreviation or airport code. Char(4)

Nm_Code CFCC feature code or blank. Char(4)

A3_Name(indexed)

Name of the A3 administrative level (city, village, town, locale) within which the landmark is located.

Char(40)*

2008.10 Data Guide 57

Page 58: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

* Names in these columns may require larger fields. Fields may be increased as needed but must be consistent within the table.

A3_Lng 2 character ISO language code of name, For example, en for English.

Char(2)

A3_Code MCD FIPS Code. Char(10)

A2_Name(indexed)

Name of the A2 administrative level (county, unitary authority, kreis) within which the landmark is located.

Char(40)*

A2_Lng 2 character ISO language code of name.For example, en for English.

Char(2)

A2_Abbr Abbreviation for the county or census division. Char(6)

A2_Code County FIPS code or census division code. Char(5)

A1_Name(indexed)

Name of the A1 administrative level (state, province, standard region, bundesland) within which the landmark is located.

Char(40)*

A1_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

A1_Abbr Abbreviation for state or province. Char(2)

A1_Code State FIPS or province code. Char(2)

A0_ Name Name of the A0 or country within which the landmark is located. Char(40)*

A0_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

A0_ISO(indexed)

ISO country code:• US = US• Canada = CA

Char(2)

SmartLabel Specially formatted text of the contents of the Name field. Char(40)*

Priority Label priority rank, 1 = lowest, 4 = highest. SmallInt

miCode(indexed)

MapInfo internal feature code. Integer

Xcoord Longitude of the named place. Float

Ycoord Latitude of the named place. Float

Field Description Type

58 Envinsa

Page 59: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 6: Landmarks

Naming ConventionsThe table naming convention is:

If a seamless table defines a landmark layer, the base tables use a region abbreviation _lk.tab and the seamless table is:

Description Code

Features of local, regional or national interest.

<3 char country ISO code or mi region code> + lk.tab

Description Code

Features of local, regional or national interest.

<3 char country ISO code or mi region code> + _lk.tab

2008.10 Data Guide 59

Page 60: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

60 Envinsa

Page 61: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

7

Gazetteer Data

This section describes the gazetteer data.

In this section:

Gazetteer Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Page 62: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Gazetteer Data

Gazetteer Data

The gazetteer layer is used in the Geocoding, Reverse Geocoding, and Map Display services. The gazetteer represents the point locations of cities, villages, hamlets, named places, and neighborhoods.

Table StructureThe structure of the gazetteer table is as follows:

Field Description Type

Name(indexed)

Name of the place, county, country, or landmark to searched. Char(40)

Nm_Lng 2 character ISO language code of the Name field. For example, en for English.

Char(2)

A3_Name(indexed)

Name of the A3 administrative level (city, village, town, locale) within which the named place is located.

Char(40)

A3_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

A3_Code Country minor subdivision code. Char(10)

A2_Name(indexed)

Name of the country secondary subdivision boundary (county, unitary authority, kreis) within which the named place is located.

Char(40)

A2_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

A2_Abbr Abbreviation for the county or census division. Char(6)

A2_Code Country secondary subdivision boundary code. Char(5)

A1_Name(indexed)

Name of the A1 administrative level (state, province, standard region, bundesland) within which the named place is located.

Char(40)

A1_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

A1_Abbr(indexed)

Abbreviation for country sub national boundary. Char(2)

A1_Code Country sub national boundary code. Char(2)

A0_ Name Name of the country within which the named place is located. Char(40)

A0_Lng 2 character ISO language code of name. For example, en for English.

Char(2)

62 Envinsa

Page 63: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Chapter 7: Gazetteer Data

Naming ConventionsThe table naming convention is:

A0_ISO(indexed)

ISO country code. Char(2)

Priority Label priority ranking (unique to gazetteer):1. Top cities2. Top city in each major urban area3. Top city in each major business area4. Top city in each county5. Top 3 cities in each county6. All cities with TotPop > 0 and not in 1-57. Other: named localities, neighborhoods, etc.

SmallInt

SmartLabel Specially formatted text of the contents of the Name field. Char(40)

miCode(indexed)

MapInfo internal feature code. Integer

Type Type of named place:0 = Unknown type1 = Landmark centroid2 = City, village, town, locale (A3) centroid3 = County, Kreis, region (A2) centroid4 = State, province, bundesland (A1) centroid5 = Country (A0) centroidNot currently used by Envinsa. Value can default to 0.

SmallInt

Xcoord Longitude of the named place. Float

Ycoord Latitude of the named place. Float

Description Code

Gazetteer. <3 char country ISO code or mi region code> + gz.tab

Field Description Type

2008.10 Data Guide 63

Page 64: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Gazetteer Data

64 Envinsa

Page 65: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

A

Glossary of Field Names

This appendix lists a glossary of the field names used in the Envinsa data product.

In this section:

General Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Field Names that Apply Only to the Enhanced EAL . . . . .68

Page 66: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

General Field Names

General Field Names

As part of the design process for Envinsa data, a concerted effort was made to normalize common aspects of the data and data table design to accommodate multi-national requirements, as well as to streamline the production process.

The following table presents a glossary of the field names that are used in the Envinsa data product.

Field Name Description Data Type

Post_Code The postal code associated with a boundary. This is specific to each county and is not always at the same level of postcode detail. For example:U.S. = 5 digit Zip code Canada = 3 character FSA.

Char

Name Always the name of the geographic feature being represented. Char

Nm_Lng The two character lower case ISO designation for the language of the content of the name field.

Char

Nm_Abbr A standard or commonly recognized abbreviation for the content of the name field. If no reasonable abbreviation exists then this field is left blank.

Char

Nm_Code A standard, official or otherwise accepted code for the geographic feature referenced by the Name field. Codes can be official government standard codes such as FIPS codes in the US or governing authority codes, such as airport designations.

Char

Name1 In some tables, it is necessary to include several names for a single geographic feature. This is the case with intersections where all unique street names are associated with a single location. In tables where this is necessary, the Name1 field name is used for the primary name and has the same meaning as the Name field in all other tables.

Char

Nm1_Lng Same as the Nm_Lng field and applies to the contents of the Name1 field.

Char

Name2 Contains the alternate name of the geographic feature, or a name in different language in multi-lingual countries.

Char

Nm2_Lng The two character lower case ISO language code for the contents of the Name2 field.

Char

A1_Name The official name of the first level of administrative/governmental boundaries within a country.

Char

66 Envinsa

Page 67: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix A: Glossary of Field Names

A1_Lng The two character lower case ISO language code for the contents of A1_Name.

Char

A1_Code The official administrative/governmental code for the first level administrative boundary.

Char

A1_Abbr Official government or postal abbreviation for the content of the A1_Name field.

Char

A2_Name The official name of the Second level of administrative/governmental boundaries within a country.

Char

A2_Lng The two character lower case ISO language code for the contents of A2_Name.

Char

A2_Code The official administrative/governmental code for the second level administrative boundary.

Char

A2_Abbr Official government or postal abbreviation for the content of the A2_Name field.

Char

A3_Name The official name of the third level of administrative/government boundaries within a country.

Char

A3_Lng The two character lower case ISO language code for the contents of A3_Name.

Char

A3_Code The official administrative/governmental code for the third level administrative boundary.

Char

A0_Name The official Country Name. Char

A0_Lng The two character lower case ISO language code for the contents of A0_Name.

Char

A0_ISO The two character upper case ISO country designation. For example,US = United StatesUK = United Kingdom of Great Britain and Northern Ireland

Char

SmartLabel A specially formatted version of the contents of the Name (Name1) field that has control characters introduced to enhance labeling on cartographic displays.

Char

Priority A value between 1 and 4 that is used for resolving labeling overlap conflict. 4 is the highest priority, meaning the feature with a priority of 4 will have their label supersede all others. 1 is the lowest priority.

Small Integer

Field Name Description Data Type

2008.10 Data Guide 67

Page 68: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Field Names that Apply Only to the Enhanced EAL

Field Names that Apply Only to the Enhanced EAL

miCode This is a feature code used internally by MapInfo to uniformly identify geographic features independently of data source. This code is used to select features by categories and subcategories and to set style standards. This is the preferred field name.

Integer

miFcode This is a feature code used internally by MapInfo to uniformly identify geographic features independently of data source. This code is used to select features by categories and subcategories and to set style standards. This is field name spelling from an early version of data production that is being phased out. It is still used in some tables.

Integer

Toll A logical field used in street tables to indicate road segments that are part of toll highway. This is used to modify display styles.

Logical

Xcoord This is the Longitude of the center of an object. For A0 boundaries the center is set at the national capital location, for A1 boundaries the center is set at the state/province capital location and for A2 boundaries the center is set at the county/administrative city location. All other objects use the geographic center.

Float

Field Name Description Data Type

PC_Left The postal code of the left side of a street segment in the direction of coordinate digitization to determine left and right.

Char

PC_Right The postal code of the right side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A4_Left The municipality name of the left side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A4_Right The municipality name of the right side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A3_Left The name of the A3 boundary of the left side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A3_Right The name of the A3 boundary of the right side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A2_Left The name of the A2 boundary of the left side of a street segment in the direction of coordinate digitization to determine left and right.

Char

Field Name Description Data Type

68 Envinsa

Page 69: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix A: Glossary of Field Names

A2_Right The name of the A2 boundary of the right side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A1_Left The abbreviation of the A1 boundary of the left side of a street segment in the direction of coordinate digitization to determine left and right.

Char

A1_Right The abbreviation of the A1 boundary of the right side of a street segment in the direction of coordinate digitization to determine left and right.

Char

ID The segment ID value from the source data provider. Used to track geocoding issues.

Char

2008.10 Data Guide 69

Page 70: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Field Names that Apply Only to the Enhanced EAL

70 Envinsa

Page 71: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

B

miCodes

This appendix lists miCodes used in Envinsa.

Sections in this Appendix:

Administrative Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Ferries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Land . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Landmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Railways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Settlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87Water . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Page 72: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Administrative Regions

The following table shows the Administrative Regions miCodes.

Category SubCat Subfeature miFCode

50 Administrative Regions 01 Governmental 0000 Admin Boundary undefined 50010000

50 Administrative Regions 01 Governmental 0100 National BDY 50010100

50 Administrative Regions 01 Governmental 0101 1st subnational 50010101

50 Administrative Regions 01 Governmental 0102 2nd subnational 50010102

50 Administrative Regions 01 Governmental 0103 3rd subnational 50010103

50 Administrative Regions 01 Governmental 0104 4th subnational 50010104

50 Administrative Regions 01 Governmental 0105 5th subnational 50010105

50 Administrative Regions 01 Governmental 0200 Seaward extent of boundary 50010200

50 Administrative Regions 02 Census 0100 Basic census unit 50020100

50 Administrative Regions 02 Census 0101 1st Census aggregation level 50020101

50 Administrative Regions 02 Census 0102 2nd Census aggregation level 50020102

50 Administrative Regions 02 Census 0103 3rd Census aggregation level 50020103

50 Administrative Regions 02 Census 0104 4th Census aggregation level 50020104

50 Administrative Regions 02 Census 0200 Seaward extent of boundary 50020200

50 Administrative Regions 03 Postal 0100 Basic postal route level 50030100

50 Administrative Regions 03 Postal 0101 1st Postal aggregation level 50030101

50 Administrative Regions 03 Postal 0102 2nd Postal aggregation level 50030102

50 Administrative Regions 03 Postal 0103 3rd Postal aggregation level 50030103

50 Administrative Regions 03 Postal 0200 Address area 50030200

50 Administrative Regions 04 Urban 0100 Incorporated urban area 50040100

50 Administrative Regions 04 Urban 0200 Area of urbanization 50040200

50 Administrative Regions 04 Urban 0300 Statistic area 50040300

50 Administrative Regions 04 Urban 0400 Private property (lots) 50040400

50 Administrative Regions 05 Districts 0100 Police precincts 50050100

72 Envinsa

Page 73: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

Ferries

The following table shows the Ferries miCodes.

50 Administrative Regions 05 Districts 0200 Fire districts 50050200

50 Administrative Regions 05 Districts 0300 School districts 50050300

50 Administrative Regions 05 Districts 0400 Voting districts 50050400

50 Administrative Regions 06 TeleCom 0100 Local calling area 50060100

50 Administrative Regions 06 TeleCom 0200 Cell/Tower area 50060200

50 Administrative Regions 06 TeleCom 0300 Area code district 50060300

Category SubCat Subfeature miFCode

70 Ferries 01 Ship/hovercraft 0100 Ferry 70010100

70 Ferries 01 Ship/hovercraft 0110 Vehicular ferry 70010110

70 Ferries 01 Ship/hovercraft 0111 Vehicular year round 70010111

70 Ferries 01 Ship/hovercraft 0112 Vehicular seasonal 70010112

70 Ferries 01 Ship/hovercraft 0120 Passenger ferry 70010120

70 Ferries 01 Ship/hovercraft 0121 Passenger year round 70010121

70 Ferries 01 Ship/hovercraft 0122 Passenger seasonal 70010122

70 Ferries 01 Ship/hovercraft 0130 Railway ferry 70010130

70 Ferries 02 Rail 0100 Rail operated 70020100

Category SubCat Subfeature miFCode

2008.10 Data Guide 73

Page 74: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Land

Land

The following table shows the Land miCodes:

Category SubCat Subfeature miFCode

60 Land 01 Land Use 0100 Open land 60010100

60 Land 01 Land Use 0110 Park grounds 60010110

60 Land 01 Land Use 0111 National Park or forest 60010111

60 Land 01 Land Use 0112 State/Provincial park 60010112

60 Land 01 Land Use 0113 County/Regional park 60010113

60 Land 01 Land Use 0114 City/Community park 60010114

60 Land 01 Land Use 0120 Marine park 60010120

60 Land 01 Land Use 0130 Landfill grounds 60010130

60 Land 01 Land Use 0140 Lighthouse grounds 60010140

60 Land 01 Land Use 0150 Rest area grounds 60010150

60 Land 01 Land Use 0200 Industrial 60010200

60 Land 01 Land Use 0210 Company grounds 60010210

60 Land 01 Land Use 0220 Industrial harbor 60010220

60 Land 01 Land Use 0230 Institutional grounds 60010230

60 Land 01 Land Use 0240 Water mill grounds 60010240

60 Land 01 Land Use 0250 Windmill grounds 60010250

60 Land 01 Land Use 0300 Recreational areas 60010300

60 Land 01 Land Use 0310 Play grounds 60010310

60 Land 01 Land Use 0311 Amusement parks 60010311

60 Land 01 Land Use 0312 Zoo grounds 60010312

60 Land 01 Land Use 0313 Golf course 60010313

60 Land 01 Land Use 0314 Stadium grounds 60010314

60 Land 01 Land Use 0320 Tourism 60010320

60 Land 01 Land Use 0321 Castles (not to visit) 60010321

74 Envinsa

Page 75: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

60 Land 01 Land Use 0322 Castles (to visit) 60010322

60 Land 01 Land Use 0323 Place of Interest ground 60010323

60 Land 01 Land Use 0324 Sport hall ground 60010324

60 Land 01 Land Use 0330 Cultural 60010330

60 Land 01 Land Use 0331 Art Center ground 60010331

60 Land 01 Land Use 0332 Theatre ground 60010332

60 Land 01 Land Use 0333 Museum 60010333

60 Land 01 Land Use 0400 Cemetery 60010400

60 Land 01 Land Use 0500 Educational or religious 60010500

60 Land 01 Land Use 0510 Educational institution 60010510

60 Land 01 Land Use 0511 University ground 60010511

60 Land 01 Land Use 0512 Library ground 60010512

60 Land 01 Land Use 0520 Religious ground 60010520

60 Land 01 Land Use 0521 Place of worship 60010521

60 Land 01 Land Use 0522 Monastery ground 60010522

60 Land 01 Land Use 0523 Abbey ground 60010523

60 Land 01 Land Use 0600 Custodial facilities 60010600

60 Land 01 Land Use 0601 Hospitals 60010601

60 Land 01 Land Use 0602 Orphanage 60010602

60 Land 01 Land Use 0610 Correctional facility 60010610

60 Land 01 Land Use 0611 Penitentiary 60010611

60 Land 01 Land Use 0612 Prison farm 60010612

60 Land 01 Land Use 0700 Government grounds 60010700

60 Land 01 Land Use 0710 Government center 60010710

60 Land 01 Land Use 0711 Courthouse ground 60010711

60 Land 01 Land Use 0712 Fire station ground 60010712

Category SubCat Subfeature miFCode

2008.10 Data Guide 75

Page 76: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Land

60 Land 01 Land Use 0713 Police station ground 60010713

60 Land 01 Land Use 0714 State police station ground 60010714

60 Land 01 Land Use 0715 Post office ground 60010715

60 Land 01 Land Use 0720 Military 60010720

60 Land 01 Land Use 0721 Naval base 60010721

60 Land 01 Land Use 0722 Army base 60010722

60 Land 01 Land Use 0723 Air force base 60010723

60 Land 01 Land Use 0724 Marine base 60010724

60 Land 01 Land Use 0725 Coast guard base 60010725

60 Land 01 Land Use 0726 Fortress ground 60010726

60 Land 01 Land Use 0730 Special enclaves 60010730

60 Land 01 Land Use 0731 Native reservations 60010731

60 Land 01 Land Use 0732 Government reserves 60010732

60 Land 01 Land Use 0733 Government protectorates 60010733

60 Land 01 Land Use 0734 Royal holdings/Emirates 60010734

60 Land 01 Land Use 0735 Embassy or foreign mission 60010735

60 Land 01 Land Use 0736 Free trade zone 60010736

60 Land 01 Land Use 0800 Commercial grounds 60010800

60 Land 01 Land Use 0801 Shopping center 60010801

60 Land 01 Land Use 0802 Airport grounds 60010802

60 Land 01 Land Use 0803 Runway grounds 60010803

60 Land 01 Land Use 0804 Railway station grounds 60010804

60 Land 01 Land Use 0805 Right of way/Easement 60010805

60 Land 01 Land Use 0900 Footprint 60010900

60 Land 01 Land Use 0910 Commercial 60010910

60 Land 01 Land Use 0920 Parking 60010920

Category SubCat Subfeature miFCode

76 Envinsa

Page 77: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

Landmarks

The following table shows the Landmarks miCodes:

60 Land 01 Land Use 0930 Recreational 60010930

60 Land 01 Land Use 0940 Government 60010940

60 Land 01 Land Use 0950 Residential 60010950

60 Land 02 Land Cover 0100 Woodlands 60020100

60 Land 02 Land Cover 0200 National/Regional forest 60020200

60 Land 02 Land Cover 0300 Beach/Dunes 60020300

60 Land 02 Land Cover 0400 Moor/Heath land 60020400

60 Land 02 Land Cover 0500 Desert/Tundra 60020500

60 Land 03 Land Masses 0100 Mainland 60030100

60 Land 03 Land Masses 0200 Island 60030200

60 Land 03 Land Masses 0210 Atoll 60030210

60 Land 03 Land Masses 0300 Reef 60030300

60 Land 03 Land Masses 0400 Sand bar/Spit 60030400

Category SubCat Subfeature miFCode

10 POI 00 Unclassified 0000 unclassified 10000000

10 POI 01 Shopping – retail & wholesale 0000 Unclassified 10010000

10 POI 01 Shopping – retail & wholesale 0100 General merchandise stores/shops 10010100

10 POI 01 Shopping – retail & wholesale 0101 Department stores 10010101

10 POI 01 Shopping – retail & wholesale 0102 Variety stores 10010102

10 POI 01 Shopping – retail & wholesale 0103 Warehouse club stores 10010103

10 POI 01 Shopping – retail & wholesale 0200 Food stores 10010200

10 POI 01 Shopping – retail & wholesale 0201 Food stores – supermarket 10010201

Category SubCat Subfeature miFCode

2008.10 Data Guide 77

Page 78: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Landmarks

10 POI 01 Shopping – retail & wholesale 0202 Food stores – grocery stores 10010202

10 POI 01 Shopping – retail & wholesale 0203 Food stores – fish/seafood market 10010203

10 POI 01 Shopping – retail & wholesale 0204 Food stores – fruits/veg. market 10010204

10 POI 01 Shopping – retail & wholesale 0205 Beverage/Bottle store 10010205

10 POI 01 Shopping – retail & wholesale 0300 Apparel and accessory 10010300

10 POI 01 Shopping – retail & wholesale 0400 Auto sales and service stations 10010400

10 POI 01 Shopping – retail & wholesale 0401 Car dealership – sales 10010401

10 POI 01 Shopping – retail & wholesale 0402 Car dealership – service 10010402

10 POI 01 Shopping – retail & wholesale 0403 Car dealership – sales & service 10010403

10 POI 01 Shopping – retail & wholesale 0404 Car repair facilities 10010404

10 POI 01 Shopping – retail & wholesale 0405 Car rental office 10010405

10 POI 01 Shopping – retail & wholesale 0410 Motorcycle sales and service 10010410

10 POI 01 Shopping – retail & wholesale 0500 Gas/Petrol stations 10010500

10 POI 01 Shopping – retail & wholesale 0600 Furniture and home furnishings 10010600

10 POI 01 Shopping – retail & wholesale 0700 Building materials & garden supplies 10010700

10 POI 01 Shopping – retail & wholesale 0800 Wholesale trade durable & non durable

10010800

10 POI 01 Shopping – retail & wholesale 0900 Shopping malls/Shopping centers 10010900

10 POI 02 Eating and drinking places 0000 Unclassified 10020000

10 POI 02 Eating and drinking places 0100 Restaurants – ethnic 10020100

10 POI 02 Eating and drinking places 0101 Restaurants – ethnic-American 10020101

10 POI 02 Eating and drinking places 0102 Restaurants – ethnic-Chinese 10020102

10 POI 02 Eating and drinking places 0103 Restaurants – ethnic-Italian 10020103

10 POI 02 Eating and drinking places 0104 Restaurants – ethnic-German 10020104

10 POI 02 Eating and drinking places 0105 Restaurants – ethnic-French 10020105

10 POI 02 Eating and drinking places 0106 Restaurants – ethnic-Japanese 10020106

10 POI 02 Eating and drinking places 0107 Restaurants – ethnic-Indian 10020107

Category SubCat Subfeature miFCode

78 Envinsa

Page 79: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

10 POI 02 Eating and drinking places 0108 Restaurants – ethnic-Thai 10020108

10 POI 02 Eating and drinking places 0109 Restaurants – ethnic-Vietnamese 10020109

10 POI 02 Eating and drinking places 0110 Restaurants – ethnic-Middle East 10020110

10 POI 02 Eating and drinking places 0111 Restaurants – ethnic-Greek 10020111

10 POI 02 Eating and drinking places 0112 Restaurants – ethnic-Mexican 10020112

10 POI 02 Eating and drinking places 0200 Restaurants – IceCream/SoftDrink soda

10020200

10 POI 02 Eating and drinking places 0300 Restaurants – fast food 10020300

10 POI 02 Eating and drinking places 0400 Restaurants – family 10020400

10 POI 02 Eating and drinking places 0500 Restaurants – pizza 10020500

10 POI 02 Eating and drinking places 0600 Restaurants – seafood 10020600

10 POI 02 Eating and drinking places 0700 Restaurants – drinking/alcoholic 10020700

10 POI 02 Eating and drinking places 0800 Area of high concentration of restaurants

10020800

10 POI 03 Business & personal services 0000 Unclassified 10030000

10 POI 03 Business & personal services 0100 Hotels/Motels 10030100

10 POI 03 Business & personal services 0200 Personal service business 10030200

10 POI 03 Business & personal services 0201 Laundromat 10030201

10 POI 03 Business & personal services 0202 Salons 10030202

10 POI 03 Business & personal services 0300 Financial services 10030300

10 POI 03 Business & personal services 0301 Banks 10030301

10 POI 03 Business & personal services 0302 ATM Machine / Cash dispenser 10030302

10 POI 03 Business & personal services 0400 Broadcasting service 10030400

10 POI 03 Business & personal services 0500 Automobile club 10030500

10 POI 04 Other business 0000 Office/Company/Industry 10040000

10 POI 04 Other business 0100 Agriculture and mining 10040100

10 POI 04 Other business 0101 Mine/Quarry 10040101

Category SubCat Subfeature miFCode

2008.10 Data Guide 79

Page 80: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Landmarks

10 POI 04 Other Business 0200 Manufacturing 10040200

10 POI 11 Tourism 0000 Unclassified 10110000

10 POI 11 Tourism 0100 Tourist Attraction 10110100

10 POI 11 Tourism 0200 Tourist Attraction – building 10110200

10 POI 11 Tourism 0201 Museum 10110201

10 POI 11 Tourism 0202 Art gallery/Art center 10110202

10 POI 11 Tourism 0203 Aquarium 10110203

10 POI 11 Tourism 0300 Tourist Attraction – monument 10110300

10 POI 11 Tourism 0301 Memorial 10110301

10 POI 11 Tourism 0400 Tourist Attraction – natural 10110400

10 POI 11 Tourism 0401 Scenic/panoramic view 10110401

10 POI 11 Tourism 0402 Beach, represented by a point 10110402

10 POI 11 Tourism 0403 Mountain peak 10110403

10 POI 11 Tourism 0405 Mountain pass 10110405

10 POI 11 Tourism 0500 Tourist attraction – historic site 10110500

10 POI 11 Tourism 0600 Tourist attraction – other 10110600

10 POI 11 Tourism 0601 Winery 10110601

10 POI 11 Tourism 0700 Tourist information center 10110700

10 POI 11 Tourism 0800 Rest area (public) 10110800

10 POI 12 Sports 0000 Sports – unclassified 10120000

10 POI 12 Sports 0100 Sport center/Stadium 10120100

10 POI 12 Sports 0101 Tennis court 10120101

10 POI 12 Sports 0102 Cricket 10120102

10 POI 12 Sports 0103 Football/Soccer 10120103

10 POI 12 Sports 0104 Baseball 10120104

10 POI 12 Sports 0105 Ice skating rink 10120105

Category SubCat Subfeature miFCode

80 Envinsa

Page 81: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

10 POI 12 Sports 0106 Hockey 10120106

10 POI 12 Sports 0107 Basketball/Netball 10120107

10 POI 12 Sports 0108 Golf course 10120108

10 POI 12 Sports 0109 Race course 10120109

10 POI 12 Sports 0110 Rifle range 10120110

10 POI 12 Sports 0111 Bowling center 10120111

10 POI 12 Sports 0300 Water sport 10120300

10 POI 12 Sports 0301 Swimming pool 10120301

10 POI 12 Sports 0302 Yacht basin 10120302

10 POI 12 Sports 0400 Sports club 10120400

10 POI 12 Sports 0500 Health club 10120500

10 POI 12 Sports 0600 Ski resort 10120600

10 POI 13 Recreation/Entertainment 0000 Unclassified 10130000

10 POI 13 Recreation/Entertainment 0100 Cultural/Civic/Community center 10130100

10 POI 13 Recreation/Entertainment 0101 Theater 10130101

10 POI 13 Recreation/Entertainment 0102 Opera 10130102

10 POI 13 Recreation/Entertainment 0103 Concert hall 10130103

10 POI 13 Recreation/Entertainment 0104 Music center 10130104

10 POI 13 Recreation/Entertainment 0105 Cinema 10130105

10 POI 13 Recreation/Entertainment 0200 Leisure center 10130200

10 POI 13 Recreation/Entertainment 0201 Park 10130201

10 POI 13 Recreation/Entertainment 0202 Zoo 10130202

10 POI 13 Recreation/Entertainment 0203 Amusement park 10130203

10 POI 13 Recreation/Entertainment 0204 Camping ground/Caravan park 10130204

10 POI 13 Recreation/Entertainment 0205 Fairgrounds 10130205

10 POI 13 Recreation/Entertainment 0206 Night life/Clubs 10130206

Category SubCat Subfeature miFCode

2008.10 Data Guide 81

Page 82: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Landmarks

10 POI 13 Recreation/Entertainment 0207 Casino 10130207

10 POI 13 Recreation/Entertainment 0208 Recreational clubs 10130208

10 POI 13 Recreation/Entertainment 0300 Convention center 10130300

10 POI 13 Recreation/Entertainment 0301 Exhibition center 10130301

10 POI 21 Educational 0000 Educational 10210000

10 POI 21 Educational 0100 Kindergarten/Nursery school 10210100

10 POI 21 Educational 0200 Elementary/Middle/High school 10210200

10 POI 21 Educational 0201 Elementary/Middle/High school – catholic

10210201

10 POI 21 Educational 0202 Elementary/Middle/High school – private

10210202

10 POI 21 Educational 0203 Elementary/Middle/High School – public

10210203

10 POI 21 Educational 0300 Colleges/Universities 10210300

10 POI 21 Educational 0400 Vocational/Trade 10210400

10 POI 21 Educational 0500 Special schools 10210500

10 POI 21 Educational 0600 Library 10210600

10 POI 21 Educational 0700 Child care center 10210700

10 POI 22 Place of worship 0000 Places of worship, undefined 10220000

10 POI 22 Place of worship 0100 Church 10220100

10 POI 22 Place of worship 0101 Baptist church 10220101

10 POI 22 Place of worship 0102 Catholic church 10220102

10 POI 22 Place of worship 0103 Methodist church 10220103

10 POI 22 Place of worship 0200 Mosque 10220200

10 POI 22 Place of worship 0300 Synagogue 10220300

10 POI 22 Place of worship 0400 Buddhist temple 10220400

10 POI 22 Place of worship 0500 Hindu temple 10220500

10 POI 22 Place of worship 0600 Other 10220600

Category SubCat Subfeature miFCode

82 Envinsa

Page 83: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

10 POI 23 Health 0000 Health facilities, undefined 10230000

10 POI 23 Health 0010 Pharmacy 10230010

10 POI 23 Health 0100 Hospital/Polyclinic 10230100

10 POI 23 Health 0200 Nursing and personal care 10230200

10 POI 23 Health 0300 Office/Clinic of medical doctors 10230300

10 POI 23 Health 0400 Office/Clinic of dentist 10230400

10 POI 23 Health 0500 Medical/Dental Laboratories/Services 10230500

10 POI 23 Health 0600 Ambulance station 10230600

10 POI 23 Health 0700 Veterinarian Clinic/Hospital 10230700

10 POI 24 Public 0000 All 10240000

10 POI 24 Public 0100 Government facilities 10240100

10 POI 24 Public 0101 City/Municipal/local facility 10240101

10 POI 24 Public 0102 Courts 10240102

10 POI 24 Public 0103 Embassy /Foreign Government Representation

10240103

10 POI 24 Public 0104 Frontier crossing 10240104

10 POI 24 Public 0300 Police station/facility 10240300

10 POI 24 Public 0400 Fire stations 10240400

10 POI 24 Public 0500 Post office 10240500

10 POI 24 Public 0501 Post office – main 10240501

10 POI 24 Public 0502 Post office – minor 10240502

10 POI 24 Public 0600 Prisons 10240600

10 POI 24 Public 0700 Military base/Defense 10240700

10 POI 24 Public 0800 Cemetery/Crematorium 10240800

10 POI 24 Public 0900 Waste disposal/Sewerage 10240900

10 POI 31 Airports 0000 Unclassified 10310000

10 POI 31 Airports 0010 Check-in facility at airport 10310010

Category SubCat Subfeature miFCode

2008.10 Data Guide 83

Page 84: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Landmarks

10 POI 31 Airports 0011 Check-in facility at airport departures 10310011

10 POI 31 Airports 0012 Check-in facility at airport arrivals 10310012

10 POI 31 Airports 0013 Check-in facility at airport departure/arrivals

10310013

10 POI 31 Airports 0100 Airport – civil 10310100

10 POI 31 Airports 0101 Airport – public 10310101

10 POI 31 Airports 0102 Airport – private 10310102

10 POI 31 Airports 0200 Airport – military 10310200

10 POI 31 Airports 0300 Helipad 10310300

10 POI 32 Stations 0000 Unclassified 10320000

10 POI 32 Stations 0100 Ferry terminal /Wharf/Jetty/Pontoon 10320100

10 POI 32 Stations 0101 Ferry terminal ship/hovercraft 10320101

10 POI 32 Stations 0102 Ferry terminal train 10320102

10 POI 32 Stations 0200 Railway station, undefined 10320200

10 POI 32 Stations 0201 Railway station, underground/metro 10320201

10 POI 32 Stations 0202 Railway station, International 10320202

10 POI 32 Stations 0203 Railway station, national 10320203

10 POI 32 Stations 0204 Railway station, (Sub) urban 10320204

10 POI 32 Stations 0300 Bus terminal /Depot 10320300

10 POI 33 Parking 0000 Parking – unclassified 10330000

10 POI 33 Parking 0100 Parking garage 10330100

10 POI 33 Parking 0200 Open parking area 10330200

10 POI 33 Parking 0210 Park and ride lot 10330210

10 POI 33 Parking 0300 Rent-a-car parking 10330300

10 POI 34 Interchanges 0000 Intersection 10340000

10 POI 34 Interchanges 0100 Freeway exit/entrance 10340100

10 POI 34 Interchanges 0200 Freeway to freeway interchange 10340200

Category SubCat Subfeature miFCode

84 Envinsa

Page 85: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

Railways

The following table shows the Railways miCodes:

Settlements

The following table shows the Settlements miCodes:

10 POI 34 Interchanges 0300 Non freeway intersection 10340300

10 POI 34 Interchanges 0400 Site of Interchange signage text 10340400

Category SubCat Subfeature miFCode

40 Rails 01 Railway 0000 Railway track undefined 40010000

40 Rails 01 Railway 0100 Main rail 40010100

40 Rails 01 Railway 0200 Spur 40010200

40 Rails 01 Railway 03 Inclined 40010300

40 Rails 01 Railway 0400 Other minor line 40010400

40 Rails 02 Light 0100 Subway 40020100

40 Rails 02 Light 0200 Trolley/Tram 40020200

40 Rails 02 Light 0300 Cable 40020300

40 Rails 03 Yard 0100 Yard 40030100

Category SubCat Subfeature miFCode

80 Settlements 01 Governmental 0000 Capital city 80010000

80 Settlements 01 Governmental 0100 International capital 80010100

80 Settlements 01 Governmental 0200 National capital 80010200

80 Settlements 01 Governmental 0300 1st Level capital 80010300

Category SubCat Subfeature miFCode

2008.10 Data Guide 85

Page 86: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Settlements

80 Settlements 01 Governmental 0400 2nd Level capital 80010400

80 Settlements 01 Governmental 0500 3rd level capital 80010500

80 Settlements 01 Governmental 0600 4th level capital 80010600

80 Settlements 02 Rank order 0100 Settlement 80020100

80 Settlements 02 Rank order 0101 Largest settlements 80020101

80 Settlements 02 Rank order 0102 2nd largest 80020102

80 Settlements 02 Rank order 0103 3rd largest 80020103

80 Settlements 02 Rank order 0104 4th largest 80020104

80 Settlements 02 Rank order 0105 5th largest 80020105

80 Settlements 02 Rank order 0106 6th largest 80020106

80 Settlements 02 Rank order 0107 7th largest 80020107

80 Settlements 02 Rank order 0108 8th largest 80020108

80 Settlements 02 Rank order 0109 9th largest 80020109

80 Settlements 02 Rank order 0110 10th largest 80020110

80 Settlements 02 Rank order 0111 11th largest 80020111

80 Settlements 02 Rank order 0112 12th largest 80020112

80 Settlements 02 Rank order 0113 13th largest 80020113

80 Settlements 02 Rank order 0114 14th largest 80020114

80 Settlements 02 Rank order 0115 15th largest 80020115

80 Settlements 02 Rank order 0116 16th largest 80020116

80 Settlements 02 Rank order 0117 17th largest 80020117

80 Settlements 02 Rank order 0118 18th largest 80020118

80 Settlements 02 Rank order 0119 19th largest 80020119

80 Settlements 02 Rank order 0120 20th largest 80020120

80 Settlements 02 Rank order 0121 21th largest 80020121

80 Settlements 02 Rank order 0122 22th largest 80020122

Category SubCat Subfeature miFCode

86 Envinsa

Page 87: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

Streets

The following table shows the Streets miCodes:

80 Settlements 02 Rank order 0124 23th largest 80020123

80 Settlements 02 Rank order 0124 24th largest 80020124

80 Settlements 03 Purpose 0100 Commercial 80030100

80 Settlements 03 Purpose 0110 Agricultural 80030110

80 Settlements 03 Purpose 0120 Rail head 80030120

80 Settlements 03 Purpose 0130 Port 80030130

80 Settlements 03 Purpose 0200 Military 80030200

80 Settlements 03 Purpose 0300 Frontier 80030300

80 Settlements 03 Purpose 0400 Service 80030400

Category SubCat Subfeature miFCode

20 Streets 01 Limited access/Motorways 0000 Freeway 20010000

20 Streets 01 Limited access/Motorways 0010 Freeway (part of Toll road) 20010010

20 Streets 01 Limited access/Motorways 0100 Multi-carriageway 20010100

20 Streets 01 Limited access/Motorways 0110 Multi-carriageway (part of Toll road) 20010110

20 Streets 01 Limited access/Motorways 0200 Single carriageway 20010200

20 Streets 01 Limited access/Motorways 0210 Single carriageway (part of Toll road) 20010210

20 Streets 01 Limited access/Motorways 0300 Roundabout/Traffic circle 20010300

20 Streets 01 Limited access/Motorways 0301 Special traffic feature 20010301

20 Streets 01 Limited access/Motorways 0310 Roundabout/Traffic circle (part of Toll road)

20010310

20 Streets 01 Limited access/Motorways 0311 Special traffic feature (part of Toll road) 20010311

20 Streets 01 Limited access/Motorways 0400 Slip road/ramp 20010400

Category SubCat Subfeature miFCode

2008.10 Data Guide 87

Page 88: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Streets

20 Streets 01 Limited access/Motorways 0401 Motorway to motorway ramp 20010401

20 Streets 01 Limited access/Motorways 0402 Motorway to secondary ramp 20010402

20 Streets 01 Limited access/Motorways 0410 Slip road/ramp (part of Toll road) 20010410

20 Streets 01 Limited access/Motorways 0411 Motorway to motorway ramp (part of Toll road)

20010411

20 Streets 01 Limited access/Motorways 0412 Motorway to secondary ramp (part of Toll road)

20010412

20 Streets 01 Limited access/Motorways 1000 Part of a bridge 20011000

20 Streets 01 Limited access/Motorways 1010 Part of a bridge (part of toll road) 20011010

20 Streets 01 Limited access/Motorways 1100 Part of a tunnel 20011100

20 Streets 01 Limited access/Motorways 1110 Part of a tunnel (part of toll road) 20011110

20 Streets 01 Limited access/Motorways 1200 Part of a causeway/dike/levee 20011200

20 Streets 01 Limited access/Motorways 1210 Part of a Causeway/dike/levee (part of toll road)

20011210

20 Streets 02 Major road 0000 Highway 20020000

20 Streets 02 Major road 0010 Highway (part of toll road) 20020010

20 Streets 02 Major road 0100 Multi-carriageway 20020100

20 Streets 02 Major road 0110 Multi-carriageway (part of toll road) 20020110

20 Streets 02 Major road 0200 Single carriageway 20020200

20 Streets 02 Major road 0210 Single carriageway (part of toll road) 20020210

20 Streets 02 Major road 0300 Roundabout/Traffic circle 20020300

20 Streets 02 Major road 0301 Special traffic feature 20020301

20 Streets 02 Major road 0310 Roundabout/Traffic circle (part of toll road)

20020310

20 Streets 02 Major road 0311 Special traffic feature (part of toll road) 20020311

20 Streets 02 Major road 0400 Slip road/Ramp 20020400

20 Streets 02 Major road 0401 Connector to non-motorway 20020401

20 Streets 02 Major road 0402 Connector to motorway 20020402

Category SubCat Subfeature miFCode

88 Envinsa

Page 89: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

20 Streets 02 Major road 0410 Slip road/Ramp (part of toll road) 20020410

20 Streets 02 Major road 0411 Connector to non-motorway (part of Toll road)

20020411

20 Streets 02 Major road 0412 Connector to motorway (part of Toll road)

20020412

20 Streets 02 Major road 0500 Service road 20020500

20 Streets 02 Major road 1000 Part of a bridge 20021000

20 Streets 02 Major road 1010 Part of a bridge (part of toll road) 20021010

20 Streets 02 Major road 1100 Part of a tunnel 20021100

20 Streets 02 Major road 1110 Part of a tunnel (part of toll road) 20021110

20 Streets 02 Major road 1200 Part of a causeway/dike/levee 20021200

20 Streets 02 Major road 1210 Part of a causeway/dike/levee (part of toll road)

20021210

20 Streets 03 Regional Connectors 0000 Main road 20030000

20 Streets 03 Regional Connectors 0000 Main road (part of Toll road) 20030010

20 Streets 03 Regional Connectors 0100 Multi-carriageway 20030100

20 Streets 03 Regional Connectors 0100 Multi-carriageway (part of Toll road) 20030110

20 Streets 03 Regional connectors 0200 Single carriageway 20030200

20 Streets 03 Regional connectors 0200 Single carriageway (part of Toll road) 20030210

20 Streets 03 Regional connectors 0300 Roundabout/Traffic circle 20030300

20 Streets 03 Regional connectors 0301 Special traffic feature 20030301

20 Streets 03 Regional connectors 0300 Roundabout/Traffic circle (part of toll road)

20030310

20 Streets 03 Regional connectors 0301 Special traffic feature (part of toll road) 20030311

20 Streets 03 Regional connectors 0400 Slip road/Ramp 20030400

20 Streets 03 Regional connectors 0401 Connector to non-motorway 20030401

20 Streets 03 Regional connectors 0402 Connector to motorway 20030402

20 Streets 03 Regional connectors 0400 Slip road/Ramp (part of toll road) 20030410

Category SubCat Subfeature miFCode

2008.10 Data Guide 89

Page 90: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Streets

20 Streets 03 Regional connectors 0401 Connector to non-motorway (part of toll road)

20030411

20 Streets 03 Regional connectors 0402 Connector to motorway (part of toll road)

20030412

20 Streets 03 Regional connectors 0500 Service road 20030500

20 Streets 03 Regional connectors 1000 Part of a bridge 20031000

20 Streets 03 Regional connectors 1010 Part of a bridge (part of toll road) 20031010

20 Streets 03 Regional connectors 1100 Part of a tunnel 20031100

20 Streets 03 Regional connectors 1110 Part of a Tunnel (part of toll road) 20031110

20 Streets 03 Regional connectors 1200 Part of a causeway/dike/levee 20031200

20 Streets 03 Regional connectors 1210 Part of a causeway/dike/levee (part of toll road)

20031210

20 Streets 04 Secondary roads 0000 Road 20040000

20 Streets 04 Secondary roads 0100 Multi-carriageway 20040100

20 Streets 04 Secondary roads 0200 Single carriageway 20040200

20 Streets 04 Secondary roads 0300 Roundabout/Traffic circle 20040300

20 Streets 04 Secondary roads 0301 Special traffic feature 20040301

20 Streets 04 Secondary roads 0400 Slip road/Ramp 20040400

20 Streets 04 Secondary roads 0401 Connector to non-motorway 20040401

20 Streets 04 Secondary roads 0402 Connector to motorway 20040402

20 Streets 04 Secondary roads 0500 Service road 20040500

20 Streets 04 Secondary roads 0600 Car park entrance/exit 20040600

20 Streets 04 Secondary roads 1000 Part of a bridge 20041000

20 Streets 04 Secondary roads 1100 Part of a tunnel 20041100

20 Streets 04 Secondary roads 1200 Part of a causeway/dike/levee 20041200

20 Streets 05 Local connectors 0000 Road 20050000

20 Streets 05 Local connectors 0100 Multi-carriageway 20050100

20 Streets 05 Local connectors 0200 Single carriageway 20050200

Category SubCat Subfeature miFCode

90 Envinsa

Page 91: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

20 Streets 05 Local connectors 0300 Roundabout/Traffic circle 20050300

20 Streets 05 Local connectors 0301 Special traffic feature 20050301

20 Streets 05 Local connectors 0400 Slip road/Ramp 20050400

20 Streets 05 Local connectors 0401 Connector lane 20050401

20 Streets 05 Local connectors 0500 Service road 20050500

20 Streets 05 Local connectors 0600 Car park entrance/exit 20050600

20 Streets 05 Local connectors 0700 Pedestrian zone 20050700

20 Streets 05 Local connectors 1000 Part of a bridge 20051000

20 Streets 05 Local Connectors 1100 Part of a Tunnel 20051100

20 Streets 05 Local Connectors 1200 Part of a Causeway/Dike/Levee 20051200

20 Streets 06 Local road high importance 0000 Road 20060000

20 Streets 06 Local road high importance 0100 Multi-carriageway 20060100

20 Streets 06 Local road high importance 0200 Single carriageway 20060200

20 Streets 06 Local road high importance 0300 Roundabout/Traffic circle 20060300

20 Streets 06 Local road high importance 0301 Special traffic feature 20060301

20 Streets 06 Local road high importance 0400 Slip road/Ramp 20060400

20 Streets 06 Local road high importance 0401 Connector lane 20060401

20 Streets 06 Local road high importance 0500 Service road 20060500

20 Streets 06 Local road high importance 0600 Car park entrance/exit 20060600

20 Streets 06 Local road high importance 0700 Pedestrian zone 20060700

20 Streets 06 Local road high importance 1000 Part of a Bridge 20061000

20 Streets 06 Local road high importance 1100 Part of a Tunnel 20061100

20 Streets 06 Local road high importance 1200 Part of a Causeway/Dike/Levee 20061200

20 Streets 07 Local roads 0000 Road 20070000

20 Streets 07 Local roads 0100 Multi-carriageway 20070100

20 Streets 07 Local roads 0200 Single carriageway 20070200

Category SubCat Subfeature miFCode

2008.10 Data Guide 91

Page 92: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Streets

20 Streets 07 Local roads 0300 Roundabout/Traffic circle 20070300

20 Streets 07 Local roads 0301 Special traffic feature 20070301

20 Streets 07 Local roads 0400 Slip road/Ramp 20070400

20 Streets 07 Local roads 0401 Connector lane 20070401

20 Streets 07 Local roads 0500 Service road 20070500

20 Streets 07 Local roads 0600 Car park entrance/exit 20070600

20 Streets 07 Local roads 0700 Pedestrian zone 20070700

20 Streets 07 Local roads 0800 Car park 20070800

20 Streets 07 Local roads 0900 Local access 20070900

20 Streets 07 Local roads 1000 Part of a bridge 20071000

20 Streets 07 Local roads 1100 Part of a tunnel 20071100

20 Streets 07 Local roads 1200 Part of a causeway/dike/levee 20071200

20 Streets 08 Local minor roads 0000 Road 20080000

20 Streets 08 Local minor roads 0100 Multi-carriageway 20080100

20 Streets 08 Local minor roads 0200 Single carriageway 20080200

20 Streets 08 Local minor roads 0300 Roundabout/Traffic circle 20080300

20 Streets 08 Local minor roads 0301 Special traffic feature 20080301

20 Streets 08 Local minor roads 0400 Slip road/Ramp 20080400

20 Streets 08 Local minor roads 0401 Connector lane 20080401

20 Streets 08 Local minor roads 0500 Service road 20080500

20 Streets 08 Local minor roads 0600 Car park entrance/exit 20080600

20 Streets 08 Local minor roads 0700 Pedestrian zone 20080700

20 Streets 08 Local minor roads 0800 Car park 20080800

20 Streets 08 Local minor roads 0900 Local access 20080900

20 Streets 08 Local minor roads 0910 Alley 20080910

20 Streets 08 Local minor roads 0920 Cul-de-Sac 20080920

Category SubCat Subfeature miFCode

92 Envinsa

Page 93: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

Water

The following table shows the Water miCodes:

20 Streets 08 Local minor roads 1000 Part of a bridge 20081000

20 Streets 08 Local minor roads 1100 Part of a tunnel 20081100

20 Streets 08 Local minor roads 1200 Part of a causeway/dike/levee 20081200

20 Streets 09 Other roads 0000 Other Thoroughfares 20090000

20 Streets 09 Other roads 0100 Vehicular Trail 20090100

20 Streets 09 Other roads 0200 Back road 20090200

20 Streets 09 Other roads 0210 Paved road 20090210

20 Streets 09 Other roads 0220 Unpaved road 20090220

20 Streets 09 Other roads 0221 Tractor lane 20090221

20 Streets 09 Other roads 0300 Paths 20090300

20 Streets 09 Other roads 0310 Walkways 20090310

20 Streets 09 Other roads 0311 Pedestrian bridge 20090311

20 Streets 09 Other roads 0312 Pedestrian tunnel 20090312

20 Streets 09 Other roads 0313 Hiker’s trail 20090313

20 Streets 09 Other roads 0400 Address area 20090400

20 Streets 09 Other roads 0500 Intersection construction segment 20090500

20 Streets 09 Other roads 0600 Routing construction segment 20090600

20 Streets 09 Other roads 0700 Proposed/Planned/Paper road 20090700

Category SubCat Subfeature miFCode

30 Hydrography 01 Coastline 0100 Shoreline 30010100

30 Hydrography 02 Flowing 0100 Rivers 30020100

30 Hydrography 02 Flowing 0110 Major rivers 30020110

Category SubCat Subfeature miFCode

2008.10 Data Guide 93

Page 94: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Water

30 Hydrography 02 Flowing 0120 Minor rivers 30020120

30 Hydrography 02 Flowing 0121 Braided stream, river or slough 30020121

30 Hydrography 02 Flowing 0200 Canal 30020200

30 Hydrography 02 Flowing 0300 Aquaduct 30020300

30 Hydrography 02 Flowing 0400 Pipe/Channel 30020400

30 Hydrography 02 Flowing 0410 Ditch 30020410

30 Hydrography 03 Lakes 0100 Lake 30030100

30 Hydrography 03 Lakes 0110 Major Lake 30030110

30 Hydrography 03 Lakes 0120 Minor Lake 30030120

30 Hydrography 03 Lakes 0200 Pond 30030200

30 Hydrography 03 Lakes 0300 Reservoir 30030300

30 Hydrography 03 Lakes 0301 Perennial reservoir 30030301

30 Hydrography 03 Lakes 0302 Intermittent reservoir 30030302

30 Hydrography 04 Sea/Ocean 0100 Ocean 30040100

30 Hydrography 04 Sea/Ocean 0200 Sea 30040200

30 Hydrography 04 Sea/Ocean 0300 Bay 30040300

30 Hydrography 04 Sea/Ocean 0400 Gulf 30040400

30 Hydrography 04 Sea/Ocean 0500 Sound 30040500

30 Hydrography 04 Sea/Ocean 0600 Estuary 30040600

30 Hydrography 05 Special 0100 Glacier 30050100

30 Hydrography 05 Special 0200 Quarry 30050200

30 Hydrography 05 Special 0300 Harbor 30050300

30 Hydrography 05 Special 0400 Strait 30050400

30 Hydrography 05 Special 0500 Dam 30050500

30 Hydrography 05 Special 0600 marsh/swamp 30050600

30 Hydrography 05 Special 0700 sump 30050700

Category SubCat Subfeature miFCode

94 Envinsa

Page 95: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix B: miCodes

30 Hydrography 05 Special 0800 Undefined 30050800

30 Hydrography 05 Special 0900 Custom water feature 30050900

Category SubCat Subfeature miFCode

2008.10 Data Guide 95

Page 96: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Water

96 Envinsa

Page 97: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

C

Map Layer Display Settings

This section lists the layer names and descriptions for high, medium, and low map display settings.

In this section:

Layer Names and Descriptions . . . . . . . . . . . . . . . . . . . . . .98High Map Display Settings. . . . . . . . . . . . . . . . . . . . . . . . .100Medium Map Display Settings . . . . . . . . . . . . . . . . . . . . . .103Low Map Display Settings . . . . . . . . . . . . . . . . . . . . . . . . .106

Page 98: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Layer Names and Descriptions

Layer Names and Descriptions

This table provides a list of the layer names and their descriptions:

Table Name Layer Name Layer Description

wnagz7.tab City7 Comprehensive city layer. All Municipalities regardless of Population.Appropriate for detailed (<30 mile) zoom levels.

wnagz6.tab City6 Cities for metropolitan area viewing. Appropriate for 30-50 mile zoom levels.

wnagz5.tab City5 Cities for county-level viewing. Appropriate for 50-125 mile zoom levels.

wnagz4.tab City4 Major cities for sub-state level viewing. Appropriate for 125-400 mile zoom levels.

wnagz3.tab City3 Major cities for state level viewing. Appropriate for 400-750 mile zoom levels.

wnagz2.tab City2 Major cities in each metropolitan statistical area.Appropriate for regional (750-2500 mile zoom level) viewing.

wnagz1.tab City1 Capitals and Major Cities.Appropriate for nationwide (2500-5000 mile zoom level) viewing.

wna_ow OneWay Label theme to show one way street symbols.

wnalk.tab Landmarks Features of local, regional or national interest.

wnay1.tab HwyShld1 Sub National Highway and other highway shields (0-5 miles).

wnay2.tab HwyShld2 Sub National and other highway shields (5-15 miles).

wnay3.tab HwyShld3 Sub National highway and other highway shields (15-50 miles).

wnay4.tab HwyShld4 Sub National and other highway shields (50-100 miles).

wnax1.tab IntShld1 Major/National Motor/Highway shields (0-5 miles).

wnax2.tab IntShld2 Major/National Motor/Highway shields (5-15 miles).

98 Envinsa

Page 99: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix C: Map Layer Display Settings

wnax3.tab IntShld3 Major/National Motor/Highway shields (15-50 miles).

wnax4.tab IntShld4 Major/National Motor/Highway shields (50-150 miles).

wnax5.tab IntShld5 Major/National Motor/Highway shields (150-250 miles).

wnax6.tab IntShld6 Major/National Motor/Highway shields (250-400 miles).

wnax7.tab IntShld7 Major/National Motor/Highway shields (400-750 miles).

wnax8.tab IntShld8 Major/National Motor/Highway shields (750-1250 miles).

wnab1.tab SubnationalBdr Sub national borders. For example, state, territory, province, standard, region, bundesland.

wnad1_m.tab HwyPrim_mediumScale Primary highways: medium scale.

wnad1_s.tab HwyPrim_smallScale Major roads: small scale.

wna_d1.tab HwyPrim_largeScale Primary highways.

wna_d2.tab HwySec_largeScale Major roads.

wna_d3.tab HwyMajRd_largeScale Secondary roads.

wna_d4.tab Streets_largeScale Local roads.

wnafy.tab Ferries Ferries.

wnab0_s.tab InternationalBdr_smallScale National borders: small scale.

wnab0_l.tab InternationalBdr_largeScale National borders: large scale.

wnamw_s.tab MajorWater_smallScale Major water boundaries: small scale

wnamw_m.tab MajorWater_mediumScale Major water boundaries: medium scale

wnawb_l WaterBodies_largeScale Water boundaries: large Scale.

wnald_s.tab LandUseAreas_smallScale Land use: small scale.

wnald_m.tab Not Present Land use: medium scale.

wnald.tab LandUseAreas_largeScale Land use.

Table Name Layer Name Layer Description

2008.10 Data Guide 99

Page 100: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

High Map Display Settings

High Map Display Settings

This table lists the high map display settings:

wnaua_l.tab UrbanAreas Urban areas: Large Scale.

wnaua_s.tab UrbanAreas Urban areas: Small Scale.

wnap2.tab SecondSubnationalPt Country secondary sub national points. For example, state, territory, province, standard, region, bundesland.

wnab2_l.tab Not Present Country secondary sub national borders. For example, state, territory, province, standard, region, bundesland. Large scale.

wnab2_s.tab SecondSubnationalBdr Country secondary sub national borders. For example, state, territory, province, standard, region, bundesland. Small scale.

wnaa1.tab NationalArea Country sub national boundaries. For example, state, territory, province, standard, region, bundesland.

wnaa2_l.tab SecondarySubnationalArea_largeScale

Second order subnational boundaries. For example, county and census boundaries. Large scale.

wnaa2_s.tab SecondarySubnationalArea_smallScale

Second order subnational boundaries. For example, county and census boundaries. Small scale.

wnaa4p.tab MunicipalArea_labels Municipal label points.

wlda0.tab World World boundaries.

ocean.tab Ocean Background ocean layer.

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

wnagz7.tab 0.00 30.00 9093 TRUE 0.00 30.00 mile

wnagz6.tab 30.00 50.00 9093 TRUE 30.00 50.00 mile

wnagz5.tab 50.00 125.00 9093 TRUE 50.00 125.00 mile

Table Name Layer Name Layer Description

100 Envinsa

Page 101: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix C: Map Layer Display Settings

wnagz4.tab 125.00 400.00 9093 TRUE 125.00 400.00 mile

wnagz3.tab 400.00 750.00 9093 TRUE 400.00 750.00 mile

wnagz2.tab 750.00 2499.99 9093 TRUE 750.00 2499.99 mile

wnagz1.tab 2499.99 4999.99 9093 TRUE 2499.99 4999.99 mile

wnalk.tab 0.00 5.00 9093 TRUE 0.00 6.44 kilometer

wnay1.tab 0.00 5.00 9093 TRUE 0.00 5.00 mile

wnay2.tab 5.00 15.00 9093 TRUE 5.00 15.00 mile

wnay3.tab 15.00 50.00 9093 TRUE 15.00 50.00 mile

wnay4.tab 50.00 150.00 9093 TRUE 50.00 150.00 mile

wnax1.tab 0.00 5.00 9093 TRUE 0.00 5.00 mile

wnax2.tab 5.00 15.00 9093 TRUE 5.00 15.00 mile

wnax3.tab 15.00 50.00 9093 TRUE 15.00 50.00 mile

wnax4.tab 50.00 150.00 9093 TRUE 50.00 150.00 mile

wnax5.tab 150.00 250.00 9093 TRUE 150.00 250.00 mile

wnax6.tab 250.00 400.00 9093 TRUE 250.00 400.00 mile

wnax7.tab 400.00 750.00 9093 TRUE 400.00 750.00 mile

wnax8.tab 750.00 1250.00 9093 TRUE 750.00 1250.00 mile

wnab1.tab 0.00 50.00 9093 FALSE 0.00 0.00 mile

wnab1.tab 50.00 600.00 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 1500.00 2999.99 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 250.00 1500.00 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 150.00 250.00 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 150.00 250.00 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 150.00 250.00 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 150.00 250.00 9093 FALSE 0.00 0.00 mile

wna_d1.tab 2.50 150.00 9093 FALSE 0.00 0.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

2008.10 Data Guide 101

Page 102: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

High Map Display Settings

wna_d1.tab 2.50 150.00 9093 TRUE 4.02 9.66 kilometer

wna_d1.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d1.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d2.tab 2.50 150.00 9093 TRUE 4.02 9.66 kilometer

wna_d2.tab 2.50 150.00 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d3.tab 2.50 50.00 9093 TRUE 4.02 9.66 kilometer

wna_d3.tab 2.50 50.00 9093 TRUE 4.02 9.66 kilometer

wna_d3.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d3.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wna_d4.tab 0.00 2.50 9093 TRUE 0.00 4.02 kilometer

wna_d4.tab 0.00 2.50 9093 FALSE 0.00 0.00 kilometer

wna_d4.tab 2.50 10.00 9093 FALSE 0.00 0.00 mile

wnarw_m.tab 0.00 5.00 9093 FALSE 0.00 0.00 mile

wnafy.tab 0.00 20.00 9093 FALSE 0.00 0.00 mile

wnawr_m.tab 30.00 150.00 9093 FALSE 0.00 0.00 mile

wnawr.tab 0.00 20.00 9093 TRUE 0.00 5.00 mile

wnab0_s.tab 600.00 99999.75 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 600.00 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 600.00 9093 FALSE 0.00 0.00 mile

wnamw_s.tab 30.00 750.00 9093 TRUE 48.28 482.80 kilometer

wnamw_m.tab 30.00 250.00 9093 TRUE 48.28 128.75 kilometer

wnawb_l.tab 0.00 15.00 9093 TRUE 0.00 24.14 kilometer

wnald_s.tab 40.00 600.00 9093 TRUE 16.09 804.67 kilometer

wnald_m.tab 40.00 75.00 9093 TRUE 50.00 75.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

102 Envinsa

Page 103: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix C: Map Layer Display Settings

*Zoom settings have been rounded to the nearest 100th.

Medium Map Display Settings

This lists the medium map display settings:

wnald.tab 0.00 40.00 9093 TRUE 0.00 40.00 mile

wnab1.tab 0.00 600.00 9093 FALSE 0.00 0.00 mile

wnaua_s.tab 50.00 600.00 9093 FALSE 0.00 0.00 mile

wnap2.tab 100.10 600.00 9093 TRUE 193.12 402.34 kilometer

wnab2_l.tab 0.00 100.00 9093 FALSE 0.00 0.00 kilometer

wnab2_s.tab 100.10 600.00 9093 FALSE 0.00 0.00 kilometer

wnaa1.tab 200.00 1000000.00 9093 TRUE 600 6000 mile

wlda0.tab 0.00 - FALSE 0.00 0.00 mile

ocean.tab 0.00 - FALSE 0.00 0.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

wnagz7.tab 0.00 15.00 9093 TRUE 0.00 15.00 mile

wnagz6.tab 15.00 25.00 9093 TRUE 15.00 25.00 mile

wnagz5.tab 25.00 62.50 9093 TRUE 25.00 62.50 mile

wnagz4.tab 62.50 200.00 9093 TRUE 62.50 200.00 mile

wnagz3.tab 200.00 375.00 9093 TRUE 200.00 375.00 mile

wnagz2.tab 375.00 1250.00 9093 TRUE 375.00 1250.00 mile

wnagz1.tab 1250.00 2499.99 9093 TRUE 1250.00 2499.99 mile

wnalk.tab 0.00 2.50 9093 TRUE 0.00 3.22 kilometer

wnay1.tab 0.00 2.50 9093 TRUE 0.00 2.50 mile

wnay2.tab 2.50 7.50 9093 TRUE 2.50 7.50 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

2008.10 Data Guide 103

Page 104: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Medium Map Display Settings

wnay3.tab 7.50 25.00 9093 TRUE 7.50 25.00 mile

wnay4.tab 25.00 75.00 9093 TRUE 25.00 75.00 mile

wnax1.tab 0.00 2.50 9093 TRUE 0.00 2.50 mile

wnax2.tab 2.50 7.50 9093 TRUE 2.50 7.50 mile

wnax3.tab 7.50 25.00 9093 TRUE 7.50 25.00 mile

wnax4.tab 25.00 75.00 9093 TRUE 25.00 75.00 mile

wnax5.tab 75.00 125.00 9093 TRUE 75.00 125.00 mile

wnax6.tab 125.00 200.00 9093 TRUE 125.00 200.00 mile

wnax7.tab 200.00 375.00 9093 TRUE 200.00 375.00 mile

wnax8.tab 375.00 625.00 9093 TRUE 375.00 625.00 mile

wnab1.tab 0.00 25.00 9093 FALSE 0.00 0.00 mile

wnab1.tab 25.00 300.00 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 750.00 1500.00 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 125.00 750.00 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 75.00 125.00 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 75.00 125.00 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 75.00 125.00 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 75.00 125.00 9093 FALSE 0.00 0.00 mile

wna_d1.tab 1.25 75.00 9093 FALSE 0.00 0.00 mile

wna_d1.tab 1.25 75.00 9093 TRUE 2.01 4.83 kilometer

wna_d1.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

wna_d1.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

wna_d2.tab 1.25 75.00 9093 TRUE 2.01 4.83 kilometer

wna_d2.tab 1.25 75.00 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

104 Envinsa

Page 105: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix C: Map Layer Display Settings

wna_d3.tab 1.25 25.00 9093 TRUE 2.01 4.83 kilometer

wna_d3.tab 1.25 25.00 9093 TRUE 2.01 4.83 kilometer

wna_d3.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

wna_d3.tab 0.00 1.25 9093 FALSE 0.00 0.00 mile

wna_d4.tab 0.00 1.25 9093 TRUE 0.00 2.01 kilometer

wna_d4.tab 0.00 1.25 9093 FALSE 0.00 0.00 kilometer

wna_d4.tab 1.25 5.00 9093 FALSE 0.00 0.00 mile

wnarw_m.tab 0.00 2.50 9093 FALSE 0.00 0.00 mile

wnafy.tab 0.00 10.00 9093 FALSE 0.00 0.00 mile

wnawr.tab 0.00 10.00 9093 TRUE 0.00 2.50 mile

wnab0_s.tab 300.00 49999.88 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 300.00 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 300.00 9093 FALSE 0.00 0.00 mile

wnamw_s.tab 15.00 375.00 9093 TRUE 24.14 241.40 kilometer

wnamw_m.tab 15.00 125.00 9093 TRUE 24.14 64.37 kilometer

wnawb_l.tab 0.00 7.50 9093 TRUE 0.00 12.07 kilometer

wnald_s.tab 20.00 300.00 9093 TRUE 8.05 402.34 kilometer

wnald_m.tab 20.00 37.50 9093 TRUE 25.00 37.50 mile

wnald.tab 0.00 20.00 9093 TRUE 0.00 20.00 mile

wnab1.tab 0.00 300.00 9093 FALSE 0.00 0.00 mile

wnaua_s.tab 25.00 300.00 9093 FALSE 0.00 0.00 mile

wnap2.tab 50.05 300.00 9093 TRUE 96.56 201.17 kilometer

wnab2_l.tab 0.00 50.00 9093 FALSE 0.00 0.00 kilometer

wnab2_s.tab 50.05 300.00 9093 FALSE 0.00 0.00 kilometer

wnaa1.tab 200.00 1000000.00 9093 TRUE 600 6000 mile

wlda0.tab 0.00 - FALSE 0.00 0.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

2008.10 Data Guide 105

Page 106: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Low Map Display Settings

*Zoom settings have been rounded to the nearest 100th.

Low Map Display Settings

This lists the low map display settings:

ocean.tab 0.00 - FALSE 0.00 0.00 mile

Table Name

Minimum Zoom

Maximum Zoom

EPSGCode Labeled MinLabel MaxLabel Unit

wnagz7.tab 0.00 7.50 9093 TRUE 0.00 7.50 mile

wnagz6.tab 7.50 12.50 9093 TRUE 7.50 12.50 mile

wnagz5.tab 12.50 31.25 9093 TRUE 12.50 31.25 mile

wnagz4.tab 31.25 100.00 9093 TRUE 31.25 100.00 mile

wnagz3.tab 100.00 187.50 9093 TRUE 100.00 187.50 mile

wnagz2.tab 187.50 625.00 9093 TRUE 187.50 625.00 mile

wnagz1.tab 625.00 1250.00 9093 TRUE 625.00 1250.00 mile

wnalk.tab 0.00 1.25 9093 TRUE 0.00 1.61 kilometer

wnay1.tab 0.00 1.25 9093 TRUE 0.00 1.25 mile

wnay2.tab 1.25 3.75 9093 TRUE 1.25 3.75 mile

wnay3.tab 3.75 12.50 9093 TRUE 3.75 12.50 mile

wnay4.tab 12.50 37.50 9093 TRUE 12.50 37.50 mile

wnax1.tab 0.00 1.25 9093 TRUE 0.00 1.25 mile

wnax2.tab 1.25 3.75 9093 TRUE 1.25 3.75 mile

wnax3.tab 3.75 12.50 9093 TRUE 3.75 12.50 mile

wnax4.tab 12.50 37.50 9093 TRUE 12.50 37.50 mile

wnax5.tab 37.50 62.50 9093 TRUE 37.50 62.50 mile

wnax6.tab 62.50 100.00 9093 TRUE 62.50 100.00 mile

TableName

Minimum Zoom

Maximum Zoom

EPSG Code Labeled MinLabel MaxLabel Unit

106 Envinsa

Page 107: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Appendix C: Map Layer Display Settings

wnax7.tab 100.00 187.50 9093 TRUE 100.00 187.50 mile

wnax8.tab 187.50 312.50 9093 TRUE 187.50 312.50 mile

wnab1.tab 0.00 12.50 9093 FALSE 0.00 0.00 mile

wnab1.tab 12.50 150.00 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 375.00 750.00 9093 FALSE 0.00 0.00 mile

wnad1_s.tab 62.50 375.00 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 37.50 62.50 9093 FALSE 0.00 0.00 mile

wnad1_m.tab 37.50 62.50 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 37.50 62.50 9093 FALSE 0.00 0.00 mile

wnad2_s.tab 37.50 62.50 9093 FALSE 0.00 0.00 mile

wna_d1.tab 0.62 37.50 9093 FALSE 0.00 0.00 mile

wna_d1.tab 0.62 37.50 9093 TRUE 1.01 2.41 kilometer

wna_d1.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d1.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.62 37.50 9093 TRUE 1.01 2.41 kilometer

wna_d2.tab 0.62 37.50 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d2.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d3.tab 0.62 12.50 9093 TRUE 1.01 2.41 kilometer

wna_d3.tab 0.62 12.50 9093 TRUE 1.01 2.41 kilometer

wna_d3.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d3.tab 0.00 0.62 9093 FALSE 0.00 0.00 mile

wna_d4.tab 0.00 0.62 9093 TRUE 0.00 1.01 kilometer

wna_d4.tab 0.00 0.62 9093 FALSE 0.00 0.00 kilometer

wna_d4.tab 0.62 2.50 9093 FALSE 0.00 0.00 mile

wnafy.tab 0.00 5.00 9093 FALSE 0.00 0.00 mile

Table Name

Minimum Zoom

Maximum Zoom

EPSGCode Labeled MinLabel MaxLabel Unit

2008.10 Data Guide 107

Page 108: Envinsa Data Guide - Pitney Bowesreference1.mapinfo.com/software/envinsa/english/4_3_1/data/2008_10_Data_Guide.pdf · 2008.10 Data Guide 7 Data Component List ... DataDomain\US_CA\Routing.Pedestrian

Low Map Display Settings

*Zoom settings have been rounded to the nearest 100th.

wnab0_s.tab 150.00 24999.94 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 150.00 9093 FALSE 0.00 0.00 mile

wnab0_l.tab 0.00 150.00 9093 FALSE 0.00 0.00 mile

wnamw_s.tab 7.50 187.50 9093 TRUE 12.07 120.70 kilometer

wnamw_m.tab 7.50 62.50 9093 TRUE 12.07 32.19 kilometer

wnawb_l.tab 0.00 3.75 9093 TRUE 0.00 6.04 kilometer

wnald_s.tab 10.00 150.00 9093 TRUE 4.02 201.17 kilometer

wnald_m.tab 10.00 18.75 9093 TRUE 12.50 18.75 mile

wnald.tab 0.00 10.00 9093 TRUE 0.00 10.00 mile

wnab1.tab 0.00 150.00 9093 FALSE 0.00 0.00 mile

wnaua_s.tab 0.00 150.00 9093 FALSE 0.00 0.00 mile

wnap2.tab 25.02 150.00 9093 TRUE 48.28 100.58 kilometer

wnab2_l.tab 0.00 25.00 9093 FALSE 0.00 0.00 kilometer

wnab2_s.tab 25.02 150.00 9093 FALSE 0.00 0.00 kilometer

wnaa1.tab 200.00 1000000.00 9093 TRUE 600 6000 mile

wlda0.tab 0.00 - FALSE 0.00 0.00 mile

ocean.tab 0.00 - FALSE 0.00 0.00 mile

Table Name

Minimum Zoom

Maximum Zoom

EPSGCode Labeled MinLabel MaxLabel Unit

108 Envinsa