Home

Excavators

Utilities

Promotion & Education

Resources

Statistics

Welcome i-Notice One-call Process Stake-out Response Worksheets

Welcome About DigSafelyNewYork Membership Topics Service AreaTopics Destination Topics Response Topics

Welcome Field Reps Damage Prevention Councils Printed Materials Trinkets Events Calendar Event Registrations Vendor Registrations Excavator Seminars

Welcome Site Map Code Rule 753 Events Calendar Master List of Members Private Locators Related Links Sustaining Members Email and Public Forums PSC Information

Welcome NYGAS Sheets Board iNotice Stats Damage Reporting Field Rep Activity DPC Stats

Members

Service Areas

Destinations

Response Issues

Etc.

Membership (Joining) Membership (General) Member Setup Billing Setup

Service Areas Ticket Priorities Service Area Setup Dispatch Options Holidays Positive Response

Destinations Destination Setup Hardware Guide Ticket Resends Daily Audits Ticket Format

What is Legal Notice? Marking up a buried facility Positive Response Do I have to respond?

What is Dig Safely New York? Ticket Searches

Map Change Management

This section provides instruction on how to manage any upcoming changes to the map via the Map Change Detection tool. Before we dive in, let us first embark on a little orientation...

The toolbar contains the Map Change Detector tool on the far right. (see Fig. 1)

Toolbar
fig. 1

This M tool is used to review the "recommended changes" to your service area due to a staged map update.

You'll see three layers at the top of the Layer Control Box - streets being added shown in grey, streets being changed shown in blue, and streets being removed shown in red cross hatch. (see Fig. 2)

fig. 2

The "streets being added" layer shows where any new streets will be located after the system map update.

The "streets being changed" layer shows the streets that will have changed attributes (such as address ranges or names,) without being physically moved after the system map update.

The "streets being removed " layer shows street segments currently existing in the present map that will be deleted as a result of the update.

You'll quickly discover that not all deletions are actual deletions, and not all additions are "new". Quite often, rather than change an existing street segment, the map vendor will have killed and re-added a segment as a "new" street.

To show or hide the various changes: Go to the top of the layers list on the left hand side of the map. Click on the check boxes for streets being added, streets to be changed, and streets being removed, as desired. (see Fig. 7 & 8)

To review your change recommendations:

Click on the Map Change detector tool button.

The Change Recommendations layer appears (figure 3), and the REVIEW SERVICE AREA CHANGE RECOMMENDATIONS box appears. (see Fig. 4)

The "Change Recommendations" layer will only be visible in the layer control box while the Map Change Detection tool is being used.

This layer shows the status of the "change recommendations" for your service area.
Unreviewed changes are shown in red. Rejected changes are shown in yellow. Approved changes are shown in green.(see fig. 3)

fig. 3

*IMPORTANT*

During the Change Review process, you can still make updates your service areas. And as per normal, any manual edits are stored in your pending layers. Remember that you will need to coordinate their release with Dig|Safely. New York as you normally do.

The "change recommendations" are a completely separate layer, however. When the new version of the map is eventually made "live", any approved or un-reviewed recommendations will be added to your service area. Meanwhile, any rejected "change recommendations" will simply be discarded.

IF you wish to manually draw any changes to the recommendations, please remember the order in which things must occur - any non-refused recommendations are applied, and then you can commit your pending layers into production.

fig. 4

At the top of the dialog box is the name of the service area you are working on.

The default setting brings up a list of unreviewed "change recommendations" by county.

The unreviewed "change recommendations" are listed by address range and street.

Double click on a "change recommendation"; the map will zoom to the recommendation and highlight it. Note that the tools on the Map Toolbar (such as zoom in, zoom out, and pan) are still active, and can be used as well. (see Fig. 5)

fig. 5

Keep in mind...

The “change recommendations” layer will only be visible while using the Map Change Detector tool. If you close the Review Service Area Change Recommendations window, the “change recommendations” layer will be hidden. If you discover that this window is in the way... remember that you can minimize or drag it to another part of the screen.

fig. 7

fig. 8

As you double-click on each recommendation, decide whether to approve or reject the "change recommendation" and click the corresponding button at the bottom of the Review Service Area Change Recommendations box. Again, note that any recommendations that are not rejected will be applied when the new map is loaded. If you do not want a recommendation, you must specifically reject it. (See fig. 9)

fig.9

If you wish to "tune" a recommendation (and you my choose to do so), you will Reject it, and manually draw the correction using the normal Map Toolbar tools. Remember, though - any manually drawn corrections are not automatically applied when the new map is loaded; they are normal "pending changes". You will need to coordinate their release into production with Dig|Safely. New York, as you would any other.

To help you keep track of what has and has not been reviewed, you can filter the list of recommendations by selecting options as highlighted in "figure 10":

fig. 10

The "change recommendations" that you review will save automatically, so you do not have to review all of the "change recommendations" at one time. When you are done for the day, simply close the "Review Service Area Change Recommendations" window.

As usual, however, any manually drawn pending layers will need saving.