A lot of people say that location-enabled services will be the #### [*] of tomorrow, so is there any Geo NoSQL?
Populating a MongoDB with POIs ☞
What I especially liked is the flexibility you get from this kind of databases (nb MongoDB) and the ease of installation and use. The downside for geographic applications is that at the moment there is no built-in support for geometries.
Using MongoDB to Store Geographic Data ☞
Managing GIS data with NoSQL in circumstances where performances and scalability are a major issue could be the way for the win.
GeoCouch: The future ☞
What I call “complex analytics” is things like: “return all apple trees that are located with a 10km range around buildings that have are over 100m high, but only in countries with a population over 50 million people” is not possible with GeoCouch as you would need the attribute values as well. Those are stored in CouchDB, so you would need to request them. What GeoCouch only supports is a simple: give me all IDs within a bounding box/polygon/radius.
Tokyo Cabinet: Loading and querying point data ☞
I’m going to load 500.000 POIs in a database and query them with a bounding box query. I will use the table database from Tokyo Cabinet because it supports the most querying facilities. With a table database you can query numbers with full matched and range queries and for strings you can do full matching, forward matching, regular expression matching,…
And so the answer is: yes, we do have some Geo NoSQL!