{"id":1610,"date":"2014-11-21T14:15:18","date_gmt":"2014-11-21T12:15:18","guid":{"rendered":"http:\/\/www.webcodegeeks.com\/?p=1610"},"modified":"2014-11-21T20:31:55","modified_gmt":"2014-11-21T18:31:55","slug":"efficiently-paging-geospatial-data-with-mongodb","status":"publish","type":"post","link":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/","title":{"rendered":"Efficiently Paging Geospatial Data With MongoDB"},"content":{"rendered":"

From release 2.6, MongoDB includes a new minDistance<\/code> option for geospatial queries.<\/p>\n

This is exciting because it lets you page through geospatial results very efficiently, and because it’s the first feature I’ve contributed to the database itself.<\/p>\n

I’ll measure how minDistance<\/code> performs and show you an example app.<\/p>\n

Better, Faster<\/h2>\n

I’m going to fill a MongoDB collection with the locations of sidewalk caf\u00e9s in NYC, and declare a 2dsphere<\/code> index on those locations. In Python:<\/p>\n

from pymongo import MongoClient\r\ndb = MongoClient().test\r\ndb.cafes.insert({\r\n    'Entity Name': 'Cafe Mocha, Inc.',\r\n    'Sidewalk Cafe Type': 'Unenclosed',\r\n    'Street Address': '116 2 Avenue',\r\n    'location': {\r\n        'type': 'Point',\r\n        'coordinates': [\r\n            -73.98817410082268,\r\n            40.72788705499784\r\n        ],\r\n    }\r\n})\r\n\r\ndb.cafes.create_index([\r\n    ('location', '2dsphere')])<\/pre>\n
I have info for 1008 caf\u00e9s from NYC Open Data<\/a>. Now I can query for the ten caf\u00e9s nearest Union Square:<\/p>\n
result = db.command(\r\n    'geoNear', 'cafes',\r\n    near={\r\n        'type': 'Point',\r\n        'coordinates': [\r\n            -73.991084,\r\n            40.735863]},\r\n    spherical=True,\r\n    num=10)<\/pre>\n
MongoDB returns them to me sorted from nearest to farthest. The problems start if I want the next<\/strong> 10 results. MongoDB doesn’t support skip<\/code> with geo queries. I can simulate it with the aggregation framework. I query for 20 caf\u00e9s and filter out the first 10 with the aggregation framework’s $skip<\/code> operator:<\/p>\n
result = db.cafes.aggregate([{\r\n    '$geoNear': {\r\n        'near': {\r\n            'type': 'Point',\r\n            'coordinates': [\r\n                -73.991084,\r\n                40.735863]},\r\n        'spherical': True,\r\n        'distanceField': 'dist',\r\n        'num': 20}\r\n}, {\r\n    '$skip': 10\r\n}])<\/pre>\n
This trick (from my colleague Asya Kamsky<\/a>) lets me page through geo results, but it gets slower with bigger skip values. I timed it on a collection of 10,000 random locations:<\/p>\n
\"skip-performance<\/a><\/p>\n
As the $skip<\/code> number grows from zero to 10,000, the duration grows linearly, even though the query always returns 10 results. After all, in order to get those 10 documents, MongoDB must find all the prior documents and pass them through the aggregation pipeline, only to discard them at the $skip<\/code> phase.<\/p>\n
Paging through geo results is obviously useful, so how do we do it efficiently? MongoDB 2.6 comes with a new minDistance<\/code> option for geospatial queries. This is my first contribution to MongoDB’s C++ code\u2014generally I work on Python. Hold your applause, please: I just wired together some mechanisms built by minds greater than mine, and even so I needed a lot of handholding from Hari Khalsa<\/a>. However simple the feature was to implement, it makes paging through geo results much faster.<\/p>\n
Here’s how to page with minDistance<\/code>. I query for the first 10 locations normally. When I want the next 10 locations, I set minDistance<\/code> to the farthest distance I’ve seen so far. So if my 10th result is 268 meters away and has id 42:<\/p>\n
{\r\n    'dis': 268,\r\n    'obj': {\r\n        '_id': 42,\r\n        'Entity Name': 'LM Restaurant Group',\r\n        'Street Address': '120 East 15 Street',\r\n        'location': {\r\n            'type': 'Point',\r\n            'coordinates': [\r\n                -73.98834760821919,\r\n                40.73463761939186\r\n             ]\r\n         }\r\n     }\r\n}<\/pre>\n
… then I set minDistance<\/code> to 268 and query for the next 10 documents. I must also exclude this document’s id to avoid seeing it again in the next batch, since minDistance<\/code> is inclusive.<\/p>\n
ids = [42]\r\n\r\nresult = db.command(\r\n    'geoNear', 'cafes',\r\n    near={\r\n        'type': 'Point',\r\n        'coordinates': [\r\n            -73.991084,\r\n            40.735863]},\r\n    spherical=True,\r\n    minDistance=268,\r\n    query={\r\n        '_id': {\r\n            '$nin': ids}},\r\n    num=10)<\/pre>\n
The farthest document from the first batch is excluded using a “not in” ($nin<\/code>) query. If several documents are equally far away, I’d exclude all their ids. This technique performs quite well on my random collection:<\/p>\n
\"minDistance-performance<\/a><\/p>\n
The first batch performs the same as it did with the aggregation framework, but the final batch takes one tenth the time with minDistance<\/code> as it did with $skip<\/code>: 170ms instead of 1.6 seconds.<\/p>\n
An Example App<\/h2>\n
Paging with minDistance<\/code> requires some futzy code, compared to the straightforward aggregation technique. To work out the kinks, I made an example app with my sidewalk-caf\u00e9 data. You can play with it here:<\/p>\n
http:\/\/emptysqua.re\/geopaging<\/a><\/p>\n
The app uses PyMongo, Flask, and MongoDB. To start, enter a location dense with sidewalk caf\u00e9s, like my zipcode “10009”. The app asks Google for the coordinates of your location, and shows you the 10 nearest caf\u00e9s:<\/p>\n
\"sidewalk-cafes-table\"<\/a><\/p>\n
\"sidewalk-cafes-screenshot\"<\/a><\/p>\n
As you click Next, some Javascript asks the server-side application for the next 10 points. The script keeps track of the farthest distance it has seen so far, and passes that distance to the server when it asks for the next batch. You can see the ring of caf\u00e9s move outwards from the center-point as minDistance<\/code> increases.<\/p>\n
When the script asks the server for the next batch, it also passes the ids of all documents at the current farthest distance, and the server excludes them. Normally this exclusion-list has just one id: the id of the last point retrieved. But the city’s data has some bugs. There are 14 caf\u00e9s with the same geocoordinates, despite distinct addresses. Bruno The King Of Ravioli, for example, is twelve blocks from my beloved Benny’s Burritos, but they’re listed at the same (wrong) geocoordinates on 10th Street near Avenue B. Since they’re at the same coordinates, they have the same distance from your center point. Paging through such data using minDistance<\/code> requires a careful algorithm. In pseudo-Python:<\/p>\n
min_distance = 0\r\nlast_ids = []\r\n\r\ndef get_batch():\r\n    global min_distance, last_ids\r\n\r\n    result = db.command(\r\n        'geoNear', 'cafes',\r\n        near=center_point,\r\n        spherical=True,\r\n        minDistance=min_distance,\r\n        query={\r\n            '_id': {'$nin': last_ids}\r\n        },\r\n        num=10)\r\n\r\n    results = result['results']\r\n    if not results:\r\n        # Finished.\r\n        return []\r\n\r\n    # Last result is farthest.\r\n    new_min_distance = result[-1]['dis']\r\n\r\n    if new_min_distance == min_distance:\r\n        # We're still paging through results\r\n        # all at same distance as previous\r\n        # farthest. Append to last_ids.\r\n        last_ids += [\r\n            r['obj']['_id'] for r in results]\r\n    else:\r\n        # Results in this page are farther\r\n        # than previous page.\r\n        # Replace last_ids.\r\n        min_distance = new_min_distance\r\n        last_ids = [\r\n            r['obj']['_id']\r\n            for r in result['results']\r\n            if r['dis'] == min_distance]\r\n\r\n    return results<\/pre>\n
This takes care of paging forward from the nearest 10 caf\u00e9s to the farthest. How do we go backwards? Unfortunately, the geoNear<\/code> command doesn’t support searching inward from a maxDistance<\/code>: it always iterates from near to far. My solution is simply to cache results as I retrieve them. So when you click Previous in my app, it shows you the previous page from the results it keeps in memory. If you hit Next again, the app checks whether it has the next page of results cached, and if so avoids the round trip to the server.<\/p>\n
What’s Next?<\/h2>\n
Check out my application on GitHub; the most interesting code is the server-side results() function<\/a> which runs the geoNear<\/code> command, and the Javascript getMoreRows() function<\/a> which implements the paging algorithm. Install the current production release of MongoDB<\/a>, make something cool with geo data, and let me know<\/a>.<\/p>\n
\n\n\n\n
Reference: <\/span><\/td>\nEfficiently Paging Geospatial Data With MongoDB<\/a> from our WCG partner<\/a> Jesse Davis at the A. Jesse Jiryu Davis<\/a> blog.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results very efficiently, and because it’s the first feature I’ve contributed to the database itself. I’ll measure how minDistance performs and show you an example app. Better, Faster I’m going to fill a …<\/p>\n","protected":false},"author":29,"featured_media":1650,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[57],"class_list":["post-1610","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nosql","tag-mongodb"],"yoast_head":"\nEfficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026<\/title>\n<meta name=\"description\" content=\"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Efficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026\" \/>\n<meta property=\"og:description\" content=\"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\" \/>\n<meta property=\"og:site_name\" content=\"Web Code Geeks\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/webcodegeeks\" \/>\n<meta property=\"article:published_time\" content=\"2014-11-21T12:15:18+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2014-11-21T18:31:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"150\" \/>\n\t<meta property=\"og:image:height\" content=\"150\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Jesse Davis\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@https:\/\/twitter.com\/jessejiryudavis\" \/>\n<meta name=\"twitter:site\" content=\"@webcodegeeks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jesse Davis\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\"},\"author\":{\"name\":\"Jesse Davis\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/294d6819cb410ef55f273ecf25426c56\"},\"headline\":\"Efficiently Paging Geospatial Data With MongoDB\",\"datePublished\":\"2014-11-21T12:15:18+00:00\",\"dateModified\":\"2014-11-21T18:31:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\"},\"wordCount\":1091,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg\",\"keywords\":[\"MongoDB\"],\"articleSection\":[\"NoSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\",\"url\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\",\"name\":\"Efficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026\",\"isPartOf\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg\",\"datePublished\":\"2014-11-21T12:15:18+00:00\",\"dateModified\":\"2014-11-21T18:31:55+00:00\",\"description\":\"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results\",\"breadcrumb\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage\",\"url\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg\",\"contentUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg\",\"width\":150,\"height\":150},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.webcodegeeks.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"NoSQL\",\"item\":\"https:\/\/www.webcodegeeks.com\/category\/nosql\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Efficiently Paging Geospatial Data With MongoDB\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#website\",\"url\":\"https:\/\/www.webcodegeeks.com\/\",\"name\":\"Web Code Geeks\",\"description\":\"Web Developers Resource Center\",\"publisher\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.webcodegeeks.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\",\"name\":\"Exelixis Media P.C.\",\"url\":\"https:\/\/www.webcodegeeks.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png\",\"contentUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png\",\"width\":864,\"height\":246,\"caption\":\"Exelixis Media P.C.\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/webcodegeeks\",\"https:\/\/x.com\/webcodegeeks\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/294d6819cb410ef55f273ecf25426c56\",\"name\":\"Jesse Davis\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/2db0fdaadd8cd6b86d93e1205e30dd3b43e3c46b91826513ab618934c3db8cf9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/2db0fdaadd8cd6b86d93e1205e30dd3b43e3c46b91826513ab618934c3db8cf9?s=96&d=mm&r=g\",\"caption\":\"Jesse Davis\"},\"description\":\"Jesse is a senior engineer at MongoDB in New York City. He specializes in Python, MongoDB drivers, and asynchronous frameworks.\",\"sameAs\":[\"http:\/\/emptysqua.re\/blog\/\",\"https:\/\/x.com\/https:\/\/twitter.com\/jessejiryudavis\"],\"url\":\"https:\/\/www.webcodegeeks.com\/author\/jesse-davis\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Efficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026","description":"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/","og_locale":"en_US","og_type":"article","og_title":"Efficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026","og_description":"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results","og_url":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/","og_site_name":"Web Code Geeks","article_publisher":"https:\/\/www.facebook.com\/webcodegeeks","article_published_time":"2014-11-21T12:15:18+00:00","article_modified_time":"2014-11-21T18:31:55+00:00","og_image":[{"width":150,"height":150,"url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg","type":"image\/jpeg"}],"author":"Jesse Davis","twitter_card":"summary_large_image","twitter_creator":"@https:\/\/twitter.com\/jessejiryudavis","twitter_site":"@webcodegeeks","twitter_misc":{"Written by":"Jesse Davis","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#article","isPartOf":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/"},"author":{"name":"Jesse Davis","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/294d6819cb410ef55f273ecf25426c56"},"headline":"Efficiently Paging Geospatial Data With MongoDB","datePublished":"2014-11-21T12:15:18+00:00","dateModified":"2014-11-21T18:31:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/"},"wordCount":1091,"commentCount":0,"publisher":{"@id":"https:\/\/www.webcodegeeks.com\/#organization"},"image":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage"},"thumbnailUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg","keywords":["MongoDB"],"articleSection":["NoSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/","url":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/","name":"Efficiently Paging Geospatial Data With MongoDB - Web Code Geeks - 2026","isPartOf":{"@id":"https:\/\/www.webcodegeeks.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage"},"image":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage"},"thumbnailUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg","datePublished":"2014-11-21T12:15:18+00:00","dateModified":"2014-11-21T18:31:55+00:00","description":"From release 2.6, MongoDB includes a new minDistance option for geospatial queries. This is exciting because it lets you page through geospatial results","breadcrumb":{"@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#primaryimage","url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg","contentUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2014\/11\/mongodb-logo.jpg","width":150,"height":150},{"@type":"BreadcrumbList","@id":"https:\/\/www.webcodegeeks.com\/nosql\/efficiently-paging-geospatial-data-with-mongodb\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.webcodegeeks.com\/"},{"@type":"ListItem","position":2,"name":"NoSQL","item":"https:\/\/www.webcodegeeks.com\/category\/nosql\/"},{"@type":"ListItem","position":3,"name":"Efficiently Paging Geospatial Data With MongoDB"}]},{"@type":"WebSite","@id":"https:\/\/www.webcodegeeks.com\/#website","url":"https:\/\/www.webcodegeeks.com\/","name":"Web Code Geeks","description":"Web Developers Resource Center","publisher":{"@id":"https:\/\/www.webcodegeeks.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.webcodegeeks.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.webcodegeeks.com\/#organization","name":"Exelixis Media P.C.","url":"https:\/\/www.webcodegeeks.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png","contentUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png","width":864,"height":246,"caption":"Exelixis Media P.C."},"image":{"@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/webcodegeeks","https:\/\/x.com\/webcodegeeks"]},{"@type":"Person","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/294d6819cb410ef55f273ecf25426c56","name":"Jesse Davis","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/2db0fdaadd8cd6b86d93e1205e30dd3b43e3c46b91826513ab618934c3db8cf9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2db0fdaadd8cd6b86d93e1205e30dd3b43e3c46b91826513ab618934c3db8cf9?s=96&d=mm&r=g","caption":"Jesse Davis"},"description":"Jesse is a senior engineer at MongoDB in New York City. He specializes in Python, MongoDB drivers, and asynchronous frameworks.","sameAs":["http:\/\/emptysqua.re\/blog\/","https:\/\/x.com\/https:\/\/twitter.com\/jessejiryudavis"],"url":"https:\/\/www.webcodegeeks.com\/author\/jesse-davis\/"}]}},"_links":{"self":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts\/1610","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/comments?post=1610"}],"version-history":[{"count":0,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts\/1610\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/media\/1650"}],"wp:attachment":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/media?parent=1610"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/categories?post=1610"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/tags?post=1610"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}