Data catalog service introduction |
It provides a convenient data organization and management way. Through the data catalog service, the data hosted by SuperMap iServer and user self-management data can be managed centrally. The powerful data management capabilities to support the management of multiple iServer DataStore, supports the management of thousands of relational datasets and spatio-temporal datasets. The data catalog service provides for the common users with access to the various types of data, including relational data, binary data, large data file sharing data, tile data and spatio-temporal large data. Also, it supports creating/deleting/uploading/downloading dataset in the iServer hosted database.
The relational data managed in the data catalog service relies on iServer DataStore management capabilities to store the datasets in its built-in postgresql database. The functions on the relational data include: view datasets, create / delete datasets, upload data, download data and publish as GIS services.
In the dataset list of the relationship/datasets resource, you can view all relational datasets hosted in iServer DataStore and all the relational datasets in the registered spatial database. These dataset sources include: 1 the existing datasets in iServer DataStore; 2 the datasets created by the data catalog service; 3 the imported datasets; 4 the existing datasets in the registered spatial database.
It supports creating/deleting datasets in the relationship/datasets resource.
New Dataset:
Input the dataset name and type, you can create an empty dataset in the relational datasource in iServer DataStore. It also supports inputting the prjCoordSys information to create an empty dataset with coordinates information. After the dataset is created successfully, it can get the dataset resource, its url is relationship/datasets/{datasetName}.
The types of datasets currently supported are POINT, POINTEPS, LINE, LINEEPS, REGION, REGIONEPS, TEXT, TEXTEPS, CAD, TABULAR
Delete dataset.
You can delete the corresponding dataset by sending a Delete request to the dataset resource relationship / datasets / {datasetName}.
Under the relationship / dataimport resource, you can upload datasets. The supported file types include: UDB datasource, CSV file, workspace, Excel file, GeoJson file, shape file and the udb datasource, shape file and workspace need to be compressed to * .zip format.
When the dataset is uploaded successfully, it returns a unique dataID that is used to represent the uploaded file. A detailed description of the packet can be obtained by accessing the relationship / datas / {dataID} resource.
The successfully uploaded dataset appears in the dataset list of the relationship / datasets resource.
If both the DataStore and an editable spatial database are registered into iServer,the editable spatial database will be preferred for storage; If only the DataStore is registered into iServer, the DataStore will be used for storage.
If multiple editable spatial database are registered into iServer, the database which has the least number of datasets will be used for storing the uploaded data.
For the Shape-type files, they only can be stored into the registered editable HBase database.
Under relationship/datas resource, you can download datasets. The supported file types include: udb and Shape files. For the workspace-type data ,the supported download format also supports workspace type; For the Shape-type data, the download format only supports Shape type.
The "Quick Publish Service" function in the iServer management module supports publishing relational data in the data category service as a map service, data services, and spatial analysis services.
Input the data address of the data catalog service, format as: :http://{ip}:{port}/iserver/services/datacatalog/rest/datacatalog/relationship/datas/{dataID}
The binary data managed in the data catalog service relies on the management capabilities of the iServer DataStore, which stores the data files in the associated MongoDB database in binary stream, where the version of the MongoDB database needs to be 3.2 above. The functions for binary data include: viewing the data list, uploading / downloading / deleting data.
Under the binary/datas resource, you can view the binary data ID that was uploaded successfully in the data catalog service. You can view the details of the data by clicking the link for the data ID.
In the binary / dataimport resource, support uploading and storing various types of data files to the MongoDB database associated with iServer DataStore in the form of binary stream.
When the data is uploaded successfully, it returns a unique dataID that is used to represent the uploaded file. A detailed description of the packet can be obtained by accessing the binary/datas/{dataID} resource.
On the binary / datas / {dataID} resource page, click "Delete" in the data information list box to delete the corresponding data file in MongoDB. Click "Download" to automatically download the data file.
The datasets managed in the sharefile resource of the data catalog service is the large data file sharing that the iServer administrator registers through the "cluster" "data registration" function. The data registration function can register the CSV file and the UDB datasource in the HDFS directory and the shared directory as their corresponding dataset.
You can view the dataset details by clicking on the dataset name listed on the sharefile resource page.
The cache data managed in the data catalog service relies on the management capabilities of the iServer DataStore, which stores the data files in the associated MongoDB database in cache format, where the version of the MongoDB database needs to be 3.2 above. The functions for cache data include: viewing the data list, uploading / downloading / deleting data.
Under the tiles/datas resource, you can view the cache data ID that was imported successfully in the data catalog service. You can view the details of the data by clicking the link for the data ID.
In the tiles / dataimport resources, supports importing and storing the tiles in form of SMTiles and GeoPackage into the MongoDB database associated with iServer DataStore.
When the data is uploaded successfully, it returns a unique dataID that is used to represent the uploaded file. A detailed description of the packet can be obtained by accessing the tiles/datas/{dataID} resource.
The "Quick publish Service" function in the iServer management module supports publishing the cache data in the data catalog service as a map service.
Input the data address of the data catalog service, format as: :http://{ip}:{port}/iserver/services/datacatalog/rest/datacatalog/tiles/datas/{dataID}
In the dataset list of the spatiotemporal/datasets resource, you can view all spatio-temporal datasets hosted in iServer DataStore.