Receiving work map

 Print Previous page Top page

This stage is designed to compare the versions of the base and work maps relative to the standard one, generate protocols for changing map data and interactively compare them, with subsequent acceptance of changes to the base map.

 

compare_dialog_en

 

Procedure  of actions

1. Select a directory of standard open.

2. Select a work map open.

 

After selecting a work map, protocols are automatically generated and the tree of changes to the object's data is filled.

 

Table composition

 

List of changes

Contains information about the key, localization and change of the metric data, object type and semantic characteristics in the object

Base map

Contains a list of changes of the base map. It is filled in from the transaction log of the base map, starting from the moment the work map is issued to the operator

Work map (operator name)

Contains a list of changes of the work map compared to the standard map saved at the time of issuing the original work mapd to the operator.

Standard map

Contains explanations about the original characteristics of the modified object

 

The «object» node. The format of the «object key» record.

fig1

 

The localization of the object is indicated as an icon:

- polygon

- linear

- vector

- point

- title

- mixed

 

The «Base map» and «Work map» fields indicate the type of operation. Additionally, the name of the operator who made the changes is recorded in the «Base map» field. If the object has not been changed in the base or work maps, then the type of operation is not specified in the corresponding fields.

 

Types of object changes

 

Creating an object. Node «object». Type of operation is «created». his object has been created.

 

Deleting an object. Node «object». Type of operation is «deleted». This object has been deleted.

 

Updating the metric. Node «metric». Type of operation is «updated».

Indicates a change in the metric of the object.

The background of this node has a light blue color.

 

fig2

 

 

Field

Description

Record format

length

changing the length of an object

«length; ±change»

length– new object lengt                

±change – increasing/decreasing length onto value change

square

change in the area of the object

«square; ±change»

square – new object area        

±change– increasing/decreasing area onto value change

points

changing the total and number of edited object points

«points; ±count», «points; count»

points – new points number

±count – increasing/decreasing the number of points onto value count

count   – number of edited points

direct

changing the direction of object digitization

«turn»

 

Updating the object type. Node «type». The operation type is «updated».

Indicates a change in the object type.

The background of this node has a light green color.

fig3

 

Updating semantics. Node «semantic». The operation type is «updated».

This node contains a list of semantics that have been deleted, added, and whose values have been changed.

«List of changes» field contains the name and the semantics code. The semantics value is recorded into the «Base map» and «Work map» fields.

The background of this node has a light gray color.

fig4

 

Fields with deleted semantics have a light lilac background.

 

Additional modes

roll - Collapse all tree nodes.

unroll - Expand all tree nodes.

filter - Filter data by unaccepted decisions.

 

compare_dialog2

 

filter_blue - Filter data by localization, semantics, and type of object change. Lists of semantics, localizations, and type of change are formed according to changes in the work map. These lists

 

By change type

By semantics

By localization

 

In accordance with the set filter parameters, data will be displayed only for those objects that meet these conditions. You can also combine data filtering by unaccepted decisions filter, by localization, semantics, and the type of object change filter_blue. To disable filtering, press the buttons filter_blue and filter.

 

Acceptance of changes

When forming a tree of changes, positive solutions for changes in the work map are automatically set galka.

fig5

If there are changes for this object and in the base map, then this record will be highlighted in yellow and in the «Work map» field the iconvopros will be set. In this case, it is necessary to accept galka or reject crossthe changes by clicking the left mouse button on the status icon in the «Work map» field.

 

fig6

When the status changes in the «object», «semantic» nodes, the status of the solution will also change in the child nodes.

If there are accepted and unaccepted decisions in the child nodes, then the icon galka_grey will be set in the status of the parent node.

 

fig7

For the value of the repeated semantics in the «Base map» field, you can specify: whether to leave this value in the base map or replace it from the work map.

The status bar displays the number of unaccepted decisions. By default, nodes containing unaccepted decisions are expanded.

To save changes from the work map into the base map, you need to call the «Save Changes» mode open-2. If, when saving the changes, there are unaccepted decisions, the following warning will appear.

 

warning_en

 

 

If you click on the «Yes» button, then all unaccepted decisions will be approved positively and added into the base map.

 

Result

Map view before accepting changes

mapview_before

 

Map view after accepting changes (all changes are accepted)

mapview_after

 

Decisions on acceptance of the changes will be recorded into the protocol of the work map.

 

protocol2_0