#community-help

Geo Shape Indexing in TypeSense: Proposed Features and Integration

TLDR Timon requested for geo shape indexing on TypeSense, a feature found in Elasticsearch. Kishore Nallan acknowledged that the feature could be implemented with user assistance for API design and testing.

25mo

Join the chat

Dec 11, 2021 (25 months ago)

Photo of md5-047f1a87663ea0dcc43a01fc89a14f08

Timon

01:03 PM

Hi! First, I want to thank the maintainers for this awesome tool! I really love how easy it is to install and use TypeSense. Currently, you support operations on geo points. Is indexing geo shapes such as polygons with operations like the one offered by Elasticsearch (point within Polygon, intersecting Polygons...) on your roadmap? Do you have plans to integrate it?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

01:09 PM

👋 Timon Sorry I think I missed responding to your (?) earlier comment on this feature request which had been created earlier: https://github.com/typesense/typesense/issues/421

We will be happy to add this to our short term roadmap if you have an immediate use case for this and can work closely with us to develop these additional geo features 🙂

Timon

01:36 PM

Kishore Nallan I appreciate the prompt response. Indeed, this is me :=). I would love to help you on this feature. To explain my use-case: Imagine indexing polygons in TypeSense (for me, these are geo administrative boundaries). The operation I would like to apply is to throw a geopoint at TypeSense and filter all polygons out that do not include this geo point (kind of the reverse what is possible now: filter geopoints with a polygon). In Elasticsearch this is called "WITHIN". Sadly, I have no cpp experience. But I can do some research on indexing strategies (quadtree etc) and write a proposal for it. But maybe you are experienced in geospatial indexing?

Kishore Nallan

03:01 PM

Thanks for explaining! We can implement this with the current library we are using so certainly it should not be too difficult. Your inputs on the API design and testing on your dataset should be sufficient support for us!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Optimizing Bulk Indexing and Reducing RAM Usage in Typesense

Timon experienced issues with Typesense becoming unresponsive during bulk indexing and sought advice. Jason recommended larger import requests and adjusting the client-side timeout allowance, revealing a need to increase RAM allocation for Docker. Kishore Nallan undertook to find ways to optimize memory usage, particularly for geopoint indexing.

25mo

Guiding GeoPoint Search with Typesense's Polygon

Ignacio had trouble with geopoint search in Typesense. Jason helped them solve it by using the counter-clockwise method with polygon points. The solution was posted on GitHub for future reference.

30mo

Using TypeSense for Geolocation Tagged Job Search

Nicholas needed help to enable geo-location based job search on a board. James suggested using filter_by from TypeSense, while Jason elaborated on 'OR' and 'AND' operations in TypeSense.

27mo