ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

NoSQL Graph Databases and the Future of GIS

Coming from a GISer:

[…] I think this type of database (nb graph databases) is the obvious direction that spatial-enabled databases should take. A lot of our spatial analysis tasks involve searching the relationships between data. This could really expand those functions, and potentially make them quicker. Personally, I think this type of database is the obvious direction that spatial-enabled databases should take. A lot of our spatial analysis tasks involve searching the relationships between data. This could really expand those functions, and potentially make them quicker.

[…]

One is topology. What is topology to us but the relationship between different geometries?

[…]

The other possibility that I see with this, is relationships between metadata. Metadata in a GIS is boring. Yes it is important, but no one seems to use it, and it is tedious to create. FGDC is a pain. Metadata through relationships sounds a lot more interesting to me.

via: http://www.boxshapedworld.com/blog/post/NoSQL-the-next-step-in-GIS.aspx