The system has encountered a MongoDB error stating: 'Unable to retrieve geographical keys from object' specifically with Type: Point

Question

The system has encountered a MongoDB error stating: 'Unable to retrieve geographical keys from object' specifically with Type: Point

Trying to set up my database field for geocoding like this:

MyCollection._ensureIndex({'data.address.located':'2dsphere'});

However, encountering an error message:

MongoError: Can't extract geo keys from object, malformed geometry?:
{ type: "Point", coordinates: [ 32.4586858, -110.8571443 ] }

Having trouble identifying the issue with this field. Any suggestions?

Referencing this link, it provides this example:

The following example stores a GeoJSON Point:

{ loc: { type: "Point", coordinates: [ 40, 5 ] } }

javascript mongodb meteor

Answer 1

Answer №1

It seems that there is an issue with the given coordinates

[ 32.4586858, -110.8571443 ]

as they do not follow the correct format for longitude and latitude. The order should be longitude first followed by latitude, but in this case it appears to be reversed (since the valid latitude range is -90 to 90 and -110.8571443 falls outside of that).

Perhaps you intended:

{ type: "Point", coordinates: [ -110.8571443, 32.4586858 ] }

or there may have been another input error.

Answer 2

It seems that there is an issue with the given coordinates

[ 32.4586858, -110.8571443 ]

as they do not follow the correct format for longitude and latitude. The order should be longitude first followed by latitude, but in this case it appears to be reversed (since the valid latitude range is -90 to 90 and -110.8571443 falls outside of that).

Perhaps you intended:

{ type: "Point", coordinates: [ -110.8571443, 32.4586858 ] }

or there may have been another input error.

Answer 3

Answer №2

As highlighted by the user @go-oleg, the issue lies in the specified range of coordinates:

Longitude: (+-) 180°
Latitude: (+-) 90°

The index expects the coordinates to fall within these boundaries.

If you are trying to utilize the index on data that has already been imported and discover that the coordinates are switched, it would be more efficient to simply swap them back instead of reimporting the entire collection. The following mongoshell script can help with this:

Assuming you have a properly formatted GeoJSON object of type Point.

db.coll.find().forEach(function (e) {
    // assuming `geoJson` field contains `coordinates`
    e.geoJson.coordinates = [ // Swapping Lat/Lon
        e.geoJson.coordinates[1], // Longitude comes first
        e.geoJson.coordinates[0] // Latitude comes last
    ];
    db.coll.save(e);
    // Optionally, include a `print(e.name)` statement here to track progress
});

Answer 4

As highlighted by the user @go-oleg, the issue lies in the specified range of coordinates:

Longitude: (+-) 180°
Latitude: (+-) 90°

The index expects the coordinates to fall within these boundaries.

If you are trying to utilize the index on data that has already been imported and discover that the coordinates are switched, it would be more efficient to simply swap them back instead of reimporting the entire collection. The following mongoshell script can help with this:

Assuming you have a properly formatted GeoJSON object of type Point.

db.coll.find().forEach(function (e) {
    // assuming `geoJson` field contains `coordinates`
    e.geoJson.coordinates = [ // Swapping Lat/Lon
        e.geoJson.coordinates[1], // Longitude comes first
        e.geoJson.coordinates[0] // Latitude comes last
    ];
    db.coll.save(e);
    // Optionally, include a `print(e.name)` statement here to track progress
});

Answer 5

Answer №3

While I had the correct longitude and latitude order, I encountered a problem. The issue was that I had written coordiantes instead of coordinates, causing MongoDB to show this error:

pymongo.errors.WriteError: Can't extract geo keys: {data}  Point must be an array or object

It's possible that you have the right ordering but there may be an issue with your key names.

Answer 6

While I had the correct longitude and latitude order, I encountered a problem. The issue was that I had written coordiantes instead of coordinates, causing MongoDB to show this error:

pymongo.errors.WriteError: Can't extract geo keys: {data}  Point must be an array or object

It's possible that you have the right ordering but there may be an issue with your key names.

Answer 7

Answer №4

Although the issue has been resolved, it's worth noting that this bug could resurface if the type of GeoJSON object is omitted.

In my situation, I was able to fix it by including type: 'Point' in the model's value.

Answer 8

Although the issue has been resolved, it's worth noting that this bug could resurface if the type of GeoJSON object is omitted.

In my situation, I was able to fix it by including type: 'Point' in the model's value.

Answer 9

Answer №5

I encountered a similar error, but the root cause was having a LineString with two identical coordinates.

"geometry" : {
    "type" : "LineString",
    "coordinates" : [ 
        [ 
            143.345763, 
            -33.840952
        ], 
        [ 
            143.345763, 
            -33.840952
        ]
    ]
}

To resolve this issue, I had to convert it into a Point for it to be considered valid.

"geometry" : {
    "type" : "Point",
    "coordinates" : [ 
        143.345763, 
        -33.840952
    ]
}

Answer 10

I encountered a similar error, but the root cause was having a LineString with two identical coordinates.

"geometry" : {
    "type" : "LineString",
    "coordinates" : [ 
        [ 
            143.345763, 
            -33.840952
        ], 
        [ 
            143.345763, 
            -33.840952
        ]
    ]
}

To resolve this issue, I had to convert it into a Point for it to be considered valid.

"geometry" : {
    "type" : "Point",
    "coordinates" : [ 
        143.345763, 
        -33.840952
    ]
}

Answer 11

Answer №6

Start by inserting data in the correct object format to avoid errors.

schema :
location:{
            type: { type: String },
            coordinates:[mongoose.Schema.Types.Mixed]
        },

Then, proceed with inserting data into the database.

db.userDetails.createIndex({location: "2dsphere"})

An index will only be created if the location field contains an object.

Next, write a query to find the distance.

db.userDetails.aggregate( [
 $geoNear: {
                  near: { type: "Point",  coordinates: [data.lat1,data.lon1]},
                  spherical: true,
                  "distanceMultiplier" : 0.001,
                  distanceField: "calcDistance",
                  $maxDistance: distance,

               }
] )

Lastly, make sure to pass data without using quoted strings like this:

"lat":18.7323
"lon":73.1232

This is important for proper data handling.

Answer 12

Start by inserting data in the correct object format to avoid errors.

schema :
location:{
            type: { type: String },
            coordinates:[mongoose.Schema.Types.Mixed]
        },

Then, proceed with inserting data into the database.

db.userDetails.createIndex({location: "2dsphere"})

An index will only be created if the location field contains an object.

Next, write a query to find the distance.

db.userDetails.aggregate( [
 $geoNear: {
                  near: { type: "Point",  coordinates: [data.lat1,data.lon1]},
                  spherical: true,
                  "distanceMultiplier" : 0.001,
                  distanceField: "calcDistance",
                  $maxDistance: distance,

               }
] )

Lastly, make sure to pass data without using quoted strings like this:

"lat":18.7323
"lon":73.1232

This is important for proper data handling.

Answer 13

Answer №7

One issue I encountered was that the coordinates were initially stored as strings rather than integers or floats.

To resolve this, I made the following adjustment:

{ type: "Point", coordinates: [ "9.27261834568901", "55.9298104971287" ] } }

Modified to:

{ type: "Point", coordinates: [ 9.27261834568901, 55.9298104971287 ] } }

Using:

const new_lat = parseFloat(old_lat)

Answer 14

One issue I encountered was that the coordinates were initially stored as strings rather than integers or floats.

To resolve this, I made the following adjustment:

{ type: "Point", coordinates: [ "9.27261834568901", "55.9298104971287" ] } }

Modified to:

{ type: "Point", coordinates: [ 9.27261834568901, 55.9298104971287 ] } }

Using:

const new_lat = parseFloat(old_lat)

The system has encountered a MongoDB error stating: 'Unable to retrieve geographical keys from object' specifically with Type: Point

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Answer №6

Answer №7

Similar questions

Is there a way to retrieve the JavaScript variable name for a rhandsontable displayed in a Shiny application?

Bootstrap / Blazor - no action when clicking on an image link

Oops, there was an issue while trying to delete the user with ID "delete8" on the local server. Access was

Taking you back to the main page

What is the best way to conceal the second and fourth rows of a table using either css or jquery?

An effective approach to retrieving the results of a query by leveraging the observer pattern

What is the best way to alter the href of menu items while excluding 2 specific items

Unveil the socket connection using web sockets

Deleting object properties in JavaScript is not possible

Tips on utilizing CSS modules in React without changing class names

What causes a ReferenceError when attempting to retrieve the class name of a React component?

Node.js Express causing JSON object formatting issue with MongoDB insertion

Sending a piece of state information to a different component

Generate an array that can be accessed across all components

Here is a unique rewrite of the text:"Implementing a feature to upload an image in PHP and AJAX without

Utilize MongoDB provider to efficiently sort through numerous parameters

magnetic container: stationary container nested within absolutely positioned container

When JSON data is copied and displayed in Node.js or JavaScript, it appears as a string

Determine the frequency of duplicate elements in an array and arrange them in descending order based on their frequency

Error message: Next.js - Unable to access properties of an undefined object (user)