Data catalog service introduction |
The data catalog services provide a convenient way to organize and manage data. With data catalog service, you can set the SuperMap iServer-hosted data and user-self-managed data can be managed centrally. The powerful data management capability supports the management of multiple iServer DataStores, thereby supporting the management of thousands of relational data sets and spatio-temporal data sets. The data catalog services provides access for ordinary users to view and retrieve various types of data, including relational data, binary data, big data file share data, tile data, and spatio-temporal big data. In addition, data catalog service supports the ability to create and delete data sets, and upload-download data from the iServer managed database. For databases registered on iServer and databases managed by iServer DataStore, they can also be published as services through publishing data catalog . Please refer to the following table for the data types that can be imported and the service types that can be published for databases registered on iServer and managed by iServer DataStore::
Managed/registered database in data catalog service | Data type supported for import | Service type supported for publishing | |||||||||||
UDB | CSV | SMWU | SXWU | Excel | geojson | shp | SMTiles | GeoPackage | REST-map | REST-data | REST-spatialAnalysis | ||
Relational data | PostGIS(data registration) | √ | √ | - | - | √ | √ | √ | - | - | √ | √ | √ |
PostgreSQL(data registration) | √ | √ | √ | √ | √ | √ | √ | - | - | √ | √ | √ | |
PostgreSQL(Datastore) | √ | √ | √ | √ | √ | √ | √ | - | - | √ | √ | √ | |
Oracle(data registration) | √ | √ | - | - |
√ |
√ |
√ |
- | - | √ | √ |
√ |
|
DM (data registration) | √ | √ | - | - | √ | √ | √ | - | - | √ | √ | √ | |
HighGo DB (data registration) | √ | √ | - | - | √ | √ | √ | - | - | √ | √ | √ | |
KINGBASE(data registration) | √ | √ | √ | √ | √ | √ | √ | - | - | √ | √ | √ | |
Yukon(data registration) | √ | √ | - | - | √ | √ | - | - | - | √ | √ | - | |
Vastbase(data registration) | √ | √ | - | - | √ | √ | - | - | - | √ | √ | - | |
HDFS(data registration) | - | √ | - | - | √ | √ | - | - | - | √ | √ | √ | |
Binary data | MongoDB(Datastore) |
Importing data from iServer is not supported |
Publishing as a service is not supported |
||||||||||
Spatio-temporal data | Elasticsearch(Datastore) |
Importing data from iServer is not supported |
Publishing as a service is not supported |
||||||||||
Tile cache data | MongoDB(data registration) |
Importing data from iServer is not supported |
Publishing as a service is not supported |
||||||||||
MongoDB(Datastore) | - | - | - | - | - | - | - | √ | √ | √ | - | - |
Relying on the management capabilities of iServer DataStore, the relational data managed in data catalog service is stored in built-in PostgreSQL database. The functions of data catalog service for relational data include: viewing data sets, creating/deleting data sets, uploading data, downloading data, and supporting publishing as GIS services.
Under the dataset list of the relationship/datasets resource, you can see all relational data sets in iServer DataStore and all relational data sets under the registered spatial database. Data sets come from the following sources: 1. Existing data set in iserver DataStore; 2. Data set created through data catalog service; 3. Data set imported through data set import function; 4. Existing data set in registered spatial database.
Note: Viewing video data set and topology data set is not supported at present.
Under the relationship/datasets resource, creation and deletion of datasets are supported.
Create dataset:
By entering the name and type of the dataset, an empty dataset can be created in the relational data source of iServer DataStore. It also supports passing in prjCoordSys information to create an empty dataset with coordinate information. After the successful creation of the dataset, the dataset resource will be obtained with the URL: relationship/datasets/{datasetName}
Currently supported dataset types include POINT, POINTEPS, LINE, LINEEPS, REGION, REGIONEPS, TEXT, TEXTEPS, CAD, and TABULAR
Delete dataset:
For dataset resource relationship/datasets/{datasetName}, send a delete request to delete the corresponding data set.
Under the relationship/data import resource, you can upload the data set. Supported file types include: UDB data source, CSV file, workspace, Excel file, GeoJson file, and Shapefile file. The import format of UDB data source, shapefile and workspace need to be compressed to *.zip format.
After the data set upload success, a unique dataID is returned to represent the data package of the uploaded file. You can visit the relationship/datas/{ dataID } resource to get a detailed description of the package.
The dataset uploaded successfully also appears in the dataset list in the relationship/datasets resource.
If DataStore has already registered with iServer and editable spatial databases have been registered, editable spatial databases is prior to select for storage; If there is no registered editable database, DataStore is prior to select for storage.
If multiple editable spatial databases are registered, the database with fewer data sets is preferred when uploading data.
Under the relationship/datas resource, you can download the data set. The formats supported for downloading include: UDB and Shapefile files. If the uploaded data is of workspace type, the supported download format also includes workspace; if the uploaded data is of Shapefile type, only Shapefile is included.
The quickly publish service function in the iServer management module supports publishing relational data in data catalog service as map services, data services and spatialanalyst service.
When publishing, you need to specify data catalog data. The format is: 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 iServer DataStore to store data files in a binary stream format in an associated MongoDB database. The MongoDB database version needs to be 3.2 or above. The functions of the data catalog service for binary data include: viewing data lists, uploading/downloading/deleting data.
Under binary/datas resource, you can view the binary data ID of the upload success in the data catalog service. You can view the detailed information of the data by clicking the link of the data ID.
Under the binary/dataimport resource, various types of data files can be uploaded and stored in the form of binary streams in the MongoDB database associated with iServer DataStore
After the data upload successfully, a unique dataID will be returned to represent the data package of the uploaded file. You can visit the binary/datas/{dataID} resource to get a detailed description of the package.
On the binary/datas/{dataID} resource page, click Delete in the data info list box to delete the corresponding data file in MongoDB; click Download, and the browser will automatically download the data file.
The sharefile resource management dataset in the data catalog service is a big data file share registered by iServer administrators through the cluster->data registration function in iServer. The data registration function provides the ability to register CSV files and UDB data sources in the HDFS directory and share directory as their corresponding datasets.
You can view the dataset detailed information by clicking the dataset name listed on the sharefile resource page.
The tile cache data managed in the data catalog service relies on the management capabilities of iServer DataStore to store data files in a binary stream format in an associated MongoDB database. The MongoDB database version needs to be 3.2 or above. The functions of data catalog service for tile cache data include: viewing data list, uploading/downloading/deleting data.
Under the tiles/datas resource, you can view the successfully imported tile cache data IDs in the data catalog service. You can view the detailed information of the data by clicking the link of the data ID.
Under the tiles/dataimport resource, it is supported to import and store SMTiles and GeoPackage tile packages into the MongoDB database associated with iServer DataStore.
After the data uploaded successfully, a unique dataID will be returned to represent the data package of the uploaded file. You can access tiles/datas/{dataID} resource to obtain a detailed description of the package.
The quickly publish service function in the iServer management module supports publishing the tile cache data in the data catalog services as map services.
When publishing, you need to specify data catalog data in the format: HTTP://{IP}:{port}/iserver/services/datacatalog/rest/datacatalog/tiles/datas/{dataID}
Under the dataset list of the spatiotemporal/datasets resource, you can view all spatio-temporal datasets currently hosted by iServer in iServer DataStore.