my data
My data module supports add data and add database. The added data is listed in the data list according to categories and can be published as a service.
1. Add data
Open the "Mapmost Studio" software, switch to the "My Data" module in the left navigation bar, and click "Add Data" to enter the corresponding data addition page.
Select the corresponding data type according to the data that needs to be added.
Please note that when the data to be added is a general 3D model, please select the corresponding model type according to the type of data to be added, such as OBJ, FBX or GLTF.
The following is a description of the fields you need to fill in when adding data:
| Field | illustrate |
|---|---|
| data type | Required, supports selecting the corresponding data type as needed, and supports single selection. |
| Model type | Required, only displayed when using a general 3D model. You can choose OBJ, FBX or GLTF. |
| Data name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| input file | Required, the input file is determined according to the selected data type. Please see the table below for details. |
| Remark | Not required, fill in the remarks as needed |
Different data types support uploaded file types as follows:
| data type | Supported file types |
|---|---|
| vector data | .zip (must contain.shp,.shx,.dbf,.prj) |
| image | .tif/.tiff |
| terrain | .tif |
| Universal 3D model | The general 3D model service supports 3 model types, namely OBJ, FBX, and GLTF. OBJ: The file format is.obj or.zip. The zip format is suitable for model data with a material description file.mtl. Please ensure that the path set by the mtlib instruction in the.obj file is consistent with the path of the.mtl file relative to the.obj file. At the same time, the relative path of the specific material must be correctly set in the.mtl file. FBX: The file format is.fbx. GLTF: The file format is.gltf,.glb or.zip. The zip format is suitable for discrete glTF model data. Please ensure that the relative paths used to index other files in each file in the package are set correctly. For example, there are usually xx.gltf and xx.bin files as well as many xxx.jpg files in the package, so the relative paths of xx.bin and xxx.jpg set in xx.gltf must be correct. |
| Tilt 3D model | .zip. The zip package must include the Data directory. The folders under which the tilt model data are stored are stored. Each folder stores.osgb files. If there is a metadata.xml file at the same level as Data, the spatial reference and zero point coordinates will be automatically parsed from the file. |
| point cloud data | .las |
| picture | .png/.jpg/.hdr |
When uploading data, the system will automatically verify the compliance of the data format and prompt for missing data files and missing coordinate information.
Add data drawer action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data adding process, and the entered content will not be saved. |
| Add to | Click Add to save the current content and return to the data list, where you can view the upload progress. |
2. Add database
Open the "Mapmost Studio" software, switch to the "My Data" module in the left navigation bar, click "Add Database" to enter the corresponding database addition page.
| Field | illustrate |
|---|---|
| Alias | Required, customize the name of the database to be displayed in studio, the length should be within 4-20 characters. |
| Database name | Required, the name of the database to be connected. |
| Database address | Required. The database address is the network location identifier used to locate and access the database server. It usually refers to the IP address (or domain name), such as 192.168.1.1:3306. |
| Database port | Required, usually the default port number is 5432. |
| Database type | Required, currently only supports PostgreSQL and cannot be modified. |
| Schema | Required, the schema specified by the user when connecting. |
| username | Required, the user name used to log in to the database. |
| password | Optional, the password corresponding to the user name used to log in to the database. |
| Remark | It is not required and can be filled in according to the actual situation. |
Add database drawer action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current database adding process, and the entered content will not be saved. |
| Add to | Click Add to save the current content and return to the database list. You can view the added database in the database list. |
3. Data list
The data list displays resources saved by adding data/adding database, and supports operations such as data publishing service, data download, data deletion, data sharing, associated projects, and data filtering.
3.1. Data-vector data
3.1.1. Release
Successfully uploaded vector data supports publishing operations.
①Single data release: table operation-publish, supports single data release.
②Batch data release: Select multiple data to be released and click the release button in the multi-select operation box above the table.
Please note: Under the vector data type, batch data publishing only supports mvt type services and does not support geojson type services.
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Basic information:
| Field | illustrate |
|---|---|
| Service type | Required, the two service types are mvt and geojson respectively. Among them, if you publish the mvt vector map service, you need to regenerate the slices after the data is updated, and the service content will not automatically change with the changes in the original data; if you publish the geojson dynamic data service, it will directly respond to the real-time query results, and the service content will be automatically updated as the underlying data changes. |
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Source coordinate system | Optional, supported source coordinate systems include EPSG:4326, EPSG:3857, EPSG:4528, EPSG:4490, EPSG:4549, Suzhou 2000 |
| preview center | Optional, the latitude and longitude are automatically calculated based on the selected spatial field and table name. |
| Service cache | Optional, can only be set under mvt type. Setting the service cache for data that changes infrequently can improve service loading performance. It is recommended to start with a value of 256MB and the maximum value should not exceed 1024MB. |
| cache type | Optional, only displayed under mvt type, you can select memory or disk. Among them, the memory cache supports extremely fast response but fails to restart, which is suitable for high-frequency access and small data volume scenarios; the disk cache supports persistent storage but is slightly slower, and is suitable for large-capacity or long-term stable data services. |
| Remark | It is not required and can be filled in according to the actual situation. |
Layer information:
| Field | illustrate |
|---|---|
| table name | Required. When the original data comes from the data center: it is automatically filled in based on the selected data; when the original data comes from the database: it needs to be filled in by selecting it from the drop-down box or searching for the table name. |
| Layer name | Required, only displayed under mvt type, defaults to the same as the table name; name requirements: length 4-32, composed of letters, numbers, and underscores, and must start with a lowercase letter. |
| spatial field | Required, the spatial field is automatically read according to the selected table content, and geom is displayed. Click to select; if the table content has no spatial field, "This table has no spatial field" will be displayed. Please note: If there is no space field, it cannot be published. Please replace the table and try again. |
| Space ID | Required, just select the id field generated by importing the pg library. |
| Hierarchy scope | Required, set the minimum and maximum levels of vector data slicing. The data will only be sliced within this range, which can significantly improve slicing efficiency and front-end loading performance. Default level range: 0-24. |
| attribute field | Optional. Check the attribute fields required for service publishing. You can select them selectively or select them all. |
| Add new layer | Optional. When the original data comes from the database and the service type is mvt, you can click to add a layer. A map service can add up to 25 layers. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.1.2. Download
Data successfully uploaded by myself can be downloaded to the local area, but data shared by others cannot be downloaded.
①Single data download: table operation-download, supports single data download.
② Batch data download: Select multiple data to be downloaded and click the download button in the multi-select operation box above the table.
3.1.3. Delete
Only data uploaded by yourself can be deleted. Data shared by others & data of associated projects cannot be deleted.
①Single data deletion: table operation-deletion, supports single data deletion.
② Batch data deletion: Select multiple data to be deleted and click the delete button in the multi-select operation box above the table.
Please note:
The vector data of published services does not support deletion, and the data of associated projects does not support deletion.
3.1.4. Sharing
Only the data successfully uploaded by myself supports sharing. The operation path is: table operation-sharing.
Sharing supports sharing by typing or searching for members' real names. The names of members who have been shared will be displayed in the sharing pop-up window.
3.1.5. Related projects
①Single associated item: table operation-associated item, supports single data association.
② Batch related projects: Select the data of multiple projects to be related, and click the related project button in the multi-select operation box above the table.
Related projects support searching by project name or table selection, and supporting multiple projects.
3.1.6. Filtering
Data list supports filtering
①Supports data filtering by keyword-data name, data owner
②Support filtering by upload time
3.1.7. Rename
The data name supports renaming, and you can only rename the data you uploaded.
3.2. Data-Image
3.2.1. Publishing
Successfully uploaded image data supports publishing operations.
①Single image data release: table operation-publish, supports single image data release.
②Batch data release: Select multiple data to be released and click the release button in the multi-select operation box above the table.
Publish Image Service:
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically filled based on selected input data. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Basic information:
| Field | illustrate |
|---|---|
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Uploader | Required, automatically entered, cannot be modified. |
| Remark | It is not required and can be filled in according to the actual situation. |
Coordinate parameters:
| Field | illustrate |
|---|---|
| spatial reference | Optional, spatial reference can be vividly compared to the positioning system of geographical data, which defines how to identify and place data at specific locations on the earth. The spatial reference is used to determine the true location of the data. Improper setting of this will result in incorrect location of the processing results or even processing failure. If the input file contains spatial reference information, the system will automatically recognize it and no settings are required at this time. Otherwise, the user needs to manually specify it based on the spatial reference of the data. Supports filling in ENU coordinates, EPSG encoding, and strings in PROJ or WKT format indicating spatial reference. Automatic filling is supported after clicking the button at the bottom to select. |
| Longitude and latitude local coordinate system | Optional, fill in the longitude and latitude, and automatically construct an ENU string. |
| EPSG encoding search | Optional, fill in the encoding to automatically construct an EPSG string. |
| Zero point coordinates | Optional. Specify the offset of the data origin relative to the spatial reference. It is divided into three directions: xyz and unit meter. The default is no offset (0,0,0). Setting this value allows the data to be offset in the corresponding direction. It is generally used for problems where the coordinates of a three-dimensional model are very large and difficult to operate in certain projected coordinate systems. It is therefore assumed that the data has an offset position, then in this spatial reference: modeled coordinates + zero point coordinates = projected coordinates. |
Processing parameters:
| Field | illustrate |
|---|---|
| maximum level | Optional, the maximum level parameter controls the level to which the tile can ultimately be enlarged. Default: Automatically calculated, the value will be calculated based on the raster data resolution. Supports self-setting, the range is [10, 25], the actual value will be the set value and the automatically calculated minimum value. The default value is recommended. |
| Tile size | Optional, the pixel width and height of the image after slicing, supports 256 and 512. According to common tradition, the tile size is 256, but in fact it can be set to 512, which can reduce the number of tile requests on large screens. |
| Service type | Optional. The slice index organization method in the published image service supports WMTS and TMS. WMTS starts from level 0, with the upper left corner of the map as the origin, the positive direction of the horizontal axis from left to right, and the positive direction of the vertical axis from top to bottom. The slice index of the published WMTS service type is in the form of {z}/{x}/{y}. TMS takes the lower left corner of the map as the origin, and the vertical axis is the positive direction from bottom to top. |
| Projection type | Optional, Mercator and latitude and longitude formats are supported. |
| background transparent | Optional. Background transparency is used to solve the problem of white or black edges in the data after slicing. Three methods are supported. Automatic: Automatically determine which band is transparent based on the band metadata of the raster, suitable for data with complete metadata information. Fourth band: If the number of bands in the raster is greater than 3, then the fourth band is forced to be a transparent band, which is suitable for actual data that has a fourth band and is determined to be a transparent value. Transparent color: No matter how many bands the raster has, as long as the read color is equal to the RGB value set here, the pixel is considered to be purely transparent, which is suitable for data with incomplete transparency information. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.2.2. Download
The detailed operation of downloading image data is the same as Vector data download
3.2.3. Delete
The detailed operation of image data deletion is the same as Vector data removed
3.2.4. Sharing
The detailed operation of image data sharing is the same as Vector Data Sharing
3.2.5. Related projects
The detailed operations of the image data association project are the same as Vector Data Association Project
3.2.6. Filtering
The detailed operation of image data list filtering is the same as Vector data list filter
3.2.7. Rename
The image renaming operation is the same as Vector data renaming
3.3. Data-Terrain
3.3.1. Publishing
Successfully uploaded terrain data supports publishing operations.
①Single data release: table operation-publish, supports single data release.
②Batch data release: Select multiple data to be released and click the release button in the multi-select operation box above the table. Batch data publishing only supports the Quantized-Mesh service type.
Publish Terrain Service:
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Basic information:
| Field | illustrate |
|---|---|
| Service type | Required, the two service types are Quantized-Mesh and Terrain-RGB; only the Quantized-Mesh service type is supported when selecting multiple data. Quantized-Mesh is available with Mapmost SDK for UE5 and Terrain-RGB is available with Mapmost SDK for WebGL. |
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Uploader | Required, automatically entered, cannot be modified. |
| Remark | It is not required and can be filled in according to the actual situation. |
Coordinate parameters:
| Field | illustrate |
|---|---|
| spatial reference | Optional, only supported when Quantized-Mesh is selected as the service type. Spatial reference can be vividly compared to the positioning system of geographical data, which defines how to identify and place the specific location of data on the earth. The spatial reference is used to determine the true location of the data. Improper setting of this will result in incorrect location of the processing results or even processing failure. If the input file contains spatial reference information, the system will automatically recognize it and no settings are required at this time. Otherwise, the user needs to manually specify it based on the spatial reference of the data. Supports filling in ENU coordinates, EPSG encoding, and strings in PROJ or WKT format indicating spatial reference. Automatic filling is supported after clicking the button at the bottom to select. |
| Longitude and latitude local coordinate system | Optional, supported when Quantized-Mesh is selected as the service type. Fill in the longitude and latitude, and automatically construct the ENU string. |
| EPSG encoding search | Optional, supported when Quantized-Mesh is selected as the service type. Fill in the encoding to automatically construct an EPSG string. |
Processing parameters:
| Field | illustrate |
|---|---|
| Trigonometric algorithm | Optional, supported when Quantized-Mesh is selected as the service type. Supports both ctb and vcg. ctb: A fast mesh-based triangle network simplification algorithm, which is characterized by fast speed and the processing time is about 1/60 of vcg, but the error is large. Default ctb. vcg: Triangulation network simplification algorithm based on the classic edge collapse algorithm. It is characterized by better grid structure quality and small errors, but slow processing speed. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.3.2. Download
The detailed operation of terrain data download is the same as Vector data download
3.3.3. Delete
The detailed operation of deleting terrain data is the same as Vector data removed
3.3.4. Sharing
The detailed operation of terrain data sharing is the same as Vector Data Sharing
3.3.5. Related projects
The detailed operation of the terrain data association project is the same as Vector Data Association Project
3.3.6. Filtering
The detailed operation of terrain data list filtering is the same as Vector data list filter
3.3.7. Rename
The terrain renaming operation is the same as Vector data renaming
3.4. Data-Universal 3D Model
3.4.1. Release
Successfully uploaded general 3D model data supports publishing operations.
①Single data release: table operation-publish, supports single data release.
②Batch data release: Select multiple data to be released and click the release button in the multi-select operation box above the table. Batch data publishing only supports publishing of the same data type.
For example: If the selected data file formats are all zip, batch data release is supported; if the selected data A file formats are all zip, and the data B file format is fbx, batch data release is not supported.
Publish universal 3D model service:
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
| Model type | Required, brought in by default according to the model type corresponding to the selected data. The general 3D model service supports 3 model types: OBJ: the file format is.obj or.zip. FBX: The file format is.fbx. GLTF: The file format is.gltf,.glb or.zip. Please note: If the model type does not correspond to the file format, publishing will fail. |
Basic information:
| Field | illustrate |
|---|---|
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Uploader | Required, automatically entered, cannot be modified. |
| Remark | It is not required and can be filled in according to the actual situation. |
Coordinate parameters:
| Field | illustrate |
|---|---|
| spatial reference | Required, spatial reference can be vividly compared to the positioning system of geographical data, which defines how to identify and place the specific location of data on the earth. The spatial reference is used to determine the true location of the data. Improper setting of this will result in incorrect location of the processing results or even processing failure. If the input file contains spatial reference information, the system will automatically recognize it and no settings are required at this time. Otherwise, the user needs to manually specify it based on the spatial reference of the data. Supports filling in ENU coordinates, EPSG encoding, and strings in PROJ or WKT format indicating spatial reference. Automatic filling is supported after clicking the button at the bottom to select. |
| Longitude and latitude local coordinate system | Optional, fill in the longitude and latitude, and automatically construct an ENU string. |
| EPSG encoding search | Optional, fill in the encoding to automatically construct an EPSG string. |
| Zero point coordinates | Optional. Specify the offset of the data origin relative to the spatial reference. It is divided into three directions: xyz and unit meter. The default is no offset (0,0,0). Setting this value allows the data to be offset in the corresponding direction. It is generally used for problems where the coordinates of a three-dimensional model are very large and difficult to operate in certain projected coordinate systems. It is therefore assumed that the data has an offset position, then in this spatial reference: modeled coordinates + zero point coordinates = projected coordinates. For details, please refer to: https://mp.weixin.qq.com/s/wapDcuesF_emaCsj9vMzFQ |
| Flip YZ coordinates | Optional. If the Y axis of the model is upward, the Z axis will be upward after turning on this switch, and vice versa. This option is used to solve the problem of inconsistent upward axis when the 3D engine is loaded after the service is released. |
| Output coordinate system | Optional, supports Mapmost default coordinate system and EPSG: 4978 as the service output coordinate system. If you need to use Mapmost loading service, it is recommended to choose MM coordinate system (Mapmost default coordinate system), the service loading speed is faster; if you need to be compatible with Cesium or Mapmost loading service, it is recommended to choose CesiumIS coordinate system (EPSG: 4978). Select Mapmost's default coordinate system, which does not support vertex compression. |
Processing parameters:
| Field | illustrate |
|---|---|
| processor | Optional, divided into small scene processor and octree processor. The characteristic of the small scene processor is that it does not make any simplification or scaling of the input data and uses the original precision. But it will do merging, compression, splitting, etc. Maximize data loading efficiency without losing display quality. In general, small scene processors are used to publish services. Only when the data cannot be loaded after processing, the octree processor is considered to create LOD. Creating LOD requires high algorithms and takes a long time to run. |
| Maximum slice | Optional, supported by small scene processor. This parameter controls the maximum slice size, unit MB, range [1-256]. The default is 20MB, which means that if some b3dm exceeds 20MB during processing, try to split it. |
| Number of instance optimizations | Optional, supported by small scene processor. This parameter indicates that if the number of times a geometry is reused exceeds this value, i3dm will be used for rendering, otherwise b3dm will be used. The higher the model reuse rate, the greater the significance of i3dm optimization. It is best to match and adjust based on the data to achieve a balance between rendering batches and data volume. The default is 50. |
| minimum level | Optional, supported by octree processor. The default is automatic: that is, automatic identification based on model data, and supports specification. However, it is generally recommended to be level 16, corresponding to an accuracy of 0.59 meters, which means that the difference of about half a meter can be clearly seen at most. |
| level range | Optional, supported by octree processor. The level range is used to determine the maximum level. The calculation formula is: maximum level = minimum level + level range. The supported value range is [0, 8] |
| LOD strategy | Optional, supported by octree processor. Reconstruction and simplification: Divide the data into blocks according to the octree block boundaries and try to simplify within each block. This strategy is characterized by its simplicity and strong adaptability, but the simplification speed is too slow, and some surface normal vectors are incorrect. Size filtering: Calculate the pixel size of the object based on the size of each object and the current octree level. When it is greater than the minimum pixel parameter, the object is stored in the current octree node. Under this strategy, each object is not actually streamlined, but the loading priority of each object is different depending on its size, which is suitable for complex BIM models with a very large number of components. |
| Triangle network simplification | Optional, supported by octree processor. It is effective when the LOD strategy selects reconstruction and simplification. If it is not turned on, the geometry will not be reconstructed, but the texture will be reconstructed. Turn on to reduce the number of vertices. If the geometry density in the scene is very complex, it is recommended to turn it on. |
Texture parameters:
| Field | illustrate |
|---|---|
| Texture merging | Optional, supported by small scene processor. Texture merging is an optimization of merging textures with repeated mapping. |
| texture format | It is optional and divided into four types: default, basis, webp and ktx2. Default: Use jpg (non-transparent) or png (transparent) format. Basis: The compression speed is faster and supports multi-platform use on PC, Android, and iPhone. webp: The size is about 70% of the default jpg, which can speed up network transmission but does not reduce video memory usage. ktx2: The size is about 90% of the default jpg, reducing video memory consumption by 5/6, but the service release time will increase. |
| color to texture | Optional, turned off by default. This option is suitable for BIM components with almost no texture inside. Most components are of different colors. In order to reduce the rendering batch, turn it on. |
Compression parameters:
| Field | illustrate |
|---|---|
| vertex compression | Optional, select Mapmost's default coordinate system, which does not support vertex compression. When vertex compression is turned on, the Draco compression algorithm will be used to reduce the storage amount of vertex data, with a compression rate of about 1/7, thereby saving the amount of transmitted data. |
| Compression level | It is not required and is divided into elementary, intermediate and advanced levels. You can choose according to your own requirements. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.4.2. Download
The detailed operation of downloading general 3D model data is the same as Vector data download
3.4.3. Delete
The detailed operation of general 3D model data deletion is the same as Vector data removed
3.4.4. Sharing
The detailed operation of general 3D model data sharing is the same as Vector Data Sharing
3.4.5. Related projects
The detailed operation of the general 3D model data association project is the same as Vector Data Association Project
3.4.6. Filtering
The detailed operation of general 3D model data list filtering is the same as Vector data list filter
3.4.7. Copy data address
Successfully uploaded data supports copying the data address. Click the copy button to copy the data address to the clipboard. The data address can be used by front-end developers. By loading the data address, the 3D model can be loaded and displayed.
3.4.8. Rename
The 3D model renaming operation is the same as Vector data renaming
3.5. Data-tilt 3D model
3.5.1. Publishing
Successfully uploaded tilted 3D model data supports publishing operations. Tilted 3D models only support a single data release: table operation-publish.
Publish oblique 3D model service:
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Is the field supplement required? - Completed
Basic information:
| Field | illustrate |
|---|---|
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Uploader | Required, automatically entered, cannot be modified. |
| Remark | It is not required and can be filled in according to the actual situation. |
Coordinate parameters:
| Field | illustrate |
|---|---|
| spatial reference | Optional, spatial reference can be vividly compared to the positioning system of geographical data, which defines how to identify and place data at specific locations on the earth. The spatial reference is used to determine the true location of the data. Improper setting of this will result in incorrect location of the processing results or even processing failure. If the input file contains spatial reference information, the system will automatically recognize it and no settings are required at this time. Otherwise, the user needs to manually specify it based on the spatial reference of the data. Supports filling in ENU coordinates, EPSG encoding, and strings in PROJ or WKT format indicating spatial reference. Automatic filling is supported after clicking the button at the bottom to select. |
| import from file | It is optional. Select the corresponding metadata.xml, and the spatial reference and zero coordinates will be automatically parsed. The SRS tag in the file is the spatial reference, and the SRSOrigin tag is the zero coordinate. |
| Longitude and latitude local coordinate system | Optional, fill in the longitude and latitude, and automatically construct an ENU string. |
| EPSG encoding search | Optional, fill in the encoding to automatically construct an EPSG string. |
| Zero point coordinates | Optional. Specify the offset of the data origin relative to the spatial reference. It is divided into three directions: xyz and unit meter. The default is no offset (0,0,0). Setting this value allows the data to be offset in the corresponding direction. It is generally used for problems where the coordinates of a three-dimensional model are very large and difficult to operate in certain projected coordinate systems. It is therefore assumed that the data has an offset position, then in this spatial reference: modeled coordinates + zero point coordinates = projected coordinates. |
| Output coordinate system | Optional, supports Mapmost default coordinate system and EPSG: 4978 as the service output coordinate system. If you need to use Mapmost loading service, it is recommended to choose MM coordinate system (Mapmost default coordinate system), the service loading speed is faster; if you need to be compatible with Cesium or Mapmost loading service, it is recommended to choose CesiumIS coordinate system (EPSG: 4978). Select Mapmost's default coordinate system, which does not support vertex compression. |
Rebuild top level:
| Field | illustrate |
|---|---|
| Rebuild the top level | Optional. The top-level reconstruction function will use octree reconstruction based on the tile space structure relationship. Therefore, when enabled, the service rendering speed will be accelerated, but the service release time will be increased. It is disabled by default. |
Effect parameters:
| Field | illustrate |
|---|---|
| Force double sided | Optionally, the texture is forced to be rendered on both sides, that is, both front and back sides. Generally, there is no need to turn it on, but for some abnormal data, there may be loopholes caused by front and back cropping. You can try turning this option on to achieve the purpose of double-sided rendering. |
| No light | Not required. Turn this option on for a more realistic rendering effect. It is turned on by default. However, because the generated tiles do not contain normal information, and some engines render this type of data black, you can try turning off this option to avoid this problem. |
Compression parameters:
| Field | illustrate |
|---|---|
| vertex compression | Optional, select Mapmost's default coordinate system, which does not support vertex compression. When vertex compression is turned on, the Draco compression algorithm will be used to reduce the storage amount of vertex data, with a compression rate of about 1/7, thereby saving the amount of transmitted data. |
| Compression level | It is not required and is divided into elementary, intermediate and advanced levels. You can choose according to your own requirements. |
| texture format | Optional, the default is jpg format: the format in the original osgb. webp: The size is about 70% of the default jpg, which can speed up network transmission. ktx2: The size is about 90% of the default jpg, reducing video memory consumption by 5/6, but the service release time will increase. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.5.2. Download
The detailed operation for downloading tilted 3D model data is the same as Vector data download
3.5.3. Delete
The detailed operation of deleting tilted 3D model data is the same as Vector data removed
3.5.4. Sharing
The detailed operation of tilted 3D model data sharing is the same as Vector Data Sharing
3.5.5. Related projects
The detailed operation of the tilted 3D model data association project is the same as Vector Data Association Project
3.5.6. Filtering
The detailed operation of filtering the oblique 3D model data list is the same as Vector data list filter
3.5.7. Rename
The renaming operation of the tilted 3D model is the same as Vector data renaming
3.6. Data-point cloud data
3.6.1. Release
Successfully uploaded point cloud data supports publishing operations.
①Single data release: table operation-publish, supports single data release.
②Batch data release: Select multiple data to be released and click the release button in the multi-select operation box above the table.
Publish point cloud data service:
Input data:
| Field | illustrate |
|---|---|
| Data name | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Is the field supplement required? - Completed
Basic information:
| Field | illustrate |
|---|---|
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Uploader | Required, automatically entered, cannot be modified. |
| Remark | It is not required and can be filled in according to the actual situation. |
Coordinate parameters:
| Field | illustrate |
|---|---|
| spatial reference | Required, spatial reference can be vividly compared to the positioning system of geographical data, which defines how to identify and place the specific location of data on the earth. The spatial reference is used to determine the true location of the data. Improper setting of this will result in incorrect location of the processing results or even processing failure. If the input file contains spatial reference information, the system will automatically recognize it and no settings are required at this time. Otherwise, the user needs to manually specify it based on the spatial reference of the data. Supports filling in ENU coordinates, EPSG encoding, and strings in PROJ or WKT format indicating spatial reference. Automatic filling is supported after clicking the button at the bottom to select. |
| Longitude and latitude local coordinate system | Optional, fill in the longitude and latitude, and automatically construct an ENU string. |
| EPSG encoding search | Optional, fill in the encoding to automatically construct an EPSG string. |
| Zero point coordinates | Optional. Specify the offset of the data origin relative to the spatial reference. It is divided into three directions: xyz and unit meter. The default is no offset (0,0,0). Setting this value allows the data to be offset in the corresponding direction. It is generally used for problems where the coordinates of a three-dimensional model are very large and difficult to operate in certain projected coordinate systems. It is therefore assumed that the data has an offset position, then in this spatial reference: modeled coordinates + zero point coordinates = projected coordinates. |
Processing parameters:
| Field | illustrate |
|---|---|
| color storage | Optional, if this option is turned on, we will store the color of the point cloud in 3dtiles. Note that some laser-scanned point clouds generally do not have color values, while the point clouds generated by oblique processing are colored, so enable this option based on your own data. If not enabled, the amount of 3dtiles will be reduced. |
| maximum level | Optional. The maximum level is related to the point cloud density. If it is too small, the accuracy of the point cloud will be reduced. If it is too large, the processing time will be increased and too many Tiles will be generated. The default is 20. |
Compression parameters:
| Field | illustrate |
|---|---|
| vertex compression | Optionally, if vertex compression is turned on, the Draco compression algorithm will be used to reduce the amount of vertex data stored, thereby saving the amount of transmitted data. |
| Compression level | Optional. The higher the compression level, the greater the compression rate, and the loss of data accuracy will be greater. It is recommended to use the intermediate level. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.6.2. Download
The detailed operation of point cloud data download is the same as Vector data download
3.6.3. Delete
The detailed operation of point cloud data deletion is the same as Vector data removed
3.6.4. Sharing
The detailed operation of point cloud data sharing is the same as Vector Data Sharing
3.6.5. Related projects
The detailed operation of the point cloud data association project is the same as Vector Data Association Project
3.6.6. Filtering
The detailed operation of point cloud data list filtering is the same as Vector data list filter
3.6.7. Rename
The point cloud data renaming operation is the same as Vector data renaming
3.7. Data-Pictures
3.7.1. Download
The detailed operation for downloading pictures is the same as Vector data download
3.7.2. Delete
Only pictures uploaded by yourself can be deleted. Pictures shared by others cannot be deleted.
①Single picture deletion: table operation-delete, supports single picture deletion.
② Batch picture deletion: Select multiple pictures to be deleted and click the delete button in the multi-select operation box above the table.
Please note: Pictures of associated projects cannot be deleted.
3.7.3. Sharing
The detailed operation of image sharing is the same as Vector Data Sharing
3.7.4. Related projects
The detailed operation of the picture association project is the same as Vector Data Association Project
3.7.5. Filtering
The detailed operation of filtering the picture list is the same as Vector data list filter
3.7.6. Copy data address
Successfully uploaded images support copying the data address. Click the copy button to copy the image address to the clipboard. This image address can be used by front-end developers, and image loading and display can be achieved by loading this address.
3.7.7. Rename
The image renaming operation is the same as Vector data renaming
3.8. Database
3.8.1. Edit
The added database supports editing operations. Click to enter the edit database page, as shown in the figure above. You can modify it as needed and then add it again.
3.8.2. Release
The database supports publishing mvt type and geojson type services, which can be selected according to needs.
database:
| Field | illustrate |
|---|---|
| Alias | Required, automatically populated based on selected input. If you need to modify it, please exit the data publishing drawer and re-select the data to be published in the data list. |
Field description supplement is required or not - Completed
Basic information:
| Field | illustrate |
|---|---|
| Service type | Required, the two service types are mvt and geojson respectively. Among them, if you publish the mvt vector map service, you need to regenerate the slices after the data is updated, and the service content will not automatically change with the changes in the original data; if you publish the geojson dynamic data service, it will directly respond to the real-time query results, and the service content will be automatically updated as the underlying data changes. |
| Service name | Required, the name must start with a lowercase letter, be 4-32 characters in length, and consist of letters, numbers, and underscores. |
| Source coordinate system | Optional, the supported source coordinate systems are as follows: EPSG:4326, EPSG:3857, EPSG:4528, EPSG:4490, EPSG:4549, Suzhou 2000 |
| preview center | Optional, the latitude and longitude are automatically calculated based on the selected spatial field and table name. |
| Service cache | Optional, can only be set under mvt type. Setting the service cache for data that changes infrequently can improve service loading performance. It is recommended to start with a value of 256MB and the maximum value should not exceed 1024MB. |
| cache type | Optional, only displayed under mvt type, you can select memory or disk. Among them, the memory cache supports extremely fast response but fails to restart, which is suitable for high-frequency access and small data volume scenarios; the disk cache supports persistent storage but is slightly slower, and is suitable for large-capacity or long-term stable data services. |
| Remark | It is not required and can be filled in according to the actual situation. |
Layer information:
| Field | illustrate |
|---|---|
| table name | Required, when the original data comes from the data center: it is automatically filled in based on the selected data; when the original data comes from the database: you need to select from the drop-down box or search the table. |
| Layer name | Required, only displayed under mvt type, defaults to the same as the table name; name requirements: length 4-32, composed of letters, numbers, and underscores, and must start with a lowercase letter. |
| spatial field | Required, the spatial field is automatically read according to the selected table content, and geom is displayed. Click to select; if the table content has no spatial field, "This table has no spatial field" will be displayed. Please note: If there is no space field, it cannot be published. Please replace the table and try again. |
| Space ID | Required, just select the id field generated by importing the pg library. |
| attribute field | It is not required. Check the attribute fields required for drawing. You can select them selectively or select them all. |
| Add new layer | Optional. When the original data comes from the database and the service type is mvt, you can click to add a layer. A map service can add up to 25 layers. |
Publish Drawer Action:
| Field | illustrate |
|---|---|
| Cancel | Click Cancel to exit the current data publishing process, and the entered content will not be saved. |
| release | Click Publish, the current content is saved and published into the corresponding service, and the progress can be viewed in My Services - Service List. |
3.8.3. Delete
The database supports delete operations
Please note: Databases of published services and databases of associated projects do not support deletion.
3.8.4. Related projects
Related projects: table operations - related projects, supporting single database association. Related projects support searching by project name or table selection, and supporting multiple projects.
3.8.5. Filtering
Data list supports filtering
①Supports database filtering through keyword-database alias, and supports data table filtering through table names.
②Support filtering by database update time
