Skip to main content

abilityLimit

#Technical Specifications

Product version​

Version number: v9.12.0-beta

Functional capabilities​

Multi-source data support​

2D vector data and services​

  1. Supports GeoJSON data. The EPSG:4490 and EPSG:4326 coordinate systems are supported by default. Other coordinate data need to be converted to the default coordinate system for loading.
  2. Support the vector tile service published by Mapmost Studio.
  3. The EPSG:3857 coordinate system vector tile service published by WMTS data through GeoServer can be registered and accessed in Mapmost Studio.

2D Raster Service​

  1. Supported service types:
    • WMTS: Rutian Map, ArcGIS static slicing service [using quadtree slicing scheme]
    • WMS: dynamic services such as ArcGIS
    • TMS
  2. Supported coordinate systems: EPSG:3857 is supported by default, EPSG:4326, EPSG:4528, and EPSG:4490 can be configured through the project parameters. Other coordinate systems can be loaded by setting a custom spatial reference.
  3. Static slicing service format: XYZ format, that is, the URL template contains {z}/{x}/{y}, such as https://example.com/{z}/{x}/{y}.png. Details are shown in the table below:
    Service sourceSupported serviceSupported coordinate system
    Tian MapTian Map (_w logo)EPSG:3857
    Heaven Map (_c logo)EPSG:4490
    ArcGISDynamic ServicesEPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: You need to provide the coordinate system proj4 description, the tile cutting origin, the resolution of each level of the tile, and the tile size
    Slicing ServiceEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: You need to provide the coordinate system proj4 description, the tile cutting origin, the resolution of each level of the tile, and the tile size
    Other platformsWMTSEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: You need to provide the coordinate system proj4 description, the tile cutting origin, the resolution of each level of the tile, and the tile size
    WMSEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: You need to provide the coordinate system proj4 description, the tile cutting origin, the resolution of each level of the tile, and the tile size
    TMSEPSG:3857
    Note: There is a performance gap between Mapmost SDK for WebGL when loading ArcGIS-related services and the native framework. Regardless of network speed, the overall loading speed is 1 second slower than the native framework; at the same time, it only supports loading ArcGIS static tile services that use the quadtree slicing scheme.

3D model data​

  1. Supported model formats: glTF, GLB, FBX, OBJ format.
  2. Support draco vertex compression and KTX2.0 texture compression.
  3. The modeling coordinate system of the model is EPSG: 3857.

Note: The model special effects and submersion analysis functions of the 3D model require the model to face upward in the Local coordinate system (the object’s own coordinate system) in the Blender software.

3D model service​

The 3D model service currently supports 3DTiles-v1.0 data service and I3S-v1.3 data service.

  1. 3DTiles
    Currently supports 3DTiles-v1.0 and 3DTiles-v1.1 data formats.

    • Raw data: manual modeling
      • Service release platform: Studio, CesiumLab-v4.0.7 (as of February 13, 2025). -Supports octree mode and small scene mode.
      • KTX2 texture compression is supported, and the 3DTiles service must have the KHR_texture_basisu extended attribute.
    • Raw data: Skewed data (OSGB)
      • Service release platform: Studio, CesiumLab-v4.0.7 (as of February 13, 2025).
      • Support top-level merging.
      • KTX2 texture compression is supported, and the 3DTiles service must have the KHR_texture_basisu extended attribute.
    • Note: Service publishing configuration requires the correct spatial reference to be entered.

  2. I3S

    • Supports I3S-v1.3 version data format loading.
    • Supports EPSG:3857, EPSG:4490, EPSG:4326, EPSG:4528 coordinate system and Suzhou 2000 coordinate system.

Terrain Services​

  • Supports the Terrain-RGB format released by the Studio platform, but does not support the quantized-mesh format released by CesiumLab.

Video Fusion​

Load video file​

  • Data format support: Supports video formats supported by the HTML5 video tag, including MP4, WebM, and Ogg.

Load real-time video​

  • Data format support: supports Hls video stream and Flv video stream, supports h264 encoding layer standard format.

3D video projection​

  • Data format support: supports MP4, img, Flv formats.

    Note: Obtaining video projection related parameters requires relying on the video calibration tool. For details, please contact customer service (lower right corner).

Spatial analysis​

  • Supports 7 spatial analysis methods, including surface excavation analysis, submergence analysis, and tilt single analysis. There are differences in the data types supported by different spatial analysis.

    Analysis TypeVectorRaster3D Model3DTilesI3SMultiple Instance Creation
    Surface excavation analysissupportsupportnot supportnot supportnot supportnot support
    flooding analysisnot supportednot supportedsupportedsupportedsupportedsupported
    Tilted single analysisNot supportedNot supportedSupportedSupportedSupportedSupported
    visual area analysissupportnot supportsupportsupportsupportsupport
    visual analysissupportnot supportsupportsupportsupportnot support
    cube sectionsupportnot supportsupportsupportsupportnot support
    Measurement (area and distance)supportsupportsupportsupportsupportnot support

Coordinate system​

Supports CGCS2000 coordinate system and Suzhou 2000 coordinate system

CGCS2000 coordinate system​

The matching data format and coordinate system processing relationship under the coordinate system are as follows:

data typeCGCS2000
GeoJSONEPSG:4490/EPSG:4326
vector tileEPSG:3857
Raster serviceEPSG:3857, EPSG:4326, EPSG:4490, EPSG:4528 and coordinate systems that can be transformed through proj4
3D modelModeling coordinate system EPSG:3857
3DTilesEPSG:4978
I3SEPSG:3857、EPSG:4326、EPSG:4490、EPSG:4528

Suzhou 2000 coordinate system​

Adapting to business needs in Suzhou area, instructions for using the Suzhou 2000 coordinate system

data typecoordinate systemprocessing processloading method
Vector map serviceSuzhou 2000Use Mapmost Studio to publish, select "Suzhou 2000"Call the loading interface
Raster ServiceNoneCall the loading interface addRasterLayer2
3D model (GLB)NoneModel center point coordinates: adjust the conversion interface and convert Suzhou 2000->SDK coordinates
Vector data (GeoJSON)NoneCalling the GeoJSON file coordinate conversion interface: Suzhou 2000->SDK coordinates
Oblique data (OSGB)Use Mapmost Studio to publish, select "EPSG:3857"Call the loading interface
I3S serviceNoneCall loading interface
GPS collection pointWGS84Backend service: 84->Suzhou 2000Calling the coordinate conversion interface, Suzhou 2000->SDK coordinate

Technical limitations​

Supported platforms​

Offline authorization configuration​

CategorySupported Configuration
CPU2 cores and above
Memory8GB and above
Operating SystemUbuntu 2204
Note: Mapmost SDK for WebGL offline authorization and Mapmost Studio server need to be deployed on different servers.

Client configuration​

ClassificationStandard configurationRecommended configuration
CPUIntel Core i5 equivalent or higher configurationIntel Core i7 equivalent or higher configuration
GPUNvidia GeForce GTX 1060Nvidia GeForce RTX 3060
Video Memory3GB8GB
memory8GB16GB
Operating systemWindows 10 64-bit operating systemWindows 10 64-bit operating system
BrowserChrome 100+, enable WebGL featuresChrome latest version, enable WebGL features
Note: For supported operating systems and browser versions, the minimum client configuration for 3D system development and operation must meet the recommended configuration requirements. Complex 3D scene development requires higher hardware configuration to ensure performance requirements.

Performance limitations​

1. Performance indicators and interactive experience grading​

  • Performance indicators
    • First screen loading time: the time from the triggering of the loading command to the completion of loading of all scenes
    • Frame rate: the number of frames displayed per second, the unit is FPS
  • Interactive experience grading
    • In order to facilitate users to have an intuitive feeling about the frame rate indicator, the experience is graded based on the frame rate value.
    • Based on a display with a maximum refresh frame rate of 60Hz (corresponding to 60FPS), running under the recommended hardware configuration (regardless of the impact of the network environment), the corresponding relationship between frame rate and interactive experience is as follows:
      Frame rate (FPS)ExperienceDescription
      0-29Interaction lag is obviousSimilar to PPT page turning effect, the movement is completely intermittent
      30-44SmoothSimilar to early games, slightly smeared but barely coherent
      45-59High fluencyClose to movie texture, natural dynamic blur
      60Extremely smoothSmooth as water, no afterimage in high-speed lenses
      Note: The refresh frame rate for the 3D system to run smoothly needs to be at least 30FPS.

2. Description of performance limitations​

  • Test scenario description
    • Single scene performance: The test scene only contains a single type of data, with no other load interference.
    • Mixed scene performance: The test scene contains multiple types of data overlays (such as vector layers, 3D models, video streams, etc.).
  • Performance limit requirements (the performance limits given in the technical specifications refer to the maximum data load amount that the engine can simultaneously meet the following requirements)
    • Regardless of network impact
    • First screen loading time ≤4s
    • Refresh frame rate ≥30FPS

3. Single scene performance​

  • vector data

    • Vector data includes two-dimensional point, line, surface, annotation and extruded volume layer data. The specific performance indicators are as follows:
      Layer typeData formatFirst screen loading time (S)Refresh frame rate (FPS)Supported data amount (10,000)
      2D point layerGeoJSON≤46040
      Vector Service≤26030
      2D annotation layerGeoJSON/vector service<2≥3010
      2D line layerGeoJSON<46010
      Vector Service<36035
      2D surface layerGeoJSON<36020
      Vector Service<36030
      3D extruded bodyGeoJSON/vector service<36020

  • 3D labels

    • Without turning on annotation avoidance, it supports smooth loading of 3,000 3D labels, refresh frame rate ≥30fps, and first screen loading time <1 second.

  • Video fusion

    • flv video streaming: supports smooth loading of 30 channels of video, refresh frame rate ≥30fps.

  • Batch model

    Number of model triangles (number)First screen loading time (S)Refresh frame rate (FPS)Supported data amount (10,000)
    300≤2≥3070
    1500≤0.5≥303
    10000≤0.5≥300.2
    • Note: The load capacity of a batch model is related to the number of faces of a single model. The more complex a single model is, the smaller the load capacity is.

  • 3D model data

    Data volume (M)Loading time (S)Refresh frame rate (FPS)Number of verticesNumber of trianglesNumber of texturesNumber of Mesh
    20034018993306331103110472
    2503.525473453415781784343785
    • Note: The maximum amount of data supported for a 3D model is related to the number of triangles, textures and meshes of the model, and is not determined by a single factor.

  • 3DTiles service

    Data range (square kilometers)Data volume (G)First screen loading time (S)Dynamic loading time (S)Dynamic refresh frame rate (FPS)
    2785104.6440

4. Mixed scene performance​

The current performance indicators of mixed scenarios (multiple types of data overlay) are still under testing, and specific limit parameters will be updated in subsequent versions.