The design and implementation of web mapping in the project talk Webgis

Article copyright by the author Xiaohui Li is and the blog park, if reproduced please clearly indicate the source: http://www.cnblogs.com/naaoveGIS/

1. Background information

In general Webgis projects, the flow of the front-end presentation data is basically the first Data warehousing, Service release, and then the front-end call display. What if the user does not have a basic GIS background and needs to quickly display the local Excel or CSV files on the map?

Currently on the market to address this demand for products have been emerging, such as the Mapbox of the Studio,esri portal, Super Map, and the original project manager after the departure of the map without worry and other products. Such products are generally packaged in the concept of cloud services, providing web mapping of local documents, related spatial analysis, data editing, sharing, etc. Here, I use a company project to talk about individual design and implementation of such requirements.

2. Product Design

Studying mature products on the market will find that the 28 law is widespread, such as ESRI's portal provides a lot of spatial analysis capabilities, but these features can be used by users of very low probability, limited to sell products when the account Manager's skill show state. Extracting pervasive functionality, locating users, and combining the needs of the company are the principles that I started designing.

Here first define the user: Company development (goal-data integration, rapid development), engineering colleagues (some needs can be solved independently), users (to solve the user's simple needs).

Based on the above three principles, this paper proposes the concept of product function:

A. Quick display of local files (R & D, engineering, customer).

B. Local document Mapping (R & D, engineering, customer).

C. Basic spatial analysis (R & D, engineering, customer).

D. Data editing (Research and development, engineering, customer).

E. Data sharing

For research and development: to provide data level docking, service level docking, front-end interface docking.

For Engineering: Provides service publishing capabilities.

For customers: Provides front-end view of shared data.

F. Data permissions

For engineering, Customer: Configurable Data View permissions.

3. Product Architecture Design

To the core of the module, the map operations and mapping services are split to create two large modules:

Configure management of whether each function module can be added in the Portal:

4. Design and implementation of local data presentation

Local data presentation is primarily for local CSV and local Excel data, which requires a coordinate field (X, Y) to be added to the map for quick presentation via the Portal:

Design and implementation of 5.WEB cartography 5.1 simple rendering

Simple rendering means that the user can choose to render the fill color, fill transparency, border color, border transparency, and choose whether to use the icon (the icon can be uploaded selection) to show:

5.2 Classification Rendering

Categorical rendering means that a user can check the fields of a category and then render a different display of different thresholds for the field:

6. Design and implementation of spatial analysis 6.1 multi-dimensional analysis

In multi-dimensional analysis, we provide two dimensions of thermal zone display and cluster analysis, and the parameters can be controlled:

6.2 Buffering Analysis

Provides buffer analysis capabilities for points, lines, and polygons for uploading data:

7. Data Management 7.1 Data keyword query

Check the query field, enter the query keyword, you can search out the data to meet the requirements of the results, click on the results panel can be located on the map to the feature:

7.2 Data Editing

Provides added, modified, deleted, and saved functions for data, where the Save function can export the modified data to a CSV file at a cost:

8. Data Sharing 8.1 Design

Choose to use PostGIS to store uploaded data, the main consideration is that you can use GeoServer to publish the uploaded data as a layer directly later. Then three tables were designed to manage the metadata of the data, namely the Tc_user_upload_data,tc_user_upload_data_field,tc_user_upload_data_style table, the three tables, The first one is the data table, style sheet, uploader for the data that is uploaded, the fields owned by each data corresponding to the second table, and the third table stores the style files corresponding to the data. Finally, each data upload, in addition to populating the three metadata table, also generates a data storage table for the data, the table contains the Geom field in the St_geometry format for storage, for later docking with the geographic server.

8.2 implementation

Click the upload button to upload the data to the PG library:

8.3geoserver Release

Release with GeoServer:

Or take advantage of udig distribution with the company's Integrated publishing tools:

Preview in GeoServer:

9. Permissions Configuration

Configure permissions for each post on the service layer:

Browse layers in the layer tree:

10. Extended Design

A. Add the front end to configure the style to read the upload data interface, for the development of the front-end call.

B. Provide a data-level docking solution for the development of special needs.

C. Add more extended GIS functions, such as path correction, contour lines, heat maps, etc.

D. Extended support for more local file formats.

E. Add map Basemap styles to toggle the configuration interface. Replace the map basemap with a vector cut, and configure the vector transduction in YAML format.

-----Welcome reprint, but retain the copyright, please indicate the source in obvious place: http://www.cnblogs.com/naaoveGIS/

The design and implementation of web mapping in the project talk Webgis