SuperMap iDesktopX boundary check, quickly find wrong tiles

Table of contents

foreword

1. Instructions for use

1.1 Function entry

1.2 Parameter description

1.2.1 Boundary check dialog parameter setting

1.2.1 Bounds Check Window

2. Application examples


Author: kxj

foreword

   The desktop supports the inspection of map tiles near the boundary. Users can generate a tile inspection grid based on the boundary data, and then mark tiles at different levels to complete the inspection. It also supports customizing the type of error tiles, which is convenient for users to manually check the tiles and record the inspection results in time.

1. Instructions for use

1.1 Function entry

[Data] tab -> [Tile Management] module -> [Boundary Check]

insert image description here

1.2 Parameter description

1.2.1 Boundary check dialog parameter setting

insert image description here

  • Local tile:  Select this radio button to select the sci file of the local tile for processing.
  • Mongo tiles:  Select this radio button, click the button to load Mongo tiles on the right , and enter the parameter setting page for loading MongoDB tiles. The specific parameters are as follows:

    insert image description here


    Among them:
    server address:  the address of the MongoDB server where the Mongo tile is located, for example: localhost:27017
    database name:  the name of the MongoDB database where the Mongo tile is located. Note: In the authentication mode, you need to enter the user name and user password before you can get the list of existing databases.
    Username (optional):  The username to access the MongoDB database.
    User password (optional):  The password to access the MongoDB database.
  • Boundary Data Source:  Select the data source where the boundary data is located.
  • Boundary Dataset:  Select a boundary line dataset (only line datasets are supported).
  • Check result:  Select the check result to save the data source (only udbx data source is supported).
    Note: To continue the inspection, you only need to select the tiles and the inspection results that need to be continued.

1.2.1 Bounds Check Window

insert image description here

  1. Tile Information:  Display the basic information of the inspected tile, including tile file, tile type, image type, block size, coordinate system, etc.
  2. Tile markup:
  • Level:  Select the tile level that needs to be marked.
  • Data Export:  Export the labeled error grid as a dataset.
  • Template:  It is the template for marking the wrong grid. The system provides six templates: Wrong [E], Missing [W], White [A], Black [S], Transparent [D], White Line [F]. Users can modify the template by selecting More... from the drop-down button on the right side of the template or the template management button.
  • Template management:  Markup types for managing error grids.
  • Mark:  Provide a tile list to view the mark type, and provide two types of correct and wrong to mark the tiles. The display of tiles in the marker list can be controlled via the Show All, Show Errors Only, Show Unmarked Only buttons. Batch selection and marking of grids via custom marked rectangle and freeform buttons.
  • The tile information list shows the total number of tiles, the number of checks, and the number of errors for each level .

2. Application examples

Taking the China map tile as an example, check the tiles near the border of Chengdu in the 1155583 level tiles.

Specific steps are as follows:

  1. Boundary data preparation: Create a dataset of inspection boundary lines.

    insert image description here

  2. Generate check grid: Use the boundary check function to generate a tile grid for check. The parameter settings in the boundary check dialog box are as follows:

insert image description here

  1. Mark tiles:
  • On the Boundary Check window -> Tile Marking page, select check tile level 1155583.

  • Label the tiles as desired. Select the marked tile type, and for the wrong tile, select the wrong type at the template according to the tile situation , left-click to select the marked tile in the interactive window, and right-click to end.

    insert image description here

  1. The result shows: the wrong grid is exported, and it is superimposed on the map with the original map tiles, which is convenient for comparison and viewing.

    insert image description here

  2. Fix wrong tiles: Check whether the map itself has the same problem according to the range and type of wrong border tiles.

  • If the same problem exists, after modifying the correct display effect in the map, re-specify the wrong tile range to generate tiles.
  • If the same problem does not exist, you need to check the cause according to the specific situation. For example: if there are black lines on the tiles, but the map itself has no black lines, check whether the display of Windows is 100% when cutting the map. If the display is not 100%, there may be white lines, black lines and other abnormal display. After modifying the Windows display to 100%, re-cut the tiles, and the tiles display normally.

Guess you like

Origin blog.csdn.net/supermapsupport/article/details/132015066