---
title: "Discussion on \"Geo Queries and Firebase\" | Hashnode"
description: "Discussion on \"Geo Queries and Firebase\". We can’t execute geo queries by simply storing latitude and longitude as distinct variables and querying a bounding box since Cloud Firestore only permits one range clause per compound query.\nOne solution for this as mentioned in Firebase documents i..."
url: "https://hashnode.com/posts/geoqueries-and-firebase-2781d98820cd/628a8993aad1d35780a0013c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Geo Queries and Firebase](https://ashya.hashnode.dev/geoqueries-and-firebase-2781d98820cd?utm_source=hashnode&utm_medium=feed)

We can’t execute geo queries by simply storing latitude and longitude as distinct variables and querying a bounding box since Cloud Firestore only permits one range clause per compound query. One solution for this as mentioned in Firebase documents i...

Jan 17, 2022 · 5 min read · ashya.hashnode.dev  
Read the article

-   [#firebase](https://hashnode.com/tag/firebase)
-   [#geolocation](https://hashnode.com/tag/geolocation)
-   [#firestore](https://hashnode.com/tag/firestore)

## Written by

[Ash Vic](https://hashnode.com/@AshCatchEmAll)

@AshCatchEmAll

  
[View profile](https://hashnode.com/@AshCatchEmAll)

My name is Ash, I don't own a pikachu yet, but my love for coding and creating isn't shocking at all.

My name is Ash, I don't own a pikachu yet, but my love for coding and creating isn't shocking at all.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
