A method and device for processing one-code multi-state geographic entity data

Abstract

The present application discloses a method for processing one-code polymorphic geographic entity data, comprising: generating a geographic entity data set, wherein each geographic entity includes an identifier of the geographic entity and any number of components, and components can be arbitrarily added or subtracted; each component independently includes at least one expression data set; and editing the geographic entity containing associated components to change the component data therein by running at least one method through a system acting on one or more of the components. The present application solves the problem of the prior art that the geographic information system database and application are separated from the polymorphic data of geographic entities, and that the editing and application of geographic entities are inconvenient. The present application also includes a processing device. Drawing on the ECS concept, the present application changes the prior art data structure centered on geographic entities into a data structure centered on attributes (components), thereby reducing the complexity of geographic entity data management and facilitating large-scale parallel optimization processing of attribute data.

Description

Technical Field

[0001] The present application relates to the field of geographic information system databases, and in particular to a method and device for processing one-code polymorphic geographic entity data. Background Art

[0002] The relationship between new surveying and mapping geographic entities is inconvenient to express, it is difficult to save attribute information for combined entities, and polymorphic data is unrelated. The reason is that most current application systems use an object-oriented approach, and the system architecture is based on class inheritance and calling. When the parent class attributes and the number and attributes of its subclasses cannot be determined in advance, if the parent class and subclass need to be modified after the system is running, the class attributes and the relationship between classes need to be modified again. In addition, in terms of data storage, relational databases are generally used to store data. For newly added attributes and when the relationship between data changes, the data association needs to be redefined. Therefore, based on object-oriented architecture and relational databases, when the relationship between objects and object attributes change, the system architecture also needs to be changed accordingly, which lacks flexibility.

[0003] ECS is a framework concept for gaming software. It is built on top of the rendering engine and physics engine, and its purpose is to handle updates to game objects. ECS consists of entities, components, and systems. To accommodate management complexity, components are simply combinations of data without any methods for manipulating data; systems are simply combinations of methods that perform calculations based on the object-component combination or are used to update the status of specific components; and several systems are driven by external game frameworks. Compared to traditional OOP, ECS is much more complex to write. An object can use multiple components to manage centralized data, and additional systems are required to handle logic. The ECS design concept is mostly used in games, but has not been applied to new types of surveying and mapping geographic entities.

[0004] Currently, new basic surveying and mapping technologies require flexible data organization. Multiple types of surveying and mapping data are needed for the same geographic entity, as well as aggregated geographic entity data to achieve unified functionality or management objectives. Representing geographic entities requires polymorphic data, such as common two-dimensional maps at various scales and varying engineering maps. In some applications, three-dimensional geographic entities, such as oblique entities or point clouds, are required to display vertical details. Geographic entities often involve a large amount of attribute data. However, in existing GIS databases and applications, the data representation of geographic entities and polymorphic data are separated. For example, creating a three-dimensional map data set can contain a three-dimensional representation of all geographic entities, but this 3D map data is generated independently and is unrelated to the generation and storage of geographic elements in the GIS database. It is only connected to the geographic elements through the location information of each point within the 3D map data. Furthermore, each polymorphic data set must be edited independently using a specific application, making it inconvenient to use the GIS database. Summary of the Invention

[0005] This application proposes a method and apparatus for processing polymorphic geographic entity data using a single code. This method addresses the existing problem of geographic information system (GIS) databases and applications being separated from polymorphic data processing, which inconveniently handles editing and application of geographic entities. Specifically, this application's solution draws on ECS principles to design GIS data and application structures, transforming entity-centric data structures into attribute-centric ones. This reduces the complexity of geographic entity data management and facilitates the parallel optimization of large-scale attribute data processing.

[0006] On the one hand, the embodiment of the present application proposes a method for processing one-code polymorphic geographic entity data, comprising the following steps:

[0007] Generate geographic entity datasets, each geographic entity contains any number of components; arbitrarily increase or decrease components;

[0008] Each component independently contains at least one expression dataset;

[0009] The geographic entity including the associated component pointer is edited to change the component data therein by executing at least one method on the system acting on one or more of the components.

[0010] In a second aspect, the present application further proposes a one-code multi-state geographic entity data processing device for implementing the method described in the first aspect of the present application, comprising:

[0011] NoSQ non-relational database, used to store data of the geographic entities and components;

[0012] a system processor for executing at least one method on the system;

[0013] A graphic display is configured to display at least a portion of data in at least a portion of components of at least one geographic entity.

[0014] In the method or device of the present application, preferably, the at least one expression data set is at least one of the following: two-dimensional vector data, attribute data, three-dimensional model data, tilt model data, point cloud data, DEM data, DOM data, TIM data.

[0015] In the method or device of the present application, preferably, the system comprises at least one of the following:

[0016] 2D graphics system, used to change 2D vector data;

[0017] A three-dimensional graphics system for changing three-dimensional graphics data;

[0018] a display system for displaying at least a portion of data in at least a portion of components in at least one geographic entity;

[0019] The geographic entity production system is used to add geographic entities. Furthermore, the geographic entity production system is also used to generate an aggregated first geographic entity using one or more second geographic entities as components.

[0020] In the method or device of the present application, preferably, the arbitrary addition or reduction of components includes adding, reducing or modifying the pointer of the component; the changing of the component data therein includes adding, reducing or modifying the content of the expression data set in the associated component.

[0021] In the method or apparatus of the present application, preferably, the first geographic entity includes a pointer to the second geographic entity, and the second geographic entity is used as a component of the first geographic entity. Alternatively, multiple second geographic entities are respectively used as components and aggregated into one first geographic entity.

[0022] In the method or apparatus of the present application, preferably, a customized system is created to collect at least a portion of the data in at least one selected component to form a customized dataset. Furthermore, the selected geographic entity containing the selected component is edited, and / or the data in any component of the selected geographic entity containing the selected component is edited.

[0023] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0024] The existing object-oriented data of geographic entities, graphics, attributes, etc., when combined with ECS, has the characteristic of "one code, multiple states".

[0025] Because the ECS architecture is data-oriented, entity attributes can be independently added, modified, and deleted while the application system is running. Therefore, without changing the code or database structure, corresponding polymorphic data can be added, modified, and deleted for the same geographic data, and multiple geographic entity data can be aggregated.

[0026] Furthermore, the use of a NoSQL non-relational file storage database within the ECS architecture facilitates the expansion of various components, allowing the collection of geographic entity attributes to be expressed in a file format, making it easier to expand geographic entity attributes within the database. Therefore, the ECS architecture combined with NoSQL non-relational data allows for polymorphic representation of a geographic entity without changing the system code or database.

[0027] As buildings or environments change, proper planning can be done without having to amend any codes.

[0028] This application solution adopts the principle of "composition is better than inheritance." It eliminates the complex inheritance chains and intertwined functions inherent in the inheritance model. Through decoupling, encapsulation, and modular redesign, it allows for more flexible combination and expansion, meeting the diverse and complex needs of new surveying and mapping applications. It reduces the complexity of geographic entity data management and facilitates the parallel optimization of large-scale polymorphic data. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0030] Figure 1 This is a flow chart of an embodiment of the method for processing geographic entity data with a single code and multiple states according to the present application;

[0031] Figure 2 This is a structural diagram of an embodiment of a one-code polymorphic geographic entity data processing device of the present application;

[0032] Figure 3 A flowchart of an embodiment of an application method of the application method and apparatus;

[0033] Figure 4 This is a schematic diagram of the data processing system architecture for this application;

[0034] Figure 5 A schematic diagram of an embodiment of the entities, components, and system relationships of the application system of this application;

[0035] Figure 6 This is a schematic diagram of the effect of the method and device of the present application realizing multi-state display of geographic entities with one code. DETAILED DESCRIPTION

[0036] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0037] The following describes in detail the technical solutions provided by various embodiments of the present application in conjunction with the accompanying drawings.

[0038] Figure 1 This is a flow chart of an embodiment of the method for processing geographic entity data with one code and multiple states in this application.

[0039] On the one hand, the embodiment of the present application proposes a method for processing one-code polymorphic geographic entity data, comprising the following steps:

[0040] Step 110: Define component data sets, where each component independently contains at least one expression data set.

[0041] The expression data set is at least one of the following: two-dimensional vector data, attribute data, three-dimensional model data, tilt model data, point cloud data, DEM data, DOM data, and TIM data.

[0042] In one embodiment of the present application, the scope of each component corresponds to one or a group of geographic entities. The expression dataset for the one or a group of geographic entities is defined within the geographic scope of the one or a group of geographic entities. For example, the expression dataset for a house is defined within the geographic scope of the land feature of the house.

[0043] For example, the tilt model data within a geographical range is constructed by a large number of triangulated meshes. Taking the spatial range of a specific geographical entity as the boundary, boundary lines are introduced into the corresponding tilt model data, and the triangulated mesh data adjacent to the boundary lines is reconstructed.

[0044] For another example, point cloud data within a geographic range includes a large number of point matrix data sets, and the point cloud data is divided into multiple parts based on the spatial range of a specific geographic entity as a boundary.

[0045] In another embodiment of the present application, the scope of each component is larger than any one or a group of geographic entities. The expression dataset is not limited to the geographic scope of one or a group of geographic entities, but is larger than the geographic entities, so that any geographic entity or combination of geographic entities is included in the scope of the component's expression dataset.

[0046] Similarly, the scope of the components of the present application may also be smaller than any one or a group of geographic entities, or may be unrelated to the geographic scope of the geographic entities.

[0047] In one embodiment of the present application, the components of the present application are related to non-graphic attributes of a geographic entity, such as a name attribute, property attribute, use attribute, etc. of a geographic entity, and the components include an expression data set related to the non-graphic attributes.

[0048] In one embodiment of the present application, the expression data set may also be other attribute data or other information unrelated to geographic graphics, such as natural and cultural information.

[0049] In some embodiments of the present application, the expression dataset may also include an interface for triggering executable local applications or Internet applications, such as accessing social software, shopping software, etc., to trigger communication and information processing functions related to addresses (physical addresses or device addresses) within the scope of a geographic entity.

[0050] Step 120: Define a geographic entity dataset. Each geographic entity contains any number of components. Components can be added or reduced at will.

[0051] For example, a geographic entity is represented by a set of identification data, which includes the identification of the geographic entity and a pointer to at least one associated component. In an embodiment of the present application, preferably, at least one geographic entity includes pointers to multiple components.

[0052] In this application, each geographic entity contains any number of components, which do not need to be predefined and can be added later as needed.

[0053] The identifier of the geographic entity may be, for example, a user-defined code, or, for another example, a code in a geographic information system database for identifying a geographic feature, or a code for identifying a combination of multiple geographic features.

[0054] It should be noted that the components of a geographic entity are not limited to the geographic scope of the geographic entity. For example, the 3D dataset within the geographic scope of geographic entity A is defined as component D of geographic entity B as the expression dataset.

[0055] It should also be noted that a component is not limited to one entity, and multiple entities may contain the same component. For example, geographic entity A and geographic entity B contain a common component D.

[0056] Step 130: Run at least one method on the system acting on one or more of the components to process the component dataset or the geographic entity dataset.

[0057] The system may be, for example, a two-dimensional graphics system for modifying two-dimensional vector data; another example may be a three-dimensional graphics system for modifying three-dimensional graphics data; another example may be a display system for displaying at least a portion of data in at least a portion of components of at least one geographic entity; another example may be a geographic entity production system for adding geographic entities. The present application is not limited to having only one system, and each system operates on one or more components. For example, a two-dimensional graphics system and a three-dimensional graphics system may be introduced simultaneously, wherein the two-dimensional graphics system executes a two-dimensional vector data processing method, and the three-dimensional graphics system executes a three-dimensional graphics data processing method; wherein, for example, when the three-dimensional graphics system operates on multiple components, it can process multiple types of three-dimensional graphics data.

[0058] The system acts on components, and it can also be that the expression data set of one or more components drives the method in the system to generate an application scenario with a GUI. In some embodiments, the system implements the function of graphic display or editing.

[0059] The system implements data processing, which includes: editing a geographic entity including associated components to change the number or type of associated components, and / or editing at least one associated component to change component data therein.

[0060] In data processing, the arbitrary addition or subtraction of components can be achieved by changing the component pointers therein, which can include, for example, adding, subtracting, or modifying the component pointers. The changing of the component data therein can include, for example, adding, subtracting, or modifying the content of the expression data set in the associated component.

[0061] It should be noted that when editing a geographic entity, a component of the geographic entity can be another geographic entity. For example, a first geographic entity can contain a pointer to a second geographic entity, with the second geographic entity serving as a component of the first geographic entity. Furthermore, multiple second geographic entities can be aggregated into a single first geographic entity, each serving as a component.

[0062] It should also be noted that the term "running at least one method" in this application refers to a function, algorithm, or functionality that processes a set of data as input parameters and returns a result. For example, a method for rendering a three-dimensional image or a method for extracting individual buildings from geographic information graphics data based on a specified geographic coordinate range may be used.

[0063] It's important to note that a geographic entity dataset contains both the entity identifier and component object pointers. Accessing a geographic entity allows you to retrieve all its components. However, a component doesn't contain any information about which entity it belongs to; in other words, it doesn't know which entity it belongs to. Components don't have a containment relationship; they are all independent. The relationship between entities and components is determined by the system.

[0064] The system can retrieve all entities containing one or more components, then traverse these entities to obtain the attributes of other components contained in the entity; for example, it can search for all entities that have both 2D and 3D graphics components and modify them. Alternatively, it can directly access the components without accessing the entities and change the expression data set within them.

[0065] It should also be noted that, in addition to the aforementioned system examples, the system of this application can create a customized system based on application needs, collect at least a portion of the data from at least one selected component, and form a customized dataset. Furthermore, to meet application needs, the selected geographic entity containing the selected component can be edited, and / or the data in any component of the selected geographic entity containing the selected component can be edited.

[0066] In the event of changes in buildings or the environment, there is no need to modify any code to make reasonable plans. For example: if a new school is built next to a community, a district-based enrollment plan can be made by counting the number of households, the size of the school, the distance between each household and the school, and other attributes. To implement this application, a new entity (new school) is defined, which contains the entity's identifier and associated component pointers. The associated components include: two-dimensional geographic graphics data components, school location distribution data components, resident population registration data components, etc. Create a new system to calculate the data of the above components to derive a district-based enrollment plan. Furthermore, by modifying the list of components associated with the new entity or modifying the data of other components associated with the new entity through the system, the building or environmental geographic information is updated to adapt to the new enrollment plan.

[0067] As can be understood, since geographic entities in existing technologies contain attributes, that is, entities are containers for attributes. This application's solution abandons the inheritance-based architecture and adopts an ECS component-based architecture, eliminating the complex inheritance chains and intertwined functions inherent in the inheritance model. Through decoupling, encapsulation, and modular redesign, it allows for more flexible combination and expansion, meeting the diverse and complex needs of new surveying and mapping applications.

[0068] In this application, when components are used to describe an attribute, each component can be processed independently, and the combination of multiple components is determined by the reference relationship of the entity. The entity itself does not contain the component data, so the existing data structure centered on geographic entities is changed to an attribute-centered data structure.

[0069] Figure 2 This is a structural diagram of an embodiment of a one-code polymorphic geographic entity data processing device of the present application.

[0070] In a second aspect, the present application further provides a one-code polymorphic geographic entity data processing device, configured to implement the one-code polymorphic geographic entity data processing method described in any one embodiment of the first aspect of the present application, comprising:

[0071] The NoSQ non-relational database 21 is used to store the data of the geographic entities and components. In the geographic entity data set, each geographic entity contains the identifier of the geographic entity and a pointer to at least one component, wherein at least one geographic entity contains pointers to multiple components. In the component data set, each component independently contains at least one expression data set. Figures 3 and 4 For more components of the embodiment of the present application, see Figure 5 .

[0072] The system processor 22 is configured to execute at least one method in the system to process the component dataset or the geographic entity dataset. The data processing includes: editing a geographic entity containing associated component pointers to change the component pointers therein, and / or editing at least one associated component to change the data therein. For more information about the system embodiments of the present application, see Figure 5 .

[0073] The graphical display 23 is configured to display at least a portion of the data in at least a portion of the components of at least one geographic entity. The graphical display displays the results of the processing of the geographic entity and component data by the apparatus of the present application in response to instructions from the user interface. For example, in response to instructions from the user interface, at least a portion of the data in at least one selected component is collected to form a custom dataset (e.g., the enrollment plan in the previous example). Furthermore, to meet application needs, in response to instructions from the user interface, the selected geographic entity containing the selected component (e.g., the new school geographic entity in the previous example) is edited, and / or the data in any component of the selected geographic entity containing the selected component is edited.

[0074] Figure 3 The present invention is a flow chart of an embodiment of an application method of the application method and device.

[0075] Step 310: Build a system framework using the ECS architecture as the application system and the NoSQ non-relational database as the database.

[0076] Establish a geographic entity component system, in which geographic entity data is the entity of the ECS architecture and polymorphic data is the component. The system is responsible for adding, modifying and aggregating various geographic entities.

[0077] Step 320: Adding components for the same geographic entity: determining whether it is necessary to add other surveying and mapping data, and performing the data adding operation based on the determination result.

[0078] When adding data to a geographic entity, you only need to add the corresponding component pointer in the geographic entity dataset.

[0079] In step 320, different data representations can be flexibly added and modified for a geographic entity. For example, for the same geographic entity, three-dimensional representation, DOM, and white model can be used.

[0080] It should be noted that:

[0081] Component association: Generate data for two-dimensional graphics, real-life three-dimensional, orthographic images, and various attribute data in the form of "components" and associate them with set entities; "association" in this application refers to establishing a relationship between entities and components. For example, if a data set is associated with an entity, then the data set becomes a component of this entity. In other words, if an entity A is associated with another entity B, then the entity A becomes a component of another entity B. For another example, if an entity B is associated with a component C, it means that a new data relationship is established with the component C as the entity and the entity B as the component. At this time, the entity feature of component C is the specific identification data in component C, in which the pointer of entity B is associated.

[0082] Entity independence: Each entity can have associated components or no associated components, or different associated components, or increase or decrease components;

[0083] Component extension: For each entity, components can be customized as needed.

[0084] Step 330: For multiple geographic entities, determine whether geographic entity data needs to be aggregated, and aggregate the geographic entity data based on the determination result.

[0085] When multiple geographic entities are aggregated into a new geographic entity, a new geographic entity is generated, for example, a first geographic entity containing pointers to multiple second geographic entities. Such a geographic entity becomes a component of another geographic entity.

[0086] In step 330 , multiple geographic entities may be aggregated into one geographic entity. For example, several houses and yards may be aggregated into one community.

[0087] Set the relationship between multiple entities, such as the containment relationship: community-courtyard-house; for example, the application relationship: community-school (the population component in the community includes the same information of children attending the school).

[0088] Step 340: Display geographic entity data in multiple forms for the same geographic entity.

[0089] In step 340 , not only the components in the geographic entity are queried and displayed, but also other geographic entities associated with any geographic entity can be traced back and queried and displayed.

[0090] Figure 4 This is a schematic diagram of the data processing system architecture for this application.

[0091] The ECS architecture 41 includes entities, components and systems. Among them, entities do not contain any data and business logic. Its data structure is simple. There is an ID for a geographic entity, and all components added to the entity are associated with this ID. Therefore, the components and component data can be accessed through the entity. The components only contain data, and the components themselves have no way to change the data. The data of the component describes a certain type of feature of the entity. If you want the component to work, you must load the component onto the entity. A separate component is meaningless. What really contains the business logic is the system. A collection of one or more components that act on the system drives the system, and the entity that has all the components in the collection is captured through the collection. After that, you can operate these entities, delete them, add or delete components on the entity, change the data on the component, etc. For more embodiments of entities, components and systems in this application, see Figure 5 .

[0092] Combine Figures 1 to 5 In the embodiment shown, step 130 further includes the following steps:

[0093] Step 130A: The system runs and obtains component data, which is as described in step 110.

[0094] Step 130B: Determine the entity associated with the component. The system determines the entity associated with each component by searching for the entity's identifier and its key component pointer.

[0095] Step 130C: The system executes a data processing method to edit component data, or executes an entity aggregation method to set relationships between entities and components, including associating one or more components with an entity (as in step 320), or associating one or more entities as components with other entities (as in step 330). In some embodiments, a specific field in any component is designated as an entity, and an associated component is further set for any entity.

[0096] It should be noted that when a component is associated with multiple entities, editing and modifying the component data can facilitate the use of different geographic entities at the same time, that is, there is no need to modify the attributes of each geographic entity separately.

[0097] Step 130D: Display the geographic entity by running the graphic display method through the system.

[0098] In one embodiment, the polymorphic components of a specific geographic entity are dynamically displayed to generate an application picture to support engineering applications. For example, it can be used as a data twin application scenario map. For another example, different polymorphic components can be called on demand. For another example, plan views and three-dimensional views can be displayed periodically in turn.

[0099] In one embodiment, a combination of geographic entities is further displayed. It should be noted that merging components associated with multiple aggregated geographic entities into a single component does not necessarily require merging component data. Instead, the association between the aggregated entity and the component may be increased, and / or the association between the component and the selected geographic entity may be eliminated.

[0100] In one embodiment, dynamic business applications are further implemented for geographic entities or combinations of geographic entities. For example, a component may include an expression dataset that also includes an interface for triggering executable local applications (such as graphics, image, and information processing tools) or internet applications (such as accessing social media or shopping apps) to trigger communication and information processing functions related to addresses (physical or device addresses) within the geographic entity's scope.

[0101] The NoSQ non-relational database 21 stores geographic entities as polymorphic data. Important functions of a geographic information system include adding and modifying mapping data within a single geographic entity and aggregating multiple geographic entities to create a new entity. For example, the apparatus of the present application may combine multiple systems, such as a geographic entity production system 51. The geographic entity production system further includes a mapping data editing module 42 and a geographic entity aggregation module 43. The data editing module is used to add or modify mapping data for the same geographic entity, and the geographic entity aggregation module is used to aggregate multiple geographic entity data to achieve polymorphism and aggregate multiple geographic entities into a single geographic entity.

[0102] The data architecture, data processing method and device of the present application replace the attributes of traditional geographic entities with components. The data is processed by the system. The geographic entity is a data set based on the identifiers and pointers defined by the components, avoiding the overly complex subclass relationship in the inheritance class.

[0103] Figure 5 This is a schematic diagram illustrating an embodiment of the entities, components, and system relationships of the application system of this application. The diagram shows geographic entities A, B, C, and their associated components. It provides specific examples of geographic entities and associated components, and describes the functions and effects produced when the system is executed.

[0104] Each geographic entity can be associated with one or more components, such as a 2D vector (2D map) component, a 3D model component, a basic attribute component, an associated entity component (an entity is a component of another entity), an associated relationship component, etc. Different systems process fixed one or more components, such as the 3D rendering system 52, which only processes data with 3D model components and entities with 3D model components. As shown by the arrow lines in the figure, the associated 3D components include 3D model components, tilted monomer components, point cloud monomer components, DEM monomer components, and DOM monomer components; the 2D graphics system 53 processes entities with 2D vector components. Figure 5 In this embodiment, the 2D graphics system is associated with the 2D vector component, the basic attribute component, and the extended attribute component. The geographic entity production system 51 processes entities with associated entities and entity-linked relationship components. This facilitates the implementation of the system's integrated polymorphism and high scalability, avoiding complex class inheritance relationships.

[0105] Figure 6 A schematic diagram of the effect of realizing multi-state display of geographic entities using the method and apparatus of the present application. A set of geographic entities includes multiple geographic entities, and each geographic entity includes several components. Figure 6 By means of specific examples, the results of the same or different components of various geographic entities are given; as well as the application functions and effects that can be supported by the results of aggregating multiple geographic entities.

[0106] For example, the graphic display of the present application, or as a result of the operation of the geographic entity display system, includes a polymorphic display result of a selected aggregated geographic entity (cell) or a plurality of selected geographic entities (buildings, roads).

[0107] In the upper right corner is the integrated polymorphic data switch. For example, if you select a 2D vector, 3D white model, tilted monomer, or artificial model component, the 2D and 3D graphics systems associated with these components will operate, searching for several geographic entities 61 containing 2D vector components, several geographic entities 62 containing 3D white model components, several geographic entities 63 containing tilted monomer components, and several geographic entities 64 containing artificial model components. When these geographic entities are aggregated into a new geographic entity, further searches will be conducted for aggregated geographic entities containing these geographic entities as components.

[0108] In the technical solution of this application, in a further embodiment, a component in the ECS architecture can belong to multiple entities, such as entity House 1 and entity House 2; the component may include a three-dimensional map and a two-dimensional map. The three-dimensional map contains graphics of House 1 and House 2; the two-dimensional map also contains graphics of House 1 and House 2. Furthermore, each house entity has a spatial location attribute component. When the display system wants to display House 1, it searches for House 1's geospatial location component, obtains its geographic range information, and then reads and displays the data of the three-dimensional map component and the two-dimensional map component.

[0109] An entity contains an entity identifier and can also have composite relationship components, which further contain component identifiers or pointers. Alternatively, a geographic entity dataset contains both entity identifiers and component identifiers, with component identifiers serving as component pointers. This way, attribute values ​​are not contained within a traditional entity data cluster, but rather exist in separate, specialized data components. For example, if you want to display a house, the house entity only contains an entity identifier and component identifiers, but no geographic information.

[0110] This allows the system to retrieve a component and trace it back to any entity associated with it. Furthermore, the system can query data from other components of that entity. For example, a spatial location component contains the spatial coordinate data for all entities. This makes GIS data within the ECS architecture easier to assemble and disassemble.

[0111] From a code implementation perspective, a geographic entity is represented by an ID, which is then linked to a component through the system. Regardless of the entity, storing data from the same component together allows for unified data management, editing, and further optimization, improving operational efficiency.

[0112] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0113] Therefore, the present application also proposes a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of the present application.

[0114] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0115] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0116] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0117] Furthermore, the present application also proposes an electronic device (or computing device), comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in any embodiment of the present application when executing the computer program.

[0118] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory. Memory is an example of a computer-readable medium. Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented using any method or technology for information storage. Information can be computer-readable instructions, data structures, program modules, or other data.

[0119] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0120] It should also be noted that "at least one" and "at least one" in this application include 1 type / individual or multiple types / individual, wherein multiple types / individual includes 2 types / individual or more than 2 types / individual.

[0121] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A method for processing one-code multi-state geographic entity data, characterized in that: include: Geographic entity data is an entity of the ECS architecture, and polymorphic data is a component. The system is responsible for adding, modifying, and aggregating components for each geographic entity. Generate a geographic entity dataset, which contains geographic entity identifiers and component object pointers. The combination of multiple components is determined by the reference relationship of the entities. The entity itself does not contain component data. A component is associated with multiple entities; each component independently contains at least one expression data set; the component does not contain any indication of which entity it belongs to; The geographic entity including the associated components is edited to change the component data therein by executing at least one method on the system acting on one or more of the components.

2. The method for processing geographic entity data with one code and multiple states as claimed in claim 1, characterized in that: The at least one expression dataset is at least one of the following: 2D vector data, attribute data, 3D model data, tilt model data, point cloud data, DEM data, DOM data, TIM data.

3. The method for processing geographic entity data with one code and multiple states as claimed in claim 1, wherein: The system comprises at least one of the following: 2D graphics system, used to change 2D vector data; A three-dimensional graphics system for changing three-dimensional graphics data; a display system for displaying at least a portion of data in at least a portion of components in at least one geographic entity; Geographic entity production system, used to add geographic entities.

4. The method for processing geographic entity data with one code and multiple states as claimed in claim 1, characterized in that: The changing of the component data includes increasing, decreasing or modifying the expression data set content in the associated component.

5. The method for processing geographic entity data with one code and multiple states as claimed in claim 1, wherein: The first geographic entity includes a pointer to the second geographic entity, and the second geographic entity is used as a component of the first geographic entity.

6. The method for processing geographic entity data with one code and multiple states as claimed in claim 1, characterized in that: A plurality of second geographic entities are respectively used as components and aggregated into a first geographic entity.

7. The method for processing geographic entity data with one code and multiple states according to claim 1, wherein: A custom system is created to collect at least a portion of the data from at least one selected component to form a custom data set.

8. The method for processing geographic entity data with one code and multiple states as claimed in claim 7, characterized in that: The selected geographic entity including the selected component is edited, and / or the data in any component of the selected geographic entity including the selected component is edited.

9. A one-code multi-state geographic entity data processing device, used to implement the method according to any one of claims 1 to 8, characterized in that: Include: NoSQ non-relational database, used to store data of the geographic entities and components; a system processor for executing at least one method on the system; A graphic display is configured to display at least a portion of data in at least a portion of components of at least one geographic entity.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for processing one-code polymorphic geographic entity data as described in any one of claims 1 to 8 is implemented.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein: When the processor executes the computer program, the method for processing one-code polymorphic geographic entity data as described in any one of claims 1-8 is implemented.

Images