CN114153437A - WEBGIS compatible system, method, device and storage medium - Google Patents

Abstract

The invention discloses a WEBGIS compatible system, comprising: the domain abstraction interface is used for receiving a WEBGIS control instruction of a specified type sent by an external service system; the WEBGIS control object converts a WEBGIS control instruction of a specified type into a specific WEBGIS platform control instruction; and the specific WEBGIS platform is used for executing the WEBGIS operation according to the specific WEBGIS platform control instruction. According to the invention, a unified domain abstraction interface is set to receive WEBGIS control instructions of an external business system, and compatibility among different WEBGIS platforms is realized through platform packaging, so that the platform is not required to be replaced, and the original WEBGIS instruction codes are not required to be replaced.

Description

WEBGIS compatible system, method, device and storage medium

Technical Field

The present invention relates to webbios, and more particularly, to a web bios compatible system, method, apparatus, and storage medium.

Background

WebGIS refers to a Web-based GIS technology, and is a technology for interacting with a GIS server in a browser by using an HTTP protocol and presenting GIS information in a webpage.

At present, WebGIS secondary development platforms are very abundant, and each large GIS manufacturer has own WebGIS secondary development platform, such as ESRI, Supermap and the like; many internet map manufacturers also provide their WebGIS secondary development platforms, such as Baidu and God; in addition, some open-source WebGIS secondary development platforms such as OpenLayers, leaflets, Mapbox GL JS, CesiumJS and the like exist, map types and protocols supported by different development platforms are different, and realized GIS functions are different, for example, some support only 2D, and some support 2D/3D.

In the face of such numerous WebGIS development platforms, service system developers often face a difficult choice because, on one hand, the developers face various service requirements of different users, and on the other hand, the developers also consider the capability differences of different WebGIS platforms, and if the originally selected WebGIS platform cannot meet the requirements of new projects, the developers face the problem of platform replacement. For an enterprise, the WebGIS platform is replaced, and not only is the learning cost brought by adapting to a new framework of a developer, but also a series of workloads such as code rewriting, testing and the like are carried out.

Disclosure of Invention

In order to solve the technical problem that different WEBGIS platforms are incompatible with each other under the prior art, so that code rewriting is required, the invention provides a WEBGIS compatible system, which comprises the following components:

the domain abstraction interface is used for receiving a WEBGIS control instruction of a specified type sent by an external service system;

the abstract packaging is used for constructing an abstract platform packaging rule according to the field abstract interface;

the platform package is used for generating specific platform package according to the abstract platform package rule, generating a WEBGIS control object by using the specific platform package, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform control instruction by using the WEBGIS control object;

and the specific WEBGIS platform is used for executing the WEBGIS operation according to the specific WEBGIS platform control instruction.

In the technical scheme, a uniform domain abstract interface is set on the basis of the functions of each WEBGIS platform and is used for receiving a WEBGIS control instruction of an external service system, and then the WEBGIS control instruction is converted into a specific WEBGIS instruction which can be identified for specific WEBGIS through platform packaging, so that the compatibility among different WEBGIS platforms is realized, and even if the platforms need to be replaced, the original WEBGIS instruction codes do not need to be replaced;

preferably, the platform is packaged as a class library for implementing the specified type of webbis control instruction through the particular webbis platform; the class library is a JavaScript class library.

Further preferably, the domain abstraction interface is an interface defining the WEBGIS platform control instruction of the specified type;

the platform encapsulation inherits from the domain abstraction interface.

In the further preferable technical scheme, through the design mode of the abstract object generator and the specific package, WEBGIS instructions of different target platforms can be simply and effectively converted, maintainability is high, and required cost is low

Further preferably, the domain abstraction interface is used for generating a service WEBGIS object, and the platform package generates a target platform WEBGIS object according to the service WEBGIS object;

the service webbios object specifically includes: a map object for presenting a target map;

the layer object is a certain type of object presented on the target map, and specifically comprises one or more of a park and a building;

the event object specifically comprises one or more of a map moving event and a mouse clicking event;

the geographic object specifically comprises one or more of Geometry and Feature;

the symbolic object is a point map object required by point scattering on a map;

the popup frame object is an information frame object popped up when the symbol object is clicked;

and the style object is a rendering style of the point, line and surface element of the map object.

Preferably, the specific WEBGIS platform is a webbios platform comprising: one of OpenLayers platform and Mapbox platform.

Preferably, the webbios control instruction includes: zooming in, zooming out, and roaming.

Further preferably, the webbios control instruction further includes: specific plotting instructions, domain-specific object instructions, specific path showing instructions, specific animation instructions.

In another aspect, a webbios compatible method is provided, including:

receiving a WEBGIS control instruction of a specified type sent by an external service system;

constructing an abstract platform packaging rule according to the field abstract interface;

generating specific platform packaging according to the abstract platform packaging rule, generating a WEBGIS control object by using the specific platform packaging, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform control instruction by using the WEBGIS control object;

and executing WEBGIS operation according to the specific WEBGIS platform control instruction.

In another aspect, a webbios compatible device is provided, comprising a memory and a processor and a computer program stored on the memory;

the computer program is configured to implement the steps of a websis compatible method when called by a processor.

In another aspect, there is provided a storage medium characterized by: the storage medium has stored therein a computer program configured to implement the steps of a websis compatible method when invoked by a processor.

The invention at least comprises the following technical effects:

(1) on the basis of the functions of each WEBGIS platform, a uniform domain abstract interface is set for receiving a WEBGIS control instruction of an external service system, and then the WEBGIS control instruction is converted into a specific WEBGIS instruction which can be identified for specific WEBGIS through platform packaging, so that the compatibility among different WEBGIS platforms is realized, and even if the platforms need to be replaced, the original WEBGIS instruction codes do not need to be replaced;

(2) through the design mode of the abstract object generator and the specific package, WEBGIS instructions of different target platforms can be simply and effectively converted, maintainability is high, and required cost is low.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic structural view of example 1 of the present invention;

fig. 2 is an illustration diagram of a user perspective implementation flow in embodiment 1 of the present invention;

FIG. 3 is a diagram for explaining the operation of the program in embodiment 1 of the present invention;

fig. 4 is a schematic flow chart of embodiment 2 of the present invention.

The system comprises a domain abstraction interface 1, a platform package 2 and a specific WEBGIS platform 3.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically depicted, or only one of them is labeled. In this document, "one" means not only "only one" but also a case of "more than one".

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

In addition, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.

Example 1:

as shown in fig. 1, the present embodiment provides a webbios compatible system, which includes:

the domain abstraction interface 1 is used for receiving a WEBGIS control instruction of a specified type sent by an external service system; (ii) a

The abstract packaging is used for constructing an abstract platform packaging rule according to the field abstract interface 1;

the platform package 2 is used for generating a specific platform package according to the abstract platform package rule, generating a WEBGIS control object by using the specific platform package, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform 3 control instruction by using the WEBGIS control object;

and the specific WEBGIS platform 3 is used for executing the WEBGIS operation according to the control instruction of the specific WEBGIS platform 3.

WebGIS refers to a Web-based GIS technology, and is a technology for interacting with a GIS server in a browser by using an HTTP protocol and presenting GIS information in a webpage. However, since each large GIS manufacturer has its own WebGIS secondary development platform, and different development platforms support different map types and protocols, the GIS functions implemented are also different, and a service system developer needs to meet various service requirements of different users on one hand and also needs to consider the capability differences of different WebGIS platforms on the other hand, and needs to change platforms if the originally selected WebGIS platform cannot meet the requirements of new projects. For enterprises, not only is the learning cost brought by adapting a new framework of developers, but also a series of workloads such as code rewriting and testing are realized by replacing the WebGIS platform.

The domain abstraction interface 1 defines the basic operations of the WebGIS and the special requirements of the industry for the WebGIS. The abstract interface is designed for services, only functions required by the services are defined, and only the interface and no specific implementation are defined. Encapsulation refers to a set of JavaScript class libraries for realizing functions defined in a service interface by adopting a certain WebGIS platform. For example, as shown in fig. 2, if OpenLayers are planned to implement a service function, the WebGIS domain abstract interface is implemented according to OpenLayers. From the dependency relationship, the business system depends on the WebGIS field abstract interface, and the package depends on the WebGIS field abstract interface and a specific WebGIS platform. And the service system does not directly depend on a certain WebGIS platform, thereby achieving the decoupling purpose. Just because the service system does not depend on a specific WebGIS platform, the capability of switching different WebGIS platforms can be realized under the condition of not changing the codes of the service system.

In the embodiment, on the basis of the functions of each WEBGIS platform, a uniform field abstract interface 1 is set for receiving a WEBGIS control instruction of an external service system, and then the WEBGIS control instruction is converted into a specific WEBGIS instruction which can be identified for specific WEBGIS through a platform packaging 2, so that the compatibility among different WEBGIS platforms is realized, and even if the platform needs to be replaced, the original WEBGIS instruction code does not need to be replaced.

Preferably, the platform package 2 is a class library for implementing the WEBGIS control instruction of the specified type through the specific WEBGIS platform 3; the class library is a JavaScript class library. The domain abstract interface 1 is an interface which defines the WEBGIS platform control instruction of the specified type; the platform encapsulation 2 is inherited from the domain abstraction interface 1.

In concrete implementation, the domain abstract interface 1 not only defines basic operations of the map, but also comprises an abstract object generator which defines a creation interface of a basic object. The encapsulation includes an entity object generator, which inherits the abstract object generator and is responsible for initializing the basic object.

In concrete operation, as shown in fig. 3, firstly, a WebGIS domain abstract interface is defined according to business system requirements, and considering that the requirements of each industry for GIS are different, in addition to basic map operation, special requirements of the industry need to be considered, so that the WebGIS domain abstract interface is only applicable to the industry, but not applicable to all industries. Secondly, creating an abstract object generator, and defining various objects required by the map after defining the WebGIS field abstract interface, wherein the abstract object generator is an object generator class used for creating various map objects, and the abstract object generator is only responsible for defining the created interface and is not specifically realized. And thirdly: and creating a package, wherein the package is a set of classes, and a certain WebGIS platform is adopted to realize the functions defined in the WebGIS field abstract interface. For example, a WebGIS domain abstract interface can be realized by adopting OpenLayers SDK. The class in the package needs to inherit the corresponding interface class in the WebGIS field abstract interface and realize the method of the interface class. For example, an IMap interface is defined in the abstract interface of the WebGIS field, and the IMap interface defines a Zoomin () method, so that OLMap inheritance IMap needs to be defined in OpenLayers packaging, and the Zoomin () method is implemented. And finally, creating an entity object generator, aiming at the abstract object generator defined in the WebGIS field abstract interface, defining an entity object generator in the package to inherit the abstract object generator, and realizing the method in the abstract object generator. The service code calls the method of the entity object generator to create various objects.

In the embodiment, through the design of the abstract object generator and the specific package, WEBGIS instructions of different target platforms can be simply and effectively converted, the maintainability is high, and the required cost is low.

Preferably, the domain abstraction interface 1 is used for generating a service WEBGIS object, and the platform package 2 generates a target platform WEBGIS object according to the service WEBGIS object;

the service webbios object specifically includes: a map object for presenting a target map;

the layer object is a certain type of object presented on the target map, and specifically comprises one or more of a park and a building;

the event object specifically comprises one or more of a map moving event and a mouse clicking event;

the geographic object specifically comprises one or more of Geometry and Feature;

the symbolic object is a point map object required by point scattering on a map;

the popup frame object is an information frame object popped up when the symbol object is clicked;

and the style object is a rendering style of the point, line and surface element of the map object.

Generally, the abstract object generator needs to create objects, which include at least the following types: map objects, DIV, base map configuration and the like need to be appointed when creating; the layer object refers to a certain type of object presented on a map, such as a park, a building and the like; event objects such as map movement events, mouse click events, and the like; geographic objects such as Geometry, Feature; a symbol object (Marker) which is a point map object required for scattering points on a map; a Popup object (Popup) which refers to an information frame object that pops up when a Marker object is clicked; the style object is a rendering style of a point, a line and a surface element; and other specific business objects.

Preferably, the specific WEBGIS platform 3 is a WEBGIS platform comprising: one of OpenLayers platform and Mapbox platform. Meanwhile, other platforms such as the Leafelet, the GL JS and the CesiumJS can be selected according to actual conditions, and the platforms can be selected according to actual requirements. When a certain WebGIS platform needs to be switched, only one set of package needs to be compiled aiming at a defined WebGIS field abstract interface and a specific WebGIS platform SDK, and service codes do not need to be changed.

Preferably, the webbios control instruction includes: zooming in, zooming out, and roaming. The webbios control instruction further includes: specific plotting instructions, domain-specific object instructions, specific path showing instructions, specific animation instructions.

Considering that the requirements of each industry on the GIS are different, the special requirements of the industry need to be considered besides the basic map operation, so that the WebGIS domain abstract interface is only applicable to the industry and is not applicable to all industries. The basic map operation comprises conventional map operations such as zooming in, zooming out and roaming; the industry special requirements comprise specific plotting functions, domain objects, path display requirements, animations, various thematic map functions and the like.

Specifically, abstract platform object generator interfaces include, but are not limited to, createGeometry (type: string, coordinates); createmap (options); createfeations (options); createmarker (options); createpopup (options);

createStyle(type:string,options)；getMapType(string)；

WEBGIS Domain abstraction interfaces include, but are not limited to, setResolution (resolution: number); getResolution (); setcenter (lonlat); getCenter (); setZoom (zoom: number); number; panto (lonlat); setextend (); getExtent (); addoverlay (overlay); removeoverlay (overlay); addlayer (layer); removelayer (layer); getOverlayById (id: string); getSize (); removeLayerById (layerId); getLayerById (layerId);

example 2:

the present embodiment provides a webbios compatible method, as shown in fig. 4, including:

s1: receiving a WEBGIS control instruction of a specified type sent by an external service system;

s2: constructing an abstract platform packaging rule according to the field abstract interface 1;

s3: generating specific platform packaging according to the abstract platform packaging rule, generating a WEBGIS control object by using the specific platform packaging, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform 3 control instruction by using the WEBGIS control object;

s4: and executing WEBGIS operation according to the specific WEBGIS platform 3 control instruction.

WebGIS refers to a Web-based GIS technology, and is a technology for interacting with a GIS server in a browser by using an HTTP protocol and presenting GIS information in a webpage. However, since each large GIS manufacturer has its own WebGIS secondary development platform, and different development platforms support different map types and protocols, the GIS functions implemented are also different, and a service system developer needs to meet various service requirements of different users on one hand and also needs to consider the capability differences of different WebGIS platforms on the other hand, and needs to change platforms if the originally selected WebGIS platform cannot meet the requirements of new projects. For enterprises, not only is the learning cost brought by adapting a new framework of developers, but also a series of workloads such as code rewriting and testing are realized by replacing the WebGIS platform.

The domain abstraction interface 1 defines the basic operations of the WebGIS and the special requirements of the industry for the WebGIS. The abstract interface is designed for services, only functions required by the services are defined, and only the interface and no specific implementation are defined. Encapsulation refers to a set of JavaScript class libraries for realizing functions defined in a service interface by adopting a certain WebGIS platform. For example, if OpenLayers are planned to implement the service function, the WebGIS domain abstract interface is implemented according to OpenLayers. From the dependency relationship, the business system depends on the WebGIS field abstract interface, and the package depends on the WebGIS field abstract interface and a specific WebGIS platform. And the service system does not directly depend on a certain WebGIS platform, thereby achieving the decoupling purpose. Just because the service system does not depend on a specific WebGIS platform, the capability of switching different WebGIS platforms can be realized under the condition of not changing the codes of the service system.

In the embodiment, on the basis of the functions of each WEBGIS platform, a uniform field abstract interface 1 is set for receiving a WEBGIS control instruction of an external service system, and then the WEBGIS control instruction is converted into a specific WEBGIS instruction which can be identified for specific WEBGIS through a platform packaging 2, so that the compatibility among different WEBGIS platforms is realized, and even if the platform needs to be replaced, the original WEBGIS instruction code does not need to be replaced.

In a specific operation process, for example, an original Mapbox code is used to be changed to Openlayers, in the specific operation process, before a specific object is created, a switching point from the Mapbox to the Openlayers is selected, then according to an operation of a user, for example, when the user drags a map, a Pan () function interface provided by a domain abstract interface is called, then, a corresponding function of the Openlayers for realizing a dragging action is called through the Pan () function interface of the domain abstract interface, and an actual dragging operation is completed through the function.

Example 3:

the present embodiment provides a webbios compatible device comprising a memory and a processor and a computer program stored on said memory;

the computer program is configured to implement the steps of a webbios compatible method described in embodiment 2 when invoked by a processor.

Example 4:

the present embodiment provides a storage medium having stored therein a computer program configured to implement the steps of a webbios compatible method of embodiment 2 when invoked by a processor.

The device can be a desktop computer, a notebook, a palm computer, a tablet computer, a mobile phone, a man-machine interaction screen and the like. The apparatus may include, but is not limited to, a processor, a memory. Those skilled in the art will appreciate that the device is merely an example and not a limitation of the device, and may include more or less components than those shown, or some components in combination, or different components, as exemplary: the device may also include input/output interfaces, display devices, network access devices, communication buses, communication interfaces, and the like. A communication interface and a communication bus, and may further comprise an input/output interface, wherein the processor, the memory, the input/output interface and the communication interface complete communication with each other through the communication bus. The memory stores a computer program, and the processor is used for executing the computer program stored on the memory to realize the method in the embodiment.

The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a field-Programmable Gate Array (fPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory may be an internal storage unit of the device, exemplary: hard disk or memory of the device. The memory may also be an external storage device of the device, for example: the device comprises a plug-in hard disk, an intelligent memory Card (SMC), a Secure Digital (SD) Card, a flash Card and the like. Further, the memory may also include both internal storage units of the device and external storage devices. The memory is used for storing the computer program and other programs and data required by the device. The memory may also be used to temporarily store data that has been output or is to be output.

A communication bus is a circuit that connects the described elements and enables transmission between the elements. Illustratively, the processor receives commands from other elements via the communication bus, decrypts the received commands, and performs calculations or data processing based on the decrypted commands. The memory may include program modules, illustratively, a kernel (kernel), middleware (middleware), an Application Programming Interface (API), and applications. The program modules may be comprised of software, firmware or hardware, or at least two of the same. The input/output interface forwards commands or data input by a user via the input/output interface (e.g., sensor, keypad, touch screen). The communication interface connects the device with other network devices, user equipment, networks. Illustratively, the communication interface may be by wireOr wirelessly connected to a network to connect to external other network devices or user equipment. The wireless communication may include at least one of: wireless fidelity (_Wifi), Bluetooth (BT), short-range wireless communication technology (NfC), Global Positioning Satellite (GPS) and cellular communications, among others. The wired communication may include at least one of: universal Serial Bus (USB), high-definition multimedia interface (HDMI), asynchronous transfer standard interface (RS-232), and the like. The network may be a telecommunications network and a communications network. The communication network may be a computer network, the internet of things, a telephone network. The device may connect to the network through the communication interface, and a protocol by which the device communicates with other network devices may be supported by at least one of an application, an Application Programming Interface (API), middleware, a kernel, and a communication interface.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/device and method may be implemented in other ways. The above-described apparatus/device embodiments are merely exemplary, and the division of the modules or units is merely an example of a logical division, and there may be other divisions in actual implementation, and it is exemplary that a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated modules/units may be stored in a medium if implemented in the form of software functional units and sold or used as separate products. Based on such understanding, all or part of the flow in the method according to the above embodiments may be implemented by sending instructions to relevant hardware through a computer program, where the computer program may be stored in a medium, and when the computer program is executed by a processor, the steps of the above method embodiments may be implemented. Wherein the computer program may be in source code form, object code form, an executable file or some intermediate form, etc. The medium may include: any entity or device capable of carrying the computer program, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, software distribution medium, etc. It should be noted that the content contained in the medium can be increased or decreased as appropriate according to the requirements of legislation and patent practice in the jurisdiction, and the following are exemplary: in some jurisdictions, in accordance with legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunications signals. It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of program modules is illustrated, and in practical applications, the above-described distribution of functions may be performed by different program modules, that is, the internal structure of the apparatus may be divided into different program units or modules to perform all or part of the above-described functions. Each program module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one processing unit, and the integrated unit may be implemented in a form of hardware, or may be implemented in a form of software program unit. In addition, the specific names of the program modules are only used for distinguishing the program modules from one another, and are not used for limiting the protection scope of the application.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (10)

1. A websis compatible system, comprising:

the domain abstraction interface is used for receiving a WEBGIS control instruction of a specified type sent by an external service system;

the abstract packaging is used for constructing an abstract platform packaging rule according to the field abstract interface;

the platform package is used for generating specific platform package according to the abstract platform package rule, generating a WEBGIS control object by using the specific platform package, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform control instruction by using the WEBGIS control object;

and the specific WEBGIS platform is used for executing the WEBGIS operation according to the specific WEBGIS platform control instruction.

2. A WEBGIS compatible system according to claim 1, wherein the platform is packaged as a class library that implements the specified type of WEBGIS control instructions through the particular WEBGIS platform; the class library is a JavaScript class library.

3. The WEBGIS compatible system of claim 2, wherein the domain abstraction interface is an interface that defines the specified type of WEBGIS platform control instructions;

the platform encapsulation inherits from the domain abstraction interface.

4. The WEBGIS compatible system of claim 3, wherein the domain abstraction interface is configured to generate a business WEBGIS object, and the platform package generates a target platform WEBGIS object according to the business WEBGIS object;

the service webbios object specifically includes:

a map object for presenting a target map;

the layer object is a certain type of object presented on the target map, and specifically comprises one or more of a park and a building;

the event object specifically comprises one or more of a map moving event and a mouse clicking event;

the geographic object specifically comprises one or more of Geometry and Feature;

the symbolic object is a point map object required by point scattering on a map;

the popup frame object is an information frame object popped up when the symbol object is clicked;

and the style object is a rendering style of the point, line and surface element of the map object.

5. The web bios compatible system of claim 1, wherein the particular web platform is a web compatible platform comprising: one of OpenLayers platform and Mapbox platform.

6. The WEBGIS compatible system of claim 1, wherein the WEBGIS control instructions comprise: zooming in, zooming out, roaming, etc.

7. The WEBGIS compatible system of claim 6, wherein the WEBGIS control instructions further comprise: specific plotting instructions, domain-specific object instructions, specific path showing instructions, specific animation instructions.

8. A websis compatible method, comprising:

receiving a WEBGIS control instruction of a specified type sent by an external service system;

constructing an abstract platform packaging rule according to the field abstract interface;

generating specific platform packaging according to the abstract platform packaging rule, generating a WEBGIS control object by using the specific platform packaging, and converting the WEBGIS control instruction of the specified type into a specific WEBGIS platform control instruction by using the WEBGIS control object;

and executing WEBGIS operation according to the specific WEBGIS platform control instruction.

9. A webbios compatible device, comprising: a computer program comprising a memory and a processor and stored on the memory;

the computer program is configured to implement the steps of a websis compatible method of claim 8 when invoked by a processor.

10. A storage medium, characterized by: the storage medium having stored thereon a computer program configured to, when invoked by a processor, perform the steps of a WEBGIS compatible method of claim 8.

Images