mongodb - Difference in $geoWithin and $geoIntersects operators? -


what difference in $geowithin , $geointersects operators in mongodb?

if looking coordinates (using default coordinate reference system), $geowithin , $geointersects return same result.

please correct me if wrong.

any simple use case understanding difference appreciated.

from $geointersects:

selects documents geospatial data intersects specified geojson object; i.e. intersection of data , specified object non-empty. includes cases data , specified object share edge.

from $geowithin:

selects documents geospatial data exists entirely within specified shape.

take following example:

> db.test.drop() > var poly1 = { "type" : "polygon", "coordinates" : [[[0, 0], [3, 0], [0, 3], [0, 0]]] } > var poly2 = { "type" : "polygon", "coordinates" : [[[1, 1], [2, 1], [1, 2], [1, 1]]] } // poly1 similar triangle inside poly2 > var poly3 = { "type" : "polygon", "coordinates" : [[[1, 0], [-2, 0], [1, 3], [1, 0]]] } // poly3 poly1 flipped around "vertical" edge, bumped on 1 unit, intersects poly1 not contained in > db.test.insert({ "loc" : poly2 }) > db.test.insert({ "loc" : poly3 }) > db.test.ensureindex({ "loc" : "2dsphere" }) > db.test.find({ "loc" : {     "$geointersects" : {         "$geometry" : poly1     } } }) // poly2 , poly3 returned > db.test.find({ "loc" : {     "$geowithin" : {         "$geometry" : poly1     } } }) // poly2 returned

Comments

Post a Comment

Popular posts from this blog

java - Spring Data JPA: Why findOne(id) executing delete query internally? -

i have 1 application using @manytomany annotation link 2 different entities 1 parent entity. not sure if have implemented properly. when execute .findone() on parent entity's repository find it, @ first fetch data along executing delete queries internally delete record mapping table (a table jpa creates after adding @manytomany annotation.). following generated sql queries , code snippet: java class @entity @table(name = "inventory") public class inventory { @id long id; // many other properties @manytomany(fetch=fetchtype.lazy) private list<stream> streams; @manytomany(fetch=fetchtype.lazy) private list<subject> subjects; } there no other annotation i've put in stream , subject entity class link inventory class. when run app, create following tables: inventory stream subject inventory_stream inventory_subject (inventory_stream , inventory_subject, 2 tables created automatically, don't k...
Read more

python - Mongodb How to add addtional information when aggregating? -

i beginner , wrote line pipeline works, wanna add other information output, screen name , or number of tweets.i tried add under $group gave me syntax error everytime here pipeline: def make_pipeline(): # complete aggregation pipeline pipeline = [ { '$match': { "user.statuses_count": {"$gt":99 }, "user.time_zone": "brasilia" } }, { "$group": { "_id": "$user.id", "followers": { "$max": "$user.followers_count" } } }, { "$sort": { "followers": -1 } }, { "$limit" : 1 } ]; i using on example : { "_id" : objectid("5304e2e3cc9e684aa98bef97"), "text" : "first week of school on :p", "in_reply_to_status_id" : null, "retweet_count" : null, ...
Read more

java - Incorrect order of records in M-M relationship in hibernate -

Image
i have 4 records in bridge table in mysql database. using @manytomany in hibernate, accurate order of employees incorrect incorrect of projects. following required material figure out doing mistake. this source. @entity @table(name="project") public class projectbean { @id @generatedvalue @column(name="project_id") private int projectid; @column(name="title") private string projecttitle; @manytomany(mappedby="projects") private collection<employeebean> employees; public projectbean() { employees = new arraylist<employeebean>(); } //getters & setters } @entity @table(name="employee") public class employeebean { @id @generatedvalue @column(name="employee_id") private int employee_id; @column(name="first_name") private string ...
Read more