A method for providing real-life 3D data services for mega-cities

Abstract

The present invention relates to the field of three-dimensional technology, and in particular to a method for providing real-life three-dimensional data services for megacities, with the following specific steps: S1, slicing, integrating and building databases for real-life three-dimensional data and publishing services according to a unified grid; S2, dynamically aggregating data according to administrative divisions; S3, authorizing and updating data service addresses; S4, accessing and monitoring real-life three-dimensional data services. The present invention takes into account the grid service management of real-life three-dimensional data sets, as well as dynamic assembly according to administrative divisions, to achieve unified daily management of data services, as well as on-demand, dynamic, fast and secure service provision, that is, on the basis of unified grid data organization, through rapid service aggregation, data provision and updating for municipal, county, town and street, and even community levels are formed, thus achieving the supply of real-life three-dimensional elements for megacities.

Description

Technical Field

[0001] The present invention relates to the field of three-dimensional technology, and in particular to a method for providing a super-large city real-scene three-dimensional data service. Background Art

[0002] Realistic 3D data is a kind of city 3D model with strong sense of reality obtained by using real aerial images and automatic modeling. The daily management of real 3D data can be realized through the standardized organization of model data, and it can be flexibly assembled for various scene applications. Rapid supply and safe use are the basic work to give full play to the value of data elements and carry out urban governance.

[0003] The conventional method of organizing and providing real-life 3D data services is to use the real-life 3D of a single project or administrative division as a service unit, slice and integrate the model data within the scope to form a single package file, and then publish the packaged file as a data service, and provide data to the terminal through an accessible data service address. When the 3D engine loads the address, it can call and render the entire real-life 3D data. This method has the following problems:

[0004] First, data is not uniformly organized and managed according to the scope of the project. Since the scope of the project is not fixed, it is easy to cause data to be scattered, which is not convenient for historical version management, update and rapid scheduling;

[0005] Second, it is not organized according to administrative divisions, making it difficult to provide data services and perform authority control according to different administrative divisions;

[0006] Third, even when organizing by administrative divisions, the maintenance of multiple sets of data caused by administrative division levels is not considered. For example, if there are three levels of city-district-county-town and street, and each level maintains a set of data services, then three sets of model data must be maintained;

[0007] Fourth, the data service organization is not dynamic enough. For example, there are hundreds or thousands of towns and streets in the city. If each town and street is integrated into one data set, the maintenance workload will be huge. Summary of the invention

[0008] The purpose of the present invention is to solve the shortcomings of the prior art and to propose a method for providing real-life three-dimensional data services for a megacity.

[0009] In order to achieve the above object, the present invention adopts the following technical solutions:

[0010] A method for providing real-life 3D data services for mega-cities is designed. The specific steps are as follows:

[0011] S1. Slice real-life 3D data, integrate database building and service publishing according to a unified grid;

[0012] S2. Dynamic data aggregation is carried out according to administrative divisions, as follows:

[0013] (1) Obtaining administrative division scope and code: Obtaining the administrative division organization and code, clarifying the division scope of the city, district, county, town, street and even community, and obtaining a unique division code;

[0014] (2) Retrieve all real-life 3D data within the administrative division: First, calculate the real-life 3D tiles contained in all grid cell databases according to the range of different administrative divisions; since the real-life 3D tiles include multiple level-of-detail models (LODs), further calculate the LOD models contained in the administrative division based on the center point to obtain index information of these LOD models;

[0015] (3) Dynamically combine all LOD models included in the administrative division: reassemble and aggregate them into a new administrative division dynamic database based on the index information, and publish it as an administrative division dynamic data service;

[0016] (4) According to different administrative division codes, a data supply system for the city, district, county, town and street included in the megacity is constructed, and different levels of administrative division codes are assigned to each administrative division dynamic data service. Each data can be named as "sjsw_administrative division code";

[0017] S3, data service address authorization and update;

[0018] S4. Real-life 3D data service access and monitoring.

[0019] Preferably, the specific steps of step S1 are as follows:

[0020] First, determine the grid division method and organize the real-scene 3D data by grid: set the grid origin gridOrg (x0, y0) as the engineering origin during real-scene 3D production. The grid size is determined by the integer multiples of the side length slen of a single real-scene 3D tile and the amount of data after packaging. Set the center point of the grid (xc, yc). The grid number gridID is determined according to the grid origin and size, which is:

[0021] gridID=[(xc-x0) / slen]&&[(yc-y0) / slen]

[0022] According to the center point of the real-scene 3D tile, the real-scene 3D original data is respectively included in the corresponding grids, and the real-scene 3D data in each grid constitutes a real-scene 3D grid unit data set;

[0023] Second, the grid unit data set is packaged into a grid unit database, and the grid unit data service is published. The grid unit data set is used as the basic unit, and the real-life 3D model data is converted through coordinate conversion, format conversion, root node merging, and model sharing. Unified optimization is performed to obtain slice data for loading the Web-side 3D engine. The slice data service is then packaged and built into a database to obtain the grid unit database, which is published as a basic grid unit data service.

[0024] Preferably, the specific steps of step S3 are as follows:

[0025] (1) Data service authorization management;

[0026] (2) Users can access real-life 3D scene configurations;

[0027] (3) Real scene 3D data service update method.

[0028] Preferably, the specific steps of data service authorization management are as follows:

[0029] Establish a real-life 3D data supply management center to authorize users and provide real-life 3D services. Customize an SDK for each user, give a user ID in the SDK, establish the user role in the management center, and configure real-life 3D scenes that only the user can access, so as to achieve the purpose of user authorization.

[0030] Preferably, the specific steps for users to access the real-life 3D scene configuration are as follows:

[0031] Each user establishes an accessible real-life 3D scene, the center of which includes data services accessible to the user, and the data address interface provided by the administrative division is in the following format and remains unchanged;

[0032] http: / / IP:Port number / UserID / sjsw_Administrative division code / Serial number

[0033] After obtaining the data interface, the management center will analyze the accessible real-life 3D specific address based on the user ID, including data of different categories such as terrain, images, and buildings;

[0034] It is also possible to provide data services by grid unit or other custom range organization, the principles and methods are the same as providing by administrative divisions.

[0035] Preferably, the specific steps of the real scene 3D data service update method are as follows:

[0036] Grid unit dataset update: Regardless of the source of the updated data, data is merged, edited, and updated according to the grid unit dataset, thereby avoiding the need to update all datasets;

[0037] Administrative division dataset update: The grid unit dataset update should ensure that the LOD model name in the tile is consistent. If it is inconsistent, it should be dynamically aggregated according to the administrative division to obtain a new administrative division dataset and add a time label.

[0038] Finally, reconfigure the user-accessible real-life 3D scene. In the service management center, the user can reconfigure the accessible real-life 3D scene. At this time, the data address interface provided to the user remains unchanged, avoiding the need for the user to modify the data service address.

[0039] Preferably, the specific steps of step S4 are as follows:

[0040] (1) Record access status based on user SDK

[0041] For different user SDKs, all access situations of the SDK are recorded in the service management center. Different users have different access data, which can be tracked and recorded;

[0042] (2) Record access based on website address IP

[0043] For deployed application websites, all data access information of the application websites is recorded in the service management center. Through IP restrictions, one set of SDKs can be prevented from being used on multiple unauthorized servers.

[0044] (3) Record access based on terminal IP

[0045] For each terminal IP, all access to the SDK is recorded in the service management center. In certain cases, illegal proxy and forwarding of the terminal are controlled.

[0046] Based on these access situations, statistical analysis is performed to analyze abnormal access behaviors as access and monitoring of the service.

[0047] The present invention proposes a method for providing real-life three-dimensional data services for a megacity, which has the beneficial effect that the method takes into account the grid service management of real-life three-dimensional data sets and dynamic assembly according to administrative divisions, thereby realizing unified daily management of data services and providing services on demand, dynamically, quickly and securely. That is, on the basis of unified grid data organization, through rapid service aggregation, data provision and updating for municipal, district, county, town, street and even community levels are formed, thereby realizing the supply of real-life three-dimensional elements for megacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 The present invention provides a flow chart of a method for providing real-life three-dimensional data services for a megacity. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0050] Reference Figure 1 A method for providing real-life 3D data services for a megacity is characterized by the following specific steps:

[0051] S1. Slice the real-life 3D data, build an integrated database and publish services according to the unified grid. The specific steps are as follows:

[0052] First, determine the grid division method and organize the real-life 3D data by grid: set the grid origin gridOrg (x0, y0) as the engineering origin during real-life 3D production. The grid size is determined by the integer multiples of the side length slen of a single real-life 3D tile and the size of the packaged data (e.g., if the tile size is 100m*100m and the data volume is less than 200GB, the grid size can be determined to be approximately 4km*4km, or refer to the approximate standard map size). Set the center point of the grid (xc, yc). The grid number gridID is determined according to the grid origin and size, as follows:

[0053] gridID=[(xc-x0) / slen]&&[(yc-y0) / slen]

[0054] According to the center point of the real-scene 3D tile, the real-scene 3D original data (such as osgb format) are respectively included in the corresponding grids, and the real-scene 3D data in each grid constitute a real-scene 3D grid unit data set (hereinafter referred to as grid unit data set);

[0055] Second, the grid unit data set is packaged into a grid unit database, and the grid unit data service is published. The grid unit data set is used as the basic unit, and the real-life 3D model data is converted through coordinate conversion, format conversion, root node merging, and model sharing. Unified optimization is performed to obtain slice data (such as 3dTiles format or other slice formats) for loading by the Web-side 3D engine. The slice data service is then packaged and built into a database to obtain the grid unit database, which is published as a basic grid unit data service.

[0056] S2. Dynamic data aggregation is carried out according to administrative divisions, as follows:

[0057] (1) Obtaining administrative division scope and code: Obtaining the administrative division organization and code, clarifying the division scope of the city, district, county, town, street and even community, and obtaining a unique division code;

[0058] (2) Retrieve all real-life 3D data within the administrative division: First, calculate the real-life 3D tiles contained in all grid cell databases according to the range of different administrative divisions; since the real-life 3D tiles include multiple level-of-detail models (LODs), further calculate the LOD models contained in the administrative division based on the center point to obtain index information of these LOD models;

[0059] (3) Dynamically combine all LOD models included in the administrative division: reassemble and aggregate them into a new administrative division dynamic database based on the index information, and publish them as administrative division dynamic data services. This process is automated, so it can be quickly and dynamically aggregated into data services;

[0060] (4) According to different administrative division codes, a data supply system for the city, district, county, town and street included in the megacity is constructed, and different levels of administrative division codes are assigned to each administrative division dynamic data service. Each data can be named as "sjsw_administrative division code";

[0061] S3, data service address authorization and update;

[0062] S4, real-life 3D data service access and monitoring, the specific steps are as follows:

[0063] (1) Record access status based on user SDK

[0064] For different user SDKs, all access situations of the SDK are recorded in the service management center. Different users have different access data, which can be tracked and recorded;

[0065] (2) Record access based on website address IP

[0066] For deployed application websites, all data access information of the application websites is recorded in the service management center. Through IP restrictions, one set of SDKs can be prevented from being used on multiple unauthorized servers.

[0067] (3) Record access based on terminal IP

[0068] For each terminal IP, all access to the SDK is recorded in the service management center. In certain cases, illegal proxy and forwarding of the terminal are controlled;

[0069] Based on these access situations, statistical analysis is performed to analyze abnormal access behaviors as access and monitoring of the service.

[0070] 3. The method for providing real-life 3D data services for a megacity according to claim 1, wherein the specific steps of step S3 are as follows:

[0071] (1) The specific steps of data service authorization management are as follows:

[0072] Establish a real-life 3D data supply management center (hereinafter referred to as the management center) to authorize users and provide real-life 3D services. Customize SDK for each user, give a user ID in the SDK, establish the user role in the management center, and configure real-life 3D scenes that only the user can access, so as to achieve the purpose of user authorization;

[0073] (2) The specific steps for users to access the real-life 3D scene configuration are as follows:

[0074] Each user establishes an accessible real-life 3D scene, the center of which includes data services accessible to the user, and the data address interface provided by the administrative division is in the following format and remains unchanged;

[0075] http: / / IP:Port number / UserID / sjsw_Administrative division code / Serial number

[0076] After obtaining the data interface, the management center will analyze the accessible real-life 3D specific address based on the user ID, including data of different categories such as terrain, images, and buildings;

[0077] It can also provide data services by grid unit or other custom range organization, the principle and method are the same as providing by administrative division;

[0078] (3) The specific steps of the real scene 3D data service update method are as follows:

[0079] Grid unit dataset update: Regardless of the source of the updated data, data is merged, edited, and updated according to the grid unit dataset, thereby avoiding the need to update all datasets;

[0080] Administrative division dataset update: The grid unit dataset update should ensure that the LOD model name in the tile is consistent. If it is inconsistent, it should be dynamically aggregated according to the administrative division to obtain a new administrative division dataset and add a time label.

[0081] Finally, reconfigure the user-accessible real-life 3D scene. In the service management center, the user can reconfigure the accessible real-life 3D scene. At this time, the data address interface provided to the user remains unchanged, avoiding the need for the user to modify the data service address and reducing operation and maintenance work.

[0082] The present invention takes into account the grid service management of real-life three-dimensional data sets and dynamic assembly according to administrative divisions, thereby realizing unified daily management of data services and providing services on demand, dynamically, quickly and securely. That is, on the basis of unified grid data organization, through rapid aggregation of services, data provision and updating for municipal, district, county, town, street and even community levels is formed, thus realizing the supply of real-life three-dimensional elements for megacities.

[0083] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A method for providing real-life 3D data services for a megacity, characterized in that: The specific steps are as follows: S1. Slice the real-life 3D data, build an integrated database and publish services according to the unified grid. The specific steps are as follows: First, determine the grid division method and organize the real-scene 3D data by grid: set the grid origin gridOrg (x0, y0) as the engineering origin during real-scene 3D production. The grid size is determined by the integer multiples of the side length slen of a single real-scene 3D tile and the amount of data after packaging. Set the center point of the grid (xc, yc). The grid number gridID is determined according to the grid origin and size, which is: gridID=[(xc-x0) / slen]&&[(yc-y0) / slen] According to the center point of the real-scene 3D tile, the real-scene 3D original data is respectively included in the corresponding grids, and the real-scene 3D data in each grid constitutes a real-scene 3D grid unit data set; Second, the grid unit data set is packaged into a grid unit database, and the grid unit data service is published. With the grid unit data set as the basic unit, the real scene 3D model data is converted into coordinates and formats, and root nodes are merged and the model sharing is optimized uniformly to obtain the slice data for loading the Web-side 3D engine. The slice data service is then packaged and built into a database to obtain the grid unit database, which is published as the basic grid unit data service. S2. Dynamic data aggregation is carried out according to administrative divisions, as follows: (1) Obtaining administrative division scope and code: Obtaining the administrative division organization and code, clarifying the division scope of the city, district, county, town, street and even community, and obtaining a unique division code; (2) Retrieve all real-life 3D data within the administrative division: First, calculate the real-life 3D tiles contained in all grid cell databases according to the range of different administrative divisions; since the real-life 3D tiles include multiple level-of-detail models (LODs), further calculate the LOD models contained in the administrative division based on the center point to obtain index information of these LOD models; (3) Dynamically combine all LOD models included in the administrative division: reassemble and aggregate them into a new administrative division dynamic database based on the index information, and publish it as an administrative division dynamic data service; (4) According to different administrative division codes, a data supply system for the city, district, county, town and street included in the megacity is constructed, and different levels of administrative division codes are assigned to each administrative division dynamic data service. Each data can be named as "sjsw_administrative division code"; S3, data service address authorization and update; S4. Real-life 3D data service access and monitoring.

2. The method for providing real-life 3D data services for mega cities according to claim 1, characterized in that: The specific steps of step S3 are as follows: (1) Data service authorization management; (2) Users can access real-life 3D scene configurations; (3) Real scene 3D data service update method.

3. The method for providing real-life 3D data services for mega cities according to claim 2, characterized in that: The specific steps of data service authorization management are as follows: Establish a real-life 3D data supply management center to authorize users and provide real-life 3D services. Customize an SDK for each user, give a user ID in the SDK, establish the user role in the management center, and configure real-life 3D scenes that only the user can access, so as to achieve the purpose of user authorization.

4. The method for providing real-life 3D data services for mega cities according to claim 2, characterized in that: The specific steps for users to access the real-life 3D scene configuration are as follows: Each user establishes an accessible real-life 3D scene, the center of which includes data services accessible to the user, and the data address interface provided by the administrative division is in the following format and remains unchanged; http: / / IP:Port number / UserID / sjsw_Administrative division code / Serial number After obtaining the data interface, the management center will analyze the accessible real-life 3D specific address based on the user ID, including data of different categories such as terrain, images, and buildings; It is also possible to provide data services by grid unit or other custom range organization, the principles and methods are the same as providing by administrative divisions.

5. The method for providing real-life 3D data services for mega cities according to claim 2, characterized in that: The specific steps of the real scene 3D data service update method are as follows: Grid unit dataset update: Regardless of the source of the updated data, data is merged, edited, and updated according to the grid unit dataset, thereby avoiding the need to update all datasets; Administrative division dataset update: The grid unit dataset update should ensure that the LOD model name in the tile is consistent. If it is inconsistent, it should be dynamically aggregated according to the administrative division to obtain a new administrative division dataset and add a time label. Finally, reconfigure the user-accessible real-life 3D scene. In the service management center, the user can reconfigure the accessible real-life 3D scene. At this time, the data address interface provided to the user remains unchanged, avoiding the need for the user to modify the data service address.

6. The method for providing real-life 3D data services for mega cities according to claim 1, characterized in that: The specific steps of step S4 are as follows: (1) Record access status based on user SDK For different user SDKs, all access situations of the SDK are recorded in the service management center. Different users have different access data, which can be tracked and recorded; (2) Record access based on website address IP For deployed application websites, all data access information of the application websites is recorded in the service management center. Through IP restrictions, one set of SDKs can be prevented from being used on multiple unauthorized servers. (3) Record access based on terminal IP For each terminal IP, all access to the SDK is recorded in the service management center. In certain cases, illegal proxy and forwarding of the terminal are controlled. Based on these access situations, statistical analysis is performed to analyze abnormal access behaviors as access and monitoring of the service.

Images