Migrating Parcels to a Spatial DBMS Jim Landwehr Land Information Systems Analyst Waukesha County Dept. of Parks and Land Use William Cozzens III Land.

Migrating Parcels to a Spatial DBMS

Jim Landwehr

Land Information Systems Analyst

Waukesha County

Dept. of Parks and Land Use

William Cozzens III

Land Information Mapping Technician

Waukesha County

Dept. of Parks and Land Use

Overview

History of Waukesha Co. Parcel Database

Migration Objectives

Geodatabase Design Process

Data Conversion Process

Maintenance

Geodatabase Tools

Data Demo

Caveats

Platform

Migration just completed(Linking/Maintenance) Q2 2004

Maintenance Questions

Not the experts…

Co. Parcel Inventory Specifics

Approx. 138,000 parcels

Approx. 2000 new parcels/year

1”=100 and 1”=200’ scales

Mapped to NMAS accuracy (+/-3.3’ & 6.6’)

Were maintained by consultant (in-house)

Currently maintained by LIS Mapping Technician

Why move to a Spatial database?

Legacy system was file-based on “dated” technology

RDBMS technology and indexing makes for bigger, stronger, faster data access

Ability to co-join disparate data sets

GIS Industry trend

GeoDatabase Migration Objectives

Cleanse existing dataConflate, simplify, intersect, fix dangles

Enrich existing dataAdd attributes, close non-closed features, est. relationships

Incorporate disparate databasesParcel history file, condo relate table, parcel address database, etc

Restructure data to improve efficienciesAvoid any data lossAbandon unused legacy featuresCompile feature-level metadata

Parcel Database History“In the beginning…” Genasys

Compilation originally done by SEWRPC 1987-99 Using Genamap software

Files tiled as either section or quarter- section files

No linkages to relational database

Parcel Database History The move to County’s MGE platform

County converted files to Intergraph MGE Microstation file format in 1997

Migrated to township tiling system

Linked to relational database (Oracle)

Parcel Database History The move to a spatial DBMS

Converted files Microsoft SQL Server SDE Geodatabase

Migrated to seamless county file

Link to imaging, data warehouse and tract indexing systems

Cleaned, enhanced, etc.

Co. Parcel Data Evolution

Data richness,

integrity, usefulness

Projected Parcel Maintenance Workflowand GIS Environment

Cogo CSM’s, Condos, Subd

w/toolset

PublicationDatabase

ProductionDatabase

Monthly

ArcIMSApplications

Co. ArcGISUsers

MunicipalData Users

View an

d Query

View and Query

View, Query Update?

Topology Validation

Geodatabase Design Process (Players)

Chose a consultant to manage project

Fairview Industries

Consultant partnered w/technical expert

Headwaters Resources LLC

Oversight by Co. Land Info Technical Working Group (LITWG)

Cities of Brookfield, Muskego, New Berlin, Oconomowoc and Waukesha

Village of Menomonee Falls

SEWRPC

Geodatabase DesignAssessed current data condition

Quality ---------------------------Good, some skeletons

Strengths -------------------------Tested, Cartographically sound

Shortcomings/Limitations------Linkages, Closure, Legacy items

Assessed current processesParcel data collection------------Fast, workflow a bit clunky

Other database items------------Separate processes, complex

Data conversion/distribution---Time consuming

GeoDatabase Design Process

Defined spatial extents and precisionDefined “core” feature datasetsBegan with a small, manageable Feature Dataset

Allowed topology rule definition and testingEnabled familiarization with GDB

Defined a pilot areaRural/Urban mixIncluded areas near waterOld/New Development mix

Waukesha County Geodatabase Structure

H isto r icP roposed

H isto r icP roposed

A nnexa t ions

C o n stru c t_ P o ly

C o ns truc t_L ine

C ar to L ine

R e s tric t io n*

R e gu la te d U s e*

T a x H y d ro

P a rce lB o u nd a ry

T a x P a rc e l

S im C o n D iv is ion

S im u ltan e ou s C o nv e y an ce

R R R O W

R O W

P a rce lB o u nd a ry

C iv ilD iv is io ns

L andF eature Dataset

P L S S A n n o ta tion

R e tire dP LS S C o rn e rs

P L S S _ T ow n sh ip _ A re as

P L S S _ S e ctio n _A re as

P L S S _ Q T R _ S e ctio n _A re as

P L S S _ L ine

P L S S _ C orn er_ P ts

PL SSF eature Dataset

M a ny F ea tu re C las s es

A nnotationF eature Dataset

Land_Records GeoDatabase (Summary)

PLSS Feature Dataset

Acquired control points from SEWRPCInsured points were accurate/current

Enhanced attribution

Used sub-types and domain lists

Applied topology rules to insure integrity

PLSS Feature Dataset Attribution Enhancement

PLSS Topology Rules

Origin Feature Class Topology Rule Comparison Feature Class

PLSS_Township_Areas Area No OverlapPLSS_Township_Areas Area No GapsPLSS_Section_Areas Area No OverlapPLSS_Section_Areas Area No GapsPLSS_Section_Areas Area Covered By Area Class PLSS_Township_AreasPLSS_QTR_Section_Areas Area No OverlapPLSS_QTR_Section_Areas Area No GapsPLSS_QTR_Section_Areas Area Covered By Area Class PLSS_Section_AreasPLSS_Line Line Covered By Area Boundary PLSS_QTR_Section_Areas

Land Feature Dataset

Where linkages/relationships exist

Dataset that will drive applications

Dataset will produce products (in publication GDB) used by ArcMap users

Land Feature Dataset --Primary Feature Classes--

Tax Parcel PolygonsIncludes “Gap” and “Overlap” polygons

Simultaneous ConveyanceExternal Boundaries, or portion thereof, of “active” SC documents

Simultaneous Conveyance Divisions • Lots, out lots, etc.

• Populate at later date…

Historic Tax Parcel PolygonsRetired geometries (this date forward)

Right-of-Way Polygons

Land Dataset Enhancements--Simultaneous Conveyance--

Name, TractID, Type3000+ Subdivisions9600+ CSM’s700+ Condominiums

Land Dataset Enhancements--Rights of Way--

Closed PolygonsAid cartographic presentation (e.g. extended parcels)

Enables sub-typing (Dedicated, reserved, etc)

RR Status

Active

Proposed

Retired

ROW Type

Dedicated

Prescriptive

Proposed

Reserved

Vacated

Land Dataset Relationships

Tax Parcel Feature Class

Combine disparate databasesTax Assessment File

9999 condo relate table (multi-owners)

Parcel history file• Date of update, quality of fit, document #, etc.

Tax Parcel Relationships

Link to Data Warehouse

(Tax Assessment)

Link for Multi-Ownership (Condos,etc)

Link to Parcel History File

Data Migration Processes

Convert vectors to coverages using AMLEasily scripted by consultant

Allows topology checks, error trapping, etc.

Convert CAD text to GDB Annotation

Vector Data clean-up processClean

CAD Files

Run .aml toFind errant

Labels

Clean?

Importcoverage to

GDB

No

Yes

DefineTopol.Rules

ValidateTopology

CleanTopologyErrors in

GDB

ValidateTopology

Clean? No

FinalGDB

Yes

Annotation Feature Dataset

Determined we could not use Feature-linked Annotation for legacy anon

Technology still evolving (e.g. Annotation Sub-typing)

Interesting issues raised…

Interesting Issue #1Annotation Migration Results

Black = Desired text heights displayed as they look in CAD filesRed = Annotation after import into GDB (using default settings, Arial font)

Pre-ConversionAnnotation Considerations

SizeScaled by 1.3 to match CAD sizes

Text Origin Moved from Center Center to Left Bottom

Minimizes shift

Desired font Set prior to converting text

Beware of special characters/fonts CAD fonts vs. True Type

(e.g. +/-)

Why is this? I have no idea…

Parcel Maintenance

NovaLIS

Toolset customized for our workflow(s)

Work in progress

ESRI Geodatabase Tools( Available on ArcScripts Online)

Geodatabase DesignerUsed to Import/Export GDB schemas (.xml)

Geodatabase ReporterUsed to Summarize GDB structure (.htm)

Geodatabase DiagrammerUsed to Document GDB design using MS Visio (.vsd)

SDE MonitorUsed to Monitor your SDE activity

Things to remember(i.e. free advice)

Assess needs vs. wants

Clean data up-front, then use topology tools to “mop up”

Limit # of feature classes by using sub-types where possible

Tap into the knowledge base

Take your time

Questions/Demonstration

Thank You.

[email protected]

[email protected]