[Milwaukee County Enterprise GIS Migration

Project]

[Milwaukee County Enterprise GIS Migration

Project]

presented by: Kevin White, GIS Supervisor – Milwaukee CountyScott Stocking, Systems Analyst – GeoAnalytics

presented by: Kevin White, GIS Supervisor – Milwaukee CountyScott Stocking, Systems Analyst – GeoAnalytics

Wisconsin Land Information Association Conference 2005

February 23, 2005

Wisconsin Land Information Association Conference 2005

February 23, 2005

[ Agenda ][ Agenda ]

Background Needs Assessment Geodatabase Data Model Migration Plan Current Work Plan

Background Needs Assessment Geodatabase Data Model Migration Plan Current Work Plan

[ Background: ][ Background: ]

MCAMLIS Roles SEWRPC Roles Registry of Deeds Office City of Milwaukee County emergence as the LIO

MCAMLIS Roles SEWRPC Roles Registry of Deeds Office City of Milwaukee County emergence as the LIO

[ Background: MCAMLIS Roles][ Background: MCAMLIS Roles]

The MCAMLIS Board is a public-private consortium

MCAMLIS Work Program:o PLSS maintenance and survey controlo Establish a Topographic base mapo Land Records automationo Street Address data for parcels

The MCAMLIS Board is a public-private consortium

MCAMLIS Work Program:o PLSS maintenance and survey controlo Establish a Topographic base mapo Land Records automationo Street Address data for parcels

[Background: SEWRPC Roles ][Background: SEWRPC Roles ]

When MCAMLIS was formed the County had no GIS capabilities

SEWRPC provided management and technical support to MCAMLIS Steering Committee.

This arrangement was in place from 1991 thru 2004

When MCAMLIS was formed the County had no GIS capabilities

SEWRPC provided management and technical support to MCAMLIS Steering Committee.

This arrangement was in place from 1991 thru 2004

[Background: Registry of Deeds Office ][Background: Registry of Deeds Office ]

Traditionally the County maintained paper maps in the Tax Listing Section until June 2004. These maps were considered the “official” County cadastral maps.

MCAMLIS began to maintain their cadastral maps with an employee in the ROD office.

ROD office is now moving to a GIS cadastral map. ROD office is further automating process and would

like to link their imaging system to the GIS in the future.

Traditionally the County maintained paper maps in the Tax Listing Section until June 2004. These maps were considered the “official” County cadastral maps.

MCAMLIS began to maintain their cadastral maps with an employee in the ROD office.

ROD office is now moving to a GIS cadastral map. ROD office is further automating process and would

like to link their imaging system to the GIS in the future.

[Background: City of Milwaukee ][Background: City of Milwaukee ]

City maintenance their own set of cadastral maps outside of the MCAMLIS program – and have done so since 1978

In 1998 MCAMLIS began a program to convert city maps to MCAMLIS standards

County would like bring the City maps in for a seamless countywide cadastral map.

No political push to make this happen unless the County undertakes the City Tax Listing services.

City maintenance their own set of cadastral maps outside of the MCAMLIS program – and have done so since 1978

In 1998 MCAMLIS began a program to convert city maps to MCAMLIS standards

County would like bring the City maps in for a seamless countywide cadastral map.

No political push to make this happen unless the County undertakes the City Tax Listing services.

[Background: County Emergence as the LIO ][Background: County Emergence as the LIO ]

In 2002 County approached MCAMLIS to begin the transition of management role to the County.

In September 2004, MCAMLIS approved the transfer of management to the County.

County plans to fill the role of the LIO

In 2002 County approached MCAMLIS to begin the transition of management role to the County.

In September 2004, MCAMLIS approved the transfer of management to the County.

County plans to fill the role of the LIO

[Background: County Emergence as the LIO ][Background: County Emergence as the LIO ]

Internal GIS Management. Local Government Partners Regional Partner Relationships

Internal GIS Management. Local Government Partners Regional Partner Relationships

[ Needs Assessment: ][ Needs Assessment: ]

Focus on Core Data Layers County Departments and GIS Local Government Partners Key Findings

Focus on Core Data Layers County Departments and GIS Local Government Partners Key Findings

[ Needs Assessment: Focus on Core Data Layers]

[ Needs Assessment: Focus on Core Data Layers]

County hired GeoAnalytics in 2004 to provide services developing a enterprise GIS based upon the Geodatabase model.

County focused on providing high quality data in the land records and street addressing.

The end goals is to provide a the following:o Provide a complete countywide cadastral layero Provide a sopshicated framework for a street

addressing system countywide that can incorporate local addressing needs

o Create partnerships to maintain the data and feely distribute digital products to the user community.

County hired GeoAnalytics in 2004 to provide services developing a enterprise GIS based upon the Geodatabase model.

County focused on providing high quality data in the land records and street addressing.

The end goals is to provide a the following:o Provide a complete countywide cadastral layero Provide a sopshicated framework for a street

addressing system countywide that can incorporate local addressing needs

o Create partnerships to maintain the data and feely distribute digital products to the user community.

[ Needs Assessment: County Departments and GIS]

[ Needs Assessment: County Departments and GIS]

Current GIS Utilization within County – not supporting enterprise applications.

Perceived Needs and Issues:

o Local Government input required for high quality

o Open Access to Land Records and Addressing Vision and Recommendations:

o Technical Assistance –tie operations to GIS

o Make Information Available to the Public

Current GIS Utilization within County – not supporting enterprise applications.

Perceived Needs and Issues:

o Local Government input required for high quality

o Open Access to Land Records and Addressing Vision and Recommendations:

o Technical Assistance –tie operations to GIS

o Make Information Available to the Public

[ Needs Assessment: Local Government Partners]

[ Needs Assessment: Local Government Partners]

Major Partnership with City of Milwaukee – seeking new collaboration opportunities.

Other Local Governments – being flexible in services provided

E911 Center support – County and Cities Private Utilities – continue to work closely to

exchange information via MCAMLIS

Major Partnership with City of Milwaukee – seeking new collaboration opportunities.

Other Local Governments – being flexible in services provided

E911 Center support – County and Cities Private Utilities – continue to work closely to

exchange information via MCAMLIS

[ Needs Assessment: Key Findings][ Needs Assessment: Key Findings]

No major applications dependent on GIS – left room to develop optimal Geodatabase models

Need for formal management – changes to the MCAMLIS relationship. County wanted to become an active force.

County clearly understands that they needed active local government partners to make this work.

County wanted to provide better services to the public via the use of GIS.

No major applications dependent on GIS – left room to develop optimal Geodatabase models

Need for formal management – changes to the MCAMLIS relationship. County wanted to become an active force.

County clearly understands that they needed active local government partners to make this work.

County wanted to provide better services to the public via the use of GIS.

[ Geodatabase Data Model: ][ Geodatabase Data Model: ]

Design Principals Geodatabase Model review

o Land Records Model

o Street Addressing Summary of Final Design

Design Principals Geodatabase Model review

o Land Records Model

o Street Addressing Summary of Final Design

[Geodatabase Design Model: Design Principals ][Geodatabase Design Model: Design Principals ]

Focus on key foundation layers – land records and address system

Keep the Model as simple as possible

o Very few Feature Data Sets

o Feature Classes are very simple

o Few Relationship Classes Identify key Features Classes that could be

added in the future – once the model is running.

Focus on key foundation layers – land records and address system

Keep the Model as simple as possible

o Very few Feature Data Sets

o Feature Classes are very simple

o Few Relationship Classes Identify key Features Classes that could be

added in the future – once the model is running.

[Geodatabase Data Model: Model Review ][Geodatabase Data Model: Model Review ]Tax Parcel Feature ClassesThese are the boundaries of tax parcels, subdivisions,condos and rights of ways.

The type of boundary in text

Direction is the angle between a line and an arbitrary chosen reference line

Distance is the linear measure along a line

The angle at the center of radius of a circular arc

Radius of a circular curve.

A straight line that touches a given curve at one and only one point

The length of a curve

The side of the curved element where the radius is located (L or R)

The boundary type used as a code – hooked to domain of values

Simple feature classParcelBoundary Contains Z values

Contains M valuesGeometry Polyline

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

OBJECTID Object IDSHAPE Geometry Yes

BoundaryType String Yes 16Direction String Yes 12Distance String Yes 10

Delta String Yes 10Radius String Yes 10Tangent String Yes 10

ArcLength String Yes 10Side String Yes 1

BoundaryTypeCode Long integer Yes 1 0SHAPE_Length Double Yes 0 0

TableCondoRelate

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Type a description of this featureclass or table in this placeholder text.

OBJECTID Object IDCondoTaxKey String Yes 14 Place a succinct description of the field in this text

TaxKey String Yes 14 Place a succinct description of the field in this text

Relationship class

NamePrimary keyForeign key

TypeCardinalityNotification

Forward labelBackward label

No relationship rules defined.

CondoRelate

Origin feature class Destination table

SimpleOne to manyNone

CondoTaxParcelsCondos

TaxParcelTaxKeyCondoTaxKey

CondoRelateName

Simple feature classPublicLands Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Non-Taxable publicly held lands

OBJECTID Object IDSHAPE Geometry Yes

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

TaxKey String Yes 14 The tax key number if the lands have a tax key

PLKey String Yes 20 The public lands key – a system assigned number

ManagingAgency String Yes 50 The managing agency for the lands

Leased String Yes 3 Is the land leased or not

Simple feature classHistTaxParcel Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Retired or non-current tax parcels

OBJECTID Object IDShape Geometry Yes

RetiredDate String Yes 10 The date the tax parcel was retired

GISAcres Double Yes 0 0 The area computed in the GIS

TaxKey String Yes 14 The tax key of the retired tax parcel

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0comments

sourceecode

texttexttext

YesYesYes

000

000

2555020

Comments entered by the editor

The source document

Any applicable e-code

Simple feature classTaxParcel Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

The current tax parcels

OBJECTID Object IDShape Geometry Yes

GISAcres Double Yes 0 0 The area of the tax parcel as computed in the GIS

TaxKey String Yes 14 The tax key number

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0GapOverlap String Yes 1 Y = GAP or OVERLAP – tax parcel areas that gap or overlap

Ecodecomments

source

StringStringString

YesYesYes

2025550

This code supports the current mapping environment

Comments entered by the editor

Source document

Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtypeSubtype field

SubtypeCode

Subtypes of ParcelBoundaryBoundaryTypeCode1

1 Parcelline No values set2 ExtPatLine No values set

EncumbranceType

Simple feature classCivilDivisions Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

These are municipal areas of thecounty

OBJECTID Object IDSHAPE Geometry Yes

MuniName String Yes 50 The name of the municipality

MunType String Yes T MuniTypeCode 1 The type of municipality – see domain

FIPSCode String Yes 10 The federal information system processing system code

WIDORCode String Yes 10 Wisconsin dept of revenue code

MuniID Short integer Yes 0 An identifier used for sub typing or lookup tables

MuniCode String Yes MuniCode 50 The municipal code or short abbreviation

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Coded value domain

DescriptionField type

Split policyMerge policy

Type of encumbranceStringDefault valueDefault value

DescriptionCode

Easement Easement - General

Utility Utility Easement

Conservation Conservation Easement

Ingress-Egress Ingress-Egress

Flood Flood Easement

Vacation Vacation (Road)

Other Other

RecTrail Recreation Trail

Simple feature classEasements Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Limitations on use of land – such asutility easement. This feature classdoes not include road or rail roadrights of way

OBJECTID Object IDSHAPE Geometry YesTaxKey String Yes 14 The tax key number if applicable

PLKey String Yes 20 The public lands key if applicable

EasementType String Yes 50 The type of easement, see domain of values

EasementOwner String Yes 50 The easement owner, who hold the rights to use the easement

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Simple feature classHistSimultaneousConveyance Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Portions of simultaneousconveyances that have been retired

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the simultaneous conveyance

SimConType Long integer Yes 1 0 The type of simultaneous conveyance

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0RetiredDate Date Yes 0 0 0 The date this portion of the sim con was retired

Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtypeSubtype field

SubtypeCode

Subtypes of SimultaneousConveyanceSimConType1

1 Subdivision_Plat No values set2 CSM No values set3 Condo_Plat No values set4 Assessor_Plat No values set

Simple feature classSimultaneousConveyance Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Simultaneous Conveyances are areasdefined at one time by a survey. Thisis the currently active simultaneousconveyance areas

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the simultaneous conveyance

SimConType Long integer Yes 1 0 The type of sim con used for subtyping

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

DocNo String Yes 50 Register of Deeds document number reference

The status – where is the plat in the review or approval process

Register of Deeds document number reference

Simple feature classPreliminaryPlat Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

A plat submitted for approval andreview

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the plat or condo (proposed name)

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

Status String Yes 50DocNo String Yes 50

Coded value domain

DescriptionField type

Split policyMerge policy

Type of MunicipalityStringDefault valueDefault value

DescriptionCode

T Town

V Village

C City

MuniTypeCode

EncumbranceType

Simple feature classCivilDivisions Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

These are municipal areas of thecounty

OBJECTID Object IDSHAPE Geometry Yes

MuniName String Yes 50 The name of the municipality

MunType String Yes T MuniTypeCode 1 The type of municipality – see domain

FIPSCode String Yes 10 The federal information system processing system code

WIDORCode String Yes 10 Wisconsin dept of revenue code

MuniID Short integer Yes 0 An identifier used for sub typing or lookup tables

MuniCode String Yes MuniCode 50 The municipal code or short abbreviation

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Coded value domain

DescriptionField type

Split policyMerge policy

Type of encumbranceStringDefault valueDefault value

DescriptionCode

Easement Easement - General

Utility Utility Easement

Conservation Conservation Easement

Ingress-Egress Ingress-Egress

Flood Flood Easement

Vacation Vacation (Road)

Other Other

RecTrail Recreation Trail

Simple feature classEasements Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Limitations on use of land – such asutility easement. This feature classdoes not include road or rail roadrights of way

OBJECTID Object IDSHAPE Geometry YesTaxKey String Yes 14 The tax key number if applicable

PLKey String Yes 20 The public lands key if applicable

EasementType String Yes 50 The type of easement, see domain of values

EasementOwner String Yes 50 The easement owner, who hold the rights to use the easement

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Simple feature classHistSimultaneousConveyance Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Portions of simultaneousconveyances that have been retired

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the simultaneous conveyance

SimConType Long integer Yes 1 0 The type of simultaneous conveyance

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0RetiredDate Date Yes 0 0 0 The date this portion of the sim con was retired

Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtypeSubtype field

SubtypeCode

Subtypes of SimultaneousConveyanceSimConType1

1 Subdivision_Plat No values set2 CSM No values set3 Condo_Plat No values set4 Assessor_Plat No values set

Simple feature classSimultaneousConveyance Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Simultaneous Conveyances are areasdefined at one time by a survey. Thisis the currently active simultaneousconveyance areas

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the simultaneous conveyance

SimConType Long integer Yes 1 0 The type of sim con used for subtyping

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

DocNo String Yes 50 Register of Deeds document number reference

The status – where is the plat in the review or approval process

Register of Deeds document number reference

Simple feature classPreliminaryPlat Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

A plat submitted for approval andreview

OBJECTID Object IDShape Geometry YesName String Yes 100 The name of the plat or condo (proposed name)

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

Status String Yes 50DocNo String Yes 50

Coded value domain

DescriptionField type

Split policyMerge policy

Type of MunicipalityStringDefault valueDefault value

DescriptionCode

T Town

V Village

C City

MuniTypeCode

Parcel Framework Feature Classes

CartographicFeature Classes

Simple feature classConstruct_Poly Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Type a description of this featureclass or table in this placeholder text.

OBJECTID Object IDSHAPE Geometry Yes

LEC String Yes 10 Place a succinct description of the field in this text

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Simple feature classConstruct_Line Contains Z values

Contains M valuesGeometry Polyline

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

Type a description of this featureclass or table in this placeholder text.

OBJECTID Object IDSHAPE Geometry Yes

BoundaryType String Yes 16 Place a succinct description of the field in this text

Direction String Yes 12 Place a succinct description of the field in this text

Distance String Yes 10 Place a succinct description of the field in this text

Delta String Yes 10 Place a succinct description of the field in this text

Radius String Yes 10 Place a succinct description of the field in this text

Tangent String Yes 10 Place a succinct description of the field in this text

ArcLength String Yes 10 Place a succinct description of the field in this text

Side String Yes 1 Place a succinct description of the field in this text

BoundaryTypeCode Long integer Yes 1 BoundaryType 0 Place a succinct description of the field in this text

SHAPE_Length Double Yes 0 0

Simple feature classCartoLine Contains Z values

Contains M valuesGeometry Polyline

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

The cartographic presentation lines.These were used in the CAD files andmay be needed to preserve the lookand feel of hardcopy maps

OBJECTID Object IDShape Geometry Yes

LineType Long integer Yes 10 0 The type of carto line for subtyping

Shape_Length Double Yes 0 0

Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtypeSubtype field

SubtypeCode

Subtypes of CartoLineLineType10

20 CivilDivision No values set1 EA-Encumberance No values set2 PL-DA No values set3 PL-Extended_Tie_line No values set4 PL-IA No values set5 PL-Meander_Line No values set6 PL-Note No values set7 PL-Original_Parcel_Line No values set8 PL-PT No values set9 PL-Tie No values set

10 PL-Tie_Line No values set11 RW_Radius No values set12 SD-SD_Block_O_100 No values set13 SD-SD_Block_O_200 No values set14 ROW_CL No values set15 RR_CL No values set

Easement line - edge of easements

Edges of civil divisions

Dimension arrows

Historical boundary lines

Identification arrows

Water meander lines

Leader Line for Notes

Parcel Lines extending into Water Bodies

Tangency Tic Points

Tie Hooks showing ownership across historic property boundary lines

Historic property boundary lines

The radius line for cul-de-sacs

Subdivision block circle around text of block no

Subdivision block circle around text of block no

Road centerlines - copied to public safety geodatabase

Rail road centerlines

Tax Parcel Feature Classes

Relationship class

NamePrimary keyForeign key

TypeCardinalityNotification

Forward labelBackward label

TaxParcelsHaveSitus

Origin feature class Destination feature class

SimpleOne to manyNone

HasIs assigned to

TaxParcelTaxKeyTAXKEY

SitusNamePrimary keyForeign key

Features with Addresses

The unique identifier for the address at this point

Simple feature classSitus Contains Z values

Contains M valuesGeometry Point

NoNo

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A situs point is a geographicrepresentation of an address

OBJECTID OIDSHAPE Geometry Yes

AddressID Integer Yes 0TaxKey String Yes 14 The TaxKey for the parcel this address is in

ParcelID String Yes 16 The ParcelID for the parcel this address is in

A building is a polygon thatrepresents the roof outline of astructure, as digitized from aerialphotography.

The unique identifier for the Building

The unique identifier for theTax Parcel

Simple feature classBuilding Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

OBJECTID OIDSHAPE Geometry Yes

BuildingID Integer Yes 0ParcelID Integer Yes 0 0

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

Relationship classSitusHaveAddress

TypeCardinalityNotification

SimpleOne to OneNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Situs

AddressIDAddressID

Name

Primary KeyForeign Key

Address

AddressIDAddressID

HasIs assigned to

Relationship classBuildingsHaveAddresses

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Building

BuildingIDBuildingID

Name

Primary KeyForeign Key

Building_X_Address

BuildingIDBuildingID

HasIs assigned to

Simple feature classTaxParcel Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allownulls

The current tax parcels

OBJECTID Object IDShape Geometry Yes

GISAcres Double Yes 0 0 The area of the tax parcel as computed in the GIS

TaxKey String Yes 14 The tax key number

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0GapOverlap String Yes 1 Y = GAP or OVERLAP – tax parcel areas that gap or overlap

Ecodecomments

source

StringStringString

YesYesYes

2025550

TableAddress

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

An address describes a locationin relation to a street.

OBJECTID OIDAddressID Integer Yes 0Houseno String Yes 5Housesx String Yes 2

Dir String Yes DirectionCodes 2Street String Yes 30StType String Yes StTypeValues 4

The house number component of the address.

PDir String Yes DirectionCodes 2

The alphabetic component of the address.

Muni

Unit

Zip_Code

Mail_Status

Status

Date_Entered

Date_Changed

String

String

String

String

String

Date/Time

Date/Time

Yes

Yes

Yes

Yes

Yes

MuniValues 25

5

9

2

10

The Prefix direction component of the address

The Street Name component of the address

The Post direction component of the address

The municipality that the address resides in

The Building Unit component of the address

The zip_code component of the address

Mailing Address Status FlagStatus (Active or Retired)

The date the address was first entered into the systemThe date the address was last changed

The date the address was retiredDate_Retired Date/Time

The Street Type component of the address

Features with Addresses Addresses

The unique identifier for the address at this point

Simple feature classSitus Contains Z values

Contains M valuesGeometry Point

NoNo

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A situs point is a geographicrepresentation of an address

OBJECTID OIDSHAPE Geometry Yes

AddressID Integer Yes 0TaxKey String Yes 14 The TaxKey for the parcel this address is in

ParcelID String Yes 16 The ParcelID for the parcel this address is in

A building is a polygon thatrepresents the roof outline of astructure, as digitized from aerialphotography.

The unique identifier for the Building

The unique identifier for theTax Parcel

Simple feature classBuilding Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

OBJECTID OIDSHAPE Geometry Yes

BuildingID Integer Yes 0ParcelID Integer Yes 0 0

SHAPE_Length Double Yes 0 0SHAPE_Area Double Yes 0 0

TableBuilding_X_Address

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A cross reference table to getfrom the Buildings feature classto the address table

OBJECTID OIDLong Yes 0

AddressID Long Yes 0 The unique identifier for the address.The unique identifier of the building.BuildingID

Relationship classSitusHaveAddress

TypeCardinalityNotification

SimpleOne to OneNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Situs

AddressIDAddressID

Name

Primary KeyForeign Key

Address

AddressIDAddressID

HasIs assigned to

Relationship classBuildingsHaveAddresses

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Building

BuildingIDBuildingID

Name

Primary KeyForeign Key

Building_X_Address

BuildingIDBuildingID

HasIs assigned to

Relationship classAddressesHaveBuildings

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Address

AddressIDAddressID

Name

Primary KeyForeign Key

Building_X_Address

AddressIDAddressID

HasIs assigned to

TableAddress_X_Name

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A cross reference table to getfrom the Buildings feature classto the address table

OBJECTID OIDLong Yes 0

AddressID Long Yes 0 The unique identifier for the address.The unique identifier of the placename.NameID

Relationship classAddressesHavePlaceNames

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

Address

AddressIDAddressID

Name

Primary KeyForeign Key

Address_X_Name

AddressIDAddressID

HasIs assigned to

Relationship classPlaceNamesHaveAddresses

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

PlaceNames

NameIDNameID

Name

Primary KeyForeign Key

Address_X_Name

NameIDNameID

Is assigned toHas

Coded value domainParityCodesDescription

Field typeSplit policy

Merge policy

Address range parityStringDefault valueDefault value

Code

E

O

M

U

Description

Even

Odd

Mixed

Unknown

TablePlaceNames

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A geographic name is a namethat can be associated withgeographic features.

OBJECTID OIDInteger Yes 0

NamingAuthorityID Integer Yes 0 The unique identifier of the authority responsible for assigning the name.

Name String Yes 0 60

The unique identifier of the name.

The full geographic name.

NameID

Names

Relationship classRangeAddressRange (OPTIONAL)

TypeCardinalityNotification

SimpleOne to OneNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

AddressRange

AddressRangeIDAddressRangeID

Name

Primary KeyForeign Key

Street_X_AddressRangeAddressRangeIDAddressRangeID

HasIs assigned to

Relationship classAddressRangeHavePlaceNames

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

AddressRange

AddressRangeIDAddressRangeID

Name

Primary KeyForeign Key

AddressRange_X_NameAddressRangeIDAddressRangeID

HasIs assigned to

Relationship classPlaceNamesAreAssignedAddressRanges (Optional)Type

CardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

PlaceNames

NameIDNameID

Name

Primary KeyForeign Key

AddressRange_X_NameNameIDNameID

IsAssignedToHas

Table

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

OBJECTID OIDLong Yes 0

AddressRangeID Long Yes 0NameID

Category String Yes 10

AddressRange_X_Name

This cross walk table makes the AdressRange to PlaceName connection

The unique identifier for the address range.

The category of the address range

The unique identifier for the name.

TableAddressRange (OPTIONAL)

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

An address range represents theset of addresses that can befound along a street.

OBJECTID OIDAddressRangeID Integer Yes 0 The unique identifier for the address range.

FromAddress Integer Yes 0 The first address found at the from node of the feature.

ToAddress Integer Yes 0 The last address found at the to node of the feature.

Parity String Yes ParityCodes 1 Odd/Even/Mixed/Unknown address parity flag.

Street/PlaceName WithTheoretical and Actual Address

Ranges

Coded value domainParityCodesDescription

Field typeSplit policy

Merge policy

Address range parityStringDefault valueDefault value

Code

E

O

M

U

Description

Even

Odd

Mixed

Unknown

TablePlaceNames

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

A geographic name is a namethat can be associated withgeographic features.

OBJECTID OIDInteger Yes 0

NamingAuthorityID Integer Yes 0 The unique identifier of the authority responsible for assigning the name.

Name String Yes 0 60

The unique identifier of the name.

The full geographic name.

NameID

Names

Relationship classRangeAddressRange (OPTIONAL)

TypeCardinalityNotification

SimpleOne to OneNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

AddressRange

AddressRangeIDAddressRangeID

Name

Primary KeyForeign Key

Street_X_AddressRangeAddressRangeIDAddressRangeID

HasIs assigned to

Relationship classAddressRangeHavePlaceNames

TypeCardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

AddressRange

AddressRangeIDAddressRangeID

Name

Primary KeyForeign Key

AddressRange_X_NameAddressRangeIDAddressRangeID

HasIs assigned to

Relationship classPlaceNamesAreAssignedAddressRanges (Optional)Type

CardinalityNotification

SimpleOne to ManyNone

Forward labelBackward label

Origin feature class Destination table

Name

Primary keyForeign key

PlaceNames

NameIDNameID

Name

Primary KeyForeign Key

AddressRange_X_NameNameIDNameID

IsAssignedToHas

Table

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

OBJECTID OIDLong Yes 0

AddressRangeID Long Yes 0NameID

Category String Yes 10

AddressRange_X_Name

This cross walk table makes the AdressRange to PlaceName connection

The unique identifier for the address range.

The category of the address range

The unique identifier for the name.

TableAddressRange (OPTIONAL)

Data typeField namePrec-ision Scale LengthDomain

Default value

Allownulls

An address range represents theset of addresses that can befound along a street.

OBJECTID OIDAddressRangeID Integer Yes 0 The unique identifier for the address range.

FromAddress Integer Yes 0 The first address found at the from node of the feature.

ToAddress Integer Yes 0 The last address found at the to node of the feature.

Parity String Yes ParityCodes 1 Odd/Even/Mixed/Unknown address parity flag.

Street/PlaceName WithTheoretical and Actual Address

Ranges

[Geodatabase Data Model: Summary - Final Design ]

[Geodatabase Data Model: Summary - Final Design ]

Simple Model today – with a migration path to more complex modeling arrangements

Flexible address model that allows very complex to simple tools for address resolutions

Simple Model today – with a migration path to more complex modeling arrangements

Flexible address model that allows very complex to simple tools for address resolutions

Key Principals for Success Focus on County Data Incorporate City Data

Key Principals for Success Focus on County Data Incorporate City Data

[ Migration Plan: ][ Migration Plan: ]

[Migration Plan: Key Principals for Success ][Migration Plan: Key Principals for Success ]

Planning process - to develop clear methodology on moving through each stage of the migration process

Use Automated tools whenever possible to lower overhead

High level QA/QC that is done at the County staff level for final acceptance.

Planning process - to develop clear methodology on moving through each stage of the migration process

Use Automated tools whenever possible to lower overhead

High level QA/QC that is done at the County staff level for final acceptance.

[Migration Plan: Focus on County Data ][Migration Plan: Focus on County Data ]

Take this on first - We understand this data and it is in good shape

Develop the methodology and tools to support the effort

Verify with ROD Office on existing Land Records base

Create a historical digital copy of the paper maps as a departure point to the GIS

Take this on first - We understand this data and it is in good shape

Develop the methodology and tools to support the effort

Verify with ROD Office on existing Land Records base

Create a historical digital copy of the paper maps as a departure point to the GIS

[Migration Plan: Incorporate City of Milwaukee Data ]

[Migration Plan: Incorporate City of Milwaukee Data ]

Other political processes must be addressed before this becomes a priority.

City of Milwaukee data is currently in transition – to ESRI format by SEWRPC

New issues will need to be addressed to incorporate and maintain this data within a Countywide Enterprise GIS.

Other political processes must be addressed before this becomes a priority.

City of Milwaukee data is currently in transition – to ESRI format by SEWRPC

New issues will need to be addressed to incorporate and maintain this data within a Countywide Enterprise GIS.

Work Plan for 2005 Additional Phases for 2006-7 Create a County Land Information portal

Work Plan for 2005 Additional Phases for 2006-7 Create a County Land Information portal

[ Current Work Plan: ][ Current Work Plan: ]

[Current Work Plan: For Fiscal Year 2005 ][Current Work Plan: For Fiscal Year 2005 ]

County cadastral conversion to Geodatabase

o Covert existing GIS coverages to new data model

o Scan current “official” paper maps for final check

o PLSS adjustment to the Geodatabase

o Publish in ArcSDE Annotation Geodatabase model ROD Office map series at 100 and 200 scale

County cadastral conversion to Geodatabase

o Covert existing GIS coverages to new data model

o Scan current “official” paper maps for final check

o PLSS adjustment to the Geodatabase

o Publish in ArcSDE Annotation Geodatabase model ROD Office map series at 100 and 200 scale

[Current Work Plan: Additional Work Plans for 2006-7 ]

[Current Work Plan: Additional Work Plans for 2006-7 ]

Work plan – Fiscal year 2006:

o County Addressing System Migration.

o Production data maintenance tools are developed

Work plan – Fiscal Year 2007:

o Bring City of Milwaukee cadastral and street address systems into the County GIS.

o Enterprise portal developed

o Enterprise Geocoding service developed

Work plan – Fiscal year 2006:

o County Addressing System Migration.

o Production data maintenance tools are developed

Work plan – Fiscal Year 2007:

o Bring City of Milwaukee cadastral and street address systems into the County GIS.

o Enterprise portal developed

o Enterprise Geocoding service developed

[Current Work Plan: Create County Land Information Portal ]

[Current Work Plan: Create County Land Information Portal ]

Open Access to Development Partners – via a easy to use LI Portal operated by the County

ArcSDE site to allow direct access to key data layers

ArcIMS site to allow partners post submittals for data updates

Open Access to Development Partners – via a easy to use LI Portal operated by the County

ArcSDE site to allow direct access to key data layers

ArcIMS site to allow partners post submittals for data updates

QuestionsQuestions

[ Scott Stocking ][ Scott Stocking ]sstocking@geoanalytics.com

500 W Monroe Street, Suite 3820

Chicago, IL 60661Phone: 312.863.2330

sstocking@geoanalytics.com

500 W Monroe Street, Suite 3820

Chicago, IL 60661Phone: 312.863.2330

© GeoAnalytics, Inc. 2003

kwhite@milwcnty.com

Milwaukee County

Department of Parks and Public Infrastructure

2711 W. Wells - 4th Floor

Milwaukee, WI 53208Phone: 414.278.2176

kwhite@milwcnty.com

Milwaukee County

Department of Parks and Public Infrastructure

2711 W. Wells - 4th Floor

Milwaukee, WI 53208Phone: 414.278.2176

[ Kevin White ][ Kevin White ]