One-code polymorphic geographic entity data processing method and device

Abstract

The invention discloses a one-code multi-state geographic entity data processing method which comprises the steps that a geographic entity data set is generated, each geographic entity comprises an identifier of the geographic entity and any multiple components, and the components are increased or decreased at will; each component independently comprises at least one expression data set; a geographic entity containing associated components is edited to change component data therein by operating at least one method on a system that acts on one or more of the components. The problems that in the prior art, a geographic information system database and an application program are separated from polymorphic data of a geographic entity, and editing and application of the geographic entity are inconvenient are solved. The invention further comprises a processing device. According to the method, a data structure taking a geographic entity as the center in the prior art is changed into a data structure taking attributes (components) as the center by referring to the ECS thought, so that the complexity of geographic entity data management is reduced, and parallel optimization processing of large-scale attribute data is facilitated.

Description

Technical Field

[0001] The present application relates to the field of geographic information system database, and in particular to a one-code polymorphic geographic entity data processing method and device. 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. If 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 changes in the relationship between data, data associations need 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 game software. It is built on the rendering engine and physics engine, and its purpose is to handle the update operation of game objects. ECS includes entities, components and systems. In order to adapt to the complexity of management, components are simple data combinations without any methods to operate data; systems are simple method combinations, which are calculated based on the object component combination or used to update the status of specific components; several systems are driven by the external framework of the game. Compared with traditional OOP, ECS is much more complicated in writing. The data that can be concentrated in an object can be managed by multiple components, and an additional system is required to handle the logic. The ECS design concept is mostly used in games, and has not been used for new surveying and mapping geographic entities.

[0004] At present, new basic surveying and mapping requires flexible data organization methods. For the same geographic entity, multiple surveying and mapping data are required, as well as aggregated geographic entity data formed to achieve unified functions or management purposes. The expression of geographic entities requires polymorphic data, such as common two-dimensional maps at various scales and changing engineering maps; in some applications, it is necessary to display three-dimensional geographic entities, such as inclined monomers or point cloud monomers, to show the details in the vertical direction. A large amount of attribute data is often involved in geographic entities. However, in the existing GIS database and application, the data expression of geographic entities and polymorphic data are separated. For example, creating a three-dimensional map data can contain the three-dimensional expression of all geographic entities, but the three-dimensional map data is independently generated and has nothing to do with the generation and storage of geographic elements in the GIS database. The connection between the geographic elements is established only through the location information of each sample point in the three-dimensional map data. In addition, any of the polymorphic data is edited independently and uses a specific application, which is not convenient for the use of the GIS database. Summary of the invention

[0005] This application proposes a one-code polymorphic geographic entity data processing method and device to solve the problem that the existing geographic information system database and application are separated from polymorphic data processing, which makes it inconvenient to edit and apply geographic entities. In particular, the solution of this application draws on the ECS concept to design the geographic information system data and application structure, changing the entity-centric data structure to an attribute-centric data structure, reducing the complexity of geographic entity data management, and facilitating large-scale parallel optimization processing of attribute data.

[0006] On the one hand, the embodiment of the present application proposes a one-code polymorphic geographic entity data processing method, comprising the following steps: Generate geographic entity datasets, each geographic entity contains any number of components; add or reduce components arbitrarily; Each component independently contains at least one expression dataset; By executing at least one method on the system acting on one or more of the components, a geographic entity including an associated component pointer is edited to change component data therein.

[0007] In a second aspect, the present application further proposes a one-code polymorphic geographic entity data processing device, which is used to implement the method described in the first aspect of the present application, comprising: NoSQ non-relational database, used to store data of the geographic entities and components; a system processor for executing at least one method in the system; A graphical display is provided for displaying at least a portion of the data in at least a portion of the components of at least one geographic entity.

[0008] 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.

[0009] In the method or device of the present application, preferably, 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; The geographic entity production system is used to add a geographic entity. Further, the geographic entity production system is also used to generate an aggregated first geographic entity using one or more second geographic entities as components.

[0010] 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.

[0011] In the method or device 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.

[0012] In the method or apparatus of the present application, preferably, a custom system is created to collect at least a portion of data in at least one selected component to form a custom data set. Further, 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.

[0013] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: The existing object-oriented data of geographic entities, graphics, attributes, etc., after being combined with ECS, have the characteristics of "one code with multiple forms".

[0014] Since the ECS architecture is data-oriented, the attributes of entities can be added, modified, and deleted independently during the operation of the application system. Therefore, without changing the code and database structure, the corresponding polymorphic data can be added, modified, and deleted for the same geographic data, and multiple geographic entity data can be aggregated.

[0015] In addition, the use of NoSQL non-relational file storage database in the ECS architecture makes it easy to expand various components, so that the collection of various attributes of geographic entities is expressed in the form of files, which makes it easier to expand the attributes of geographic entities in the database. Therefore, the ECS architecture + NoSQ non-relational data can achieve polymorphic representation of a geographic entity without changing the system code or database.

[0016] In the event of changes to the building or environment, reasonable planning can be done without changing any codes.

[0017] This application adopts the principle of "combination is better than inheritance". It eliminates the problems of complex inheritance chains and intertwined functions in the inheritance model. Through decoupling, encapsulation and modular redesign, it can be combined and expanded more flexibly to meet the various complex and changing needs of new surveying and mapping. It reduces the complexity of geographic entity data management and facilitates large-scale parallel optimization processing of polymorphic data. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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: Figure 1 This is a flow chart of an embodiment of a method for processing geographic entity data with one code and multiple states according to the present application; Figure 2 This is a structural diagram of an embodiment of a one-code polymorphic geographic entity data processing device of the present application; Figure 3 A flowchart of an embodiment of an application method of the application method and device; Figure 4 This is a schematic diagram of the data processing system architecture for this application; Figure 5 A schematic diagram of an embodiment of entities, components and system relationships of the application system of the present application; Figure 6 A schematic diagram of the effect of realizing multi-state display of geographic entities using one code using the method and apparatus of the present application. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0020] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0021] Figure 1 This is a flow chart of an embodiment of the one-code polymorphic geographic entity data processing method of the present application.

[0022] On the one hand, the embodiment of the present application proposes a one-code polymorphic geographic entity data processing method, comprising the following steps: Step 110: define component data sets, each component independently containing at least one expression data set.

[0023] 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.

[0024] In one embodiment of the present application, the scope of each component corresponds to one or a group of geographic entities. The expression data set of 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 data set of a house is defined within the geographic scope of the land feature of the house.

[0025] For example, the tilt model data within a geographical range is constructed by a large number of triangulated networks. 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 are reconstructed.

[0026] For another example, point cloud data within a geographic range includes a large number of point array 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.

[0027] 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 data set is not limited to the geographic scope of one or a group of geographic entities, but is larger than the geographic entity, so that any one or a combination of geographic entities is included in the expression data set scope of the component.

[0028] 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.

[0029] 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.

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

[0031] 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.

[0032] Step 120: Define a geographic entity dataset. Each geographic entity contains any number of components. Components can be increased or decreased at will.

[0033] 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.

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

[0035] The identification of the geographic entity may be, for example, a user-defined code, or, for another example, a code used to identify a geographic feature in a geographic information system database, or a code used to identify a combination of multiple geographic features.

[0036] It should be noted that the components of a geographic entity are not limited to the geographic scope of the geographic entity. For example, a three-dimensional dataset corresponding to the geographic scope of geographic entity A is defined as component D of geographic entity B as an expression dataset.

[0037] 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.

[0038] Step 130: Run at least one method through the system acting on one or more of the components to perform data processing on the component dataset or the geographic entity dataset.

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

[0040] The system acts on the components, and it can also be that the expression data set of one or more of the 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.

[0041] 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.

[0042] In data processing, the arbitrary addition or reduction of components can be achieved by changing the component pointer therein, for example, it can include: adding, reducing or modifying the component pointer. The changing of the component data therein can include: adding, reducing or modifying the content of the expression data set in the associated component.

[0043] It should be noted that when editing a geographic entity, the component of the geographic entity can be another geographic entity, for example, a first geographic entity includes a pointer to a second geographic entity, and the second geographic entity is used as a component of the first geographic entity. Furthermore, multiple second geographic entities can be used as components and aggregated into a first geographic entity.

[0044] It should also be noted that the method described in the present application is to run at least one method, where the method refers to a function, algorithm or function that processes a set of data sets as input parameters and returns a result. For example, a method for rendering a three-dimensional image, or a method for extracting a building unit from geographic information graphic data according to a set geographic coordinate range.

[0045] It should be noted that the geographic entity dataset contains the geographic entity identifier and the component object pointer. All components can be obtained by accessing the geographic entity; however, the component does not contain information indicating which entity it belongs to, that is, the component does not know which entity it belongs to. There is no containment relationship between components, and they are all independent; the relationship between entities and components is identified by the system.

[0046] The system can obtain all entities that contain one or more components, and then traverse these entities to obtain other component attributes contained in the entity; for example, search for all entities that have both 2D graphics components and 3D graphics components and modify them. Alternatively, do not access the entity, but directly access the component and change the expression data set in it.

[0047] It should also be noted that, in addition to the above-mentioned system examples, the system of the present application can create a custom system according to the needs of the application, collect at least a part of the data in at least one selected component, and form a custom data set. Furthermore, for the needs of the application, 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.

[0048] 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, and resident population registration data components. Create a new system to calculate the data of the above components to derive a district-based enrollment plan. Furthermore, the system modifies the list of components associated with the new entity or modifies the data of other components associated with the new entity, and updates the building or environmental geographic information to adapt to the new enrollment plan.

[0049] It can be understood that since the geographic entities in the prior art contain attributes, that is, entities are containers containing attributes. The solution of this application abandons the inheritance architecture and adopts the ECS component architecture, eliminating the problems of complex inheritance chains and intertwined functions in the inheritance mode. Through decoupling, encapsulation and modular redesign, it can be combined and expanded more flexibly to meet the various complex and changing needs of new surveying and mapping.

[0050] In this application, when a component is 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 geographic entity-centric data structure of the prior art is changed to an attribute-centric data structure.

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

[0052] In a second aspect, the present application further proposes a one-code polymorphic geographic entity data processing device, which is used to implement the one-code polymorphic geographic entity data processing method described in any embodiment of the first aspect of the present application, comprising: 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. Figure 3~4 For more components of the embodiment of the present application, see Figure 5 .

[0053] The system processor 22 is used for the system to run at least one method to perform data processing on the component data set or the geographic entity data set. The data processing includes: editing a geographic entity containing an associated component pointer to change the component pointer therein, and / or editing at least one associated component to change the data therein. For more system embodiments of the present application, see Figure 5 .

[0054] The graphic display 23 is used to display at least a part of the data in at least a part of the components of at least one geographic entity. The result of the device of the present application processing the data of the geographic entity and the component in response to the instruction of the user interface is displayed through the graphic display. For example, in response to the instruction of the user interface, at least a part of the data in at least one selected component is collected to form a custom data set (such as the enrollment plan in the previous example). Furthermore, for the needs of the application, in response to the instruction of the user interface, the selected geographic entity containing the selected component (such as 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.

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

[0056] Step 310: Use the ECS architecture as the application system and the NoSQ non-relational database as the database to build a system framework.

[0057] A geographic entity component system is established, in which geographic entity data is the entity of the ECS architecture, polymorphic data is the component, and the system is responsible for adding, modifying and aggregating various geographic entities.

[0058] 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.

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

[0060] 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 expression, DOM, and white model can be used.

[0061] It should be noted that: Component association: Generate data of 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 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 component C as the entity and 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.

[0062] Entity independence: Each entity can have associated components or no associated components, or different associated components, increase or decrease components; Component extension: For each entity, components can be customized as needed.

[0063] Step 330: for multiple geographic entities, determine whether it is necessary to aggregate geographic entity data, and aggregate the geographic entity data according to the determination result.

[0064] When multiple geographic entities are aggregated into a new geographic entity, a new geographic entity is generated, such as a first geographic entity, which includes pointers to multiple second geographic entities. Such a geographic entity becomes a component of another geographic entity.

[0065] 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.

[0066] 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 contains the same information of children attending school in the school).

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

[0068] 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.

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

[0070] 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. Components only contain data, and the components themselves have no way to change the data. The component data 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 single 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 through this collection, entities that have all the components in the collection are captured. 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 .

[0071] Combination Figures 1 to 5 In the embodiment shown, in step 130, further steps are included: Step 130A: The system runs and obtains component data, which is as described in step 110 .

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

[0073] Step 130C: The system runs a data processing method to edit component data, or the system runs an entity aggregation method to set the relationship between entities and components, including associating one or more components with entities (such as step 320), or associating one or more entities as components with other entities (such as 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.

[0074] 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.

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

[0076] In one embodiment, polymorphic components of specific geographic entities are dynamically displayed to generate application scenarios 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.

[0077] In one embodiment, further, the combination of geographic entities is displayed. It should be noted that the components associated with the aggregated multiple geographic entities are merged into the same component, which does not necessarily mean merging the component data. It can be to increase the association relationship between the aggregated entity and the component, and / or eliminate the association relationship between the component and the selected geographic entity.

[0078] In one embodiment, further, dynamic business applications are performed on geographic entities or combinations of geographic entities. For example, an expression data set that also includes an interface for triggering executable local applications (such as graphics, images, and information processing tools) or Internet applications (such as accessing social software, shopping software, etc.) is used as a component to trigger communication and information processing functions related to addresses (physical addresses or device addresses) within the scope of the geographic entity.

[0079] The NoSQ non-relational database 21 stores geographic entities using polymorphic data. For a geographic information system, important functions involve: adding and modifying surveying and mapping data in a single geographic entity, and aggregating multiple geographic entities to generate a new entity. For example, in the device of the present application, multiple systems can be combined, such as including a geographic entity production system 51, and the geographic entity production system further includes a surveying and mapping data editing module 42 and a geographic entity aggregation module 43. The data editing module is used to realize adding or modifying surveying and 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 one geographic entity.

[0080] 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 identifier and pointer defined by the component, avoiding overly complex subclass relationships in the inheritance class.

[0081] Figure 5 This is a schematic diagram of an embodiment of the entities, components and system relationships of the application system of the present application. The figure shows a geographic entity A, B, C... and associated components; specific examples of geographic entities and specific examples of associated components are given, and the functions and effects generated when the system is executed are explained.

[0082] Each geographic entity may be associated with one or more components, such as a two-dimensional vector (two-dimensional map) component, a three-dimensional 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 one or more fixed components, such as a three-dimensional rendering system 52, which only processes data with a three-dimensional model component and entities with a three-dimensional model component. As shown by the arrow lines in the figure, the associated three-dimensional components include a three-dimensional model component, a tilted monomer component, a point cloud monomer component, a DEM monomer component, and a DOM monomer component; a two-dimensional graphics system 53, which processes entities with two-dimensional vector components, Figure 5 In the embodiment, the two-dimensional graphics system is associated with the two-dimensional 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 realization of the system's integrated polymorphism and high scalability, and avoids complex class inheritance relationships.

[0083] Figure 6 A schematic diagram of the effect of realizing multi-state display of geographic entities using the method and device 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.

[0084] 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).

[0085] The upper right corner is a switch for integrated polymorphic data. For example, if you select a 2D vector, 3D white model, tilted monomer, or artificial model component, the 2D graphics system and 3D graphics system associated with these components will run, 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 search for aggregated geographic entities with these geographic entities as components.

[0086] In the technical solution of the present 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 includes, for example, a three-dimensional map and a two-dimensional map. The three-dimensional map has graphics of house 1 and house 2; the two-dimensional map also has 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 the geographic spatial location component of house 1, obtains the geographic range information, and then reads the three-dimensional map component and the two-dimensional map component data and displays them.

[0087] An entity contains an entity identifier and can also have a composite relationship component, which further contains a component identifier or pointer. In other words, a geographic entity dataset contains an entity identifier and a component identifier, and the component identifier can be a pointer to the component. In this way, the attribute value is not included in the data cluster of an entity as traditionally, but exists separately in a professional data component. For example, if you want to display a house, the house entity only has an entity identifier and a component identifier, and no geographic information data.

[0088] In this way, when the system calls a component, it can trace back to any entity related to this component. Furthermore, the system queries data from other components of the entity. For example, there is a spatial location component; for example, in the spatial coordinate component, the spatial coordinate data of all entities are included. In this way, the geographic information system data under the ECS architecture is easier to assemble and split.

[0089] From the code implementation point of view, the geographic entity itself is actually represented by an ID, which is associated with the component through the system. No matter which entity it belongs to, when the data of the same component is stored together, unified data management, editing and further optimization can be achieved to improve operation efficiency.

[0090] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. 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 disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] Therefore, the present application also proposes a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method described in any embodiment of the present application is implemented.

[0092] 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 flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, 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 flowchart and / or block diagram. 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.

[0093] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate 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 A function specified in one or more boxes.

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

[0095] 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.

[0096] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory. The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium. Computer-readable media include permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, modules of programs, or other data.

[0097] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

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

[0099] The above is only 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 modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for processing one-code polymorphic geographic entity data, characterized in that: include: Generate geographic entity datasets, each of which contains any number of components; Add or reduce components at will; Each component independently contains at least one expression dataset; By executing at least one method on the system acting on one or more of the components, a geographic entity including associated components is edited to change component data therein.

2. The one-code-multi-state geographic entity data processing method according to 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 one-code-multi-state geographic entity data processing method according to claim 1, characterized in that: 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 one-code polymorphic geographic entity data processing method as claimed in claim 1, characterized in that: The changing of the component data includes increasing, decreasing or modifying the content of the expression data set in the associated component.

5. The one-code-multi-state geographic entity data processing method as claimed in claim 1, characterized in that: 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 one-code-multi-state geographic entity data processing method according to 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 one-code-multi-state geographic entity data processing method according to claim 1, characterized in that: 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 one-code-multi-state geographic entity data processing method 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 described in 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 in the system; A graphical display is provided for displaying at least a portion of the data in at least a portion of the 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 one-code polymorphic geographic entity data processing method as described in any one of claims 1-8 is implemented.

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

Images