mongodb type_error ai_generated true

MongoServerError: Can't use geo index with non-geo query filter: expected field 'location' to be a GeoJSON object

ID: mongodb/geo-index-with-non-geo-query

Also available as: JSON · Markdown · 中文
88%Fix Rate
86%Confidence
1Evidence
2024-03-05First Seen

Root Cause

A 2dsphere or 2d index exists on a field, but the query filter uses a non-geospatial operator (e.g., $eq, $regex) on the same field, causing type mismatch.

generic

中文

字段上存在 2dsphere 或 2d 索引，但查询过滤器在同一字段上使用了非地理空间操作符（如 $eq、$regex），导致类型不匹配。

Official Documentation

https://www.mongodb.com/docs/manual/core/index-geospatial/

Workarounds

  1. 90% success Ensure the field contains valid GeoJSON data (e.g., {type: 'Point', coordinates: [lng, lat]}) and use geospatial operators like $geoWithin in the query. Example: db.places.find({location: {$geoWithin: {$centerSphere: [[-73.97, 40.77], 0.01]}}}) 
    Ensure the field contains valid GeoJSON data (e.g., {type: 'Point', coordinates: [lng, lat]}) and use geospatial operators like $geoWithin in the query. Example: db.places.find({location: {$geoWithin: {$centerSphere: [[-73.97, 40.77], 0.01]}}})
  2. 85% success If the field is not geospatial, drop the geo index and create a regular index (e.g., db.collection.createIndex({location: 1})), then use non-geo queries. 
    If the field is not geospatial, drop the geo index and create a regular index (e.g., db.collection.createIndex({location: 1})), then use non-geo queries.

中文步骤

  1. Ensure the field contains valid GeoJSON data (e.g., {type: 'Point', coordinates: [lng, lat]}) and use geospatial operators like $geoWithin in the query. Example: db.places.find({location: {$geoWithin: {$centerSphere: [[-73.97, 40.77], 0.01]}}})
  2. If the field is not geospatial, drop the geo index and create a regular index (e.g., db.collection.createIndex({location: 1})), then use non-geo queries.

Dead Ends

Common approaches that don't work:

  1. 85% fail

    Removing the geo index entirely bypasses the error but degrades geospatial query performance; the error returns if the index is recreated.

  2. 80% fail

    Changing the query to use $geoWithin or $near without converting the field data to GeoJSON format still fails with a similar error.