Vector data display method and device and medium

Abstract

The invention discloses a vector data display method and device and a medium, and the method comprises the steps: analyzing multi-format vector data into PostGIS spatial data, and storing the PostGIS spatial data to a PostGIS database; the deployed GeoServer is connected with a PostGIS (Geographic Information System) database; in a GeoServer, according to a preset service logic, performing layer grouping on the vector data; naming each layer group, and adding metadata to each layer group according to the naming information of the layer group so as to publish the layer group as a map service; in the front-end Web application, a map service is accessed through OpenLayers; and when a screening condition request is received, according to the naming information and the metadata of the layer groups, screening a target layer group meeting a condition, and displaying the target layer group in the front-end Web application. The vector data can be efficiently and flexibly displayed.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a vector data display method, device and medium. Background Art

[0002] When traditional Web technologies display vector data, the formats of vector data from different sources vary. Due to the large amount of data and complex formats, the data often loads slowly and has low rendering efficiency, affecting the user experience.

[0003] In addition, existing layer management functions can usually only filter data in a fixed way, and users cannot customize the filtering rules, resulting in a lack of flexibility and an inability to quickly filter data according to specific rules.

[0004] In summary, a solution that is compatible and can efficiently and flexibly display vector data is needed. Summary of the Invention

[0005] Embodiments of the present application provide a vector data display method, device, and medium for solving the problems of slow loading of vector data display and inability to flexibly filter vector data.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] On the one hand, an embodiment of the present application provides a vector data display method, which includes: parsing multi-format vector data into PostGIS spatial data, and storing the PostGIS spatial data in a PostGIS database; connecting a deployed GeoServer to the PostGIS database; in the GeoServer, grouping the vector data into layers according to preset business logic; naming each layer group, and adding metadata to each layer group based on the naming information of the layer group, so as to publish the layer group as a map service; in a front-end Web application, accessing the map service through OpenLayers; when receiving a filtering condition request, filtering the target layer group that meets the conditions based on the naming information and metadata of the layer group, and displaying the target layer group in the front-end Web application.

[0008] In one example, parsing the multi-format vector data into PostGIS spatial data specifically includes: extracting geometric information and attribute information of the data from the multi-format vector data; and determining a PostGIS spatial data type that matches the data based on the geometric information and attribute information of the data.

[0009] In one example, the vector data is grouped into layers according to the preset business logic, specifically including: according to the first preset business logic, the vector data is configured into different independent layers, and a display style is configured for each independent layer; according to the second preset business logic, multiple related independent layers are merged to obtain different layer groups.

[0010] In one example, each layer group is named, and metadata is added to each layer group based on the naming information of the layer group, specifically including: determining a layer group naming specification including a business prefix and a classification identifier; naming the layer group according to the layer group naming specification; and adding metadata to each layer group based on the classification identifier of each layer group.

[0011] In one example, after publishing the layer group as a map service, the method further includes: generating map tiles according to a set map zoom level and geographic range, and caching the map tiles to a preset cache directory.

[0012] In one example, the method of screening eligible target layer groups based on the naming information and metadata of the layer groups and displaying the target layer groups in the front-end web application specifically includes: screening eligible target layer groups based on the naming information and metadata of the layer groups; returning the map tiles of the target layer groups to OpenLayers; splicing the map tiles of the target layer groups through OpenLayers, and displaying the spliced ​​map tiles in a map container according to the initial default view information.

[0013] In one example, accessing the map service through OpenLayers in the front-end Web application specifically includes: creating a map container through the OpenLayers API in the front-end Web application; connecting OpenLayers with the GeoServer to load the map service published by the GeoServer; and configuring the initial default view information of the map.

[0014] In one example, connecting the deployed GeoServer to the PostGIS database specifically includes: after deploying GeoServer, configuring the connection parameters of the PostGIS database; the connection parameters include the database name, port and host name; and connecting the GeoServer to the PostGIS database according to the connection parameters.

[0015] On the other hand, an embodiment of the present application provides a vector data display device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a vector data display method described in any one of the above items.

[0016] On the other hand, an embodiment of the present application provides a vector data display non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions can execute any of the above-mentioned vector data display methods.

[0017] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0018] By parsing multi-format vector data into PostGIS spatial data and combining the back-end GeoServer service with the front-end OpenLayers, efficient display of vector data in web browsers is achieved, breaking through the limitations of traditional web technology in vector data processing.

[0019] Specifically, the system's flexibility and data compatibility are enhanced through the parsing and storage of multiple common vector data formats, making it easier for users to access data from different sources, thereby enabling compatibility with common vector data formats. Standardized layer group names and metadata extensions enable quick name-based filtering, allowing users to dynamically load data from specific categories based on their needs. This improves data management and display efficiency and optimizes layer management capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solution of the present application, some embodiments of the present application will be described in detail below with reference to the accompanying drawings, in which:

[0021] Figure 1 A flowchart of a vector data display method provided in an embodiment of the present application;

[0022] Figure 2 A schematic structural diagram of a vector data display device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] To make the objectives, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0024] Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0025] Figure 1 This is a flow chart of a vector data display method provided in an embodiment of the present application. Certain input parameters or intermediate results in the process allow for manual intervention and adjustment to help improve accuracy.

[0026] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For ease of understanding and description, the following embodiments are described in detail using a server as an example.

[0027] It should be noted that the server can be a single device or a system composed of multiple devices, that is, a distributed server, and this application does not make any specific restrictions on this.

[0028] It should be noted that the following are explanations of key terms.

[0029] Vector data: Vector data is a data type that represents geographic spatial information through geometric elements such as points, lines, and surfaces. It has precise coordinates and topological relationships and is widely used in geographic information systems (GIS), map drawing, and other fields. It can accurately describe the shape, location, and attributes of geographic entities.

[0030] GeoServer: GeoServer is an open source server software for publishing and editing geospatial data. It supports multiple data formats and protocols and can convert geographic data into web services for front-end applications to access and display.

[0031] PostGIS: PostGIS is an extension of the PostgreSQL database used to process geographic spatial data. It provides a rich set of spatial data types and functions, supports spatial query and analysis, and can efficiently store and manage vector data.

[0032] Tile technology: Tile technology is a technology used to optimize map loading and display. It divides the map into multiple small blocks (tiles) and loads the corresponding tiles on demand according to the user's view range and resolution, reducing data transmission volume and improving loading speed and user experience.

[0033] WMS (Web Map Service): WMS is a web service specification for providing map images. Clients can obtain map images of specific geographic areas and layers by requesting WMS services. It is often used to display the visualization effects of geographic spatial data.

[0034] WFS (Web Feature Service): WFS is a Web service specification for providing access to geographic feature data, allowing clients to obtain, edit, and query geographic vector data, and supporting data interaction and sharing.

[0035] Web display: Web display refers to the way of accessing and presenting information through an Internet browser. Users can access data and applications on the server by entering the URL. It has the advantages of cross-platform and convenient access, allowing users to obtain and interact with data without installing specific software.

[0036] Layers: In GeoServer, layers are a way to organize and present geographic data. They encapsulate geographic data stored in a data source (such as a PostGIS database) and give it visual styles and attribute information for display on a map. A layer can correspond to a table in a database or a set of related geographic data, and can be configured according to different business needs, including setting the layer's display range, projection mode, annotation style, etc. Multiple layers can also be combined into layer groups for management and display.

[0037] Layer group: A logical collection of multiple related layers in GeoServer. Layer groups are constructed based on specific business logic or data characteristics, such as time (e.g., "map1_2024" contains all data for 2024), geographic region, data type, and other rules. By centrally managing and manipulating layer groups, batch control of multiple layers is achieved, streamlining the map configuration process. In web presentations, users can quickly retrieve a group of related layer data by calling the layer group name, enabling the filtering and display of specific data, improving the efficiency of data management and map presentation.

[0038] Shapefile: Shapefile is a geospatial vector data storage format consisting of multiple files. It is widely used in the GIS field to store the geometric information and attribute information of geographic features.

[0039] Figure 1 The process in includes the following steps:

[0040] S101: Parse multi-format vector data into PostGIS spatial data, and store the PostGIS spatial data in a PostGIS database.

[0041] In some embodiments of the present application, geometric information and attribute information of the data are extracted from multi-format vector data, and then, a PostGIS spatial data type that matches the data is determined based on the geometric information and attribute information of the data.

[0042] In other words, vector data (e.g., Shapefile or GeoJSON format) is parsed and stored in a PostGIS database. During the parsing process, the geometric information (points, lines, and surfaces) and attribute information of the data are extracted and stored according to the PostGIS spatial data type to ensure efficient spatial indexing and querying of the data.

[0043] It should be noted that the business system can also interact with PostGIS through database connections (such as JDBC) to implement operations such as adding, deleting, modifying, and querying vector data. The business layer can perform pre-processing such as filtering and conversion on the data as needed to provide support for subsequent map services.

[0044] S102: Connecting the deployed GeoServer to the PostGIS database.

[0045] In some embodiments of the present application, after deploying GeoServer, the connection parameters of the PostGIS database are configured. Then, GeoServer is connected to the PostGIS database according to the connection parameters.

[0046] It should be noted that the connection parameters include database name, port, host name, user name and password, etc., to ensure that GeoServer can access the stored vector data.

[0047] S103: In the GeoServer, the vector data is grouped into layers according to a preset business logic; each layer group is named, and metadata is added to each layer group according to the naming information of the layer group, so as to publish the layer group as a map service.

[0048] In some embodiments of the present application, vector data is configured into different independent layers according to the first preset business logic, and a display style is configured for each independent layer, such as color, line type, and symbol.

[0049] In addition, according to the second preset business logic, multiple related independent layers are merged to obtain different layer groups.

[0050] It should be noted that related layers can be combined into layer groups for easier unified management and publishing. For example, all data layers for the same year can be grouped into one layer group.

[0051] In some embodiments of the present application, the layer group name uses the format of "{business prefix}_{classification identifier}". For example, "map1_2024" represents a layer group that includes data for 2024. The classification identifier can be year, region, business type, etc., defined according to actual needs.

[0052] It's important to note that the business prefix identifies the business module, project, or function to which the data belongs (similar to a "namespace") to avoid name conflicts between layer groups of different businesses. The classification identifier is used to annotate the core classification attributes of the layer group (such as year, region, business type, etc.), making the name self-explanatory through a unified format.

[0053] Based on this, we determined the naming convention for layer groups, including the business prefix and classification identifier. We then named the layer groups according to the naming convention. Then, we added metadata to each layer group based on its classification identifier.

[0054] It should be noted that metadata is added to each layer group in GeoServer to record the classification type for subsequent filtering. The classification type (such as "year" or "region") and the specific value (such as "2024" or "Beijing") are clearly marked.

[0055] It should be noted that metadata is independent of the name and can store more complex classification information (such as descriptions of classification types and multiple classification dimensions). When the naming conventions are not sufficient to describe the classification logic (such as multi-level classification and fuzzy matching), metadata provides more flexible filtering conditions, the name remains concise, and complex classification logic is managed independently through metadata (for example, 2023 in the name may correspond to the "year" or "version number" in the metadata, and the semantics need to be clarified through metadata).

[0056] In some embodiments of this application, configured layers or layer groups are published as map services in GeoServer. Multiple service types are supported, such as WMS (Web Map Service) and WFS (Web Feature Service). WMS provides map images, while WFS provides vector data itself, meeting different application requirements.

[0057] When configuring services in GeoServer, you can dynamically filter layer groups by layer name. For example, you can use "map1_2024" to obtain all layer group data with the year 2024.

[0058] It should be noted that when directly loading a complete large-size map (such as a global map), the server needs to render the entire map data in real time, and the user's browser also needs to load an extremely large image, resulting in slow loading and lag.

[0059] Based on this, in order to optimize the loading performance of large maps, the map is "cut into small pieces" (tiles), generated and stored in advance, and small pieces are loaded on demand when users browse, just like puzzle pieces. Figure 1 This way you can quickly piece together a complete map.

[0060] The tile cache feature is enabled in GeoServer. Tiles are pre-generated based on the map's zoom level and extent and stored in a cache directory. When a user requests a map, the tiles are directly read from the cache, reducing real-time rendering time.

[0061] Based on this, map tiles are generated according to the set map zoom level and geographic range, and the map tiles are cached to the preset cache directory.

[0062] For example, different zoom levels correspond to different map scales (similar to zooming in and out on a map). For example: Zoom level 0 shows the entire Earth, with large tiles (e.g., 256x256 pixels) and a small number of tiles (one or four). Zoom level 18 shows a specific street, with small tiles and a very large number (perhaps millions). The map range is a country, city, etc.

[0063] S104: In the front-end web application, access the map service through OpenLayers.

[0064] In some embodiments of the present application, a map container is created in a front-end web application using the OpenLayers API. OpenLayers is then connected to GeoServer to load the map service published by GeoServer. The initial default view information for the map is then configured.

[0065] In other words, in the front-end web application, introduce the OpenLayers library. Using the OpenLayers API, create a map container and load the WMS service published by GeoServer. Set the initial view of the map (such as the center point coordinates and zoom level) to implement basic map display functions.

[0066] In addition, interactive functions are implemented: using OpenLayers' interactive components, map panning, zooming, click query and other functions are added. For example, when a user clicks a feature on the map, the detailed attribute information of the feature is obtained through the WFS service and displayed on the front end.

[0067] Additionally, tile technology has been optimized: OpenLayers supports on-demand tile loading. When the user pans or zooms the map, the system automatically requests tiles for the required area, stitching and displaying them on the front end. By properly configuring tile caching strategies, network requests are reduced, improving map loading speeds.

[0068] In addition, the filter interface is integrated: a filter condition input box or drop-down menu is provided on the front end, and users can select the classification type (such as year) and the corresponding value (such as 2024). The front end combines the filter parameters into the corresponding layer name and dynamically loads the layer group data that meets the conditions.

[0069] S105: When a filtering condition request is received, target layer groups that meet the conditions are filtered according to the naming information and metadata of the layer groups, and the target layer groups are displayed on the front-end Web application.

[0070] In some embodiments of the present application, a target layer group that meets the criteria is screened based on the layer group's naming information and metadata. The target layer group's map tiles are then returned to OpenLayers. OpenLayers then stitches the target layer group's map tiles together, and the stitched map tiles are displayed in a map container based on the initial default view information.

[0071] To sum up, the storage and management of vector data: using the spatial data management capabilities of PostGIS to achieve efficient storage and query of vector data.

[0072] Configuration and optimization of GeoServer: Rationally configure GeoServer layers and tile caches to ensure the performance and stability of map services.

[0073] Collaboration between front-end and back-end: Through the seamless connection between OpenLayers and GeoServer, smooth display and interaction of vector data on the front-end are achieved.

[0074] Layer group naming conventions and filtering logic: Define the format specifications for layer group names and implement dynamic filtering based on these specifications on the backend and frontend.

[0075] It should be noted that although the embodiments of this application are based on Figure 1 Steps S101 to S105 are described in sequence, but this does not mean that steps S101 to S105 must be performed in a strict order. Figure 1 The order shown in FIG1 is to introduce and explain step S101 to step S105 in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S105 can be appropriately adjusted according to actual needs.

[0076] pass Figure 1This method, by parsing multi-format vector data into PostGIS spatial data and combining the back-end GeoServer service with the front-end OpenLayers, achieves efficient display of vector data in Web browsers, breaking through the limitations of traditional Web technology in vector data processing.

[0077] Specifically, the system's flexibility and data compatibility are enhanced through the parsing and storage of multiple common vector data formats, making it easier for users to access data from different sources, thereby enabling compatibility with common vector data formats. Standardized layer group names and metadata extensions enable quick name-based filtering, allowing users to dynamically load data from specific categories based on their needs. This improves data management and display efficiency and optimizes layer management capabilities.

[0078] In addition, tile technology is used to divide large maps into small tiles for loading and display, which reduces the amount of single data transmission and rendering complexity, significantly improves the loading speed and response performance of the map, improves the user experience, and optimizes the loading and display performance of large maps.

[0079] In summary, the vector data display architecture based on PostGIS and GeoServer: This architecture implements full-process support for the storage, management, publishing and display of vector data, and is innovative and practical.

[0080] The application method of tile technology in vector data display: including tile generation, caching and on-demand loading strategies, which effectively improves the display performance of large maps.

[0081] Compatible processing technology for multi-format vector data: including methods of data parsing, conversion and storage, to ensure that the system can support the access and processing of multiple vector data formats.

[0082] Dynamic filtering technology based on layer group name specifications: including naming rules, metadata extensions, and front-end and back-end interaction logic, realizes efficient data filtering and display.

[0083] It can be seen that it effectively solves the performance bottlenecks and compatibility issues of traditional Web vector data display, and has the advantages of compatibility with multiple vector data formats, significant performance optimization, and good user experience. It provides WebGIS applications with efficient and stable vector data display capabilities and can be widely used in geographic information systems, map applications and other fields.

[0084] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0085] Figure 2 A schematic diagram of the structure of a vector data display device provided in an embodiment of the present application includes:

[0086] at least one processor; and,

[0087] a memory communicatively connected to the at least one processor; wherein,

[0088] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform any one of the above-mentioned vector data display methods.

[0089] Some embodiments of the present application provide a vector data display non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions can execute any of the above-mentioned vector data display methods.

[0090] The various embodiments in this application are described in a progressive manner. Similar portions between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device and medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant portions, refer to the descriptions of the method embodiments.

[0091] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects to their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0092] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0093] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1A device that provides the functions specified in a block or multiple blocks.

[0094] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

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

[0096] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0097] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0098] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0099] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0100] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modifications, equivalent replacements, improvements, etc. made within the technical principles of the present application should fall within the scope of protection of the present application.

Claims

1. A vector data display method, characterized in that: The method comprises: Parsing multi-format vector data into PostGIS spatial data, and storing the PostGIS spatial data in a PostGIS database; Connect the deployed GeoServer to the PostGIS database; In the GeoServer, the vector data is grouped into layers according to a preset business logic; each layer group is named, and metadata is added to each layer group according to the naming information of the layer group, so as to publish the layer group as a map service; In the front-end web application, access the map service through OpenLayers; When a filtering condition request is received, target layer groups that meet the conditions are filtered according to the naming information and metadata of the layer groups, and the target layer groups are displayed on the front-end Web application.

2. The method according to claim 1, characterized in that The parsing of multi-format vector data into PostGIS spatial data specifically includes: Extract geometric and attribute information from multi-format vector data; According to the geometric information and attribute information of the data, the PostGIS spatial data type that the data matches is determined.

3. The method according to claim 1, characterized in that The layer grouping of the vector data according to the preset business logic specifically includes: According to a first preset business logic, the vector data is configured into different independent layers, and a display style is configured for each independent layer; According to the second preset business logic, multiple related independent layers are merged to obtain different layer groups.

4. The method according to claim 1, wherein The above steps are to name each layer group and add metadata to each layer group based on the naming information of the layer group, including: Determine the naming conventions for layer groups, including business prefixes and classification identifiers; Naming the layer group according to the layer group naming specification; Add metadata to each layer group based on its classification identifier.

5. The method according to claim 1, wherein After publishing the layer group as a map service, the method further includes: Generate map tiles according to the set map zoom level and geographic range, and cache the map tiles to a preset cache directory.

6. The method according to claim 5, characterized in that The filtering of target layer groups that meet the conditions according to the naming information and metadata of the layer groups, and displaying the target layer groups in the front-end web application specifically includes: Filter target layer groups that meet the conditions based on the naming information and metadata of the layer groups; Return the map tiles of the target layer group to OpenLayers; The map tiles of the target layer group are spliced ​​together using OpenLayers, and the spliced ​​map tiles are displayed in a map container according to initial default view information.

7. The method according to claim 1, characterized in that In the front-end web application, accessing the map service through OpenLayers specifically includes: In the front-end web application, create a map container through the OpenLayers API; Connect OpenLayers to the GeoServer to load the map service published by the GeoServer; Configure the initial default view information of the map.

8. The method according to claim 1, characterized in that Connecting the deployed GeoServer to the PostGIS database specifically includes: After deploying GeoServer, configure the connection parameters of the PostGIS database; the connection parameters include database name, port, and host name; According to the connection parameters, the GeoServer is connected to the PostGIS database.

9. A vector data display device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the vector data display method according to any one of claims 1 to 8.

10. A vector data display non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer-executable instructions can execute the vector data display method described in any one of claims 1 to 8.

Images