Setting Expectations for a Web-Based Geographic Information System

Almost all of the information and data that we work with as environmental scientists and engineers has a spatial component. Whether it’s water quality collected from a monitoring point, geologic information, or human health surveys, all of this data can be tied to a particular point on Earth. We also have clients and offices located around the world that all need slightly different ways to view and analyze data in order to make informed decisions.

These geographic issues have led us more into the arena of web-based geographic information systems (or Web GIS). These systems work great, especially for teams that are located in different offices, allowing decision makers to quickly evaluate and communicate with staff on the most critical issues affecting their project.

However, we’ve found that it’s critically important to set expectations when developing a Web GIS. Here are a few questions that you should answer before you start development:

• What decisions are you trying to make? Having a clearly defined goal is required for any project but it is particularly helpful to fully define and evaluate the one or two decisions that you are making with a Web GIS. Do you want to evaluate water quality over time? Create geologic cross-sections? Or evaluate infrastructure needs? Picking one or two of these decisions will narrow the scope and increase quality. Also, do not let this defined scope expand unless it is absolutely necessary. Scope creep is an easy way to derail a Web GIS.
• What functionality do you need? Extra functionality is great but it can lead to longer development times resulting in increased costs and missed deadlines. Determining the highest priority functionality that you or your client need, will help answer your team make quicker decisions for the project.
• What data do you want to see? Try to limit the amount of data included in the Web GIS to only the data needed to make a decision. There is really no limit to the amount of information that can be included in these systems but adding every bit of information available will confuse the end user and make it difficult to get an answer, thus defeating the purpose of the Web GIS.

Definitively answering these questions before developing a Web GIS will lead to a better end product for the user, faster development, and better decision making for your project.

Please stay safe and healthy.