A visual configuration system construction method and platform of GIS

Abstract

The application discloses a visual configuration type system construction method and platform of GIS, relates to the application technical field of geographic information system, and solves the problems of system structure solidification, complex configuration, difficult expansion, and difficult unified management of multi-map collaborative display and component linkage of existing GIS systems; the application comprises the following steps: configuring a platform structure, a page layout, a function module, a map component and a map layer of a GIS system through a visual configuration mode, generating structured configuration data, and dynamically constructing a page structure and a business function module of the GIS system during system operation; based on the structured configuration data, a map component instance is uniformly managed; through an event response mechanism between components, spatial linkage display between the multiple map instances is realized; through configuration of business metadata for the map layer, unified management and linkage control of the map layer are realized; and the application reduces dependence on a hard coding mode and reduces system customization and adjustment cost.

Description

Technical Field

[0001] This invention relates to the field of geographic information system application technology, specifically to a method and platform for constructing a GIS visual configuration system. Background Technology

[0002] In the development and application of general geographic information systems (GIS), the system's construction typically relies on direct program code implementation to define the page structure, functional modules, and map display logic. This results in a fixed overall system architecture from the initial development stage. When application scenarios or business logic need to be changed, extensive code rewriting or structural adjustments to the page layout, functional combinations, and map logic are often necessary, leading to high costs for customized development and subsequent expansion.

[0003] To improve code reusability, some systems have adopted a component-based design approach. However, the composition relationships and linkage logic between components still heavily rely on manual coding by developers, resulting in complex and inflexible configuration processes. In application scenarios requiring the integration of multiple map instances on a single page, spatial linkage between map views, such as synchronized zooming, panning, highlighting, and collaborative responses between the map and business function components like sidebars and charts, typically require customized development for specific needs. Currently, there is a lack of a unified mechanism to effectively manage these instances and configure their interactive behaviors. Furthermore, the visualization rendering logic of map layers is tightly coupled with their inherent business attributes, making centralized management of layers, unified style configuration, and cross-layer linkage control difficult to achieve. This further increases the complexity of system maintenance and the difficulty of functional expansion. Therefore, existing technologies still have significant limitations in achieving system configuration flexibility, supporting multi-view collaborative interaction, and promoting loosely coupled linkage between components. Summary of the Invention

[0004] To address the problems existing in the prior art, this invention provides a method and platform for constructing a visually configurable GIS system, which solves the common problems in existing GIS systems such as rigid system structure, complex configuration, difficulty in expansion, and difficulty in unified management of multi-map collaborative display and component linkage.

[0005] A method for building a GIS-oriented visual configuration system includes the following steps:

[0006] S1. Configure the platform structure, page layout, functional modules, map components and map layers of the GIS system through visual configuration to generate structured configuration data;

[0007] S2. Based on the structured configuration data, dynamically construct the page structure and business function modules of the GIS system during system operation;

[0008] S3. Based on the structured configuration data, map component instances are managed in a unified manner, and multiple map instances are created and run on the same page;

[0009] S4. Through the event response mechanism between components, the spatial linkage display between the multiple map instances and the collaborative response between the map component and other business components are realized;

[0010] S5. By configuring business metadata for map layers, unified management and linkage control of map layers can be achieved.

[0011] Furthermore, the visual configuration method includes dragging, combining, and configuring parameters of page layout, functional modules, and map components through a graphical editing interface. The parameters include, but are not limited to, component attributes, data source binding relationships, and event response rules.

[0012] Furthermore, the dynamic construction refers to the system running and rendering module parsing and executing the structured configuration data during system runtime to instantly generate page structures, load functional components, and initialize their states, without relying on pre-compiled fixed page code.

[0013] Furthermore, the multiple map instances are distinguished by unique identifiers on the same page, and are uniformly scheduled and maintained by the map component management module; each instance can independently load different base map services and display layers.

[0014] Furthermore, the spatial linkage includes automatically driving other associated map instances to synchronously update their display range, viewpoint, or highlight status through the event bus of the linkage control module when any map instance undergoes a viewpoint change, range zoom, or element selection interaction.

[0015] Furthermore, the collaborative response between the map component and other business components includes: the map component encapsulates user interaction events into standard messages and publishes them to the event bus; business components that subscribe to the messages automatically trigger preset business logic and update their display content; the operation results of the business components can also be fed back to the map component through the event bus, triggering corresponding updates to the map state.

[0016] Furthermore, the layer business metadata is structured descriptive information attached to the map layer, including the layer's unique identifier, business classification code, visualization rendering rules, interactivity switch, the identifier of the layer group to which it belongs, and association rules with other components. The metadata is used to realize batch control of layers, linkage between visible and hidden elements, and unified style switching.

[0017] A GIS-oriented visual configuration-based system construction platform, comprising:

[0018] The visual configuration module is used to graphically configure the page structure, functional modules, and map components of the GIS system.

[0019] A configuration data management module is used to store and manage the structured configuration data generated by the visualization configuration module;

[0020] The system operation and rendering module is used to dynamically construct and render system pages and business functions during system operation based on the structured configuration data.

[0021] The map component management module is used to perform unified creation, registration, and lifecycle management of multiple map component instances based on the structured configuration data.

[0022] The linkage control module is used to realize spatial linkage between multiple map instances and collaborative response between map components and business components through the event response mechanism between components;

[0023] The layer management module is used to manage and control map layers in a unified manner based on the business metadata configured for the map layers.

[0024] The beneficial effects of this invention include:

[0025] The visual configuration method and component-based dynamic construction mechanism designed in this invention change the reliance on hard-coding, enabling the system's page structure and functional module combination to be flexibly configured and adjusted according to actual needs. This greatly reduces the system's customized development cost and later maintenance difficulty, and improves the reusability of functional modules and the adaptability of the system.

[0026] This invention establishes a unified management, event response, and collaboration mechanism for map component instances and business components, and introduces layer metadata that carries business attributes. This effectively realizes efficient spatial linkage of multiple map views within a single page, deep interaction between maps and business logic, and centralized intelligent control of layers, thereby comprehensively enhancing the system's interactive experience, business linkage display capabilities, and overall maintainability. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating a GIS-oriented visual configuration system construction method according to an embodiment of this application. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0029] A GIS-oriented visual configuration-based system construction platform, comprising:

[0030] The visual configuration module is used to graphically configure the page structure, functional modules, and map components of the GIS system.

[0031] To support visual configuration and drag-and-drop assembly of components in the low-code platform, a metadata-driven component description mechanism has been introduced. Components must provide a structured metadata file during registration, providing a unified description of the component's basic attributes, parameters, slots, styles, and editable items.

[0032] Metadata not only defines the default runtime parameters of a component, but also describes how the component is configured and interacts in a low-code editor. This allows business users to configure component parameters and build interfaces through a graphical interface without writing code. Through this metadata mechanism, the technical implementation of a component is decoupled from its business configuration, improving system customization capabilities and business response speed.

[0033] This embodiment addresses the diversity and complexity of maps and interactions in meteorological operations by encapsulating the VmMap map component based on maplibre-gl and providing multi-map management capabilities using useVueMaplibre and CtWidgetMap. Each map is managed through a unique containerId, allowing the system to retrieve the currently active map or all map instances, supporting independent operations in multi-map scenarios.

[0034] The configuration data management module is used to store and manage the structured configuration data generated by the visualization configuration module.

[0035] The system operation and rendering module is used to dynamically construct and render system pages and business functions during system operation based on the structured configuration data.

[0036] The map component management module is used to perform unified creation, registration, and lifecycle management of multiple map component instances based on the structured configuration data.

[0037] The linkage control module is used to achieve spatial linkage between multiple map instances and coordinated response between map components and business components through the event response mechanism among components;

[0038] In terms of event response, the platform adopts the lightweight and high-performance global event bus vmMitt, which supports system-level, business-level, and component-level events. Events such as timeline changes, map operations, and table row clicks are all broadcast through vmMitt to achieve cross-component and cross-level linkage. For example, global timeline events trigger precipitation, radar, lightning, site data, and multi-map synchronous refresh, realizing the dynamic response ability of business data visualization.

[0039] The layer management module is used to uniformly manage and linkage-control map layers based on the business metadata configured for the map layers. By reading the layer metadata to construct a business attribute tree, it realizes the control of legend, visibility, transparency, label, and colormap switching, uniformly manages the life cycles of style-layer and custom-layer, and separates rendering from the business layer.

[0040] The platform also includes a component repository for managing components and their metadata, including component registration and component version management.

[0041] This mechanism effectively reduces the development costs of system function expansion and business adjustment, enabling the same set of components to support the different business requirements of different levels and positions in provinces, cities, and counties.

[0042] In another embodiment, it relates to a method for constructing a visualization configuration system for GIS, as Figure 1 shown, including the following steps:

[0043] Drag, combine, and configure parameters for the platform structure, page layout, functional modules, map components, and map layers of the GIS system through the graphical editing interface of the visualization configuration module, and generate structured configuration data to be saved in the configuration data management module; the parameters include but are not limited to component attributes, data source binding relationships, and event response rules.

[0044] Call the structured configuration data from the configuration data management module, and use the system operation and rendering module to dynamically construct the page structure and business functional modules of the GIS system during system operation; the dynamic construction means that during system operation, parse and execute the structured configuration data, instantaneously generate the page structure, load functional components, and initialize their states, without relying on pre-compiled fixed page code.

[0045] The map component management module uniformly manages map component instances based on the structured configuration data, creates and runs multiple map instances on the same page; the linkage control module executes the event response mechanism between components to achieve spatial linkage display between the multiple map instances and collaborative response between the map component and other business components;

[0046] The event response mechanism is built based on a unified event bus, adopts a publish-subscribe communication mode, and each map component instance and business component is connected to the event bus as an event node; when any component generates an interaction operation or a state change, the operation is encapsulated as a standard event message and published to the event bus; the event bus matches, schedules, and routes the standard event message according to the preset subscription relationship and linkage rules, and the component that receives the standard event message automatically executes corresponding spatial view synchronization, business logic trigger, or state feedback operations according to the event content, so as to achieve collaborative linkage control between multiple map instances and across components. The preset subscription relationship and linkage rules are the basis for the event bus to perform message routing and collaborative control; among them, the preset subscription relationship defines the event types and corresponding filtering conditions that each component instance is interested in, and the linkage rules further specify the specific actions that the subscribed component should execute when a matching event occurs, including action types, parameter mapping, and execution modes; both are defined during the system visualization configuration stage and persisted as structured configuration data, enabling components to achieve collaborative linkage control of multiple map instances and across components on demand and precisely.

[0047] The spatial linkage display includes that when any map instance undergoes a perspective change, range zoom, or primitive selection interaction, the linkage control of the event response mechanism automatically drives other associated map instances to synchronously update their display ranges, perspectives, or highlight states.

[0048] The multiple map instances are distinguished by unique identifiers on the same page and are uniformly scheduled and state-maintained by the map component management module; each instance can independently load different base map services and display layers.

[0049] The collaborative response between the map component and other business components includes: the map component encapsulates the user's interaction events as standard messages and publishes them to the event bus, and the business component that subscribes to the message automatically triggers the preset business logic and updates its display content; the operation results of the business component can also be fed back to the map component through the event bus, triggering corresponding updates to the map state. S5. By configuring business metadata for the map layer, unified management and linkage control of the map layer are achieved. The other business components refer to various non-map visualization and interaction modules related to GIS business functions except the map component, including data statistics and visualization components, table and list components, form and query components, information display components, and business function components.

[0050] The data statistics and visualization components include bar charts, pie charts, line charts, heat maps, etc., used to display statistical data related to selected points or regions on the map.

[0051] The table and list components include an attribute table and a query result list, which are used to display detailed attribute information of map features.

[0052] The form and query components include condition filtering and spatial query input boxes, which are used to construct query conditions and drive map updates.

[0053] The information display components include pop-ups, sidebars, legends, and scale bars, used to present map interaction results or supplementary explanations.

[0054] The business function components include an analysis tool panel and a task flow console, which are used to trigger spatial analysis or business processing logic.

[0055] The layer business metadata is a structured descriptive information attached to the map layer, including the layer's unique identifier, business classification code, visualization rendering rules, interactivity switch, the identifier of the layer group to which it belongs, and the association rules with other components. The layer management module uses this metadata to realize batch control of layers, linkage between display and hiding, and unified style switching.

[0056] Specifically, this embodiment takes the construction of a numerical weather prediction model product browsing system as an example to illustrate the implementation process of the method of the present invention, and the specific steps are as follows.

[0057] Step 1: Visual Configuration Steps

[0058] The system provides a visual configuration platform, and the system pages are configured using a graphical editing interface, including:

[0059] 1) Add a map component by dragging and dropping in the page layout area;

[0060] 2) Add a numerical weather prediction mode product browsing component by dragging and dropping;

[0061] 3) Arrange the map component and the numerical weather prediction model product browsing component on the same page to form the initial page structure;

[0062] 4) Save the above configuration results as structured configuration data.

[0063] Step 2: Component Property Configuration Steps:

[0064] After adding the components, configure the attribute parameters of each component, specifically including:

[0065] 1) Configure the map component's properties and set its display mode to 2×2 split-screen mode so that the system can automatically generate four map instances;

[0066] 2) Assign a unique instance identifier to each map instance;

[0067] 3) Configure the attributes of the numerical weather prediction model product browsing component and preset the selectable numerical weather prediction model types, including but not limited to EC, GRAPES-3KM, GRAPES-9KM, SHANGHAI-3KM, SHANGHAI-9KM, JAPAN, GERMANY, etc.

[0068] 4) Configure optional meteorological element types, including physical quantity elements such as altitude layer, wind field, sea level pressure field, temperature, precipitation, humidity, and visibility;

[0069] 5) Users can select the mode type and meteorological elements to be displayed by checking boxes;

[0070] 6) Write the above component attribute information into the structured configuration data.

[0071] Step 3: System Operation and Dynamic Rendering Steps:

[0072] After the system starts up, the system operation and rendering module performs the following operations based on the structured configuration data:

[0073] 1) Parse the page layout configuration data;

[0074] 2) Dynamically generate page structure;

[0075] 3) Load the map component and the numerical weather prediction model product browsing component;

[0076] 4) Initialize the running status of each component;

[0077] 5) Complete the real-time rendering and display of the system pages.

[0078] The above method enables the dynamic construction of system pages and business functions without the need to pre-compile fixed page code.

[0079] Step 4: Map Component Instance Management Steps

[0080] The system manages multiple map instances in a unified manner through the map component management module, which specifically includes:

[0081] 1) Based on the structured configuration data, automatically create four map instances;

[0082] 2) Register and manage each map instance, and establish instance index relationships;

[0083] 3) Maintain the lifecycle status of each map instance, including initialization, running, and destruction statuses;

[0084] 4) Unify the scheduling of resource loading, view updates and interactive responses for each map instance.

[0085] Step 5: Linkage Control and Coordinated Response Steps:

[0086] The system achieves collaborative linkage between multiple components through a linkage control module based on an event response mechanism, specifically including:

[0087] (a) Spatial linkage between map instances

[0088] 1) Establish a default view linkage relationship for the four map instances;

[0089] 2) When any map instance undergoes zooming, panning, or viewpoint change operations, a corresponding map interaction event is generated;

[0090] 3) Encapsulate the map interaction events and publish them to the event bus;

[0091] 4) The event bus distributes the events to other associated map instances;

[0092] 5) Other map instances will update their display range and zoom level synchronously based on the event content.

[0093] (ii) Collaborative Response Between Map Components and Business Components

[0094] 1) When a user clicks the mode or feature selection button in the numerical weather prediction model product browsing component, a business operation event is generated;

[0095] 2) Publish the aforementioned business operation events to the event bus;

[0096] 3) The currently active map instance subscribes to and receives the aforementioned business operation events;

[0097] 4) The map instance loads and displays the corresponding numerical forecast product layer based on the event parameters;

[0098] 5) Complete the dynamic display of numerical weather prediction products in the target map instance.

[0099] Step Six: Layer Management and Status Synchronization Steps:

[0100] The system achieves unified management and status synchronization of layers through a layer management module, specifically including:

[0101] 1) When a map instance loads or removes a numerical weather prediction product layer, a layer change event is automatically triggered;

[0102] 2) The layer management module receives the layer change event and updates the layer list information;

[0103] 3) When a user performs a layer removal or show / hide operation in the layer management module, a layer control event is generated;

[0104] 4) Publish the layer control events to the event bus;

[0105] 5) The corresponding map instance receives the layer control event and performs the layer show or hide operation;

[0106] 6) The synchronized update button of the product browsing component in numerical weather prediction mode is highlighted to reflect the current layer loading status.

[0107] Through the above embodiments, the present invention has at least the following technical effects:

[0108] 1) Enable rapid and visual construction of GIS system pages and business functions;

[0109] 2) Supports unified management and synchronized display of multiple map instances;

[0110] 3) Enable flexible loading and dynamic switching of numerical weather prediction products;

[0111] 4) Improve the system's scalability and maintainability;

[0112] 5) Reduce system development and deployment costs.

[0113] The embodiments described above merely illustrate specific implementation methods of this application, and while the descriptions are detailed and specific, they should not be construed as limiting the scope of protection of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the technical solution of this application, and these modifications and improvements all fall within the scope of protection of this application.

Claims

1. A method for constructing a GIS-oriented visual configuration system, characterized in that, Includes the following steps: S1. Configure the platform structure, page layout, functional modules, map components and map layers of the GIS system through visual configuration to generate structured configuration data; S2. Based on the structured configuration data, dynamically construct the page structure and business function modules of the GIS system during system operation; S3. Based on the structured configuration data, map component instances are managed in a unified manner, and multiple map instances are created and run on the same page; S4. Through the event response mechanism between components, the spatial linkage display between the multiple map instances and the collaborative response between the map component and other business components are realized; S5. By configuring business metadata for map layers, unified management and linkage control of map layers can be achieved.

2. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, The visual configuration method in S1 includes dragging, combining, and configuring parameters of page layout, functional modules, and map components through a graphical editing interface. The parameters include, but are not limited to, component attributes, data source binding relationships, and event response rules.

3. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, In S2, dynamic construction refers to the system running and rendering module parsing and executing the structured configuration data during system runtime to instantly generate page structure, load functional components, and initialize their states, without relying on pre-compiled fixed page code.

4. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, In S4, multiple map instances are distinguished by a unique identifier on the same page, and are uniformly scheduled and maintained by the map component management module; each instance can independently load different base map services and display layers.

5. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, The spatial linkage in S4 includes automatically driving other associated map instances to synchronously update their display range, viewpoint, or highlight status through the event bus of the linkage control module when any map instance undergoes a viewpoint change, range zoom, or element selection interaction.

6. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, The collaborative response between the map component and other business components in S4 includes: the map component encapsulates user interaction events into standard messages and publishes them to the event bus; business components that subscribe to the messages automatically trigger preset business logic and update their display content; the operation results of business components can also be fed back to the map component through the event bus, triggering corresponding updates to the map state.

7. The method for constructing a GIS-oriented visual configuration system according to claim 1, characterized in that, The business metadata is a structured descriptive information attached to the map layer, including the layer's unique identifier, business classification code, visualization rendering rules, interactivity switch, the identifier of the layer group to which it belongs, and the association rules with other components. The layer management module uses this metadata to realize batch control of layers, linkage between display and hiding, and unified style switching.

8. A GIS-oriented visual configuration system construction platform, characterized in that, include: The visual configuration module is used to graphically configure the page structure, functional modules, and map components of the GIS system. A configuration data management module is used to store and manage the structured configuration data generated by the visualization configuration module; The system operation and rendering module is used to dynamically construct and render system pages and business functions during system operation based on the structured configuration data. The map component management module is used to perform unified creation, registration, and lifecycle management of multiple map component instances based on the structured configuration data. The linkage control module is used to realize spatial linkage between multiple map instances and collaborative response between map components and business components through the event response mechanism between components; The layer management module is used to manage and control map layers in a unified manner based on the business metadata configured for the map layers.

Images