{'fraction_non_alphanumeric': 0.01529051987767584, 'fraction_numerical': 0.0030581039755351682, 'mean_word_length': 5.298076923076923, '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}}
Geographic data in a graph oriented database: A study with Neo4j and PostgreSQL

Graph databases, similar to other NoSQL approaches, have emerged as an alternative to solve specific problems ill fitted to relational models. The huge amounts of data produced, and the high capability for horizontal scalability provided by NoSQL databases has led to the increasing adoption of these systems, which can now be adapted to support geographic data. This article presents an analysis on the behavior of a graph oriented geographic databases compared to those designed with a relational model, using the database management systems PostgreSQL/PostGIS and Neo4j.