Find duplicates of rounded geometries with mongo aggregation
up vote
0
down vote
favorite
I have the following mongodb query which find objects by duplicated geometries within a collection:
db.coll.aggregate([{
$match: { // Selection
}
},
{
$group: {
_id: {
geometry: "$geometry"
},
dups: {
"$addToSet": "$_id"
},
count: {
"$sum": 1
}
}
},
{
$match: {
count: {
"$gt": 1
} // Duplicates considered as count greater than one
}
}
],
{ allowDiskUse: true }
I would like to change this query to find "similar" geometries, which means if the first n digit of the coordinates (so floored coordinates) are the same they should consider identical. All of my geometries are LineStrings.
mongodb aggregation-framework
add a comment |
up vote
0
down vote
favorite
I have the following mongodb query which find objects by duplicated geometries within a collection:
db.coll.aggregate([{
$match: { // Selection
}
},
{
$group: {
_id: {
geometry: "$geometry"
},
dups: {
"$addToSet": "$_id"
},
count: {
"$sum": 1
}
}
},
{
$match: {
count: {
"$gt": 1
} // Duplicates considered as count greater than one
}
}
],
{ allowDiskUse: true }
I would like to change this query to find "similar" geometries, which means if the first n digit of the coordinates (so floored coordinates) are the same they should consider identical. All of my geometries are LineStrings.
mongodb aggregation-framework
2
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or ofPolygon
,MultiPolygon
orLineString
since they are all basically different in structure. That's by-design
– Neil Lunn
Nov 19 at 15:12
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have the following mongodb query which find objects by duplicated geometries within a collection:
db.coll.aggregate([{
$match: { // Selection
}
},
{
$group: {
_id: {
geometry: "$geometry"
},
dups: {
"$addToSet": "$_id"
},
count: {
"$sum": 1
}
}
},
{
$match: {
count: {
"$gt": 1
} // Duplicates considered as count greater than one
}
}
],
{ allowDiskUse: true }
I would like to change this query to find "similar" geometries, which means if the first n digit of the coordinates (so floored coordinates) are the same they should consider identical. All of my geometries are LineStrings.
mongodb aggregation-framework
I have the following mongodb query which find objects by duplicated geometries within a collection:
db.coll.aggregate([{
$match: { // Selection
}
},
{
$group: {
_id: {
geometry: "$geometry"
},
dups: {
"$addToSet": "$_id"
},
count: {
"$sum": 1
}
}
},
{
$match: {
count: {
"$gt": 1
} // Duplicates considered as count greater than one
}
}
],
{ allowDiskUse: true }
I would like to change this query to find "similar" geometries, which means if the first n digit of the coordinates (so floored coordinates) are the same they should consider identical. All of my geometries are LineStrings.
mongodb aggregation-framework
mongodb aggregation-framework
edited Nov 20 at 6:56
asked Nov 19 at 15:07
Paxi
418
418
2
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or ofPolygon
,MultiPolygon
orLineString
since they are all basically different in structure. That's by-design
– Neil Lunn
Nov 19 at 15:12
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54
add a comment |
2
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or ofPolygon
,MultiPolygon
orLineString
since they are all basically different in structure. That's by-design
– Neil Lunn
Nov 19 at 15:12
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54
2
2
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or of
Polygon
, MultiPolygon
or LineString
since they are all basically different in structure. That's by-design– Neil Lunn
Nov 19 at 15:12
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or of
Polygon
, MultiPolygon
or LineString
since they are all basically different in structure. That's by-design– Neil Lunn
Nov 19 at 15:12
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53377462%2ffind-duplicates-of-rounded-geometries-with-mongo-aggregation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
"... but I do not think it matters" - Oh it most certainly does. matter. GeoJSON uses varying formats, mostly with different "ring" configurations of nested arrays. So the exact type of data you want to "extract these points" from is intrinsically important to the structure of the aggregation pipeline. There is no "generic" way to break apart either/or of
Polygon
,MultiPolygon
orLineString
since they are all basically different in structure. That's by-design– Neil Lunn
Nov 19 at 15:12
Yes, you are right, I'm going to clarify the question then,
– Paxi
Nov 20 at 6:54