A method and system for big data visualization configuration

By integrating background management, style management, chart management, and scene management modules through a big data visualization configuration method and system, the high technical threshold and fragmented data processing problems of traditional big data visualization are solved. This enables rapid configuration and data consistency for non-technical personnel, reduces system maintenance costs, and adapts to the rapid iteration needs of the tourism industry.

CN120909572BActive Publication Date: 2025-12-09浙江云野科技有限公司
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202511457519.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-10-13
Publication Date
2025-12-09
Estimated Expiration
2045-10-13

AI Technical Summary

Technical Problem

Traditional big data visualization practices face multiple technical hurdles, requiring developers to write a large amount of code, involving professional work such as data interface development, chart rendering logic, and front-end interaction design. This makes it difficult to cover the needs of non-technical users, and the requirements for visualization forms vary significantly across different scenarios, resulting in a long cycle from requirements communication to solution implementation. Preprocessing operations such as data cleaning and aggregation rely on external data engineers, which can easily lead to inconsistencies in data interpretation.

Method used

This paper provides a big data visualization configuration method and system. It receives editing instructions from the tourism data interface of the interaction layer, parses and determines the type of adjustment instruction, calls the backend service module to extract template data, and provides feedback materials to achieve visualization configuration. It builds a standardized third-party interface adaptation layer, integrates background management, style management, chart management, scene management and template management modules, supports personalized visual customization and rapid switching of multiple business scenarios, and combines display preview and publishing functions to reduce the technical threshold and ensure data consistency.

Benefits of technology

Business personnel can efficiently configure the tourism data interface without writing code, reducing the technical threshold by more than 80%, shortening the demand response cycle from several weeks to 1-2 days, ensuring seamless data flow, improving data consistency by 90%, reducing system maintenance costs by 60%, and adapting to the rapid iteration needs of the business.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120909572B_ABST
    Figure CN120909572B_ABST
Patent Text Reader

Abstract

The application relates to the technical field of digital data processing, and discloses a big data visualization configuration method and system. Business personnel can efficiently and independently configure a tourism data interface, the technical threshold is reduced by more than 80%, the business personnel can complete full-process operation from data access to scene release through a no-code interface, the demand response cycle is greatly shortened, the period from demand submission to scene online is compressed from several weeks to 1 to 2 days, temporary data analysis demand can realize efficient configuration of the tourism data interface through template reuse and rapid configuration, the real-time performance of supporting business decision-making is improved, the system maintenance cost is significantly reduced, the modularization and decoupling design reduces the single-module modification cost by more than 60%, when a new chart type is added, a style is adjusted or a third-party interface is updated, full-amount reconstruction code is not needed, and the maintenance cost linearly grows with the scene complexity instead of exponentially.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The application relates to a big data visualization configuration method and system, and belongs to the technical field of digital data processing. BACKGROUND

[0002] With the deep penetration of digital economy, big data technology has become the core support for enterprise decision-making, business monitoring and trend prediction. Through graphical methods, complex data is converted into intuitive and easy-to-understand charts and dashboards, helping decision-makers quickly capture key information.

[0003] Traditional big data visualization practice faces multiple technical thresholds, and developers need to write a large amount of code, involving data interface development, chart rendering logic, front-end interaction design and other professional work.

[0004] Different scenarios have significant differences in visualization form requirements, and users need to have certain data modeling and tool operation experience, which is difficult to cover the use requirements of non-technical personnel. From demand communication to scheme landing, the average cycle is as long as several weeks, which cannot adapt to the rapid iteration rhythm of business, especially in response to temporary data analysis requirements.

[0005] Data cleaning, aggregation and other preprocessing operations need to rely on external data engineers to complete, and the visualization configuration and data processing links are fragmented, which is prone to data inconsistency problems.

[0006] Therefore, it is necessary to propose a big data visualization configuration method and system to solve the problem that traditional big data visualization technology cannot realize efficient and accurate data graphical. SUMMARY

[0007] The application provides a big data visualization configuration method and system, which can solve the problems of multiple technical thresholds in big data visualization practice, significant differences in visualization form requirements in different scenarios, and fragmentation of visualization configuration and data processing links.

[0008] The application provides a big data visualization configuration method, which comprises the following steps:

[0009] Receiving a tourism data interface editing instruction of an interaction layer;

[0010] Analyzing the tourism data interface editing instruction of the interaction layer to obtain an adjustment instruction; the adjustment instruction comprises one or more of a front-end interaction layer instruction, a management business layer instruction, a data support layer instruction, and an external integration layer instruction;

[0011] Based on the core business management logic algorithm, it is judged whether the adjustment instruction belongs to the external integration layer instruction;

[0012] If the adjustment instruction does not belong to the external integration layer instruction, the tourism data interface editing instruction of the interaction layer is fed back to the data support layer;

[0013] Based on the tourism data interface editing instructions, the core business management logic algorithm process support script, call the back-end service module, extract the template data connected to the database;

[0014] The feedback of the tourism data interface editing instructions corresponds to the picture material, table material and chart material to realize the visualization configuration of the tourism data interface;

[0015] If the adjustment instruction belongs to the external integration layer instruction, a standardized third-party interface adaptation layer is constructed to call the third-party database;

[0016] The third-party database is included in the core business management logic algorithm to generate one or more save templates;

[0017] Extract the picture material, table material and chart material in the save template that meets the tourism data interface editing instructions to realize the visualization configuration of the tourism data interface.

[0018] Specifically, at the function level, the big data visualization configuration method can realize personalized visual customization through background management and display style management, support tourism scene visual expression, provide rich chart type selection and fine style configuration through display chart management and chart component attribute management, adapt to different tourism data dimension display requirements, realize multi-business scene classification management and quick switching through display scene management, such as scenic spot operation monitoring, tourism market analysis, passenger flow early warning, etc., rely on chart data management to complete data cleaning, association and update maintenance, and guarantee data caliber consistency; combined with the display preview function and the display publishing function, support real-time viewing and one-key publishing of configuration effect, greatly shorten the period from demand to landing, reduce the technical barriers for business personnel to participate in configuration through modular architecture design, adapt to tourism business rapid iteration requirements through flexible style and scene management, reduce the maintenance cost in the later period through standardized data interface and component design, and finally provide efficient, professional and easy-to-use big data visualization solutions for the tourism industry, helping tourism enterprises to drive business decision-making and operation optimization through data visualization.

[0019] It can be understood that the front-end interaction layer instruction is used to drive the front-end interaction layer, which is a modular interaction entrance. The management business layer instruction is used to drive the core business layer, which realizes module cooperation and logic processing with a dependency relationship as the link. The data support layer instruction is used to drive the data support layer, which undertakes the storage and flow of system data. The external integration layer instruction is used to drive the external integration layer, which provides functional expansion support for the attribute management module and breaks the system capability boundary.

[0020] Further, background color gradient, gradient parameter settings, picture material import, transparency dynamic adjustment are included in the architecture branch of background editing management;

[0021] The main auxiliary color value definition, font family adaptation, spacing rule configuration, and border shadow parameter adjustment are included in the architecture branch of style editing management;

[0022] The chart type switching, data dimension mapping, coordinate axis scale customization, and legend interactive configuration are included in the architecture branch of chart editing management to realize the data visualization interface editing based on non-single type chart engine;

[0023] Based on the terminal adaptation rule preset script, component level adjustment script, and responsive layout parameter configuration script, the scene editing management architecture branch is formed;

[0024] The basic editing module of the tourism data interface is constructed; the basic editing module includes one or more basic editing architectures of background editing management, style editing management, chart editing management, scene editing management, and template editing management.

[0025] Specifically, as the core hub of the front-end visualization editing system, the module integrates background management, style management, chart management, scene management, and template management in an integrated architecture to build a creation and editing capability hub covering the whole life cycle of visual content. In terms of function landing, the five basic modules have their own focuses: the background management module supports background color gradient, gradient parameter settings, picture material import, and transparency dynamic adjustment to realize fine control of the canvas base style. The style management module focuses on the theme system building, covering main auxiliary color value definition, font family adaptation, spacing rule configuration, and border shadow parameter adjustment to ensure the visual uniformity of the visualization content. The chart management module integrates multiple types of chart engines to provide chart type switching, data dimension mapping, coordinate axis scale customization, legend interactive configuration, and other depth editing functions to meet the diversified expression needs of data visualization. The scene management module is responsible for scene layout scheme storage and switching, supporting multi-terminal adaptation rule preset, component level adjustment, and responsive layout parameter configuration. The template management module realizes the storage, classification, version control, and one-key reuse function of standardized templates, greatly improving the content creation efficiency. The core module deeply depends on the attribute management module in the core business layer of the front-end architecture, and realizes the precise landing of personalized configurations such as background style parameters, chart interactive attributes, and scene layout rules by calling the dynamic attribute configuration engine, style rule verification interface, and real-time configuration synchronization capability provided by the attribute management module. The unified attribute dictionary and configuration schema provided by the attribute management module ensure the consistency and compatibility of the configuration items of each functional module, and the configuration change real-time push mechanism supported by the attribute management module ensures the immediate feedback of style and data in the visualization editing process, providing users with a smooth and efficient editing experience.

[0026] Further, receive the input instruction of the client;

[0027] Based on the input instruction, determine whether the input instruction of the client calls the basic editing module;

[0028] If the client calls the basic editing module, parse the input instruction of the client to generate the travel data interface editing instruction;

[0029] If the client does not call the basic editing module, determine that the input instruction of the client calls the auxiliary function module of the interaction layer;

[0030] Parse the input instruction of the client;

[0031] Obtain the establishment instruction of the travel data interface editing project;

[0032] Find the target editing template of the establishment instruction in the auxiliary function module;

[0033] Based on the establishment instruction of the travel data interface editing project, generate the travel data interface editing instruction for the target editing template.

[0034] Specifically, in the case that the client calls the basic editing module, the travel data interface editing instruction can be generated by using the basic editing module. The basic editing module serves as the source of content creation and provides basic creation capabilities such as rich text editing, format layout, and multimedia insertion. The structured content data generated by the basic editing module will serve as the core data source of the whole process and provide accurate input for subsequent modules.

[0035] In the case that the client does not call the basic editing module, the travel data interface editing instruction can be generated by using the project management module of the auxiliary function module. The project management module serves as the core support module of the front-end system and undertakes the important responsibilities of whole-process project life cycle management and basic technical support. This module deeply integrates the project full-link function and provides complete management capabilities for users from project initialization to termination. At the same time, it builds a unified technical base to support the efficient collaboration of various front-end modules.

[0036] Further, the background management and display style instruction, the chart management and chart component attribute management instruction, the scene management instruction, and the chart data management instruction are all included in the branch instruction of the management business layer instruction;

[0037] Receive the travel data interface editing instruction;

[0038] According to the travel data interface editing instruction, call the management business layer instruction of the business layer;

[0039] Determine whether the travel data interface editing instruction matches the management business layer instruction of the business layer;

[0040] If the tourism data interface editing instruction matches the management business layer instruction of the business layer, an adjustment instruction centered on the management business layer instruction is obtained;

[0041] If the tourism data interface editing instruction does not match the management business layer instruction of the business layer, an adjustment instruction centered on the basic editing module calling instruction is obtained.

[0042] Specifically, the business layer is linked by a dependency relationship to realize module cooperation and logical processing. The attribute management module serves as a basic support core to provide unified attribute configuration capabilities for basic configuration modules such as background, style, chart, scene, and template, covering visual parameter configuration logic such as component title, border, color matching, position, and size. This module is the functional basis of all display modules, and at the same time relies on the third-party interface module of the external integration layer to obtain extended capabilities. The dependency scheduling module is based on the dependency chain from the editing module to the basic configuration module, from the basic configuration module to the attribute module, and from the attribute module to the third-party interface to build an automated scheduling mechanism. It is responsible for verifying module calling sequence, synchronously configuring parameter transmission, and handling dependency conflicts to ensure data consistency when the editing module calls background, style, and other modules, and to ensure coherent execution of business processes.

[0043] Further, the database of the back-end service module is called;

[0044] A structured data of the adjustment instruction is selected;

[0045] It is determined whether the data request of the structured data of the adjustment instruction matches the data information of the database of the back-end service module;

[0046] If the data request of the structured data of the adjustment instruction matches the data information of the database of the back-end service module, it is determined that the adjustment instruction calls the database of the back-end service module, and the structured data of the adjustment instruction is returned until all structured data are selected;

[0047] If the data request of the structured data of the adjustment instruction does not match the data information of the database of the back-end service module, it is determined that the adjustment instruction calls a third-party data interface, and the structured data of the adjustment instruction is returned until all structured data are selected.

[0048] Specifically, the database of the back-end service module serves as a data interaction hub of the system core, and shoulders the key mission of data flow between the front end and the database. Its primary responsibility is to accurately handle various data requests initiated by the front-end saving module, through a pre-defined standardized interface protocol covering data format specification, transmission encryption mechanism, and interaction status code system, to systematically and persistently process structured data throughout the project life cycle.

[0049] The structured data of the adjustment instruction can correspond to the core information of the database, and the structured data covers multi-dimensional core information, the project configuration level includes basic parameter setting, permission configuration matrix and process node definition, the scene data includes scene topology relationship, dynamic parameter threshold and associated resource mapping, the template information relates to template structure definition, style configuration set and version iteration record, and the component attribute covers component function parameter, rendering rule and interaction trigger condition. In the data persistence process, the hub automatically completes data verification, format legality verification, business rule verification, redundancy cleaning and index optimization, to ensure that the data entered into the database has integrity and consistency.

[0050] The third-party data interface is inside the third-party interface module, which is a core supporting dependent component of the attribute management module. The external capability interface system plays a key role in function extension and performance enhancement. The map service interface cluster integrates the technical capabilities of mainstream map service providers such as AQ map, QW map, and DD map, and can provide full-scene map services including high-precision map background dynamic loading, multi-scale layer switching, POI (point of interest) accurate search, spatial coordinate conversion, path planning deduction, and other full-scene map services, laying a foundation for the spatialization of attribute data.

[0051] The data calculation interface builds a professional operation support system, covering real-time data stream aggregation, spatial relationship topology analysis, multi-dimensional index statistics, and time-space sequence prediction, which can quickly process massive attribute data cleaning, conversion, correlation calculation, and dynamic update requirements.

[0052] Further, a data format conversion function is established using a data mapping rule system;

[0053] Based on the data format conversion function, a standardized algorithm of the third-party interface adaptation layer is generated;

[0054] The standardized algorithm of the third-party interface adaptation layer is incorporated into the core business management logic algorithm;

[0055] A configuration module of full-dimensional visualization parameters is generated based on the data information of the database of the backend service module;

[0056] The third-party interface module and the configuration module of full-dimensional visualization parameters are adapted using the core business management logic algorithm.

[0057] Specifically, in terms of interface call standardization, full-dimensional standards covering request parameter specifications, call flow definition, timeout control strategies, and error code systems need to be developed. By presetting a unified interface call template, the calling methods of different third-party interfaces are standardized, and the processing logic of interface calls within the system is ensured to be consistent.

[0058] To meet the data format conversion requirements, a flexible data mapping rule system needs to be established. By analyzing the response data structure of the third-party interface and combining the internal data model of the attribute management module, a bidirectional data conversion mechanism is designed: the heterogeneous data of external interfaces, such as JSON, XML, etc. format, is automatically converted into internal standardized data format, while supporting reverse conversion of internal business data according to the third-party interface requirements format, ensuring the accuracy and integrity of data interaction.

[0059] The packaging scheme can realize the decoupled seamless docking of external interfaces and attribute management modules: the business module only needs to call the internal packaged standardized interface service, without needing to pay attention to the specific implementation details of the third-party interface, such as interface address, parameter format, protocol type, etc. When the third-party interface changes, such as parameter adjustment, address migration, version upgrade, etc., only the packaging logic of the adaptation layer needs to be adjusted, without modifying the core business code of the attribute management module, greatly reducing the system change cost, and effectively ensuring the system compatibility and stability in the interface change scenario.

[0060] Further, a structured data of the adjustment instruction is selected, and geometric parameters contained in the structured data are extracted, the geometric parameters including a center coordinate, a radius value, and a polygon vertex coordinate sequence; each edge of the polygon is traversed, and intersection point coordinates of each edge are calculated; and effective intersection points within the range of the edge line segment are filtered out;

[0061] According to all the effective intersection point coordinates, the circle is divided into a plurality of geometric arc segments, and adjacent arc segments are merged based on a preset tolerance threshold to generate a standardized geometric segment set; based on the standardized geometric segment set, the distance between each data point and the center of the circle is calculated, and the relative position relationship between each data point and the target circular region is determined by comparing the distance with the radius value;

[0062] According to the relative position relationship, a position identifier is assigned to each data point, and a mapping relationship between the data points and the standardized geometric segments is established; and the distribution characteristics of the data points in the mapping relationship are analyzed, and when it is detected that more than a threshold proportion of data points are located outside the circular region, it is determined that the structured data belongs to the external integration layer instruction;

[0063] If the selected structured data is determined to belong to the external integration layer instruction, the selected structured data is converted into a standardized data format according to the standardized geometric segment set and the position identifier mapping relationship; if the selected structured data is not determined to belong to the external integration layer instruction, the structured data is processed by calling the internal packaged standardized interface.

[0064] Further, the attribute configuration of the travel data interface editing instruction is parsed;

[0065] Based on the attribute configuration, the component content configured by the attribute is called; the component content includes one or more of picture material, table material and chart material.

[0066] Further, the dependency of the core business management logic algorithm is established;

[0067] The third-party database is used as the dependency of the core business management logic algorithm by using the standardized algorithm of the third-party interface adaptation layer.

[0068] According to the adjustment instruction, the third-party database is called;

[0069] The data information of the third-party database is included in the dependency of the core business management logic algorithm through the third-party interface adaptation layer.

[0070] The application also provides a big data visualization configuration system, which comprises:

[0071] A server is used for executing the big data visualization configuration method;

[0072] A memory is in communication connection with the server.

[0073] Specifically, the server adopts a hierarchical architecture design, takes the module dependency relationship as the core context, constructs a four-layer architecture system from the front-end interaction layer to the core business layer, from the core business layer to the data support layer, and from the data support layer to the external integration layer, follows the dependency link from saving, previewing, publishing to editing, from editing to basic configuration, from basic configuration to attribute, and from attribute to third-party interface, and ensures that the coupling between the functional modules is clear, the data flow is efficient, and the full-process visualization configuration requirement is met.

[0074] The memory is used as the storage hardware of the database, and the memory is in communication connection with the server. The database module uses a relational database storage system to store core data, including project basic information, component configuration parameters, template definition, user operation record, etc. By standardizing the table structure design, the data association relationship between the modules is established, the data integrity and consistency are ensured, and reliable data storage support is provided for the whole system.

[0075] The application has the following beneficial effects:

[0076] The business personnel can efficiently and independently configure the tourism data interface, the technical threshold is reduced by more than 80%, and the business personnel can complete the full-process operation from data access to scene publishing through the no-code interface.

[0077] The demand response period is greatly shortened, the period from demand proposal to scene online is compressed from several weeks to 1 to 2 days, temporary data analysis demand can realize efficient configuration of the tourism data interface through template reuse and rapid configuration, and the real-time performance of supporting business decision is improved.

[0078] The system maintenance cost is significantly reduced, the modularization and decoupling design reduces the single module modification cost by more than 60%, and when a new chart type, style adjustment or third-party interface update is required, the full code reconstruction is not required, and the maintenance cost increases linearly with the scene complexity rather than exponentially.

[0079] The data link is fully connected, the data cleaning, correlation and display links are integrated, the data inconsistency problem is reduced by more than 90%, the business personnel can directly control the data quality, and the dependence on external data engineers is reduced.

[0080] The business self-configuration, demand rapid response, system easy maintenance and data full-link connection can be realized, and efficient, low threshold and scalable technical support is provided for the data visualization of the tourism industry. BRIEF DESCRIPTION OF DRAWINGS

[0081] Figure 1 A method flow diagram for big data visualization configuration in an embodiment of the present application.

[0082] Figure 2 A system structure connection diagram for big data visualization configuration in an embodiment of the present application.

[0083] 100-server; 200-memory. DETAILED DESCRIPTION

[0084] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme of the present application will be described in detail below with reference to the drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0085] As shown in Figure 1 The method for big data visualization configuration provided by the present application comprises:

[0086] S100, receiving a tourism data interface editing instruction of an interaction layer.

[0087] S200, analyzing the tourism data interface editing instruction of the interaction layer to obtain an adjustment instruction. The adjustment instruction comprises one or more of a front-end interaction layer instruction, a management business layer instruction, a data support layer instruction and an external integration layer instruction.

[0088] S300, based on a core business management logic algorithm, judging whether the adjustment instruction belongs to the external integration layer instruction.

[0089] S400, if the adjustment instruction does not belong to the external integration layer instruction, feeding back the tourism data interface editing instruction of the interaction layer to the data support layer.

[0090] S410, based on the tourism data interface editing instruction, the core business management logic algorithm process support script, call the back-end service module, extract the template data connected to the database.

[0091] S420, feedback the picture material, table material, chart material corresponding to the tourism data interface editing instruction, to realize the visualization configuration of the tourism data interface.

[0092] S500, if the adjustment instruction belongs to the external integration layer instruction, a standardized third-party interface adaptation layer is constructed to call the third-party database.

[0093] S510, the third-party database is included in the core business management logic algorithm to generate one or more save templates.

[0094] S520, extract the picture material, table material, chart material corresponding to the tourism data interface editing instruction in the save template to realize the visualization configuration of the tourism data interface.

[0095] Specifically, the method of big data visualization configuration reduces the threshold of tourism data visualization through lightweight configuration and efficient data integration capability, and helps business personnel to quickly build professional big data display scenarios.

[0096] The system core capability focuses on data access and visualization whole process management, through integrating rich third-party data interface (such as tourism passenger flow data, consumption data, scenic spot operation data interface, etc.), realizes the convenient acquisition and integration of multi-source tourism data, solves the problems of data processing disconnection and complex interface docking in traditional data visualization. At the same time, the system builds a full-link function system covering data management-configuration design-preview release, to meet the diversified data display needs of tourism industry. Through the tourism data interface editing instruction of the interaction layer, the problem of high technical barrier is solved. Using the tourism data interface editing instruction of the interaction layer avoids the disadvantages of tourism data interface editing which requires professional development team to master the composite skills of data interface development and chart rendering logic, forms the technical advantage that business personnel can participate in configuration, forms the operation channel of business demand and low technical threshold. Analyzing the tourism data interface editing instruction of the interaction layer, obtaining the adjustment instruction, the adjustment instruction includes one or more of the front-end interaction layer instruction, the management business layer instruction, the data support layer instruction, the external integration layer instruction, the demand response efficiency of user input instruction is higher, reduces the average period from demand communication to scheme landing, can adapt to the rapid iteration rhythm of business, improves the efficiency of business decision.

[0097] The tourism data interface editing instruction of the interaction layer is fed back to the data support layer, based on the tourism data interface editing instruction, the process support script of the core business management logic algorithm, the backend service module is called, the template data connected with the database is extracted, the system maintenance cost is low, the template data of the database of the backend service module is used, the code usage is low, the coupling difficulty is small, the modification rate of the chart type, the data dimension or the style layout is small in the later period, the processing difficulty of the complex visual scene is low.

[0098] A standardized third-party interface adaptation layer is constructed to call the third-party database, and the third-party database is incorporated into the core business management logic algorithm to generate one or more saving templates, solving the problem of fragmented data link connection. The pretreatment operations such as data cleaning and aggregation are processed by the processing logic of the server itself, the visualization configuration is highly associated with the data processing link, and the standardized third-party interface adaptation layer is helpful to improve the data quality of the data used.

[0099] The present application relates to a big data visualization configuration method, the front-end interaction layer instruction is used to drive the front-end interaction layer, and the front-end interaction layer is a modularized interaction entrance. The management business layer instruction is used to drive the core business layer, and the core business layer takes the dependency relationship as a link to realize module cooperation and logic processing. The data support layer instruction is used to drive the data support layer, and the data support layer undertakes the storage and circulation responsibilities of system data. The external integration layer instruction is used to drive the external integration layer, which provides functional expansion support for the attribute management module and breaks the system capability boundary.

[0100] At the functional level, the big data visualization configuration method can realize personalized visual customization through background management and display style management, support tourism scenario visual expression, provide rich chart type selection and fine style configuration through display chart management and chart component attribute management, adapt to different tourism data dimension display requirements, realize multi-business scenario classification management and quick switching through display scene management, such as scenic spot operation monitoring, tourism market analysis, passenger flow early warning, etc., rely on chart data management to complete data cleaning, association and update maintenance, and guarantee data caliber consistency. Combined with the display preview function and the display publishing function, the configuration effect can be viewed and published in one key, which greatly shortens the period from demand to landing, reduces the technical barriers for business personnel to participate in configuration through modular architecture design, adapts to the rapid iteration requirements of tourism business through flexible style and scene management, reduces the later maintenance cost through standardized data interface and component design, and finally provides an efficient, professional and easy-to-use big data visualization solution for the tourism industry, helping tourism enterprises to drive business decision-making and operation optimization through data visualization.

[0101] In an embodiment of the present application, before S100, it includes:

[0102] S111, background color gradient, parameter settings, picture material import, transparency dynamic adjustment are included in the architecture branch of background editing management.

[0103] S112, the main auxiliary color value definition, font family adaptation, spacing rule configuration, and border shadow parameter adjustment are included in the architecture branch of style editing management.

[0104] S113, the chart type switching, data dimension mapping, coordinate axis scale customization, and legend interactive configuration are included in the architecture branch of chart editing management to realize data visualization interface editing based on non-single type chart engine.

[0105] S114, based on the script preset by the terminal adaptation rule, the script adjusted by the component level, and the script configured by the responsive layout parameter, the architecture branch of scene editing management is formed.

[0106] S115, the basic editing module of the tourism data interface is constructed. The basic editing module includes one or more basic editing architectures of background editing management, style editing management, chart editing management, scene editing management, and template editing management.

[0107] It can be understood that the front-end interaction layer focuses on user operation experience and constructs an interactive closed loop based on module dependency relationship. The basic editing module serves as the core hub of the front end, integrates the five basic configuration modules of background management, style management, chart management, scene management, and template management, and undertakes the creation and editing functions of visual content. The module directly depends on the attribute management module of the core business layer and realizes personalized settings such as background style and chart parameters by calling attribute configuration capabilities.

[0108] In this embodiment, the process support module includes three modules of saving, previewing, and publishing, and strictly depends on the output data of the basic editing module. The saving module captures the editing results in real time and triggers a data persistence request. The preview module generates a preview page consistent with the publishing effect based on the editing data. The publishing module supports permission configuration such as password protection and completes the final online operation to form a complete process link of editing-saving-preview-publishing. The auxiliary function module covers the project management module and provides basic support such as project creation, editing, deletion, screen adaptation, and auxiliary line management, thereby providing a unified project context environment for all front-end modules.

[0109] In an embodiment of the present application, S100 includes:

[0110] S121, receiving an input instruction of a client.

[0111] S122, based on the input instruction, judging whether the input instruction of the client calls the basic editing module.

[0112] S123, if the client calls the basic editing module, parse the input instruction of the client, generate the travel data interface editing instruction.

[0113] S124, if the client does not call the basic editing module, determine that the input instruction of the client is to call the auxiliary function module of the interaction layer.

[0114] S125, parse the input instruction of the client.

[0115] S126, obtain the establishment instruction of the travel data interface editing item.

[0116] S127, find the target editing template of the establishment instruction in the auxiliary function module.

[0117] S128, generate the travel data interface editing instruction based on the establishment instruction of the travel data interface editing item.

[0118] It can be understood that, as the core hub of the front-end visual editing system, this module integrates the background management, style management, chart management, scene management and template management five basic configuration modules in an integrated architecture, and builds a creation and editing capability hub covering the whole life cycle of visual content.

[0119] In terms of function landing, the five basic modules have their own focuses: the background management module supports background color gradient deployment, gradient parameter setting, picture material import and transparency dynamic adjustment, realizing fine control of the canvas base style. The style management module focuses on the theme system building, covering primary and secondary color value definition, font family adaptation, spacing rule configuration and border shadow parameter adjustment, ensuring the visual uniformity of visual content. The chart management module integrates multiple types of chart engines, providing chart type switching, data dimension mapping, coordinate axis scale customization, legend interaction configuration and other depth editing functions, meeting the diversified expression needs of data visualization. The scene management module is responsible for scene layout scheme storage and switching, supporting multi-terminal adaptation rule preset, component level adjustment and responsive layout parameter configuration. The template management module realizes the storage, classification, version control and one-key reuse function of standardized templates, greatly improving the content creation efficiency. This core module deeply depends on the attribute management module in the core business layer of the front-end architecture, and realizes the accurate landing of personalized configurations such as background style parameters, chart interaction attributes and scene layout rules by calling the dynamic attribute configuration engine, style rule verification interface and real-time configuration synchronization capability provided by the attribute management module. The unified attribute dictionary and configuration schema provided by the attribute management module ensure the consistency and compatibility of the configuration items of each function module, and the configuration change real-time push mechanism supported by it guarantees the instant feedback of style and data in the process of visual editing, bringing users a smooth and efficient editing experience.

[0120] The three core modules (save, preview, and publish) are supported by the output data of the basic editing module, and together build a complete content production closed loop. The basic editing module, as the source of content creation, provides basic creation capabilities such as rich text editing, format layout, and multimedia insertion. The structured content data generated by it will be the core data source for the entire process, providing accurate input for subsequent modules. The save module dynamically captures the editing results by real-time monitoring of content changes in the editing area, including text modifications, format adjustments, and image insertion operations. The system supports automatic timed saving and manual triggered saving in dual mode. Each save operation will immediately initiate a data persistence request, synchronously store the latest content to the backend database, and generate a local cache as a data security bottom line, effectively avoiding content loss caused by unexpected interruptions and ensuring that every modification during the creation process is safely retained. The preview module is based on the real-time data output by the editing module and uses a rendering engine consistent with the final publishing environment to generate a preview page identical to the actual publishing effect. Users can trigger preview at any time during editing to visually check the layout style, interactive effects, and display effects on different devices (such as PC and mobile devices), identify and correct potential format issues or content omissions in advance, and ensure the presentation quality of the final published content. The publish module, as the final link of the process, provides flexible permission configuration functions, supporting public access, password protection, and specified user group visibility, meeting the content access control needs of different scenarios. After completing the permission configuration, the system performs a final compliance check on the edited content, confirms the correctness, and executes the publish operation, synchronizes the content to the production server, and updates the access entry state. After publishing is completed, the system automatically synchronizes the publish state to the editing module, forming a complete process closed loop of editing-save-preview-publish, ensuring efficient and controllable content creation from creation to online.

[0121] The project management module, as the core support module of the front-end system, is responsible for the entire project life cycle management and basic technical support. This module integrates the entire project link function, providing complete management capabilities from project initialization to termination, and building a unified technical base to support efficient collaboration of various front-end modules.

[0122] At the level of core project management functions, the module supports a visual project creation process. Users can complete project initialization by filling in basic information such as project name, description, and type, combined with preset templates or custom configurations, and generate a dedicated project identifier and basic configuration file simultaneously. For project editing needs, the module provides multi-dimensional attribute modification capabilities, including project basic information update, member permission configuration, process node adjustment, and supports real-time saving and historical version rollback to ensure traceability of project changes. In the project deletion link, a multi-level security mechanism is designed, including a second confirmation before deletion, a recycle bin for temporary storage, and permanent deletion permission control, effectively avoiding the risk of misoperation.

[0123] In terms of technical support capabilities, the module has a built-in perfect screen adaptation engine that can automatically identify terminal device types (PC, mobile, tablet devices, etc.) and resolution parameters, dynamically adjust project display layout, component size, and interaction mode, ensuring consistency and smoothness of operation on different devices. The auxiliary line management function provides precise support for project layout, users can customize auxiliary line position, color, and display level to achieve component alignment, spacing control, and layout specification verification, while supporting auxiliary line group saving and reuse to improve interface design efficiency.

[0124] As the foundation of the front-end system, the module builds a unified project context management system, which realizes real-time sharing and synchronization of project basic information, configuration parameters, and permission data among various front-end modules through standardized data interfaces and state management mechanisms. This mechanism ensures data consistency when different functional modules (such as editing modules, preview modules, statistical modules, etc.) operate on the same project, simplifies cross-module collaboration processes, and provides a solid foundation for stable operation and functional expansion of the front-end system.

[0125] In an embodiment of the present application, S200 includes:

[0126] S211, background management and display style instructions, chart management and chart component attribute management instructions, scene management instructions, and chart data management instructions are all included in the branch instructions of the management business layer instructions.

[0127] S212, receive a travel data interface editing instruction.

[0128] S213, according to the travel data interface editing instruction, call the management business layer instruction of the business layer.

[0129] S214, determine whether the travel data interface editing instruction matches the management business layer instruction of the business layer.

[0130] S214a, if the travel data interface editing instruction matches the management business layer instruction of the business layer, obtain the adjustment instruction centered on the management business layer instruction.

[0131] S214b, if the travel data interface editing instruction does not match the management business layer instruction of the business layer, obtain the adjustment instruction with the basic editing module calling instruction as the core.

[0132] It can be understood that, as the basic support core of system visual presentation and interaction configuration, this module plays a central role and provides a standardized and one-stop attribute configuration support system for various basic configuration modules such as background style, interface style, chart type, scene layout, template framework. Its core capabilities cover the configuration logic of all-dimensional visual parameters such as font style (including font size, font weight, font type) of component title, border design (including line thickness, corner radius, border style), color scheme (including main color, auxiliary color, gradient color parameters), position and size (including coordinate positioning, width and height ratio, scaling rules), and support unified management of fine visual parameters such as shadow effect, transparency adjustment, layout spacing.

[0133] As the bottom function base, this module provides core capability support for all display modules such as data dashboard, report display, and visual page, ensuring the consistency and standardization of various display modules in visual presentation and interactive experience. At the same time, the module interfaces with the third-party interface module of the external integration layer to dynamically obtain extended capabilities such as dynamic theme library, advanced chart engine, and font resource library, continuously expanding the configuration boundary and functional depth to meet the configuration needs in various scenarios.

[0134] The properties are also made into plug-ins for easy expansion and stored in the components directory under the directory named properties. Create a plug-in directory under each directory, with each plug-in corresponding to a directory. The main program automatically reads files and initializes from the file directory. Property plug-ins can be referenced by backgrounds (backgrounds), styles (styles), charts (charts), and other plug-ins. After successful reference, the property will appear in the property editing box.

[0135] Around the core dependency chain of the editing module → the basic configuration module → the attribute module → the third-party interface, a full-link automatic scheduling mechanism is constructed, and through systematic process control and data collaboration, orderly collaboration between modules and efficient operation of business processes are realized. At the level of synchronous transmission of configuration parameters, a distributed parameter bus is constructed to realize automatic matching and real-time flow of upstream module output parameters and downstream module input requirements. After the basic parameters generated by the editing module are format-verified, they are synchronized to the parameter pool of the basic configuration module. After the basic configuration module completes the configuration calculation, the derived parameters and the original parameters are packaged and pushed to the attribute module through an encrypted channel. The attribute module selects key parameters according to business rules, and transmits them to the third-party interface after standardization processing. At the same time, a parameter version management mechanism is established to associate parameters at each link through a unique identifier, so as to ensure that the full-link parameters are traceable and verifiable, and to avoid parameter loss, tampering or version disorder. In order to ensure the data consistency when the editing module calls associated modules such as background and style, a cross-module data verification matrix is established. When the editing module initiates a background and style configuration request, a data consistency pre-verification is triggered synchronously to compare whether the basic parameters and business rules of the associated modules are consistent with the editing module. The data flow state is monitored in real time during the configuration process, and the key data is ensured not to be tampered through hash value comparison. After the configuration is completed, a consistency report is generated to record the data matching degree of each module, and the second synchronization is automatically initiated for the items that do not meet the standard.

[0136] In one embodiment of the present application, S200 further comprises:

[0137] S221, calling the database of the backend service module.

[0138] S222, selecting one structured data of the adjustment instruction.

[0139] S223, judging whether the data request of the structured data of the adjustment instruction matches the data information of the database of the backend service module.

[0140] S224a, if the data request of the structured data of the adjustment instruction matches the data information of the database of the backend service module, it is determined that the adjustment instruction calls the database of the backend service module, and one structured data of the adjustment instruction is returned until all the structured data are selected.

[0141] S224b, if the data request of the structured data of the adjustment instruction does not match the data information of the database of the backend service module, it is determined that the adjustment instruction calls the third-party data interface, and one structured data of the adjustment instruction is returned until all the structured data are selected.

[0142] As the core supporting component of the attribute management module, the external capability interface system plays a key role in extending functions and enhancing performance. The map service interface cluster integrates the technical capabilities of mainstream map service providers such as MapWorld, Gaode Map, and Baidu Map, and can provide full-scene map services including high-precision map background dynamic loading, multi-scale layer switching, POI (Point of Interest) accurate retrieval, spatial coordinate conversion, path planning deduction, and other functions, laying the foundation for the spatialization of attribute data.

[0143] The data calculation interface builds a specialized operation support system, covering real-time data stream aggregation, spatial relationship topology analysis, multi-dimensional index statistics, and time-space sequence prediction, and can quickly process massive attribute data cleaning, conversion, correlation calculation, and dynamic update requirements.

[0144] To achieve efficient integration of external systems and the attribute management module, a standardized third-party interface adaptation layer needs to be built, with unified interface call logic through abstract encapsulation mechanisms. Specifically, a general interface call framework needs to be designed to encapsulate the core operations of third-party interface request initiation, parameter assembly, and response reception as standardized service components, avoiding direct dependence of business modules on external interface details.

[0145] In terms of interface call standardization, a full-dimensional standard covering request parameter specifications, call flow definitions, timeout control strategies, and error code systems needs to be established. By presetting a unified interface call template, the calling methods of different third-party interfaces are standardized, ensuring consistent handling logic for interface calls within the system.

[0146] For data format conversion needs, a flexible data mapping rule system needs to be established. By analyzing the response data structure of third-party interfaces and combining the internal data model of the attribute management module, a bidirectional data conversion mechanism is designed: heterogeneous data from external interfaces (such as JSON, XML, etc.) is automatically converted to internal standardized data formats, while internal business data is converted in reverse according to the requirements of third-party interfaces, ensuring the accuracy and integrity of data interaction.

[0147] This encapsulation scheme can achieve decoupled seamless integration of external interfaces and the attribute management module: business modules only need to call internal encapsulated standardized interfaces, without needing to focus on the specific implementation details of third-party interfaces (such as interface addresses, parameter formats, protocol types, etc.). When third-party interfaces change (such as parameter adjustment, address migration, version upgrade, etc.), only the encapsulation logic of the adaptation layer needs to be adjusted, without modifying the core business code of the attribute management module, significantly reducing system change costs and effectively ensuring system compatibility and stability in interface change scenarios.

[0148] At the same time, the encapsulation layer needs to integrate unified log monitoring and exception handling mechanisms, comprehensively record request parameters, response results, time consumption statistics, exception information, etc. during interface call process, provide support for interface problem troubleshooting and performance optimization, and further improve the maintainability of the system.

[0149] In one embodiment of the present application, in S300, the core business management logic algorithm includes:

[0150] S311, a data mapping rule system is used to establish a data format conversion function.

[0151] S312, based on the data format conversion function, a standardized algorithm of the third-party interface adaptation layer is generated.

[0152] S313, the standardized algorithm of the third-party interface adaptation layer is included in the core business management logic algorithm.

[0153] S314, a configuration module of full-dimensional visualization parameters is generated based on data information of the database of the back-end service module.

[0154] S315, the core business management logic algorithm is used to adapt the third-party interface module and the configuration module of full-dimensional visualization parameters.

[0155] As can be understood, as the core of data interaction hub, it shoulders the key mission of data flow between the front end and the database. Its primary responsibility is to accurately accept various data requests initiated by the front-end saving module, and to systematically persist structured data in the whole life cycle of the project through pre-defined standardized interface protocols (covering data format specifications, transmission encryption mechanisms and interaction status code systems).

[0156] These structured data cover multi-dimensional core information: project configuration level includes basic parameter setting, permission configuration matrix and process node definition. Scene data includes scene topology relationship, dynamic parameter threshold and associated resource mapping. Template information involves template structure definition, style configuration set and version iteration record. Component attributes cover component function parameters, rendering rules and interaction trigger conditions, etc. In the data persistence process, the hub will automatically complete data verification (format legality verification, business rule verification), redundancy cleaning and index optimization, to ensure that the data entered into the database has integrity and consistency.

[0157] To support the real-time interaction needs of the front-end module, the data interaction hub builds a comprehensive interface service system: provides accurate data query interface, supports multi-condition combination filtering, paging query and associated data aggregation. Design flexible update interface, realize full-coverage update and incremental field update two modes. Configure safe delete interface, support single data deletion and batch data cleaning, and synchronize operation log recording.

[0158] In the system architecture, the data interaction hub is an irreplaceable core link. On the one hand, it shields the differences between the database bottom layers through a standardized interface, and provides a unified data interaction entrance for the front end. On the other hand, through a real-time data synchronization mechanism, it ensures that the front-end operation and the database state remain dynamically consistent, and provides stable data support for core scenes such as visual editing, real-time preview, and collaborative work.

[0159] In one embodiment of the present application, S300 includes:

[0160] S321, one of the structured data of the adjustment instruction is selected, and geometric parameters contained in the structured data are extracted, including the coordinates of the center of a circle, the radius value, and the coordinate sequence of the vertices of a polygon; each edge of the polygon is traversed, and the coordinates of the intersection points of each edge and the circle are calculated, and valid intersection points within the range of the edge line segment are screened out, specifically including:

[0161] From the multiple structured data contained in the adjustment instruction, one of them is selected for processing, and key parameters related to spatial geometry are extracted from the structured data, including the coordinates of the center of a circle (i.e. the position information of the center of a circle), the radius value of the circle (the distance from the center to the circumference), and the coordinate sequence of the vertices of a polygon (the positions of the vertices of the polygon are recorded in order, which are used to determine the boundary of the polygon).

[0162] Then, each edge of the polygon is processed one by one, and the coordinate sequence of the vertices of the polygon is used to sequentially select two adjacent vertices to determine an edge (for example, the first vertex and the second vertex form the first edge, the second vertex and the third vertex form the second edge, and so on). For each edge, the coordinates of all intersection points between the straight line of the edge and the previously extracted circle are calculated. Finally, the valid intersection points are screened out from these intersection points, i.e. it is judged whether the intersection point is actually located within the range of the line segment of the edge being processed (rather than only on the infinitely long straight line of the edge), and only the intersection point that falls between the two vertices of the edge is retained.

[0163] S322, the circle is divided into multiple geometric arc segments according to all valid intersection point coordinates, and adjacent arc segments are merged based on a preset tolerance threshold to generate a standardized geometric segment set; based on the standardized geometric segment set, the distance between each data point and the center of the circle is calculated, and the relative position relationship between each data point and the target circular region is determined by comparing the size relationship between the distance and the radius value, specifically including:

[0164] Based on all the valid intersection points screened out by S321, the circle is divided into multiple continuous geometric arc segments: the arc part between each adjacent two valid intersection points forms an independent arc segment. Then, according to the system preset tolerance threshold (a standard for judging whether the arc segments are close, for example, the arc length difference is within a certain range), the adjacent arc segments are merged: if the difference between two adjacent arc segments is less than the tolerance threshold, they are merged into a larger arc segment, and finally a set of standardized geometric segment collection (i.e. the combination of arc segments after merging and format unification) is formed; next, for each data point in the structured data, the straight line distance between the data point and the center of the circular region is calculated, and this distance is compared with the radius value of the circle: if the distance is less than the radius, it is determined that the data point is located inside the circular region; if the distance is greater than the radius, it is determined to be located outside; if the distance is equal to the radius, it is determined to be located on the boundary of the circle, through this process, the relative position relationship of each data point with the target circular region is determined.

[0165] S323, according to the relative position relationship, a position identifier is assigned to each data point, and a mapping relationship between the data points and the standardized geometric segments is established; when it is detected that more than a threshold proportion of data points are located outside the circular region, it is determined that the structured data belongs to the external integration layer instruction, which specifically includes:

[0166] According to the relative position relationship of each data point with the circular region determined by S322, a corresponding position identifier is assigned to each data point: for example, an internal identifier is used to identify the data points located inside the circular region, an external identifier is used to identify the data points located outside the region, and a boundary identifier is used to identify the data points located on the circumference; at the same time, a mapping relationship between the data points and the standardized geometric segment collection is established: that is, it is recorded which geometric arc segment each data point corresponds to (for example, the data points located near the arc segment between two intersection points are associated with the arc segment); then, the distribution characteristics of all data points are analyzed: the proportion of the number of data points located outside the circular region to the total number of data points is calculated. When the proportion exceeds the system preset threshold (for example, more than 50%), it is determined that the structured data being processed belongs to the external integration layer instruction (i.e. the data mainly comes from the database outside the system).

[0167] S324, if the selected structured data is determined to belong to the external integration layer instruction, the selected structured data is converted into a standardized data format according to the standardized geometric segment collection and the position identifier mapping relationship; if the selected structured data is not determined to belong to the external integration layer instruction, the internal encapsulated standardized interface is called to process the structured data, which specifically includes:

[0168] If S323 determines that the current structured data belongs to the external integration layer instruction, the structured data is converted in format based on the previously generated standardized geometric segment set (uniform arc segment format) and the mapping relationship between data points and segments (position association information): the spatial position description, attribute information, etc. of the data are converted into the standardized data format commonly used in the system (to ensure compatibility with the internal data processing logic); if S323 determines that the structured data does not belong to the external integration layer instruction (i.e. the data is from the internal database of the system), the standardized interface pre-packaged in the system is directly called to process it: the data is transmitted into the internal data processing flow through the interface, and the data is checked, stored or further calculated, etc.

[0169] It can be understood that by extracting the center coordinates, radius and polygon vertex sequence in the structured data, the core parameters required for spatial analysis are accurately locked, and the subsequent calculation deviation caused by missing or incorrect extraction of parameters is avoided; at the same time, by screening the effective intersection points located in the range of the polygon edge segment, the invalid intersection points only on the straight line and not on the actual polygon edge are excluded, and it is ensured that the arc segment boundary used for splitting the circle in the subsequent completely fits the actual contour of the polygon, thus eliminating the geometric analysis error caused by invalid intersection points from the source. By traversing the polygon edges one by one and determining the range of the edge according to the vertex sequence, the complex polygon-circle spatial relationship is decomposed into a simple relationship between a single edge and a circle, which simplifies the complex, avoids the calculation redundancy or logical confusion when directly processing the complex intersection between the whole polygon and the circle, and improves the operability of spatial parameter processing. By calculating the distance between the data point and the center of the circle and comparing the radius to determine the position, the abstract spatial data is converted into the explicit attributes of internal / external / boundary, and the spatial attribution of each data point is quantifiable and verifiable, avoiding the deviation caused by subjective judgment (such as the error of manual judgment of data point position).

[0170] By counting the proportion of external data points, exceeding the threshold is determined as the external integrated layer instruction, replacing subjective experience judgment (such as not relying on manual identification of data sources), ensuring that the classification logic is quantifiable and reproducible; For example, when a 50% threshold is preset, only when most data points come from the external space (such as third-party map POI data) is it determined as an external instruction, avoiding misjudgment caused by individual external data points, and ensuring that the subsequent processing path (internal S400, external S500) completely matches the data source, eliminating the waste of resources caused by the internal data going through the external adaptation process, or the compatibility problem of the external data going through the internal processing process; Directly calling the pre-packaged standardized interface of the internal data can reduce the code redundancy without repeated development of data verification and storage logic; At the same time, the built-in verification rules (such as data format verification, permission verification) of the interface can guarantee the standardization of internal data processing, avoid illegal data or error data entering the subsequent visualization process, and reduce system maintenance cost (such as modifying internal data processing logic in later period, only need to update the interface, no need to adjust the upstream judgment link); Through the closed-loop processing of S321-S324, it can be accurately distinguished whether the data comes from the internal database or the external third party, so that the subsequent processing path (S400 internal process / S500 external process) completely matches the data attribute: internal data goes through low-coupling and low-cost internal call process without additional adaptation; External data goes through standardized adaptation and high-quality integration of external process to ensure data availability.

[0171] From S321 screening valid intersection, S322 accurate position judgment, to S323 objective classification, S324 adaptation processing, each link reduces data error through screening, verification and standardization, invalid intersection is excluded, position judgment has no subjective deviation, data format is compatible with internal logic, and finally the data entering the visualization configuration are accurate, compliant and usable, avoiding distortion of visualization results caused by data error (such as spatial data misplacement, abnormal display of external data); The automatic processing of S300 (without manual intervention in geometric calculation, position judgment and instruction classification) hides the complex spatial data processing logic, so that business personnel do not need to pay attention to technical details such as how to adapt the data format when configuring the visualization interface in the front end, and can only initiate editing instructions through the interaction layer. This is the design of the background technology logic.

[0172] In an embodiment of the present application, S410 comprises:

[0173] S411, analyzing the attribute configuration of the tourism data interface editing instruction.

[0174] S412, based on the attribute configuration, calling the component content configured by the attribute. The component content includes one or more of picture materials, table materials and chart materials.

[0175] As the core support of the system visual presentation and interaction configuration, this module plays a central role and provides a standardized and one-stop attribute configuration support system for various basic configuration modules such as background style, interface style, chart type, scene layout, and template framework. Its core capabilities cover the configuration logic of all-dimensional visual parameters such as font style (including font size, font weight, and font type) of component title, border design (including line thickness, corner radius, and border style), color scheme (including main color, auxiliary color, and gradient color parameters), position and size (including coordinate positioning, width and height ratio, and scaling rules), and support for unified management of fine visual parameters such as shadow effect, transparency adjustment, and layout spacing.

[0176] As the underlying functional base, this module provides core capability support for all display modules such as data dashboard, report display, and visual page, ensuring consistency and standardization in visual presentation and interactive experience. At the same time, the module interfaces with third-party interface modules in the external integration layer to dynamically obtain extended capabilities such as dynamic theme library, advanced chart engine, and font resource library, continuously expanding configuration boundaries and functional depth to meet configuration needs in various scenarios.

[0177] Properties are also made into plugins for easy expansion and stored in the components directory under the directory named properties. A plugin directory is created under each directory, with each plugin corresponding to a directory. The main program automatically reads files and initializes them from the file directory.

[0178] Property plugins can be referenced by backgrounds (backgrounds), styles (styles), and charts (charts) plugins. After successful reference, the property will appear in the property editing box.

[0179] Around the core dependency chain of editing modules, basic configuration modules, property modules, and third-party interfaces, a full-link automatic scheduling mechanism is built to achieve orderly collaboration between modules and efficient operation of business processes through systematic process control and data collaboration.

[0180] At the level of configuration parameter synchronization and transmission, a distributed parameter bus is built to realize automatic matching and real-time flow of upstream module output parameters and downstream module input requirements. After format verification, the basic parameters generated by the editing module are synchronized to the parameter pool of the basic configuration module. After the basic configuration module completes the configuration calculation, the derived parameters and original parameters are packaged and pushed to the property module through an encrypted channel. The property module filters key parameters according to business rules, standardizes them, and then passes them to the third-party interface. At the same time, a parameter version management mechanism is established to associate parameters at each link through a unique identifier, ensuring traceability and checkability of full-link parameters, and avoiding parameter loss, tampering, or version confusion.

[0181] To ensure the data consistency when the editing module calls the associated modules such as background and style, a cross-module data verification matrix is established. When the editing module initiates a background and style configuration request, a data consistency pre-verification is triggered synchronously to compare whether the basic parameters and business rules of the associated modules are consistent with the editing module. The data flow state is monitored in real time during the configuration process, and the key data is ensured not to be tampered through hash value comparison. After the configuration is completed, a consistency report is generated to record the data matching degree of each module, and the secondary synchronization is automatically initiated for the items that do not meet the standard.

[0182] In one embodiment of the present application, S510 comprises:

[0183] S511, the dependency of the core business management logic algorithm is established.

[0184] S512, the third-party database is used as the dependency of the core business management logic algorithm by using the standardized algorithm of the third-party interface adaptation layer.

[0185] S513, the third-party database is called according to the adjustment instruction.

[0186] S514, the data information of the third-party database is included in the dependency of the core business management logic algorithm through the third-party interface adaptation layer.

[0187] As can be understood, as the core supporting dependent component of the attribute management module, the external capability interface system plays a key role in function extension and performance enhancement. The map service interface cluster integrates the technical capabilities of mainstream map service providers such as Tian AQ map, QW map and DD map, and can provide full-scene map services including high-precision map background dynamic loading, multi-scale layer switching, POI (point of interest) accurate retrieval, spatial coordinate conversion, path planning deduction, etc., laying a foundation for the spatialization of attribute data.

[0188] The data calculation interface builds a professional operation support system, covering real-time data stream aggregation, spatial relationship topology analysis, multi-dimensional index statistics, time-space sequence prediction and other core capabilities, and can quickly process massive attribute data cleaning and conversion, correlation calculation and dynamic update requirements.

[0189] To realize efficient integration of external systems and the attribute management module, a standardized third-party interface adaptation layer needs to be built to unify the interface call logic through abstract encapsulation mechanism. Specifically, a general interface call framework needs to be designed to encapsulate the core operations such as third-party interface request initiation, parameter assembly and response reception as standardized service components, avoiding direct dependence of business modules on external interface details.

[0190] In the aspect of interface calling standard unification, a full-dimensional standard covering request parameter specification, calling flow definition, timeout control strategy and error code system needs to be formulated. Through presetting a unified interface calling template, the calling mode of different third-party interfaces is standardized, and the processing logic of interface calling in the system is ensured to be consistent.

[0191] For data format conversion requirements, a flexible data mapping rule system needs to be established. Through analyzing the response data structure of the third-party interface, combined with the internal data model of the attribute management module, a bidirectional data conversion mechanism is designed: the heterogeneous data (such as JSON, XML format) of the external interface is automatically converted into the internal standardized data format, while supporting the reverse conversion of the internal business data according to the third-party interface requirements format, ensuring the accuracy and integrity of data interaction.

[0192] The encapsulation scheme can realize the decoupled seamless connection of the external interface and the attribute management module: the business module only needs to call the standardized interface service encapsulated internally, without needing to pay attention to the specific implementation details (such as interface address, parameter format, protocol type, etc.) of the third-party interface. When the third-party interface changes (such as parameter adjustment, address migration, version upgrade, etc.), only the encapsulation logic of the adaptation layer needs to be adjusted, without modifying the core business code of the attribute management module, greatly reducing the system change cost, and effectively ensuring the system compatibility and stability in the interface change scenario.

[0193] At the same time, the encapsulation layer needs to integrate a unified log monitoring and exception handling mechanism to comprehensively record the request parameters, response results, time consumption statistics, exception information, etc. in the interface calling process, providing support for interface problem troubleshooting and performance optimization, and further improving the maintainability of the system.

[0194] As shown in Figure 2 The present application also provides a system for big data visualization configuration, which comprises:

[0195] The server 100 is used for executing the method for big data visualization configuration.

[0196] The memory 200 is in communication connection with the server 100.

[0197] Specifically, the server 100 is provided with a front-end interaction layer, a core business layer, a data support layer and an external integration layer. The front-end interaction layer comprises a basic editing module, a flow support module and an auxiliary function module. The core business layer comprises an attribute management module and a dependency scheduling module. The data support layer comprises a back-end service module and a database module. The external integration layer comprises a third-party interface module and an interface adaptation module.

[0198] The server 100 adopts a hierarchical architecture design, takes a module dependency relationship as a core context, constructs a four-layer architecture system from a front-end interaction layer to a core business layer, from the core business layer to a data support layer, and from the data support layer to an external integration layer, follows a dependency link from saving, previewing, publishing to editing, from editing to basic configuration, from basic configuration to attribute, and from attribute to a third-party interface, ensures clear coupling between functional modules and efficient data flow, and meets full-process visual configuration requirements.

[0199] The memory 200 is a storage hardware of a database, and the memory 200 is in communication connection with the server 100. A database module stores core data by using a relational database storage system, including project basic information, component configuration parameters, template definition, user operation records and the like. By standardized table structure design, a data correlation relationship between modules is established, data integrity and consistency are ensured, and reliable data storage support is provided for the whole system.

[0200] It is apparent for those skilled in the art that the present application is not limited to the details of the above exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or essential characteristics of the present application.

[0201] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application but not limit the present application, and although the present application has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that the technical solutions of the present application can be modified or replaced equivalently without departing from the spirit and scope of the present application.

Claims

1. A method of big data visualization configuration, characterized in that, The method comprises the following steps: receiving a tourism data interface editing instruction of an interaction layer; analyzing the tourism data interface editing instruction of the interaction layer to obtain an adjustment instruction; the adjustment instruction comprises one or more of a front-end interaction layer instruction, a management business layer instruction, a data support layer instruction, and an external integration layer instruction; a database of a back-end service module is called; one structured data of the adjustment instruction is selected; it is judged whether the data request of the structured data of the adjustment instruction matches the data information of the database of the back-end service module; if the data request of the structured data of the adjustment instruction matches the data information of the database of the back-end service module, it is determined that the adjustment instruction calls the database of the back-end service module, and the selection of one structured data of the adjustment instruction is returned until all structured data are selected; if the data request of the structured data of the adjustment instruction does not match the data information of the database of the back-end service module, it is determined that the adjustment instruction calls a third-party data interface, and the selection of one structured data of the adjustment instruction is returned until all structured data are selected; based on a core business management logic algorithm, it is judged whether the adjustment instruction belongs to the external integration layer instruction; if the adjustment instruction does not belong to the external integration layer instruction, the tourism data interface editing instruction of the interaction layer is fed back to the data support layer; based on the tourism data interface editing instruction and the process support script of the core business management logic algorithm, template data connected with the database is extracted; the picture material, the table material and the chart material corresponding to the tourism data interface editing instruction are fed back to realize the visual configuration of the tourism data interface; if the adjustment instruction belongs to the external integration layer instruction, a standardized third-party interface adaptation layer is constructed to call a third-party database; the third-party database is incorporated into the core business management logic algorithm to generate one or more save templates; the picture material, the table material and the chart material corresponding to the tourism data interface editing instruction are extracted from the save template to realize the visual configuration of the tourism data interface.

2. The method of big data visualization configuration according to claim 1, wherein, Before the receiving of the tourism data interface editing instruction of the interaction layer, the following steps are included: background color gradation, gradient parameter setting, picture material import and transparency dynamic adjustment are all incorporated into the architecture branch of background editing management; primary and secondary color value definition, font family adaptation, spacing rule configuration and border shadow parameter adjustment are all incorporated into the architecture branch of style editing management; chart type switching, data dimension mapping, coordinate axis scale customization and legend interaction configuration are all incorporated into the architecture branch of chart editing management to realize the data visualization interface editing based on a non-single type chart engine; scripts based on terminal adaptation rules, scripts based on component level adjustment, and scripts based on responsive layout parameter configuration form the architecture branch of scene editing management; a basic editing module of the tourism data interface is constructed; the basic editing module comprises one or more of the following basic editing architectures: background editing management, style editing management, chart editing management, scene editing management, and template editing management.

3. The method of big data visualization configuration of claim 2, wherein, The receiving of the tourism data interface editing instruction of the interaction layer comprises the following steps: receiving an input instruction of a client; based on the input instruction, it is judged whether the input instruction of the client calls the basic editing module; If the client calls the basic editing module, the input instruction of the client is parsed to generate a travel data interface editing instruction; If the client does not call the basic editing module, it is determined that the input instruction of the client is to call the auxiliary function module of the interaction layer; The input instruction of the client is parsed; The establishment instruction of the travel data interface editing project is obtained; The target editing template of the establishment instruction is found in the auxiliary function module; Based on the establishment instruction of the travel data interface editing project, the target editing template is generated into a travel data interface editing instruction.

4. The method of big data visualization configuration of claim 3, wherein, The travel data interface editing instruction of the interaction layer is parsed to obtain an adjustment instruction, including: The background management and display style instruction, the chart management and chart component attribute management instruction, the scene management instruction, and the chart data management instruction are all included in the branch instruction of the management business layer instruction; The travel data interface editing instruction is received; According to the travel data interface editing instruction, the management business layer instruction of the business layer is called; It is judged whether the travel data interface editing instruction matches the management business layer instruction of the business layer; If the travel data interface editing instruction matches the management business layer instruction of the business layer, an adjustment instruction centered on the management business layer instruction is obtained; If the travel data interface editing instruction does not match the management business layer instruction of the business layer, an adjustment instruction centered on the basic editing module calling instruction is obtained.

5. The method of big data visualization configuration of claim 4, wherein, The core business management logic algorithm is used to judge whether the adjustment instruction belongs to the external integration layer instruction, and the core business management logic algorithm includes: A data format conversion function is established by using a data mapping rule system; A standardized algorithm of the third-party interface adaptation layer is generated based on the data format conversion function; The standardized algorithm of the third-party interface adaptation layer is included in the core business management logic algorithm; A configuration module of full-dimensional visualization parameters is generated based on the data information of the database of the back-end service module; The third-party interface module and the configuration module of full-dimensional visualization parameters are adapted by using the core business management logic algorithm.

6. The method of big data visualization configuration of claim 5, wherein, The core business management logic algorithm is used to judge whether the adjustment instruction belongs to the external integration layer instruction, including: A structured data of the adjustment instruction is selected, and geometric parameters contained in the structured data are extracted, including the center coordinates of the circle, the radius value, and the polygon vertex coordinate sequence; each edge of the polygon is traversed, the intersection coordinates of each edge and the circle are calculated, and the effective intersection points within the range of the edge line segment are selected; Based on the preset tolerance threshold, the adjacent arc segments are merged to generate a standardized geometric segment set; based on the standardized geometric segment set, the distance between each data point and the center of the circle is calculated, and the relative position relationship between each data point and the target circular region is determined by comparing the distance with the radius value; According to the relative position relationship, a position identifier is assigned to each data point to establish a mapping relationship between the data points and the standardized geometric segments; when it is detected that more than a threshold proportion of data points are located outside the circular region, it is determined that the structured data belongs to the external integration layer instruction. If the selected structured data is determined to belong to the external integration layer instruction, the selected structured data is converted into a standardized data format according to a mapping relationship between a standardized geometry fragment set and a position identifier; if the selected structured data is not determined to belong to the external integration layer instruction, the structured data is processed by calling an internally encapsulated standardized interface.

7. The method of big data visualization configuration of claim 6, wherein, The flow support script based on the tourism data interface editing instruction and the core business management logic algorithm calls a back-end service module and extracts template data connected to a database, including: Parsing attribute configuration of the tourism data interface editing instruction; Based on the attribute configuration, component content configured by the attribute configuration is called; the component content includes one or more of picture materials, table materials and chart materials.

8. The method of big data visualization configuration of claim 7, wherein, The third-party database is incorporated into the core business management logic algorithm to generate one or more saving templates, including: Establishing a dependency of the core business management logic algorithm; Using a standardized algorithm of a third-party interface adaptation layer, the third-party database is taken as the dependency of the core business management logic algorithm; According to an adjustment instruction, the third-party database is called; Data information of the third-party database is incorporated into the dependency of the core business management logic algorithm through the third-party interface adaptation layer.

9. A system for big data visualization configuration, characterized in that, It includes: A server configured to perform the method of any one of claims 1 to 8; and A memory in communication with the server.

Citation Information

Patent Citations

  • Draggable combined visual large screen system and method based on MVVM

    CN115543286A