technical specifications
Product version
Version number:v9.0.0
functional ability
Multi-source data support
2D vector data and services
- supportGeoJSONData, supported by defaultEPSG:4490andEPSG:4326Coordinate system, other coordinate data need to be converted to the default coordinate system and loaded.
- support Mapmost Studio Published vector tile service.
- passGeoServerpublishedEPSG:3857Coordinate system vector tile service inMapmost StudioRegister to access.
2D raster service
- Supported service types:
- WMTS:Like the sky map,ArcGISStatic slicing service
- WMS:likeArcGISDynamic services
- TMS
- 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.
- 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 source Supported services Supported coordinate systems sky map Map of the sky (_wlogo) EPSG:3857 Map of the sky (_clogo) EPSG:4490 ArcGIS Dynamic services 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 Slicing service EPSG: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 platforms WMTS EPSG: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 WMS EPSG: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 TMS EPSG:3857
3D model data
- Supported model formats:glTF、GLB、 FBX、OBJFormat.
- support draco vertex compression,KTX2.0 Texture compression.
- 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 type CGCS2000 GeoJSON EPSG:4490/EPSG:4326 vector tiles EPSG:3857 grid service EPSG:3857、EPSG:4326、EPSG:4490、EPSG:4528and can be passedproj4The coordinate system for coordinate transformation 3D model Modeling coordinate systemEPSG:3857 3DTiles EPSG:4978
technical limitations
Supported platforms
Mobile configuration
Andriod:
| Classification | Standard configuration | Recommended configuration |
|---|---|---|
| Memory | Memory8Gand above | Memory12Gand above |
| CPU | Snapdragon870or equivalent processor | Snapdragon8Core and above performance processor |
| system | Android10 | Android11 |
IOS:
| Classification | Standard configuration | Recommended configuration |
|---|---|---|
| chip | A15 | A17 pro |
| system | IOS 15 | IOS 17.5.1 |
| model | iphone 13 | iphone 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:
Note: The minimum refresh frame rate required for the 3D system to run smoothly is30FPSaboveFrame rate (FPS) experience describe 0-29 Interaction lag is obvious similarPPTPage turning effect, the movement is completely intermittent 30-44 Smooth Similar to earlier games, slightly smeared but barely coherent 45-59 High fluency Close to movie quality, natural dynamic blur 60 Extremely smooth Smooth as water, no afterimage in high-speed lenses
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 type Data format First screen loading time (S) Refresh frame rate (FPS) Supported data volume (10,000) 2D point layer GeoJSON ≤4 60 10 vector service ≤2 60 30 2D annotation layer GeoJSON <4 60 5 Vector slice ≤2 60 15 2D line layer GeoJSON ≤4 60 5 Vector slice <2 60 40 2D polygon layer GeoJSON <4 60 5 Vector slice <4 60 30 3D extruded body GeoJSON <4 60 10 Vector slice <3 60 30
- Vector data includes two-dimensional point, line, surface, annotation and extruded volume layer data. The specific performance indicators are as follows:
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.