Skip to main content

technical specifications

Product version

Version number:v9.0.0

functional ability

Multi-source data support

2D vector data and services

  1. supportGeoJSONData, supported by defaultEPSG:4490andEPSG:4326Coordinate system, other coordinate data need to be converted to the default coordinate system and loaded.
  2. support Mapmost Studio Published vector tile service.
  3. passGeoServerpublishedEPSG:3857Coordinate system vector tile service inMapmost StudioRegister to access.

2D raster service

  1. Supported service types:
    • WMTS:Like the sky map,ArcGISStatic slicing service
    • WMS:likeArcGISDynamic services
    • TMS
  2. Supported coordinate systems: supported by defaultEPSG:3857,PassableprojectParameter configuration supportEPSG:4326、EPSG:4528、EPSG:4490,Other coordinate systems can be loaded by setting a custom spatial reference.
  3. Static slicing service form:XYZ format, i.e. URL Template contains {z}/{x}/{y},like https://example.com/{z}/{x}/{y}.png。
    Details are shown in the table below:
    Service sourceSupported servicesSupported coordinate systems
    sky mapMap of the sky (_wlogo)EPSG:3857
    Map of the sky (_clogo)EPSG:4490
    ArcGISDynamic servicesEPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: Coordinate systems need to be providedproj4Description, origin of tile cutting, resolution of each tile level, and tile size
    Slicing serviceEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: Coordinate systems need to be providedproj4Description, origin of tile cutting, resolution of each tile level, and tile size
    Other platformsWMTSEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: Coordinate systems need to be providedproj4Description, origin of tile cutting, resolution of each tile level, and tile size
    WMSEPSG:4490
    EPSG:4528
    EPSG:3857
    EPSG:4326
    Other coordinate systems: Coordinate systems need to be providedproj4Description, origin of tile cutting, resolution of each tile level, and tile size
    TMSEPSG:3857

3D model data

  1. Supported model formats:glTF、GLB、 FBX、OBJFormat.
  2. support draco vertex compression,KTX2.0 Texture compression.
  3. The model modeling coordinate system isEPSG: 3857。

Note: The model special effects of the three-dimensional model require the model to be in Blender in softwareLocalUnder the coordinate system (the object’s own coordinate system) Y The shaft faces upward.

3D model service

Currently only supports3DTiles-v1.0Data services,Not supported3DTiles-v1.1Data format.

  • Raw Data: Manual Modeling
    • Service publishing platform:Studio、CesiumLab-v4.0.7(As of2025Year2moon13day).
    • Supports octree mode and small scene mode.
    • supportKTX2texture compression, and3DTiles Services must come with KHR_texture_basisu Extended attributes.
  • Raw data: skewed data (OSGB)
    • Service publishing platform:Studio、CesiumLab-v4.0.7(As of2025Year2moon13day).
    • Supports top-level merging.
    • supportKTX2texture compression, and3DTiles Services must come with KHR_texture_basisu Extended attributes.
  • Note: Service publishing configuration requires the correct spatial reference to be entered.

video fusion

Load video files

  • Data format support: supportedHTML5 videoVideo formats supported by the tag, includingMP4、WebM、Ogg。

Load live video

  • Data format support: supportedHlsvideo streaming andFlvVideo streaming, supporth264Coding layer standard format.

3D video projection

  • Data format support: supportedMP4、img、FlvFormat.

coordinate system

  • supportCGCS2000coordinate system. The matching data format and coordinate system processing relationship under the coordinate system are as follows:
    data typeCGCS2000
    GeoJSONEPSG:4490/EPSG:4326
    vector tilesEPSG:3857
    grid serviceEPSG:3857、EPSG:4326、EPSG:4490、EPSG:4528and can be passedproj4The coordinate system for coordinate transformation
    3D modelModeling coordinate systemEPSG:3857
    3DTilesEPSG:4978

technical limitations

Supported platforms

Mobile configuration

Andriod:

ClassificationStandard configurationRecommended configuration
MemoryMemory8Gand aboveMemory12Gand above
CPUSnapdragon870or equivalent processorSnapdragon8Core and above performance processor
systemAndroid10Android11

IOS:

ClassificationStandard configurationRecommended configuration
chipA15A17 pro
systemIOS 15IOS 17.5.1
modeliphone 13iphone 15Models with or above configurations

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, in units ofFPS
  • Interactive experience rating
    • 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 the maximum refresh frame rate60Hz(correspond60FPS)display, running under the recommended hardware configuration (regardless of the influence of the network environment), the corresponding relationship between frame rate and interactive experience is as follows:
      Frame rate (FPS)experiencedescribe
      0-29Interaction lag is obvioussimilarPPTPage turning effect, the movement is completely intermittent
      30-44SmoothSimilar to earlier games, slightly smeared but barely coherent
      45-59High fluencyClose to movie quality, natural dynamic blur
      60Extremely smoothSmooth as water, no afterimage in high-speed lenses
      Note: The minimum refresh frame rate required for the 3D system to run smoothly is30FPSabove

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 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 volume (10,000)
      2D point layerGeoJSON≤46010
      vector service≤26030
      2D annotation layerGeoJSON<4605
      Vector slice≤26015
      2D line layerGeoJSON≤4605
      Vector slice<26040
      2D polygon layerGeoJSON<4605
      Vector slice<46030
      3D extruded bodyGeoJSON<46010
      Vector slice<36030
  • 3D label

    • Supported without turning on annotation avoidance8000Three-dimensional labels are loaded smoothly, refreshing the frame rate≥30fps,First screen loading time<2Second.
  • video fusion

    • flvVideo streaming: supported6Road video loads smoothly and refreshes the frame rate≥30fps,First screen loading time9Second.

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.