ignore unmapped fields on geo-queries

Addresses issue #123

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Search response will include records which don't even have spatial attributes.

What is the new/expected behavior?

Correctly filters records meeting spatial criteria.

Have you added/updated Unit Tests and Integration Tests?

YES