Method, apparatus, electronic device and readable medium for managing scene data

Abstract

The present disclosure provides a method, apparatus, electronic device, and readable medium for managing scenario data, belonging to the field of computer technology. The method includes: drawing corresponding scenario elements through the drawing entrances of each element included in the scenario editing interface; obtaining user private data stored in the private storage space through the private data access entrance in the scenario editing interface; obtaining system public data stored in the public storage space through the public data access entrance in the scenario editing interface; editing the drawn scenario elements based on the user private data and the system public data to obtain a scenario model; and generating a scenario description file in response to the received scenario saving instruction for providing to a scenario parser for parsing and loading. This approach separates the storage of user private data and system public data, facilitating the setting of different data access permissions for different users and achieving the purpose of isolating and protecting user private data.

Description

Technical Field

[0001] The present disclosure belongs to the field of computer technology, and particularly relates to a method, apparatus, electronic device, and readable medium for managing scenario data. Background Art

[0002] A Geographic Information System (GIS), also known as a "geo-information system", belongs to a specific spatial information system. This system is used to collect, store, manage, calculate, analyze, display, and describe geographical distribution data in the space of the entire or part of the Earth's surface (including the atmosphere) under the support of computer hardware and software systems.

[0003] For example, in professional field systems such as cities, transportation, and environmental protection, geographical information data is often required for display and data analysis. To meet the application requirements of the above scenarios, it is necessary to develop each scenario separately one by one, which is time-consuming and laborious.

[0004] It can be seen that the scenarios developed in the existing geographic information system cannot be saved and reused, thereby increasing the scenario management cost and being unfavorable for the rapid creation and editing of scenarios. Summary of the Invention

[0005] The present disclosure aims to provide a method, apparatus, electronic device, and readable medium for managing scenario data.

[0006] The first aspect of the present disclosure provides a method for managing scenario data, which includes:

[0007] Drawing corresponding scenario elements through each element drawing entry included in the scenario editing interface, where the scenario editing interface includes a plurality of element drawing entries for drawing different types of scenario elements;

[0008] Obtaining user private data stored in the private storage space through the private data access entry in the scenario editing interface; obtaining system public data stored in the public storage space through the public data access entry in the scenario editing interface;

[0009] Based on the obtained user private data and system public data, editing each of the drawn scenario elements to obtain a scenario model including a plurality of scenario elements;

[0010] In response to receiving a scenario save instruction, obtaining the element attribute information of each scenario element included in the scenario model, generating a scenario description file corresponding to the element attribute information of each scenario element based on a preset specification, and storing the scenario description file in the private storage space for parsing and loading by a scenario parser.

[0011] The second aspect of the present disclosure provides a method for managing scenario data, which includes:

[0012] In response to a received scenario loading request, obtain a scenario description file corresponding to the scenario loading request;

[0013] Parse the scenario description file based on a preset specification to obtain the element attribute information of each scenario element included in the scenario model corresponding to the scenario description file;

[0014] Based on the element attribute information of each scenario element, load and display the scenario model.

[0015] The third aspect of the present disclosure provides a device for managing scenario data, which includes:

[0016] A drawing module, configured to draw corresponding scenario elements through each element drawing entry included in the scenario editing interface, where the scenario editing interface includes a plurality of element drawing entries for drawing different types of scenario elements;

[0017] An acquisition module, configured to obtain user private data stored in a private storage space through a private data access entry in the scenario editing interface; obtain system public data stored in a public storage space through a public data access entry in the scenario editing interface;

[0018] An editing module, configured to edit each drawn scenario element based on the obtained user private data and system public data to obtain a scenario model including a plurality of scenario elements;

[0019] A generation module, configured to, in response to a received scenario saving instruction, obtain the element attribute information of each scenario element included in the scenario model, generate a scenario description file corresponding to the element attribute information of each scenario element based on a preset specification, and store the scenario description file in the private storage space for parsing and loading by a scenario parser.

[0020] The fourth aspect of the present disclosure provides a device for managing scenario data, which includes:

[0021] An acquisition module, configured to obtain a scenario description file corresponding to the received scenario loading request in response to the received scenario loading request;

[0022] A parsing module, configured to parse the scenario description file based on a preset specification to obtain the element attribute information of each scenario element included in the scenario model corresponding to the scenario description file;

[0023] A loading module, configured to load and display the scenario model based on the element attribute information of each scenario element.

[0024] The fifth aspect of the present disclosure provides an electronic device, including:

[0025] One or more processors;

[0026] A memory storing one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the method described in any one of the above;

[0027] One or more I / O interfaces connected between the processor and the memory and configured to implement information interaction between the processor and the memory.

[0028] The sixth aspect of the present disclosure provides a computer-readable medium storing a computer program, which when executed by a processor, implements the method described in any one of the above. Description of the Drawings

[0029] Figure 1 It is a flowchart of the method for managing scenario data provided by an embodiment of the present disclosure;

[0030] Figure 2 It is a flowchart of the method for managing scenario data provided by another embodiment of the present disclosure;

[0031] Figure 3 It is a flowchart of the method for managing scenario data provided by another embodiment of the present disclosure;

[0032] Figure 4 It is a flowchart of the specific implementation manner of step S330.

[0033] Figure 5 It shows a schematic structural diagram of a device for managing scenario data provided by another embodiment of the present disclosure;

[0034] Figure 6 It shows a schematic structural diagram of a device for managing scenario data provided by yet another embodiment of the present disclosure;

[0035] Figure 7 It is a principle block diagram of an electronic device provided by an embodiment of the present disclosure. Detailed Embodiments

[0036] To enable those skilled in the art to better understand the technical solutions of the present disclosure / invention, the present disclosure / invention will be further described in detail below with reference to the drawings and specific embodiments.

[0037] Unless otherwise defined, technical terms or scientific terms used in this disclosure shall have the ordinary meanings as understood by those of ordinary skill in the field to which this disclosure belongs. The "first", "second" and similar terms used in this disclosure do not denote any order, quantity or importance, but are only used to distinguish different components. Similarly, words such as "a", "an" or "the" do not denote a quantity limitation, but mean that there is at least one. Words such as "including" or "comprising" mean that the elements or objects appearing before this word cover the elements or objects listed after this word and their equivalents, without excluding other elements or objects. Words such as "connected" or "coupled" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Upper", "lower", "left", "right", etc. are only used to represent relative positional relationships. When the absolute position of the object being described changes, the relative positional relationship may also change accordingly.

[0038] In a first aspect, an embodiment of the present disclosure provides a method for managing scenario data. The management method realizes a flexible creation process of a scenario model based on a GIS system and can implement a quick save operation of the scenario model.

[0039] As Figure 1 shown, the method for managing scenario data provided by the embodiment of the present disclosure can be applied to a GIS system. The method includes:

[0040] Step S110: Draw corresponding scenario elements through each element drawing entry included in the scenario editing interface. The scenario editing interface includes multiple element drawing entries for drawing different types of scenario elements.

[0041] Among them, the scenario editing interface is used to edit the created scenario. In the scenario editing interface, there are multiple element drawing entries for drawing different types of scenario elements. Through different element drawing entries, corresponding types of scenario elements can be drawn.

[0042] Among them, a GIS scenario includes multiple types of scenario elements, and a complete GIS scenario is jointly composed of various types of scenario elements. For example, scenario elements include: basic layers, map data, 3D models, vector graphics, etc. The present invention does not limit the specific types and quantities of scenario elements, and any module or unit that can be used to constitute a GIS scenario can be used as a scenario element.

[0043] Step S120: Obtain user private data stored in the private storage space through the private data access entry in the scenario editing interface; obtain system public data stored in the public storage space through the public data access entry in the scenario editing interface.

[0044] Among them, user private data refers to: personal data belonging to the currently logged-in user. Among them, the user private data of each logged-in user is for the use of this user, and other users usually have no permission to access it. By setting user private data, it is convenient to flexibly manage the personalized data of each user. Through user private data, the personalized data of users can be stored, such as facility data within the user's work unit, building data near the user's home, etc. Moreover, user private data is stored in a private storage space and can only be accessed according to the user identification of the corresponding user, and other users have no access permission.

[0045] In the GIS system, in addition to storing user private data uploaded by users in advance, there is also system public data that can be shared by each logged-in user. Different from the permission access method of user private data, system public data can be accessed by all users. Through system public data, the general data in the map drawing process can be stored, such as public roads, public buildings, and other publicized contents. Among them, system public data is stored in a public storage space, and each user can access it through the public data access interface.

[0046] Step S130: Based on the obtained user private data and system public data, edit each drawn scene element to obtain a scene model containing multiple scene elements.

[0047] Among them, each scene element contains various information. For example, taking the scene element of the 3D model type as an example, in order to accurately describe each part of the 3D model, it is necessary to load the corresponding model resources. Among them, different model resources may be stored in the private storage space and the public storage space respectively. Correspondingly, based on the obtained user private data and system public data, edit each drawn scene element to obtain a scene model composed of each scene element.

[0048] Step S140: In response to the received scene saving instruction, obtain the element attribute information of each scene element included in the scene model, generate a scene description file corresponding to the element attribute information of each scene element based on a preset specification, and store the scene description file in the private storage space to provide it to the scene parser for parsing and loading.

[0049] Among them, the scene saving instruction can be of various types such as a cloud saving instruction or a local saving instruction. The preset specification is used to define the data format and storage method of the scene description file. In this disclosure, a preset specification for generating the scene description file is predefined, and through this preset specification, various types of scene contents can be uniformly stored. Among them, the element attribute information of each scene element included in the scene model is stored in the scene description file.

[0050] Correspondingly, the scene description file can be parsed and loaded by the scene parser, so as to quickly restore the scene model configured by the user.

[0051] It can be seen that by storing the user's private data and the system's public data separately, this method facilitates setting different data access permissions for different users, achieving the purpose of isolating and protecting the user's private data. When loading scene data, only the user's private data related to the scene and the system's public data within the viewport are loaded, improving the data reuse rate, reducing the data loading volume, and enhancing the scene rendering speed. Moreover, by presetting preset specifications, the scene model can be stored as a standardized scene description file, which is convenient for quickly parsing and restoring the corresponding scene through the scene parser to implement scene management operations, and then realizing the reuse of scenes, reducing the scene management cost.

[0052] In a second aspect, the embodiments of the present disclosure provide a method for managing scene data. This management method is based on a GIS system or other business systems to implement the parsing and loading process of the scene description file, and can achieve the rapid loading of the scene model.

[0053] As Figure 2 shown, the method for managing scene data provided by the embodiments of the present disclosure can be applied to a GIS system or other business systems. The method includes:

[0054] Step S210: In response to the received scene loading request, obtain the scene description file corresponding to the scene loading request.

[0055] Among them, the scene loading request can be triggered through the scene loading entry in the GIS system, or it can also be triggered through the scene loading entry in the business system. Among them, the business system can communicate with the GIS system and is used to implement specified business functions with the help of map data.

[0056] The scene description file can be generated in the manner of the embodiment Figure 1 shown. Among them, the scene description file can be either a locally stored file or a cloud-stored file, and can be specifically obtained through the scene identifier included in the scene loading request.

[0057] Step S220: Parse the scene description file based on the preset specifications to obtain the element attribute information of each scene element included in the scene model corresponding to the scene description file.

[0058] Among them, the preset specification is used to define the data format and storage method of the scenario description file. In the present disclosure, a preset specification for generating the scenario description file is predefined, and through this preset specification, the element attribute information of various types of scenario elements can be uniformly stored. Correspondingly, the scenario description file can be parsed and loaded through the scenario parser, so as to quickly restore the scenario model configured by the user. The scenario parser can be set in the GIS system or the business system to implement the parsing and loading functions of the scenario description file.

[0059] Step S230: Load and display the scenario model based on the element attribute information of each scenario element.

[0060] To facilitate the user's management operations such as browsing and secondary editing of the scenario model, in this step, the loaded scenario model is displayed in the system interface.

[0061] It can be seen that this method can quickly parse the scenario description file through the scenario parser by presetting the preset specification, so as to restore the corresponding scenario model, which is convenient for management operations such as modifying and editing the scenario model, realizes the reuse of scenarios, and reduces the scenario management cost.

[0062] In a third aspect, the embodiments of the present disclosure provide a method for managing scenario data to implement the generation, parsing, and loading processes of the scenario description file and enable the rapid loading of the scenario model.

[0063] As Figure 3 shown, the method for managing scenario data provided by the embodiments of the present disclosure can be applied to the GIS system or other business systems. Among them, Figure 3 the embodiments shown are intended to provide a more detailed description of Figure 1 and Figure 2 the embodiments shown. The method includes:

[0064] Step S310: Receive and store the user private data uploaded to the GIS system.

[0065] In this embodiment, the geographic information data is managed in layers. The so-called layer management means that the user private data and the system public data are stored in different data storage spaces respectively to implement the management of different access permissions. For example, the user private data is stored in the private storage space, and the system public data is stored in the system public space. In addition, in order to prevent the user private data from being maliciously accessed by other users, in this embodiment, the private storage space further includes: a plurality of user private spaces corresponding to different users respectively, where the user private spaces of different users are isolated from each other, and each user private space can only be accessed through the corresponding user identifier, and other users have no access permission.

[0066] Among them, a private data upload entry is included in the system interface of the GIS system. Through this private data upload entry, user private data can be uploaded to the GIS system. This user private data can also be called material data and can be specifically stored in the user private space corresponding to the user account. For example, in response to a received private data upload request, obtain the user identification and user private data included in the private data upload request; store the user private data in the user private space corresponding to the user identification in the private storage space. Among them, the private data upload request is triggered through the above-mentioned private data upload entry.

[0067] In an alternative implementation, the user private data is user material, which is specifically stored in the material management library and uploaded through the material management entry. First, deploy the GIS system to the user machine, specifically using the installation package for deployment, or the mirror can also be used for deployment. Then, register the user in the GIS system. Finally, upload the user private data in the material management library for subsequent steps. Among them, the material can be a picture, a 3D model, a json data file, etc.

[0068] For example, a "material management" entry is set in the system interface of the GIS system. The user can click this entry to upload the material and set the material type.

[0069] Step S320: In response to a received scene creation request, generate a scene identifier and create scene framework data.

[0070] This step is mainly used to implement the scene creation operation to create a user scene corresponding to the scene identifier. This scene is usually a user-defined scene and is stored in the user's private space after creation.

[0071] Among them, the scene creation request can be triggered through the "scene management" entry set in the system interface. In response to the received scene creation request, a scene creation interface is displayed in the system interface. This scene creation interface includes a scene name setting entry and a scene introduction setting entry for setting the auxiliary description information of the scene, so as to quickly filter available scenes from multiple created scenes through the auxiliary description information.

[0072] In addition, in this step, based on the scene creation request, generate a scene identifier and create scene framework data. Among them, the scene framework data is used to implement the framework construction of the scene to display the general outline of the scene. Among them, multiple types of scene framework data corresponding to different types of scenes can be preset in advance, so as to create the scene framework data corresponding to the scene type according to the scene type included in the scene creation request.

[0073] Step S330: In response to the received scene editing request, draw a scene model corresponding to the scene editing request based on the user's private data and the system public data in the GIS system.

[0074] In the GIS system, in addition to storing the user's private data uploaded in advance by the user, there is also system public data that can be shared by each logged-in user. Different from the permission access method of the user's private data, the system public data can be accessed by all users. Through the system public data, general data in the map drawing process can be stored, such as public roads, public buildings and other publicized contents. Correspondingly, the scene model is generated based on the user's private data and the system public data.

[0075] Among them, the scene editing request is used to implement the editing operation for the created scene, specifically including: a start editing request for entering the scene editing interface, an element drawing request for drawing different types of scene elements, an element editing request for editing each drawn element, and an event configuration request for configuring events for the scene elements. Correspondingly, step S330 further includes Figure 4 the sub-steps shown below. As Figure 4 shown, step S330 includes the following sub-steps:

[0076] Sub-step S331: Draw the corresponding scene elements through the respective element drawing entrances included in the scene editing interface. The scene editing interface includes multiple element drawing entrances for drawing different types of scene elements.

[0077] Among them, in response to the received start editing request, the above-mentioned scene editing interface is displayed. In response to the element drawing request triggered through the element drawing entrance included in the scene editing interface, obtain the element type identifier included in the element drawing request, and draw the scene element corresponding to the element type identifier. Among them, the scene element is drawn based on the scene framework data.

[0078] In one example, the scene elements include at least one of the following nine types: basic layer, map data, road network, vector graphics, 3D model, data visualization, event, special effect, view. Correspondingly, the element drawing entrances for drawing different types of scene elements include: the first element drawing entrance (basic layer drawing entrance) for drawing scene elements of the basic layer type, the second element drawing entrance (map data drawing entrance) for drawing scene elements of the map data type, the third element drawing entrance (road network drawing entrance) for drawing scene elements of the road network type, the fourth element drawing entrance (vector graphics drawing entrance) for drawing scene elements of the vector graphics type, the fifth element drawing entrance (3D model drawing entrance) for drawing scene elements of the 3D model type, the sixth element drawing entrance (data visualization drawing entrance) for drawing scene elements of the data visualization type, the seventh element drawing entrance (event drawing entrance) for drawing scene elements of the event type, the eighth element drawing entrance (special effect drawing entrance) for drawing scene elements of the special effect type, and the ninth element drawing entrance (view drawing entrance) for drawing scene elements of the view type. In this example, nine types of scene elements are preset, and an entrance list area is provided in the scene editing interface. Each element drawing entrance is displayed in this entrance list area, and the user can select the corresponding drawing entrance according to the type of the scene element to be drawn. Moreover, a scene image drawing area is also included in the scene editing interface, and this area is used to display in real time the scene model composed of various scene elements drawn by the user. By presetting multiple scene elements and setting corresponding drawing entrances for various scene elements respectively, various complex scenes can be flexibly drawn with scene elements as the basic unit. Among them, the GIS scene is composed of multiple different types of scene elements.

[0079] Sub-step S332: Obtain the user's private data stored in the private storage space through the private data access entrance in the scene editing interface; obtain the system public data stored in the public storage space through the public data access entrance in the scene editing interface.

[0080] Among them, the corresponding element resource data usually also needs to be included in the scene elements. For example, taking the scene element of the 3D model type as an example, the corresponding element resource data also needs to be added to this 3D model. The element resource data includes: file type resource data, video type resource data, picture type resource data, etc.

[0081] To facilitate configuring the corresponding element resource data for the scene elements, it is necessary to access the user's private data and the system public data mentioned above. Since the two types of data are stored separately, when accessing, different access entrances in the front-end interface need to be used respectively to point to different storage spaces, so as to obtain the corresponding data.

[0082] For example, in response to a private data access request triggered by a private data access entry in the scenario editing interface, obtain the user identifier of the current user included in the private data access request, and call the private data access interface to access the user private space corresponding to the user identifier to obtain user private data. Also, in response to a public data access request triggered by a public data access entry in the scenario editing interface, call the public data access interface to access the public storage space to obtain system public data.

[0083] Sub-step S333: Based on the obtained user private data and system public data, edit each of the drawn scenario elements to obtain a scenario model including multiple scenario elements.

[0084] Among them, since the scenario elements include different types of element resource data, and different element resource data may be provided by user private data and system public data respectively. Therefore, in this step, based on the obtained user private data and system public data, edit each of the drawn scenario elements to obtain a scenario model including multiple scenario elements. It can be seen that the scenario elements are edited according to user private data and system public data, and the scenario model is composed of multiple scenario elements.

[0085] Sub-step S334: In response to the received event configuration request, determine the scenario element corresponding to the event configuration request, and configure a trigger event matching the event type included in the event configuration request for the scenario element.

[0086] Among them, sub-step S334 is an optional step. In other embodiments, sub-step S334 may also be omitted.

[0087] Through sub-step S334, response events can be added to the scenario model, and the response events are usually triggered for one or more scenario elements in the scenario model. Among them, the event configuration request can be triggered through the event drawing entry mentioned above, or can be triggered in other ways, which is not limited in the present invention. Among them, for the scenario element, an event interface is configured, and the event association data corresponding to the triggered event is bound to the event interface to configure the event type of the triggered event through the event interface. It can be seen that in this embodiment, an event interface is configured for a specific scenario element, and the event interface is bound to the event association data. Among them, the event association data refers to various data related to the triggered event, such as monitoring data after the triggered event is started, alarm data during subsequent alarm processing after the triggered event is started, alarm policies, etc. Among them, the event types include: monitoring type and prediction type. Correspondingly, the event association data corresponding to the triggered event includes at least one of the following: monitoring object data of the triggered event, monitoring policy data, and event response result data. For example, when the event type is the monitoring type, when configuring a triggered event for a scenario element that matches the event type included in the event configuration request, the following information of the triggered event is configured through the event interface: monitoring object, monitoring policy, and event response result. This event interface is used to set the event attribute information of the triggered event, including at least one of the following: monitoring object of the triggered event, monitoring policy, and event response result.

[0088] Among them, the scenario model in this embodiment can be applied to the application scenario of digital twin city. Through the digital twin city, scenes such as buildings, vehicles, and water systems in the real world can be presented in a three-dimensional virtual space in a virtual reality manner, creating a digital twin scenario, also called a virtual world, so as to render the positioning attributes, addresses, and location information of the three-dimensional model of each city.

[0089] In an optional implementation manner, a triggered event is configured for the scenario object of the 3D model included in the scenario model to implement the fire monitoring function. For example, a triggered event is configured for the fire protection system in the 3D model. The event type of this triggered event is the monitoring type, and the event association data includes: monitoring object data (for example, the ambient temperature value of the fire protection system, specifically the value obtained by the temperature monitor), monitoring policy data (for example, the monitoring policy is to obtain the monitoring value of the temperature monitor every 10 seconds and compare the monitoring value with a preset fire temperature threshold to determine whether the monitoring value is greater than the preset fire temperature threshold), and event response result data (for example, if the monitoring value is greater than the preset fire temperature threshold, then control the display mode of the 3D model to change, such as changing the color of the 3D model or displaying a flame element in the 3D model to play a warning role).

[0090] In yet another alternative implementation, a trigger event is configured for the 3D model, which is a scene object included in the scene model, to implement the function of predicting the machine life. For example, a trigger event is configured for the factory machine in the 3D model. The event type of this trigger event is a prediction type, and the event-associated data includes: monitoring object data (e.g., the usage duration of the machine), monitoring strategy data (e.g., the monitoring strategy is to compare the usage duration of the machine with a preset life threshold to determine whether the usage duration is greater than the preset life threshold), and event response result data (e.g., if the absolute value of the difference between the usage duration and the life threshold is less than a preset value, change the color of the machine to serve as a warning). Additionally, during the prediction process, a pre-trained deep learning model can be further combined to obtain multiple parameters associated with the machine, so as to more accurately predict the machine life by combining the parameter values of the multiple parameters.

[0091] For another example, a response event can also be added for the rain gauge, a scene element. The monitoring object of the monitoring event is configured through the event interface to be the rainfall amount, the monitoring strategy is to obtain the rainfall monitoring result every 5 minutes, and the event response result is to give an early warning when the rainfall monitoring result is greater than a preset value.

[0092] In a specific example, the scene model is visually edited using the scene editor provided by the GIS system, including drawing ground features, roads, adding 3D models, visualizing data, special effects, configuring views, editing key frames, etc.

[0093] Step S340: In response to the received scene saving instruction, generate a scene description file corresponding to the scene model based on a preset specification; wherein, the scene description file is used to be provided to the scene parser for parsing and loading.

[0094] When the scene saving instruction is received, obtain the element attribute information of each scene element included in the scene model, generate a scene description file corresponding to the element attribute information of each scene element based on a preset specification, and store the scene description file in the user's private space to be provided to the scene parser for parsing and loading.

[0095] Among them, the scene saving instruction can be of various types such as a cloud saving instruction or a local saving instruction. First, determine the element attribute information of each scene element included in the scene model respectively, and generate element description data for describing each element attribute information based on a preset specification. Then, generate a scene description file according to the element description data of each element attribute information. Among them, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method. The preset specification is used to define the format of the scene description file, specifically used to define the mapping relationship between the element attribute information of the scene element and the description specification in the scene description file.

[0096] In the first implementation manner, the scene saving instruction includes: a cloud saving instruction. Correspondingly, the scene description file is associated and stored in the cloud database through the cloud saving entry. For example, when the user clicks the save button, the GIS system analyzes the current scene, generates the scene description data in the scene description file according to the scene configuration specification (i.e., the preset specification), and saves it to the user private space in the cloud database.

[0097] In the second implementation manner, the scene saving instruction includes: a local saving instruction. Correspondingly, the scene description file is exported and stored in the user private space of the local database through the local saving entry. For example, when the user clicks the export button, the GIS system generates the scene description data according to the scene configuration specification and exports it as a json file.

[0098] Step S350: In response to the received scene loading request, obtain the scene description file corresponding to the scene loading request.

[0099] In one implementation manner, the scene loading request includes: a cloud loading request. Correspondingly, obtain the scene identifier included in the scene loading request, and obtain the scene description file corresponding to the scene identifier from the cloud database based on the scene identifier.

[0100] In another implementation manner, the scene loading request includes: a local loading request. Correspondingly, according to the scene identifier included in the scene loading request, obtain the scene description file stored locally corresponding to the scene identifier.

[0101] Step S360: Parse the scene description file based on the preset specification to obtain the scene model corresponding to the scene description file, and load and display the scene model.

[0102] Among them, the element attribute information of each scene element included in the scene model corresponding to the scene description file is obtained by parsing the scene description file based on a preset specification; the scene model is loaded and displayed based on the element attribute information of each scene element. For example, the element description data included in the scene description file is obtained, and the element attribute information of each scene element corresponding to the element description data is determined based on the preset specification; among them, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method. In addition, the element description data is used to store the element attribute information of the scene element in accordance with the format defined by the preset specification. Correspondingly, the scene description file is stored in the user's private space, consists of element description data, and the element description data follows the above preset specification.

[0103] It can be seen that the element attribute information of the scene element is described according to the preset specification to obtain the element description data, and the scene description file is composed of the element description data.

[0104] In one implementation, when loading and displaying the scene model, each scene element included in the scene model is obtained, the scene element configured with the trigger event is determined as the target scene element, and a trigger event matching the event type corresponding to the target scene element is generated. Specifically, the event interface configured for the target scene element is determined, the event association data bound to the event interface is obtained, and the trigger event is generated according to the event association data. Among them, the event types include: monitoring type and prediction type, and the event association data bound to the event interface includes at least one of the following: monitoring object data of the trigger event, monitoring strategy data, and event response result data. When the scene loading request is a cloud loading request (corresponding to the case where the scene saving instruction is a cloud saving instruction), when the user uses the scene, the scene parser is added to the business system by using an embedded framework (such as web iframe), and the scene identifier is specified in the URL. The parser will obtain the scene description data from the GIS system according to the scene identifier and parse it, and finally display it on the business page.

[0105] When the scene loading request is a local loading request (corresponding to the case where the scene saving instruction is a local saving instruction), when the user uses offline data, the scene parser is included in the business system by using an embedded framework, and the json file data is sent to the parser in the iframe framework by using communication mechanisms such as postMessage. The parser parses according to the scene description data and finally displays it on the business page.

[0106] Among them, in one implementation, steps S350 to S370 are executed by the GIS system. In another implementation, steps S350 to S370 are executed by a business system capable of communicating with the GIS system. Moreover, in the latter case, the scenario description file is parsed by a scenario parser set in the business system to obtain a scenario model corresponding to the scenario description file. Additionally, with the help of the business system, additional functions such as monitoring and querying can be performed on the loaded scenario model. For example, if the element attribute information includes element extension data, the element extension data of each scenario element can be queried and displayed in the business system to provide reference for users. Among them, the element extension data includes: auxiliary description information of the scenario element.

[0107] Among them, the loading method based on cloud storage can uniformly manage the user's scenario model through the cloud database, which is beneficial to reducing the management cost of the user-side device. The loading method based on local storage stores the scenario model directly locally without passing through the cloud. For some data with high security, the risk of being maliciously intercepted during transmission can be avoided. The above two storage methods can be flexibly set according to the security requirements of the business scenario.

[0108] The above embodiments can be implemented based on WebGL (i.e., Web Graphics Library). Among them, WebGL is a JavaScript API that can render high-performance interactive 3D or 2D graphics in any compatible Web browser without using plugins. WebGL achieves this by introducing an API that is very consistent with OpenGL ES 2.0, and this API can be used in HTML5 <canvas>It is used in elements. This feature enables the API to utilize the hardware graphics acceleration function provided by the user's device, thereby achieving an improvement in the model drawing speed.

[0109] The above embodiments can solve the deficiencies and defects existing in the current need for multiple developments for similar requirements, and provide a management system capable of describing geographical information scenarios, which has the characteristics of clear process, time-saving, labor-saving, convenient maintenance, rapid update, etc., and can effectively improve work efficiency and meet the needs of displaying and calculating and analyzing various geographical information data.

[0110] In this embodiment, hierarchical management of geographical information data is realized by using a geographical information data hierarchical model. Among them, the geographical information data in the actual scenario is divided into three categories: system public data (i.e., public data), user private data (such as the user's static data), and scenario-specific data (i.e., the scenario description file corresponding to the scenario model). Among them, the system public data is provided by the GIS system; the user private data is uploaded by the user and can only be accessed by the user himself; in various usage scenarios, scenario-specific data can be generated based on the system public data and the user private data, that is, scenario data that conforms to the geographical information scenario description language specification.

[0111] The following details the data types stored in each layer of a data hierarchical model in a specific example:

[0112] One data layer of the data hierarchical model is the user private data layer, which stores the following types of data: map management data, road network data, terrain data, urban building data, water system data, vector data, regional division data, indoor map data, POI data, material data, data interface, BIM, CIM, device data, control interface.

[0113] Another data layer of the data hierarchical model is the system public data layer, also called the basic data and capability layer, which stores the following types of data: map basic data, three-dimensional terrain data, map perspective operation, map layer, map control, 3D tile hosting workflow, online map layer, vector data support, event engine, model support, GeoJSON support, POI interest point, map object, data visualization, video fusion, scene roaming, path planning, underground pipe network, urban white model, model monomerization, scene background skybox, weather effect, spatial analysis calculation, BIM model analysis, and virtual simulation.

[0114] Correspondingly, based on the user private data layer and the system public data layer, and combined with the spatio-temporal data configuration description, the above-mentioned scenario-specific data (i.e., the scenario description file corresponding to the scenario model) can be obtained. The scenario-specific data specifically includes the following types of data: map parameter configuration, overlay attributes (customizable), event triggering, data binding, visualization data, 3D models, interactive elements, navigation, perspective, story, chart, action, special effect, material reference.

[0115] In this embodiment, through a preset specification, also known as the Geographic Information Scene Description Language Specification, the generation and parsing operations of the scenario description file are implemented. This specification abstracts the geographic information scene into nine data types: basic layer, user map, road network, vector graphics, view, 3D model, event, special effect, and data visualization, and organizes them in the form of a json object. Each data type is a list, which includes data elements that can correspond to the corresponding ground objects on the map and describes their configurations in the form of a json object. If there is a need in the future, these nine data types can be extended to support more scenarios. After the user uses the visualization scene editor of the GIS system to save or export the scene data as a file, the scene data that conforms to this specification can be read by the scene parser of the GIS system and the geographic scene can be restored for display.

[0116] For example: To describe a three-dimensional object on the ground, the possible configuration is:

[0117]

[0118]

[0119]

[0120]

[0121]

[0122] In summary, in the scenario data generation process described in this embodiment, based on the geographic information data layering model and the scenario description language specification, the GIS system generates scenario description data according to the visual scenario configured by the user for the purpose of displaying the scenario. The specific process includes the following operations: perform hierarchical management on the geographic information data, perform unified abstract description on the GIS data used by the user, and form the Geographic Information Scene Description Language Specification. Use the industry cloud GIS system to visually edit the geographic information, generate the user GIS scenario description data and store it. When in use, obtain the scenario data using the scenario data identifier or import the scenario data using an offline file, so as to input the scenario data into the GIS system to restore the scenario.

[0123] Through the solution in this embodiment, it has at least the following beneficial effects: First, using the data layering model can effectively manage geographical information data, isolate user private data, reduce the amount of scenario data, and improve the loading speed. Second, hosting the static map data in the cloud achieves decentralized and on-demand loading, improves the loading and running speed, and optimizes the user experience. Third, standardizing the description of GIS scenarios, generating configurable data, and using the GIS system for unified management avoid the drawback of having to develop for each scenario and improve work efficiency. Finally, it provides a lightweight cloud scenario management solution and a scenario file management solution suitable for offline environments, which is applicable to both online and offline scenarios and multiple terminals, with stronger adaptability and can meet various usage scenarios. In addition, it provides a unified specification for describing geographical information scenarios, standardizes various scenario data, and makes it easier to manage.

[0124] Moreover, through the method of configuring events, this solution can implement various functions such as monitoring or prediction. This solution can load the scenario model in the GIS system into the business system and, combined with the characteristics of the business system, implement the monitoring or prediction function. Furthermore, it can query the auxiliary description information of elements in the business system by means of element extension data, and then add the content required in the business system to the scenario model of the GIS system in the form of element extension data, thus facilitating the use of the business system. Among them, the business system can be the digital twin city system mentioned above or various systems such as the population migration prediction system that need to cooperate with the GIS model.

[0125] Figure 5 The structure diagram of a management device for providing a scenario data according to another embodiment of the present disclosure is shown as Figure 5 shown, the management device includes:

[0126] A drawing module 51, configured to draw corresponding scenario elements through each element drawing entry included in the scenario editing interface, and the scenario editing interface includes a plurality of element drawing entries for drawing different types of scenario elements;

[0127] An acquisition module 52, configured to acquire user private data stored in the private storage space through the private data access entry in the scenario editing interface; acquire system public data stored in the public storage space through the public data access entry in the scenario editing interface;

[0128] An editing module 53, configured to edit each of the drawn scenario elements based on the acquired user private data and system public data to obtain a scenario model including a plurality of scenario elements;

[0129] A generation module 54, configured to, in response to a received scenario saving instruction, obtain the element attribute information of each scenario element included in the scenario model, generate a scenario description file corresponding to the element attribute information of each scenario element based on a preset specification, and store the scenario description file in the private storage space to be provided to a scenario parser for parsing and loading.

[0130] Optionally, the private storage space further includes: a plurality of user private spaces respectively corresponding to different users;

[0131] The obtaining module is specifically configured to: determine the user private space corresponding to the current user in the private storage space according to the user identifier, and obtain user private data from the user private space corresponding to the current user;

[0132] Moreover, the apparatus further includes:

[0133] An upload module, configured to, in response to a received private data upload request, obtain the user identifier and the user private data included in the private data upload request; store the user private data in the user private space corresponding to the user identifier in the private storage space.

[0134] Optionally, the apparatus further includes:

[0135] A configuration module, configured to, in response to a received event configuration request, determine the scenario element corresponding to the event configuration request, and configure a trigger event matching the event type included in the event configuration request for the scenario element.

[0136] Optionally, the configuration module is specifically configured to:

[0137] Configure an event interface for the scenario element, and bind the event association data corresponding to the trigger event to the event interface, so as to configure the event type of the trigger event through the event interface.

[0138] Optionally, the event type includes: a monitoring type and a prediction type; then the event association data corresponding to the trigger event includes at least one of the following: the monitoring object data, monitoring strategy data, and event response result data of the trigger event.

[0139] Optionally, the generation module is specifically configured to:

[0140] Respectively determine the element attribute information of each scenario element included in the scenario model, generate element description data corresponding to the element attribute information of the scenario element based on the preset specification, and generate the scenario description file according to the element description data;

[0141] Among them, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method.

[0142] Optionally, the scene saving instruction includes: a cloud saving instruction, and the generating module is specifically configured to:

[0143] Associate and store the scene description file with the scene identifier in the user private space of the cloud database through the cloud saving entry.

[0144] Optionally, the scene saving instruction includes: a local saving instruction, and the generating module is specifically configured to: export and store the scene description file to the user private space of the local database through the local saving entry.

[0145] Figure 6 The structural schematic diagram of a management device for scene data according to another embodiment of the present disclosure is shown, as Figure 6 shown, a management device for scene data includes:

[0146] An obtaining module 61, configured to obtain a scene description file corresponding to the received scene loading request in response to the received scene loading request;

[0147] An analysis module 62, configured to analyze the scene description file based on a preset specification to obtain the element attribute information of each scene element included in the scene model corresponding to the scene description file;

[0148] A loading module 63, configured to load and display the scene model based on the element attribute information of each scene element.

[0149] Optionally, the loading module is specifically configured to:

[0150] Obtain each scene element included in the scene model, determine the scene element configured with a trigger event as the target scene element, and generate a trigger event that matches the event type corresponding to the target scene element.

[0151] Optionally, the loading module is specifically configured to:

[0152] Determine the event interface configured for the target scene element, obtain the event association data bound to the event interface, and generate the trigger event according to the event association data.

[0153] Optionally, the event types include: monitoring type and prediction type. Then, the event-related data bound to the event interface includes at least one of the following: the monitoring object data of the triggering event, the monitoring policy data, and the event response result data.

[0154] Optionally, the parsing module is specifically configured to:

[0155] Obtain the element description data included in the scenario description file, and determine the element attribute information of each scenario element corresponding to the element description data based on a preset specification;

[0156] Wherein, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method.

[0157] For the specific structures and working principles of the above-mentioned various modules, reference can be made to the descriptions of the corresponding steps in the method embodiments, which will not be elaborated here.

[0158] In addition, Figure 5 The management device shown can be integrated into the GIS system. Figure 6 The management device shown can be integrated into either the GIS system or the business system. In addition, Figure 5 and Figure 6 The management devices in [[ ]] can also be integrated into the same management device and jointly set in the GIS system.

[0159] Referring to [[ ]], an embodiment of the present disclosure provides an electronic device, which includes: Figure 7 one or more processors 901;

[0160] a memory 902, on which one or more programs are stored. When the one or more programs are executed by the one or more processors, the one or more processors implement the management method of the scenario data according to any one of the above.

[0161] one or more I / O interfaces 903, connected between the processor and the memory, configured to implement information interaction between the processor and the memory.

[0162]

[0163] ​Among them, the processor 901 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 902 is a device with data storage capabilities, including but not limited to a random access memory (RAM, more specifically such as SDRAM, DDR, etc.), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory (FLASH); the I / O interface (read / write interface) 903 is connected between the processor 901 and the memory 902 and can realize the information interaction between the processor 901 and the memory 902, including but not limited to a data bus (Bus), etc.

[0164] In some embodiments, the processor 901, the memory 902, and the I / O interface 903 are interconnected through a bus and then connected to other components of the computing device.

[0165] This embodiment also provides a computer-readable medium, on which a computer program is stored. When the program is executed by the processor, it implements the management method of the scenario data provided in this embodiment. To avoid repeated description, the specific steps of the management method of the scenario data are not elaborated here.

[0166] Those of ordinary skill in the art will understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations. In the hardware implementation, the division between the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be executed by several physical components working together. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or can be implemented as hardware, or can be implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0167] It should be noted that, in this article, the term "including", "comprising", or any other variant thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or device that includes a series of elements not only includes those elements but also includes other elements that are not explicitly listed, or further includes elements that are inherent to such process, method, article, or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article, or device that includes such element.

[0168] It can be understood that the above embodiments are merely exemplary embodiments adopted to illustrate the principles of the present disclosure / invention, and the present disclosure / invention is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the present disclosure / invention, and these modifications and improvements are also considered within the protection scope of the present disclosure / invention.< / canvas>

Claims

1. A method for managing scenario data, comprising: Drawing corresponding scenario elements through respective element drawing entrances included in a scenario editing interface, where the scenario editing interface includes a plurality of element drawing entrances for drawing different types of scenario elements; Responding to an event configuration request received, determining a scenario element corresponding to the event configuration request, and configuring a trigger event matching the event type included in the event configuration request for the scenario element; Obtaining user private data stored in a private storage space through a private data access entrance in the scenario editing interface; Obtaining system public data stored in a public storage space through a public data access entrance in the scenario editing interface; Based on the obtained user private data and system public data, editing each of the drawn scenario elements to obtain a scenario model including a plurality of scenario elements; Responding to a scenario save instruction received, obtaining element attribute information of each scenario element included in the scenario model, generating a scenario description file corresponding to the element attribute information of each scenario element based on a preset specification, and storing the scenario description file in the private storage space for parsing and loading by a scenario parser.

2. The method according to claim 1, wherein The private storage space further includes: a plurality of user private spaces respectively corresponding to different users; The obtaining user private data stored in a private storage space through a private data access entrance in the scenario editing interface includes: determining a user private space corresponding to the current user in the private storage space according to a user identifier, and obtaining user private data from the user private space corresponding to the current user; And, before the drawing corresponding scenario elements through respective element drawing entrances included in the scenario editing interface, further includes: responding to a private data upload request received, obtaining the user identifier and user private data included in the private data upload request; storing the user private data in the user private space corresponding to the user identifier in the private storage space.

3. The method according to claim 1, wherein The configuring a trigger event matching the event type included in the event configuration request for the scenario element includes: Configuring an event interface for the scenario element, and binding event associated data corresponding to the trigger event to the event interface to configure the event type of the trigger event through the event interface.

4. The method according to claim 3, wherein The event type includes: a monitoring type and a prediction type; then the event associated data corresponding to the trigger event includes at least one of the following: monitoring object data of the trigger event, monitoring policy data, and event response result data.

5. The method according to claim 1, wherein, Before the drawing corresponding scenario elements through respective element drawing entrances included in the scenario editing interface, further includes: responding to a scenario creation request received, generating a scenario identifier, and creating scenario framework data; Then the drawing corresponding scenario elements through respective element drawing entrances included in the scenario editing interface includes: drawing the scenario elements based on the scenario framework data.

6. The method according to claim 5, wherein In response to the received scenario saving instruction, obtaining the element attribute information of each scenario element included in the scenario model, and generating a scenario description file corresponding to the element attribute information of each scenario element based on a preset specification includes: Determining the element attribute information of each scenario element included in the scenario model respectively, generating element description data corresponding to the element attribute information of the scenario element based on the preset specification, and generating the scenario description file according to the element description data; Wherein, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method.

7. The method according to claim 6, wherein, If the scenario saving instruction includes: a cloud saving instruction, then storing the scenario description file in the private storage space includes: Associating and storing the scenario description file with a scenario identifier in the user private space of the cloud database through the cloud saving entry.

8. The method according to claim 6, wherein, If the scenario saving instruction includes: a local saving instruction, then storing the scenario description file in the private storage space includes: exporting and storing the scenario description file to the user private space of the local database through the local saving entry.

9. A method for managing scenario data, which includes: In response to the received scenario loading request, obtaining a scenario description file corresponding to the scenario loading request; wherein, the scenario description file is generated based on any one of the methods recited in claims 1-8; Parsing the scenario description file based on a preset specification to obtain the element attribute information of each scenario element included in the scenario model corresponding to the scenario description file; Loading and displaying the scenario model based on the element attribute information of each scenario element.

10. The method according to claim 9, wherein, The loading and displaying the scenario model includes: Obtaining each scenario element included in the scenario model, determining the scenario element configured with a trigger event as a target scenario element, and generating a trigger event matching the event type corresponding to the target scenario element.

11. The method according to claim 10, wherein, The determining the scenario element configured with a trigger event as a target scenario element and generating a trigger event matching the event type corresponding to the target scenario element includes: Determining the event interface configured for the target scenario element, obtaining the event association data bound to the event interface, and generating the trigger event according to the event association data.

12. The method according to claim 11, wherein If the event type includes: a monitoring type and a prediction type, then the event association data bound to the event interface includes at least one of the following: the monitoring object data of the trigger event, monitoring strategy data, and event response result data.

13. The method according to claim 9, wherein The parsing the scenario description file based on a preset specification to obtain the element attribute information of each scenario element included in the scenario model corresponding to the scenario description file includes: Obtaining the element description data included in the scenario description file, and determining the element attribute information of each scenario element corresponding to the element description data based on a preset specification; Among them, the element attribute information includes at least one of the following: element identifier, element type, element size, element orientation, element extension data, and element loading method.

14. The method according to claim 9, wherein The scene loading request includes: a cloud loading request. Then, in response to the received scene loading request, obtaining the scene description file corresponding to the scene loading request includes: obtaining the scene identifier included in the scene loading request, and obtaining the scene description file corresponding to the scene identifier from the cloud database based on the scene identifier.

15. The method according to claim 9, wherein The scene loading request includes: a local loading request. Then, in response to the received scene loading request, obtaining the scene description file corresponding to the scene loading request includes: obtaining the scene description file corresponding to the scene identifier stored locally according to the scene identifier included in the scene loading request.

16. The method according to any one of claims 9-15, wherein, The method is executed by a GIS system, or the method is executed by a business system capable of communicating with the GIS system; Moreover, the parsing the scene description file based on a preset specification to obtain the element attribute information of each scene element included in the scene model corresponding to the scene description file includes: Parsing the scene description file through a scene parser set in the business system to obtain a scene model corresponding to the scene description file.

17. A management device for scene data, which includes: A drawing module, configured to draw corresponding scene elements through each element drawing entry included in the scene editing interface, and the scene editing interface includes a plurality of element drawing entries for drawing different types of scene elements; An obtaining module, configured to obtain user private data stored in a private storage space through a private data access entry in the scene editing interface; Obtaining system public data stored in a public storage space through a public data access entry in the scene editing interface; An editing module, configured to edit each drawn scene element based on the obtained user private data and system public data to obtain a scene model including a plurality of scene elements; A generating module, configured to, in response to a received scene saving instruction, obtain the element attribute information of each scene element included in the scene model, generate a scene description file corresponding to the element attribute information of each scene element based on a preset specification, and store the scene description file in the private storage space for parsing and loading by a scene parser.

18. A management device for scene data, which includes: An obtaining module, configured to obtain a scene description file corresponding to the received scene loading request; wherein, the scene description file is generated based on the management device for scene data according to claim 17; A parsing module, configured to parse the scene description file based on a preset specification to obtain the element attribute information of each scene element included in the scene model corresponding to the scene description file; A loading module, configured to load and display the scene model based on the element attribute information of each scene element.

19. An electronic device, which includes: One or more processors; A storage device storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method according to any one of claims 1-9 or claims 9-16; One or more I / O interfaces connected between the processor and the memory and configured to enable information interaction between the processor and the memory.

20. A computer-readable medium storing a computer program which, when executed by a processor, implements the method according to any one of claims 1-8 or claims 9-16.

Images