能否用MongoDB地理空间查询判断点是否在批量小区多边形内？

Absolutely feasible! MongoDB’s geospatial capabilities are tailor-made for this scenario—even with 5000 neighborhood polygon records, you can efficiently check if a given coordinate falls within any of them. Let’s break down how to implement this step by step.

1. Feasibility Overview #

MongoDB supports GeoJSON-based geospatial queries and indexes, which handle polygon containment checks seamlessly. With a proper 2dsphere index, querying 5000 polygons will be fast enough for most use cases (no performance bottlenecks here unless you’re dealing with tens of millions of records).

2. Document Schema Design #

You’ll need to store each neighborhood’s polygon as a GeoJSON Polygon (note: GeoJSON uses [longitude, latitude] order, the reverse of your sample data’s structure). Here’s the recommended schema:

{
  "_id": ObjectId("..."),
  "name": "Greenwood Apartments", // Optional: neighborhood identifier for clarity
  "geofence": {
    "type": "Polygon",
    "coordinates": [
      [
        [77.67696, 12.9475827],    // [longitude, latitude]
        [77.674655, 12.9477697],
        [77.67454, 12.9463797],
        [77.675466, 12.946131],
        [77.675473, 12.947066],
        [77.676847, 12.947198],
        [77.67695, 12.94757],
        [77.67696, 12.9475827]     // Critical: Close the polygon by repeating the first point
      ]
    ]
  }
}

Key notes:

• Always close the polygon by repeating the first coordinate as the last one (follows GeoJSON standards and avoids edge-case issues).
• The coordinates array for a Polygon is an array of linear rings—for a simple neighborhood boundary, you’ll only need one ring (the outer perimeter).

3. Create a Geospatial Index #

To make queries efficient, create a 2dsphere index on the geofence field. This index optimizes MongoDB’s geospatial query engine for fast containment checks:

db.neighborhoods.createIndex({ geofence: "2dsphere" })

4. Query to Check if a Point is in Any Polygon #

To check if the point (12.948, 77.66) (latitude, longitude) falls within any neighborhood, use the $geoWithin operator with a GeoJSON Point. Remember to reverse the coordinates to match GeoJSON’s [longitude, latitude] order:

Find all neighborhoods containing the point: #

db.neighborhoods.find({
  geofence: {
    $geoWithin: {
      $geometry: {
        type: "Point",
        coordinates: [77.66, 12.948] // [longitude, latitude]
      }
    }
  }
})

Just check if any neighborhood contains the point: #

If you only need a true/false result instead of full neighborhood details, use findOne or count matches:

// Option 1: Check for existence of a matching neighborhood
const isInside = !!db.neighborhoods.findOne({
  geofence: {
    $geoWithin: {
      $geometry: {
        type: "Point",
        coordinates: [77.66, 12.948]
      }
    }
  }
})

// Option 2: Count matching documents
const matchCount = db.neighborhoods.countDocuments({
  geofence: {
    $geoWithin: {
      $geometry: {
        type: "Point",
        coordinates: [77.66, 12.948]
      }
    }
  }
})
const isInside = matchCount > 0

Quick Pro Tips #

• Double-check coordinate order: Mixing up longitude/latitude is a common pitfall—GeoJSON strictly uses [lon, lat].
• For neighborhoods with inner holes (like a central park), add additional linear rings to the coordinates array (the first ring is the outer boundary, subsequent rings are holes).
• If you need to optimize further for very high traffic, consider pre-filtering with a bounding box query before running the point-in-polygon check, but for 5000 records, this is usually unnecessary with a 2dsphere index.

内容的提问来源于stack exchange，提问作者deadly beast