Well, it's doing a full table scan of 2M rows... The reason it is doing this is because more than ~35% of the values in the GeoFeatureLocationBoundingBox index fall between 1 and 2. In order to get the index to be used, you will need to supply more stringent criteria.
BTW, KimSeong Loh's comments made absolute sense when he wrote them. From your query in the first post, it looked like you were issuing an impossible query against an INT field. Since you did not supply the table schema, we wouldn't know if the field values *could* fall between 1 and 2...
Jay Pipes
Community Relations Manager, North America, MySQL Inc.
Got Cluster?
http://www.mysql.com/cluster
Personal:
http://jpipes.com