{'fraction_non_alphanumeric': 0.031578947368421054, 'fraction_numerical': 0.0, 'mean_word_length': 4.863013698630137, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
GOOGLE MAPS AND MOBILE DEVICES: CAN JUST ONE GENERIC DESIGN WORK?

The phenomena that is Google Map® has both made mapping more visible and made access to base maps more immediate. The proliferation of mash-ups and other Web-delivered map products that are based on Google maps illustrates this 'use-it-for-everything mapping phenomena. But, can Google's maps be used for everything, including mobile and small-format map delivery platforms? Can we just 'Google it? 
This paper discusses how user/producers have exploited the availability and accessibility of base maps from Google. It explores the numerous small format / mobile applications that have been developed and the content that they deliver. Then it considers whether it is appropriate and 'good' design practice to accept Google maps as an 'underlay' for developing this genre of map products.