Geospatial
Storing, indexing, and querying location data — core to Localz as a 'find providers near me' marketplace, not just background theory.
Why we need this / what value this brings
Naive proximity search (compute distance to every row, then sort) doesn't scale — proper geospatial indexing is what keeps 'near me' queries fast as the provider count grows.
When to use this
As soon as any 'nearby'/'distance'/map-based search feature exists — this isn't optional once location matters to the product.
How to use or implement this
Start with PostGIS on the existing Postgres instance (adds proper spatial types and indexes) before reaching for a separate geospatial database or service.
Subtopics
Research questions
- What geo queries does Localz actually need: 'providers within N km', 'sort by distance', map-view bounding-box search — which ones are built today?
Empty folder — drop notes, links, and findings here as you research.