Unfortunately, I haven't used mongodb or any other nosql databases for geo stuff, except for Elasticsearch (Lucene), which I mention on the next slide.
Personally, I would opt for a relational database, like PostGIS or MsSQL, because I know they're working well with geodata. Geo is a rather niche topic, and it definitely will be lower priority for database developers, plus it can be difficult to implement properly. This is why many databases don't have geo support. By using a database with not very well developed geo support, I feel like I would put my product at risk. So I'd have to weigh it very carefully.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for your question, Jordon!
Unfortunately, I haven't used mongodb or any other nosql databases for geo stuff, except for Elasticsearch (Lucene), which I mention on the next slide.
Personally, I would opt for a relational database, like PostGIS or MsSQL, because I know they're working well with geodata. Geo is a rather niche topic, and it definitely will be lower priority for database developers, plus it can be difficult to implement properly. This is why many databases don't have geo support. By using a database with not very well developed geo support, I feel like I would put my product at risk. So I'd have to weigh it very carefully.