Skip to content

Support for Geo Queries Within Main Query Structure #117

Closed
@armanhadifatah

Description

@armanhadifatah

Description:

Currently, geo queries in Convex are implemented as a completely separate system from the main query engine. This separation creates unnecessary complexity, especially for real-world applications where spatial data is just one of many filtering dimensions.

For example, in a real estate app, we often need to query properties based on multiple criteria such as:

Number of bedrooms

Price range

Property type

AND location (latitude/longitude radius)

Right now, combining a geo query with these other filters is cumbersome because the geo query is treated as a distinct system, almost like querying a separate database. This limits composability and makes the developer experience more fragmented.

Proposal:

Unify geo queries with the main Convex query system, so spatial filtering can be composed directly alongside other standard filters. This would significantly simplify use cases involving geospatial data and make Convex more suitable for location-based apps.

Benefits:

Easier to build apps with combined filtering (e.g., "Find nearby apartments under $1000/month with 2+ bedrooms")

Cleaner, more intuitive developer experience

Better alignment with real-world use cases where location is just one of many filters

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions