Instructions
Whether there are some problems in your vector tiles can be checked like white blocks, white lines, missing tiles, ruined tiles and so on through and re- generate tiles for these problem tiles. With the feature of checking tiles, you can check the generated tiles thereby correct them timely.
- iDesktop supports checking the compact tiles and MongoDB tiles.
- iDesktop supports checking raster tiles not vector tiles.
- iDesktop supports tiles generated by multiple tasks.
Function Entrances
- Click Maps tab > Mapping group > Tile Check.
- Right click on a map window and select Tile Check. (iDesktopX)
Operating Instructions
In the Check Tiles dialog box set the following parameters.
- Working Directory : The path of your tiles.
- Check Bounds : Using a GeoJson file describes a polygon to determine the checking bound. Tile contents within the bound will be checked. You are allowed to draw a checking bound and then export as a GeoJson file.
- Specific the project to be checked as users’ needs
- Save Error Data : Check the box to record error results to check.udb datasource under the check folder in the working directory.
- Check Solid Tiles : Checking the box means the tile with a solid color will be checked too.
- Check Block : Checking the box means the tile with more than 100 sequential white pixels along horizontal/vertical directions is considered as a block error tile.
- Regenerate Error Tiles : After checking tiles, error tiles will be re-generated automatically if you check the box. The application will get sub-tasks (*.sci) with errors from the failed folder. If you do not check the box, you can re-generate error tiles in the failed folder through the feature of resuming tiles.
- The correct sub-tasks(.sci) will be saved in the “checked” folder, and the sub-tasks(.sci) with errors will be saved in the “failed” folder.
- check.udb in the “check” folder records error information. In the check.udb datasource, there are some region datasets with names consisting of corresponding denominators of scales of error tiles and every dataset records the boundary of the corresponding error tile.
5 types of errors could be happened.
| Error Type No. (errortype) | Error Types (errordesc) | Error Type Description |
|---|---|---|
| 1 | missing | The tile data does not exist. |
| 2 | white | The tile is not a pure color tile but it is white. |
| 3 | lost | For compact tiles, the cf file is not found. |
| 4 | failure | For compact tiles, the cf file is not opened successfully. |
| 5 | error | There is an error happened when reading the tile. |