Vector TileMap Cartography Consideration
IX. Vector Tile Generation Configuration
This paper summarizes the SuperMap map styles and settings that SuperMap Vector Tile can support and does not support, defines clear capability boundaries, and assists users to make vector maps suitable for Vector Tile production.
SuperMap supports generating vector maps into Vector Tile (.mvt) conforming to the MapBox MVT specification. Tile Data contains the geometry and Attributes of features, and the style of features is described by the MapBox standard style file (style. JSON). And follow the style specification of MapBox GL version 8. For MapBox styles, see: https://www.mapbox.com/mapbox-gl-style-spec.
The Vector Tile generated by SuperMap will be displayed on the SuperMap iClient client based on the MapBox style file, and the client will render and display the Vector Tile using MapBox GL or Open Layers; Among them, OpenLayers supports the rendering and display of Vector Tile of various projections, while MapBox GL only supports the rendering and display of Vector Tile of EPSG3857 projection.
During Generate Vector Tile, the program needs to convert the map style of SuperMap into MapBox style description, but some map styles and settings of SuperMap are not supported by MapBox and cannot be converted into MapBox style description. Display Effects are inconsistent with the map after SuperMap map Generate Vector Tile, or some style and map setting effects are lost.
| Map content, rendering styles, and related configuration | Is Vector Tile supported | Note description | |
|---|---|---|---|
| I. Layer data content | |||
| Vector Dataset | 2D Point, Line, Surface, Text Dataset | Support | Raster Data layers are not supported. If your map contains unsupported Dataset layers, the Generate Vector Tile ignores them. If the Geometry contains too many sub-objects, the cutting speed will be affected when creating the Vector Tile. It is recommended to split the sub-objects to improve the cutting efficiency. |
| 3D Point, Line, Surface, Text Dataset | Support | ||
| Tsinghua Shanwei (EPS) Point, Line, Surface, Text Dataset | Support | ||
| Other Dataset | Not supported | ||
| Geometry complexity | For massive surface data, in order to improve the generation and display efficiency of Vector Tile, the data needs to be thinned. The user can set whether to apply thinning according to the actual data.
|
||
| Vector Data coordinate system | If the coordinate system of the data is different from the map Display Coordinates system, the system will convert the coordinate system of the data to the map Display Coordinates system during Generate Vector Tile. The operation of coordinate system conversion will take up a lot of disk space and time. It is recommended that the user first convert the coordinate system of the data to the map Display Coordinates system, and then Generate Vector Tile. | ||
| 2. Layer Properties Settings | |||
| Layer Visible Scale | Maximum and Minimum Visible Scale. | Support | Vector Tile is created with Global scale, and the visible scale range of the layer in the vector map needs to be adjusted according to the Global scale, otherwise, the display and hidden effects of the map elements of Vector Tile will be inconsistent with the map. The layer visible scale values and Numerical Precision should be exactly the same as the Global scale. |
| The layer displays Filter | Filter Expression | Partially supported | Only simple logical relationship judgment and comparison operations are supported.
|
| Layer Join Attribute Table Settings | Not supported | ||
| Normal Layer and Thematic Layer Aggregation |
The label and the corresponding Vector Layer need to be under the same Layer Group. |
||
| Layer Blend Mode | Not supported | ||
| Scale Symbol | Not supported | ||
| Weight | Not supported | ||
| Thinning Show Settings | Not supported | ||
| Filter overlapping small objects settings | Not supported | ||
| Object Display Order | Not supported | ||
| III. Thematic map | |||
| Unique-values Map | Single value expression | Partially supported | Only single field is supported. Field expression and SQL function Calculate Result, such as name | | '_' | | type, are not supported. |
| Property Field Definition Marker Style | Not supported | Through properties Field Settings Symbol, Color, Size, Rotation angle are not supported. | |
| Theme Layers Offset Settings | Not supported | ||
| Marker Style | Partially supported | For support, refer to the sections of Point symbol, Line symbol and Fill symbol. | |
| Traffic Situation configuration | Not supported | ||
| Graudated Colors Map | Segmentation expression | Support | Currently, only a single field is supported. Field expressions and the SQL function Calculate Result are not supported. |
| Segmentation method | Support | ||
| Segmentation accuracy | Support | ||
| Marker Style | Partially supported | For support, refer to the sections of Point symbol, Line symbol and Fill symbol. | |
| Uniform Label Thematic Map | Label expression | Partially supported | For the annotation field used by the Thematic Label Map, only a single field is currently supported, and the field expression and the SQL function Calculate Result, such as name | | '_' | | type, are not supported. |
| Label background | Partially supported |
When the label background uses a dot symbol, the dot symbol does not automatically resize with the length of the label. |
|
| Label offset | Support | ||
| Pull line | Not supported | ||
| Labels and Alignment | Partially supported | Left Baseline, Right Baseline, and Central Baseline alignment are not supported. | |
| Gland and Avoidance Settings (Flow, No Overlap) | Not supported | The avoidance processing of MapBox is different from that of SuperMap, which leads to differences in the number of labels displayed, labels and alignments, etc. | |
| Typesetting (extra long text handling, line wrapping, multi-line text alignment, Landscape Display Tags) | Not supported | MapBox handles wrapping for long tags differently than SuperMap. Display Effects in the Tile are quite different from the map after the Generate Vector Tile when the settings for label wrapping and the settings for multi-line text typesetting are applied to the Thematic Label Map. | |
| Text Avoidance Tile Range | Not supported | ||
| Label Height Range | Not supported | ||
| Text Style Settings | Partially supported | See the Text Style section for support | |
| Show direction along the label line | Partially supported | The MapBox style only supports two display directions along the line (normal direction along the line and top to bottom, left to right). If the map has other display directions along the line, the Vector Tile will place the label with the direction of "top to bottom, left to right". | |
| Show Slivers | Not supported | ||
| Signature spacing along the line | Not supported | MapBox handles Label Alongline differently than SuperMap, so Vector Tile displays Label Alongline differently than original map. | |
| Relative angle along the line | Not supported | ||
| Label along line mode | Not supported | ||
| Fixed Text Angle | Not supported | ||
| Remove Duplicate Labels | Not supported | ||
| Periodic spacing along the line | Not supported | ||
| Type of label drawing along the line (Split Draw, Entire Draw, Compatible Draw, etc.) | Not supported | ||
| Single-valued Thematic Label Map. | Single value field | Partially supported | Only single field is supported. Field expression and SQL function Calculate Result, such as name | | '_' | | type, are not supported. For the same Point Dataset, if a Unique-values Map and a single-value Thematic Label Map based on the Point Dataset exist at the same time, the single-value fields of the two must use the same field. |
| Other Settings content | Consistent with Uniform Label Thematic Map | ||
| Custom Thematic Map | Not supported | The map contains thematic maps that are not supported. These thematic layers will be ignored for Generate Vector Tile. | |
| Composite Thematic Label Map. | Not supported | ||
| Matrix Thematic Label Map. | Not supported | ||
| Graduated Symbols Map | Not supported | ||
| Statistical Thematic Map | Not supported | ||
| Dot Density Map | Not supported | ||
| Aggregated graphs (thermodynamic, grid, etc.) | Not supported | ||
| IV. Text Style | |||
| Font | Support | Make sure there is a corresponding Font File in the computer. | |
| Text color | Support | ||
| Font size | Support | ||
| Font Effects | Bold | Support | When bold and italic effects are used in the text, it is necessary to ensure that there are bold and italic font library files of the corresponding fonts in the computer, so that the bold and italic effects of the text in the generated Vector Tile are effective. |
| Italics | Support | ||
| Outline | Support | ||
| Shadow | Not supported | ||
| Underline | Not supported | ||
| Strikethrough | Not supported | ||
| Rotation angle | Support | ||
| Tilt (left tilt, right tilt, tilt angle) | Not supported | ||
| Fixed Size | Support | When Generate Vector Tile, the text in the map needs to be set to Fixed Size, otherwise, the text effect displayed by Tile may be different from that of the original map. | |
| Text background | Not supported | The text background appears as a text outline in the Vector Tile. | |
| Superscript | Not supported | ||
| Text typesetting | Multi-line TextAlignment, etc. | Not supported | |
| V. Dot symbol | |||
| System point symbol | System0 | Not supported | The System 0 square dot symbol appears as a dot symbol in the Vector Tile. Bypass scheme: Create a new point symbol and draw a square Geometry to make a square point symbol. |
| System1 | Support | ||
| Vector dot symbol | Support | ||
| Grid point symbol | Support | ||
| Color | Support | ||
| Symbol Rotation angle | Support | ||
| Symbol transparency | Not supported | ||
| Scale Symbol | Not supported | ||
| VI. Line symbol | |||
| System linetype | System0、System1 | Support | |
| System2、System3、System4 | Not supported | System2, System3, System4 linetypes will appear as solid lines in the Vector Tile. Alternative: Create a new linetype, add a dash (system linetype) subline, and adjust the Virtual-real Mode of the subline to make the required dashed linetype. |
|
| Custom linetype | Support | Custom linetypes support linetype symbols that contain more than one child, but each child must be of type Default. | |
| Subline style | Short horizontal line (system line type) | Support | Virtual-real Mode is supported. |
| Other subline types | Not supported | Unsupported sublines appear as solid lines in the Vector Tile. | |
| Sub-line settings | End Symbol | Not supported | |
| Subline offset | Not supported | ||
| Scale Symbol | Not supported | ||
| VII. Fill symbol | |||
| System Fill symbol | System0、System1、System2、System3、System4、System5、System6、System7 | Support | |
| Fill symbol sideline | Consistent with the line notation | The MapBox style supports the contour lines of face symbols in the same way as line symbols. | |
| Custom Fill symbol | Support | Custom Fill Symbol only supports a fill symbol that contains one fill sublayer. The fill sublayer can be Image Filling or the symbol Fill Symbol. | |
| Fill symbol sublayer | Symbol Filling | Support | |
| Image Filling | Support | ||
| Scale Symbol | Not supported | ||
| VIII. Map Properties Settings | |||
| Map Fixed Scale | Support | Vector Tile is created with Global Scale, and the vector map Fixed Scale needs to be adjusted with reference to Global Scale; otherwise, the display and hidden effects of the map elements of Vector Tile will be inconsistent with the map. The layer visible scale values and Numerical Precision should be exactly the same as the Global scale. |
|
| Map Overlap Settings | Not supported | ||
| Fixed Symbol Angle | Not supported | ||
| Fixed Text Angle | Not supported | ||
| Fixed Text Direction | Not supported | ||
| Line Antialiasing | Not supported | ||
| Text Antialiasing | Not supported | ||
| Label weight setting | Not supported | ||
| IX. Vector Tile Generation Configuration | |||
| Slice scale | Global scale | Support | |
| Custom Scale | Not supported | ||
| Slice level range | Continuous scale hierarchy | Support | |
| Discontinuous scale hierarchy | Support | Scale bar levels are not continuous. Missing levels cause Display Effects to appear unexpectedly when the Vector Tile is displayed. | |
| Storage Format | Compact | Support | |
| Original | Support | ||
| MongoDB | Support | ||
| Store the directory | Local Directory | Support | |
| Shared directory | Not supported | ||
| FTP directory | Not supported | ||
| Object storage directory | Partially supported | Only Vector Tiles that support the original Storage Format are stored in the object store. | |
| Tile Bounds | Whole Map | Support | Default slice range |
| Current Windows (Desktop) | Support | Not supported by GPA tool | |
| Custom Bounds-Rectangular Range | Support | GPA tools are specified by Left, Top, Right, Bottom coordinate values | |
| Custom Bounds-Specify Object (Desktop) | Support | Not supported by GPA tool | |
| Custom Bounds-Custom Expression (Desktop) | Not supported | ||
| Origin of Tile | Modify Origin of Tile. | Not supported | |
| Vector Tile parameter | Generate font cache file | Support | "Generate font cache file" needs to be enabled, otherwise, the text content in the resulting Vector Tile is abnormal. |
| Generate Vector Tile | Support | Generate Vector Tiles。 In the Vector Tile update scenario: When Separate Data from Style, if the vector map data does not change, only the map style changes, and the style does not use new field content, there is no need to Generate Vector Tiles again when updating the Vector Tile. Just Generate Tiles Style again. In this case, this item may not be enabled. |
|
| Generate Tiles Style | Support | Generate vector tile style. In the Vector Tile update scenario: When Separate Data from Style, if the vector map only updates the data content and the map style does not change, when updating the Vector Tile, it is not necessary to Generate Tiles Style again, just Generate Vector Tile again. This item may not be enabled. |
|
| Separate Data from Style | Support | Enable "Separate Data from Style" to facilitate separate updates of Vector Tile data and style. | |
| Add All Property Fields | Support | When the Vector Tile is generated, only the attribute Select Fields used by the map will be written into the Vector Tile data. In general, it is not necessary to add all Property Fields, which affects slicing performance when the map data is large. In the Vector Tile update scenario: If the map data does not change, but the map style changes, and new fields are used to match the map, if the Tile is updated, it is not only to Generate Tiles Style again, but also to Generate Vector Tiles again, so that the new fields can be written into the Vector Tile data. |
|
| Rarefy Display | Support | For massive surface data, in order to improve the generation and display efficiency of Vector Tile, the data needs to be thinned. The user can set whether to apply thinning according to the actual data. This setting is only valid for non-PostGISDatasource. If Rarefy Display "is enabled, it indicates that thinning is performed; otherwise, thinning is not performed. For PostGISDatasource, you need to modify the SuperMap. XML file (located in the installation directory/BIn/of iDesktopX), add the label "< mvts implifypgis > TRUE ", and the default value of the parameter value is TRUE. Indicates rarefaction; FALSE indicates no rarefaction. For face objects with dense nodes and complex shapes, under a small scale, after thinning, the resulting Vector Tile has face object deformation, for example:
|
|
| Generate Index | Support | When generating a 3D Web MV TVector Tile, you need to check this option. | |
| Vector Tile breakpoint continuous cut | Not supported | ||
| X. Vector Tile Update | |||
| Vector Tile All Update | Update/Append Tiles "in that iDesktopX" Generate Vector Tile "dialog. | Support | |
| Vector TileLocal update | Support | ||
Related topics