Suppose you have two compound geo indexes defined on the same collection. For instance:

Currently, the explain() output for queries that should use these indexes is deficient the following ways:

1. The exact index being used isn't noted. All we get is the cursor type: GeoSearchCursor.

2. The index bound aren't provided for either field. This makes it impossible to know whether the compound index is even worth maintaining.

For instance:

"cursor" : "GeoSearchCursor",
"nscanned" : 1,
"nscannedObjects" : 1,
"n" : 1,
"millis" : 0,
"nYields" : 0,
"nChunkSkips" : 0,
"isMultiKey" : false,
"indexOnly" : false,
"indexBounds" : {}