We’ve all been there. You receive a request to create a web map. It takes days, or weeks, creating map services, configuring up your web map, and documenting how to use it. You send it off to the department or team that requested it, and silence.
Very little feedback and hardly any usage. It’s frustrating. You wonder, why was it requested at all?
At geoWidgets, we feel your pain. We’ve identified some reasons why web maps go unused – typically:
- Unfamiliarity with the software;
- Lack of time to learn a new business process; or,
- Users did not read your documentation or attend your training seminar.
We built geoSherpa to change all that. With geoSherpa, there’s no more searching for PDF documentation to find the steps on how to create a report or export data. Regardless of whether your web map is in Web AppBuilder for ArcGIS, Geocortex, or a custom HTML5 web map, we know that you already spent time creating documentation. So, how do you make it better?
In the steps below we’ll provide suggestions on how to empower your users to use your web maps effectively and keep coming back.