Making a Web Map to Share Your Analysis Results

Making a web map: how to show your analysis results to others

Making a web map means turning your analysis result into a map on a web page that anyone can zoom and click. You can make one with a QGIS export plugin or a simple web tool, and you must check the location information before you publish it.

In short

  • A web map can be zoomed and clicked, so it is more useful than an image.
  • In QGIS, the qgis2web plugin creates a web map folder.
  • Before publishing, delete or aggregate personal data columns and the locations of vulnerable people.

Have you ever finished a flood risk analysis, captured the result screen and sent it by messenger, only to get the reply "Where is my house on this?" An image shows only the scene the maker chose, so the receiver cannot check the places they are curious about.

A web map solves this problem. With one link, anyone can zoom to the place they want and click a point to see its information. But remember that the moment you publish a map, the locations and attributes inside it are published too. This post covers the flow of making a web map with QGIS and the items you must check before uploading.

aerial city map GIS
Stock photo. Photo: WikiImages / Pixabay

What is the benefit of sharing analysis results as a map instead of an image?

A screenshot shows only the one view the maker chose. An image gets blurry when you zoom in, and the scale or legend can be cut off. With a web map, the receiver can zoom and pan on their own and click points to see attributes. Even for the same predicted flood result, the biggest difference is that people can look up for themselves how far the water reaches on their own street. Because it is shared as one address (URL), files are less likely to get mixed up in several versions, and when you update, you can build it so that only the map at the same address changes. However, a web map is a tool for showing, not for rerunning the analysis, and an image is more convenient for a printed report. So it helps to split the uses: images for meeting materials, web maps for resident guidance and field sharing. A typical use is a guide where residents click shelter locations to check them.

How do I export a web map from QGIS?

In QGIS, many people use a plugin (an extension that adds features) called qgis2web. Search for it and install it under Plugins > Manage and Install Plugins, and it appears under the Web menu. When you run it, a window opens where you choose, for each layer, the attributes to show in the popup and the base map, and you can see a preview on the right. For the base map you can choose a tile map such as OpenStreetMap, and as a rule you should not remove the attribution. When you export, an index.html file and a data folder are created as a set, and you need to upload this folder to a web server or hosting service so that others can see it. Menu names and options can differ slightly depending on the QGIS and plugin versions, so look for the names on your screen. If you export a polygon layer of predicted flood areas together with a point layer of shelters, you get a guide map where people can click the nearest shelter right away.

What simple web map tools can I use without coding?

If QGIS feels like too much, there are tools that work in the browser alone. With geojson.io you can upload a GeoJSON file (a text-based spatial file that holds points, lines and polygons), check it and make simple edits. Google My Maps and uMap make it easy to draw points or areas yourself and create a share link, and services such as ArcGIS Online and Felt offer a more polished display. However, features, pricing and sharing policies change often, so check each service's current guidance before use. How far you can go without an account, and whether saving and sharing need an account, also differ by tool. Also remember that the moment you upload a file, the data sits on an external server. If it is internal data of an organization, first check whether it fits your security rules. I recommend practicing with a few points at first. It fits light uses well, such as quickly sharing a few temporary assembly points with your team during a drill.

What information should I delete or hide when publishing a web map?

Once a map is public, it is hard to take back. First, delete attributes that identify individuals, such as names, phone numbers, detailed addresses and unit numbers. Hiding them only in the popup is not enough. The attributes can remain in the exported data file, so you need to delete the columns themselves. It is safer to show the point locations of vulnerable groups, such as elderly people living alone, people with disabilities and care facility residents, as totals by administrative district or grid cell, and to merge cells with only a few people so that no individual can be inferred. For facilities whose precise location is restricted for security reasons, check the disclosure rules first. Some things you learn only by trying. Open the link in a browser where you are not logged in (a private window), open the files in the exported data folder with a text editor, and search for yourself whether the information you deleted is still there. This check matters especially when you make a map supporting vulnerable groups.

How should I decide the scope of publication and updates?

The scope can roughly be divided into internal to the organization, only people who know the link, and anyone. Letting only people who know the link view it is convenient, but once the link spreads, it is effectively the same as public. The level you choose depends on the sensitivity of the information. Put the date it was made (reference date), the data sources, and the assumptions and limits of the analysis on the map. An old map that looks up to date can mislead decisions. Decide who will update it and how often, make the data files light in case of heavy traffic, and add a line with a contact point so you can receive error reports. For a predicted flood map, place on the first screen which rainfall condition was assumed and a note that the actual flooded area may differ, so that residents neither overtrust nor ignore the risk.

Step by step on screen

The diagram shows the order of the steps and may use a Korean interface. Menu positions are the same in the English interface.

Overview of the steps

  1. Organize the layers
    In the Layers panel, tick only the layers to publish, then right-click a layer > Open Attribute Table and check the name and contact columns.
  2. Delete sensitive columns
    In the Processing Toolbox, search for Drop Field(s), select the name, phone number and detailed address columns, and run it.
  3. Install the plugin
    Plugins > Manage and Install Plugins > in the All tab, search for qgis2web > Install.
  4. Open the export window
    Run Web > qgis2web > Create web map, then choose Leaflet or OpenLayers.
  5. Set the popups
    In Layers and Groups, leave only columns that are safe to publish in each layer's popup fields, then run Export.
  6. Check the result
    Open the index.html in the output folder in a private window, and open the files in the data folder with a text editor to search for the information you deleted.
  7. If the menu names differ
    Check the Installed tab of the plugin manager or the Web menu at the top of QGIS.

Menu names may differ slightly between program versions. The figure above is a diagram that summarizes the order.

Prompts you can copy

Get a checklist that separates the columns to delete from the columns to mask before publishing a web map

You are an assistant who helps protect personal information in spatial data. I want to publish a map related to [target disaster] on the web at [organization name].
Below is a list of the column names of a layer. I have not pasted any actual values or personal data.
Column names: [list the column names separated by commas]
Layer type: [point / line / polygon], contents: [for example, shelters, facilities for vulnerable groups]
Classify each column as delete, process (aggregate or round), or safe to publish, and write the reason in one line each in a table.
At the end, list separately the items that a person must check directly.
Do not give legal interpretations or definitive judgments, and mark the parts that need confirmation by the organization's security or privacy officer.

Get a draft of the notice on the reference date, sources and limits to put on the first screen of a web map

You are a staff member who writes disaster safety notices. Write the notice for [map name], published by [organization name].
Include: reference date [date], data sources [sources], analysis assumptions [for example, rainfall condition], limits, and contact point [contact point].
Write one paragraph of 3 to 5 sentences in a polite tone, and do not use wording that stirs fear or states that people are safe.
Do not invent numbers or organization names that I did not give you, and leave blanks as [ ].
A person must check that the date, sources and limits in the result match reality.

Replace the bracketed parts for your situation. Do not use the answers as they are; check the facts first.

Try it yourself

  • Upload open data to geojson.io, click the points and check which attributes are visible.
  • Export a practice layer from QGIS with qgis2web, then open the files in the data folder with a text editor.
  • Use the attribute table to check whether your own map has any columns that could be personal data.

Common questions

Do I need to know coding to make a web map?
It is not required. Plugins such as qgis2web and browser-based tools let you make one just by using menus. However, if you host it yourself, you need to know how to upload files.
If I hide it in the popup, is personal information not visible?
No. Depending on the tool, hidden attributes can remain in the exported data file. Delete the columns themselves before publishing and open the files directly to check.
Is it safe to let only people who know the link view it?
It is not full protection, because anyone who is given the link can see it. For sensitive information, whatever the scope, it is safer to delete or aggregate it from the start.

A web map is the easiest way to make analysis results reach many people, but the more it shows, the more you need to think about what to hide. Share a map instead of an image, tidy the columns before exporting, and state the reference date and limits after publishing, and you can use it safely. Then how can you collect scattered field information from many people onto a map in real time? A later post in this series covers this.

This is an English adaptation of a post in the Korean GeoAI basics series. The original is here, and more learning materials are on GeoAI for Disaster Safety.

This post was drafted with the help of AI tools and reviewed by the author. Tool features and data portals change over time, so check the official documentation when you practice.

Comments

Popular posts from this blog

What Is GeoAI, and How Does It Help Disaster Safety?

Getting Started with QGIS: What to Do First

Whitebox QGIS Practice 26 — Elevation Statistics of Two Basins: Means of 2,000.1 m and 1,924.3 m, a 76 m Gap