Maps are a great way to tell stories and illustrate differences between jurisdictional laws. However, there are many user experience challenges when sharing this type of data thus limiting the usefulness of the map and frustrating clients. For example, the Wikipedia page on the Legality of Cannabis by U.S. Jurisdiction. This wiki page provides a good case study for the challenges of publishing map data and why Map Engine, and its customer-focused delivery, can help avoid these pitfalls.

‍

The wiki cannabis page is dominated by a large data table that covers four different aspects of each state's Cannabis law and provides detailed state-specific historical notes and links to further information. In the corner of the page, sits a single non-interactive map. This image has too much information to tell a clear story and simultaneously fails to illustrate the majority of the data in the table that it references. Instead, the map conflates two aspects of the law (Medical and Recreational Use), while completely ignoring the other two items addressed in the table (Transportation and Cultivation).  And since the map is static, it forces users to jump back to the top of the page to reference the map and then search the table below for the related data.

Similarly to this wiki case study, many published '50 State Survey' reports and websites offer the same limited static experience.

With Map Engine you can quickly and easily turn your custom data set into a beautiful map (or four, or ten!) to answer your clients' specific questions and to help them navigate and interpret all of your data. Explore the interactive map below.

‍

This interactive mapping structure allows your clients easy and direct access to all of the data you are delivering in a single frame, at exactly the level of detail they need. Clients will no longer be forced to wade through rows of irrelevant data, or to decipher complex, inscrutable maps to find the specific information they're looking for.

‍