0% found this document useful (0 votes)
291 views

Address Data Model

The document discusses the ArcGIS Address Data Model, which provides a template for creating a geodatabase schema to model address data. It describes key concepts like streets having multiple names and address ranges, and features being associated with multiple addresses. It covers loading data into the model, customizing it, editing addresses, geocoding, and visualizing errors. The template allows for complex relationships between addresses and other geographic entities to be modeled in a normalized way.

Uploaded by

tenoriom
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
291 views

Address Data Model

The document discusses the ArcGIS Address Data Model, which provides a template for creating a geodatabase schema to model address data. It describes key concepts like streets having multiple names and address ranges, and features being associated with multiple addresses. It covers loading data into the model, customizing it, editing addresses, geocoding, and visualizing errors. The template allows for complex relationships between addresses and other geographic entities to be modeled in a normalized way.

Uploaded by

tenoriom
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 36

Address Data Model

Agatha Wong
Sergey Ivanenko

UC 2007 Tech Sessions 1


Outline

• What is the ArcGIS Address Data Model?


• Key concepts
• Creating the Geodatabase schema and loading the data
• Customizing the data model
• Editing addresses
• Geocoding
• Errors visualization
• Additional resources

UC 2007 Tech Sessions 2


What is the ArcGIS Address Data Model?

• Template for creating a Geodatabase schema for


addresses
• Normalized Geodatabase schema for modeling
complexities of addresses
• Not a standard

UC 2007 Tech Sessions 3


Key Concepts

• Normalized data model


• Model complex relationships between features,
addresses, names, and zones

*
Names

* * *
Features Addresses

*
Zones

UC 2007 Tech Sessions 4


Key Concepts

• Streets can have many names

UC 2007 Tech Sessions 5


Key Concepts

• Streets can have


many names

UC 2007 Tech Sessions 6


Key Concepts

• Streets can have many address ranges and names

UC 2007 Tech Sessions 7


Street StreetHasAddressRanges
Key Concepts StreetID
1
StreetID
1
AddressRangeID Side
1 Left
Category
Official
1 2 Right Official
1 3 Left County
1 4 Right County

AddressRange
• Streets can have many AddressRangeID FromAddress ToAddress Parity
address ranges and 1 100 198 Even
names 2 101 199 Odd
3 10100 10198 Even
4 10101 10199 Odd

AddressRangesHaveNames
AddressRangeID GeoNameID Category
1 1 Official
2 1 Official
3 2 County
4 2 County

GeoName
GeoNameID FullName PrefixType BaseName SuffixType
1 Main St Main St
2 County Rd 1 County Rd 1
UC 2007 Tech Sessions 8
Key Concepts

• Features can have many addresses


ST

UC 2007 Tech Sessions 9


Key Concepts
Parcel ParcelsHaveAddresses
ParcelID ParcelID AddressID Category
1 1 1 Official
1 2 Entrance

Address
• Features can have many AddressID HouseNumber

addresses 1
2
123
120

AddressesHaveNames
AddressID GeoNameID Category
1 1 Official
2 2 Official

GeoName
GeoNameID FullName PrefixDirection BaseName SuffixType
1 E Main St E Main St
2 N 1st Ave N 1 st
Ave

UC 2007 Tech Sessions 10


Key Concepts

• Addresses can have many ZoneSets (unique and


valid combinations of zones)

UC 2007 Tech Sessions 11


Key Concepts

• Addresses can have many


ZoneSets

UC 2007 Tech Sessions 12


Demonstration

• Feature classes in shapefiles as source data


• Load data into an address data model using the Address
Management Tool (a prototype development sample)
• Navigate the ArcGIS Address Data Model
– Find the name assigned to a street
– Find the address of an object

UC 2007 Tech Sessions 13


Address Management Tool
• Create Address Data Model based on a pre-defined
schema
• Import address data
• Export address data
• Fishbone

UC 2007 Tech Sessions 14


Creating the Geodatabase Schema

• Create a blank target Geodatabase


• Download the sample Geodatabase and its schema from
support.esri.com/DataModels
• Copy the schema from the sample Geodatabase to the
target Geodatabase
– Use XMLImport in ArcCatalog or Address Management Tool
– Remember to define your spatial reference!

Import Customize Refine


Load Data
Schema Schema Schema

UC 2007 Tech Sessions 17


Customizing the Data Model

• Add fields
• Add new addressable feature classes
– e.g. Parcel feature class
• Change the set of zones
• Modify the set of name components
• Change table and field names

Import Customize Refine


Load Data
Schema Schema Schema

UC 2007 Tech Sessions 18


Loading Data

• Load data using


– ArcCatalog, ArcMap, Geoprocessing tools, scripts, models
or
– Address Management Tool

Import Customize Refine


Load Data
Schema Schema Schema

UC 2007 Tech Sessions 19


Loading Data (Method 1)

ArcMap

Geoprocessing

Target
Source Data
Geodatabase

ArcCatalog

UC 2007 Tech Sessions 20


Loading Data (Method 2)

Source Data

Target
Geodatabase

UC 2007 Tech Sessions 21


Refining the Data Model

• Refining the data model is an iterative process


– ArcCatalog tools
– ArcMap tools
– Geoprocessing tools, scripts, models

Import Customize Refine


Load Data
Schema Schema Schema

UC 2007 Tech Sessions 22


Working with the Address Data Model

UC 2007 Tech Sessions 23


Editing in Address Data Model

• Editing Addresses
– Assign an address to a feature
– Add a name to a street
– Add a name to a set of addresses

UC 2007 Tech Sessions 24


Geocoding for Address Data Model

• Custom address locator styles for Address Data Model

UC 2007 Tech Sessions 25


Errors Visualization (Fish-bones)

UC 2007 Tech Sessions 26


Demonstration

• Editing in the ArcGIS Address Data Model


– Assign an address to a feature
– Add a name to a street
– Add a name to a set of addresses

• Geocoding
– Creating locators
– Matching addresses

• Fish-boning
– Viewing address errors

UC 2007 Tech Sessions 27


Exporting the Address Data Model

• Use of de-normalized address data might be necessary


– Legacy workflow
– Third party applications

UC 2007 Tech Sessions 28


Exporting the Address Data Model:
Considerations

• For point and polygon, data export is a table join


operation
• Additional steps for street centerlines
– Convert street attributes into left/right fields depending on the
values of the “Side” attribute
– Store alternate street names in separate sets of fields

UC 2007 Tech Sessions 29


Demonstration

• Export the normalized data in the Address Data Model


into a de-normalized feature class using the Address
Management Tool

UC 2007 Tech Sessions 30


Summary

• Use the sample Geodatabase as a template


• Customize the data model
• Load existing data
• Refine the data model
• Use it for address maintenance and geocoding

UC 2007 Tech Sessions 31


We need your feedback!

UC 2007 Tech Sessions 32


Resources and References
• ESRI Knowledge Base and Free Downloads
– http://support.esri.com
• ESRI ArcScripts Website
– http://arcscripts.esri.com
• Geocoding Development Kit
http://edn.esri.com/index.cfm?fa=downloads.detail&downloadId=117
• ArcGIS Address Data Model and Address Management
Tools
– http://support.esri.com/DataModels
– http://support.esri.com/index.cfm?fa=downloads.dataModels.filtere
dGateway&dmid=32
• ESRI Address Management Discussion Forum
– http://forums.esri.com

UC 2007 Tech Sessions 33


Please fill out and submit your
evaluation form

UC 2007 Tech Sessions 34


Technical Session Presentation Title

Name of Presenter(s)

UC 2007 Tech Sessions 35


Successful Presentation Guidelines

• Remember your target audience


• Keep your slides uncluttered and to the point
– Only use a key phrase or a few words to reinforce your point
– 3-7 bullet points per page
– 1-5 words per bullet point
• Use several title slides for each section
– Make it clear where you are going
• Avoid too much animation
– Keep it simple

UC 2007 Tech Sessions 36


Commonly Used Icons

UC 2007 Tech Sessions 37


Commonly Used Icons

text text text

text text text

Enterprise Service Bus

Enterprise Service Bus

UC 2007 Tech Sessions 38

You might also like