A real scene three-dimensional oriented one code multiple state data management method and system

Abstract

The application relates to the field of real scene three-dimensional data management, and discloses a one-code multi-state data management method and system for real scene three-dimensional data, which comprises the following steps: collecting and arranging real scene three-dimensional data based on a preset one-code multi-state data model, supporting database construction and system application; pre-processing vector data, three-dimensional model data and oblique photography data; encoding the pre-processed data according to entity classification, spatial position, geometric shape and time information; combining a Yukon database and a local storage mode to construct a one-code multi-state data storage system; taking the code as an index to support linkage management and realize various data updating modes such as object updating and grid updating; and realizing one-code multi-state basic geographic entity query, display, statistical analysis and other functions based on the real scene three-dimensional data management system. The method realizes taking real scene three-dimensional basic geographic entities as management units and correlatively managing multi-state and multi-form data in the real scene three-dimensional data based on entity coding.

Description

TECHNICAL FIELD

[0001] The application belongs to the field of real scene three-dimensional data management, and particularly relates to a one-code multi-state data management method and system for real scene three-dimensional. BACKGROUND

[0002] Real scene three-dimensional is a new type of basic surveying and mapping standardized product, which is mainly constructed by carrying structured, semantic, human-computer compatible understanding and Internet of Things real-time sensing geographic entities on a three-dimensional geographic scene, to provide a unified spatial base for social economic development and departmental informatization. Among them, the geographic entity is a geographic object in the real world that occupies a certain and continuous spatial position and range, and has the same attribute or complete function, and the basic geographic entity refers to the geographic entity collected and expressed by basic surveying and mapping, which is the positioning framework and carrying basis of other geographic entities and related information. The basic geographic entity needs to express its semantic attributes, spatial structure, geographic position, time characteristics and other multi-dimensional information using standardized norms due to its semantic and structured characteristics, which involves massive heterogeneous data. Therefore, to meet the expression and application needs of the basic geographic entity, orderly and efficient integrated management of various heterogeneous data has become a great challenge for real scene three-dimensional data management.

[0003] At present, the real scene three-dimensional data management method mainly adopts the conventional method of managing geographic big data. For example, the patent with the publication number CN115471617A adopts a slice index updating method, and the patent with the publication number CN114549761A adopts a distributed storage method. Although these methods can solve the problem of massive data storage and management, they do not conform to the characteristics of real scene three-dimensional entity description of the geographic world, and fail to take advantage of the management of heterogeneous data with entity coding as the link, making it difficult to meet the application service needs of the structured and semantic basic geographic entity of real scene three-dimensional. In order to support intelligent comprehensive application of real scene three-dimensional data, a new data management method is proposed, which realizes fast storage, unified management and on-demand update of data in units of entities, and can effectively meet the application needs of real scene three-dimensional basic geographic entity services. SUMMARY

[0004] To solve the needs mentioned in the background technology, the purpose of the present application is to provide a one-code multi-state data management method and system for real scene three-dimensional, which realizes the correlation management of multi-form and multi-temporal data in real scene three-dimensional by entity coding.

[0005] The purpose of the present application can be achieved by the following technical solutions:

[0006] In a first aspect, a one-code multi-state data management method for real scene three-dimensional is provided, comprising the following steps:

[0007] S1: Collect and organize real scene three-dimensional data based on a preset one-code multi-state data model, the one-code multi-state data model is designed by comprehensively analyzing the attribute, form, and time characteristics of the basic geographic entity;

[0008] S2: Preprocess the real scene three-dimensional data, the real scene three-dimensional data includes vector, three-dimensional model, digital orthophoto, and oblique photography, the preprocessing operation includes format conversion, coordinate conversion, map edge joining, and quality control;

[0009] S3: Assign a unique code to the basic geographic entity according to the entity classification, spatial position, geometric form, and time information, and perform grid subdivision and coding on the digital orthophoto and oblique photography data;

[0010] S4: Store the vector and three-dimensional model data in the Yukon database, and store the digital orthophoto and oblique photography data locally according to the spatial grid and year;

[0011] S5: Use the code as an index to update all data related to the same entity or the same grid;

[0012] S6: Based on the constructed real scene three-dimensional data management system, automatically associate the index and process the display based on the coding, to realize the all-round expression of entity multi-form and multi-time.

[0013] Further, the one-code multi-state data model described in S1 is specifically:

[0014] The basic geographic entity is the core concept of the real scene three-dimensional product system, as the positioning framework and carrier of other geographic entities and related information, its state can be divided into form and time; from the form, the basic geographic entity has two-dimensional and three-dimensional forms, the two-dimensional form includes vector form, digital orthophoto form, etc., the three-dimensional form includes white model form, oblique photography single model form, and three-dimensional fine model form; from the time, the same basic geographic entity has different attributes, geometric forms, and entity relationships at different time points; the one-code multi-state data model organizes the data of each state as a management unit based on the basic geographic entity, and correlates and organizes them through unified coding, supports finding all related data of the entity through coding, and realizes the integrated storage, management, and display of various data.

[0015] Further, the preprocessing of real scene three-dimensional data in S2 is specifically:

[0016] Under the condition of ensuring lossless information conversion, convert different formats of real scene three-dimensional data into a unified data exchange format;

[0017] Convert real scene three-dimensional data in different coordinate systems to the 2000 national geodetic coordinate system;

[0018] The data in the form of a map is edge-joined to ensure the integrity of the data.

[0019] The spatio-temporal reference correctness and attribute integrity of the final result data are checked.

[0020] Further, the real scene three-dimensional data encoding method described in S3 is:

[0021] Vector and three-dimensional model data encoding: the vector and three-dimensional model data encoding uses a three-part entity encoding format, specifically: spatial position code + classification code + time code; wherein the spatial position code uses Beidou grid position code and is adaptively adjusted according to the characteristics of the basic geographic entity to expand the grid level in two-dimensional and three-dimensional space. The position code is divided into two forms of 26-bit two-dimensional position code and 44-bit three-dimensional position code, the vector data uses the two-dimensional position code, and the three-dimensional model data uses the three-dimensional position code; the 6-bit classification code is used to record the first and second classes of entity classification, and the real scene three-dimensional basic geographic entity classification code is used as the standard; the 8-bit time code is used to record the time information of the current state of the entity, and the format is yyyymmdd, wherein y represents the year, m represents the month, and d represents the day; the encoding result is stored in the attribute of the basic geographic entity.

[0022] Oblique photography and digital orthophoto data encoding: oblique photography and digital orthophoto data have continuity and do not directly express single entities, only record the spatial position information of the data, and quickly find the oblique photography and digital orthophoto of the entity at the spatial position by entity encoding; before encoding, the two types of data are sliced according to the grid division rules of each level space, and the 26-bit spatial position code is set as the slice file name.

[0023] Further, the two-dimensional and three-dimensional data storage method based on Yukon database described in S4 is as follows:

[0024] The encoded vector data and three-dimensional model data are uniformly organized and stored in the domestic Yukon database. Yukon database is a relational database supporting two-dimensional and three-dimensional integrated spatial data storage after adding yukongeomodel, yukongeogridcoder and other modules based on PostGIS, which can better meet the data management, visualization and analysis needs of one code multiple states. In terms of data organization design, the vector data is stored according to the entity first class, each table takes the entity code as the primary key, and the three-dimensional model data is stored in a single table, and the table name is the entity code.

[0025] Further, the local data storage method combined with spatio-temporal characteristics described in S4 is:

[0026] The digital orthographic image and the oblique photography data after the slicing are managed in a local storage mode, classified by using a secondary folder for facilitating data indexing. In the method, the source data is classified by a primary folder according to data year, and classified by a secondary folder according to the slicing grid accuracy in the same year folder, and the digital orthographic image and the oblique photography slicing data of the same year and the same accuracy are stored in the secondary folder.

[0027] Further, the real scene three-dimensional data updating method described in S5 includes the following two methods:

[0028] Entity updating: updating the vector data and the three-dimensional model data in units of basic geographic entities; selecting the entities to be updated, searching the data in the Yukon database through the entity code, querying the vector data with the primary key meeting the condition and the three-dimensional model data with the table name meeting the condition, and uniformly replacing the data;

[0029] Grid updating: updating the digital orthographic image and the oblique photography data in units of spatial grids; selecting a specific grid at a certain time point and a certain level to be updated, finding the folder where the slicing data to be updated is located through the time primary folder and the level secondary folder, and finding the data to be updated through the matching of the grid to be updated and the slicing file name to update the data.

[0030] Further, the data indexing and form construction method described in S6 is specifically as follows:

[0031] selecting a specific entity by querying or selecting to obtain the entity code; indexing all the associated data of the forms and the time states in the Yukon database and the local storage folder, including the vector data, the three-dimensional model data, the digital orthographic image data and the oblique photography data; stretching the vector data according to the entity height field to generate a white model, and performing monomerization processing on the digital orthographic image data and the oblique photography data by means of the vector data, to finally generate the vector form, the white model form, the fine model form, the digital orthographic image form and the oblique photography form of the selected entity.

[0032] In a second aspect, a one-code multi-form data management system for real scene three-dimensional is provided, and the system includes the following modules:

[0033] A map browsing module is used for supporting two-dimensional and three-dimensional map browsing, setting a visualization effect of a layer, and providing a map tool to realize a calculation, flight and plotting function;

[0034] An entity query module is used for providing an entity retrieval method according to a code, a name, a spatial position and the like, and supporting fuzzy search;

[0035] A data updating module is configured to provide entity-based and grid-based updating modes according to different updating requirements, automatically find data items to be updated through coding association, and complete data replacement;

[0036] A multi-state display module is configured to display all states and time states of a specific entity based on a code association, display each state using a split screen mode, and provide time node options in each state split screen to switch the time state.

[0037] A statistical analysis module is configured to support two-dimensional and three-dimensional spatial analysis, and provide statistical functions of basic geographic entities according to types, time and states.

[0038] The present application has the following advantages:

[0039] In the use process of the present application, the attribute, state and time characteristics of the basic geographic entity are comprehensively analyzed, and a one-code multi-state data model is designed. The data preprocessing is completed through format conversion and map edge joining. The basic geographic entity is assigned a unique code according to the entity classification, spatial position, geometric state and time information, and the digital orthophoto and oblique photography data are grid divided. The data is classified and stored according to the code by using the combination of Yukon database and local storage. The data updating is realized in multiple modes such as entity-based and grid-based. The real scene three-dimensional data management system is constructed, and the basic geographic entity state and time state are fully displayed through entity code association index, processing and display.

[0040] The present application uses entity code as a link to associate and manage multi-state and multi-state data of basic geographic entities, realizes fast storage, unified management and on-demand updating of data in units of entities, and better meets the application requirements of real scene three-dimensional basic geographic entity service. In addition, the present application proposes a practical and effective one-code multi-state data model, storage system, updating scheme and system application, which provides more efficient and reliable technical method support for the actual management and updating of data in real scene three-dimensional projects. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, for those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

[0042] Figure 1 is a method flowchart of the present application;

[0043] Figure 2 is a one-code multi-state data model schematic diagram in the embodiment of the present application;

[0044] Figure 3is a real scene three-dimensional data encoding rule schematic diagram in the embodiment of the present application;

[0045] Figure 4 is a digital orthophoto / oblique photography storage system schematic diagram in the embodiment of the present application;

[0046] Figure 5 is a real scene three-dimensional data updating flow schematic diagram in the embodiment of the present application;

[0047] Figure 6 is a data index and form construction flow schematic diagram in the embodiment of the present application. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0049] As shown in Figure 1 , a one-code multi-state data management method for real scene three-dimensional, comprising the following steps:

[0050] S1: based on a preset one-code multi-state data model, collecting and arranging real scene three-dimensional data, the one-code multi-state data model is designed by comprehensively analyzing the attribute, form, and time characteristics of the basic geographic entity.

[0051] Among them, the one-code multi-state data model design is the core of subsequent data management and application, and its design is as follows:

[0052] The basic geographic entity is the core concept of the real scene three-dimensional product system, which is the positioning framework and carrier of other geographic entities and related information, and its state can be divided into form and time; from the form, the basic geographic entity has two-dimensional and three-dimensional forms, the two-dimensional form includes vector form, digital orthophoto form, etc., and the three-dimensional form includes white model form, oblique photography monomerization model form, three-dimensional fine model form, etc.; from the time, the same basic geographic entity has different attributes, geometric forms, and entity relationships at different time points.

[0053] Based on the above analysis, the one-code multi-state data model designed by the present application is as shown in Figure 2 , which describes the three types of information including attribute, form, and time that the basic geographic entity needs to contain, and the three types of information are associated with the basic geographic entity through entity coding. When it is necessary to comprehensively display or manage a specific entity, the attribute and related data of each form and time of the basic geographic entity can be found through the entity coding of the basic geographic entity, so as to realize the unified storage, management, and display of the related data.

[0054] S2: Preprocessing the real scene three-dimensional data, the real scene three-dimensional data including vector, three-dimensional model, digital orthographic image, oblique photography, the preprocessing operation including format conversion, coordinate conversion, map edge joint and quality control.

[0055] The process of preprocessing the real scene three-dimensional data includes the following steps:

[0056] In the case of ensuring lossless information conversion, different formats of real scene three-dimensional data are converted into a unified data exchange format.The unified format of the real scene three-dimensional data set by the application is shown in Table 1:

[0057] Table 1: Format table of real scene three-dimensional data

[0058]

[0059] The real scene three-dimensional data in different coordinate systems is converted to the 2000 national geodetic coordinate system.

[0060] The map edge joint processing is performed on the data in the form of map, and the incomplete line and surface data at the map boundary are connected and merged to ensure the integrity of the data.

[0061] The spatial and temporal reference correctness and attribute integrity of the final result data are checked.The main contents of the check include: ensuring that the collected various real scene three-dimensional data meets the relevant specifications of the source data;ensuring that the formats of various real scene three-dimensional data are unified according to the format table;ensuring the completeness and accuracy of the elements at the map edge joint;ensuring that the attribute data of the basic geographic entity meets the requirements of the national "Basic Geographic Entity Semantic Basic Regulations".

[0062] S3: According to the entity classification, spatial position, geometric shape and time information, a unique code is assigned to the basic geographic entity, and the digital orthographic image and oblique photography data are grid divided and coded.

[0063] The coding rules of the vector data and three-dimensional model data are as follows:

[0064] For example Figure 3As shown, vector and 3D model data encoding uses a three-segment entity encoding format: spatial location code + classification code + time code. The spatial location code adopts the BeiDou grid location code, adaptively adjusted based on the characteristics of the basic geographic entities, expanding the grid levels in both 2D and 3D space. The location code comes in two forms: a 26-bit 2D location code and a 44-bit 3D location code. Vector data uses the 2D location code, and 3D model data uses the 3D location code. The 6-bit classification code records the primary and secondary categories of the entity, using the real-scene 3D basic geographic entity classification code as the standard. The 8-bit time code records the current state of the entity, in the format yyyymmdd, where y represents the year, m represents the month, and d represents the day. The encoding results are stored in the attributes of the basic geographic entities.

[0065] The encoding rules for oblique photogrammetry and digital orthophoto data are as follows:

[0066] like Figure 3 As shown, oblique photogrammetry and digital orthophoto data are continuous and do not directly represent individual entities. They only record the spatial location information of the data. The oblique photogrammetry and digital orthophotos of the entity's spatial location can be quickly found by entity coding. Before coding, the two types of data are sliced ​​according to the grid subdivision rules of each level of space, and the 26-bit spatial location code is set as the slice file name.

[0067] S4: Vector and 3D model data are stored in the Yukon database, while digital orthophotos and oblique photogrammetry data are stored locally by year according to a spatial grid.

[0068] Specifically, the two- and three-dimensional data storage method based on the Yukon database is as follows:

[0069] The encoded vector data and 3D model data are uniformly organized and stored in the domestically developed Yukon database. Yukon is a relational database built on top of PostGIS, with added modules such as yukongeomodel and yukongeogridcoder supporting integrated 2D and 3D spatial data storage. It effectively meets the needs for data management, visualization, and analysis with a single code and multiple schemas. In terms of data organization, vector data is stored in tables based on entity classes, with each table using the entity code as the primary key. 3D model data is stored in a single table named after the entity code.

[0070] Specifically, the local data storage method that incorporates spatiotemporal characteristics is as follows:

[0071] The digital orthographic image and the oblique photography data after the slicing are managed in a local storage mode, classified by using a secondary folder for facilitating data indexing; wherein, the source data is classified by a primary folder according to data year, and a secondary folder according to slicing grid accuracy in the same year folder, the secondary folder stores the digital orthographic image and the oblique photography slicing data of the same year and the same accuracy, and the structure is as shown in Figure 4 .

[0072] S5: indexing by encoding, and updating all data related to the same entity or the same grid.

[0073] As shown in Figure 5 , the real scene three-dimensional updating mode includes the following two modes, and specifically includes:

[0074] Updating by entity: updating the vector data and the three-dimensional model data by taking the basic geographic entity as a unit. First, select the entity to be updated, search the data in the Yukon database through the entity encoding, query the vector data with the primary key meeting the condition and the three-dimensional model data with the table name meeting the condition, and uniformly replace the data.

[0075] Updating by grid: updating the digital orthographic image and the oblique photography data by taking the spatial grid as a unit. First, select a specific grid of a certain time point and a certain level to be updated, find the folder where the slicing data to be updated is located through the time primary folder and the level secondary folder, and find the file to be updated through the matching of the grid to be updated and the slicing file name to update the data.

[0076] Generally, data updating often involves real scene three-dimensional data of different formats or structures, so data processing and format conversion are needed to make the data correctly recognized and replaced. In order to improve the efficiency and accuracy of data updating, batch processing technology and multi-thread parallel processing technology can be used to improve the efficiency and effect of data processing while ensuring data consistency.

[0077] S6: based on the constructed real scene three-dimensional data management system, automatically associating indexing, processing and display by encoding, realizing all-round expression of entity multi-form and multi-time.

[0078] As shown in Figure 6 , the method of data indexing and visualization, specifically includes:

[0079] In the system, a specific entity is selected by querying or map selection, and the entity code is obtained for data indexing;

[0080] All morphological and temporal associated data, including vector data, 3D model data, DOM data and oblique photography data, are indexed in Yukon database and local storage folder. The index logic is: vector data is queried by matching primary key and entity code; 3D model data is queried by matching table name and entity code; DOM and oblique photography data are first filtered according to time and level, and then queried by matching file name and spatial location code in entity code.

[0081] The acquired data is processed to form various morphologies of the entity: the vector data is stretched according to the entity height field to generate a white model, and the digital orthophoto and oblique photography data are individualized processed by means of the vector data, so as to finally generate the vector morphology, white model morphology, fine model morphology, digital orthophoto morphology and oblique photography morphology of the selected entity.

[0082] Another embodiment of the present application provides a one-code multi-morphology data management system for real scene three-dimensional, which comprises the following modules:

[0083] The resource service module displays the resource structure in the form of a directory, and can display the data hierarchical structure according to user configuration. The resource service directory includes two-dimensional data, thematic data and three-dimensional data resources of different types and different times, and the user can view and browse the data service according to the time dimension and attribute dimension. In addition to displaying resources, the resource service also provides resource retrieval, multi-year data comparison viewing and other operation functions.

[0084] The map browsing module supports two-dimensional and three-dimensional map browsing, setting of layer visualization effect, and provides rich map tools, including administrative district positioning, layer control, two-dimensional and three-dimensional calculation, two-dimensional and three-dimensional split screen, two-dimensional and three-dimensional plotting, clearing, viewing, flying, legend and other functions.

[0085] The entity query module supports users to quickly query the basic geographic entity meeting the conditions by inputting entity code, type and other information, and indexes and displays multiple data types. The user can select to retrieve data in multiple forms such as by attribute, by range, by condition, and also supports fuzzy search.

[0086] The data update module provides two update methods of entity and grid according to different update requirements, automatically finds the data items to be updated in Yukon database and local storage folder through coding association, and completes data replacement.

[0087] The multi-morphology display module displays all morphologies and temporal states of a specific entity. The morphologies are displayed in the form of split screen, including vector morphology, digital orthophoto morphology, oblique photography morphology, white model morphology and three-dimensional model morphology. The temporal state of each morphology is switched by the time node option in the split screen.

[0088] The statistical analysis module supports two-dimensional analysis such as buffer analysis and overlay analysis, and three-dimensional analysis such as viewshed analysis, visibility analysis, profile analysis, skyline analysis, etc. In addition, statistical functions are provided according to types, time, and forms of basic geographic entities to help users better understand the overall situation of the data.

[0089] In the description of the present specification, the description referring to the terms "one embodiment", "an example", "a specific example" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0090] The basic principles, main features and advantages of the present application are shown and described above. It should be understood by those skilled in the art that the present application is not limited by the above embodiments, and the above embodiments and descriptions in the specification are only illustrative of the principles of the present application. Without departing from the spirit and scope of the present application, various changes and improvements can be made to the present application, and these changes and improvements all fall within the scope of the claimed present application.

Claims

1. A method for managing one code multiple state data in a real scene three-dimensional direction, characterized in that, The method comprises the following steps: Based on a preset one-code multi-state data model, real scene three-dimensional data is collected and arranged, the one-code multi-state data model is designed by comprehensively analyzing the attribute, shape and time characteristics of the basic geographic entity; The real scene three-dimensional data is preprocessed, the real scene three-dimensional data comprises vector, three-dimensional model, digital orthographic image and oblique photography, and the preprocessing operation comprises format conversion, coordinate conversion, map edge joining and quality control; According to the entity classification, spatial position, geometric shape and time information, a unique code is assigned to the basic geographic entity, and the digital orthographic image and oblique photography data are grid divided and coded; The vector and three-dimensional model data are stored in a Yukon database, and the digital orthographic image and oblique photography data are locally stored according to the spatial grid and year; Taking the code as an index, all data related to the same entity or the same grid are updated in linkage; Based on the constructed real scene three-dimensional data management system, the index is automatically associated and displayed by coding, so that the entity is expressed in multiple shapes and multiple time states in all directions; The one-code multi-state data model specifically comprises: The basic geographic entity is the core concept of the real scene three-dimensional data, is the positioning framework and bearing basis of other geographic entities and related information, and has two states, i.e. shape and time; from the shape, the basic geographic entity has two shapes, i.e. two-dimensional shape and three-dimensional shape, the two-dimensional shape comprises vector shape and digital orthographic image shape, and the three-dimensional shape comprises white model shape, oblique photography single-body model shape and three-dimensional fine model shape; from the time, the same basic geographic entity has different attributes, geometric shapes and entity relationships at different time points; the one-code multi-state data model associates and organizes the data in different states by taking the basic geographic entity as a management unit and by using unified coding, and supports finding all related data of the entity in different states by using the coding, realizes integrated storage, management and display of various data; The real scene three-dimensional data coding method specifically comprises: Vector and three-dimensional model data coding: the vector and three-dimensional model data coding uses a three-part entity coding format, specifically: spatial position code+classification code+time code; wherein the spatial position code adopts Beidou grid position code, and is adaptively adjusted according to the characteristics of the basic geographic entity, expands the grid level of two-dimensional and three-dimensional space, and the position code comprises 26-bit two-dimensional position code and 44-bit three-dimensional position code, the vector data uses the two-dimensional position code, and the three-dimensional model data uses the three-dimensional position code; the 6-bit classification code is used for recording the first class and the second class of the entity classification, and the real scene three-dimensional basic geographic entity classification code is used as the standard; the 8-bit time code is used for recording the time information of the current state of the entity, and the format is yyyymmdd, wherein y represents year, m represents month, and d represents day; the coding result is stored in the attribute of the basic geographic entity; Oblique photography and digital orthophoto data encoding: Oblique photography and digital orthophoto data have continuity and do not directly express monomerized entities, only record spatial position information of data, and the oblique photography and digital orthophoto of the spatial position of the entity are quickly found by entity coding; before coding, the two types of data are sliced according to the grid division rules of each hierarchical space, and the 26-bit spatial position code is set as the slice file name.

2. The method according to claim 1, wherein, The real scene three-dimensional data preprocessing, the specific steps include: In the case of lossless information conversion, convert different formats of real scene three-dimensional data into a unified data exchange format; Convert real scene three-dimensional data in different coordinate systems to the 2000 national geodetic coordinate system; The data in the form of division is processed by map edge connection, and the incomplete line, surface and body data at the map boundary are connected and merged to ensure the integrity of the data; Check the correctness of the space-time reference and the integrity of the attributes of the final result data.

3. The method of claim 1, wherein the method is a method of managing a real scene-oriented three-dimensional one code multi-state data, characterized in that, The vector and three-dimensional model data are stored in the Yukon database, specifically including: The coded vector data and three-dimensional model data are uniformly organized and stored in the Yukon database; in terms of data organization design, the vector data is stored according to the entity class, and each table takes the entity code as the primary key; the three-dimensional model data is stored in a single table, and the table name is the entity code.

4. The method of claim 1, wherein the method is a method of managing a real scene-oriented three-dimensional one code multi-state data, characterized in that, The digital orthophoto and oblique photography data are locally stored according to the spatial grid and year, specifically including: The digital orthophoto and oblique photography data after slicing are organized and managed using local storage, and are classified using two-level folders for easy data indexing; among them, the source data is divided into one-level folders according to the data year, and the two-level folders are divided according to the slicing grid accuracy in the same year folder, and the two-level folders store the digital orthophoto and oblique photography slice data of the same year and accuracy.

5. The method of claim 1, wherein the method is a one code multi-state data management method for a real scene oriented three dimensions, and Using the code as an index, all data related to the same entity or the same grid are updated, specifically including: Entity update: update the vector data and three-dimensional model data in units of basic geographic entities; select the entity to be updated, search the Yukon database through the entity code, query the vector data with the primary key meeting the conditions and the three-dimensional model data with the table name meeting the conditions, and uniformly replace the data; Grid update: update the digital orthophoto and oblique photography data in units of spatial grids; select a specific grid at a certain time point and level, find the folder where the slice data to be updated is located through the time one-level folder and the level two-level folder, and find the file to be updated through the matching of the grid to be updated and the slice file name to update the data.

6. The method of claim 1, wherein the method is a one code multi-state data management method for a real scene oriented three dimensions, and Through coding, automatic association index, processing and display, realize the full range expression of entity multi-form and multi-time, specifically including: Selecting a specific entity by query or selection, obtaining the entity code; indexing all morphological and temporal associated data in Yukon database and local storage folder, including vector data, three-dimensional model data, digital orthophoto data and oblique photography data; stretching the vector data according to the entity height field to generate a white model, and using the vector data to individualize the digital orthophoto data and oblique photography data, finally generating the vector morphology, white model morphology, fine model morphology, digital orthophoto morphology and oblique photography morphology of the selected entity.

7. A system for performing the real scene oriented three-dimensional one code multi-state data management method of claim 1, characterized in that, The system comprises the following modules: A resource service module for supporting resource self-defined configuration, organizing a directory tree according to the classification, morphology and time state of entities, and providing a data management and browsing system more in line with real three-dimensional applications; A map browsing module for supporting two-dimensional and three-dimensional map browsing, setting layer visualization effects, and providing map tools to realize calculation, flight and plotting functions; An entity query module for providing entity retrieval in multiple ways according to code, name and spatial position, and supporting fuzzy search; A data update module for providing entity-based and grid-based update methods according to different update requirements, automatically finding data items to be updated through code association, and completing data replacement; A multi-state display module for displaying all morphologies and time states of a specific entity based on one code association, displaying each morphology using a split screen, and providing time node options in each morphology split screen to realize time state switching; A statistical analysis module for supporting two-dimensional and three-dimensional spatial analysis, and providing statistical functions of basic geographic entities according to type, time and morphology.

Images