Synchronize Our Modified Data with the Latest Vendor Update

By Charline AveyIT Operations Support Lead

Using Geolocation at a Water Utility

Customers mapped for Meter reading Customers mapped for Service Calls Service calls not attached to Customers need

to be mapped Maintenance activities need to be mapped and

displayed with facilities

Applications requiring Geolocation

Meter reading route design► Customers must be geolocated► Centerlines must exist to get to the customers► Customers must be close enough to

centerlines to infer connection One Call locate request

► Geolocation of ticket using address without zipcode

The Problem

Centerline data set is required for developing Meter Reading Routes

Centerline data set needs to have routeable attributes

Entire Service Area includes Counties that do not have routable centerlines.

Water Utility needs new centerlines as they are placed in service

The Solution

Purchase national routable dataset Develop default template for new centerlines Create new centerline file from developer plans. Add default routable attributes with best information

available Compare against national dataset Make modifications as necessary to national dataset to

insert new centerlines Keep new identified by using way out of range link_id

Creating New Centerlines

Create copy of national dataset Import in to CAD program Attach best centerline data from whoever Attach proposed projects dataset Review areas in proposed dataset to

determine what needs to be added► Needed areas can also be determined from

routing program where service locations didn’t have a centerline

Where to get the attributes

Most Counties are providing the basicsOther options Cass Certification software generally gives address rangesDeveloper plans generally include the parcel address rangesQuess

L_ADDRSCH E O L_CITY INDIANAPOLIS INDIANAPOLIS L_NREFADDR 8498 8469 L_POSTCODE 46240 46240 L_REFADDR 8470 8461 R_ADDRSCH O E R_CITY INDIANAPOLIS INDIANAPOLIS R_NREFADDR 8499 8468 R_POSTCODE 46240 46240 R_REFADDR 8471 8460 ST_NAME UNION CHAPEL RD UNION CHAPEL RD ST_NM_BASE UNION CHAPEL UNION CHAPEL ST_NM_SUFF ST_TYP_AFT RD RD

Adding a new subdivision

Other required modifications

Inserting a new subdivision requires existing centerline modification

Tag existing centerline as remove Copy existing and adjust with break for new

subdivision centerline Change address ranges

Compare Against National Dataset

How much of a problem is it?► 2006 200 projects in service► 2007 170 projects in service

Datasets are only delivered every quarter and it takes 3 months to get the delivery

► Currently working with Q32007 Visual inspection is required each time a new

data set is delivered What would it take to automate this process?

Requirements for automating the review

Compare the modified map with a map update► Detect Attribute change

Would require both datasets have the same attribute fields so that compare could be done

► Geometry change detection Identify features that have had their geometry

change► Must reconcile map differences

Show what changed Allow you to choose which version to keep Save decisions to be reused on next map update

Import data

The existing map is called the Source.

The new map update is called the Target.

Detect changes in the address range and LINK_ID attributes

Select attributes to focus on

The Source and Target data after it is imported

View the data

Are able to set search distance. In this case, 5 meters.

Detect the changes

1) List of streets that have an attribution or geometry difference2) List of conflicting attributes.3) Specify which version to keep.

Reconcile

Attribute change. Click on a row and the tool highlights the street and lists the changed attribute values. In this case, a new street was added with dummy attributes. Now it appears in the latest update with good attribute values.

Geometry change. In this case, a new street was added. Now it appears in the latest update in a slightly different location.

View what changed

Merge to get a view of the result layer

Then create the result personal geodatabase

Create the result

Process outcome

Used added streets as the source Used national data set as the target Assigned 30 feet as the compare distance Chose to accept all target except where the

source didn’t match For a 50 square mile area having 240000

centerlines it took 30 minutes to get the result.

Tool assigns unique link_id to added centerlines if necessary

New Link_id can be used to gather centerline for the next update

New link_id can be used gather centerlines to submit to national dataset for update

Tool – Map Detective from ESEA

Future wants

Can’t we all just get along Promote centerline sharing with anyone public

or private Promote centerline standardization that

include routing attributes Centerlines are the basic framework layer that

supports Public Safety, Economic Development and Service delivery

Why