Geographic information model rendering method and device and nonvolatile storage medium

Abstract

The invention discloses a geographic information model rendering method and device and a nonvolatile storage medium. The method comprises the steps that front-end equipment obtains scene configuration data and scene component data from rear-end equipment, the scene configuration data comprises at least one of scene size information, scene scaling information and a preview of a geographic information model, and the scene component data comprises a to-be-rendered component; determining a data version of the scene component data; under the condition that the version number of the data version is smaller than the version number of the target version, updating the scene component data; and performing dynamic registration processing on the updated scene component data, and after dynamic registration, calling the scene configuration data to render the dynamically registered scene component data to obtain a geographic information model. The technical problem that an old-version geographic information model cannot be rendered due to updating of a low-code platform is solved.

Description

Technical Field

[0001] The present application relates to the field of model rendering, and more specifically, to a geographic information model rendering method, device, and non-volatile storage medium. Background Art

[0002] The City Information Model (CIM) platform, as the cornerstone of building digital twin cities, plays a crucial role. It is a comprehensive platform primarily used for the digital representation and management of a city's three-dimensional space, buildings, and infrastructure, providing robust data support for urban planning, construction, operations, and maintenance. The CIM platform is an indispensable information infrastructure for smart city development, and its fundamental and critical importance is self-evident.

[0003] The City Information Model, combined with the flexible iteration and rapid deployment advantages of a low-code development platform, can rapidly implement classification, hierarchical query, analysis, and visual management of multiple business contents based on geographic information. This provides more comprehensive information assurance and reliable decision-making support for the management, construction, planning, and services of smart cities.

[0004] However, when the low-code development platform is updated, the old version of the city information model often cannot be rendered due to version issues.

[0005] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0006] The embodiments of the present application provide a geographic information model rendering method, device and non-volatile storage medium to at least solve the technical problem that the old version of the geographic information model cannot be rendered due to the update of the low-code platform.

[0007] According to one aspect of an embodiment of the present application, a geographic information model rendering method is provided, including: a front-end device obtains scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered; determining a data version of the scene component data; when the version number of the data version is less than the version number of the target version, updating the scene component data; dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model.

[0008] Optionally, when the version number of the data version is smaller than the version number of the target version, updating the scene component data includes: determining the target version record data, wherein the version number corresponding to the target version record data is greater than the version number of the data version, and the target version record data records the updated fields and the update method corresponding to the updated fields; determining the fields that need to be updated in the scene component data based on the target version record data and updating them.

[0009] Optionally, dynamic registration processing of the updated scene component data includes: determining the component type of the updated scene component data; establishing a component instance corresponding to the updated scene component data based on the component type; determining the class methods lost in the process of establishing the component instance, and supplementing the class methods lost in the process of establishing the component instance.

[0010] Optionally, determining class methods lost in the process of establishing a component instance and supplementing the class methods lost in the process of establishing a component instance includes: determining the original class definition of the component instance, the original class definition recording all class methods of the component type; comparing the class methods in the component instance with the class methods in the original class definition, and determining the class methods lost in the process of establishing the component instance; dynamically supplementing the class methods lost in the process of establishing the component instance to the component instance.

[0011] Optionally, before obtaining the scene configuration data and scene component data from the back-end device, the geographic information model rendering method also includes: obtaining a configuration file and a service application image corresponding to the scene component data from the back-end device, the service application image being an image of the service application that the scene component data depends on; and configuring the service application image according to the configuration file in the target operating environment.

[0012] Optionally, the geographic information model rendering method also includes: determining the release deadline of the geographic information model, and stopping displaying the geographic information model after the release deadline; or, after receiving an access request, determining whether the geographic information model is set with a release password, and if it is determined that a release password is set, performing a password verification on the access request.

[0013] Optionally, the geographic information model rendering method also includes: the front-end device reads a component tree corresponding to the geographic information model pre-configured in the front-end device, and the child nodes of the component tree correspond one-to-one to the components in the geographic information model; after converting the component tree into a string, it is passed to the back-end device.

[0014] Optionally, the geographic information model rendering method further includes: the back-end device determining the service application that the scene component data depends on; and packaging the service application into a mirror file.

[0015] According to another aspect of an embodiment of the present application, a geographic information model rendering device is also provided, which is suitable for use in a front-end device, and includes: a first processing module for obtaining scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered; a second processing module for determining the data version of the scene component data; a third processing module for updating the scene component data when the version number of the data version is less than the version number of the target version; a fourth processing module for dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model.

[0016] According to another aspect of an embodiment of the present application, a geographic information model rendering system is also provided, including a front-end device and a back-end device, wherein: the front-end device is used to obtain scene configuration data and scene component data from the back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered; determining the data version of the scene component data; updating the scene component data when the version number of the data version is less than the version number of the target version; dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model; the back-end device is used to determine the service application on which the scene component data depends; and packaging the service application into a mirror file.

[0017] According to another aspect of an embodiment of the present application, a non-volatile storage medium is provided, in which a program is stored. When the program is running, the device where the non-volatile storage medium is located is controlled to execute the geographic information model rendering method.

[0018] According to another aspect of an embodiment of the present application, an electronic device is provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the geographic information model rendering method is executed when the program is run.

[0019] According to another aspect of an embodiment of the present application, a computer program product is further provided, including a computer program, which implements a geographic information model rendering method when executed by a processor.

[0020] In an embodiment of the present application, a front-end device is used to obtain scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes the component to be rendered; determining the data version of the scene component data; updating the scene component data when the version number of the data version is less than the version number of the target version; dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain the geographic information model. The JSON data is updated through the version history record and the scene component data is dynamically registered, thereby achieving the purpose of ensuring the functional integrity of the component and the compatibility of the data version, thereby achieving the technical effect of quickly deploying the geographic information model to different environments and automatically adapting to platform updates, thereby solving the technical problem that the old version of the geographic information model cannot be rendered due to the update of the low-code platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] 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:

[0022] Figure 1 is a structural diagram of a computer terminal provided according to an embodiment of the present application;

[0023] Figure 2 This is a flowchart of a geographic information model rendering method provided in accordance with an embodiment of the present application;

[0024] Figure 3 This is a schematic diagram of a process for publishing a geographic information model according to an embodiment of the present application;

[0025] Figure 4 This is a schematic diagram of a process for rendering a geographic information model according to an embodiment of the present application;

[0026] Figure 5 This is a schematic diagram of the structure of a geographic information model rendering system provided according to an embodiment of the present application;

[0027] Figure 6 It is a structural diagram of a geographic information model rendering device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0031] Low-code development platforms are efficient application building environments that allow developers to quickly create fully functional applications with minimal or no coding. These platforms typically feature intuitive drag-and-drop components, graphical model design tools, and automated code generation, significantly lowering the barrier to entry for developers of all skill levels and accelerating application development. This model not only improves development efficiency but also encourages participation from non-professional developers, making application development more accessible and accessible.

[0032] CIM (City Information Model): The City Information Model (CIM) takes city information data as its core, deeply integrates city information with three-dimensional spatial models, and forms a comprehensive and detailed city digital twin. In terms of breadth, it covers large-scale scene data at the macro level and small-scale BIM (Building Information Modeling) data at the micro level. It also integrates Internet of Things and Geographic Information System (GIS) data to achieve comprehensive integration of multi-source heterogeneous data. The CIM platform is essentially a data-driven platform. Its core lies in its ability to accommodate and process a variety of data types, which is the prerequisite for developing various applications based on it. Only when the platform has a strong data carrying capacity can the richness and practicality of subsequent applications be ensured.

[0033] When a city develops to a certain stage, the management affairs related to urban construction grow exponentially, bringing new challenges to the work of related business departments. Combined with the current administrative approval work in the field of engineering construction, how to efficiently plan, approve and serve specific projects for implementation has become a new challenge.

[0034] Amid the boom in information technology, the City Information Model (CIM) came into being. It uses multi-source data, multiple forms, including various heterogeneous data, to form an urban system information model that is a 1:1 holographic mirror image of the physical city, realizing the orderly scheduling and organization of various seemingly or related data. At the spatial scale, it can achieve positive guidance and intervention in urban operations from a macro perspective, making the city a more livable, resilient and secure information platform, realizing the natural operation of the city in the time dimension, efficient service and orderly development and governance from a macro perspective, and achieving the purpose of real-time "twin".

[0035] The City Information Model (CIM) platform, as the cornerstone of building digital twin cities, plays a crucial role. It is a comprehensive platform primarily used for the digital representation and management of a city's three-dimensional space, buildings, and infrastructure, providing robust data support for urban planning, construction, operations, and maintenance. The CIM platform is an indispensable information infrastructure for smart city development, and its fundamental and critical importance is self-evident.

[0036] The City Information Model, combined with the flexible iteration and rapid deployment advantages of a low-code development platform, can rapidly implement classification, hierarchical query, analysis, and visual management of multiple business contents based on geographic information. This provides more comprehensive information assurance and reliable decision-making support for the management, construction, planning, and services of smart cities.

[0037] However, when the low-code development platform is updated, the old version of the city information model often cannot be rendered due to version issues.

[0038] In order to solve this problem, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0039] According to an embodiment of the present application, a method embodiment of a geographic information model rendering method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0040] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG1 shows a hardware structure block diagram of a computer terminal for implementing a geographic information model rendering method. Figure 1 As shown, the computer terminal 10 may include one or more (illustrated as 102a, 102b, ..., 102n in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0041] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry." The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10. As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0042] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the geographic information model rendering method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned geographic information model rendering method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0043] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0044] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0045] In the above operating environment, the embodiment of the present application provides a geographic information model rendering method, such as Figure 2 As shown, the method includes the following steps:

[0046] In step S202, the front-end device obtains scene configuration data and scene component data from the back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered.

[0047] Optionally, scene configuration data includes basic scene information, such as the scene's length and width (i.e., dimensions), zoom ratio, and preview image. When rendering a scene, the scene configuration data is used for rendering. Furthermore, the configuration data also stores scene permission information, such as the release time, release password, and release code, which are used for data permission management.

[0048] Optionally, generate a preview image through the html2canvas plug-in of the vue framework, call the image upload interface to save the preview image on minio, and save the returned path to the scene configuration data.

[0049] The scene component data (which can be in JSON format) is the specific component that needs to be rendered. The data is in a tree structure, with the outer node being the canvas and the lower nodes being the components. Optionally, further component nodes can be attached under the component node.

[0050] As an optional implementation, the geographic information model rendering method also includes: determining the release deadline of the geographic information model and stopping displaying the geographic information model after the release deadline; or, after receiving an access request, determining whether the geographic information model is set with a release password, and if it is determined that a release password is set, performing a password verification on the access request.

[0051] Optionally, after building the geographic information model through the low-code platform, the geographic information model needs to be packaged and published for deployment in other environments, such as cloud server environments, local server environments, or edge computing environments, to ensure that the model can run under different IT (Information Technology) architectures and network conditions, and to achieve widespread distribution and application of the geographic information model.

[0052] When publishing, users need to fill in relevant permission data first: users need to fill in the publishing deadline first. When deploying the model, the publishing deadline of the geographic information model will be determined. If it expires, it cannot be viewed (that is, the geographic information model will stop being displayed after the publishing deadline); whether there is a publishing password. If so, the password will be verified when accessing the page; publishing code, the code needs to be unique, and different scenarios are accessed through publishing codes. Different publishing codes mean different scenario data and configurations, which helps to reuse the same basic services in multiple environments while keeping the data between each scenario independent to prevent data confusion.

[0053] As an optional implementation, the geographic information model rendering method also includes: the front-end device reads a component tree corresponding to the geographic information model pre-configured in the front-end device, and the child nodes of the component tree correspond one-to-one to the components in the geographic information model; after converting the component tree into a string, it is passed to the back-end device.

[0054] Optionally, the front-end device reads the component tree stored in the Store within the Vue framework, calls the JSON.stringify method to convert the object into a string, and passes it to the back-end device. The back-end device saves the relevant database data to a file and uses Liquibase to write the data to the database in the new environment when the application starts. For example, the relevant table creation statements are written to the create_table.sql file and the initial data is written to insert_data.sql. Liquibase then initializes the table and data after the new application environment starts.

[0055] As an optional implementation, the geographic information model rendering method further includes: the back-end device determining the service application that the scene component data depends on; and packaging the service application into a mirror file.

[0056] Optionally, the service applications that need to be packaged include the CIM front-end application and the CIM back-end basic data application. The CIM front-end application is used to process JSON data to render the CIM scene. After the package is released, only viewing permissions are granted and editing is no longer possible. The CIM back-end basic data application is used to provide basic data services, including CIM page configuration and related component information.

[0057] Optionally, the backend device receives the string converted from the component, finds the applications corresponding to all dependent services, and packages the corresponding applications into an image, for example, by converting the string into an object collection through fastjson. The collection is traversed to determine whether the current component has a data source. Furthermore, if it exists, determine whether the data source type is a dynamic interface data source. Furthermore, if so, determine whether the interface URL contains a domain name variable through the regular expression \$(\w)+\ / . Furthermore, call the parameter configuration interface of the system management application to obtain the application configuration information corresponding to the domain name. Call docker through ProcessBuilder to generate the application image package.

[0058] Optionally, the backend device also generates a configuration file, such as nacos or nginx. The default values ​​of some parameters that may need to be modified (such as port numbers and application names) are replaced with variables and written to the variable file. Users can modify the default values ​​of the variable file as needed.

[0059] As an optional implementation method, before obtaining the scene configuration data and scene component data from the back-end device, the geographic information model rendering method also includes: obtaining a configuration file and a service application image corresponding to the scene component data from the back-end device, the service application image being an image of the service application that the scene component data depends on; and configuring the service application image based on the configuration file in the target operating environment.

[0060] Optionally, when the low-code platform completes the construction of the CIM scene (i.e., geographic information model) and prepares to publish it, the system performs a deep scan of the scene to identify the back-end service applications that all component data depends on. These service applications may cover data management, map services, analysis tools, etc., which are an indispensable part of scene rendering. In order to ensure the integrity and availability of the scene in any target operating environment, before obtaining the scene configuration data and scene component data from the back-end device, the front-end device will download the configuration files and Docker images of the service applications corresponding to these component data from the back-end device according to the configuration information of the scene.

[0061] Configuration files contain the parameters necessary to run service applications, such as database connection information, service ports, and access control lists. This information is crucial for the service application to start correctly in a new environment. Service application images contain the entire environment in which the service runs, from the operating system to the application code, ensuring service consistency and stability.

[0062] After obtaining the configuration file and service application image, the system deploys them to the target operating environment, such as a cloud server, a local data center, or an edge computing device. During deployment, the system sets the service application's operating parameters according to the configuration file's instructions, including but not limited to network configuration and data storage location. To adapt to different environments, configuration parameters may be stored as variables, allowing users to modify variable values ​​before deployment, such as database usernames and passwords or the IP address of the service listener.

[0063] Once configured, the service application images are started in the target environment. They will run according to the parameters set in the configuration file, providing the necessary services to support the rendering of the CIM scene. For example, the map service will load and provide map data, and the data analysis tool will process the real-time data in the scene to achieve dynamic display of the scene.

[0064] Through this series of operations, CIM scenes can be quickly deployed and rendered normally even if the target environment configuration changes, unaffected by version compatibility issues or environmental differences. This approach greatly simplifies the cross-platform scene migration process and improves deployment efficiency, while ensuring the integrity of scene data and consistency of rendering effects, providing strong technical support for scene management and application distribution in smart city projects.

[0065] Step S204: determine the data version of the scene component data.

[0066] Optionally, the larger the version number of the scene component data, the shorter the update time of its version is from the current time, that is, its version is newer. Before the scene is released, the low-code platform will version-mark the current scene component data. Each component data contains a version field to record the version number of the platform corresponding to its creation or last update. For example, the version number can be "1.2.3". This version field not only identifies the data generation environment, but also provides a checkpoint for subsequent scene deployment, allowing the system to determine whether the component data needs to be upgraded to adapt to the current platform version.

[0067] Step S206: When the version number of the data version is smaller than the version number of the target version, the scene component data is updated.

[0068] In the technical solution provided in step S206, when the version number of the data version is smaller than the version number of the target version, updating the scene component data includes: determining the target version record data, wherein the version number corresponding to the target version record data is greater than the version number of the data version, and the target version record data records the updated fields and the update method corresponding to the updated fields; determining the fields that need to be updated in the scene component data based on the target version record data and updating them.

[0069] Optionally, after obtaining the component data, the version data needs to be updated before rendering. There is a version field inside the component data to save the current data version. When the version data is updated, it will be determined whether the current data version is less than the internal version of the platform component. If so, the data will be updated. There is a component version history file inside the platform component, which saves the version of the component field (that is, the updated field) added, modified, and deleted (that is, the update method). According to the current version of the json data, find all version records that are greater than the current version, and update the version data field of the json data in turn to ensure data integrity.

[0070] Step S208 , dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model.

[0071] Optionally, the updated scene component data is traversed and dynamically registered. When a user attempts to access an updated CIM scene, the front-end application first calls the back-end interface to obtain the updated scene component data. At this point, the data is stored in JSON format and does not contain complete class definitions and methods. To render these components, the system must dynamically register them and re-assign the necessary class methods to the component instances.

[0072] In the technical solution provided in step S208, the dynamic registration processing of the updated scene component data includes: determining the component type of the updated scene component data; establishing a component instance corresponding to the updated scene component data based on the component type; determining the class method lost in the process of establishing the component instance, and supplementing the class method lost in the process of establishing the component instance.

[0073] Optionally, the component data is analyzed to determine the type of each component, such as a map layer, a 3D building model, or a data analysis chart. Subsequently, based on the component type, the corresponding class or constructor is called to create a component instance. During component instantiation, attributes in the component data, such as location coordinates, size, color, etc., are automatically read to initialize the attribute values ​​of the component instance.

[0074] Optionally, since the class methods will be lost after the string is converted to a JavaScript object, it is necessary to regenerate the object to supplement the lost methods.

[0075] As an optional implementation method, determining the class methods lost in the process of establishing a component instance and supplementing the class methods lost in the process of establishing the component instance includes: determining the original class definition of the component instance, the original class definition records all class methods of the component type; comparing the class methods in the component instance with the class methods in the original class definition, and determining the class methods lost in the process of establishing the component instance; dynamically supplementing the class methods lost in the process of establishing the component instance to the component instance.

[0076] Optionally, in order to supplement class methods that may be lost during the creation of a component instance, the front-end device will query the original class definition of the component type. The original class definition contains class methods for all component types, which becomes a comparison benchmark. The system will compare the method list in the component instance with the method list in the original class definition to find out the methods that were not loaded during the instantiation process or may have been lost due to data format problems. For example, the "3D Building Model" class may contain interactive methods such as "Rotate", "Zoom in", and "Zoom out", but after data conversion, if the "Zoom out" method is not inherited by the component instance, the system will identify and supplement this method to ensure the complete functionality of the component.

[0077] After dynamically registering and supplementing all missing class methods, the component instance is rendered according to the scene configuration data. The scene configuration data contains basic information about the scene, such as scene size, preview image, permission information, etc., as well as the layout and rendering parameters of the components in the scene. The system will set the canvas size, background, camera perspective, etc. according to the configuration data, and place the component instance in the correct position, adjusting its size and orientation to meet the layout requirements of the scene. Ultimately, a complete CIM geographic information model will be presented on the user's device, and users can get a consistent, high-quality scene experience whether on desktop applications, mobile devices or large-screen control centers.

[0078] Through dynamic registration and class method supplementation mechanisms. Dynamic registration enables front-end devices to flexibly create and initialize component instances based on component types without having to know all specific component types in advance. This greatly enhances the adaptability and scalability of CIM scenarios. Furthermore, by supplementing class methods that may be lost during component instance creation, this ensures that each component instance is fully functional regardless of the environment, avoiding rendering errors or interaction issues caused by missing methods. This not only addresses compatibility challenges associated with version updates but also improves the efficiency and user experience of CIM scenario deployment on multiple platforms, providing a solid technical foundation for the efficient management and operation of smart city projects.

[0079] Optionally, Figure 3 A geographic information model publishing process is shown in Figure 3 As shown, the process includes the following steps:

[0080] Step S301: The user fills in relevant data to publish the CIM scenario. When publishing, the user needs to fill in relevant permission data first.

[0081] Step S302: Read the Vue Store to generate JSON data, the Vue framework generates a preview image, and converts the data of all components into JSON data (for example, read the component tree stored in the Vue Store. Call the JSON.stringify method to convert the object into a string).

[0082] Step S303: Call the interface to send json to the backend, the backend writes the data into liquibase-related files, writes the relevant table creation statements into the create_table.sql file, and writes the initial data into the insert_data.sql file. After the application is started in the new environment, the table and data are initialized through liquibase.

[0083] Step S304: Backend variable json, using ProcessBuilder to call docker to generate an image: The backend receives the string and converts it into an object collection using fastjson. The collection is traversed to determine whether the current component has a data source. If so, the data source type is determined to be a dynamic interface data source. If so, the regular expression \$(\w)+\ / is used to determine whether the interface URL contains a domain name variable. Furthermore, the parameter configuration interface of the system management application is called to obtain the application configuration information corresponding to the domain name. The application image package is generated by calling docker through ProcessBuilder.

[0084] Step S305: Generate nacos configuration and nginx configuration files. The backend obtains the nacos configuration file name and file content, such as gis-service-dev.yaml, and modifies some configurations, such as database configuration, domain name configuration, and generates nginx-default.conf file, which is used for the validity period of pre-check requests, etc.

[0085] Step S306: Return the processing result.

[0086] Optionally, Figure 4 A geographic information model rendering process is shown, such as Figure 4 As shown, the process includes the following steps:

[0087] Step S401: Call the interface to obtain json data.

[0088] Step S402: Initialize store data, clear the Canvas, and load canvas configuration data.

[0089] Step S403: Call the versionUpgrade method to perform version upgrade.

[0090] Step S404: call the updateComponent method to register the component and regenerate the component object.

[0091] Step S405: Put the processed data into the store and start rendering the page.

[0092] Through the above steps, the rapid publishing and rendering of geographic information models can be achieved: the construction of the CIM scene is quickly completed through the low-code platform, and the application services and data resources that the CIM scene depends on are integrated together in combination with the Docker image and configuration file, so as to achieve rapid deployment to different environments. The published scene is protected by the publishing time, publishing password and publishing code. In addition, in the related technology, when the low-code platform is updated, the old version of the scene is often unable to be rendered due to version issues. The method embodiment of the present application avoids this problem by processing the published json data at the data level. Specifically, the method embodiment of the present application has the following advantages:

[0093] 1. Quick release and deployment: CIM is combined with low code. Through the visual interface, only a small amount of code is needed to build a CIM scenario, which lowers the development threshold. After release, it integrates resources by parsing JSON file data, migrates Liquibase data, releases based on Docker images, generates Nacos configurations, and generates Nginx configurations, making it easy to deploy to different platforms.

[0094] 2. Version upgrade: Iteratively upgrade JSON data based on version history records. When the platform is upgraded, when rendering old scene data, it will automatically merge and upgrade according to the version record to avoid the old data from being unusable and reduce user maintenance costs.

[0095] The embodiment of the present application provides a geographic information model rendering system, Figure 5 This is a structural diagram of the system, as shown in Figure 5 As shown, the system includes a front-end device 51 and a back-end device 52, wherein: the front-end device is used to obtain scene configuration data and scene component data from the back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered; determining the data version of the scene component data; when the version number of the data version is less than the version number of the target version, updating the scene component data; dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model; the back-end device is used to determine the service application that the scene component data depends on; and packaging the service application into a mirror file.

[0096] The embodiment of the present application provides a geographic information model rendering device suitable for use in a front-end device. Figure 6 is a structural diagram of the device, such as Figure 6As shown, the apparatus includes: a first processing module 60, for acquiring scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of a geographic information model, and the scene component data includes components to be rendered; a second processing module 62, for determining a data version of the scene component data; a third processing module 64, for updating the scene component data when the version number of the data version is less than the version number of the target version; a fourth processing module 66, for dynamically registering the updated scene component data, and after dynamic registration, calling the scene configuration data to render the dynamically registered scene component data to obtain a geographic information model.

[0097] In some embodiments of the present application, when the version number of the data version is smaller than the version number of the target version, the third processing module 64 updates the scene component data, including: determining the target version record data, wherein the version number corresponding to the target version record data is greater than the version number of the data version, and the target version record data records the updated fields and the update method corresponding to the updated fields; determining the fields that need to be updated in the scene component data based on the target version record data and updating them.

[0098] In some embodiments of the present application, the fourth processing module 66 performs dynamic registration processing on the updated scene component data, including: determining the component type of the updated scene component data; establishing a component instance corresponding to the updated scene component data based on the component type; determining the class method lost in the process of establishing the component instance, and supplementing the class method lost in the process of establishing the component instance.

[0099] In some embodiments of the present application, the fourth processing module 66 determines the class methods lost in the process of establishing the component instance, and supplements the class methods lost in the process of establishing the component instance, including: determining the original class definition of the component instance, the original class definition records all class methods of the component type; comparing the class methods in the component instance with the class methods in the original class definition, and determining the class methods lost in the process of establishing the component instance; dynamically supplementing the class methods lost in the process of establishing the component instance to the component instance.

[0100] In some embodiments of the present application, before obtaining the scene configuration data and scene component data from the back-end device, the first processing module 60 is also used to: obtain a configuration file and a service application image corresponding to the scene component data from the back-end device, where the service application image is an image of the service application that the scene component data depends on; and configure the service application image according to the configuration file in the target operating environment.

[0101] In some embodiments of the present application, the first processing module 60 is also used to: determine the release deadline of the geographic information model, and stop displaying the geographic information model after the release deadline; or, after receiving an access request, determine whether the geographic information model is set with a release password, and if it is determined that a release password is set, perform a password verification on the access request.

[0102] In some embodiments of the present application, the front-end device is also used to read a component tree corresponding to the geographic information model pre-configured in the front-end device, and the child nodes of the component tree correspond one-to-one to the components in the geographic information model; after converting the component tree into a string, it is passed to the back-end device.

[0103] In some embodiments of the present application, the backend device is used to determine the service application that the scene component data depends on; and package the service application into a mirror file.

[0104] It should be noted that the various modules in the above-mentioned geographic information model rendering device can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0105] An embodiment of the present application provides a non-volatile storage medium, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the following geographic information model rendering method: a front-end device obtains scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of the geographic information model, and the scene component data includes components to be rendered; determines a data version of the scene component data; when the version number of the data version is less than the version number of the target version, updates the scene component data; dynamically registers the updated scene component data, and after the dynamic registration, calls the scene configuration data to render the dynamically registered scene component data to obtain a geographic information model.

[0106] An embodiment of the present application provides an electronic device, comprising: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the following geographic information model rendering method is executed when the program is running: a front-end device obtains scene configuration data and scene component data from a back-end device, wherein the scene configuration data comprises at least one of the following: scene size information, scene scaling information, and a preview image of a geographic information model, and the scene component data comprises components to be rendered; determining a data version of the scene component data; updating the scene component data when the version number of the data version is less than the version number of the target version; dynamically registering the updated scene component data, and calling the scene configuration data after dynamic registration to render the dynamically registered scene component data to obtain a geographic information model.

[0107] An embodiment of the present application provides a computer program product, including a computer program, which implements the following geographic information model rendering method when executed by a processor: a front-end device obtains scene configuration data and scene component data from a back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information and a preview image of a geographic information model, and the scene component data includes components to be rendered; determines a data version of the scene component data; when the version number of the data version is less than the version number of the target version, updates the scene component data; dynamically registers the updated scene component data, and after the dynamic registration, calls the scene configuration data to render the dynamically registered scene component data to obtain a geographic information model.

[0108] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0109] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0110] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0111] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0112] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0113] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A geographic information model rendering method, characterized in that: include: The front-end device obtains scene configuration data and scene component data from the back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information, and a preview image of the geographic information model, and the scene component data includes components to be rendered; Determining a data version of the scene component data; When the version number of the data version is smaller than the version number of the target version, updating the scene component data; Dynamic registration processing is performed on the updated scene component data, and after dynamic registration, the scene configuration data is called to render the dynamically registered scene component data to obtain the geographic information model.

2. The geographic information model rendering method according to claim 1, characterized in that: When the version number of the data version is smaller than the version number of the target version, updating the scene component data includes: Determine target version record data, wherein the version number corresponding to the target version record data is greater than the version number of the data version, and the target version record data records an updated field and an update method corresponding to the updated field; The fields that need to be updated in the scene component data are determined based on the target version record data and updated.

3. The geographic information model rendering method according to claim 1, characterized in that: Dynamically registering the updated scene component data includes: Determining the component type of the updated scene component data; Establishing a component instance corresponding to the updated scene component data according to the component type; A class method lost during the process of establishing the component instance is determined, and the class method lost during the process of establishing the component instance is supplemented.

4. The geographic information model rendering method according to claim 3, characterized in that: Determining the class method lost in the process of establishing the component instance, and supplementing the class method lost in the process of establishing the component instance includes: Determine the original class definition of the component instance, where the original class definition records all class methods of the component type; comparing the class methods in the component instance with the class methods in the original class definition to determine class methods lost during the creation of the component instance; The class methods lost during the process of establishing the component instance are dynamically added to the component instance.

5. The geographic information model rendering method according to claim 1, characterized in that: Before obtaining scene configuration data and scene component data from the backend device, the geographic information model rendering method further includes: Obtaining a configuration file and a service application image corresponding to the scene component data from a backend device, where the service application image is an image of a service application on which the scene component data depends; The service application image is configured according to the configuration file in the target operating environment.

6. The geographic information model rendering method according to claim 1, characterized in that: The geographic information model rendering method further includes: Determine a release deadline for the geographic information model, and stop displaying the geographic information model after the release deadline; or After receiving the access request, it is determined whether the geographic information model is set with a publishing password, and if it is determined that the publishing password is set, the access request is password verified.

7. The geographic information model rendering method according to claim 1, characterized in that: The geographic information model rendering method further includes: The front-end device reads a component tree corresponding to the geographic information model that is pre-configured in the front-end device, wherein the child nodes of the component tree correspond one-to-one to the components in the geographic information model; After converting the component tree into a string, the string is passed to the backend device.

8. The geographic information model rendering method according to claim 1, characterized in that: The geographic information model rendering method further includes: The backend device determines the service application that the scene component data depends on; The service application is packaged into an image file.

9. A geographic information model rendering device, suitable for use in a front-end device, characterized in that: include: A first processing module is configured to obtain scene configuration data and scene component data from a backend device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information, and a preview image of the geographic information model; and the scene component data includes components to be rendered; A second processing module, configured to determine a data version of the scene component data; A third processing module is configured to update the scene component data if the version number of the data version is smaller than the version number of the target version; The fourth processing module is used to dynamically register the updated scene component data, and after dynamic registration, call the scene configuration data to render the dynamically registered scene component data to obtain the geographic information model.

10. A geographic information model rendering system, characterized in that: Including front-end equipment and back-end equipment, including: The front-end device is configured to obtain scene configuration data and scene component data from the back-end device, wherein the scene configuration data includes at least one of the following: scene size information, scene scaling information, and a preview image of the geographic information model, and the scene component data includes components to be rendered; determine a data version of the scene component data; if the version number of the data version is less than the version number of the target version, update the scene component data; dynamically register the updated scene component data, and after the dynamic registration, call the scene configuration data to render the dynamically registered scene component data to obtain the geographic information model; The backend device is used to determine the service application that the scene component data depends on; and package the service application into a mirror file.

11. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the geographic information model rendering method according to any one of claims 1 to 8.

12. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the geographic information model rendering method according to any one of claims 1 to 8 is executed when the program is run.

13. A computer program product, characterized in that The method comprises a computer program, which implements the geographic information model rendering method according to any one of claims 1 to 8 when executed by a processor.

Images