{'fraction_non_alphanumeric': 0.017456359102244388, 'fraction_numerical': 0.0, 'mean_word_length': 4.5, '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}}
I can see for miles: Re-visualizing the internet

The visual representation of a network shows us far more than where nodes are or what types of network links connect them. A network map tells us the information its authors thought was important, and in doing so tells us what message they wished to convey, the level of technical detail they wished to share, and their ability to express this. We have collected a large set of publicly available network maps from a range of operators, countries, and times, and manually transcribed them into a portable data format. The result is a large store of network topology data and associated metadata. In this article we discuss some of the lessons learned both in collecting this data, and in what it can teach us about the priorities of network map makers.