1 / 23

Synchronize Our Modified Data with the Latest Vendor Update

Synchronize Our Modified Data with the Latest Vendor Update. By Charline Avey IT 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

djuana
Télécharger la présentation

Synchronize Our Modified Data with the Latest Vendor Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Synchronize Our Modified Data with the Latest Vendor Update By Charline Avey IT Operations Support Lead

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. Where to get the attributes • Most Counties are providing the basics • Other options Cass Certification software generally gives address ranges • Developer plans generally include the parcel address ranges • Quess

  8. Adding a new subdivision

  9. 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

  10. 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?

  11. 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

  12. Import data The existing map is called the Source. The new map update is called the Target.

  13. Select attributes to focus on Detect changes in the address range and LINK_ID attributes

  14. View the data The Source and Target data after it is imported

  15. Detect the changes Are able to set search distance. In this case, 5 meters.

  16. Reconcile • List of streets that have an attribution or geometry difference • List of conflicting attributes. • 3) Specify which version to keep.

  17. View what changed 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.

  18. Create the result Merge to get a view of the result layer Then create the result personal geodatabase

  19. 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.

  20. 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

  21. 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

  22. Why

More Related